bannera

Book A.
Introduction

Book B.
7150 Requirements Guidance

Book C.
Topics

Tools,
References, & Terms

SPAN
(NASA Only)

Link
Leave blank if none exists

Title
This is the text which will be hyperlinked, if a link exists

SOFTWARE ASSURANCE AND SOFTWARE SAFETY STANDARD

SWE or Topic

SWE-001, SWE-013, SWE-014, SWE-020, SWE-022, SWE-023, SWE-024, SWE-025, SWE-026, SWE-034, SWE-039, SWE-044, SWE-045, SWE-051, SWE-052, SWE-060, SWE-061, SWE-066, SWE-069, SWE-074, SWE-075, SWE-076, SWE-077, SWE-084, SWE-085, SWE-105, SWE-106, SWE-110, SWE-112, SWE-116, SWE-120, SWE-121, SWE-122, SWE-125, SWE-129, SWE-131, SWE-132, SWE-133, SWE-134, SWE-136, SWE-138, SWE-139, SWE-141, SWE-160, SWE-164, SWE-176, SWE-179, SWE-205, SWE-209, SWE-216, SWE-221, Topic 7.2, Topic 7.3, Topic 7.4, Topic 7.12, Topic 7.18, Topic 7.20, Intro, Maint, SAP, IDD, Safety, SDD, SVD, Topic 8.2, Topic 8.6, Topic 8.8, Topic 8.9, Topic 8.10, Topic 8.11, Topic 8.13, Topic 8.14, Topic 8.15, Topic 8.16, Topic 8.17, Topic 8.18, Topic 8.20, Topic 8.22, Topic 7.1, Topic 7.21, p02, FAQ, ObjEv, IVVRef, SAANALYSIS, SADESIGN, SASTATUS, SATest, SASource, SAAudit,

Citation
This contains additional information, which will appear after the title, separated by a comma

NASA-STD-8739.8B , NASA TECHNICAL STANDARD, Approved 2022-09-08
Superseding "NASA-STD-8739.8A,

Notes
More specific directions where to look in the resource for relevant content

Example Reference as it will appear to end user:

  1. Title, Citation

where:



Old versions of NASA-STD-8739.8

Quotes used in SWEs and Topics

Software is classified as safety-critical if the software is determined by and traceable to a hazard analysis. Software is classified as safety-critical if it meets at least one of the following criteria:

a. Causes or contributes to a system hazardous condition/event,
b. Controls functions identified in a system hazard,
c. Provides mitigation for a system hazardous condition/event,
d. Mitigates damage if a hazardous condition/event occurs,
e. Detects, reports, and takes corrective action if the system reaches a potentially hazardous state.

Software Assurance and Software Safety Tasks contained in NASA-STD-8739.8A - related to SWE-134

1. Analyze the software requirements and the software design and work with the project to implement NPR 7150.2, SWE-134 requirement items "a" through "l."

2. Assess that the source code satisfies the conditions in the NPR 7150.2, SWE-134 requirement "a" through "l" for safety-critical and mission-critical software at each code inspection, test review, safety review, and project review milestone.

3. Confirm 100% code test coverage is addressed for all identified software safety-critical software components or assure that software developers provide a risk assessment explaining why the test coverage is not possible for the safety-critical code component.

4. Confirm that all identified safety-critical software components have a cyclomatic complexity value of 15 or lower. If not, assure that software developers provide a risk assessment explaining why the cyclomatic complexity value needs to be higher than 15 and why the software component cannot be structured to be lower than 15.

5. Confirm that the values of the safety-critical loaded data, uplinked data, rules, and scripts that affect hazardous system behavior have been tested.

6. Analyze the software design to ensure:
a. Use of partitioning or isolation methods in the design and code,
b. That the design logically isolates the safety-critical design elements and data from those that are non-safety-critical.

7. Participate in software reviews affecting safety-critical software products.

1. Analyze the software requirements and the software design and work with the project to implement NPR 7150.2, SWE-134 requirement items "a" through "l."

2. Assess that the source code satisfies the conditions in the NPR 7150.2, SWE-134 requirement "a" through "l" for safety-critical and mission-critical software at each code inspection, test review, safety review, and project review milestone.

3. Confirm 100% code test coverage is addressed for all identified software safety-critical software components or assure that software developers provide a risk assessment explaining why the test coverage is not possible for the safety-critical code component.

4. Confirm that all identified safety-critical software components have a cyclomatic complexity value of 15 or lower. If not, assure that software developers provide a risk assessment explaining why the cyclomatic complexity value needs to be higher than 15 and why the software component cannot be structured to be lower than 15.

5. Confirm that the values of the safety-critical loaded data, uplinked data, rules, and scripts that affect hazardous system behavior have been tested.

6. Analyze the software design to ensure:
a. Use of partitioning or isolation methods in the design and code,
b. That the design logically isolates the safety-critical design elements and data from those that are non-safety-critical.

7. Participate in software reviews affecting safety-critical software products.