SNIP_ADAPTIVE_CAN_FIGURE_Figure_3_81

Figure 3.81: Modeling of optionality on the level of ApplicationDataType [TPS_MANI_01184] Definition of optional elements on the level of ApplicationDataType Upstream requirements: RS_MANI_00030 ⌈The modeling approach for the definition of optional elements on the level of ApplicationDataType is to set the attribute ApplicationRecordElement.isOptional to the value true. If the attribute is not set or set to the value false then the respective ApplicationRecordElement shall be considered mandatory .⌋ Class ApplicationRecordDataType Package M2::AUTOSART emplates::SWComponentT emplate::Datatype::Datatypes Note An application data type which can be decomposed into prototypes of other application data types. Tags: atp.recommendedPackage=ApplicationDataT ypes Base ARElement, ARObject, ApplicationCompositeDataT ype, ApplicationDataT ype, AtpBlueprint , Atp Blueprintable, AtpClassifier , AtpT ype, AutosarDataT ype, CollectableElement, Identifiable, Multilanguage Referrable, PackageableElement, Referrable Aggregated by ARPackage.element Attribute Type Mult. Kind Note element (ordered) ApplicationRecord Element * aggr Specifies an element of a record. The aggregation of ApplicationRecordElement is subject to variability with the purpose to support the conditional existence of elements inside a ApplicationrecordData T ype. Stereotypes: atpSplitable; atpVariation Tags: atp.Splitkey=element.shortName, element.variation Point.shortLabel vh.latestBindingTime=preCompileTime Table 3.179: ApplicationRecordDataType