As a result of successful implementation of this process:

ENG 2.1 A defined set of system requirements is established

ENG 2.2 System requirements are categorized and analyzed for correctness and testability

ENG 2.3 The impact of the system requirements on the operating environment is evaluated

ENG 2.4 Prioritization for implementing the system requirements is defined

ENG 2.5 The system requirements are approved and updated as needed

ENG 2.6 Consistency and bilateral traceability are established between customer requirements and system requirements

ENG 2.7 Changes to the customer’s requirements baseline are evaluated for cost, schedule and technical impact

ENG 2.8 The system requirements are communicated to all affected parties and baselined

NOTE: For system requirements specifications, the IEEE-Standard 1233- 1998, Guide for Developing System Requirements Specifications might be used.

NOTE 1: System requirements may be categorized in terms of feasibility and risk.

NOTE 2: System requirements may typically include functional, performance, interface, design requirements and verification criteria. Verification criteria define the qualitative and quantitative criteria for verification of a requirement. Verification criteria demonstrate that a requirement can be verified within agreed constraints.

NOTE 3: Analysis of system requirements for testability includes development of verification criteria.