Task: Annotate time budget influencing properties with known or assigned values
In the task Annotate time budget influencing properties with known or assigned values, the time budget influencing properties identified previously are completed with time values when possible.
Relationships
InputsMandatory: Optional:
  • None
External:
  • None
Outputs
Main Description

In the task Annotate time budget influencing properties with known or assigned values, the time budget influencing properties identified previously are completed with time values when possible. This activity falls into one of three categories:

1.    The information can be retrieved from a lower abstraction level

2.    The property is already known from another context

3.    The property is something that we impose on the system

The first category reuses information that has already been derived for the parts of the solution that has already been developed bottom-up at a lower abstraction level. The lower-level properties cannot directly be copied to the current abstraction level, since the solution structure looks different and has less detail. The events on the lower abstraction level therefore have to be mapped to events on the current abstraction level. Once this is done, the delay constraint itself can be copied and contain the same information as it did on the lower abstraction level, with the difference that it is associated with the current-level events.

The second category tries to find information from an external source, for example another project where the same function has been used.

Other timing properties of the system do not follow from higher abstraction levels or can be found by a particular analysis method, but they are rather design decisions. In the third category, the developer may assign timing properties, based on his experience, in such a way that he believes that the system will perform timingly. Previously known properties, belonging to categories 1 and 2, must be considered. The assigned time budget influencing properties will be verified in a separate task and possibly be revised in a later iteration.

 

Properties
Predecessor
Multiple Occurrences
Event Driven
Ongoing
Optional
Planned
Repeatable
More Information