3.10.5 The project manager shall record, address, and track to closure the results of software validation activities.
NPR 7150.2, NASA Software Engineering Requirements, does not include any notes for this requirement.
1.2 Applicability Across Classes
Simply performing validation is not sufficient to ensure the software will perform as intended in the customer environment. The project team must capture the results of validation activities to prove the validation was conducted and to document the findings from those activities. Identified issues need to be analyzed to determine the cause. The team then identifies associated resolutions, and tracks to closure the work to implement those resolutions. This completes the cycle and provides the best assurance that the software will be of high quality and perform as intended.
Where resolution involves revision to the validation process, environment, etc., tracking such issues helps to document process improvements and improve process quality resulting in more accurate validation results in the future.
The basic validation process is shown below with the steps addressed by this requirement highlighted:
Recording validation results and activities
Results and the validation activities and validated products that generated them can be recorded in the following ways, as appropriate for the validation method used:
Analyzing validation results
When analyzing validation results to determine whether those results support a conclusion that the software will perform as intended in the operational environment, consider the following steps:
Tracking discrepancies to closure
When tracking discrepancies to closure, consider the following activities:
Typical content and documentation
The following is a list of information typically captured in the validation results, analysis results, or in the post-analysis documentation of those results. This is not a complete list. Center procedures may call for additional information, or additional information may be needed to document fully the result or identified issue. Note that problem tracking or corrective action tools may capture some of this information automatically.
Center or project procedures may require additional documentation not described above.
The team reports the results of validation activities to one or more of the following:
Potential problems when recording, analyzing and tracking validation results include, but are not limited to:
Additional guidance related to Validation may be found in the following related requirements in this Handbook:
4. Small Projects
No additional guidance is available for small projects. The community of practice is encouraged to submit guidance candidates for this paragraph.
6. Lessons Learned
The NASA Lessons Learned database contains the following lessons learned related to validation: