Computer Science - Research and Development

, Volume 30, Issue 1, pp 21–34 | Cite as

Deriving fault-detection mechanisms from safety requirements

  • Dominik Sojer
  • Christian Buckl
  • Alois Knoll
Special Issue Paper


Safety requirements are an important artifact in the development of safety critical systems. They are used by experts as a basis for appropriate selection and implementation of fault detection mechanisms. Various research groups have worked on their formal modeling with the goal of determining if a system can meet these requirements.

In this paper, we propose the application of formal models of safety requirements throughout all constructive development phases of a model-driven development process to automatically generate appropriate fault detection mechanisms. The main contribution of this paper is a rigorous formal specification of safety requirements that allows the automatic propagation, transformation and refinement of safety requirements and the derivation of appropriate fault detection mechanisms. This is an important step to guarantee consistency and completeness in the critical transition from requirements engineering to software design, where a lot of errors can be introduced into a system by using conventional, non-formal techniques.


Safety Model-driven development Fault detection 


  1. 1.
    Aeronautical Radio Incorporated. ARINC 653, Avionics application software standard interface Google Scholar
  2. 2.
    Agha G (1986) Actors: a model of concurrent computation in distributed systems. MIT Press, Cambridge Google Scholar
  3. 3.
    Arora A, Kulkarni SS (1998) Detectors and correctors: a theory of fault-tolerance components. In: Proceedings of the 18th international conference on distributed computing systems Google Scholar
  4. 4.
    AUTOSAR Development Partnership. AUTOSAR Google Scholar
  5. 5.
    Avizienis A, Laprie J-C, Randell B, Landwehr C (2004) Basic concepts and taxonomy of dependable and secure computing. IEEE Trans Dependable Secure Comput Google Scholar
  6. 6.
    Bolton W (2006) Programmable logic controllers. Elsevier, Amsterdam Google Scholar
  7. 7.
    Briones JF, de Miguel M, Silva JP, Alonso A (2006) Integration of safety analysis and software development methods. In: Proceedings of the 1st international conference on system safety engineering Google Scholar
  8. 8.
    Buckl C (2008) Model-based development of fault-tolerant real-time systems. PhD thesis, TU München Google Scholar
  9. 9.
    Buckl C, Knoll A, Schieferdecker I, Zander J (2010) Model-base. In: Model-based engineering of embedded real-time systems. Springer, Berlin Google Scholar
  10. 10.
    Clarke EM, Clarke EM Jr, Grumberg O (2000) Model checking. MIT Press, Cambridge Google Scholar
  11. 11.
    Ericson CA (1999) Fault tree analysis: a history. In: Proceedings of the 17th international system safety conference Google Scholar
  12. 12.
    Ge X, Paige RF, McDermid JA (2009) Probabilistic failure propagation and transformation analysis. In: Proceedings of the international conference on computer safety, reliability and security Google Scholar
  13. 13.
    Gizopoulos D (2009) Online periodic self-test scheduling for real-time processor-based systems dependability enhancement. IEEE Trans Dependable Secure Comput 6(2):152–158 CrossRefGoogle Scholar
  14. 14.
    Graydon PJ, Knight JC, Strunk EA (2007) Assurance based development of critical systems. In: Proceedings of the 37th annual IEEE international conference on dependable systems and networks Google Scholar
  15. 15.
    Hanmer RS (2007) Patterns for fault tolerant software. Wiley, New York Google Scholar
  16. 16.
    Heitmeyer CL (2002) Software cost reduction. Encyclopedia of software engineering Google Scholar
  17. 17.
    Herrmann DS (1999) Software safety and reliability. IEEE Computer Society, Los Alamitos Google Scholar
  18. 18.
    Hölscher H, Rader J (1984) Microcomputers in safety technique. TÜV Rheinland Google Scholar
  19. 19.
    International Electrotechnical Commission. IEC 61882, Hazard and operability studies (HAZOP studies)—Application guide Google Scholar
  20. 20.
    International Electrotechnical Commission. IEC 61508, Functional safety of electrical/electronic/programmable electronic safety-related systems, April 2010 Google Scholar
  21. 21.
    International Organization for Standardization (2011) ISO 26262, Road vehicles: functional safety Google Scholar
  22. 22.
    Joshi A, Miller SP, Whalen M, Heimdahl MPE (2005) A proposal for model-based safety analysis. In: Proceedings of the 24th digital avionics systems conference Google Scholar
  23. 23.
    Kelly T, Weaver R (2004) The goal structuring notation—a safety argument notation. In: Proceedings of the dependable systems and networks 2004 workshop on assurance cases Google Scholar
  24. 24.
    Leveson N. (2009) Engineering a safer world Google Scholar
  25. 25.
    Li Y, Mutlu O, Mitra S (2009) Operating system scheduling for efficient online self-test in robust systems. In: IEEE/ACM international conference on computer-aided design—digest of technical papers Google Scholar
  26. 26.
    McDermid JA, Pumfrey DJ (1994) A development of hazard analysis to aid software design. In: Proceedings of the ninth annual conference on computer assurance, pp 17–25 Google Scholar
  27. 27.
    Mernik M, Heering J, Sloane AM (2005) When and how to develop domain-specific languages. In: ACM computing surveys (CSUR), pp 316–344 Google Scholar
  28. 28.
    Mohamed A, Zulkernine M (2008) On failure propagation in component-based software systems. In: Proceedings of the eighth international conference on quality software Google Scholar
  29. 29.
    Object Management Group. Object constraint language Google Scholar
  30. 30.
    Object Management Group (2001). Model driven architecture, a technical perspective. Technical report No. ab/2001-02-04 Google Scholar
  31. 31.
    Object Management Group (2006) Meta object facility (MOF) core specification Google Scholar
  32. 32.
    Pap Z, Majzik I, Pataricza A (2001) Checking general safety criteria on UML statecharts. Lecture notes in computer science Google Scholar
  33. 33.
    Papadopoulos Y, Walker M, Reiser M-O, Weber M, Chen D, Törngren M, Servat D, Abele A, Stappert F, Lonn H, Berntsson L, Johansson R, Tagliabo F, Torchiaro S, Sandberg A (2010) Automatic allocation of safety integrity levels. In: Proceedings of the 1st workshop on critical automotive applications: robustness & safety Google Scholar
  34. 34.
    Pinedo ML (2008) Scheduling: theory, algorithms and systems. Springer, Berlin Google Scholar
  35. 35.
    Radio Technical Commission for Aeronautics (1992) DO-178B, software considerations in airborne systems and equipment certification Google Scholar
  36. 36.
    SAE International (1996) ARP 4754, Certification considerations for highly-integrated or complex aircraft systems, November 1996 Google Scholar
  37. 37.
    Schneider D, Trapp M (2010) Conditional safety certificates in open systems. In: Proceedings of the 1st workshop on critical automotive applications: robustness & safety Google Scholar
  38. 38.
    Sojer D, Knoll A, Buckl C (2011) Synthesis of diagnostic techniques based on an IEC 61508-aware metamodel. In: Proceedings of the 6th IEEE international symposium on industrial embedded systems Google Scholar
  39. 39.
    Tribble AC, Miller SP (2004) Software intensive systems safety analysis.
  40. 40.
    Wallace M. (2005) Modular architectural representation and analysis of fault propagation and transformation. In: Proceedings of the workshop on formal foundations of embedded systems and component-based software architecture Google Scholar

Copyright information

© Springer-Verlag 2011

Authors and Affiliations

  1. 1.Department of InformaticsTechnische Universität MünchenGarching bei MünchenGermany
  2. 2.Cyber-Physical SystemsFortiss GmbHMünchenGermany

Personalised recommendations