SNIP_ADAPTIVE_CAN_FIGURE_Figure_3_11

Figure 3.11: Modeling of ComSpec for persistency [TPS_MANI_01160]{DRAFT} Definition of initial value for PersistencyDataElement⌈The definition of an initial value for a PersistencyDataElement can be done on the level of a PortPrototype by means of PersistencyDataRequiredComSpec.initValue⌋(RS_MANI_00027) Class PersistencyDataRequiredComSpec Package M2::AUTOSART emplates::AdaptivePlatform::ApplicationDesign::ComSpec Note This meta-class represents the ability to define port-specific attributes for supporting use cases of data persistency on the required side. Base ARObject, RPortComSpec Aggregated by AbstractRequiredPortPrototype.requiredComSpec, PortPrototypeBlueprint.requiredComSpec Attribute Type Mult. Kind Note dataElement PersistencyData Element 0..1 ref This refrence represents the PersistencyDataElement for which the PersistencyDataRequiredComSpec applies. initValue ValueSpecification 0..1 aggr This aggregation represents the definition of an initial value for the PersistencyDataElement referenced by the enclosing PersistencyDataRequiredComSpec Table 3.29: PersistencyDataRequiredComSpec [constr_10153]{DRAFT} Multiplicity of reference in the role PersistencyDataRequiredComSpec.dataElement⌈For each PersistencyDataRequiredComSpec, the reference in the role dataElement shall exist at the time before the generation of the ara API starts .⌋() [constr_10081]{DRAFT} Existence of initial values in the definition of PersistencyDataRequiredComSpec⌈For each PersistencyDataRequiredComSpec, if the value of attribute dataElement.updateStrategy is set to the value delete, then attribute PersistencyDataRequiredComSpec.initValue shall not exist at the time before the generation of the ara API starts .⌋()