D. Topics

7.1 - History and Overview of the Software Process Improvement (SPI) Effort - 

7.3 - Acquisition Guidance -

7.5 - Work Breakdown Structures That Include Software -

7.6 - Software Test Estimation and Testing Levels -

7.7 - Software Architecture Description - 

7.9 - Entrance and Exit Criteria - 

7.10 - Peer Review and Inspections Including Checklists - Describes the role of Peer Reviews and Inspections in detecting and evaluating product defects, and tracking solutions integration into the product.

7.11 - SWE History - The SWE History Summary includes all SWE numbers and their history of use in all versions of the Software Engineering Handbook.

7.13 - Transitioning to a Higher Class - Provide guidance for projects that desire to transition software from a lower to a higher classification.

7.14 - Implementing Measurement Requirements and Analysis for Projects - Provides guidance for projects implementing the NPR 7150.2 requirements addressing or including software measurement. 

7.15 - Relationship Between NPR 7150.2 and NASA-STD-7009 - Discusses the relationship of NPR7150.2 to NASA-STD-7009 (Models and Simulation)

7.16 - Appendix C. Requirements Mapping and Compliance Matrix -  Guidance for using the 7150.2 Appendix C Requirements Mapping and Compliance Matrix.

7.17 - 7150.2C Appendices (Definitions, References, etc.) - This content is taken verbatim from NPR 7150.2C, NASA Software Engineering Requirements, Appendix A. 

7.18 - Documentation Guidance - Provide a set of minimum content guidance for software project plans, reports, and procedures. 

7.19 - Software Risk Management Checklists - Software Risk Management is a process whereby the project identifies and tracks threats to the success of the project. 

7.20 - Assessing - Meets the Intent - Guidance for projects that need to assess whether an industry partner or subcontractor’s standards meet the intent of NASA requirements. 

7.21 - Multi-condition Software Requirements - Specific recommendations for verifying software requirements with multiple conditional statements. 

-

8.1 - Off Nominal Testing -

8.2 - Software Reliability -

8.3 - Organizational Goals of Software Assurance Metrics -  

8.4 - Additional Requirements Considerations for Use with Safety-Critical Software -

8.5 - SW Failure Modes and Effects Analysis - 

8.6 -  IV&V Requirements and Surveillance - 

8.7 - Software Fault Tree Analysis - 

8.8 - COTS Software Safety Considerations - 

8.9 - Software Safety Analysis - 

8.10 - Facility Software Safety Considerations - Facility software system safety exists to ensure the safe and continuous operation of software associated with ground-based facilities.

8.11 - Auto-Generated Code - Model based coding techniques used with code generating tools.

8.12 - Basics of Software Auditing - software audits provide an independent evaluation of the conformance of software products and processes to applicable requirements, standards, guidelines, plans, and procedures.

8.13 - Test Witnessing - Guidance for software assurance personnel performing test witnessing.

8.14 - SA Tasking for NPR 7150.2B – Provides users of NPR7150.2B with the updated software assurance and software safety tasking in NASA-STD-8739.8A corresponding to the requirements in NPR 7150.2B. 

8.15 - SA Tasking Checklist Tool - Checklist tool that gives SA analysts the ability to tailor the software assurance and software safety tasks in NASA-STD-8739.8 and generate a tailored checklist for the tasks required on a project's software classification and safety criticality.

8.16 - SA Products -   Provides information for the major software assurance and safety work products resulting from the performance of the Software Assurance and Software Safety (SASS) tasks required in the NASA Software Assurance and Software Safety Standard, NASA-STD-8739.8 ²⁷⁸.  Each product’s section may include sub-products, potential analysis methods/technologies, and suggested content for capturing and reporting on the product activities.

8.17 - Software Safety Audit Checklists - This topic contains checklists for use by Software Assurance and Software  Safety  personnel when they are auditing projects with safety-critical software. 

8.18 - SA Suggested Metrics - This topic contains the complete list of software assurance/safety metrics that are suggested for use with the SA tasks in NASA-STD-8739.8.

8.19 - Dead / Dormant Code and Safety Critical Software - This topic discusses the issues of having dead or dormant code in software that is safety critical. 

8.20 - Safety Specific Activities in Each Phase - This topic provides a summary of the safety-specific activities that should be performed for any safety-critical software. The activities are grouped into the approximate life cycle phases where they will be performed.

8.21 - Software Hazard Causes - This topic provides a list of possible software causes that should be considered when developing the hazard analyses.

8.22 - Hazardous Commands - Provides some requirements for consideration when the software has hazardous commands.

1. 9.01 Software Design Principles - This topic contains the Guiding Principles that have been built over the years at NASA. These Principles are designed to help projects be successful by reducing the likelihood of defects.

3. 9.03 Coding Standards - Implement a "secure" coding standard on all mission-critical software.

5. Data Interface Integrity -

6. Dead Code Exclusion -

7. Fault Detection and Response -

9. Incorrect Memory Use or Access -

10. Initialization - Safe Mode -

12. Resource Margins -

13. Resource Oversubscription -

14. Resource Usage Measurement -

15. Safe Transitions -

16. Thread Safety -

17. Toggle Commands -

6.1 - Design for Safety Checklist  - Lists some key practices for software design, particularly when designing safety-critical software.

6.2 - Checklist for General Software Safety Requirements -  Provides a list of many of the requirements that should be included in a safety critical software system.

6.3 - Checklist for Choosing a Real Time Operating System (RTOS)  - Considerations for choosing the best RTOS for your application.

6.5 - Checklist for C Programming Practices –  Good practices to follow when coding in C for safety-critical software.

6.6 - Checklist for C++ Programming Practices – Good practices to follow when coding in C++ for safety-critical software.

6.7 - Checklist for Ada Programming Practices - Common errors to look for when coding in Ada.

6.9 - Checklist for Generic (Non-Language-Specific) Programming Practices - Practices that should be considered when coding safety critical software in any language. 

6.10 - Checklist for General Good Programming Practices - Contains a number of practices and activities that can improve the quality of the software.

6.12 - Reserved for next checklist -