AS5506A-2009 发布历史

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 language is applicable to systems that are: ? real-time@ ? resource-constrained@ ? safety-critical systems@ ? and those that may include specialized device hardware. This standard defines the core AADL that is designed to be extensible. While the core language provides a number of modeling concepts with precise semantics including the mapping to execution platforms and the specification of execution time behavior@ it is not possible to foresee all possible architecture analyses. Extensions to accommodate new analyses and unique hardware attributes take the form of new properties and analysis specific notations that can be associated with components. Users or tool vendors may define these extensions. Extensions may be proposed as annex documents for inclusion in the AADL standard. This standard does not specify how the detailed design or implementation details of software and hardware components are to be specified. Those details can be specified by a variety of software programming and hardware description languages. The standard specifies relevant characteristics of the detailed design and implementation descriptions@ such as source text written in a programming language or hardware description language@ from an external (black box) perspective. These relevant characteristics are specified as AADL component properties@ and as rules of conformance between the properties and the described components. This standard does not prescribe any particular system integration technologies@ such as operating system or middleware application program interfaces or bus technologies or topologies. However@ specific system architecture topologies@ such as the ARINC 653 executives@ can be modeled through software and execution platform components. AADL can be used to describe a variety of hardware architectures and software infrastructures. Integration technologies can be used to implement a specified system. The standard specifies rules of conformance between AADL system architecture specifications and actual system implementations. The standard was not designed around a particular set of tools. It is anticipated that systems and software tools will be provided to support the use of AADL.

AS5506A-2009由SAE - SAE International 发布于 2009-01-01，并于 2009-01-22 实施。

AS5506A-2009 发布之时，引用了标准

AS5506A-2009的历代版本如下：

2009年01月01日 AS5506A-2009

非常抱歉，我们暂时无法提供预览，您可以试试：免费下载 AS5506A-2009 前三页，或者稍后再访问。

注意：点击下载后，生成下载文件时间比较长，请耐心等待......

标准号: AS5506A-2009
发布日期: 2009年01月01日
实施日期: 2009年01月22日
废止日期: 无
中国标准分类号: /
国际标准分类号: /
发布单位: SAE - SAE International
引用标准: 333

适用范围: 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 language is applicable to systems that are: ? real-time@ ? resource-constrained@ ? safety-critical systems@ ? and those that may include specialized device hardware. This standard defines the core AADL that is designed to be extensible. While the core language provides a number of modeling concepts with precise semantics including the mapping to execution platforms and the specification of execution time behavior@ it is not possible to foresee all possible architecture analyses. Extensions to accommodate new analyses and unique hardware attributes take the form of new properties and analysis specific notations that can be associated with components. Users or tool vendors may define these extensions. Extensions may be proposed as annex documents for inclusion in the AADL standard. This standard does not specify how the detailed design or implementation details of software and hardware components are to be specified. Those details can be specified by a variety of software programming and hardware description languages. The standard specifies relevant characteristics of the detailed design and implementation descriptions@ such as source text written in a programming language or hardware description language@ from an external (black box) perspective. These relevant characteristics are specified as AADL component properties@ and as rules of conformance between the properties and the described components. This standard does not prescribe any particular system integration technologies@ such as operating system or middleware application program interfaces or bus technologies or topologies. However@ specific system architecture topologies@ such as the ARINC 653 executives@ can be modeled through software and execution platform components. AADL can be used to describe a variety of hardware architectures and software infrastructures. Integration technologies can be used to implement a specified system. The standard specifies rules of conformance between AADL system architecture specifications and actual system implementations. The standard was not designed around a particular set of tools. It is anticipated that systems and software tools will be provided to support the use of AADL.