Software safety workshop problem
More than 20 years ago, a philosophy was developed for the design and analysis of hardware systems to ensure that they would perform in a predictably safe manner, even in severe abnormal environments. This philosophy has been scrutinized and tested during the intervening years, and has proved successful in practice. A requirement guiding the development of the philosophy was that the resulting design must be simple enough to be amenable to analysis. The inherent simplicity is a safety attribute, because complex analyses, such as those represented by fault trees containing hundreds of branches, are extremely susceptible to error. There are many examples where such errors led analysts to believe systems were safe when they were not, with disastrous consequences. The purpose of this workshop problem is to determine whether the principles developed to ensure hardware safety are applicable in any way to safety-critical software systems. It is possible that hardware associations with software will need to be considered, but whether or not this is true is left as an aspect of the investigation. In order to put the ground rules in perspective, it will be necessary to establish some framework.
- Research Organization:
- Sandia National Labs., Albuquerque, NM (USA)
- Sponsoring Organization:
- DOE/DP
- DOE Contract Number:
- AC04-76DP00789
- OSTI ID:
- 6655875
- Report Number(s):
- SAND-90-2255C; CONF-9010171--2; ON: DE90016222
- Country of Publication:
- United States
- Language:
- English
Similar Records
Software Reliability Cases: The Bridge Between Hardware, Software and System Safety and Reliability
Workshop on developing safe software