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
Relationships
Context
Description

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.

In some cases, the requirement violation cannot be resolved at the same abstraction level as where the violation was found. It might be needed to acquire more detailed design information from a lower abstraction level, or to give feedback to a higher abstraction level that there might be a risk of a violated requirement.

Figure 1 illustrates the process.

 

 

Figure 1. Process for the use case Revise erroneous timing information

 

Properties
Event Driven
Multiple Occurrences
Ongoing
Optional
PlannedYes
Repeatable