Evaluation of safety-critical software
Communications of the ACM
Dictionary of computing (3rd ed.)
Dictionary of computing (3rd ed.)
Validation of ultrahigh dependability for software-based systems
Communications of the ACM
Targeting safety-related errors during software requirements analysis
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Safeware: system safety and computers
Safeware: system safety and computers
Intent Specifications: An Approach to Building Human-Centered Specifications
IEEE Transactions on Software Engineering
Communications of the ACM
Breaking Through the V and V Bottleneck
Proceedings of the Second International Eurospace - Ada-Europe Symposium on Ada in Europe
Erroneous Requirements: A Linguistic Basis for Their Occurrence and an Approach to Their Reduction
SEW '01 Proceedings of the 26th Annual NASA Goddard Software Engineering Workshop
Towards a model-based evolutionary chain of evidence for compliance with safety standards
SAFECOMP'12 Proceedings of the 2012 international conference on Computer Safety, Reliability, and Security
| Hi-index | 0.00 |
The application of software safety standards as part of the development of safety critical software is usually considered an essential element of any safety program. Yet it is fairly rare for safety practitioners to step back and critically evaluate both the effectiveness and limitations of such standards.Naive implementations of safety standards can lead to over reliance on weak inductive arguments as to the safety of the software. Whilst incorrect requirements have been identified as a major cause of software accidents it appears that current software safety standards do not place a proportionate emphasis upon this causal factor. Additionally focusing upon the definition of process as opposed to the documentation of lessons learned the majority of software safety standards also appear inadequate to serve as repositories of the 'state of the art'.This paper examines the limitations, practical problems and issues associated with the use of current software safety standards. The evolution of software safety standards is reviewed and contrasted to the safety standards of other engineering disciplines. The paper then goes onto discuss problems with the current process based software safety standards and considers whether these standards in fact address the real causes of software related accidents. Finally the often overlooked pragmatic issues of applying safety standards are discussed. Due to space considerations the primary standards discussed are DEF-STAN 00-55 and 00-56, MIL-STD-882C, ARP 4761, ARP 4754, IEC 61508, DEF AUST 5679 and RTCA/DO-178B.