Issue 7807: Section 10 3rd paragraph (uml-qos-ft-ftf) Source: BAE SYSTEMS (Mr. Kevin Dockerill, kevin.dockerill(at)baesystems.com) Nature: Clarification Severity: Significant Summary: 3rd Paragraph - "A quality model is easy to reuse in the specification of non-functional properties .." You should have a QoS for a requirement. This raises the question "Why have Categories?". Surely a model will contain packages of requirements (as being defined in SysML) and the QoS would be applied to them. Resolution: Revised Text: Actions taken: September 30, 2004: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 30 Sep 2004 06:23:01 -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 10 FormalNumber: Ptc/2004-06-01 Version: Draft RevisionDate: 7/21/2004 Page: 31 Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description 3rd Paragraph - "A quality model is easy to reuse in the specification of non-functional properties .." You should have a QoS for a requirement. This raises the question "Why have Categories?". Surely a model will contain packages of requirements (as being defined in SysML) and the QoS would be applied to them.