Issue 6220: UML 2 Super/pg.130/missing notation explanation (uml2-superstructure-ftf) Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org) Nature: Uncategorized Issue Severity: Summary: pg. 130: Realization/Notation –dashed generalization notation is not mentioned, but it is shown in the chart on pg. 130. Add it to the text Resolution: see above Revised Text: Actions taken: September 7, 2003: received issue March 8, 2005: closed issue Discussion: Actually, the problem is slightly different than stated. The problem is that in UML 2.0, the concept of Realization – which was always denoted by a dashed line with a triangular arrowhead – has been refined for the special case when a BehavioredClassifier realizes an Interface. However, on page 110, it is stated that a Realization is now denoted by a regular dashed line with an open (stick) arrowhead and the keyword “realize” attached to it. This is a gratuitous change that is likely to cause confusion and has no justification. Hence, this resolution proposes to retain the existing dashed-line-triangular-arrowhead notation for Realization. What should the notation for Implementation be then? One possibility is to retain the currently proposed notation but simply add the “implements” keyword. However, this adds yet another keyword that is likely to be confused with other situations. Hence, the proposal here is to retain the same notation for Realization and Implementation: the dashed line with the triangular arrowhead. (Tools can automatically decide which one to use depending on the source and target elements., or it could leave the choice to the user.) The following changes need to be made to support this: ?? On page 110 in the Notation section of Realization replace the existing sentence by the following sentence and figure: “A Realization dependency is shown as a dashed line with a triangular arrowhead at the end that corresponds to the realized element. Figure 52, illustrates an example in which a Business class is realized by a combination of an Owner and Employee classes.” Figure 52 – Notation for a realization dependency ?? On page 130 in Table 4, add another entry to the table for Implementation between the entry for Generalization and the entry for Realization. This entry will have the Path Type equal to “Implementation”, the Notation that is the same as the notation for Realization, and the Reference: “See “Implementation (from Interfaces)” on page 113. End of Annotations:===== To: issues@omg.org Subject: UML 2 Super/pg.130/missing notation explanation X-Mailer: Lotus Notes Release 5.0.11 July 24, 2002 From: Branislav Selic Date: Sun, 7 Sep 2003 09:54:16 -0400 X-MIMETrack: Serialize by Router on D25ML05/25/M/IBM(Release 6.0.2CF1|June 9, 2003) at 09/07/2003 09:54:19, Serialize complete at 09/07/2003 09:54:19 pg. 130: Realization/Notation ޶dashed generalization notation is not mentioned, but it is shown in the chart on pg. 130. Add it to the text. Bran Selic IBM Software Group -- Rational Software 770 Palladium Drive Kanata, Ontario, Canada K2V 1C8 ph. (613) 591-7915 fax (613) 599-3912 e-mail: bselic@ca.ibm.com