Software safety assurance philosophy and practices at the NASA Ames are discussed. It is shown that, to be safe, software must be error-free. Software developments on two digital flight control systems and two ground facility systems are examined, including the overall system and software organization and function, the software-safety issues, and their resolution. The effectiveness of safety assurance methods is discussed, including conventional life-cycle practices, verification and validation testing, software safety analysis, and formal design methods. It is concluded (1) that a practical software safety technology does not yet exist, (2) that it is unlikely that a set of general-purpose analytical techniques can be developed for proving that software is safe, and (3) that successful software safety-assurance practices will have to take into account the detailed design processes employed and show that the software will execute correctly under all possible conditions.
Software safety - A user's practical perspective
1990-01-01
Conference paper
No indication
English
User's Perspective of Software Quality
IEEE | 2018
|British Library Conference Proceedings | 1999
|Tomorrow's trucks: The user's perspective
Tema Archive | 1985
|Debris Assessment Software User’s Guide
NTRS | 2020
|Space transportation - The commercial user's perspective
AIAA | 1988
|