Problem statement
When developing time-critical systems, it is almost inevitable that some unintended behavior passes through the development process. It is then of great importance that the verification techniques can catch the unintended behavior so that the designer may have a good chance to revise it.
This use case provides a generic pattern on how a violation of a timing requirement is detected and corrected. The pattern should then be combined with another use case, related to the type of requirement violation, describing a straight-forward error-free development process that provides the detailed hints on how to accurately develop a system with respect to the problem addressed by that use case (and the requirement violation in question).
The generic pattern is moreover exemplified with a set of decision trees related to the time budgeting problem. The example demonstrates, for each abstraction level, how to decompose a specific type of timing requirement violation and how to proceed to identify the cause of the violation, and also what measure could be taken to revise the system so that the requirement finally holds.
|