Issue 7792: QoS Constraints (uml-qos-ft-ftf) Source: Universidad Politecnica de Madrid (Dr. Miguel A. de Miguel, mmiguel@dit.upm.es) Nature: Enhancement Severity: Significant Summary: Only QoS Constraints that are represented with UML constraints can be attached to more than one modelling element. To represent end-to-end QoS constraints we need to identify the source and the target of the constraint. An UML constraint is not enough to identify the source and the target. Resolution: Revised Text: Page 15 modifies Figure 8.6 and includes new paragraphs Figure 8.6 QoSConstraint Diagram End-to-End QoS constraints make reference to quality constraints that involves two or more modeling elements. Source elements define source instants for the quantification of constraints and target define the end of interval. EndToEndSource and EndToEndTarget are properties that make reference to source and target modeling elements. An example would be a QoS constraint (for example an OCL constraint attached to two modelling elements) that makes reference to two actions in an activity diagram (an iteration diagram would be the similar). Sometimes we can identify implicitly who are the source and the target, but in some cases (for example loops) this implicit assumption can generate errors. EndToEndSource and EndToEndTarget properties define explicitly the sources and targets. Page 27 modifies Figure 9.10 to include in the profile the modifications. and the association SubConstraint/GlobalConstraint that was not included in the profile. Figure 9.10 QoS Constraints Stereotypes Disposition: Resolved Actions taken: September 30, 2004: received issue March 8, 2006: closed issue Discussion: We have included in metamodel and profile elements for the identification of source and target End of Annotations:===== m: webmaster@omg.org Date: 30 Sep 2004 06:08:11 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Miguel A. de Miguel Company: Universidad Politécnica de Madrid mailFrom: mmiguel@dit.upm.es Notification: Yes Specification: UML Profile for Modeling Quality of Service and Fault Tolerance Characteristics and Mechanisms Section: Section 8, 9.4 and Appendix A FormalNumber: Ptc/2004-06-01 Version: Draft RevisionDate: 8/15/2004 Page: 13, 27 Nature: Enhancement Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description Only QoS Constraints that are represented with UML constraints can be attached to more than one modelling element. To represent end-to-end QoS constraints we need to identify the source and the target of the constraint. An UML constraint is not enough to identify the source and the target.