Issue 19338: Including use case depends on included use case but Include is no subclass of Dependency (uml2-rtf) Source: (, ) Nature: Clarification Severity: Significant Summary: The following sentences of the specification made me wonder why Include is no subclass of Dependency. "As the primary use of the Include relationship is for reuse of common parts, what is left in a base UseCase is usually not complete in itself but dependent on the included parts to be meaningful. This is reflected in the direction of the relationship, indicating that the base UseCase depends on the addition but not vice versa." Instead of the dependency being reflected in the direction of the relationship, the class could explicitly have Dependency semantics. Resolution: Revised Text: Actions taken: April 16, 2014: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 16 Apr 2014 07:45:34 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Florian Schneider Employer: mailFrom: flo.schneider@gmail.com Terms_Agreement: I agree Specification: OMG Unified Modeling Language TM (OMG UML) Section: 18.1.3 FormalNumber: ptc/2013-09-05 Version: 2.5 Doc_Year: 2013 Doc_Month: September Doc_Day: Day Page: 672 Title: Including use case depends on included use case but Include is no subclass of Dependency Nature: Clarification Severity: Significant CODE: 3TMw8 B1: Report Issue Remote Name: extranet.linova.de Remote User: HTTP User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.75.14 (KHTML, like Gecko) Version/7.0.3 Safari/537.75.14 Time: 07:45 AM Description: The following sentences of the specification made me wonder why Include is no subclass of Dependency. "As the primary use of the Include relationship is for reuse of common parts, what is left in a base UseCase is usually not complete in itself but dependent on the included parts to be meaningful. This is reflected in the direction of the relationship, indicating that the base UseCase depends on the addition but not vice versa." Instead of the dependency being reflected in the direction of the relationship, the class could explicitly have Dependency semantics.