Jump to content

EAST-ADL

Edit links
From Wikipedia, the free encyclopedia

EAST-ADL is an Architecture Description Language (ADL) for automotive embedded systems, developed in several European research projects. It is designed to complement AUTOSAR with descriptions at higher level of abstractions. Aspects covered by EAST-ADL include vehicle features, functions, requirements, variability, software components, hardware components and communication.[1] Currently, it is maintained by the EAST-ADL Association[2] in cooperation with the European FP7 MAENAD[3] project.

Overview

[edit]

EAST-ADL is a domain-specific language using meta-modeling constructs such as classes, attributes, and relationships. It is based on concepts from UML, SysML and AADL, but adapted for automotive needs and compliance with AUTOSAR. There is an EAST-ADL UML2 profile which is used in UML2 tools for user modeling.
The EAST-ADL definition also serves as the specification for implementation in domain-specific tools.

EAST-ADL contains several abstraction levels. The software- and electronics-based functionality of the vehicle are described at different levels of abstraction. The proposed abstraction levels and the contained elements provide a separation of concerns and an implicit style for using the modeling elements. The embedded system is complete on each abstraction level, and parts of the model are linked with various traceability relations. This makes it possible to trace an entity from feature down to components in hardware and software.

EAST-ADL is defined with the development of safety-related embedded control systems as a benchmark. The EAST-ADL scope comprises support for the main phases of software development, from early analysis via functional design to the implementation and back to integration and validation on vehicle level. The main role of EAST-ADL is that of providing an integrated system model. On this basis, several concerns are addressed:

  • Documentation, in terms of an integrated system model.
  • Communication between engineers, by providing predefined views as well as related information.
  • Analysis, through the description of system structure and properties.

Behavioural models for simulation or code generation are supported as references from EAST-ADL functions to external models, such as a subsystem in MATLAB/Simulink.[4]

Organisation of EAST-ADL Meta-Model

[edit]

The EAST-ADL meta-model is organized according to 4 abstraction levels:

  • Vehicle level contains modeling elements to represent intended functionality in a solution-independent way
  • Analysis level represents the abstract functional decomposition of the vehicle with the principal internal and external interfaces.
  • Design level has the detailed functional definition, a hardware architecture and allocations of functions to hardware.
  • Implementation level relies on AUTOSAR elements and does not have EAST-ADL-specific constructs for the core structure.

For all abstraction levels, relevant extension elements for requirements, behavior, variability and dependability are associated to the core structure.

Relation between EAST-ADL and AUTOSAR

[edit]

Instead of providing modeling entities for the lowest abstraction level, i.e. implementation level, EAST-ADL uses unmodified AUTOSAR entities for this purpose and provides means to link EAST-ADL elements on higher abstraction levels to AUTOSAR elements. Thus, EAST-ADL and AUTOSAR in concert provide means for efficient development and management of the complexity of automotive embedded systems from early analysis right down to implementation. Concepts from model-based development and component-based development reinforce one another.
An early, high-level representation of the system can evolve seamlessly into the detailed specifications of the AUTOSAR language. In addition, the EAST-ADL incorporates the following system development concerns:

  • Modeling of requirements and verification/validation information,
  • Feature modeling and support for software system product lines,
  • Modeling of variability of the system design,
  • Structural and behavioral modeling of functions and hardware entities in the context of distributed systems,
  • Environment, i.e., plant model and adjacent systems, and
  • Non-functional operational properties such as a definition of function timing and failure modes, supporting system level analysis.

The EAST-ADL metamodel is specified according to the same rules as the AUTOSAR metamodel, which means that the two sets of elements can co-exist in the same model. The dependency is unidirectional from EAST-ADL to AUTOSAR, such that AUTOSAR is independent of EAST-ADL. However, relevant EAST-ADL elements can reference AUTOSAR elements to provide EAST-ADL support for requirements, variability, safety, etc. to the AUTOSAR domain.

A model may thus be defined where AUTOSAR elements represent the software architecture and EAST-ADL elements extend the AUTOSAR model with orthogonal aspects and represents abstract system information through e.g. function and feature models. Such model can be defined in UML, by applying both an EAST-ADL profile [5] and an AUTOSAR profile,[6] or in a domain specific tool based on a merged AUTOSAR and EAST-ADL metamodel.[7]

History and Specification of EAST-ADL

[edit]

The EAST-ADL language has been defined in several steps within European research projects:

