View this section on the website
See edit history of this section
Post feedback on this section
1. Requirements
2.1.1.3 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
2. Rationale
The NASA OCE assesses project compliance matrices for a variety of reasons including 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 to “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.”
3. Guidance
Projects maintain and record NPR 7150.2 compliance matrices for the life of the software project (see SWE-125). These matrices contain all requirements, waivers and deviations necessary to complete the software development life cycle.
Projects provide approved compliance matrices (see SWE-126) to the NASA OCE, upon request, to help address NPR 7120.4 policy for managers and engineers to “Support and provide information for assessments of Centers' and contractors' capabilities and compliance with engineering and program/project management requirements and standards.”
Projects also have compliance matrices available for review during OCE surveys and 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 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.
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
- (SWEREF-197) Software Processes Across NASA (SPAN) web site in NEN SPAN is a compendium of Processes, Procedures, Job Aids, Examples and other recommended best practices.
- (SWEREF-257) NPD 7120.4E, NASA Office of the Chief Engineer, Effective Date: June 26, 2017, Expiration Date: June 26, 2022
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
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.
