1 Scope of Document
This document specifies requirements on State Management. State Management implements interfaces of State Manager on the AUTOSAR Adaptive Platform, because State Management is highly project specific and therefor to be im
plemented by the project itself.
It needs to be customized according to the project. This means that it is difficult for platform software vendors to provide off-the-shelf goods.
2 Acronyms and Abbreviations
<-> Execution Management
The element of the AUTOSAR Adaptive Platform responsible for the ordered startup and shutdown of the AUTOSAR Adaptive PlatformandAdaptive Applications.
Start and stop the platform and User application as needed
<->State Management
The element defining modes of operation for AUTOSAR Adaptive Platform. It allows flexible definition of functions which are active on the platform at anygiven time.
<->Function Group
A Function Group is a set of coherent Modelled Processes which need to be controlled consistently. Depending on the state of the Function Group, processes (related to the Modelled Processes) are started or terminated. Modelled Processes can belong to more than one Function Group State (but at exactly one Function Group). "MachineState" is a Function Group with a predefined name, which is mainly used to control Machine lifecycle and processes of platform level Applications. Other Function Groups are sort of general purpose tools used (for example) to control processes of user level Applications.
It can be used to control the start and stop of user processes in different states
<-> Function Group State
The element of State Management that characterizes the current status of a set of (functionally coherent) user-level Applications. The set of Function Groups and their Function Group States is machine specific and are configured in the Machine Manifest
3.1Functional Overview
Only the interfaces and abstract functionality will be defined, because State Management is highly project specific.
EM, PHM and SM are the main safety relevant functional clusters of the AUTOSAR Adaptive Platform. Consequently, their development may require certain processes to be followed - as recommended in ISO26262 and, for instance, RS_SAF_21301 [4]. A safety argumentation for the AUTOSAR Adaptive Platform, describing functional safety measures and use-cases is provided through Explanation of Safety Overview [5].
Specific to the requirements, but did not scan the specific requirements proposed.
For example: SM should provide a standardized interface, SM should be able to control the status of APP, SM should be able to control APP or Functional Group to establish a communication channel, etc. Relatively empty.