7.16 - Appendix C. Requirements Mapping and Compliance Matrix - DEMO with Class Tabs
Web Resources
View this section on the website
See edit history of this section
Post feedback on this section
Unknown macro: {page-info}
- 1. Requirements Mapping and Compliance Matrix
- 2. Class A
- 3. Class B
- 4. Class C
- 5, Class D
- 6. Class E
- 7. Class F
- 8. Resources
1. Requirements Mapping and Compliance Matrix
The following text is slightly modified from NPR 7150.2D, NASA Software Engineering Requirements, Appendix C.
1.1 The Software Classification Spreadsheet
To download the Software Classification Spreadsheet PAT-028, please click the image below. The spreadsheet contains the full matrix from NPR7150.2D as well as a customized matrix for each of the classes, A through F.
Click on the image to preview the file. From the preview, click on Download to obtain a usable copy.
PAT-028 - NPR 7150.2D Compliance Matrix
Tabs include Class A through Class F Matrixes
1.2 Rationale
The rationale for the requirements is contained in the NASA-HDBK-2203. Programs/Projects may substitute a matrix that documents their mapping with their particular Center's implementation of NPR 7150.2 083, if applicable. See NASA-HDBK-2203 for requirements mapping matrices organized by class, tailoring field for each requirement, tailoring rationale, and approval signature lines.
The Compliance Matrix documents the program/project's mappings or intent to comply with the requirements of this NPR or justification for tailoring. The matrix lists:
- The section reference.
- The unique requirement identifier.
- The NPR 7150.2 requirement statement.
- The Authority Level responsible for assessing a project’s requirements mapping matrices and any requested tailoring from requirements in this NPR. The CIO, or the designee, has institutional authority on all Class F software projects and has joint responsibility on the cybersecurity requirements in section 3.11.
- The applicability of the requirements in this NPR 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.
1.3 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.
Center - Center Director or the Center Director's designated Engineering Technical Authority or Center Director's designated Safety and Mission Assurance Technical Authority.
CIO - The OCIO, or the designee Center CIO, has institutional authority on all Class F software projects and has joint responsibility on the cybersecurity requirements in section 3.11 per the direction in the Requirements Mapping Matrix.
Each requirement marked 'X' for the project's software classification(s) should be addressed in the Requirements Mapping Matrix. All requirements can be tailored per the guidance in this directive. Requirements that are not applicable to a given project, such as the IV&V requirements, should be tailored out in the Requirements Mapping Matrix with justification.
1.4 Applicability Across Classes
Each requirement in this Handbook also includes a graphical representation of its compliance matrix data:
Class A B C D E F Applicable?
Key: - Applicable | 
- Not Applicable
NPR 7150.2D Requirements Mapping to SW Class A Matrix
| Section | SWE # | Requirements Text | Technical Authority |
| 3.0 | Software Management Requirements | ||
| 3.1 | Software Life Cycle Planning | ||
| 3.1.2 | 33 | The project manager shall assess options for software acquisition versus development. | Center |
| 3.1.3 | 13 | The project manager shall develop, maintain, and execute software plans, including security plans, that cover the entire software life cycle and, as a minimum, address the requirements of this directive with approved tailoring. | Center |
| 3.1.4 | 24 | The project manager shall track the actual results and performance of software activities against the software plans. | Center |
| a. Corrective actions are taken, recorded, and managed to closure. | |||
| b. Changes to commitments (e.g., software plans) that have been agreed to by the affected groups and individuals are taken, recorded, and managed. | |||
| 3.1.5 | 34 | The project manager shall define and document the acceptance criteria for the software. | Center |
| 3.1.6 | 36 | The project manager shall establish and maintain the software processes, software documentation plans, list of developed electronic products, deliverables, and list of tasks for the software development that are required for the project’s software developers, as well as the action required (e.g., approval, review) of the Government upon receipt of each of the deliverables. | Center |
| 3.1.7 | 37 | The project manager shall define and document the milestones at which the software developer(s) progress will be reviewed and audited. | Center |
| 3.1.8 | 39 | The project manager shall require the software developer(s) to periodically report status and provide insight into software development and test activities; at a minimum, the software developer(s) will be required to allow the project manager and software assurance personnel to: | Center |
| a. Monitor product integration. | |||
| b. Review the verification activities to ensure adequacy. | |||
| c. Review trades studies and source data. | |||
| d. Audit the software development processes and practices. | |||
| e. Participate in software reviews and technical interchange meetings. | |||
| 3.1.9 | 40 | The project manager shall require the software developer(s) to provide NASA with software products, traceability, software change tracking information and nonconformances in electronic format, including software development and management metrics. | Center |
| 3.1.10 | 42 | The project manager shall require the software developer(s) to provide NASA with electronic access to the source code developed for the project in a modifiable format. | Center |
| 3.1.11 | 139 | The project manager shall comply with the requirements in this NPR that are marked with an “X” in Appendix C consistent with their software classification. | Center |
| 3.1.12 | 121 | Where approved, the project manager shall document and reflect the tailored requirement in the plans or procedures controlling the development, acquisition, and deployment of the affected software. | Center |
| 3.1.13 | 125 | Each project manager with software components shall maintain a requirements mapping matrix or multiple requirements mapping matrices against requirements in this NPR, including those delegated to other parties or accomplished by contract vehicles or Space Act Agreements. | Center |
| 3.1.14 | 27 | The project manager shall satisfy the following conditions when a COTS, GOTS, MOTS, OSS, or reused software component is acquired or used: | Center |
| a. The requirements to be met by the software component are identified. | |||
| b. The software component includes documentation to fulfill its intended purpose (e.g., usage instructions). | |||
| c. Proprietary rights, usage rights, ownership, warranty, licensing rights, transfer rights, and conditions of use (e.g., required copyright, author, and applicable license notices within the software code, or a requirement to redistribute the licensed software only under the same license (e.g., GNU GPL, ver. 3, license)) have been addressed and coordinated with Center Intellectual Property Counsel. | |||
| d. Future support for the software product is planned and adequate for project needs. | |||
| e. The software component is verified and validated to the same level required to accept a similar developed software component for its intended use. | |||
| f. The project has a plan to perform periodic assessments of vendor reported defects to ensure the defects do not impact the selected software components. | |||
| 3.2 | Software Cost Estimation | ||
| 3.2.1 | 15 | To better estimate the cost of development, the project manager shall establish, document, and maintain: | Center |
| a. Two cost estimate models and associated cost parameters for all Class A and B software projects that have an estimated project cost of $2 million or more. | |||
| b. One software cost estimate model and associated cost parameter(s) for all Class A and Class B software projects that have an estimated project cost of less than $2 million. | |||
| c. One software cost estimate model and associated cost parameter(s) for all Class C and Class D software projects. | |||
| d. One software cost estimate model and associated cost parameter(s) for all Class F software projects. | |||
| 3.2.2 | 151 | The project manager’s software cost estimate(s) shall satisfy the following conditions: | Center |
| a. Covers the entire software life cycle. | |||
| b. Is based on selected project attributes (e.g., programmatic assumptions/constraints, assessment of the size, functionality, complexity, criticality, reuse code, modified code, and risk of the software processes and products). | |||
| c. Is based on the cost implications of the technology to be used and the required maturation of that technology. | |||
| d. Incorporates risk and uncertainty, including end state risk and threat assessments for cybersecurity. | |||
| e. Includes the cost of the required software assurance support. | |||
| f. Includes other direct costs. | |||
| 3.2.3 | 174 | The project manager shall submit software planning parameters, including size and effort estimates, milestones, and characteristics, to the Center measurement repository at the conclusion of major milestones. | Center |
| 3.3 | Software Schedules | ||
| 3.3.1 | 16 | The project manager shall document and maintain a software schedule that satisfies the following conditions: | Center |
| a. Coordinates with the overall project schedule. | |||
| b. Documents the interactions of milestones and deliverables between software, hardware, operations, and the rest of the system. | |||
| c. Reflects the critical dependencies for software development activities. | |||
| d. Identifies and accounts for dependencies with other projects and cross-program dependencies. | |||
| 3.3.2 | 18 | The project manager shall regularly hold reviews of software schedule activities, status, performance metrics, and assessment/analysis results with the project stakeholders and track issues to resolution. | Center |
| 3.3.3 | 46 | The project manager shall require the software developer(s) to provide a software schedule for the project’s review and schedule updates as requested. | Center |
| 3.4 | Software Training | ||
| 3.4.1 | 17 | The project manager shall plan, track, and ensure project specific software training for project personnel. | Center |
| 3.5 | Software Classification Assessments | ||
| 3.5.1 | 20 | The project manager shall classify each system and subsystem containing software in accordance with the highest applicable software classification definitions for Classes A, B, C, D, E, and F software in Appendix D. | Center |
| 3.5.2 | 176 | The project manager shall maintain records of each software classification determination, each software Requirements Mapping Matrix, and the results of each software independent classification assessments for the life of the project. | Center |
| 3.6 | Software Assurance and Software Independent Verification & Validation | ||
| 3.6.1 | 22 | The project manager shall plan and implement software assurance, software safety, and IV&V (if required) per NASA-STD-8739.8, Software Assurance and Software Safety Standard. | Center |
| 3.6.2 | 141 | For projects reaching Key Decision Point A, the program manager shall ensure that software IV&V is performed on the following categories of projects: | HQ OSMA |
| a. Category 1 projects as defined in NPR 7120.5. | |||
| b. Category 2 projects as defined in NPR 7120.5 that have Class A or Class B payload risk classification per NPR 8705.4. | |||
| c. Projects selected explicitly by the NASA Chief, Safety and Mission Assurance to have software IV&V. | |||
| 3.6.3 | 131 | If software IV&V is performed on a project, the project manager shall ensure an IPEP is developed, approved, maintained, and executed in accordance with the IV&V criteria defined in NASA-STD-8739.8. | Center |
| 3.6.4 | 178 | If software IV&V is performed on a project, the project manager shall ensure that IV&V is provided access to development artifacts, products, source code, and data required to perform the IV&V analysis efficiently and effectively. | Center |
| 3.6.5 | 179 | If software IV&V is performed on a project, the project manager shall provide responses to IV&V submitted issues and risks, and track these issues and risks to closure. | Center |
| 3.7 | Safety-critical Software | ||
| 3.7.1 | 205 | The project manager, in conjunction with the SMA organization, shall determine if each software component is considered to be safety-critical per the criteria defined in NASA-STD-8739.8. | Center |
| 3.7.2 | 23 | If a project has safety-critical software, the project manager shall implement the safety-critical software requirements contained in NASA-STD-8739.8. | Center |
| 3.7.3 | 134 | If a project has safety-critical software or mission-critical software, the project manager shall implement the following items in the software: | Center |
| a. The software is initialized, at first start and restarts, to a known safe state. | |||
| b. The software safely transitions between all predefined known states. | |||
| c. Termination performed by software functions is performed to a known safe state. | |||
| d. Operator overrides of software functions require at least two independent actions by an operator. | |||
| e. Software rejects commands received out of sequence when execution of those commands out of sequence can cause a hazard. | |||
| f. The software detects inadvertent memory modification and recovers to a known safe state. | |||
| g. The software performs integrity checks on inputs and outputs to/from the software system. | |||
| h. The software performs prerequisite checks prior to the execution of safety-critical software commands. | |||
| i. No single software event or action is allowed to initiate an identified hazard. | |||
| j. The software responds to an off-nominal condition within the time needed to prevent a hazardous event. | |||
| k. The software provides error handling. | |||
| l. The software can place the system into a safe state. | |||
| 3.7.4 | 219 | If a project has safety-critical software, the project manager shall ensure that there is 100 percent code test coverage using the Modified Condition/Decision Coverage (MC/DC) criterion for all identified safety-critical software components. | Center |
| 3.7.5 | 220 | If a project has safety-critical software, the project manager shall ensure all identified safety-critical software components have a cyclomatic complexity value of 15 or lower. Any exceedance shall be reviewed and waived with rationale by the project manager or technical approval authority. | Center |
| 3.8 | Automatic Generation of Software Source Code | ||
| 3.8.1 | 146 | The project manager shall define the approach to the automatic generation of software source code including: | Center |
| a. Validation and verification of auto-generation tools. | |||
| b. Configuration management of the auto-generation tools and associated data. | |||
| c. Description of the limits and the allowable scope for the use of the auto-generated software. | |||
| d. Verification and validation of auto-generated source code using the same software standards and processes as hand-generated code. | |||
| e. Monitoring the actual use of auto-generated source code compared to the planned use. | |||
| f. Policies and procedures for making manual changes to auto-generated source code. | |||
| g. Configuration management of the input to the auto-generation tool, the output of the auto-generation tool, and modifications made to the output of the auto-generation tools. | |||
| 3.8.2 | 206 | The project manager shall require the software developers and custom software suppliers to provide NASA with electronic access to the models, simulations, and associated data used as inputs for auto-generation of software. | Center |
| 3.9 | Software Development Processes and Practices | ||
| 3.9.2 | 32 | The project manager shall acquire, develop, and maintain software from an organization with a non-expired CMMI®-DEV rating as measured by a CMMI® Institute Certified Lead Appraiser as follows: | HQ OCE and HQ OSMA |
| a. For Class A software: CMMI®-DEV Maturity Level 3 Rating or higher for software. | |||
| b. For Class B software (except Class B software on NASA Class D payloads, as defined in NPR 8705.4): CMMI®-DEV Maturity Level 2 Rating or higher for software. | |||
| 3.10 | Software Reuse | ||
| 3.10.1 | 147 | The project manager shall specify reusability requirements that apply to its software development activities to enable future reuse of the software, including the models, simulations, and associated data used as inputs for auto-generation of software, for U.S. Government purposes. | Center |
| 3.10.2 | 148 | The project manager shall evaluate software for potential reuse by other projects across NASA and contribute reuse candidates to the appropriate NASA internal sharing and reuse software system. However, if the project manager is not a civil servant, then a civil servant will pre-approve all such software contributions; all software contributions should include, at a minimum, the following information: | Center |
| a. Software Title. | |||
| b. Software Description. | |||
| c. The Civil Servant Software Technical POC for the software product. | |||
| d. The language or languages used to develop the software. | |||
| e. Any third party code contained therein and the record of the requisite license or permission received from the third party permitting the Government’s use and any required markings (e.g., required copyright, author, applicable license notices within the software code, and the source of each third-party software component (e.g., software URL & license URL)), if applicable. | |||
| f. Release notes. | |||
| 3.11 | Software Cybersecurity | ||
| 3.11.2 | 156 | The project manager shall perform a software cybersecurity assessment on the software components per the Agency security policies and the project requirements, including risks posed by the use of COTS, GOTS, MOTS, OSS, or reused software components. | Center and Center CIO |
| 3.11.3 | 154 | The project manager shall identify cybersecurity risks, along with their mitigations, in flight and ground software systems and plan the mitigations for these systems. | Center and Center CIO |
| 3.11.4 | 157 | The project manager shall implement protections for software systems with communications capabilities against unauthorized access per the requirements contained in the Space System Protection Standard, NASA-STD-1006. | Center and Center CIO |
| 3.11.5 | 159 | The project manager shall test the software and record test results for the required software cybersecurity mitigation implementations identified from the security vulnerabilities and security weaknesses analysis. | Center and Center CIO |
| 3.11.6 | 207 | The project manager shall identify, record, and implement secure coding practices. | Center and Center CIO |
| 3.11.7 | 185 | The project manager shall verify that the software code meets the project’s secure coding standard by using the results from static analysis tool(s). | Center and Center CIO |
| 3.11.8 | 210 | The project manager shall identify software requirements for the collection, reporting, and storage of data relating to the detection of adversarial actions. | Center |
| 3.12 | Software Bi-Directional Traceability | ||
| 3.12.1 | 52 | The project manager shall perform, record, and maintain bi-directional traceability between the following software elements: (See Table in 3.12.1) | Center |
| 4.0 | Software Engineering (Life Cycle) Requirements | ||
| 4.1 | Software Requirements | ||
| 4.1.2 | 50 | The project manager shall establish, capture, record, approve, and maintain software requirements, including requirements for COTS, GOTS, MOTS, OSS, or reused software components, as part of the technical specification. | Center |
| 4.1.3 | 51 | The project manager shall perform software requirements analysis based on flowed-down and derived requirements from the top-level systems engineering requirements, safety and reliability analyses, and the hardware specifications and design. | Center |
| 4.1.4 | 184 | The project manager shall include software related safety constraints, controls, mitigations and assumptions between the hardware, operator, and software in the software requirements documentation. | Center |
| 4.1.5 | 53 | The project manager shall track and manage changes to the software requirements. | Center |
| 4.1.6 | 54 | The project manager shall identify, initiate corrective actions, and track until closure inconsistencies among requirements, project plans, and software products. | Center |
| 4.1.7 | 55 | The project manager shall perform requirements validation to ensure that the software will perform as intended in the customer environment. | Center |
| 4.2 | Software Architecture | ||
| 4.2.3 | 57 | The project manager shall transform the requirements for the software into a recorded software architecture. | Center |
| 4.2.4 | 143 | The project manager shall perform a software architecture review on the following categories of projects: | Center |
| a. Category 1 Projects as defined in NPR 7120.5. | |||
| b. Category 2 Projects as defined in NPR 7120.5 that have Class A or Class B payload risk classification per NPR 8705.4. | |||
| 4.3 | Software Design | ||
| 4.3.2 | 58 | The project manager shall develop, record, and maintain a software design based on the software architectural design that describes the lower-level units so that they can be coded, compiled, and tested. | Center |
| 4.4 | Software Implementation | ||
| 4.4.2 | 60 | The project manager shall implement the software design into software code. | Center |
| 4.4.3 | 61 | The project manager shall select, define, and adhere to software coding methods, standards, and criteria. | Center |
| 4.4.4 | 135 | The project manager shall use static analysis tools to analyze the code during the development and testing phases to, at a minimum, detect defects, software security, code coverage, and software complexity. | Center |
| 4.4.5 | 62 | The project manager shall unit test the software code. | Center |
| 4.4.6 | 186 | The project manager shall assure that the unit test results are repeatable. | Center |
| 4.4.7 | 63 | The project manager shall provide a software version description for each software release. | Center |
| 4.4.8 | 136 | The project manager shall validate and accredit the software tool(s) required to develop or maintain software. | Center |
| 4.5 | Software Testing | ||
| 4.5.2 | 65 | The project manager shall establish and maintain: | Center |
| a. Software test plan(s). | |||
| b. Software test procedure(s). | |||
| c. Software test(s), including any code specifically written to perform test procedures. | |||
| d. Software test report(s). | |||
| 4.5.3 | 66 | The project manager shall test the software against its requirements. | Center |
| 4.5.4 | 187 | The project manager shall place software items under configuration management prior to testing. | Center |
| 4.5.5 | 68 | The project manager shall evaluate test results and record the evaluation. | Center |
| 4.5.6 | 70 | The project manager shall use validated and accredited software models, simulations, and analysis tools required to perform qualification of flight software or flight equipment. | Center |
| 4.5.7 | 71 | The project manager shall update the software test and verification plan(s) and procedure(s) to be consistent with software requirements. | Center |
| 4.5.8 | 73 | The project manager shall validate the software system on the targeted platform or high-fidelity simulation. | Center |
| 4.5.9 | 189 | The project manager shall ensure that the code coverage measurements for the software are selected, implemented, tracked, recorded, and reported. | Center |
| 4.5.10 | 190 | The project manager shall verify code coverage is measured by analysis of the results of the execution of tests. | Center |
| 4.5.11 | 191 | The project manager shall plan and conduct software regression testing to demonstrate that defects have not been introduced into previously integrated or tested software and have not produced a security vulnerability. | Center |
| 4.5.12 | 192 | The project manager shall verify through test the software requirements that trace to a hazardous event, cause, or mitigation technique. | Center |
| 4.5.13 | 193 | The project manager shall develop acceptance tests for loaded or uplinked data, rules, and code that affects software and software system behavior. | Center |
| 4.5.14 | 211 | The project manager shall test embedded COTS, GOTS, MOTS, OSS, or reused software components to the same level required to accept a custom developed software component for its intended use. | Center |
| 4.6 | Software Operations, Maintenance, and Retirement | ||
| 4.6.2 | 75 | The project manager shall plan and implement software operations, maintenance, and retirement activities. | Center |
| 4.6.3 | 77 | The project manager shall complete and deliver the software product to the customer with appropriate records, including as-built records, to support the operations and maintenance phase of the software’s life cycle. | Center |
| 4.6.4 | 194 | The project manager shall complete, prior to delivery, verification that all software requirements identified for this delivery have been met or dispositioned, that all approved changes have been implemented and that all defects designated for resolution prior to delivery have been resolved. | Center |
| 4.6.5 | 195 | The project manager shall maintain the software using standards and processes per the applicable software classification throughout the maintenance phase. | Center |
| 4.6.6 | 196 | The project manager shall identify the records and software tools to be archived, the location of the archive, and procedures for access to the products for software retirement or disposal. | Center |
| 5.0 | Supporting Software Life Cycle Requirements | ||
| 5.1 | Software Configuration Management | ||
| 5.1.2 | 79 | The project manager shall develop a software configuration management plan that describes the functions, responsibilities, and authority for the implementation of software configuration management for the project. | Center |
| 5.1.3 | 80 | The project manager shall track and evaluate changes to software products. | Center |
| 5.1.4 | 81 | The project manager shall identify the software configuration items (e.g., software records, code, data, tools, models, scripts) and their versions to be controlled for the project. | Center |
| 5.1.5 | 82 | The project manager shall establish and implement procedures to: | Center |
| a. Designate the levels of control through which each identified software configuration item is required to pass. | |||
| b. Identify the persons or groups with authority to authorize changes. | |||
| c. Identify the persons or groups to make changes at each level. | |||
| 5.1.6 | 83 | The project manager shall prepare and maintain records of the configuration status of software configuration items. | Center |
| 5.1.7 | 84 | The project manager shall perform software configuration audits to determine the correct version of the software configuration items and verify that they conform to the records that define them. | Center |
| 5.1.8 | 85 | The project manager shall establish and implement procedures for the storage, handling, delivery, release, and maintenance of deliverable software products. | Center |
| 5.1.9 | 45 | The project manager shall participate in any joint NASA/developer audits. | Center |
| 5.2 | Software Risk Management | ||
| 5.2 | 86 | The project manager shall record, analyze, plan, track, control, and communicate all of the software risks and mitigation plans. | Center |
| 5.3 | Software Peer Reviews/Inspections | ||
| 5.3.2 | 87 | The project manager shall perform and report the results of software peer reviews or software inspections for: | Center |
| a. Software requirements. | |||
| b. Software plans, including cybersecurity. | |||
| c. Any design items that the project identified for software peer review or software inspections according to the software development plans. | |||
| d. Software code as defined in the software and or project plans. | |||
| e. Software test procedures. | |||
| 5.3.3 | 88 | The project manager shall, for each planned software peer review or software inspection: | Center |
| a. Use a checklist or formal reading technique (e.g., perspective based reading) to evaluate the work products. | |||
| b. Use established readiness and completion criteria. | |||
| c. Track actions identified in the reviews until they are resolved. | |||
| d. Identify the required participants. | |||
| 5.3.4 | 89 | The project manager shall, for each planned software peer review or software inspection, record necessary measurements. | Center |
| 5.4 | Software Measurements | ||
| 5.4.2 | 90 | The project manager shall establish, record, maintain, report, and utilize software management and technical measurements. | Center |
| 5.4.3 | 93 | The project manager shall analyze software measurement data collected using documented project-specified and Center/organizational analysis procedures. | Center |
| 5.4.4 | 94 | The project manager shall provide access to the software measurement data, measurement analyses, and software development status as requested to the sponsoring Mission Directorate, the NASA Chief Engineer, the Center TAs, HQ SMA, and other organizations as appropriate. | Center |
| 5.4.5 | 199 | The project manager shall monitor measures to ensure the software will meet or exceed performance and functionality requirements, including satisfying constraints. | Center |
| 5.4.6 | 200 | The project manager shall collect, track, and report software requirements volatility metrics. | Center |
| 5.5 | Software Non-conformance or Defect Management | ||
| 5.5.1 | 201 | The project manager shall track and maintain software non-conformances (including defects in tools and appropriate ground software). | Center |
| 5.5.2 | 202 | The project manager shall define and implement clear software severity levels for all software non-conformances (including tools, COTS, GOTS, MOTS, OSS, reused software components, and applicable ground systems). | Center |
| 5.5.3 | 203 | The project manager shall implement mandatory assessments of reported non-conformances for all COTS, GOTS, MOTS, OSS, and/or reused software components. | Center |
| 5.5.4 | 204 | The project manager shall implement process assessments for all high severity software non-conformances (closed loop process). | Center |
8. Resources
8.1 References
[Click here to view master references table.]
- (SWEREF-083) NPR 7150.2D, Effective Date: March 08, 2022, Expiration Date: March 08, 2027 https://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPR&c=7150&s=2D Contains link to full text copy in PDF format. Search for "SWEREF-083" for links to old NPR7150.2 copies.
- (SWEREF-257) NPD 7120.4E, NASA Office of the Chief Engineer, Effective Date: June 26, 2017, Expiration Date: June 26, 2022
- (SWEREF-284) This topic contains spreadsheets for each class of software. For older versions of SWEHB, see SWE-125 and Topic 7.16 in the appropriate version.
8.2 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.
2.3 Process Asset Templates
Click on a link to download a usable copy of the template.
(PAT-028 - )
NPR 7150.2D Appendix C,
