Issue 9445: Link notation for instance diagrams does not cope with multiple classifiers (uml2-rtf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: Figure 7.54 of ptc/06-01-02 shows an Instance Diagram notation for a Link. With the accompanying text: "An instance specification whose classifier is an association represents a link and is shown using the same notation as for an association, but the solid path or paths connect instance specifications rather than classifiers. It is not necessary to show an underlined name where it is clear from its connection to instance specifications that it represents a link and not an association. End names can adorn the ends. Navigation arrows can be shown, but if shown, they must agree with the navigation of the association ends." However this does not cater for the fact that the metamodel allows an InstanceSpecification to be associated with many Classifiers. Proposed resolution: Extend the metamodel for Instances to explicitly model Links. For a good start see the instances model in the MOF2 Core Abstract Semantics chapter (it is not part of MOF - it is only there to explain the semantics of MOF in terms of metamodel instances). Resolution: Revised Text: Actions taken: March 15, 2006: received issue Discussion: End of Annotations:===== ubject: Link notation for instance diagrams does not cope with multiple classifiers Date: Wed, 15 Mar 2006 06:59:37 -0800 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Link notation for instance diagrams does not cope with multiple classifiers Thread-Index: AcZIQRPimMvbkg5sSwqNQh+Y1Pwq3g== From: "Pete Rivett" To: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id k2FEoI1i025247 Figure 7.54 of ptc/06-01-02 shows an Instance Diagram notation for a Link. With the accompanying text: "An instance specification whose classifier is an association represents a link and is shown using the same notation as for an association, but the solid path or paths connect instance specifications rather than classifiers. It is not necessary to show an underlined name where it is clear from its connection to instance specifications that it represents a link and not an association. End names can adorn the ends. Navigation arrows can be shown, but if shown, they must agree with the navigation of the association ends." However this does not cater for the fact that the metamodel allows an InstanceSpecification to be associated with many Classifiers. Proposed resolution: Extend the metamodel for Instances to explicitly model Links. For a good start see the instances model in the MOF2 Core Abstract Semantics chapter (it is not part of MOF - it is only there to explain the semantics of MOF in terms of metamodel instances). Pete Rivett (mailto:pete.rivett@adaptive.com) CTO, Adaptive Inc. Hello House, 135 Somerford Road, Christchurch, BH23 3PY, UK Tel: +44 (0)1202 491243 Fax: +44 (0)1202 491241 http://www.adaptive.com