Will it be Safe? — An Approach to Engineering Safety Requirements

  • Alan Simpson
  • Joanne Stoker


This paper describes experiences using Safety Requirements Engineering (SRE) to reduce the risk of systems not achieving safety certification and not working safely in the intended environment. Industry is creating ever-larger systems with increasing complexity. Applying traditional process-based safety assurance has become unwieldy and uneconomic. In this paper we describe some practical techniques we use for SRE to support rigorous product-based assurance. The aim is to provide detailed safety requirements to guide the choice of design, architecture and development processes, thus managing assurance more effectively. We describe an overview of the approach with specific emphasis in the second part of the paper on accident and hazard identification, illustrated with some examples from previous projects.


Application Domain Safety Requirement Safety Specification Fault Tree Analysis Fault Tree Analysis 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [Def Stan 00-56]
    Ministry of Defence: Safety Management Requirements for Defence Systems, December 1996Google Scholar
  2. [Fowler 2001]
    Fowler, D, Tiemeyer, B, Eaton, A: Safety Assurance of Air Traffic Management and Similarly Complex Systems, Proceedings of the 19th International System Safety Conference, September 2001.Google Scholar
  3. [HSE 1995]
    Health and Safety Executive: Out of Control; HSE Books ISBN 0717608476, 1995.Google Scholar
  4. [HSE 1999]
    Health and Safety Executive: Reducing Risks, Protecting People, HSE Discussion Document DDE-11, 1999.Google Scholar
  5. [IEC 61508]
    subcommittee 65A: System aspects of IEC technical committee 65: Industrial-process measurement and control: Functional safety of electrical/electronic/programmable electronic safety-related systems, December 1998.Google Scholar
  6. [ISO 13407]
    ISO Technical Committee ISO/TC 159 “Ergonomics”,Human-centred design processes for interactive systems, June 1999.Google Scholar
  7. [Jackson 1995]
    Jackson, M: The World and the Machine, Proceedings of the 17th International Conference on Software Engineering, IEEE, pp.283–292, 1995.Google Scholar
  8. [Leveson 2001]
    Leveson N: Evaluating Accident Models using Recent Aerospace Accidents, Software Engineering Research Laboratory MIT, 20 June 2001Google Scholar
  9. [Lutz 1993]
    Lutz R: Analyzing Software Requirements Errors in Safety-Critical Embedded Systems, IEEE international symposium on requirements engineering, San Diego, IEEE Comp Soc Press, 1993.Google Scholar
  10. [NUREG 0492]
    US Nuclear Regulatory Commission: Fault Tree Handbook, January 1981.Google Scholar
  11. [REVEAL]
    Praxis Critical Systems: REVEAL A keystone in Modern Systems Engineering, available from Praxis Critical Systems email:reveal Scholar
  12. [Simpson 1999]
    Simpson A, Ainsworth M: White Box Safety, Proceedings of 13th ERA International Avionics Conference, 1999.Google Scholar
  13. [Vickers 1996]
    Vickers, A J, Smith, J, Tongue, P: Complexity in Requirements Engineering, Proceedings UK INCOSE Symposium, 1996.Google Scholar
  14. [Yellow Book]
    Railtrack: Engineering Safety Management, Issue 3, Yellow Book 3. ISBN 0 9537595 0 4, 2000.Google Scholar

Copyright information

© Springer-Verlag London 2002

Authors and Affiliations

  • Alan Simpson
    • 1
  • Joanne Stoker
  1. 1.Praxis Critical Systems LimitedBathUK

Personalised recommendations