SNIP_ADAPTIVE_CAN_FIGURE_Figure_3_24

Figure 3.24: Example for the application of a ServiceInterfaceMapping The regulation stated in [TPS_MANI_01022] is exemplified in Figure 3.24. 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. 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 Base ARObject, AtpBlueprint , AtpBlueprintable, Identifiable, MultilanguageReferrable, PortInterfaceMapping, Referrable Aggregated by PortInterfaceMappingSet.portInterfaceMapping Attribute Type Mult. Kind Note composite ServiceInterface ServiceInterface 0..1 ref This represents the composite ServiceInterface. sourceService Interface ServiceInterface * ref ServiceInterface that is mapped into the composite ServiceInterface. Table 3.35: ServiceInterfaceMapping [constr_10136]{DRAFT} Multiplicity of reference in the role ServiceInterfaceMapping.compositeServiceInterface ⌈For each ServiceInterfaceMapping, the reference in the role compositeServiceInterface shall exist at the time before the generation of the ara API starts .⌋()