UML 2.6 RTF Avatar
  1. OMG Issue

UMLR — One association end is derived, another is not

  • Key: UMLR-192
  • Legacy Issue Number: 14930
  • Status: open  
  • Source: Dassault Systemes ( Mr. Nerijus Jankevicius)
  • Summary:

    One association end is derived, another is not. It causes implementation issues, as when we set one end, opposite should be automatically set also.

    Vertex::outgoing [0..*] is derived, opposite Transition::source [1] is not
    Activity::structuredNode [0..*] is derived, opposite StructuredActivityNode::activity [0..
    ConnectableElement::end [0..*] is derived, opposite ConnectorEnd::role [1] is not
    Package::ownedType [0..*] is derived, opposite Type::package [0..] is not
    Package::nestedPackage [0..*] is derived, opposite Package::nestingPackage [0..] is not
    Vertex::incoming [0..*] is derived, opposite Transition::target [1] is not

  • Reported: UML 2.5 — Fri, 8 Jan 2010 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT