SWE-212 - NASA-STD-8739 Mapping Matrices

1. Requirements 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

SWE-212 - Used first in NPR 7150.2D

RevSWE Statement

Difference between A and B




Difference between B and C



Difference between C and D

First use of this SWE in D

In previous versions this was a will statement

D The NASA Chief, SMA shall periodically review the project’s requirements mapping matrices.

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). These matrices contain all requirements, waivers, and deviations necessary to perform software assurance and software safety 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 compliance matrices may be found in the following related requirements in this Handbook:

4. Small Projects

No additional guidance is available for small projects.

5. Resources

5.1 References

No references have been currently identified for this SWE. If you wish to suggest a reference, please leave a comment below.

5.2 Tools

Tools to aid in compliance with this SWE, if any, may be found in the Tools Library in the NASA Engineering Network (NEN). 

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.

  • No labels