bannerb

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Fixed SWE table in tab 3

...

Tabsetup
1. The Requirement
1. The Requirement
12. Rationale
23. Guidance
34. Small Projects
45. Resources
56. Lessons Learned
Div
idtabs-1

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.


Div
idtabs-2

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

Swerefn
refnum257
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.”

Div
idtabs-3

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

Swerefn
refnum257
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:

Indicate Approval

- Approve Waivers and Deviations
SWE-150
- Review Changes To Tailored Requirements
Div
idtabs-4

4. Small Projects

No additional guidance is available for small projects.


Div
idtabs-5

5. Resources

 
refstable


toolstable
 

Div
idtabs-6

6. Lessons Learned

There are currently no Lessons Learned identified for this requirement.