Issue 7804: include the rationale for not declaring QoSDimension as tagged values (uml-qos-ft-ftf) Source: BAE SYSTEMS (Mr. Kevin Dockerill, kevin.dockerill(at)baesystems.com) Nature: Enhancement Severity: Significant Summary: The profile requires two stereotypes to be applied simultaneously (QoSDimension and QoSCharacteristic). This is untidy, although I can see from the examples later in the document that QoSDimension is applied to attributes when QoSCharacteristic is applied to a class. The document, at least, should include the rationale for not declaring QoSDimension as tagged values (fig 8-3 on page 11). Resolution: Revised Text: Actions taken: September 30, 2004: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 30 Sep 2004 06:19:29 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Kevin Dockerill Company: BAE SYSTEMS, Warton, Lancs UK mailFrom: Kevin.dockerill@baesystems.com Notification: No Specification: UML Profile for Modeling Quality of Service and Fault Tolerance Characteristics and Mechanisms Section: Section 9.1.1 FormalNumber: Ptc/2004-06-01 Version: Draft RevisionDate: 7/21/2004 Page: 21 Nature: Enhancement Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description The profile requires two stereotypes to be applied simultaneously (QoSDimension and QoSCharacteristic). This is untidy, although I can see from the examples later in the document that QoSDimension is applied to attributes when QoSCharacteristic is applied to a class. The document, at least, should include the rationale for not declaring QoSDimension as tagged values (fig 8-3 on page 11).