1. Requirements

6.3.4 Centers and projects shall fully comply with the "shall" statements in this NPR that are marked with an "X" in Appendix D consistent with their software classification.

1.1 Notes">1.1 Notes

If the requirement is marked with a "SO" in appendix D, the project is required to meet the requirement to the extent necessary to satisfy the safety critical aspects of the software.

1.2 Applicability Across Classes

This requirement applies to all classes and safety criticalities.

Key:    A_SC = Class A Software, Safety-Critical | A_NSC = Class A Software, Not Safety-Critical | ... | - Applicable | - Not Applicable
^X - Applicable with details, read above for more | P(C) - P(Center), follow center requirements or procedures

2. Rationale

Earlier versions of NPR 7150.2, NASA Software Engineering Requirements, assumed that readers would accept requirements marked by an "X" in Appendix D as required activities. Experience with the baseline version of this NPR, i.e., NPR 7150.2, showed that this assumption was not universally confirmed.

The purpose of the Requirements Mapping Matrix in NPR 7150.2 is to essentially pre-tailor out requirements for less critical software systems, e.g., while Class A software has 111 invoked requirements for projects, Class H has only 16. The purpose of the "X" label is to clarify the intent of NPR 7150.2 and to preclude any alternate interpretation of invoked requirements.

3. Guidance

This requirement affirms that designated Center and project personnel are to satisfy all invoked requirements of this NPR. The note further affirms that at least the safety aspects of an NPR requirement are to be satisfied if the requirement is simply labeled in NPR 7150.2, Appendix D, as "safety only" (SO).

This requirement makes a positive statement that the invoked requirement is to be fulfilled by the SWE's responsible party (indicated by the 4th column in the same Appendix D, Requirements Mapping Matrix).

Deviations, waivers, and tailoring of the requirements of NPR 7150.2 are to follow the approved processes for requirements management. (See [SWE-120] and [SWE-140].)

4. Small Projects

No additional guidance is available for small projects. The community of practice is encouraged to submit guidance candidates for this paragraph.

5. Resources

• (SWEREF-034)

  NASA Complex Electronics Handbook for Assurance Professionals,
  NASA-HDBK 8739.23A, Approved: 02-02-2016, Superseding: NASA-HDBK-8739.23 With Change 1,

• (SWEREF-278)

  SOFTWARE ASSURANCE AND SOFTWARE SAFETY STANDARD
  NASA-STD-8739.8B , NASA TECHNICAL STANDARD, Approved 2022-09-08 Superseding "NASA-STD-8739.8A,

• (SWEREF-283)

  NPR 7150.2B Appendix C. Requirements Mapping Matrix
  NPR 7150.2C, Effective Date: August 02, 2019, Expiration Date: August 02, 2024

• (SWEREF-403)

  Security of Information and Information Systems
  NPR 2810.1F, Office of the Chief Information Officer, Effective Date: January 03, 2022, Expiration Date: January 03, 2027,

• (SWEREF-686)

  Programmable Logic Devices (PLD) Handbook
  NASA-HDBK-4008, Revision: Baseline w/CHANGE 1, Document Date: 2013-12-02

5.1 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

There are currently no Lessons Learned identified for this requirement.