SNIP_ADAPTIVE_CAN_FIGURE_Figure_7_4_EXECUTIONMANAGEMENT

Figure 7.4: Execution dependencies on Non-reporting Process • Non-reporting Process (and Self-terminating Process ) A references FG1:Running. This Process is started first (as it doesn’t have any Execution Dependencies configured) and automatically enters Running Process State as per [SWS_EM_01402]. • Companion Process B is started after Non-reporting Process A (please note that A and B are also standard AUTOSAR Processes) enter Running state. Process B can use project specific method to assess if Process A is fully functional and signal this to Execution Management by reporting (or not) kRunning state. • Process C is started when (and only when) Process B enters Running Process State (i.e. reports kRunning). Please note this Execution Dependency will work independently from reporting / non-reporting configuration of Process C.