SNIP_ADAPTIVE_CAN_FIGURE_Figure_3_14

Figure 3.14: Example for the application of a ServiceInterfaceMapping [TPS_MANI_01022] Concept behind ServiceInterfaceMapping⌈ The concept behind the definition of a ServiceInterfaceMapping is that all elements of the sourceServiceInterface are required to have a counterpart of the same kind (ServiceInterface.event, ServiceInterface.field, or ServiceInterface.method) and with the identical shortName.⌋(RS_MANI_00017) The regulation stated in [TPS_MANI_01022] is exemplified in Figure 3.14. Please note that the creation of a ServiceInterfaceMapping is considered an atomic step, it is unlikely that such a ServiceInterfaceMapping is partially created and then later finished by a different party . After all, there are mutually exclusive ways to specify the mapping, and any creator of a partial mapping of ServiceInterfaces could not be sure which of the alternatives apply for a specific pairing of one ServiceInterface with another without already knowing the other ServiceInterface (in which case the mapping can already be completed). Therefore, there is no need to set the lower multiplicity of the references to ServiceInterface to 0. 67 of 270 — AUTOSAR CONFIDENTIAL — Document ID 713: AUTOSAR_TPS_ManifestSpecification