Issue 15046: Poor example of Dependency notation (uml2-rtf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: Figure 7.37 shows an example of Dependency with <<dependencyName>> in guillemets. The Notation text above it states:” The arrow may be labeled with an optional stereotype and an optional name.” However surely the name of the Dependency itself should not be in guillemets – only that of the stereotype. Note that (subclasses of) Dependency are notated using a keyword instead of a stereotype so this should also be allowed for in the text. Proposed resolution: the Figure should be revised to show the dependencyName not in guillemets and possibly with a stereotype name in guillemets. Resolution: Revised Text: Actions taken: February 10, 2010: received issue Discussion: End of Annotations:===== ubject: Issues on UML 2.3 Superstructure Date: Wed, 10 Feb 2010 16:33:56 -0800 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issues on UML 2.3 Superstructure Thread-Index: AcqqseV2uLXHGFg7QnGYwvQiPcHwGw== From: "Pete Rivett" To: 1. Poor example of Dependency notation Figure 7.37 shows an example of Dependency with <> in guillemets. The Notation text above it states:. The arrow may be labeled with an optional stereotype and an optional name.. However surely the name of the Dependency itself should not be in guillemets . only that of the stereotype. Note that (subclasses of) Dependency are notated using a keyword instead of a stereotype so this should also be allowed for in the text. Proposed resolution: the Figure should be revised to show the dependencyName not in guillemets and possibly with a stereotype name in guillemets.