SNIP_ADAPTIVE_CAN_FIGURE_Figure_3_42

Figure 3.42: Modeling of ComSpec for persistency Note that the specification of encryption as described in [TPS_MANI_01073] does not impose a binding contract. An integrator may reasonably have various reasons to overrule the configuration in the PersistencyDataProvidedComSpec. It would simply not make any sense to statically model the encryption algorithms by means of an enumeration in the AUTOSAR meta-model and consequently require an update of this very enumeration in the AUTOSAR meta-model and XML schema in order to be able to use that hipster encryption algorithm that happens to fulfill ambitious needs in terms of encryption for a specific purpose. [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 either PersistencyDataProvidedComSpec.initValue or PersistencyDataRequiredComSpec.initValue⌋(RS_MANI_00027) 134 of 591 — AUTOSAR CONFIDENTIAL — Document ID 713: AUTOSAR_TPS_ManifestSpecification