SWE-152 - Review Requirements Mapping Matrices

1. Requirements The NASA OCE shall periodically review the project 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-152 - Last used in rev NPR 7150.2D

RevSWE Statement

Difference between A and B


B The NASA Office of the Chief Engineer (OCE) shall periodically review project compliance matrices.

Difference between B and CRemoved "Office of the Chief Engineer" and just left the acronym;
Changed "compliance" to "requirements mapping" matrix.
C The NASA OCE shall periodically review the project requirements mapping matrices. 

Difference between C and DNo change
D The NASA OCE shall periodically review the project requirements mapping matrices.

2. Rationale

The NASA OCE assesses project compliance matrices for a variety of reasons including the identification of patterns and trends that indicate areas of concern or potential need for requirements revision.  This requirement also helps address the NPD 7120.4 policy for the NASA Chief Engineer:

NASA Engineering and Program/Project Management Policy - NPD 7120.4E

5.b.12 - Maintain periodic oversight of compliance with the Office of the Chief Engineer's policy, procedural requirements, and standards throughout the Agency and its contractor community. 257

3. Guidance

Projects maintain and record NPR 7150.2 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 complete the software development life cycle.  See also Topic 7.16 - Appendix C. Requirements Mapping and Compliance Matrix

Projects provide approved compliance matrices (see SWE-126 - Tailoring Considerations) to the NASA OCE, upon request, to help address NPR 7120.4 policy for managers and engineers to:

NASA Engineering and Program/Project Management Policy - NPD 7120.4E

5.j.8 - "Support and provide information for assessments of Centers' and contractors' capabilities and compliance with engineering and program/project management requirements and standards.” 257

Projects also have compliance matrices available for review during OCE surveys and the Office of Safety and Mission Assurance (OSMA) Quality Audit, Assessment and Review (QAAR) audit. See also SWE-150 - Review Changes To Tailored Requirements

Additional data calls requiring compliance matrix data may come from the NASA Software Working Group.

The NASA OCE 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. See also SWE-139 - Shall Statements, SWE-140 - Comply with Requirements,

See also SWE-021 - Transition to a Higher Class, and Topic 7.13 - Transitioning to a Higher Class when reviewing compliance related to projects changing the Class of software. 

3.1 Additional Guidance

Additional guidance related to this requirement may be found in the following materials in this Handbook:

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.  197

See the following link(s) in SPAN for process assets from contributing Centers (NASA Only). 

4. Small Projects

No additional guidance is available for small projects.

5. Resources

5.1 References

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

6.1 NASA Lessons Learned

No Lessons Learned have currently been identified for this requirement.

6.2 Other Lessons Learned

No other Lessons Learned have currently been identified for this requirement.

  • No labels