Issue 7822: obsession with use cases (uml-qos-ft-ftf) Source: BAE SYSTEMS (Mr. Kevin Dockerill, kevin.dockerill(at)baesystems.com) Nature: Clarification Severity: Significant Summary: don't understand the obsession with use cases here. A SWOT Element should not be a specialisation of a use case. A SWOT is performed for a system, not necessarily how you use it. I suggest we look for something equivalent to a Requirement (e.g. textual element), like there is in SysML Resolution: Revised Text: Actions taken: September 30, 2004: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 30 Sep 2004 06:35:33 -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-9 FormalNumber: Ptc/2004-06-01 Version: Draft RevisionDate: 7/21/2004 Page: 59 Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description I don't understand the obsession with use cases here. A SWOT Element should not be a specialisation of a use case. A SWOT is performed for a system, not necessarily how you use it. I suggest we look for something equivalent to a Requirement (e.g. textual element), like there is in SysML.