bannerc

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Tabsetup
1. The Requirement
1. The Requirement
12. Rationale
23. Guidance
34. Small Projects
45. Resources
56. Lessons Learned
Div
idtabs-1

1. Requirements

Excerpt

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

Expand
titleClick here to view the history of this requirement: SWE-152 History

Include Page
SITE:SWE-152 History
SITE:SWE-152 History

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

Div
idtabs-4

4. Small Projects

No additional guidance is available for small projects.


Div
idtabs-5

5. Resources

5.1 References

refstable
Show If
groupconfluence-users
Panel
titleColorred
titleVisible to editors only

Enter the necessary modifications to be made in the table below:

SWEREFs to be addedSWEREFS to be deleted


SWEREFs NOT called out in text but listed as germane: none

SWEREFs called out in the text: 257


5.2 Tools


Include Page
Tools Table Statement
Tools Table Statement

Div
idtabs-6

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.