BehaviorDescription

The Behavior Description Annex provides the language support for allowing a more precise declaration of various behavior concerns, such as assumed or implied by requirements and quality constraints, assigned to system environment, functions and components, or test procedures. It also constitutes the basis for consolidating such concerns in a common system design context and a gateway for supporting model transformations from EAST-ADL to external methods and tools for ensuring the analytical leverage. <br/><br/>In particular, this architectural language support would give the following benefits.<br/>1. The modeling support for behavior constraint descriptions would allow the system developers to refine textual requirements by formalizing the statements of use case and operational scenarios and thereby to elicit, validate, and derive related concerns on the basis of particular architectural design assumptions.<br/><br/>2. As a part of the overall language support for managing the traceability of requirement satisfactions, the descriptions of behavior constraints can be used to specify the required conformity of IP-protected black-box functions or components. This constitutes a basis for having a more precise reasoning about the compositional effect (i.e. the compositionality and composability).<br/><br/>3. By managing all behavioral specifications in a common architectural context, EAST-ADL behavior descriptions provide the fundamental support for assessing the correctness and completeness of refinements of system artifacts across multiple levels of abstraction for final code generation.<br/><br/>4. By having all behavior specifications in the same context of architecture design, this language package also provides a basis for capturing the design of advanced mode logics such as in regard to fault-tolerance and quality-of-services. For such advanced features, the ability of describing, predicting and managing the system wide effects of modes is of critical importance. This means that one should be able to relate system modes control with system operational situations, application behaviors, the schemes of execution and resource deployment, etc.<br/><br/>5. When targeting error specifications, the behavior descriptions can be used to refine the definitions of estimated failure modes by providing a precise specification of faulty conditions in value and time and capturing the transitions between nominal states and errors.<br/>