SNIP_ADAPTIVE_CAN_FIGURE_Figure_3_37_MANIFESTSPECIFICATION

Figure 3.37: Modeling of the PersistencyKeyValueStorageInterface In contrast to other kinds of PortInterfaces, it is not required to define elements of a PersistencyKeyValueStorageInterface. If this is intended, however, the aggregation PersistencyKeyValueStorageInterface.dataElement shall be used for this purpose. [TPS_MANI_01138]{DRAFT} Semantics of PersistencyKeyValueStorageInterface.dataElement⌈By aggregating PersistencyDataElement in the role dataElement, it is possible to explicitly model key-value pairs (and some of their properties) accessible to the application software within the context of a PersistencyKeyValueStorageInterface.⌋(RS_MANI_00027) [TPS_MANI_01180]{DRAFT} Collection of data types that requires serialization support⌈The collection of data types that requires serialization support consists of • AbstractImplementationDataTypes referenced in the role PersistencyKeyValueStorageInterface.dataTypeForSerialization • either – AbstractImplementationDataTypes taken to type a PersistencyKeyValueStorageInterface.dataElement or – AbstractImplementationDataTypes mapped to ApplicationDataTypes taken to type a PersistencyKeyValueStorageInterface.dataElement by means of PortInterfaceToDataTypeMapping. dataTypeMappingSet that also refers to the enclosing PersistencyKeyValueStorageInterface. ⌋(RS_MANI_00027) Please note that a PersistencyDataElement can be typed by either an ApplicationDataType or else a CppImplementationDataType.