SNIP_ADAPTIVE_ADAPTIVEMETHODOLOGY_SECTION_2_2_2_2_3_Workflow

2.2.2.2.3 Workflow Design signal oriented communication between Classic and Adaptive Platform Service Instance To Signal Mapping Service Interface Description Define a signal-based ServiceInterface (SignalBasedServiceInterfaceDeployment) Map Signals to Services Map SignalBasedEventDeployment to ISignalTriggerings Map SignalBasedFieldDeployment to ISignalTriggerings Map SignalBasedMethodDeployment to ISignalTriggerings Map ServiceInstance to PortPrototype System Description OEM Service Instance To Signal Mapping Set 1..* «nesting» 1..* «input» 1 «input» «nesting» 0..* «nesting» 0..* «nesting» 0..* «nesting» «nesting» «performs» +Service Interface Designer 0..* «nesting» «output» 1..* Figure 2.11: Design signal oriented communication Activity Design signal oriented communication between Classic and Adaptive Platform Package AUTOSAR Root::M2::Methodology::Methodology Use Cases::Adaptive Platform::Architecture and Design::Communication Brief Description Design signal oriented communication between CP and AP Description Usually, Adaptive Applications communicate between each other in a service oriented manner. There is even an option that applications deployed to an Adaptive Platform and Classic Platform communicate in a service oriented way via SOME/IP. If the counterpart on a Classic Platform ECU, however, communicates only in a signal-based way, a Signal-to-Service translation is needed. This activity encompasses the description of the mapping of signals to elements of a particular ServiceInterface. It will be the base for the configuration of the translation application. Relation Type Related Element Mult. Note Consumes Service Interface Description 1..* Description of the Service Interfaces which communicate to CP in a signal-oriented manner Consumes System Description