UML 2.4 RTF Avatar
  1. OMG Issue

UML24 — Figure 7.15

  • Key: UML24-41
  • Legacy Issue Number: 15056
  • Status: closed  
  • Source: Dassault Systemes ( Mr. Nerijus Jankevicius)
  • Summary:

    There are non-derived properties at both ends - clientDependency and supplierDependency.

    One association is non-navigable, that means supplierDependency is owned by Association, but what does it mean in UML metamodel implementation? How it should be implemented?

    Eclipse has no associations at all, we (MD) simply added this property into NamedElement, but not serializing it into XMI.

    I would suggest to make this property derived or remove at all (if it is not serialized, it does not affect backward compatibility).

  • Reported: UML 2.3 — Thu, 18 Feb 2010 05:00 GMT
  • Disposition: Resolved — UML 2.4
  • Disposition Summary:

    Regarding the implementation of supplierDependency as an owned end of an Association, the specification
    does not give implementations, but in the metamodels, it means the supplierDependency property is owned
    by the corresponding association between NamedElement and Dependency (the one with supplier on the
    other end). One-way associations in UML are modeled this way.
    Make NamedElement::clientDependency derived to avoid modifying the client.

  • Updated: Fri, 6 Mar 2015 20:58 GMT