2

...

...

1. Requirements Mapping and Compliance Matrix

Rationale

The rationale for the requirements is contained in this Handbook (NASA Software Engineering Handbook, NASA-HDBK-2203). Programs/Projects may substitute a matrix that documents their compliance with their particular Center's implementation of NPR 7150.2

The Compliance Matrix documents the program/project's compliance or intent to comply with the requirements of NPR 7150.2

a. The unique requirement identifier.

b. The section reference.

c. The NPR 7150.2

d. The Technical Authority Level responsible for assessing a project's compliance matrices, tailoring, waivers, and deviations from requirements in NPR 7150.2.

e. The requirement owner (the organization or individual responsible for the requirement).

f. The applicability of the requirements in NPR 7150.2 to specific systems and subsystems within the Agency's investment areas, programs, and projects is determined through the use of the NASA-wide definition of software classes.

Tailoring Guidance

Use the following guidance, also included in the matrix, to interpret the contents of the compliance matrix included in this topic:

X - Indicates an invoked requirement by this NPR consistent with Software Classification (See SWE-139). May be tailored with Technical Authority approval (NPR 7150.2, Chapter 2.2).

Blank - Optional/Not invoked by NPR 7150.2.

X (not OTS) - Does not apply to Off the Shelf (OTS), Commercial Software.

Center Director - Center Director or the Center Director's designated Engineering Technical Authority or Center Director's designated Safety and Mission Assurance Technical Authority.

Each requirement in this Handbook also includes a graphical representation of its compliance matrix data:

Applicability Across Classes

Notes

The compliance matrix contains references to notes, e.g., “(Note 2)” which are included here for reference.  These notes are also included in the compliance matrix itself.

Note 1 - Project is required to meet this requirement to the extent necessary to satisfy safety critical aspects of the software. All Safety-critical software has to be classified as Class D or Higher (See Topic 7.2).

Note 2 - Applies to Class B software except for Class B software on NASA Class D payloads, as defined in NPR 8705.4

Note 3 - For tailoring of NASA-STD-8739.8, the Software Assurance and Software Safety Standard, use the tailoring provided within those documents. They are both risk-based and Software Class based tailoring.

Note 4 - The Technical Authority implementation responsibilities for Class F software is at the NASA Headquarters Chief Information Officer (CIO) level, the Technical Authority implementation responsibilities for Class G and H is at the Center CIO organization level or at the level defined in the Center Technical Authority implementation plan. All Safety-critical software has to be classified as Class D or higher (See Topic 7.2).

The Software Classification Spreadsheet

To download the Software Classification Spreadsheet

Compliance Matrix for Each Class

...

2. Resources

2.1 References

...

...

Enter necessary modifications to be made in the table below:

...

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

SWEREFs called out in text: 039, 048, 271, 278, 443

2.2 Tools

...