Validate requirements to ensure the resulting product will perform as intended in the end user's environment.
Requirements validation is performed early in the development effort with end users to gain confidence that the requirements are capable of guiding a development that results in successful final validation. This activity should be
integrated with risk management activities. Mature organizations will typically perform requirements validation in a more sophisticated way using multiple techniques and will broaden the basis of the validation to include other stakeholder needs and
expectations.
Examples of techniques used for requirements validation include the following:
· Analysis
· Simulations
· Prototyping
· Demonstrations
Example Work Products
1. Record of analysis methods and results
Subpractices
1. Analyze the requirements to determine the risk that the resulting product will not perform appropriately in its intended use environment.
2. Explore the adequacy and completeness of requirements by developing product representations (e.g., prototypes, simulations, models, scenarios, storyboards) and by obtaining
feedback about them from relevant stakeholders.
Refer to the Validation process area for more information about preparing for validation and validating product or product components.
3. Assess the design as it matures in the context of the requirements validation environment to identify validation issues and expose unstated needs and customer
requirements.