Issue 9119: Realization classifier (uml2-rtf) Source: Eclipse Foundation (Mr. Kenneth Hussey, kenn.hussey(at)gmail.com) Nature: Uncategorized Issue Severity: Summary: The Realization classifier should not be redefined in UML::Components::BasicComponents. In a component realization, the direction of the dependency is reversed, i.e. the client (source) of the dependency is the component abstraction and the supplier (target) of the dependency is the realizing classifier; this conflicts with other specializations of Realization (e.g. InterfaceRealization). -> A new specialization ('ComponentRealization') should be introduced instead, upon which the 'abstraction' and 'realizingClassifier' properties would be defined. This could be achieved by simply renaming Realization to 'ComponentRealization' in UML::Components::BasicComponents and adding a generalization from it to UML::Classes::Dependencies::Realization. Resolution: see above Revised Text: see pages 574 - 575 of ptc/2006-04-01 Actions taken: October 26, 2005: received issue August 23, 2006: closed issue Discussion: Agreed. Note that the lower bound of Realization::realizingClassifier is currently 1, meaning that all interface realizations based on the current metamodel are effectively invalid (because although they have an implementing classifier, they do not have a realizing classifier since it is at the opposite end of the dependency). End of Annotations:===== ubject: UML 2.1 Implementation Issue X-Mailer: Lotus Notes Release 6.0.1CF1 March 04, 2003 From: Kenneth Hussey Date: Wed, 26 Oct 2005 11:57:53 -0400 X-MIMETrack: Serialize by Router on D25ML03/25/M/IBM(Release 6.5.4|March 27, 2005) at 10/26/2005 11:57:53, Serialize complete at 10/26/2005 11:57:53 The Realization classifier should not be redefined in UML::Components::BasicComponents. In a component realization, the direction of the dependency is reversed, i.e. the client (source) of the dependency is the component abstraction and the supplier (target) of the dependency is the realizing classifier; this conflicts with other specializations of Realization (e.g. InterfaceRealization). -> A new specialization ('ComponentRealization') should be introduced instead, upon which the 'abstraction' and 'realizingClassifier' properties would be defined. This could be achieved by simply renaming Realization to 'ComponentRealization' in UML::Components::BasicComponents and adding a generalization from it to UML::Classes::Dependencies::Realization. Kenn Hussey Eclipse UML2 Project Lead Rational Software, IBM Software Group 770 Palladium Drive Kanata, Ontario, K2V 1C8 T: (613) 599-3980 F: (613) 599-3912