Each TADL guide can be seen as Requirements or Property
This guide describes how TADL2 distinguishes a requirement from a property.
Relationships
Related Elements
Main Description

Short Description

A constraint that refines a Requirement is a requirement. The Requirement has a Satisfy relationship from the element in the model as is seen in the example below:

Figure 1. Example model with tracing between abstraction levels.

The Requirement is set to be satisfied by a model of the solution. Note also how requirements on different abstraction levels are traced by the Derive Requirement relationship.

The different roles of the TADL2 constraints during the modeling process becomes clear when different model elements are marked by the corresponding tasks of the Generic Method Pattern:

Figure 2. Generic Method Pattern tasks, numbered.

 

Figure 3. Example model in one abstraction level. The different modeling elements are numbered to identify in which GMP task they are modeled.

 

Task and modeling elements created:

1)    Timing Requirements: the EAST-ADL Requirements expressed textually have been modeled in the abstraction level above.

2)    Refine, Introduce & Validate Requirements: Refinement is done by creating new requirements on this level of abstraction and tracing them to requirements on the higher abstraction level using the DeriveRequirement relationship. This is a part of the requirements engineering step and does also include the modeling of the verification method to be used. This is modeled by VVCase, VVProcedure with intended outcome. The VVCase is set to verify the requirement.

3)    Create Solution: In this example from the design level there is a functional design architecture and a hardware design architecture. The HDA is set as the target for the VVCase and the FDA is set as the subject. Elements in the FDA are allocated on the HDA. The structural model of the solution is set to satisfy the requirement.

4)    Attach Timing Requirements to Solution: Timing events, event chains and TADL2 constraints are modeled. Constraints can refine requirements to make a formalization of the textual requirements.

5)    Create Timing Model:  Additional constraints are modeled to facilitate the analysis.

6)    Analyze Timing Model: During analysis the resulting properties are modeled and connected to the VVActualOutcome.

7)    Verify Solution against Timing Requirement: The actual outcome and the intended outcome are compared.

8)    Specify & Validate Timing Requirements: Additional requirements can be modeled to be refined by constraints.

9)    Timing Requirements: are now available for the next level of abstraction.

 

Links to TADL2 concepts

TADL2 Concepts

·         All constraints, see supporting material

EAST-ADL Concepts:

·         Requirement

·         Refine

·         Verify

·         VVCase

 

Abstraction level specific list of applicable events

See supporting material Abstraction level specific list of events.

 

Context Specific Example

---

 

 

More Information