NASA-STD-8739.8
SOFTWARE ASSURANCE AND SOFTWARE SAFETY STANDARD
Organization: | NASA |
Publication Date: | 10 June 2020 |
Status: | active |
Page Count: | 59 |
scope:
Document Purpose
The purpose of the Software Assurance and Software Safety Standard is to define the requirements to implement a systematic approach to Software Assurance (SA), software safety, and Independent Verification and Validation (IV&V) for software created, acquired, provided, or maintained by or for NASA. Various personnel in the program, project, or facility, and Safety and Mission Assurance (SMA) organizations can perform the activities required to satisfy these requirements. The Software Assurance and Software Safety Standard provides a basis for personnel to perform software assurance, software safety, and IV&V activities consistently throughout the life of the software, that is, from its conception, through creation to operations and maintenance, and until the software is retired.
The Software Assurance and Software Safety Standard, in accordance with NPR 7150.2, NASA Software Engineering Requirements, supports the implementation of the software assurance, software safety, and IV&V sub-disciplines. The application and approach to meeting the Software Assurance and Software Safety Standard will vary based on the system and software products and processes to which they are applied. The Software Assurance and Software Safety Standard stresses coordination between the software assurance sub-disciplines, as well as with system safety, system reliability, hardware quality, system security, and software engineering, to maintain the system perspective and minimize duplication of effort.
The objectives of the Software Assurance and Software Safety Standard include:
a. Ensuring that the processes, procedures, and products used to produce and sustain the software conform to all requirements and standards specified to govern those processes, procedures, and products.
b. Ensuring that the software systems are safe and that the software safety-critical requirements and processes are followed.
c. Ensuring that the software systems are secure.
The Software Assurance and Software Safety Standard is compatible with all software life-cycle models. The Software Assurance and Software Safety Standard does not impose a particular life-cycle model on each software project; it does support a standard set of life-cycle phases as defined in NPR 7150.2.
In this standard, all mandatory actions (i.e., requirements) are denoted by statements containing the term "shall." The terms "may" denotes a discretionary privilege or permission, "can" denotes statements of possibility or capability, "should" denotes a good practice and is recommended, but not required, "will" denotes expected outcome, and "are/is" denotes descriptive material.
Document History



