This example provides an overview on how the search for causes and corrective actions could be organized for the requirement violation Exceeded time budget. It should be pointed out that the charts are in no way exhaustive, and should only be regarded as inspiration.
The example is organized in several charts, one chart per abstraction level or AUTOSAR view. The top-level node captures the requirement violation. Below the top node there is a hierarchy of possible causes for the requirement violation. The leaf nodes capture either a corrective action or a redirection to another abstraction level (i.e. another chart).
The charts have the form of a decision tree, which in the end concludes one distinct corrective action. It is however important to understand that each design and requirement violation is unique and that it therefore is difficult, not to say impossible, to provide an exhaustive recipe on how to revise the system. The decision trees presented here are hence incomplete in the sense that there may exist more causes and corrective actions than those listed in the charts. In addition, it is necessary to get an understanding of all branches in the cause hierarchy, or in the worst case even leaf causes (causes at the lowest level), before deciding on which actions to take. It may even be the case that several corrective actions need to be taken to extinguish a requirement violation.
Figure 1 provides a legend for the different nodes in the charts.
Figure 1 Legend for revision charts
Figure 2 Revise exceeded time budget at vehicle level

Figure 3 Revise exceeded time budget at analysis level

Figure 4 Revise exceeded time budget at design level
Figure 5 Revise exceeded time budget in the VFB view

Figure 6 Revise exceeded time budget in the SWC view
Figure 7 Revise exceeded time budget in ECU view
Figure 8 Revise exceeded time budget in System view
Figure 9 Revise exceeded time budget in Operational level
|