SNIP_ADAPTIVE_CAN_FIGURE_Figure_12_4

Figure 12.4: SoftwareCluster can reference ARElement [TPS_MANI_01116]{DRAFT} Reference to model elements included in an uploadable software package ⌈ Beside the ability to explicitly reference a Process in the role containedProcess it is possible to define the following references to required model elements: • references to meta-classes derived from UploadablePackageElement are formalized by way of SoftwareCluster.containedPackageElement. • references to meta-classes derived from ARElement are formalized by way of SoftwareCluster.containedARElement. • references to meta-classes derived from FibexElement are formalized by way of SoftwareCluster.containedFibexElement. T echnically , anUploadablePackageElement is also an ARElement, but it is still mandated to use the dedicated reference specifically for UploadablePackageElement.⌋(RS_MANI_00035) T o exemplify the reference to UploadablePackageElement, Figure 12.3 contains a subclass of UploadablePackageElement: ServiceInstanceToPortPrototypeMapping. It is obvious that the uploaded software needs to integrate with the communication stack and ServiceInstanceToPortPrototypeMapping is a prominent model element for this purpose. [constr_1542]{DRAFT} No nested definition of SoftwareCluster⌈ A SoftwareCluster shall not reference another SoftwareCluster in the role containedARElement.⌋() 452 of 591 — AUTOSAR CONFIDENTIAL — Document ID 713: AUTOSAR_TPS_ManifestSpecification