Abstract
In this work, we propose an approach for the verification of the AADL architecture. This approach is based on Model Driven Engineering (MDE) and assisted by a toolchain. Indeed, we define a source meta-model for AADL and a target meta-model for the timed automata formalism; we define a transformation process in two steps: the first is a Model2 Model transformation which takes an AADL Model and produces the corresponding timed automata model. The second transformation is a Model2 Text transformation which takes a timed automata model and generates a text in ta-format code. This code is accepted by the Uppaal toolbox. A case study has been developed to show the feasibility and validity of the proposed approach.
Highlights
The MDE [1] Model Driven Engineering approach provided through its concepts a complete framework to develop a complex system
We propose an approach for the verification of the AADL architecture
We have presented an approach assisted by tools to specify and validate AADL architectures
Summary
The MDE [1] Model Driven Engineering approach provided through its concepts a complete framework to develop a complex system. The AADL [2] (Architecture Analysis and Design Language) language is an ADL (Architecture Description Language) for real-time embedded systems. In this type of system, the temporal properties take an important place in development [3]. The AADL language focuses on the architectural aspects: it allows description of components and their connections, but does not deal with their behavior implementation or semantics of the data handled. We chose the formalism of timed automata [4] as target formalism for the verification of AADL models This is justified by their ability to represent temporal constraints [4]. We close the paper with conclusion and future works
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
