SNIP_ADAPTIVE_CRYPTO_FIGURE_Figure_7_15

Figure 7.15: 1. Code that accesses the cryptographic key can be one of several owners of the cryptographic key and therefore assume read and write access to the cryptographic key . 2. Code that accesses the cryptographic key may be restricted to read access, without the permission to change. This code would be one of several users of the cryptographic key . The benefit of formally describing the relation between cryptographic keys (represented by meta-class CryptoKeySlotDesign) and the users of these keys (represented by meta-class CryptoKeySlotUserDesign) via the CryptoKeySlotUsageDesign is that a formal check for completeness and consistency becomes possible. Another aspect is that the modeling of theses relations can be taken as the recipe for handling cryptographic keys in a further design step, in which CryptoKeySlotUserDesign corresponds to meta-class Executable and CryptoKeySlotUsageDesign corresponds to RPortPrototype.