bannerc

A. Introduction

B. Institutional Requirements

C. Project Software Requirements

D. Topics

E. Tools, References, and Terms

F. SPAN
(NASA Only)

List below includes all active SWE Pages in SWE  number order along with the paragraph number from NPR 7150.2C, and the actual requirement text. 

  • SWE-002 - Software Engineering Initiative — 2.1.1.1 The NASA OCE shall lead and maintain a NASA Software Engineering Initiative to advance software engineering practices. 
  • SWE-003 - Center Improvement Plans — 2.1.5.2 Center Director, or designee, shall maintain, staff, and implement a plan to continually advance the Center’s in-house software engineering capability and monitor the software engineering capability of NASA's contractors.
  • SWE-004 - OCE Benchmarking — 2.1.1.2 The NASA OCE shall periodically benchmark each Center's software engineering capability against requirements in this directive. 
  • SWE-005 - Software Processes — 2.1.5.3 Center Director, or designee, shall establish, document, execute and maintain software processes per the requirements in this directive. 
  • SWE-006 - Center Software Inventory — 2.1.5.8 Center Director, or designee, shall maintain a reliable list of their Center’s programs and projects containing Class A, B, C, and D software. The list should include:
  • SWE-013 - Software Plans — 3.1.3 The project manager shall develop, maintain, and execute software plans that cover the entire software life cycle and, as a minimum, address the requirements of this directive with approved tailoring.
  • SWE-015 - Cost Estimation — 3.2.1 To better estimate the cost of development, the project manager shall establish, document, and maintain:
  • SWE-016 - Software Schedule — 3.3.1 The project manager shall document and maintain a software schedule that satisfies the following conditions:
  • SWE-017 - Project and Software Training — 3.4.1 The project manager shall plan, track, and ensure project specific software training for project personnel.
  • SWE-018 - Software Activities Review — 3.3.2 The project manager shall regularly hold reviews of software schedule activities, metrics, status, and results with the project stakeholders and track issues to resolution. 
  • SWE-020 - Software Classification — 3.5.1 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. 
  • SWE-021 - Transition to a Higher Class — 2.2.8 If a system or subsystem development evolves to meet a higher or lower software classification as defined in Appendix D then the project manager shall update their plan to fulfill the applicable requirements per the Requirements Mapping Matrix in Appendix C and any approved changes, and initiate adjustments to applicable supplier contracts to fulfill the modified requirements.
  • SWE-022 - Software Assurance — 3.6.1 The project manager shall plan and implement software assurance per NASA-STD-8739.8. 
  • SWE-023 - Software Safety-Critical Requirements — 3.7.2 If a project has safety-critical software, the project manager shall implement the safety-critical software requirements contained in NASA-STD-8739.8.
  • SWE-024 - Plan Tracking — 3.1.4 The project manager shall track the actual results and performance of software activities against the software plans.
  • SWE-027 - Use of Commercial, Government, and Legacy Software — 3.1.14 The project manager shall satisfy the following conditions when a Commercial Off the Shelf (COTS), Government Off the Shelf (GOTS), Modified Off the Shelf (MOTS), Open Source Software (OSS), or reused software component is acquired or used:
  • SWE-032 - CMMI Levels for Class A and B Software — 3.9.3 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:
  • SWE-033 - Acquisition vs. Development Assessment — 3.1.2 The project manager shall assess options for software acquisition versus development.
  • SWE-034 - Acceptance Criteria — 3.1.5 The project manager shall define and document the acceptance criteria for the software. 
  • SWE-036 - Software Process Determination — 3.1.6 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.
  • SWE-037 - Software Milestones — 3.1.7 The project manager shall define and document the milestones at which the software developer(s) progress will be reviewed and audited. 
  • SWE-039 - Software Supplier Insight — 3.1.8 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:
  • SWE-040 - Access to Software Products — 3.1.9 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.
  • SWE-042 - Source Code Electronic Access — 3.1.10 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. 
  • SWE-045 - Project Participation in Audits — 5.1.9 The project manager shall participate in any joint NASA/developer audits. 
  • SWE-046 - Supplier Software Schedule — 3.3.3 The project manager shall require the software developer(s) to provide a software schedule for the project's review, and schedule updates as requested.
  • SWE-050 - Software Requirements — 4.1.2 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. 
  • SWE-051 - Software Requirements Analysis — 4.1.3 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. 
  • SWE-052 - Bidirectional Traceability — 3.12.1 The project manager shall perform, record, and maintain bi-directional traceability between the following software elements: 
  • SWE-053 - Manage Requirements Changes — 4.1.5 The project manager shall track and manage changes to the software requirements. 
  • SWE-054 - Corrective Action for Inconsistencies — 4.1.6 The project manager shall identify, initiate corrective actions, and track until closure inconsistencies among requirements, project plans, and software products. 
  • SWE-055 - Requirements Validation — 4.1.7 The project manager shall perform requirements validation to ensure that the software will perform as intended in the customer environment. 
  • SWE-057 - Software Architecture — 4.2.3 The project manager shall transform the requirements for the software into a recorded software architecture.
  • SWE-058 - Detailed Design — 4.3.2 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.
  • SWE-060 - Coding Software — 4.4.2 The project manager shall implement the software design into software code.
  • SWE-061 - Coding Standards — 4.4.3 The project manager shall select and adhere to software coding methods, standards, and criteria.
  • SWE-062 - Unit Test — 4.4.5 The project manager shall unit test the software code.
  • SWE-063 - Release Version Description — 4.4.7 The project manager shall provide a software version description for each software release. 
  • SWE-065 - Test Plan, Procedures, Reports — 4.5.2 The project manager shall establish and maintain:
  • SWE-066 - Perform Testing — 4.5.3 The project manager shall test the software against its requirements.
  • SWE-068 - Evaluate Test Results — 4.5.5 The project manager shall evaluate test results and record the evaluation.
  • SWE-070 - Models, Simulations, Tools — 4.5.6 The project manager shall use validated and accredited software models, simulations, and analysis tools required to perform qualification of flight software or flight equipment.
  • SWE-071 - Update Test Plans and Procedures — 4.5.7 The project manager shall update the software test plan(s) and the software test procedure(s) to be consistent with software requirements.
  • SWE-073 - Platform or Hi-Fidelity Simulations — 4.5.8 The project manager shall validate the software system on the targeted platform or high-fidelity simulation
  • SWE-075 - Plan Operations, Maintenance, Retirement — 4.6.2 The project manager shall plan and implement software operations, maintenance, and retirement activities.
  • SWE-077 - Deliver Software Products — 4.6.3 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. 
  • SWE-079 - Develop CM Plan — 5.1.2 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. 
  • SWE-080 - Track and Evaluate Changes — 5.1.3 The project manager shall track and evaluate changes to software products. 
  • SWE-081 - Identify Software CM Items — 5.1.4 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.
  • SWE-082 - Authorizing Changes — 5.1.5 The project manager shall establish and implement procedures to:
  • SWE-083 - Status Accounting — 5.1.6 The project manager shall prepare and maintain records of the configuration status of software configuration items. 
  • SWE-084 - Configuration Audits — 5.1.7 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.
  • SWE-085 - Release Management — 5.1.8 The project manager shall establish and implement procedures for the storage, handling, delivery, release, and maintenance of deliverable software products.  
  • SWE-086 - Continuous Risk Management — 5.2.1 The project manager shall record, analyze, plan, track, control, and communicate all of the software risks and mitigation plans. 
  • SWE-087 - Software Peer Reviews and Inspections for Requirements, Plans, Design, Code, and Test Procedures — 5.3.2 The project manager shall perform and report the results of software peer reviews or software inspections for:
  • SWE-088 - Software Peer Reviews and Inspections - Checklist Criteria and Tracking — 5.3.3 The project manager shall, for each planned software peer review or software inspection:
  • SWE-089 - Software Peer Reviews and Inspections - Basic Measurements — 5.3.4 The project manager shall, for each planned software peer review or software inspection, record necessary measurements. 
  • SWE-090 - Management and Technical Measurements — 5.4.2 The project manager shall establish, record, maintain, report, and utilize software management and technical measurements
  • SWE-091 - Establish and Maintain Measurement Repository — 2.1.5.9 For Class A, B, and C software projects, the Center Director, or designee, shall establish and maintain a software measurement repository for software project measurements containing at a minimum:
  • SWE-092 - Using Measurement Data — 2.1.5.10 For Class A, B, and C software projects, the Center Director, or designee, shall utilize software measurement data for monitoring software engineering capability, improving software quality, and to track the status of software engineering improvement activities.  
  • SWE-093 - Analysis of Measurement Data — 5.4.3 The project manager shall analyze software measurement data collected using documented project-specified and Center/organizational analysis procedures. 
  • SWE-094 - Reporting of Measurement Analysis — 5.4.4 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 Technical Authorities, and Headquarters SMA. 
  • SWE-095 - Report Engineering Discipline Status — 2.1.5.7 The Center Director, or designee, shall report on the status of the Center’s software engineering discipline, as applied to its projects, upon request by the OCE or OSMA. 
  • SWE-098 - Agency PAL — 2.1.1.6 The NASA OCE shall maintain an Agency-wide process asset library of applicable best practices.  
  • SWE-100 - Software Training Funding — 2.1.1.5 The NASA OCE and Center training organizations shall provide training to advance software engineering practices.  
  • SWE-101 - Center SW Training Plans — 2.1.5.11 Center Director, or designee, will maintain and implement software training to advance its in-house software engineering capabilities.  
  • SWE-121 - Document Tailored Requirements — 3.1.12 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.
  • SWE-122 - Technical Authority Appointment — 2.1.5.5 The designated Center Engineering Technical Authority(s) or Institutional Authority(s) for requirements in this NPR shall be NASA civil servants (or JPL/Contractor employees).
  • SWE-125 - Requirements Compliance Matrix — 3.1.13 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. 
  • SWE-126 - Tailoring Considerations — 2.1.5.6 Serving as technical and institutional authorities for requirements in this directive, Center Director, or designee, shall:  
  • SWE-129 - OCE NPR Appraisals — 2.1.1.4 The NASA OCE shall authorize appraisals against selected requirements in this NPR to check compliance. 
  • SWE-131 - Independent Verification and Validation Project Execution Plan — 3.6.3 If software IV&V is performed on a project, the project manager shall ensure an IPEP is developed, negotiated, approved, maintained, and executed. 
  • SWE-134 - Safety Critical Software Design Requirements — 3.7.3 If a project has safety-critical software or mission-critical software, the project manager shall implement the following items in the software:
  • SWE-135 - Static Analysis — 4.4.4 The project manager shall use static analysis tools to analyze the code during the development and testing phases to detect defects, software security, and coding errors.
  • SWE-136 - Software Tool Accreditation — 4.4.8 The project manager shall validate and accredit the software tool(s) required to develop or maintain software.
  • SWE-139 - Shall Statements — 3.1.11 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.
  • SWE-140 - Comply with Requirements — 2.1.5.4 Center Director, or designee, shall comply with the requirements in this directive that are marked with an ”X” in Appendix C.
  • SWE-141 - Software Independent Verification and Validation — 3.6.2 For projects reaching Key Decision Point A the program manager shall ensure that software IV&V is performed on the following categories of projects:
  • SWE-142 - Software Cost Repositories — 2.1.5.12 For Class A, B, and C software projects, each Center Director, or designee, shall establish and maintain software cost repository(ies) that contains at least the following measures:
  • SWE-143 - Software Architecture Review — 4.2.4 The project manager shall perform a software architecture review on the following categories of projects:
  • SWE-144 - Software Engineering Process Assets — 2.1.5.13 Each Center Director, or designee, shall contribute applicable software engineering process assets in use at his/her Centers to the Agency-wide process asset library. 
  • SWE-146 - Auto-generated Source Code — 3.8.1 The project manager shall define the approach to the automatic generation of software source code including:
  • SWE-147 - Specify Reusability Requirements — 3.10.1 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 United States Government purposes. 
  • SWE-148 - Contribute to Agency Software Catalog — 3.10.2 The project manager shall evaluate software for potential reuse by other projects across NASA and contribute reuse candidates to the NASA Internal Sharing and Reuse Software systems. However, if the project manager is a contractor, then a civil servant must pre-approve all such software contributions; all software contributions should include, at a minimum, the following information:
  • SWE-150 - Review Changes To Tailored Requirements — 2.2.7 The engineering, CIO and SMA authorities shall review and agree with any tailored NPR 7150.2 requirements per the requirements mapping matrix authority column. 
  • SWE-151 - Cost Estimate Conditions — 3..2.2 The project manager’s software cost estimate(s) shall satisfy the following conditions:
  • SWE-152 - Review Requirements Mapping Matrices — 2.1.1.3 The NASA OCE shall periodically review the project requirements mapping matrices. 
  • SWE-153 - ETA Define Document Content — 2.1.5.14 The designated Engineering Technical Authority(s) shall define the content requirements for software documents or records.
  • SWE-154 - Identify Security Risks — 3.11.3 The project manager shall identify cybersecurity risks, along with their mitigations, in flight and ground software systems and plan the mitigations for these systems. 
  • SWE-155 - Implement Risk Mitigations — 3.11.6 The project manager shall address identified cybersecurity vulnerabilities and weaknesses.
  • SWE-156 - Evaluate Systems for Security Risks — 3.11.2 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.
  • SWE-157 - Protect Against Unauthorized Access — 3.11.4 The project manager shall implement protections for software systems with communications capabilities against unauthorized access. 
  • SWE-158 - Evaluate Software for Security Vulnerabilities — 3.11.5 The project manager shall ensure that space flight software systems are assessed for possible cybersecurity vulnerabilities and weaknesses.
  • SWE-159 - Verify and Validate Risk Mitigations — 3.11.7 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. 
  • SWE-174 - Software Planning Parameters — 3.2.3 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. 
  • SWE-176 - Software Records — 3.5.2 The project manager shall maintain records of each software classification determination, each software Requirements Mapping Matrix, and the results of each software independent classification assessment for the life of the project. 
  • SWE-178 - IV&V Artifacts — 3.6.4 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. 
  • SWE-179 - IV&V Submitted Issues and Risks — 3.6.5 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. 
  • SWE-184 - Software-related Constraints and Assumptions — 4.1.4 The project manager shall include software related safety constraints, controls, mitigations and assumptions between the hardware, operator, and software in the software requirements documentation. 
  • SWE-185 - Secure Coding Standards Verification — 3.11.9 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). 
  • SWE-186 - Unit Test Repeatability — 4.4.6 The project manager shall assure that the unit test results are repeatable. 
  • SWE-187 -Control of Software Items — 4.5.4 The project manager shall place software items under configuration management prior to testing. 
  • SWE-189 - Code Coverage Measurements — 4.5.9 The project manager shall ensure that the code coverage measurements for the software are selected, implemented, tracked, recorded, and reported.
  • SWE-190 - Verify Code Coverage — 4.5.10 The project manager shall verify code coverage is measured by analysis of the results of the execution of tests.
  • SWE-191 - Software Regression Testing — 4.5.11 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.
  • SWE-192 - Software Hazardous Requirements — 4.5.12 The project manager shall verify through test the software requirements that trace to a hazardous event, cause, or mitigation technique.
  • SWE-193 - Acceptance Testing for Affected System and Software Behavior — 4.5.13 The project manager shall develop acceptance tests for loaded or uplinked data, rules, and code that affects software and software system behavior. 
  • SWE-194 - Delivery Requirements Verification — 4.6.4 The project manager shall complete, prior to delivery, verification that all software requirements identified for this delivery have been met, that all approved changes have been implemented, and that all defects designated for resolution prior to delivery have been resolved. 
  • SWE-195 - Software Maintenance Phase — 4.6.5 The project manager shall maintain the software using standards and processes per the applicable software classification throughout the maintenance phase. 
  • SWE-196 - Software Retirement Archival — 4.6.6 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.
  • SWE-199 - Performance Measures — 5.4.5 The project manager shall monitor measures to ensure the software will meet or exceed performance and functionality requirements, including satisfying constraints.
  • SWE-200 - Software Requirements Volatility Metrics — 5.4.6 The project manager shall collect, track, and report software requirements volatility metrics. 
  • SWE-201 - Software Non-Conformances — 5.5.1 The project manager shall track and maintain software non-conformances (including defects in tools and appropriate ground software).  
  • SWE-202 - Software Severity Levels — 5.5.2 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). 
  • SWE-203 - Mandatory Assessments for Non-Conformances — 5.5.3 The project manager shall implement mandatory assessments of reported non-conformances for all COTS, GOTS, MOTS, OSS, or reused software components. 
  • SWE-204 - Process Assessments — 5.5.4 The project manager shall implement process assessments for all high-severity software non-conformances (closed loop process). 
  • SWE-205 - Determination of Safety-Critical Software — 3.7.1 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. 
  • SWE-206 - Auto-Generation Software Inputs — 3.8.2 The project manager shall require the software developers and suppliers to provide NASA with electronic access to the models, simulations, and associated data used as inputs for auto-generation of software. 
  • SWE-207 - Secure Coding Practices — 3.11.8 The project manager shall identify, record, and implement secure coding practices.
  • SWE-211 - Test Levels of Non-Custom Developed Software — 4.5.14 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. 
  • SWE-214 - Internal Software Sharing and Reuse — 2.1.5.18 The Center Director or designee (e.g., the Civil Servant Technical Point of Contact for the software product) shall perform the following actions for each type of internal NASA software transfer or reuse:  
  • SWE-215 - Software License Rights — 2.1.5.15 The Center Director or designee shall ensure that the Government has clear rights in the software, a Government purpose license, or other appropriate license or permission from third party owners prior to providing the software for internal NASA software sharing or reuse.
  • SWE-216 - Internal Software Sharing List — 2.1.5.16 The Center Director or designee shall ensure that all software listed on the internal software sharing or reuse catalog(s) conforms to NASA software engineering policy and requirements. 
  • SWE-217 - List of All Contributors and Disclaimer Notice — 2.1.5.17 The Center Director or designee (e.g., the Civil Servant Technical Point of Contact for the software product) shall perform the following actions:

  • No labels
Page Editor: Tim Crumbley
NASA Official: Tim Crumbley
NASA Software Engineering Handbook - A service of the NASA Office of the Chief Engineer
NASA Privacy Statement
______________________________________________________________________________