Refine Your Search

Search Results

Viewing 1 to 11 of 11
Standard

Architecture Analysis & Design Language (AADL)

2020-09-30
WIP
AS5506D
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 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.
Standard

SAE Architecture Analysis and Design Language (AADL) Annex Volume 5: Annex A: ARINC653 Annex, Annex C: Code Generation Annex, Annex E: Error Model Annex

2020-09-30
WIP
AS5506/5
(1) This document contains three annexes to the SAE AS5506B Standard - the SAE Architecture Analysis and Description Language. (2) The first annex, the Error-Model Language extends the AADL core language with a state machine-based notation. This notation allows for specification of different types of faults, fault behavior of individual system components, fault propagation affecting related components in terms of peer to peer interactions and deployment relationship between software components and their execution platform, aggregation of fault behavior and propagation in terms of the component hierarchy. The notation also allows for specification fault mitigation strategies expected to be implemented in the health monitoring and fault management component of the actual system – also known as Fault Detection, Isolation, and Recovery (FDIR).
Standard

Architecture Analysis & Design Language (AADL)

2017-01-18
CURRENT
AS5506C
(10) AADL specifications may be processed manually or by tools for analysis and generation. This section documents additional requirements and permissions for determining compliance. Providers of processing method implementations must document a list of those capabilities they support and those they do not support. NOTE: Notes emphasize consequences of the rules described in the (sub)clause or elsewhere. This material is informative.
Standard

Architecture Analysis & Design Language (AADL)

2012-09-10
HISTORICAL
AS5506B
(10) AADL specifications may be processed manually or by tools for analysis and generation. This section documents additional requirements and permissions for determining compliance. Providers of processing method implementations must document a list of those capabilities they support and those they do not support. NOTES: Notes emphasize consequences of the rules described in the (sub)clause or elsewhere. This material is informative.
Standard

Architecture Analysis & Design Language (AADL)

2009-01-20
HISTORICAL
AS5506A
(10) AADL specifications may be processed manually or by tools for analysis and generation. This section documents additional requirements and permissions for determining compliance. Providers of processing method implementations must document a list of those capabilities they support and those they do not support. NOTES: Notes emphasize consequences of the rules described in the (sub)clause or elsewhere. This material is informative.
Standard

ARCHITECTURE ANALYSIS & DESIGN LANGUAGE (AADL)

2004-11-05
HISTORICAL
AS5506
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 architecture model defined in AADL describes the properties and interfaces of components. Components fall into two major categories: those that represent the execution platform and those representing the application. The former is typified by processors, buses, and memory, the latter by application software modules. 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.
X