-
Key: MARTE12_-82
-
Legacy Issue Number: 18165
-
Status: closed
-
Source: Universidad de Cantabria ( Alejandro Péz Ruiz)
-
Summary:
We have detected an inconsistency between the semantic description and its mapping to UML for Protected Passive Unit (PpUnit). In figure 13.3 and in the Annex F.7.7, PpUnit inherits from BehavioredClassifier and SynchResource. But when you see the UML Representation (Section 13.3) in Figure 13.8, the PpUnit inheritance from BehavioredClassifier is taken into account by using it as the base elements to be extended with the stereotype. Its nature as synchronization resource is not explicitly mapped to UML.
For these reasons, and considering the need to link a PpUnit with its implementing mutual exclusion resources that we propose a PpUnit to have an additional attribute (with multiplicity 0..n) that includes the MutualExclusionResource that the existence of the PpUnit implies. Being a GRM:: MutualExclusionResource a specialization of SynchResource, this attribute maps the synchronization resource nature of the PpUnit as it is expressed in its definition in the Annex F. -
Reported: MARTE 1.1 — Wed, 10 Oct 2012 04:00 GMT
-
Disposition: Closed; No Change — MARTE 1.2
-
Disposition Summary:
Closed no change
The concept of PpUnit is part of HLAM which provides a set of high level concepts for dealing with real-time, parallel and concurrent modeling concerns without “implementation” flavors. Adding such properties as previously denoted in the issue summary would introduce such dependency with “implementation” concern.
-
Updated: Wed, 19 Dec 2018 16:37 GMT
MARTE12_ — Missing synchronization resource in UML mapping for PpUnit
- Key: MARTE12_-82
- OMG Task Force: MARTE 1.2 RTF 2