The timing requirements originated from the previous phase, the Analysis Phase, are transformed into timing requirements that correspond with the solution created in the current phase, the Design Phase. In the example the given timing requirement, the event chain and timing constraint in the upper part of Figure 1, are transformed into an event chain and timing requirement imposed on the solution created in the current phase.
The result of the transformation is
Scope |
Latency Timing Constraint |
Minimum |
Maximum |
HF “Sensor” … HF “Actuator” |
125 ms, -15 ms, +15 ms |
110 ms |
140 ms |
Figure 1: A simple example to demonstrate the use of the TIMMO-2-USE Generic Method Pattern and transforming timing requirements between levels of abstraction.
Observation. On the first view it seems obvious that the event chain/timing constraint specified on the higher level of abstraction (Analysis Level) is transformed in a one-to-one manner to an event chain/timing constraint on the current level of abstraction (Design Level).