AUTOSAR Gateway. Procedures AUTOSAR Gateway (ARGateway) is designed for the generation of an AUTOSAR compliant architecture from an EAST-ADL2 model. The generation process is twofold, namely from EAST- ADL2 model generation of an AUTOSAR model takes place and from this model, ARXML file can be generated. This is shown on the Figure 5-46. These two processes can be triggered separately by the user. Naturally, an AUTOSAR model first has to be generated. In order to represent the EAST-ADL2 specification, UML profile for the EAST-ADL2 is used. The same solution holds for the modelling of the AUTOSAR architectures. Therefore the first transformation is a transformation between the model expressed with the EAST-ADL2 UML profile and the model expressed with the AUTOSAR UML profile. Generation of a model based on the AUTOSAR UML profile first, instead of direct generation of an ARXML file from the EAST-ADL2 model (which was the approach used in the previous implementation of an AUTOSAR Gateway) has a significant advantage. Namely, the designer can manually change the final design of an implementation level working directly on the models. Current version of the AUTOSAR Gateway features with a predefined approach for the generation of a software architecture. In fact the generation of a software architecture, i.e. software component prototypes and their internal behaviour, poses the main question. In our predefined approach, software architecture is mostly generated based on the compositional structure of a functional specification. Non-elementary functions are transformed into composite software components. Each elementary function is transformed into the runnable entity and runnable entities are grouped into the software components in a way in which elementary functions were grouped into the non-elementary functions. Of course if two elementary functions were grouped into the same non-elementary function, but allocated to different nodes, their corresponding runnable entities will not state a part of the same internal behaviour. Previous implementation of an AUTOSAR Gateway was following simpler approach where for each elementary function, one atomic software component with one runnable entity have been generated. Figure 5-46. AUTOSAR Gateway twofold process. Evaluation Results AUTOSAR Gateway has been tested on the EAST-ADL2 model representing the Brake-by-Wire. The results are shown on a set of below figures. Result of a first step of a transformation this is a UML model stereot...
AUTOSAR Gateway. The AUTOSAR gateway builds on results from EDONA and ATESST2 projects to provide an enhanced transformation from EAST-ADL design architecture to AUTOSAR compliant software architecture, based on the ARTOP framework, which is an implementation of common base functionality for AUTOSAR development tools, available free of charge for AUTOSAR members [5]. The transformation also takes into account allocations and hardware description architecture from the EAST-ADL model to generate a tentative topology for the AUTOSAR architecture.
AUTOSAR Gateway. AUTOSAR is an open and standardized automotive software architecture, jointly developed by manufacturers, suppliers and tool developers. EAST-ADL complements AUTOSAR in several ways. The EAST-ADL metamodel is specified according to the same rules of the AUTOSAR metamodel, and AUTOSAR elements can be referenced by EAST-ADL elements. The result is a compositional metamodel where functional architecture aspects and software architecture aspects coexist, and are capable of enriching AUTOSAR with timing constraints, safety constraints and support for safety analysis, support for requirements engineering, variability management. The goal of the AUTOSAR gateway is to provide an effective means for automatic model transformation from an EAST-ADL design architecture to an AUTOSAR software architecture, supporting the engineers during the design phases. More precisely, the AUTOSAR gateway takes a XXXXX-enriched EAST-ADL model as input, i.e. an EAST-ADL design function architecture and hardware description architecture, together with a software architecture using XXXXX constructs (i.e. RtUnits). In this enriched model, each EAST- ADL elementary function is allocated to the XXXXX software components which themselves are mapped to hardware elements (the same kind of description is made for the Timing analysis see above). From this, an Autosar architecture is generated which tries to export as much information as possible. Essentially the core transformation is to map EAST-ADL each elementary function to a Runnable, then use the XXXXX software architecture description and allocation to regroup Runnables in different software components. Depending on the allocation of software component on hardware elements, different communication mechanisms are generated in the Autosar model, e.g. inter-variable mechanism for collocated elements. The resulting Autosar model is provided as a file in Autosar xml format, using the ARTOP implementation of Autosar in Eclipse. Note that use of this and development with the ARTOP framework is open for AR members only. It is intended in the course of the MAENAD project to define an Autosar UML profile so that modelling of an Autosar architecture could be feasible within EAST-ADL models in the Modeling Workbench. When available, the AR gateway will be adapted so that parts of the transformations will also be available within the modelling workbench, to complement an EAST-ADL UML model with AR elements directly in the UML model. Key points for t...
AUTOSAR Gateway. The AUTOSAR gateway builds on results from EDONA and ATESST2 projects to provide an enhanced transformation from the EAST-ADL design architecture to AUTOSAR vehicle architecture design and initial system configuration. The gateway is based on the ARTOP framework, which is an implementation of common base functionality for AUTOSAR development tools, available free of charge for AUTOSAR members [5]. The transformation takes as input the EAST-ADL Design Level with functional description, hardware description and allocation information and generates a tentative AUTOSAR software architecture, a hardware topology and mapping constraints (coming from EAST-ADL allocation information). The generation of the tentative software architecture is based on mappings between EAST-ADL functions and AUTOSAR software components/runnables that fit in the EAST-ADL Implementation Level.
AUTOSAR Gateway
