Model Driven Software Development in the Context of Embedded Component Infrastructures

  • Markus Voelter
  • Christian Salzmann
  • Michael Kircher
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3778)


In this chapter we motivate the need for an infrastructure platform for embedded software, supporting the development of reusable systems. Our solution is based on a component infrastructure that is implemented using model-driven software development (MDSD) techniques. This approach allows us to achieve the goal of re-usability while still providing an efficient system, tailored for the specific embedded hardware and operating system.

This chapter explains the principles of our approach and introduces model-driven software development. It illustrates the concepts by presenting an example of how to model and specify the embedded application (a simple weather station), and how to generate supporting component middleware infrastructure from these models.


Domain Architecture Object Management Group Embed Software Concrete Syntax Embed Device 
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.
    The AUTOSAR Consortium. AUTOSAR homepage,
  2. 2.
    Domain Specific Modelling Fourm,
  3. 3.
    Eisenecker, U., Czarnecki, K.: Generative Programming. Addison-Wesley, Reading (2000)Google Scholar
  4. 4.
    ETAS Group, ASCET Homepage, sd/index.shtml
  5. 5.
    Ewald, T.: Transactional COM+: Building Scalable Applications. Addison-Wesley, Reading (2001)Google Scholar
  6. 6.
    Gamma, H., Johnson, V.: Design Patterns. Addison-Wesley, Reading (1995)Google Scholar
  7. 7.
    Henney, K.: Inside Requirements. Programmer’s Workshop column in Application Development Advisor (May- une 2003),
  8. 8.
    I-Logix, Statemate homepage,
  9. 9.
    The Mathworks, Matlab Homepage,
  10. 10.
    The openArchitectureWare generator framework,
  11. 11.
    Object Management Group, Minimum CORBA (2004),
  12. 12.
    Object Management Group, Real-Time CORBA (2004),
  13. 13.
    Object Management Group, CORBA Component Model Specification, CCM (2004),
  14. 14.
    OMG, Model-Driven Architecture (MDA),
  15. 15.
    OSGi Alliance (2004),
  16. 16.
    Parnas, D.L.: On the Criteria To Be Used in Decomposing Systems into Modules. Communications of the ACM 15(2) (December 1972)Google Scholar
  17. 17.
    Schwanninger, C., Wuchner, E., Kircher, M.: Encapsulating Cross-Cutting Concerns in System Software. In: Workshop on Aspects, Components, and Patterns for Infrastructure Software, AOSD 2004 conference, Lancaster, UK, March 22-26 (2004)Google Scholar
  18. 18.
    Sun Microsystems, Java2 Enterprise Edition, J2EE (2004),
  19. 19.
    Voelter, M., Kircher, M., Zdun, U.: Remoting Patterns: Foundations of Enterprise. In: Internet and Realtime Distributed Object Middleware, John Wiley & Sons, Chichester (2004)Google Scholar
  20. 20.
  21. 21.
    Voelter, M., Stahl, T., Bettin, J.: Modellgetriebene Softwareentwicklung. dPunkt, to be published in (2004); an English version is in preparationGoogle Scholar
  22. 22.
    Voelter, M., Schmid, A., Wolff, E.: Server Component Patterns - Component Infrastructures Illustrated with EJB. John Wiley & Sons, Chichester (2002)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2005

Authors and Affiliations

  • Markus Voelter
    • 1
  • Christian Salzmann
    • 2
  • Michael Kircher
    • 3
  1. 1.Voelter – Ingenieurbüro für Softwaretechnologie HeidenheimGermany
  2. 2.BMW Car ITMünchenGermany
  3. 3.Siemens AG Corporate TechnologyMünchenGermany

Personalised recommendations