Issue 7795: Section 8.3                                                                                                                                                                                             (uml-qos-ft-ftf)
Source: BAE SYSTEMS (Mr. Kevin Dockerill, kevin.dockerill@baesystems.com)
Nature: Enhancement
Severity: Significant
Summary: Numbered List (point 2) - "the expressions define maximum and minimum values". I agree with the sentiment, but I can't see how the model is capturing a range (e.g. minimum and maximum) since the range itself may be associated with a QoSCharacteristic or attributes of a class. See further comments below. 

Resolution: 
Revised Text: 
Actions taken:
September 30, 2004: received issue
March 8, 2006: cosed issue
Discussion: 
The range can be represented with several approaches. An example is to use statistical qualifiers to identify the minimum and maximum qos dimensions 
Following chapters and sections include several examples.
Disposition:	Closed, no change

End of Annotations:=====

m: webmaster@omg.org 
Date: 30 Sep 2004 06:12:47 -0400 
To: <issues@omg.org> 
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 8.3
FormalNumber: Ptc/2004-06-01
Version: Draft
RevisionDate: 7/21/2004
Page: 13
Nature: Enhancement
Severity: Significant
HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Description
Numbered List (point 2) - "the expressions define maximum and minimum values". I agree with the sentiment, but I can't see how the model is capturing a range (e.g. minimum and maximum) since the range itself may be associated with a QoSCharacteristic or attributes of a class. See further comments below.