This part of the specification defines the structural constructs used in EAST-ADL2. The structural view of a model focuses on the static structure of the instances of the system being modeled and their static
relationships. This includes the internal structure of such instances just like their external interfaces through which they can be connected to communicate with each other, by exchanging data or sending messages.
Additionally, data types are defined in this part of the specification for the exchanged data, and for
parameters, are. These definitions conditions are specified that hold for the instances during their lifetime at the execution of the system . For the design of systems of arbitrary size and complexity, the possibility of hierarchical structuring of the instances is provided in the language.
EAST-ADL2 abstraction layers are used to allow reasoning of the features on several levels of abstraction.
Note, however, that the abstraction levels are only conceptual; the modeling elements are organized
according to the artifacts which may span more than one of these layers. Where applicable, entities on
different abstraction levels are related with a realization association to allow traceability analysis.
Traceability can also be deduced from the requirements structure.
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| EAST-ADL-2.0-Specification_2008-02-29.pdf | application/pdf | 658.43 KB | English | DOWNLOAD! |
Provides definitions
Cover images
Introduction
The purpose of the EAST ADL Domain Model is to capture the software and electronics architecture with enough detail to allow modeling for documentation, design, analysis and synthesis. These activities require system descriptions on several abstraction levels, from top level user features down to tasks and communication frames in CPUs and communication links. Moreover, the activities also involve the expression of non-structural aspects of the system under development, e.g. requirements, behavior and validation and verification.