wiki:AADL

Version 27 (modified by alan, 15 years ago) ( diff )

--

TOC(WikiStart, news, projects, technologies, AADL, hood, stood, adele, labassert)

AADL

The AADL

The Architecture Analysis and Design Language (AADL) has been standardized by the SAE, avionics systems division, under number AS 5506. last version of the standards has been issued in January 2009. The AADL is a textual and graphical language that can be used to design and analyze the software and hardware architecture of performance-critical real-time systems. An AADL model describes a system as a hierarchy of components with their interfaces and their interconnections.

AADL components

AADL components belong to predefined categories which precise semantics is defined by the standard.

  • Execution platform components represent the hardware parts of the system which may be: Processors, Buses, Memories and Devices.
  • Application software components describe the applicative model running on the system in terms of: Processes, Threads, Subprograms and Data.

AADL components have a type that describes their functional interface and one or several implementations defining their internal structure and in particular their subcomponents and subcomponents interactions.

AADL features and connections

The purpose of AADL features is to specify the functional interface of a component. A feature can be an incoming outgoing port (event, data or event data), a subprogram entry point or data access point. Features are end for AADL connections.

AADL properties

Default semantics of AADL constructs is described by the standard, and appear in the models either implicitly (run-time semantics) or explicitly with predefined properties. Additionally, it is possible to enrich the semantics of AADL models by defining user-defined property sets that can apply to AADL component categories, features and connections.

AADL Extensions

The AADl standard comes with a set of extensions that enlarge the scope of the language for more particular usages. Some of these Annexes have already been published and others are still being studied by the AADL committee.

  • AADL meta-model and XMI interchange.
  • UML profile through MARTE
  • Error Model Annex
  • Behaviour Annex
  • Data Modeling Annex
  • Code Generation Annex
  • ARINC 653 Annex

Verifiable Model Based Engineering

One of the main benefits of using the AADL for modeling critical systems is that this language has been developed in the purpose of being verified. The standard specifies numerous legality rules that can be checked automatically by tools to insure that all the model is correctly formed according to the AADL semantics. Moreover, a common architectural description of the system can carry a variety of information that may be processed separately in order to provide analysis reports in various areas:

  • Schedulability Analysis
  • Latency Analysis
  • Safety Analysis
  • Resource Consumption
  • ...

AADL tool chains

Since the first release of AADL in 2004, many modeling and verification tools have been developed. Ellidiss has become a leader in this area. Main available AADL tools are:

  • OSATE: (Open Source) Eclipse plugin, textual editor and analysis tools, developed by the Software Engineering Institute.
  • ADELE: (Open Source) Eclipse plugin for TOPCASED, graphical editor and code generation, developed by Ellidiss.
  • STOOD: (Commercial) Standalone tool, graphical editor, analysis tools, code and documentation generation, developed by Ellidiss.
  • OCARINA: (Open Source) Standalone tool, verification and code generation, developed by Telecom Paristech.
  • Cheddar: (Open Source) Standalone tool, real-time performance analysis, developed by the University of Brest.

All these tools can either import or export AADL models, which enables the realization of complete cost-effective tool-chain.

Attachments (6)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.