From AadlWiki

Revision as of 19:59, 17 January 2017 by Peter.Feiler (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

For committee members, please check the dedicated AADL committee wiki.


Next Standard Meetings

For information about AADL Standards meetings please see AADL meetings.

Presentation Materials

Presentation for the users days is available here:

Remote meeting

We organize periodic remote meeting to discuss modeling patterns and use of AADL. Please read the page dedicated to these AADL remote meetings if you plan to join/attend.

An SEI 2010 Technology Highlight

AADL and Model-Based Engineering as a SEI Research & Technology Highlight Jan 2010.

SAE ARD 5296

Requirements for the Avionics Architecture Description Language (AADL), SAE ARD 5296.

In 2002 the name was changed to Architecture Analysis & Design Language since it is not designed specifically for Avionics systems.

Contact Peter Feiler at the SEI for a copy - SAE does not seem to sell it anymore and some European company wants 95 Euros for it.


The SAE Architecture Analysis & Design Language (AADL), Peter H. Feiler (author, editor), SAE International Document AS-5506B, Revised Sept 2012. Referred to as AADL V2.1.

This document defines the architecture model semantics for AADL together with its textual and graphical syntax. AADL is aimed at modeling the architecture of distributed real-time embedded systems, cyber-physical systems, and other mission-critical software-reliant systems.


This standard defines a language for describing both the software architecture and the execution platform architectures of performance-critical, embedded, real-time systems; the language is known as the SAE Architecture Analysis & Design Language (AADL). An AADL model describes a system as a hierarchy of components with their interfaces and their interconnections. Properties are associated to these constructions. AADL components fall into two major categories: those that represent the physical hardware and those representing the application software. The former is typified by processors, buses, memory, and devices, the latter by application software functions, data, threads, and processes. The model describes how these components interact and are integrated to form complete systems. It describes both functional interfaces and aspects critical for performance of individual components and assemblies of components. The changes to the runtime architecture are modeled as operational modes and mode transitions.

The changes relative to AADL V2 are summarized in What's New in V2.1 and documented in detail in Approved Errata to AADL V2. There is also an AADL V2.1 Syntax Card.

If you are unfamiliar with AADL V2, please read What's New in V2 of AADL.

SAE AADL AS5506B Errata and AADL V2.2

Approved errata for AADL V2.1 have been updated in the AADL V2.1 standard document with change tracking. It can be found on the AS2C working Area. You will need to log into

NOTE: This document has passed ballot to become the AADL V2.2 standard document and will be published shortly. This document is the baseline for the development of AADL V3 (see below).

AADL V2.1 errata are now maintained at AADL V2.1 Errata.

Summaries of the errata can be found at

Approved errata since publication of AADL V2.1

Open errata since publication of AADL V2.1

Closed errata approved since publication of AADL V2.1

The most recent and any new errata are maintained at AADL V2.1 Issue Tracking


We have started an effort to develop AADL V3. Major topics include compositional interfaces, configuration support, bindings as explicit concept, virtual memory, and a number of other issues. To track this development see AADL V3 Discussion Area. You will find presentation material, discussion issues, and a wiki.

SAE AADL Annexes AS5506/1

The SAE Architecture Analysis & Design Language (AADL) First Annex Collection, Peter H. Feiler (co-author, editor), SAE International Document AS-5506/1, June 2006.

This standard document contains a collection of approved AADL Annex documents: the Graphical AADL Notation Annex, the AADL Meta model and XML/XMI Interchange Format, the Language Compliance and Application Program Interface Annex, and the Error Model Annex.


This document contains three annexes to the SAE AS5506 Standard - the SAE Architecture Analysis and Description Language. The first annex, Annex A Graphical AADL Notation, defines a set of graphical symbols for the graphical AADL notation. These graphical symbols can be used to express relationships between components, features, and connections in an AADL model. Graphical AADL diagrams are legal in accordance with the AADL core standard if the AADL model being presented graphically is legal and if the correct graphical symbols are used. For example, a graphical editor is not permitted to create a connection whose source and destination are not connected. Graphical presentations of AADL models are permitted to show subsets of legal AADL models. For example, property values may be entered through a property sheet or dialog box. The figures in this annex present different views of an AADL model. These views are not prescriptive, but intended to illustrate possible views and layouts.

The second annex, Annex C AADL Meta Model and Interchange Formats, defines the AADL meta model and XML-based interchange formats for AADL models. The AADL meta model defines the structure of AADL models, i.e., an object representation of AADL specifications that corresponds to a semantically decorated abstract syntax tree. The object representation of AADL models can be manipulated programmatically through an API. The object representation of AADL models can also be persistently stored as XML documents in a standard interchange format. This permits different tools that support the AADL XML schema [XML 2001] or XMI meta model specification [XMI 2003] to interoperate on AADL models. Both the XML schema and the XMI meta model specification for the AADL are derived from the AADL meta model, thus, the two representations are consistent with the meta model.

The third annex, Annex D Language Compliance and Application Program Interface, defines language-specific rules for source text to be compliant with an architecture specification written in AADL. While the AADL is source text language independent, this annex provides guidelines for users to transition between AADL models and source text written in Ada [ISO 1995, IEEE 2001] and source text written in C [ISO 1999]. This annex recommends the use of an Application Program Interface (API) between the application software and the execution environment to facilitate the use of mixed language application source code modules in a common execution environment.

The forth annex, Annex E Error Model Annex, defines features to enable the specification of redundancy management and risk mitigation methods in an architecture, and enable qualitative and quantitative assessments of system properties such as safety, reliability, integrity, availability, and maintainability. This annex defines a sublanguage that can be used to declare error models within an error annex library and associate them with components in an architecture specification. This annex also defines a sublanguage that may be used within an error annex clause within a core AADL standard implementation declaration.

SAE AADL Annexes AS5506/2

The SAE Architecture Analysis & Design Language (AADL) Second Annex Collection, SAE International Document AS-5506/2, Jan 2011.

This document consists of three annexes to the SAE AADL standard that

  • The Data Modeling Annex provides guidance on a standard way of associating data models expressed in other data modeling notations such as UML or ASN.1 with architecture models expressed in AADL,
  • The Behavior Annex enables modeling of component and component interaction behavior in a state-machine based annex sublanguage, and
  • The ARINC653 Annex provides guidance on a standard way of representing ARINC653 standard compliant partitioned embedded system architectures in AADL models.

Published in 2015: SAE AADL Annexes Volume AS5506/1A

The SAE Architecture Analysis & Design Language (AADL) Third Annex Collection has been published as Volume 1A SAE AADL Annex Volume 1A.

  • The Error Modeling Annex V2 is a revision of the original Error Modeling Annex published in 2006 with improvements based on user feedback.
  • The Code Generation Annex outlines support for generation of runtime systems from AADL models.
  • The ARINC653 Annex V2 Updated ARINC653 Annex to reflect a new release of the ARINC653 Standard.

In the Works: SAE AADL Annexes AS5506/4

The SAE Architecture Analysis & Design Language (AADL) additional annexes are in the works. For details about the progress see AADL User Days.

  • The Constraint Annex defines a common constraint language for use with other annexes and for specification of verification constraints. See AADL User Day Feb 2013 for a presentation and a working draft.
  • The BLESS Annex is an extension to the Behavior Annex and provides for specification of assertions and invariants that take into account time. A proof tool which transforms behaviors having proof outlines into inductive proofs is available to verify such specifications. See Media:BLESS_Annex_Standard_Document.pdf for a working draft of the annex document (4/4/2016), and Media: BLESSSyntaxCard.pdf for its syntax card.
  • The Assertion Annex defines a temporal logic used by BLESS for declarative behavior specification and annotation of states and actions to form proof outlines. It is being considered for standardization ahead of BLESS because it is more stable, and can be used to define behavior contracts, or be used by other tools. Standardization will allow other standards like AAMI/UL 2800 to reference it to define behavior contracts. See Media:Assertion_Annex_Standard_Document.pdf for a working draft of the annex document (4/4/2016), and Media: AssertionSyntaxCard.pdf for its syntax card.
  • The Hybrid Annex defines continuous-time behavior for environments, sensors, and actuators using differential equations. See Media:Hybrid_Annex_draft0.10.doc for proposed annex document text.
Personal tools