Issue 5081: It is not clear how a QoS characteristic can be attached to a Resource (uml-scheduling-ftf)
Source: International Business Machines (Mr. Morgan Bjorkander, nobody)
Nature: Uncategorized Issue
Severity: 
Summary: It is not clear how a QoS characteristic can be attached to a Resource. The example given throughout Chapter 4 is {qosDeadline = 5ms}, which leaves the reader with the idea that QoS characteristics will be attached as tagged values. But later QoS characteristics are defined to be stereotyped Packages, Values, Instances or Classifiers (stereotyped with <<GRMqosCharacteristic>>), and qosDeadline turns out to be a predefined tag value without connection to the <<GRMqosCharacteristic>> stereotype. Furthermore, in Fig. 28, the QoS characteristics of a clock are defined as required tags of the RTtimingMechanism stereotype, with no mention to <<GRMqosCharacteristic>>.

Resolution: closed no change
Revised Text: 
Actions taken:
March 20, 2002: received issue
September 24, 2004: closed issue
Discussion: 
This particular issue was really related to the initial submission and much clarifying text was added and changes made to the domain model to deal with it. It really should have been closed by the FTF since the specific issues that it raises were solved there. The only reason it was kept was that it was misinterpreted as being a broader complaint about the overall vagueness of some parts of the profile. However, on reviewing it this time, I no longer see that interpretation of this issue.
End of Annotations:=====
This is issue # 5081

It is not clear how a QoS characteristic can be attached to a Resource

It is not clear how a QoS characteristic can be attached to a
Resource. The example given throughout Chapter 4 is {qosDeadline =
5ms}, which leaves the reader with the idea that QoS characteristics
will be attached as tagged values. But later QoS characteristics are
defined to be stereotyped Packages, Values, Instances or Classifiers
(stereotyped with <<GRMqosCharacteristic>>), and qosDeadline turns out
to be a predefined tag value without connection to the
<<GRMqosCharacteristic>> stereotype. Furthermore, in Fig. 28, the QoS
characteristics of a clock are defined as required tags of the
RTtimingMechanism stereotype, with no mention to
<<GRMqosCharacteristic>>.