Preliminary hazard analysis for safety-critical software systems

Abstract

The authors identify 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, a framework is introduced for applying them to safety-critical software development. Before explaining the framework and its related strategies, relevant background issues that relate to safety are discussed.<>