Advances in Automotive System Modeling: EAST-ADL (Part 1): Page 2 of 6

May 16, 2013 //By DeJiu Chen, KTH; Lei Feng, Volvo; Henrik Lönn, Volvo; Juha-Pekka Tolvanen, MetaCase
Advances in Automotive System Modeling: EAST-ADL (Part 1)
For decades developers of automotive embedded systems have enjoyed the benefits of modeling. Models have not only served communication and gaining better understanding but are also used to prototype, analyze, simulate and test the developed systems. With dedicated generators it has also been possible to produce production-quality software code from the models. Typical cases of code generation are various control-engineering solutions and infotainment systems with HMIs.
For example, the modelling infrastructure and general approach is aligned with AUTOSAR. Compared to other system description languages for embedded systems, EAST-ADL takes a more holistic view on the system development lifecycle and addresses explicitly some key engineering issues, while maintaining a fine-grained traceability across a variety of models for the purposes of information management. As demonstrated in this article, this promotes a more systematic approach to architecture design. For the analytical leverage, EAST-ADL models can be integrated with a wide range of existing modeling technologies and tools. For the final product realization, the system architecture specification made with EAST-ADL is typically realized by more detailed software and hardware solutions (like AUTOSAR, JasPar or in-house architectures).

Example: Starting with features and requirements

Let's next inspect EAST-ADL and its application using a small example: a Regenerative Braking System with ABS. A typical starting point for the development is features of the vehicle – as illustrated in Figure 2. Here the feature model of EAST-ADL defines the braking system under development by capturing the feature configuration and in particular shows some of the key braking related vehicle functionalities and their dependencies: for instance the optional AdvancedBraking feature is specialized by ABSBraking and by optional ESPBraking, but if ESPBraking feature is chosen also ABSBraking feature is then required. While this example shows just a few vehicle features, feature models can specify and manage the content of each vehicle in relation to the entire product line by addressing the features and their relationships such as in terms of feature dependency and exclusion. For the purpose of customization, market aspects such as models and markets can be organized in a feature model and traced to more technical features (e.g. the choices of particular hardware platforms).

Figure 2. Feature model (partial) related to Regenerative Breaking with ABS. For higher resolution click here .

In parallel to the composition of vehicle features, we may start with

Design category: 

Vous êtes certain ?

Si vous désactivez les cookies, vous ne pouvez plus naviguer sur le site.

Vous allez être rediriger vers Google.