Link |
|
Title |
NASA Software Safety Standard, |
SWE or Topic |
SWE-006, SWE-013, SWE-020, SWE-022, SWE-023, SWE-039, SWE-044, SWE-049, SWE-050, SWE-051, SWE-052, SWE-054, SWE-056, SWE-059, SWE-060, SWE-062, SWE-064, SWE-067, SWE-068, SWE-069, SWE-072, SWE-074, SWE-075, SWE-077, SWE-079, SWE-080, SWE-085, SWE-086, SWE-102, SWE-106, SWE-109, SWE-112, SWE-113, SWE-115, SWE-116, SWE-122, SWE-129, SWE-130, SWE-131, SWE-133, SWE-134, SWE-136, SWE-138, SWE-147, SWE-160, SWE-164, SWE-179, SWE-184, SWE-186, SWE-205, Topic 7.2, Topic 7.4, Topic 7.12, Topic 7.15, Topic 7.18, Topic 8.22, Intro, SDP, Safety, SRS, CR-PR, SUM, IDD, SAP, SVD, |
Citation |
NASA STD 8719.13 (Rev C ) , Document Date: 2013-05-07 |
Notes |
|
Example Reference as it will appear to end user:
- Title
, Citation
where:
- Title = Title
- Link = http://www.nasa.gov
- Citation = Citation
Quotes used in SWEs and Topics
- SWE-147 - Specify Reusability Requirements - fragments taken from para 6.6.1
“Use of ... reused software that is not developed specifically for the safety-critical system can be risky. The software in this category includes ... previously created software (e.g., from a past project). It is important to evaluate the differences between how the ... reused software will be used within the new system, and how it was used in previous systems. The differences in operational constraints or configuration of the software may affect the operation of the ... reused software, sometimes in unexpected ways.”
- SWE-051 - Software Requirements Analysis - tab 3 - from para 7.2.2.5
"The provider software safety requirements analysis will be available to the acquirer and the acquirer SMA for program, project, and facility formal reviews, system-level safety reviews, and upon acquirer request."
- SUM - Software User Manual - tab 3 - from para 7.7.8 and 7.7.9
7.7.8 Operational documentation, including user manuals and procedures, will describe all safety related commands, data, input sequences, options, error messages, corrective actions, and other items necessary for the safe operation of the system which software implements. 7.7.9 The provider SMA responsible for operations and maintenance shall evaluate user manuals and procedures (including updates) for safety-related commands, data, input sequences, options, error messages, corrective actions, and other items implemented in software which are necessary for the safe operation of the system, and for any safety impacts. This will ensure that any software-related hazard closures that depend on operational workarounds are properly documented.
