The MAENAD project has reached milestone 7 and completed 2.5 years. The project has received one new member, ARCCORE, and will be extended until January 2014. A public workshop is planned autumn 2013.
Language and profile update
At the end of March 2013, the new EAST-ADL domain model version M2.1.11 has been released by the MAENAD project. It will be presented to the EAST-ADL Association for approval as the next official EAST-ADL version 2.1.11 in May 2013. Until then, minor corrections and fixes may be performed depending on the feedback from language implementers.
A number of implementations are currently available for EAST-ADL. Implementations within the commercial quality modeling tools MetaEdit+ and SystemWeaver, an open source implementation of the language based on Eclipse EMF/Sphinx provided by the EATOP initiative, and an implementation as a UML2 profile that can be used in the tool Papyrus UML. These implementations are currently available for EAST-ADL 2.1.10 and will be updated to 2.1.11 over the coming weeks and months.
In order to provide a seamless data exchange across these different implementations, a standard XML schema definition (XSD) is provided, defining the so-called EAXML format. This exchange format is currently supported by several of the above implementations and for most parts of the EAST-ADL domain model 2.1.10; this support will be updated to 2.1.11 and further extended over the coming months.
The new language version includes a number of consolidation refinements to the core of EAST-ADL (e.g. data types, values, expressions) and integrates the language amendments proposed by the TIMMO-2-USE European research project into the overall language. Some extension packages have received major updates, esp. the behavior extension. Also, several refinements have been made to keep the EAST-ADL domain model aligned to recent versions of AUTOSAR, e.g. the recent AUTOSAR changes to the inheritance hierarchy of software component types, prototypes, and ports have been reconstructed in EAST-ADL's inheritance of function types, prototypes, and ports.
Links to selected EAST-ADL implementations:
- MetaEdit+: http://www.metacase.com
- SystemWeaver: http://systemite.se
- EATOP: eclipse-auto-iwg
- UML2 Profile / Papyrus UML: http://www.papyrusuml.org
A new release of MAENAD Analysis Workbench, containing different analysis tools and plugins was released this milestone. It will be further developed throughout the project; a new release is planned before summer.
EAST-ADL and HiP-HOPS (a state of the art dependability analysis and optimisation tool extended in MAENAD) are now supporting automatic decomposition of Automotive Safety Integrity Levels (ASILs), which have been adopted as part of the automotive safety standard ISO 26262. The ASILs assigned to safety goals at system level within an EAST-ADL model can now be allocated and decomposed by HiP-HOPS into ASIL assignments for components of the model. A Brake-By-Wire case study is in progress.
For optimisation, an evolved prototype tool architecture ‘OptiPAL’ with an addon for the EAST-ADL modelling tool EPM authored by the Technical University of Berlin was developed. It is intended to support product line optimisation over the coming months, but dependability analysis with architectural optimisation and cost analysis as possible objective evaluations can already take place via HiP-HOPS.
On the timing analysis part, besides the transformation between EAST-ADL timing information and MARTE models for schedulability analysis which is already implemented in the timing analysis tool ‘Qompass’, the corresponding plug-in has been enhanced to directly analyse EAST-ADL models and a work to support the BBW model is in progress.
Concerning behavioural analysis, a behaviour description annex was developed and concepts for native behaviour constraints have been formalised and integrated into the language domain model. Novel analysis algorithms based on transformations of behavioural descriptions to fault trees and optimised Markov models were released together with enhanced compositional synthesis algorithms. These are envisaged to feed into tool development work like integration with HiP-HOPS and to link behavioural analysis tools like SPIN and UPAAL with MetaEdit+.
The MAENAD methodology is modeled in the Business Process Model and Notation (www.omg.org/spec/BPMN/2.0/). It follows one to one the abstraction level principle of the EAST-ADL language, starting from the most abstract level, the vehicle phase, to the most concrete level, the implementation phase. Each abstraction level has been structured in 7 steps according to the Generic Method Pattern (GMP) identified together with the TIMMO-2-USE project.
Moreover, the methodology has been modeled in 4 “swimlanes”; the core development methodology leading a developer through the EAST-ADL language is modeled in the “Core” lane. Specific aspects that extend the core methodology are separated to additional lanes. In fact the complete methodology includes also the functional safety swimlane, the timing swimlane and one swimlane dedicated to FEV. The swimlane related to the Functional Safety Process has been modeled in compliance with the ISO 26262 safety life-cycle, by detailing each process sub-phase in terms of inputs, outputs and activities to be performed. The FEV swimlane has been modeled by including the design activities that shall be performed according to the standards and regulations related to FEV development.
More on EAST-ADL
There is a white paper, describing the EAST-ADL modeling concepts, methodology and relations to other modeling languages. An example model is also included in this white paper. It is available on the maenad.eu website, under ”MAENAD Presentations”: http://www.maenad.eu/presentations.html
The EAST-ADL Association is open to anyone involved in EAST-ADL modeling or definition. The next meeting is in May, where new members will be accepted.
There is also the LinkedIn EAST-ADL group for discussions, and an EAST-ADL channel on YouTube.
The MAENAD Consortium