SNIP_ADAPTIVE_CAN_FIGURE_Figure_3_49_MANIFESTSPECIFICATION

Figure 3.49: Modeling of optional members of DataPrototypes in the context of a ServiceInterface [TPS_MANI_01084] Optionality for a DataPrototype typed by an ApplicationDataType⌈ A DataPrototype typed by an ApplicationDataType that is eligible for the definition of optionality can only be an ApplicationRecordElement or an entire ArgumentDataPrototype.⌋(RS_MANI_00030) [TPS_MANI_01133] Optional element of an event ⌈ An ApplicationRecordElement can in principle be used inside the definition of an event or field. In this case either the reference ServiceInterfaceSubElement.optAppRecordElementInServiceInterface or ServiceInterfaceSubElement.optImplRecordElement shall exist.⌋(RS_MANI_00030) [TPS_MANI_01134] Optional element in the context of a method⌈ If optionality occurs in the context of a ClientServerOperation then one of the following cases applies: • An entire argument identified as optional shall be referenced in the role ServiceInterfaceSubElement.optArgument. 168 of 602 — AUTOSAR CONFIDENTIAL — Document ID 713: AUTOSAR_TPS_ManifestSpecification