Issue 14045: semantics of associating a use case with another use case, or indeed anything other than an actor, are unclear (uml2-rtf) Source: Oracle (Mr. Dave Hawkins, dave.hawkins(at)oracle.com) Nature: Clarification Severity: Significant Summary: The semantics of associating a use case with another use case, or indeed anything other than an actor, are unclear. There is a rule specifying that use cases may be only be associated with other use cases with different subjects because they describe a complete usage of the subject. But that doesn't explain what it means to have any association. The only hint is in the notation section that gives some examples as "(e.g., to denote input/output, events, and behaviors)." However these details ought to be part of semantics and expanded on. Resolution: Revised Text: Actions taken: July 1, 2009: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 01 Jul 2009 12:48:52 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Dave Hawkins Company: Oracle mailFrom: dave.hawkins@oracle.com Notification: No Specification: UML Superstructure Section: 16.3.6 FormalNumber: formal/09-02-03 Version: 2.2 RevisionDate: 2/3/2009 Page: 597,600 Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 Description The semantics of associating a use case with another use case, or indeed anything other than an actor, are unclear. There is a rule specifying that use cases may be only be associated with other use cases with different subjects because they describe a complete usage of the subject. But that doesn't explain what it means to have any association. The only hint is in the notation section that gives some examples as "(e.g., to denote input/output, events, and behaviors)." However these details ought to be part of semantics and expanded on.