TY - GEN
T1 - Preliminary hazard analysis for safety-critical software systems
AU - Gowen, L. D.
AU - Collofello, J. S.
AU - Calliss, F. W.
N1 - Publisher Copyright:
© 1992 IEEE.
PY - 1992
Y1 - 1992
N2 - Due to the rapid increase in computer-related technologies, industry is continuing to put higher demands on software-controlled systems. These demands are sometimes placing software in total or partial control over critical system functions such as shutting down nuclear reactors, navigating planes, determining radiation dosages, and identifying military targets. Unfortunately, certain faults in such a system can result in catastrophic consequences such as death, environmental harm, or equipment damage. In order to help insure that safety-critical software systems do not cause accidents, researchers are concentrating on techniques for improving various life-cycle phases. This paper identifies strategies for conducting preliminary software hazard analysis, which includes software hazard identification, documentation, and review. The goal for such strategies is to improve a system's overall safety by increasing the hazard list's completeness, correctness, and preciseness. Along with presenting these strategies, this paper introduces a framework for applying them to safetycritical software development. This paper is part of a joint ongoing research effort by academia and industry to form a methodology for developing safetycritical software systems. Before explaining the framework and its related strategies, this paper discusses relevant background issues that relate to safety.
AB - Due to the rapid increase in computer-related technologies, industry is continuing to put higher demands on software-controlled systems. These demands are sometimes placing software in total or partial control over critical system functions such as shutting down nuclear reactors, navigating planes, determining radiation dosages, and identifying military targets. Unfortunately, certain faults in such a system can result in catastrophic consequences such as death, environmental harm, or equipment damage. In order to help insure that safety-critical software systems do not cause accidents, researchers are concentrating on techniques for improving various life-cycle phases. This paper identifies strategies for conducting preliminary software hazard analysis, which includes software hazard identification, documentation, and review. The goal for such strategies is to improve a system's overall safety by increasing the hazard list's completeness, correctness, and preciseness. Along with presenting these strategies, this paper introduces a framework for applying them to safetycritical software development. This paper is part of a joint ongoing research effort by academia and industry to form a methodology for developing safetycritical software systems. Before explaining the framework and its related strategies, this paper discusses relevant background issues that relate to safety.
UR - http://www.scopus.com/inward/record.url?scp=84886457392&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84886457392&partnerID=8YFLogxK
U2 - 10.1109/PCCC.1992.200597
DO - 10.1109/PCCC.1992.200597
M3 - Conference contribution
AN - SCOPUS:84886457392
T3 - 11th Annual International Phoenix Conference on Computers and Communication, IPCCC 1992 - Proceedings
SP - 501
EP - 508
BT - 11th Annual International Phoenix Conference on Computers and Communication, IPCCC 1992 - Proceedings
PB - Institute of Electrical and Electronics Engineers Inc.
T2 - 11th Annual International Phoenix Conference on Computers and Communication, IPCCC 1992
Y2 - 1 April 1992 through 3 April 1992
ER -