Advertisement

Quality Assurance and Certification of Software Modules in Safety Critical Automotive Electronic Control Units Using a CASE-Tool Integration Platform

  • Klaus D. Mueller-Glaser
  • Clemens Reichmann
  • Markus Kuehl
  • Stefan Benz
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4147)

Abstract

Up to 70 electronic control units (ECU’s) serve for safety and comfort functions in a car. Communicating over different bus systems most ECU’s perform close loop control functions and reactive functions and have to fulfill hard real time constraints. Some ECU’s controlling on board entertainment/office systems are software intensive, incorporating millions of lines of code. The challenge for the design of those distributed and networked control units is to define all requirements and constraints, understand and analyze those manifold interactions between the control units, the car and the environment (driver, road, weather) in normal as well as stress situations (crash). To improve the design of safety critical ECU’s we propose an enhanced development process (double-V-model). The use of different modeling descriptions for closed loop control, reactive systems and software intensive systems requires a CASE-tool integration platform. We have developed “GeneralStore” as a platform to support model driven design with hetero-geneous models in a design process which is concurrent and distributed between the automotive manufacturer and several suppliers.

Keywords

Unify Modeling Language Software Module Electronic Control Unit Object Management Group Unify Modeling Language Model 
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.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Agrawal, A., Karsai, G., Ledeczi, A.: An End-to-End Domain-Driven Software Development Framework. In: 18th Annual ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), Domain-Driven Development Track, Anaheim, CA (October 2003)Google Scholar
  2. 2.
    Artisan homepage: http://www.artisansw.com
  3. 3.
  4. 4.
    Belschner, R., Freess, J., Mroßko, M.: Ganzheitlicher Entwicklungsansatz für Entwurf, Dokumentation und Bewertung von E/E-Architekturen. In: Tagungsband des 12. Internationalen Kongresses Elektronik im Kraftfahrzeug, VDI Berichte, Düsseldorf, vol. 1907, pp. 225–235 (2005)Google Scholar
  5. 5.
    Bertram, T., Dominke, P., Müller, B.: The Safety-Related Aspect of Cartronic. SAE World Congress, Session Code PC26 (1999)Google Scholar
  6. 6.
    Bluetooth homepage: http://www.bluetooth.com
  7. 7.
    Bortolazzi, J.: Systems Engineering for Automotive Electronics. Lecture Notes, Dep. of EEIT, University of Karlsruhe, Germany (2003)Google Scholar
  8. 8.
  9. 9.
    Department of Defense. MIL-Handbook 21: Reliability Prediction of Electronic Equipment (1995)Google Scholar
  10. 10.
    Dörr, H., Schürr, A., Altheide, F.: Requirements to a Framework for sustainable Integration of System, EuSEC, Toulouse (2002)Google Scholar
  11. 11.
  12. 12.
    Gamma, E., et al.: Design Patterns - elements of reusable object-oriented software. Addison-Wesley, Reading (1994)Google Scholar
  13. 13.
    Edler, F., Frese, T.: Systematic Safety Design Process for Distributed Vehicle Systems. In: Tagungsband des 12. Internationalen Kongresses Elektronik im Kraftfahrzeug, VDI Berichte, Düsseldorf, vol. 1907, pp. 225–235 (2005)Google Scholar
  14. 14.
    ETAS homepage: http://en.etasgroup.com
  15. 15.
    Hauser, J.: Development of Highly complex Control Systems at BMW Group, Competence Exchange Symposium 2004 (June 2004)Google Scholar
  16. 16.
    Hörner, H., Raisch, A., Meili, O.: Basic Software Components in AUTOSAR – a Solid Foundation. In: Tagungsband des 12. Internationalen Kongresses Elektronik im Kraftfahrzeug, VDI Berichte, Düsseldorf, vol. 1907, pp. 225–235 (2005)Google Scholar
  17. 17.
  18. 18.
  19. 19.
    I-Logix homepage: http://www.ilogix.com
  20. 20.
    Kalnins, A., Barzdins, J., et al.: Business Modeling Language GRAPES-BM and Related CASE Tools. In: Proceedings of Baltic DB&IS 1996, Institute of Cybernetics, Tallinn (1996)Google Scholar
  21. 21.
    Karsai, G., Agrawal, A., Shi, F., Sprinkle, J.: On the Use of Graph Transformations for the Formal Specification of Model Interpreters. Journal of Universal Computer Science, Special issue on Formal Specification of CBS (2003)Google Scholar
  22. 22.
    Karsai, G.: A Challenge and Opportunity for Model-based Software Development, Institute for Software Integrated Systems, Vanderbilt University, Automotive Software Workshop, San Diego (2004)Google Scholar
  23. 23.
    Kleppe, A., Warmer, J., Blast, W.: MDA Explained - The Model Driven Architecture: Practice and Promise. Addison-Wesley, Reading (2003)Google Scholar
  24. 24.
    Knepper, R.: The Safety and Reliability Process in the Civil Aircraft Industry. Technical Report, DaimlerChrysler Aerospace Airbus GmbH, HamburgGoogle Scholar
  25. 25.
  26. 26.
    Moser, W.: Motronic-Software / the key to a high performing engine management. In: ETAS Symposium 2004, BOSCH Gasoline Systems (2004)Google Scholar
  27. 27.
  28. 28.
    Object Management Group, OMG / Meta Object Facility (MOF) V1.4 (2001)Google Scholar
  29. 29.
    Object Management Group, OMG / Unified Modeling Language (UML) V1.4 (2001)Google Scholar
  30. 30.
    Object Management Group, OMG / XML Metadata Interchange (XMI) V1.0 (2000)Google Scholar
  31. 31.
    OSEK/VDX homepage, http://www.osek-vdx.org
  32. 32.
    Petrov, I., Jablonski, S.: An OMG MOF based Repository System with Querying Capability - the iRM Project. In: iiWAS 2004, Jakarata, Indoesien, September 27-29 (2004)Google Scholar
  33. 33.
    Polyspace homepage, http://www.polyspace.com
  34. 34.
    Porres, I.: A Toolkit for Manipulating UML Models. Software and Systems Modeling 2(4), 262–277 (2003)CrossRefGoogle Scholar
  35. 35.
    Sussman, D., Kay, M.: XSLT Programmer’s Reference, WROX (2001)Google Scholar
  36. 36.
    Telelogic Inc. homepage, http://www.telelogic.com/
  37. 37.
    The Mathworks homepage, http://mathworks.com
  38. 38.
    Union Technique de L’Electricite, RDF2000: Reliability Data Handbook (2000)Google Scholar
  39. 39.
    Velocity template engine, http://jakarta.apache.org/velocity/
  40. 40.
  41. 41.
    World Wide Web Consortium (W3C) homepage, http://www.w3.com/Consortium
  42. 42.
    World Wide Web homepage AUTOSAR, http://www.autosar.org

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Klaus D. Mueller-Glaser
    • 1
  • Clemens Reichmann
    • 1
  • Markus Kuehl
    • 2
  • Stefan Benz
    • 3
  1. 1.Institut für Technik der Informationsverarbeitung (ITIV)Universität KarlsruheKarlsruheGermany
  2. 2.Forschungszentrum Informatik (FZI)KarlsruheGermany
  3. 3.Robert Bosch GmbHStuttgartGermany

Personalised recommendations