Once a timing requirement violation has been identified, the task Find cause for timing requirement violation investigates potential diagnostic information trying to find out one or several possible causes of the problem. The task of finding causes is to a large extent dependent on the experience of the developer.
For common types of requirement violations, an organization could build a set of decision trees, which elaborates on possible causes and corrective actions for those types of requirement violations. In a link below, such an approach is illustrated on an example of the requirement violation exceeded time budget.