Automatically Generated Safety Mechanisms from Semi-Formal Software Safety Requirements

  • Raphael Fonte Boa Trindade
  • Lukas Bulwahn
  • Christoph Ainhauser
Part of the Lecture Notes in Computer Science book series (LNCS, volume 8666)


Today’s automobiles incorporate a great number of functions that are realized by software. An increasing number of safety-critical functions also follow this trend. For the development of such functions, the ISO 26262 demands a number of additional steps to be performed compared to common software engineering activities. We address some of these demands with means to semi-formally express software safety requirements, tools to automatically implement these requirements, and artifacts and traceability information that can be used for safety case documentation. Through a hierarchical classification of safety mechanisms, a semi-formal specification language for requirements, a generation engine and a case study on a production-model automotive system, we demonstrate: first, how expert knowledge of the functional safety domain can be captured, second, how the tedious and error prone task of manually implementing safety mechanisms can be automated, and third, how this serves as a basis for formal safety argumentation.


Model Transformation Software Architecture Software Component Safety Requirement Rear Axle 
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. 1.
    Arora, A., Kulkarni, S.S.: Detectors and correctors: A theory of fault-tolerance components. In: Int. Conf. on Distributed Computing Systems, pp. 436–443 (1998)Google Scholar
  2. 2.
    Artop User Group: Artop – AUTOSAR tool platform,
  3. 3.
    Artop User Group: Artext – an AUTOSAR textual language framework (2013),
  4. 4.
    AUTOSAR Development Partnership: Main requirements (v 2.1.0, rel 4.0, rev 1)Google Scholar
  5. 5.
    Cuenot, P., Ainhauser, C., Adler, N., Otten, S., Meurville, F.: Applying model based techniques for early safety evaluation of an automotive architecture in compliance with the ISO 26262 standard. In: Embedded Real-Time Software and Systems, ERTS (2014)Google Scholar
  6. 6.
    Erkkinen, T., Conrad, M.: Safety-critical software development using automatic production code generation (technical paper). In: SAE World Congress 2007 (2007)Google Scholar
  7. 7.
    ISO: ISO/FDIS 26262, Part 6 - product development at the software level (2011)Google Scholar
  8. 8.
    ISO: ISO/FDIS 26262 road vehicles – functional safety (2011)Google Scholar
  9. 9.
    ITEA2 Project SAFE: Deliverable D3.6.b: Safety code generator specification (2013),
  10. 10.
    ITEA2 Project SAFE: Safe - Safe Automotive software architecture (2013),
  11. 11.
    ITEA2 Project SAFE: Deliverable D5.6.c: Evaluation of safety code generation, (to be published, 2014)
  12. 12.
    Kirrmann, H., Grosspietsch, K.: Fault-tolerant control systems (survey paper). Automatisierungstechnik 50(8), 362–374 (2002)Google Scholar
  13. 13.
    Mader, R., Griessnig, G., Armengaud, E., Leitner, A., Kreiner, C., Bourrouilh, Q., Steger, C., Weiss, R.: A bridge from system to software development for safety-critical automotive embedded systems. In: 38th EUROMICRO Conference on Software Engineering and Advanced Applications, SEAA 2012, pp. 75–79 (2012)Google Scholar
  14. 14.
    Masci, P., Ayoub, A., Curzon, P., Lee, I., Sokolsky, O., Thimbleby, H.: Model-based development of the generic PCA infusion pump user interface prototype in PVS. In: Bitsch, F., Guiochet, J., Kaâniche, M. (eds.) SAFECOMP. LNCS, vol. 8153, pp. 228–240. Springer, Heidelberg (2013)CrossRefGoogle Scholar
  15. 15.
    MIRA Ltd.: MISRA-C:2004 Guidelines for the use of the C language in critical systems (2004),
  16. 16.
    NASA: NASA software safety guidebook. NASA (2004)Google Scholar
  17. 17.
    The MathWorks Inc.: Simulink (2013)Google Scholar
  18. 18.
    Voelter, M., Ratiu, D., Schätz, B., Kolb, B.: mbeddr: An extensible C-based programming language and IDE for embedded systems. In: Proc. of the 3rd Ann. Conference on Systems, Programming, and Applications: Software for Humanity, SPLASH 2012, pp. 121–140. ACM (2012)Google Scholar
  19. 19.
    Wu, W., Kelly, T.: Safety tactics for software architecture design. In: Proc. of the 28th Annual Int. Computer Software and Applications Conference, COMPSAC 2004, pp. 368–375. IEEE (2004)Google Scholar

Copyright information

© Springer International Publishing Switzerland 2014

Authors and Affiliations

  • Raphael Fonte Boa Trindade
    • 1
  • Lukas Bulwahn
    • 1
  • Christoph Ainhauser
    • 1
  1. 1.BMW Car IT GmbHMünchenGermany

Personalised recommendations