try another color:
try another fontsize: 60% 70% 80% 90%

Objectives

Several projects have been and are being launched to enhance, evaluate, and demonstrate the benefits of MARTE and other standards. The analysis of the ADAMS partners is that the current entering point for ensuring successful deployment of the MARTE standard is a focussed effort to disseminate knowledge on MARTE and to coordinate feedback and update proposition on MARTE from the practice. This is why the instrument chosen to push the dissemination of MARTE was “Support Action”. By structuring the ADAMS project around the two target industrial domains, automotive and avionics, the ADAMS project will more specifically commit itself to achieve its objectives. The main objective of ADAMS is to favour the exploitation of the MARTE standard in domains having requirements similar to those that have triggered the standard elaboration process four years ago. Two domains are particularly active to standardize modelling approaches and deploy them on component-based middleware technologies: automotive and avionics. They share a large set of requirements with MARTE and thus are particularly relevant for focused dissemination and critical analysis of the current standard version. In addition, ADAMS will work on promoting MARTE on the one hand to the whole embedded systems community. On the other hand, ADAMS will also use all developed results to influence the related standardisation bodies, in order to close the feedback loop by organizing and delivering the feedback gathered from the automotive and avionics domains in the form of recommendation actions towards both OMG for MARTE evolution and domain initiatives and standards for convergence and evolution towards MARTE. To ensure a pertinent dissemination to both automotive and avionics domains, the specific work performed within ADAMS is organised around two working groups of experts from the corresponding domain. These working groups will deal with the concerns of the three following technical points of view: • The ways to specify non-functional properties. • The ways to describe application architecture and deployment. • The ways to specify the execution and communication infrastructure (middleware & OS).