Issue 10390: QoSCompoundConstraint in the profile                                                                                                                                                                    (uml-qos-ft-ftf)
Source: Universidad Politecnica de Madrid (Dr. Miguel A. de Miguel, mmiguel@dit.upm.es)
Nature: Enhancement
Severity: Significant
Summary: QoSCompoundConstraint does not have associated a stereotype in the profile. It must be represented with some

Other QoSConstraint stereotypes, but this creates imprecision. Specific stereotype is needed to avoid this.


Resolution: 
Revised Text: Figures 9.2, 9.3, 9.10, 9.12, 9.13, 9.14

Figure 9.2
Previous version:
 
New version:
 

Figure 9.3
Previous version:
 
New version:
 

Figure 9.10
Previous version:
 
New version:
 

Figure 9.12
Previous version:
 
New version:
 

Figure 9.13
Previous version:
 
New version:
 

Figure 9.14
Previous version:
 
New version:

Actions taken:
October 17, 2006: received issue
April 20, 2007: closed issue
Discussion: 
Resolution:
QoSCompoundConstraint stereotype has been included.
The QoS profile model has been updated with UML 2.1 approaches. The main difference is the method to represent stereotype properties that reference other stereotypes or modelling elements. In this approach we use associations based on UML 2.1 modification in profile chapter (Page 693 ptc06-01-02):
Stereotypes can participate in associations. The opposite class can be another stereotype, a non-stereotype class that is owned by a profile, or a metaclass of the reference metamodel. For these associations there must be a property owned by the Stereotype to navigate to the opposite class. The opposite property must be owned by the Association itself rather than the other class/metaclass.
Currently there are not too many tools that support the properties of stereotypes to other stereotypes (we don't know any tool public available). The profiles that accompanies to this document implement the associations of stereotypes as properties which type is the base element of the other stereotype. These properties should be only the stereotype or the model element annotated with the stereotype. 

End of Annotations:=====
ubject: Issue QoSCompoundConstraint in the profile
Date: Thu, 17 Aug 2006 11:13:44 +0200
X-Mailer: Microsoft Outlook, Build 10.0.2627

Source: Universidad Politecnica de Madrid (Dr. Miguel A. de Miguel, mmiguel@dit.upm.es)
Nature: Enhancement
Severity: Significant
Summary:
 
QoSCompoundConstraint does not have associated a stereotype in the profile. It must be represented with some
Other QoSConstraint stereotypes, but this creates imprecision. Specific stereotype is neede