NASA Procedures and Guidelines
This Document is Obsolete and Is No Longer Used. Check the NODIS Library to access the current version: http://nodis3.gsfc.nasa.gov
NPR 7150.2A Eff. Date: November 19, 2009 Cancellation Date: August 20, 2020	NASA Software Engineering Requirements
| TOC | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | ALL |

Appendix D. Requirements Mapping Matrix

X - "Required" - Responsible party is required to meet the requirement as written.

X (not OTS) - Project is required to meet except for off-the-shelf software.

P (Center) - Per approved Center defined process which meets a non-empty subset of the full requirement.

SO - "Safety Only" - Project is required to meet this requirement to the extent necessary to satisfy safety critical aspects of the software.

P (Center) + SO - Responsible party is required to meet this requirement to the extent necessary to satisfy safety critical aspects of the software and follow Center defined P (Center) processes for other aspects of the software.

Blank Space - Project is not required to meet the requirement.

Note 1 - 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 2 - Note that there are additional safety requirements in NASA-STD-8719.13, NASA Software Safety Standard.

Note 3 - NASA Headquarters' Chief, Safety and Mission Assurance has co-approval on any waiver or deviation decided at the HQ level that involves safety-critical software. NASA Headquarters' Chief Medical Officer has co-approval on any waiver or deviation decided at the HQ level that involves software with health and medical implications. Waivers and deviations decided at the Center level are to follow similar protocol when software safety critical or health and medical issues are involved.

Note 4 - When software development tools are used to develop or maintain Class A, B, C, or safety-critical software.

Note 5 - When software models, simulations, and analysis tools are used to perform qualification of flight software or flight equipment.

Note 6 - No test plans are required but the project shall perform software testing.

Note 7 - This NPR does not require SWE-134 for Classes C thru E and Safety Critical; however it is highly recommended that software within this category use SWE-134 as a checklist to support the identification of safety related risks and their mitigations.

HQ CE - NASA Headquarters' Chief Engineer

HQ CSMA - NASA Headquarters' Chief, Safety and Mission Assurance

DISTRIBUTION:
NODIS