Issue 8920: Page: 62 (uml2-rtf) Source: Thematix Partners LLC (Mr. James J. Odell, email(at)jamesodell.com) Nature: Clarification Severity: Significant Summary: Description Figure 36 was not changed to conform to example description. Here, the example indicates that “the dependency is an instantiate dependency, where the Car class is an instance of the Vehicle Type class. However, Fig. 36 illustrates that Car class is an instance of the CarFactory class The page indicates issue 6159 addressed this same problem, but apparently it went unchanged. Resolution: Revised Text: Actions taken: July 5, 2005: received issue Discussion: End of Annotations:===== er-Agent: Microsoft-Entourage/11.1.0.040913 Date: Tue, 05 Jul 2005 21:15:26 -0400 Subject: UML issue From: James Odell To: Juergen Boldt Name: James Odell Company: Kabira mailFrom: email@jamesodell.com Notification: Yes Specification: UML 2.0 Superstructure Section: 7 FormalNumber: ptc/04-10-02 Version: 2.0 RevisionDate: 10/08/2005 Page: 62 Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Description Figure 36 was not changed to conform to example description. Here, the example indicates that .the dependency is an instantiate dependency, where the Car class is an instance of the Vehicle Type class. However, Fig. 36 illustrates that Car class is an instance of the CarFactory class X-VR-Score: 0.00 X-Authority-Analysis: v=1.1 cv=1tC8gCE8abT1P00P8zsYPuKJ/q6rKOuccKMKwfwf08U= c=1 sm=1 a=wbKXeunVgZ0A:10 a=sibq0pftem/EOZVNIgLWKg==:17 a=OID0eoJIR3EOqIaPn1EA:9 a=a_KzJoFhG1Yh8U8N47x-e9xzE-AA:4 a=wPNLvfGTeEIA:10 a=pGLkceISAAAA:8 a=vIyW76A7970kGgg3VnMA:9 a=8XNVSu3T-AuKqOX6z8IA:7 a=NWFPrgi3D93uqPce484sAQkfHN0A:4 a=MSl-tDqOz04A:10 a=2XmQ2a48u7_tJELHhLwA:9 a=7nqE1ah0MovRdt_j3Fz-A8CfGm4A:4 a=HXjIzolwW10A:10 a=bT_ownCs-EUPWEGU:18 a=sibq0pftem/EOZVNIgLWKg==:117 X-CM-Score: 0.00 Date: Thu, 20 May 2010 14:11:28 -0400 From: Jim Logan Organization: Alion Science & Technology User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 To: uml2-rtf@omg.org Subject: Direction of <> All, It's not clear to me in which direction the <> dependency should point. The UML 2.3 spec says: In the example below, the Car class has a dependency on the CarFactory class. In this case, the dependency is an instantiate dependency, where the Car class is an instance of the CarFactory class. If Car has a dependency on CarFactory, the dependency arrow points in the other direction. Therefore, I think the diagram is backwards. Also, why is <> a stereotype on the Usage element? What does if mean for an instance to "use" a class? Thanks, -Jim Subject: RE: Direction of <> Date: Thu, 20 May 2010 16:07:15 -0400 X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: Direction of <> thread-index: Acr4SJdGWCXP/O2FTpuOWj6KhC2X5QADqcuw From: "Ed Seidewitz" To: "Jim Logan" Cc: Jim . The text is wrong. It should say: .In the example below, the CarFactory class has a dependency on the Car class. In this case, the dependency is an instantiate dependency, where objects of the Car class are instantiated by objects of the CarFactory class.. Note that neither the CarFactory nor the Car are instances . they are both classes. This dependency is specifically not .instanceOf. or something like that. The CarFactory class .uses. the Car class because, presumably, it uses some sort of constructor from that class (implicitly or explicitly) in order to create Car instances. Issue 8920 already covers the problem with this example, but resolution of this issue has been deferred as not being high priority. It should be fixed as part of the spec simplification re-write for UML 2.5. -- Ed -------------------------------------------------------------------------------- From: Jim Logan [mailto:jllogan+omg@gmail.com] Sent: Thursday, May 20, 2010 2:11 PM To: uml2-rtf@omg.org Subject: Direction of <> All, It's not clear to me in which direction the <> dependency should point. The UML 2.3 spec says: In the example below, the Car class has a dependency on the CarFactory class. In this case, the dependency is an instantiate dependency, where the Car class is an instance of the CarFactory class. If Car has a dependency on CarFactory, the dependency arrow points in the other direction. Therefore, I think the diagram is backwards. Also, why is <> a stereotype on the Usage element? What does if mean for an instance to "use" a class? Thanks, -Jim The page indicates issue 6159 addressed this same problem, but apparently it went unchanged.