Renew your license to continue
Your evaluation license of Visibility for Confluence expired. Please use the Buy button to purchase a new license.
View this section on the website
See edit history of this section
Post feedback on this section
1. Requirements
2.1.2.4 The NASA Chief, SMA shall periodically review the project’s requirements mapping matrices.
1.1 Notes
NPR 7150.2, NASA Software Engineering Requirements, does not include any notes for this requirement.
1.2 History
Renew your license to continue
Your evaluation license of Visibility for Confluence expired. Please use the Buy button to purchase a new license.
2. Rationale
The NASA OSMA assesses project compliance matrices for a variety of reasons including identification of risk, the identification of patterns and trends that indicate areas of concern or potential need for requirements revision, and a general understanding of the intent of the requirements.
3. Guidance
Projects maintain and record NASA-STD-8739.8 compliance matrices for the life of the software project (see SWE-125 - Requirements Compliance Matrix). These matrices contain all requirements, waivers, and deviations necessary to perform software assurance and software safety requirements.
See also SWE-126 - Tailoring Considerations, SWE-139 - Shall Statements, SWE-140 - Comply with Requirements, SWE-150 - Review Changes To Tailored Requirements
Projects produce compliance matrices for planning purposes. NASA OSMA, upon request, can help projects address or understand any of the requirements in NASA-STD-8739.8 or in NASA NPR 7150.2. Rationale and guidance for each requirement in the NPR and Standard are contained in this NASA Software Engineering and Software Assurance handbook, NASA_HDBK-2203.
Projects should also have their NASA-STD-8739.8 compliance matrices available for review during the Office of Safety and Mission Assurance (OSMA) Quality Audit, Assessment and Review (QAAR) audit.
Additional data calls requiring compliance matrix data may come from the NASA Software Assurance Working Group.
The NASA OSMA reviews these compliance matrices looking for patterns and trends in waivers and deviations or tailoring of software engineering requirements. Such patterns and trends may indicate where projects or particular Centers need assistance to meet specific requirements. Such patterns may also indicate areas to be addressed in the next update of software engineering, software safety, or software assurance requirements to better clarify requirement intent, purpose, or means of fulfillment.
3.1 Additional Guidance
Additional guidance related to this requirement may be found in the following materials in this Handbook:
| Related Links |
|---|
3.2 Center Process Asset Libraries
SPAN - Software Processes Across NASA
SPAN contains links to Center managed Process Asset Libraries. Consult these Process Asset Libraries (PALs) for Center-specific guidance including processes, forms, checklists, training, and templates related to Software Development. See SPAN in the Software Engineering Community of NEN. Available to NASA only. https://nen.nasa.gov/web/software/wiki 197
See the following link(s) in SPAN for process assets from contributing Centers (NASA Only).
| SPAN Links |
|---|
4. Small Projects
No additional guidance is available for small projects.
5. Resources
5.1 References
Renew your license to continue
Your evaluation license has expired. Contact your administrator to renew your Reporting for Confluence license.
Renew your license to continue
Your evaluation license of Visibility for Confluence expired. Please use the Buy button to purchase a new license.
5.2 Tools
NASA users find this in the Tools Library in the Software Processes Across NASA (SPAN) site of the Software Engineering Community in NEN.
The list is informational only and does not represent an “approved tool list”, nor does it represent an endorsement of any particular tool. The purpose is to provide examples of tools being used across the Agency and to help projects and centers decide what tools to consider.
6. Lessons Learned
There are currently no Lessons Learned identified for this requirement.
