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

3.1. The AUTOSAR standard
contained in the Component Internal Behavior Description and Component API documents
to develop functional aspects of the component. This can be done independently
from the design of the rest of the system. The functionality of the component is contained
in the Component Implementation Description. The Compile Component activity uses
the Component Implementation Description to compile the Component Implementation.
Additionally the activity requires the Component API and the Additional Headers documents
to complete the compilation process. The result of the Compile Component activity
is the Compiled Component document and a refined Component Implementation
Description.
3.1.3. AUTOSAR metamodel
The data contained in the documents that are utilized within the AUTOSAR methodology
(see section 3.1.2) is supported through the use of an AUTOSAR metamodel and the accompanying
templates 1 . The metamodel describes the structure of all components that compose
the AUTOSAR architecture, i.e. software components (depicted in figure 3.4), ECU configuration
and basic software modules. The templates describe the respective parts of the
metamodel in more detail [AUT09].
Figure 3.4.: Detailed view of the AUTOSAR metamodel in [autb] describing different types
of software components in AUTOSAR and their relationships.
1 The metamodels and the templates are available at the official AUTOSAR website. The metamodels are
described in terms of UML diagrams and available as Sparx Systems Enterprise Architect Project files.
29