EAST-ADL

Last updated

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.

Contents

Overview

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:

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

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

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

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:

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

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

Project nameTimeBudgetEAST-ADL VersionSpecification DownloadSupport by research departments of following vehicle manufacturers(OEMs)
EAST-EEA [8] 1.7.2001 - 30.6.200440 M€EAST-ADL Version 1.0No download available after project had finishedBMW, Daimler, Fiat, PSA (Peugeot/Citroen), Renault, Volvo, Valeo
ATESST [9] 1.1.2006 - 31.3. 20083.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. 20103.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. 20134.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

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

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

Related Research Articles

Unified Modeling Language general-purpose, developmental, modeling language in the field of software engineering

The Unified Modeling Language (UML) is a general-purpose, developmental, modeling language in the field of software engineering that is intended to provide a standard way to visualize the design of a system.

A modeling language is any artificial language that can be used to express information or knowledge or systems in a structure that is defined by a consistent set of rules. The rules are used for interpretation of the meaning of components in the structure.

Model-driven architecture (MDA) is a software design approach for the development of software systems. It provides a set of guidelines for the structuring of specifications, which are expressed as models. Model-driven architecture is a kind of domain engineering, and supports model-driven engineering of software systems. It was launched by the Object Management Group (OMG) in 2001.

Metamodeling

A metamodel or surrogate model is a model of a model, and metamodeling is the process of generating such metamodels. Thus metamodeling or meta-modeling is the analysis, construction and development of the frames, rules, constraints, models and theories applicable and useful for modeling a predefined class of problems. As its name implies, this concept applies the notions of meta- and modeling in software engineering and systems engineering. Metamodels are of many types and have diverse applications.

Architecture description languages (ADLs) are used in several disciplines: system engineering, software engineering, and enterprise modelling and engineering.

Domain-specific modeling (DSM) is a software engineering methodology for designing and developing systems, such as computer software. It involves systematic use of a domain-specific language to represent the various facets of a system.

The Shlaer–Mellor method, also known as Object-Oriented Systems Analysis (OOSA) or Object-Oriented Analysis (OOA) is an object-oriented software development methodology introduced by Sally Shlaer and Stephen Mellor in 1988. The method makes the documented analysis so precise that it is possible to implement the analysis model directly by translation to the target architecture, rather than by elaborating model changes through a series of more platform-specific models. In the new millennium the Shlaer–Mellor method has migrated to the UML notation, becoming Executable UML.

AUTOSAR is a worldwide development partnership of automotive interested parties founded in 2003. It pursues the objective of creating and establishing an open and standardized software architecture for automotive electronic control units (ECUs). Goals include the scalability to different vehicle and platform variants, transferability of software, the consideration of availability and safety requirements, a collaboration between various partners, sustainable utilization of natural resources, and maintainability throughout the whole "Product Life Cycle".

The Architecture Analysis & Design Language (AADL) is an architecture description language standardized by SAE. AADL was first developed in the field of avionics, and was known formerly as the Avionics Architecture Description Language.

Model-driven engineering (MDE) is a software development methodology that focuses on creating and exploiting domain models, which are conceptual models of all the topics related to a specific problem. Hence, it highlights and aims at abstract representations of the knowledge and activities that govern a particular application domain, rather than the computing concepts.

ATLAS Transformation Language programming language

ATL is a model transformation language and toolkit developed and maintained by OBEO and AtlanMod. It was initiated by the AtlanMod team. In the field of Model-Driven Engineering (MDE), ATL provides ways to produce a set of target models from a set of source models.

Executable UML is both a software development method and a highly abstract software language. It was described for the first time in 2002 in the book "Executable UML: A Foundation for Model-Driven Architecture". The language "combines a subset of the UML graphical notation with executable semantics and timing rules." The Executable UML method is the successor to the Shlaer–Mellor method.

Systems Modeling Language general-purpose modeling language for systems engineering applications

The Systems Modeling Language (SysML) is a general-purpose modeling language for systems engineering applications. It supports the specification, analysis, design, verification and validation of a broad range of systems and systems-of-systems.

Eclipse Modeling Framework modeling framework and code generation facility for building tools and other applications based on a structured data model

Eclipse Modeling Framework (EMF) is an Eclipse-based modeling framework and code generation facility for building tools and other applications based on a structured data model.

Knowledge Discovery Metamodel (KDM) is a publicly available specification from the Object Management Group (OMG). KDM is a common intermediate representation for existing software systems and their operating environments, that defines common metadata required for deep semantic integration of Application Lifecycle Management tools. KDM was designed as the OMG's foundation for software modernization, IT portfolio management and software assurance. KDM uses OMG's Meta-Object Facility to define an XMI interchange format between tools that work with existing software as well as an abstract interface (API) for the next-generation assurance and modernization tools. KDM standardizes existing approaches to knowledge discovery in software engineering artifacts, also known as software mining.

Modeling and Analysis of Real Time and Embedded systems also known as MARTE is the OMG standard for modeling real-time and embedded applications with UML2.

A metaCASE tool is a type of application software that provides the possibility to create one or more modeling methods, languages or notations for use within the process of software development. Often the result is a modeling tool for that language. MetaCASE tools are thus a kind of language workbench, generally considered as being focused on graphical modeling languages.

The GENIVI Alliance is a non-profit automotive industry alliance committed to driving the broad adoption of open source, In-Vehicle Infotainment (IVI) software and providing open technology for the connected car. The GENIVI Alliance was founded on March 2, 2009 by BMW Group, Delphi, GM, Intel, Magneti-Marelli, PSA Peugeot Citroen, Visteon, and Wind River Systems.

TRAK

TRAK is a general enterprise architecture framework aimed at systems engineers based on MODAF 1.2.

Capella (engineering) software environment for model-based systems engineering

Capella is an open-source solution for model-based systems engineering (MBSE). Hosted at polarsys.org, this solution provides a process and tooling for graphical modeling of systems, hardware or software architectures, in accordance with the principles and recommendations defined by the Arcadia method. Capella is an initiative of PolarSys, one of several Eclipse Foundation working groups.

References

  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. 1 2 EAST-ADL Association EAST-ADL Association
  3. 1 2 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)
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.