Issue 18165: Missing syncronization resource in UML mapping for PpUnit (marte-rtf) Source: (, ) Nature: Enhancement Severity: Critical 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. Resolution: Revised Text: Actions taken: October 10, 2012: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 10 Oct 2012 10:33:48 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Alejandro Péz Ruiz Employer: Universidad de Cantabria mailFrom: perezruiza@unican.es Terms_Agreement: I agree Specification: UML Profile for MARTE: Modeling and Analysis of Real-Time Embedded Systems Section: 13 FormalNumber: formal/2011-06-02 Version: 1.1 Doc_Year: 2011 Doc_Month: June Doc_Day: 30 Page: 183, 186 Title: Missing syncronization resource in UML mapping for PpUnit Nature: Enhancement Severity: Critical CODE: 3TMw8 B1: Report Issue Description: 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.