SNIP_ADAPTIVE_PLATFORM_FIGURE_Figure_3_35_MANIFESTSPECIFICATION

Figure 3.35: Specification of the SecurityEventReportToSecurityEventDefinitionMapping This meta-class maps the RPortPrototype to a SecurityEventDefinition that itself is part of the so-called Security Extract . [TPS_MANI_01339] Existence of the SecurityEventReportToSecurityEventDefinitionMapping is motivated by the AUTOSAR methodology Status: DRAFT ⌈The existence of the SecurityEventReportToSecurityEventDefinitionMapping is motivated by the AUTOSAR methodology . At the point in time when a given SecurityEventReportInterface is defined it could be that the corresponding SecurityEventDefinition is not yet defined. So it is possible to add this association later. Another reason for the existence of the mapping class is that a specific piece of application software may report different specific security events defined by different OEMs, depending on the target-configuration of the application software. Of course, the semantics of the security event all always be either identical or at least comparable, it could still happen that the Id of a security event might change depending on the specific project or simply because different OEMs use different Ids for semantically identical security events. ⌋ Class SecurityEventReportToSecurityEventDefinitionMapping Note This meta-class represents the ability to map a PortPrototype for reporting a security event to the actual security event that shall be reported by this PortPrototype. Tags: atp.Status=candidate atp.recommendedPackage=SecurityEventReportT oSecurityEventDefinitionMappings This Class is only used by the AUTOSAR Adaptive Platform. Base ARElement, ARObject, CollectableElement, Identifiable, MultilanguageReferrable, Packageable Element, Referrable, UploadableDesignElement, UploadablePackageElement Aggregated by ARPackage.element ▽