Products and product components are selected for validation on the basis of their relationship to user needs. For each product component, the scope of the validation (e.g., operational behavior, maintenance, training, and user interface) should be determined.
The requirements and constraints for performing validation are collected. Then, validation methods are selected based on their ability to demonstrate that user needs are satisfied. The validation methods not only define the technical approach to product validation, but also drive the needs for the facilities, equipment, and environments. This may 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, may 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 the relevant stakeholders.
The validation methods address the development, maintenance, support, and training for the product or product component as appropriate.