Issue 10392: Page 5 third paragraph 3                                                                                                                                                                                (uml-qos-ft-ftf)
Source: Universidad Politecnica de Madrid (Dr. Miguel A. de Miguel, mmiguel@dit.upm.es)
Nature: Enhancement
Severity: Minor
Summary: Most modeling languages provide support for the description of functional behavior, they describe ** remove the** non-functional requirement**include s** merely using simple comments or informal structures. An example are the interfaces that provide support for the description of functional services in some modeling and interface description languages, but they do not specify nonfunctional properties of implementators. When a client defines a dependency of these interfaces, it has no information about the quality properties.


Resolution: 
Revised Text: Page 5 third paragraph 3

Most modeling languages provide support for the description of functional behavior, they describe ** remove the** non-functional requirement**include s** merely using simple comments or informal structures. An example are the interfaces that provide support for the description of functional services in some modeling and interface description languages, but they do not specify nonfunctional properties of implementators. When a client defines a dependency of these interfaces, it has no information about the quality properties.

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

End of Annotations:=====

m: "Miguel A. de Miguel" <mmiguel@dit.upm.es>
To: <uml-qos-ft-ftf@omg.org>
Subject: typos in UML Profile for QoS and Fault Tolerance 
Date: Tue, 10 Oct 2006 11:34:17 +0200
X-Mailer: Microsoft Outlook, Build 10.0.2627


Source: Linda Heaton
Nature: Enhancement
Severity: Minor
Summary:

 

Page 5 third paragraph 3:

 

Most modeling languages provide support for the description of functional behavior, they describe ** remove the** non-functional requirement**include s** merely using simple comments or informal structures. An example are the interfaces that provide support for the description of functional services in some modeling and interface description languages, but they do not specify nonfunctional properties of implementators. When a client defines a dependency of these interfaces, it has no information about the quality properties.