D. Topics

7.1 - History and Overview of the Software Process Improvement (SPI) Effort - addresses the history of the NASA software improvement efforts to provide a background for the development of this electronic handbook

7.3 - Acquisition Guidance - discusses guidance for projects implementing those requirements in NASA Procedural Requirement (NPR) 7150.2, NASA Software Engineering Requirements that address software acquisition

7.5 - Work Breakdown Structures That Include Software - provides guidance on the development of a work breakdown structure (WBS) for software on projects

7.6 - Software Test Estimation and Testing Levels - provides guiding principles and best practices pertaining to software test estimation and a description of the typical "levels" of testing performed for a software project

7.7 - Software Architecture Description - recommends the kinds of content that should appear in a software architecture description for NASA projects

7.9 - Entrance and Exit Criteria - focused on the responsibilities of the software engineering community throughout the project life cycle reviews, in the areas of Entrance Criteria, Exit Criteria, and Materials for Review

7.10 - Peer Review and Inspections Including Checklists - describes the role of Peer Reviews and Inspections in detecting potential product defects and evaluating 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 - addresses guidance for projects that desire to transition software from a lower to a higher classification

7.14 - Implementing Measurement Requirements and Analysis for Projects - guidance on software measurement throughout the lifecycle, from the planning stages through implementation stages of collection, analysis and reporting

7.15 - Relationship Between NPR 7150.2 and NASA-STD-7009 - discusses the relationship 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.) - content from the Appendices of NPR 7150.2C

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

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

7.20 - Assessing - Meets the Intent - assessment via functional groupings of requirements from the NASA standards can be performed 

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

-

8.1 - Off Nominal Testing - Off-Nominal Testing focuses on out of bounds parameters, rainy scenarios, and capabilities that are typically considered as "must not work" function.

8.2 - Software Reliability - The goal of SW reliability and maintainability is to assure that SW performs consistently as desired, when operating within specified conditions. This topic covers additional basic information on software reliability.

8.3 - Organizational Goals of Software Assurance Metrics - A table of the software assurance metrics with their associated goals and questions

8.4 - Additional Requirements Considerations for Use with Safety-Critical Software - requirements to be considered when you have safety-critical software on a program/project/facility.

8.5 - SW Failure Modes and Effects Analysis - A "bottoms up" structured analysis method to help determine potential failures or hazards in the software design with guidance and forms.

8.6 -  IV&V Requirements and Surveillance - This guidance will establish the rationale behind the creation of an IV&V Requirements and Surveillance activities. 

8.7 - Software Fault Tree Analysis - A top-down analysis method to help identify the causes of presupposed hazards.

8.8 - COTS Software Safety Considerations - A discussion on the use of COTS in safety critical systems.

8.9 - Software Safety Analysis - Software Safety Analysis (SSA) is a term that is used to describe a wide range of analyses.  This article provides guidance on performing a SSA to satisfy NASA-STD-8739.8 requirement associated with NPR 7150.2 SWE-205.

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 based 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 - SA List of Confirmations -

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.

1. Software Design Principles -

3. Coding Standards -

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 -