Welcome to our development portal
This website provides help to use our AADL toolsuites (RAMSES, AADL BA Front-End, Ocarina) and other software designed for it (PolyORB-HI, POK...). You'll find useful information to install and use them. Our research at TELECOM ParisTech is focused on system generation from architectural description. We use the AADL to describe distributed real-time embedded systems and automatically generate code from AADL models.
AADL Models Edition
AADL-BA front end for OSATE 2
Using the standardized Behavior Model Annex of AADL V2 (called AADL-BA), a software architect specifies the behavior of AADL components thanks to dedicated state machines. The project AADL-BA front end for OSATE 2 provides an editor for behavior specifications, integrated into the Open Source AADL Tool Environment (OSATE). OSATE is the reference development environment for AADL, developped by the SEI.
Model Transformation
RAMSES
RAMSES (Refinement of AADL Models for Synthesis of Embedded Systems) is a model transformation and code generation tool that produces C code for ARINC653-compliant operating systems and OSEK-compliant operating systems. RAMSES interfaces with OSATE2 and proposes a command-line interface to OSATE2. RAMSES proceeds by refinement insofar as it produces a simplified version of an AADL model as an intermediate step towards code generation. This simplified model includes a behavior annex subclause that expresses the behavior resulting from the expansion of AADL components.
Code Generation
Ocarina
Ocarina is the core of our AADL toolsuite. It features an AADL V1 & AADL V2 parser, code generators targetting PolyORB, PolyORB-HI (C and Ada/Ravenscar) and POK. Besides, it includes gateway to model checkers (colored or timed Petri Nets) and WCET analysis of AADL model and associated runtime code using Bound-T.
Ocarina plug-in for Eclipse/Topcased
The ocarina plug-in is a plug-in for Eclipse/topcased that ease the use of Ocarina inside Eclipse/Topcased. Using it, you can design your models inside Eclipse/Topcased and automatically generate, build and run systems inside your modeling toolsuite. It supports our AADL runtimes PolyORB-HI-C, PolyORB-HI-Ada and POK.
AADL Runtime Environment
PolyORB-HI-C
PolyORB-HI-C is an AADL runtime written in C. It is used by Ocarina generated code to use system primitives and manage its resources. It is POSIX-compliant and fits with many operating systems (Linux, RTEMS and so on). It is fully POSIX.
- Presentation
- Download and installation
- Use PolyORB-HI-C, frequently asked questions
- Use Simulink with PolyORB-HI-C
PolyORB-HI-Ada
PolyORB-HI-Ada is our AADL runtime written in Ada/Ravenscar?. It provides the same and more services as PolyORB-HI-C and is compliant with most used operating systems and some embedded real-time systems such as RTEMS or ORK.
POK and ARINC653-related stuff
POK is our AADL partitioned runtime. It ensures space and time isolation and fit with the needs of embedded real-time systems. You can gather more information about this website on its official webpage. This page provides information about the code generator for POK. We also discuss the modeling of ARINC653 annex. TELECOM ParisTech? is involved in the ARINC653 annex and provides tools for validation, verification and implementation purposes.
- Presentation of the POK project?
- Use POK with Ocarina
- Validation regarding ARINC653 and MILS requirements
- ARINC653 annex and tool support
- ARINC653 examples with AADL
- Experiments of the ARINC653 annex described in the Aerotech09 paper
Model Checking
REAL
REAL is a language for constraints declarations on AADL (and AADL V2) language. REAL can be used either to evaluate some aspects of the model (such as memory occupation), or to verify that hard constraints are respected. It allows to have a fully AADL-centric developpement chain, from project specifications to effective system description.
Past projects
There is a list of past projects. Unfortunately, we dont have the time to maintain all our projects and some of them are leaved unmaintained. This page contains a list of past projects.
Case studies and examples
Case studies
Examples
All our examples are shipped in software releases. You can find a description of these examples on this page.
Contribute
Community
Contributors
Our research projects involve a team of several people. There is a list of who is or was involved in our projects :
- Etienne Borde
- Fabien Cadoret
- Julien Delange
- Sébastien Gardoll
- Olivier Gilles
- Jérôme Hugues
- Gilles Lasnier
- Laurent Pautet
- Xavier Renault
- Thomas Vergnaud
- Bechir Zalila
