Capability Pattern: Generic method pattern with bottom-up flow
The generic method pattern reflects a methodological structure that is imposed on all use case-specific method patterns. It makes the bottom-up flow of timing information explicit.
DescriptionWork Breakdown StructureTeam AllocationWork Product Usage
Relationships
Context
Description

This method pattern describes the idea of “Abstracting Timing Properties” on a lower level of abstraction in order to use them on a higher level of abstraction. The results of this abstraction are used as additional (optional) input work product for the task “Attach timing properties”.

Figure 1 shows a simplified view of the methodology with regard to this approach. The task “Transform Timing Properties” on the current level of abstraction transforms the timing properties’ values of a solution created on the lower level of abstraction into values of timing properties that can be used at the current level of abstraction. The transformed timing properties, including their values, are an optional input work product for the task “Attach Timing Requirements to Solution” conducted on the current level of abstraction. The idea behind this is that values of timing properties that are obtained during later phases of the development process can be used on higher levels of abstraction respectively in earlier phases of the development process. This is an important capability in order to support iterative development processes.

 

 

Figure 1 - Abstracting Timing Properties

 

Properties
Event Driven
Multiple Occurrences
Ongoing
Optional
PlannedYes
Repeatable
Illustrations