ADAPTIVE
Modul: can
Rolle: heuristic
Konfidenz: 80%
SNIP_ADAPTIVE_CAN_FIGURE_Figure_3_20
Wortlaut
Figure 3.20: Modeling of the ServiceInterfaceMapping [TPS_MANI_01002]{DRAFT} 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]{DRAFT} Usage of ServiceInterfaceMapping⌈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. This means that the PortPrototype typed by the ServiceInterface referenced in the role compositeServiceInterface is used for external communication. PassThroughSwConnectors can be used to describe in the modeled facade CompositionSwComponentType which “fine-grained” Ports are combined to a “coarse-grained” Port that is used for network communication. The mapping of Service Interface elements of the “fine-grained” Ports to the Service Interface elements of the “course-grained” Port is described with the ServiceInterfaceMapping or rather ServiceInterfaceElementMapping.⌋(RS_MANI_00017) Please note that the modeling of a facade SwComponentType does not make any assumptions about the implementation and about the realization of such a facade functionality . The facade may be realized by an Adaptive Software Component/Application or it may be realized by a “Network-Daemon”. AUTOSAR does not define any instructions for the implementation of such a functionality and the decision is project specific.
Versionen & Provenienz · Zugeordnete Anforderungen
Diese Angaben zeigt der Versions-Explorer.
Begründung & Zuweisungs-Evidenz
CompositionSwComponentType aggregating SwComponentPrototypes.
Dokumenten-Herkunft & Rückverfolgbarkeit
| Spezifikations-Dokument | TPS_ManifestSpecification.pdf |
|---|---|
| Dokumentseite | Seite 83 |
| Ziel-Modul | can (adaptive) |
| Ziel-Anforderung | TPS_SWCT_01035 |
| Semantische Rolle | heuristic |
| Automatisierungs-Konfidenz | 0.80 |