SNIP_ADAPTIVE_CAN_FIGURE_Figure_3_22

Figure 3.22: Example for the application of a ServiceInterfaceMapping The regulation stated in [TPS_MANI_01022] is exemplified in Figure 3.22. 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). [TPS_MANI_01003]{DRAFT} Limitation of the applicability of ServiceInterfaceMapping⌈The applicability of the ServiceInterfaceMapping is limited to cases where the shortNames of the elements of the compositeServiceInterface are unique in the context of the compositeServiceInterface.⌋(RS_MANI_- 00017) Class ServiceInterfaceMapping Package M2::AUTOSART emplates::AdaptivePlatform::ApplicationDesign::ServiceInterfaceMapping Note Specifies one ServiceInterfaceMapping that allows to define that a ServiceInterface is composite of several other ServiceInterfaces. Tags: atp.recommendedPackage=ServiceInterfaceMappings ▽