institut f¨ur informatik - PST Thesis Management Interface - LMU

2.1. Model-Driven Software Development
acting logical components, including their behavior. The logical components provide
functionalities described in the requirements model.
• The technical architecture defines the deployment architecture, i.e. all hardware units,
the basic software (operating system and middleware) on them and their connections -
controllers, communication devices, actuators and sensors, as well as a mapping from
the logical architecture (its structures and behaviors), to this deployment architecture.
• Behavioral models specify the functionality at a detailed level and allow the generation
of production, simulation and test code.
The work in [NH08] is motivated by the increasing integration of external devices and external
communication into the vehicle. The authors focus on developing a facility for modeldriven
development of embedded software that enables modeling from multiple viewpoints.
The viewpoints include the functional viewpoint, software structure viewpoint and humanmachine
interface viewpoint. They achieve this by extending a modeling facility that has
been proven successful in body electronics ECUs to the system level and the infotainment domain.
Furthermore, they include the associated requirements for wireless connectivity. This
way, they bring the different viewpoints together in a set of models. These models provide a
possibility to handle the associated complexity and ensure the quality of the vehicle software.
In [GHH04] the use of well-understood mathematical modeling frameworks that allow formal
verification of a system is emphasized. The background idea is early detection of bugs and
problems in order to achieve a more efficient embedded software development process. The
developed model-driven process places strong emphasis on performance and as much testing
and verification in tight-loops as possible. The models and controllers are framed in the
context of hybrid automata.
Software variability in automotive systems refers to deploying varying controller software
on the same ECU (while maintaining the same principal software structure) according to
different customer requirements. During product configuration (configuration of the ECU
software according to customer needs), specific class variants have to be selected (see section
3.1.2). Selecting the right combination of variants for a certain product is error-prone because
of the vast number of variants. Knowledge about dependent variants and conflicting
variants is currently not explicitly included in models, but it is up to the software engineers
to be aware of such dependencies and to resolve them. A solution to this problem is proposed
at system design level in [Gri08] by extending existing tools to allow explicit modeling of
dependencies between variants through creating appropriate metamodels.
A model-driven method for building embedded component infrastructures based on the
combination of component/container infrastructures is developed in [VSK05]. In particular,
automatic code generation is used to create infrastructure code required to make the
application logic work in the context of the embedded system’s hardware infrastructure.
Building a software infrastructure for embedded components is also one of the central issues
addressed by AUTOSAR. This extensive application of MDSD in the automotive domain is
concerned in this thesis and is presented in detail in chapter 3. In particular, AUTOSAR
addresses the logical and technical architecture mentioned above.
11