Issue 10407: Page 79 paragraph 79                                                                                                                                                                                    (uml-qos-ft-ftf)
Source: Universidad Politecnica de Madrid (Dr. Miguel A. de Miguel, mmiguel@dit.upm.es)
Nature: Enhancement
Severity: Minor
Summary: QoSRequired and QoSContract constraint based on QoS4SADemand can annotate UML 2.0 Messages, Control Flows,

Associations, and Transitions for the description of frequencies of demand of services. These UML elements have

associated implicitly or explicitly request of services from a client to a service provider, and the QoS Constraints provide

additional information for the temporal distribution of the invocations. ** Change QoS4SADemand** QoS4SADeamand include some dimensions that


Resolution: 
Revised Text: Page 79 paragraph 79

QoSRequired and QoSContract constraint based on QoS4SADemand can annotate UML 2.0 Messages, Control Flows,

Associations, and Transitions for the description of frequencies of demand of services. These UML elements have

associated implicitly or explicitly request of services from a client to a service provider, and the QoS Constraints provide

additional information for the temporal distribution of the invocations. ** Change QoS4SADemand** QoS4SADeamand include some dimensions that

Actions taken:
October 10, 2006: received issue
April 20, 2007: closed issue
Discussion: 

End of Annotations:=====
s is issue # 10407

Page 79 paragraph 79

QoSRequired and QoSContract constraint based on QoS4SADemand can annotate UML 2.0 Messages, Control Flows,

Associations, and Transitions for the description of frequencies of demand of services. These UML elements have

associated implicitly or explicitly request of services from a client to a service provider, and the QoS Constraints provide

additional information for the temporal distribution of the invocations. ** Change QoS4SADemand** QoS4SADeamand include some dimensions that