Issue 7824: figure 12-12 (uml-qos-ft-ftf) Source: BAE SYSTEMS (Mr. Kevin Dockerill, kevin.dockerill@baesystems.com) Nature: Clarification Severity: Minor Summary: Again, a note to reflect on the general comments. Treatment should not be a use case. I suppose this should again be a textual element. Alternatively, you could think about a dependency to an element where the risk is being mitigated (e.g. use case, requirement and constraint). Resolution: Revised Text: Actions taken: September 30, 2004: received issue March 8, 2006: closed issue Discussion: Treatments are part of the functions a system performs, and there is no reason that shouldn't be represented as a use case. Again, the idea behind a graphical language is to represent things graphically (see earlier comments). Disposition: Closed, no change End of Annotations:===== m: webmaster@omg.org Date: 30 Sep 2004 06:37:38 -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: fig. 12-12 FormalNumber: Ptc/2004-06-01 Version: Draft RevisionDate: 7/21/2004 Page: 61 Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description Again, a note to reflect on the general comments. Treatment should not be a use case. I suppose this should again be a textual element. Alternatively, you could think about a dependency to an element where the risk is being mitigated (e.g. use case, requirement and constraint).