bannerb

This version of SWEHB is associated with NPR 7150.2B. Click for the latest version of the SWEHB based on NPR7150.2C

SWE-152 - Review Compliance Matrices

1. Requirements

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

1.1 Notes

NPR 7150.2, NASA Software Engineering Requirements, does not include any notes for this requirement.


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 257 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 257 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) audits. 

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:

SWE-122

Technical Authority Appointment

SWE-125

Requirements Compliance Matrix

SWE-126

Waiver and Deviation Considerations

SWE-139

Shall Statements

SWE-140

Comply with Requirements

SWE-145

Indicate Approval

SWE-150

Review Changes To Tailored Requirements

4. Small Projects

No additional guidance is available for small projects.


5. Resources


5.1 Tools

Tools relative to this SWE may be found in the table below. You may wish to reference the Tools Table in this handbook for an evolving list of these and other tools in use at NASA. Note that this table should not be considered all-inclusive, nor is it an endorsement of any particular tool. Check with your Center to see what tools are available to facilitate compliance with this requirement.

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

 

6. Lessons Learned

There are currently no Lessons Learned identified for this requirement.


  • No labels