For the purposes of this Standard, the following definitions apply:

acquirer

An enterprise, organization, or individual that obtains a product (good or service) from a supplier.

Note	The acquirer can be a customer or user of a desired system product, or can be a developer obtaining a lower layer product in the system hierarchy from another vendor or a developer in the role of supplier. An acquirer is a type of stakeholder.

agreement

An arrangement, not necessarily contractual, between two parties (an acquirer and a supplier) that defines the tasks to be performed, the items to be delivered, the acceptance criteria to be applied to delivered items, and other requirements affecting the development or procurement of system products.

assign

Designate a function, product, process, or other item as accountable for a particular purpose.

Note

The terms allocate or partition are used in some domains to denote this concept. The "assign" relationship can be in various forms: a) requirement to function, b) requirement to product or process, c) requirement to interface, d) function to product or process, e) function to external entity (e.g., the operator), or f) requirement to external entity (e.g., external system).

associated processes

Processes that enable one or more end products to be put into service, maintained in service, or retired from service.

building block

A representation of the conceptual framework of a system that is used for organizing the requirements, work, and other information associated with the engineering of a system. An element in the...