a) Identify, collect, and prioritize acquirer's system requirements

User, customer, or assigned requirements for a system, or portion thereof, have been identified and defined in terms of needs, expectations, capabilities, and priorities, or of assigned requirements for a system, or portion thereof, as expressed in specifications. Specifically, the following have been identified, as applicable:

1. concept of operation

2. what the acquirer wants the products of the system to accomplish (functional requirements)

3. how well each function must be accomplished (performance requirements)

4. natural and induced environments in which the system products must operate or be used

5. design constraints such as use of non-developmental or reusable items

6. requirements pertaining to availability, electro-magnetic compatibility, health factors, human factors interoperability, maintainability, reliability, safety, and security

7. measures of effectiveness (MOEs) that reflect overall expectations against which satisfaction will be determined

8. constraints pertaining to development, production, test, deployment/installation, training, support/maintenance, and disposal.

b) Ensure completeness and consistency of the set of collected acquirer requirements

The collected user, customer, or assigned requirements are validated. Resolution of all conflicts and variances is competed. Invoked the Requirements Validation Process, Requirement 26.

c) Record set of acquirer requirements

Validated set of acquirer requirements is captured in the established information database.

a) Identify and collect other stakeholders end product requirements

Other types of requirements that can constrain the engineering...