DEENESPTFRRUARHIKOZHNL
ADAPTIVE Modul: can Rolle: heuristic Konfidenz: 80%

SNIP_ADAPTIVE_CAN_FIGURE_Figure_3_39

Quelle: ManifestSpecification.pdf (Seite 132) • Ziel-Anforderung: TPS_SYST_05016

Wortlaut

Figure 3.39: Simplified example of the application of ServiceInterfaceSubElement Please note that the modeling approach for the definition of optionality on the level of a ServiceInterface explicitly leaves out the question of how the necessary tag id is assigned. It is assumed that the step in the project workflow where ServiceInterfaces and their optional elements are defined is not the step where the assignment of an actual TL V data id (that is not to be confused with the actual tag that is used on the bus to identify the element) is in the focus. Therefore, the assignment of TL V data ids has intentionally been separated from the rest of the definition of optionality . Details can be found in section 3.11.3.

Versionen & Provenienz · Zugeordnete Anforderungen

Diese Angaben zeigt der Versions-Explorer.

Begründung & Zuweisungs-Evidenz

Assignment of TLV data ids

Dokumenten-Herkunft & Rückverfolgbarkeit

Spezifikations-Dokument ManifestSpecification.pdf
Dokumentseite Seite 132
Ziel-Modul can (adaptive)
Ziel-Anforderung TPS_SYST_05016
Semantische Rolle heuristic
Automatisierungs-Konfidenz 0.80