Background and Version History. 35 2.8.4 Key Features 35 2.9 Variability Resolution 36 2.9.1 Objectives 36
Background and Version History. The AUTOSAR gateway was built on results from EDONA and ATESST2 projects. The first version has been released at M12 and then it had been ported to the new Papyrus MDT platform and 2.1.9 EAST-ADL profile version. A second version of the AUTOSAR gateway has been released at M24. In this version the transformation towards the AUTOSAR implementation architecture relies on an AUTOSAR UML profile (subset of AUTOSAR centred on relevant templates: software component, system and ECU resource namely). As a result, the transformation from EAST-ADL design architecture to AUTOSAR vehicle design architecture/system configuration produces UML profiled models. AUTOSAR gateway implements also export functionality from AUTOSAR-UML profiled models to AUTOSAR XML.
Background and Version History. Let us be reminded that at the beginning of the MAENAD project the analysis engine should have been provided as a third-party tool. On the other hand, after EDONA and ATESST2, CEA worked on the implementation of schedulability analysis algorithms as part of its research activities (not included in the MAENAD project) in its own XXXXX-based plug-in called Qompass. This timing analysis support was not completely compliant with timing analyses identified as best-suited for EAST-ADL design models (Section 2.2). Moreover, in order to directly analyse EAST-ADL models, a transformation between EAST-ADL profile models and entry models for Qompass was needed. During year 2 the Qompass timing support has been adapted/enhanced in order to support EAST- ADL design-level timing analyses. An EAST-ADL/Qompass transformation has been developed as well. A new version of the Timing Analysis plug-in, has been released at M24 embedding these new features. At the end of year 2, the input model for the Qompass tool assumed only linear event chains, where each chain contained a linear sequence of functions and where neither functions nor stimuli could belong to more than one event chain. In order to support the analysis of the brake-by-wire (BBW) system, an extension was needed, as the BBW owns functions belonging to multiple event chains. With the latest release, this extension has been implemented and now Qompass can run on the BBW model.
Background and Version History. Within the ATESST2 project, a gateway was developed to provide input/output facilities of models in Simulink and Papyrus/Eclipse. The gateway has two parts: 1. a GUI plugin to the MATLAB/Simulink environment, which aids the user in creating models that conform to the format that is needed to being able to convert it into an EAST-ADL model, and 2. an Eclipse plugin, which can convert between the intermediate format of Simulink models and EAST-ADL models. In particular, the GUI plugin for Simulink converts standard Simulink subsystems to system reference blocks, and tags them for conversion to EAST-ADL by putting them in a “FunctionTypes”-library, and assigning a unique ID, to allow bi-directional exchange and updates. Import works the other way around, the function types and prototypes of an EAST-ADL architecture model are imported to empty library blocks in the “FunctionTypes”-library, and instances of them respectively. For the model exchange, the plugin also converts the MATLAB/Simulink models into a custom Ecore- based format. In MEANAD, two Simulink model transformation plugins have been developed for the MetaEdit+ environment, for a more effective EAST-ADL language verification&validation. The first plugin, developed by MetaCase, parses an EAST-ADL architecture model and creates the .mdl-files of corresponding Simulink models directly. The second plugin, developed by KTH, relies on Matlab API for automatic creation of Simulink and Stateflow models. For an EAST-ADL model, this plugin considers both the architecture specifications and the behaviour constraint annotations.
Background and Version History. Within the ATESST and ATESST2 project, a gateway was developed to transform EAST-ADL error models in and Papyrus/Eclipse to HiPHOPS. Within the MAENAD project, this Papyrus plugin is updated to support EAST-ADL models built using the UML profile version 2.1.10. It uses the concepts defined in the EAST-ADL error-model, but also other language constructs from the FDA level. Within the MAENAD project, two new gateways to HiP-HOPS that have been developed: 1. a plugin for MetaEdit+, 2. a plugin for EPM. The first plugin is mainly used for investigating a full- fledged coverage of the EAST-ADL dependability modelling concepts. The second plugin serves as the basis of ASIL decomposition export to HiP-HOPS.
Background and Version History. A proposal for an EAST-ADL optimization architecture was developed over the course of the second year of MAENAD, building upon initial ideas from the meeting in York May 2011. In the third project year, the architecture was then further refined to support product line optimization and the distinction of product line versus design space variability, mainly by introducing the concepts of optimization representatives in addition to optimization candidates. This led to the architecture shown below:
Background and Version History. As of MAENAD milestone MS7, the ASIL allocation has been implemented in HiP-HOPS and related modelling and editing support has been provided in EPM. The implementation has been tested on smaller models and a larger model immediately taken from industrial practice (from Continental). The support of ASIL decomposition at the end of project year 2 was already on a level of what was aimed for in the MAENAD DoW, and it was possible to perform decomposition of ASILs via HiP-HOPS. Apart from minor fixes and corrections, no additional work has been conducted during year 3 (in accordance to planning). Longer term development work by XXX on improved ASIL decomposition algorithms is still underway, but lies beyond the MAENAD project objectives.
Background and Version History. Within the MAENAD project, an EAST-ADL language package, referred to as Behavior Constraint Description Annex, is developed to allow an explicit description of various behavioral concerns in EAST-ADL. On the basis of a formal semantics, several transformations from EAST-ADL to behavior analysis tools have been developed, including UPPAAL, SPIN and Stateflow. The tool demonstration is based on UPPAAL transformation mainly due to its rich semantics and user friendliness. A preliminary tool prototype for the SPIN transformation has however also been developed.
Background and Version History. The Analyser was initially defined by VTEC and implemented in a project with Chalmers University of Technology. It was subsequently refined and ported to EATOP for EAST-ADL 2.1.11 and 2.1.12. The EATOP Analyzer will evolve beyond MAENAD to support additional analysis concerns and to refine the presentation of results.
Background and Version History. The plug-in is currently still in an early development stage; while most of the core variability resolution functionality has been implemented and successfully tested against test models, several development concerns are currently still ongoing. Once all core concerns and secondary functionality has been implemented and the plug-in has been exhaustively tested, it is intended to be ported to the EAST-ADL Tool Platform EATOP. Once this step has been achieved, the plug-in shall be extended by additional functionality in order to access CVM based feature-link variability support, thus providing widespread support for the entire EAST-ADL variability vocabulary. This step will then provide a basis for extensive artifact-level optimization efforts, possibly including representative-based artifact-level optimization of not-yet- configured product line models.
