Analyze requirements to ensure that they are necessary and sufficient.
In light of the operational concept and scenarios, the requirements for one level of the product hierarchy are analyzed to determine whether they are necessary and sufficient to meet the objectives of higher levels of the product hierarchy. The analyzed requirements then provide the basis for more detailed and precise requirements for lower levels of the product hierarchy.
As requirements are defined, their relationship to higher level requirements and the higher level definition of required functionality and quality attributes should be understood. Also, the key requirements used to track progress are determined. For instance, the weight of a product or size of a software product can be monitored through development based on its risk or its criticality to the customer.
Example Work Products
- Requirements defects reports
- Proposed requirements changes to resolve defects
- Key requirements
- Technical performance measures
1. Analyze stakeholder needs, expectations, constraints, and external interfaces to organize them into related subjects
2. Analyze requirements to determine whether they satisfy the objectives of higher level requirements.
3. Analyze requirements to ensure that they are complete, feasible, realizable, and verifiable.
While design determines the feasibility of a particular solution, this subpractice addresses knowing which requirements affect feasibility.
4. Identify key requirements that have a strong influence on cost, schedule, performance, or risk.
5. Identify technical performance measures that will be tracked during the development effort.
6. Analyze operational concepts and scenarios to refine the customer needs, constraints, and interfaces and to discover new requirements.
This analysis can result in more detailed operational concepts and scenarios as well as supporting the derivation of new requirements.