Task: Attach timing requirements to solution
Based on the created solution the timing requirements are formulated in a way that is suitable for further processing on the current level of abstraction.
Disciplines: Generic method pattern tasks
Relationships
Main Description

Based on the created solution the timing requirements are formulated in a way that is suitable for further processing on the current level of abstraction. Timing requirements that are carried over from a previous phase must be transformed and attached to the solution architecture accordingly, such that they are “compatible” with the timing model (and the timing properties) on the current level of abstraction.

In a nutshell: Timing requirements are expressed using events, event chains, and timing constraints that are imposed on these events and event chains. Events refer to locations, usually ports, in a solution model at which the occurrences of the events are observed; and event chains specify a causal relationship between events and their temporal occurrences. During every phase a solution model is created based on the requirements and the solution model created in the previous phase. An event specified in the previous phase referring to an observable location in the corresponding solution model possibly has to be transformed or mapped into an event referring to an observable location in the solution model created during the current phase. This transformation has to be performed for all events and event chains, and especially the values of the timing requirements imposed on event chains.

This task must be performed for alternative solutions that evolve from the task “Create Solution”.

Illustrations
More Information