Abstract
It is now widely recognised that software plays a significant role in the safety of many systems. There is a growing trend, in a number of industries, for a safety case to be required before a system can be deployed, or a plant put into operation. Where the system or plant1 contains a software element, the safety case needs to reflect the contribution of the software to system safety.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
American Society of Mechanical Engineers, Boiler and Pressure Vessel Code — Section III, Rules for the Construction of Nuclear Power Plant Components.
R Butler, G Finelli, The Infeasibility of Experimental Quantification of Life-Critical Software Reliability, in Proc. ACM SigSoft91 Conference on Software for Critical Systems, ACM Press, 1991.
S Cha, Private Communication, October 1995.
M Chudleigh, Hazard Analysis using HAZOP: A Case Study, in Proc. of SAFECOMP93, J Gorski (Ed), 1993.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 1996 Springer-Verlag London Limited
About this paper
Cite this paper
McDermid, J.A. (1996). Software Hazard and Safety Analysis: Opportunities and Challenges. In: Redmill, F., Anderson, T. (eds) Safety-Critical Systems: The Convergence of High Tech and Human Factors. Springer, London. https://doi.org/10.1007/978-1-4471-1480-2_14
Download citation
DOI: https://doi.org/10.1007/978-1-4471-1480-2_14
Publisher Name: Springer, London
Print ISBN: 978-3-540-76009-2
Online ISBN: 978-1-4471-1480-2
eBook Packages: Springer Book Archive