Capability Pattern: Revise erroneous timing information
As opposed to most other use cases, the starting point of this use case is not to start constructing or refining a system. The starting point is rather when the system has already been constructed, and we want to find out if its timing behavior conforms to its requirements. The use case is activated when verification has revealed a requirement violation, which needs to be corrected. The methodology of this use case thus starts with the GMP task Verify timing requirements and continues with an iteration (which according to the assumption of the GMP is implicit) where the solution is modified to comply with the requirement.
DescriptionWork Breakdown StructureTeam AllocationWork Product Usage
Workflow

Activity diagram: Revise erroneous timing information Identify timing fault Find cause for timing requirement violation Resolve violation at current abstraction level Reverify the validated requirement Transform timing requirement violation from higher abstraction level Transform timing requirement violation from lower abstraction level as a risk
Work Breakdown