The generation and use of various requirements and representations are introduced in Subclause 4.3. These are further described below. Figure G.1 shows the relationship of these requirements.

Figure G.1: Requirement relationships

Acquirer requirements come from a customer or user (including operators, where applicable) for a major system such as an aircraft, automobile, check processor, mail sorter, or telecommunication switch. Acquirer requirements also come from a developer needing subsystems to make up an end product of a system (see Subclause 6.2). The latter are identified as assigned requirements and would have been defined by a prior application of the System Design processes of Subclause 4.3.

Other stakeholder requirements, when added to the acquirer requirements, make up a set of stakeholder requirements that are transformed into system technical requirements. Stakeholder and system technical requirements are identified, collected, or defined by completing the Requirements Definition Process (Subclause 4.3).

The logical and physical solution representations, derived technical requirements, design solution and specified requirements are defined by completing the Solution Definition Process (Subclause 4.3).

Stakeholder requirements (acquirer and other stakeholder requirements), as well as system technical requirements and the derived technical requirements, differ from specified requirements.

1. In effect, stakeholder requirements constitute the input that establishes the problem to be solved. Such requirements can be considered as the initial specification for a development effort or as a set of specified requirements for procuring an off-the-shelf item. End products developed or purchased, and that are to be or that have been delivered to...