Execution time (Worst-case, Best-case, Simulated, Measured)
When a task performing some computation or communication is activated, the time it actually uses the resource on which it is mapped (that is, excluding preemption and blocking times) is called its execution time.
Relationships
Main Description

Short Description

When a task performing some computation or communication is activated, the time it actually uses the resource on which it is mapped (that is, excluding preemption and blocking times) is called its execution time. This time may vary from one execution to the next, for example because different branches in the code are taken (e.g. due to different input data).

ñ  Worst-case: defines an upper bound on the possible execution times of a task.

ñ  Best-case: defines a lower bound on the possible execution times of a task.

ñ  Simulated: defines bounds on the executions times of a task which are considered in a specific simulation.

ñ  Measured: defines bounds on the executions times of a task which have been measured during a given execution.

 

Links to TADL2 concepts

A constraint on an execution time is represented using a dedicated constraint called ExecutionTimeConstraint.

 

Abstraction level specific list of applicable events

Activation, Preemption, Resume, Termination events

 

Context Specific Example

---

 

More Information