標(biāo)準(zhǔn)號(hào)：SAE AS 5506/1-2006
中文標(biāo)準(zhǔn)名稱：SAE體系結(jié)構(gòu)分析和設(shè)計(jì)語(yǔ)言(AADL)附加卷1:附加A:圖解AADL符號(hào)、附加C:AADL Meta模型和交換格式、附加D:語(yǔ)言依從和應(yīng)用程序界面、附加E:錯(cuò)誤模式附加
英文標(biāo)準(zhǔn)名稱：SAE Architecture Analysis and Design Language (AADL) Annex Volume 1: Annex A: Graphical AADL Notation, Annex C: AADL Meta-Model and Interchange Formats, Annex D: Language Compliance and Application Program Interface Annex E: Error Model Annex
標(biāo)準(zhǔn)類型：V37
發(fā)布日期：2006/6/1 12:00:00
實(shí)施日期：1999/12/31 12:00:00
中國(guó)標(biāo)準(zhǔn)分類號(hào)：V37
國(guó)際標(biāo)準(zhǔn)分類號(hào)：49.140
引用標(biāo)準(zhǔn)：IEEE 1003.5b-1999;IEEE 1003.13-2003;ISO/IEC 8652-1995;ISO/IEC 9899-1999;ISO/IEC TR 15942-2000;RTCA DO-254-2000;SAE ARP 4761-1996;SAE AS 5506-2004;MIL-HDBK-217F;RTCA DO-178D
適用范圍：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 XMLbased 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.