Project name Time Budget EAST-ADL Version Specification Download Support by research departments of following vehicle manufacturers(OEMs)
EAST-EEA [8] 1.7.2001 - 30.6.2004 40 M€ EAST-ADL Version 1.0 No download available after project had finished BMW, Daimler, Fiat, PSA (Peugeot/Citroen), Renault, Volvo, Valeo
ATESST [9] 1.1.2006 - 31.3. 2008 3.9 M€ EAST-ADL Version 2.0 https://web.archive.org/web/20110725022136/http://www.atesst.org/home/liblocal/docs/EAST-ADL-2.0-Specification_2008-02-29.pdf Daimler, Volvo Group, VW/Carmeq
ATESST2 [10] 1.7.2008 - 30.6. 2010 3.8 M€ EAST-ADL Version 2.1 https://web.archive.org/web/20110725022320/http://www.atesst.org/home/liblocal/docs/ATESST2_D4.1.1_EAST-ADL2-Specification_2010-06-02.pdf Fiat, Volvo Group, Volvo Cars, VW/Carmeq
MAENAD [3][11] 1.9.2010 - 31.8. 2013 4.0 M€ V2.1.12 www.east-adl.info Fiat, Volvo Group

EAST-ADL is governed by the EAST-ADL Association,[2] founded in September 2011. The EAST-ADL UML2 profile is represented in the EAST-ADL annex to the OMG MARTE profile.

Discussion

[edit]

While interest from automotive companies in EAST-ADL is increasing over the past years, EAST-ADL is still to be seen as a research effort (as of 2012). The practical acceptance of EAST-ADL in the automotive industry is still very low, even though EAST-ADL addresses many important aspects of vehicle development. EAST-ADL is used as a reference model in other research projects, e.g. CESAR[12] and TIMMO-2-USE[13]

Modeling Tools and File Format

[edit]

EAST-ADL tool support is still limited, although a UML profile is available and domain specific tools such as MentorGraphics VSA, MetaCase MetaEdit+ [14] and Systemite SystemWeaver[15] have been tailored for EAST-ADL in the context of research projects and with customers. Papyrus UML,[16] extended within the ATESST project as a concept demonstrator has EAST-ADL support, and MagicDraw,[17] can also provide EAST-ADL palettes, diagrams, etc. In the case of UML, developers also need to have knowledge of UML (classes, stereotypes, arrow types, ..) for modeling with EAST-ADL. Many automotive engineers, in particular mechanical engineers, hardware developers, process experts) do not have this knowledge and prefer other approaches.[18] EATOP [19] is an upcoming initiative to make an Eclipse-based implementation of the EAST-ADL meta-model.

An XML-based exchange format, EAXML, allows tools to exchange EAST-ADL models. The EAXML schema is autogenerated from the EAST-ADL metamodel according to the same principles as the AUTOSAR ARXML schema. Currently, the exchange format is supported by the EAST-ADL prototype of Mentor Graphics VSA, MetaEdit+ and SystemWeaver. For UML tooling, it is possible to exchange models using XMI, subject to the XMI compatibility between tools.

Similar approaches

[edit]

References

[edit]
  1. ^ The EAST-ADL Architecture Description Language for Automotive Embedded Software, Cuenot, P. et al., Chapter 11 in Model-Based Engineering of Embedded Real-Time Systems [3-642-16276-2; 3-642-16277-0] Ed. Holger Geise et al., pp297-388, 2010
  2. ^ a b EAST-ADL Association EAST-ADL Association
  3. ^ a b MAENAD project description[permanent dead link‍]
  4. ^ Biehl, Matthias; Sjöstedt, Carl-Johan; Törngren, Martin, "A Modular Tool Integration Approach – Experiences from two Case Studies" 3rd Workshop on Model-Driven Tool & Process Integration (MDTPI 2010), 2010-06-16, Paris, France
  5. ^ "ATESST2 home page". Archived from the original on 2008-06-15. Retrieved 2008-04-26.
  6. ^ UML Profile for AUTOSAR
  7. ^ "EAST-ADL Tooling" (PDF). Archived from the original (PDF) on 2011-07-23. Retrieved 2010-09-02.
  8. ^ "EAST-EEA project: ITEA project reference 00009" (PDF). Archived from the original (PDF) on 2011-07-21. Retrieved 2010-09-02.
  9. ^ ATESST project: 6th FWP project reference 026976
  10. ^ ICT project reference ATESST2 project: 224442
  11. ^ MAENAD project: ICT project reference 260057
  12. ^ CESAR
  13. ^ TIMMO-2-USE
  14. ^ MetaEdit+
  15. ^ "SystemWeaver". Archived from the original on 2011-09-18. Retrieved 2011-11-22.
  16. ^ Papyrus UML
  17. ^ MagicDraw UML
  18. ^ H. Grönniger, J. Hartmann, H. Krahn, S. Kriebel, L. Rothhardt, and B. Rumpe, “View-Centric Modeling of Automotive Logical Architectures,” Tagungsband des Dagstuhl-Workshops Modellbasierte Entwicklung Eingebetteter Systeme (MBEES), 2008.
  19. ^ https://code.google.com/a/eclipselabs.org/p/eclipse-auto-iwg/wiki/EATOP EATOP
  20. ^ Modeling with SystemDesk (proprietary)
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=EAST-ADL&oldid=1215778543"