D. Software 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.11 - Model Based Development and Auto-generated Code  - addresses guidance for projects that desire to use model based development (MBDS)

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.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.5 - Work Breakdown Structures That Include Software - provides guidance on the development of a work breakdown structure (WBS) for software on projects

7.15 - Relationship Between NPR 7150.2 and NASA-STD-7009 - discusses the relationship to NASA-STD-7009 (Models and Simulation)

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.16 - Appendix C. Requirements Mapping and Compliance Matrix -  Guidance for using the 7150.2 Appendix C Requirements Mapping and Compliance Matrix.

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

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.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.19 - Software Risk Management Checklists - process whereby the project identifies and tracks threats to the success of the project.

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.20 - Assessing - Meets the Intent - assessment via functional groupings of requirements from the NASA standards can be performed 

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.7 - Software Fault Tree Analysis - A top-down analysis method to help identify the causes of presupposed hazards.

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.8 - COTS Software Safety Considerations - A discussion on the use of COTS in safety critical systems.

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

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.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.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.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.11 - Auto-Generated Code - Model based coding techniques used with code generating tools.

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.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.