Select products and product components to be validated and the validation methods that will be used for each.


Products and product components are selected for validation based on their relationship to end user needs. For each product component, the scope of the validation (e.g., operational behavior, maintenance, training, user interface) should be determined.


Examples of products and product components that can be validated include the following:
  • Product and product component requirements and designs
  • Product and product components (e.g., system, hardware units, software, service documentation)
  • User interfaces
  • User manuals
  • Training materials
  • Process documentation
  • Access protocols
  • Data interchange reporting formats

The requirements and constraints for performing validation are collected. Then, validation methods are selected based on their ability to demonstrate that end user needs are satisfied. The validation methods not only define the approach to product validation, but also drive the needs for the facilities, equipment, and environments. The validation approach and needs can result in the generation of lower level product component requirements that are handled by the requirements development processes. Derived requirements, such as interface requirements to test sets and test equipment, can be generated. These requirements are also passed to the requirements development processes to ensure that the product or product components can be validated in an environment that supports the methods.

Validation methods should be selected early in the life of the project so they are clearly understood and agreed to by relevant stakeholders.

Validation methods address the development, maintenance, support, and training for the product or product component as appropriate.


Examples of validation methods include the following:
  • Discussions with end users, perhaps in the context of a formal review
  • Prototype demonstrations
  • Functional demonstrations (e.g., system, hardware units, software, service documentation, user interfaces)
  • Pilots of training materials
  • Tests of products and product components by end users and other relevant stakeholders
  • Incremental delivery of working and potentially acceptable product
  • Analyses of product and product components (e.g., simulations, modeling, user analyses)


Hardware validation activities include modeling to validate form, fit, and function of mechanical designs; thermal modeling; maintainability and reliability analysis; timeline demonstrations; and electrical design simulations of electronic or mechanical product components.

Example Work Products

  1. Lists of products and product components selected for validation
  2. Validation methods for each product or product component
  3. Requirements for performing validation for each product or product component
  4. Validation constraints for each product or product component


1. Identify the key principles, features, and phases for product or product component validation throughout the life of the project.

2. Determine which categories of end user needs (operational, maintenance, training, or support) are to be validated.

The product or product component should be maintainable and supportable in its intended operational environment. This specific practice also addresses the actual maintenance, training, and support services that can be delivered with the product.


An example of evaluation of maintenance concepts in the operational environment is a demonstration that maintenance tools are operating with the actual product.

3. Select the product and product components to be validated.

4. Select the evaluation methods for product or product component validation.

5. Review the validation selection, constraints, and methods with relevant stakeholders.