Monday, November 12, 2007

Validate Product or Product Components: Specific Practices By Goal SG2

The product or product components are validated to ensure that they are suitable for use in their intended operating environment.
The validation methods, procedures, and criteria are used to validate the selected products and product components and any associated maintenance, training, and support services using the appropriate validation environment.


SP 2.1 Perform Validation
Perform validation on the selected products and product components.
To be acceptable to users, a product or product component must perform as expected in its intended operational environment.

Validation activities are performed and the resulting data are collected according to the established methods, procedures, and criteria.
The as-run validation procedures should be documented and the deviations occurring during the execution should be noted, as appropriate.
(For users of the continuous representation, this is a capability level 1 specific practice. Validation processes at capability level 1 or 2 may not include procedures and criteria, which are created in the Establish
Validation Procedures and Criteria specific practice at capability level 3. When there are no procedures or criteria established, use the methods established by the Select Products for Validation specific practice to
accomplish capability level 1 performance.)


Typical Work Products
1. Validation reports
2. Validation results
3. Validation cross-reference matrix
4. As-run procedures log
5. Operational demonstrations

SP 2.2 Analyze Validation Results
Analyze the results of the validation activities and identify issues.
The data resulting from validation tests, inspections, demonstrations, or evaluations are analyzed against the defined validation criteria. Analysis reports indicate whether the needs were met; in the case of deficiencies, these reports document the degree of success or failure and categorize probable cause of failure. The collected test, inspection, or review results are compared with established evaluation criteria to determine whether to proceed or to address requirements or design issues in the requirements development or technical solution processes.
Analysis reports or as-run validation documentation may also indicate that bad test results are due to a validation procedure problem or a validation environment problem.

Typical Work Products
1. Validation deficiency reports
2. Validation issues

3. Procedure change request
Subpractices
1. Compare actual results to expected results.
2. Based on the established validation criteria, identify products and product components that do not perform suitably in their intended operating environments, or identify problems with the methods,
criteria, and/or environment.
3. Analyze the validation data for defects.
4. Record the results of the analysis and identify issues.
5. Use validation results to compare actual measurements and performance to intended use or operational need.