bannerb

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

7.16 - Appendix C. Requirements Mapping and Compliance Matrix

1. Requirements Mapping and Compliance Matrix

The following text is slightly modified from NPR 7150.2B, NASA Software Engineering Requirements, Appendix C.

Rationale

The rationale for the requirements is contained in this Handbook (NASA Software Engineering Handbook, NASA-HDB-2203). Programs/Projects may substitute a matrix that documents their compliance with their particular Center's implementation of NPR 7150.2 039, if applicable. This topic contains a compliance matrix for the requirements organized by class and including a tailoring field for each requirement, tailoring rationale, and approval signature lines.

The Compliance Matrix documents the program/project's compliance or intent to comply with the requirements of NPR 7150.2 039 or justification for tailoring. The matrix lists:

a. The unique requirement identifier.

b. The section reference.

c. The NPR 7150.2 039 requirement statement.

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

Class

     A      

     B      

     C      

   CSC   

     D      

   DSC   

     E      

     F      

     G      

     H      

Applicable?

   

   

   

   

   

   

   

   

   

   

Key:    - Applicable | - Not Applicable
A & B = Always Safety Critical; C & D = Not Safety Critical; CSC & DSC = Safety Critical; E - H = Never Safety Critical.

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 048. For Class B software, in lieu of a CMMI rating by a development organization, the project will conduct an evaluation, performed by a qualified evaluator selected by the Center Engineering Technical Authority, of the seven process areas listed in SWE-032 and mitigate any risk, if deficient. This exception is intended to be used in those cases in which NASA wishes to purchase a product from the "best of class provider," but the best of class provider does not have the required CMMI rating. When this exception is exercised, the Center Engineering Technical Authority should be notified.

Note 3 - For tailoring of NASA-STD-8739.8 278 and NASA-STD-8719.13 271, the Software Assurance Standard and the Software Safety Standard respectively, 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 443, please click the link below.

Compliance Matrix for Each Class

2. References

2.1 Tools

Tools relative to this Topic 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 Topic. If you wish to suggest a tool, please leave a comment below.

  • No labels