SNIP_ADAPTIVE_CAN_FIGURE_Figure_3_23

Figure 3.23: Modeling of the ServiceInterfaceMapping [TPS_MANI_01002] Semantics of meta-class ServiceInterfaceMapping⌈ In order to sort out a potentially different motivation between the definition of • ServiceInterfaces explicitly designed for VFB-based communication and • ServiceInterfaces explicitly designed for network-based communication meta-class ServiceInterfaceMapping is available to map • (fine-grained) ServiceInterfaces for the VFB-communication to • (coarse-grained) ServiceInterfaces for network communication. ⌋(RS_MANI_00017) [TPS_MANI_01032] Usage of ServiceInterfaceMapping⌈ The ability to apply a ServiceInterfaceMapping can be used in two different ways: • It is possible to derive a dedicated AdaptiveApplicationSwComponentType that implements the mapping functionality . A SwComponentPrototype derived from this so-called facade software-component would expose PortPrototypes for each of the ServiceInterfaces. Other SwComponentPrototypes could then “connect” to the PortPrototypes typed by ServiceInterfaces referenced in the role sourceServiceInterface. 107 of 602 — AUTOSAR CONFIDENTIAL — Document ID 713: AUTOSAR_TPS_ManifestSpecification