This use case describes the TIMMO-2-USE Generic Method Pattern that is the basis for all steps to be taken during the course of a phase that deals with creating, altering, processing, and utilizing timing information.
The generic method pattern reflects a methodological structure that is imposed on all use case-specific method patterns. This means that all use case-specific tasks and work products have to relate to the corresponding tasks and work products in this generic method pattern. This relation is of type many to one. Many use case-specific tasks are related to one task in the generic method pattern. The relation for work products is analogous.
Important Assumptions
The following assumptions shall be kept in mind when reading the following paragraphs:
1. All tasks can be repeated [an arbitrary number of times].
2. A sequence of tasks can be repeated [an arbitrary number of times].
3. A role or roles performing a task have access to all artifacts that are a) available at the beginning of a phase, and b) created by tasks during the course of the phase. For all details about the work product dependencies refer to the EPF model [4].
4. The term “Timing Property” is used in such a way that it refers to the timing property and its value.
|