SNIP_ADAPTIVE_CAN_FIGURE_Figure_7_13

Figure 7.13: Example configuration for state transition Before we specify how internals of a state transition works, let’s consider an example configuration illustrated in figure Figure 7.13. As we can see Execution Dependencies that spans outside of a Function Group and moreover of a single Function Group State are forbidden. The dependency from Process B (inside Function Group FG_B) to Process A (inside Function Group FG_A) is forbidden, as it would introduce hidden dependencies between Function Groups that are not visible to State Management . If system configuration requires this kind of dependencies, please see [12] for advice on how to configure them. Dependencies outside of a single Function Group State definition are forbidden, as they would result in starting a Process that is not configured to run in the given State. For more information on Execution Dependencies see Section 7.3.4.1 ([SWS_EM_01001] and [constr_1689] [3]). Please note that Process B has different Execution Dependencies in Function Group State ABC and Function Group State XYZ. This configuration requires existence of two different startup configurations ( StateDependentStartupConfig), which in turns will mandate Process B restart if State Management request Function Group State change from ABC to XYZ. This is enforced by [SWS_EM_02251].