UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — Section: 9.3.11 p 182

  • Key: UML22-1129
  • Legacy Issue Number: 11087
  • Status: closed  
  • Source: UPM ( Juan Pedro Silva)
  • Summary:

    All rolenames in non-navigable associations in the UML metamodel should be stated, to allow reaching from one element of the association to the other using OCL. Currently, this is limited to un-ambigous type names if the rolename is not stated. For example, in section "9.3.11 Port (from Ports)", Port has required and provided interfaces, and has no rolename on both associations. There is no current way, using OCL, of getting from one Interface to a Port that provides or requires it, as "self.port" is ambigous because it doesn't specify if the programmer is looking for Ports providing or requiring such Interface. The situation repeats in many other associations.

  • Reported: UML 2.1.1 — Thu, 31 May 2007 04:00 GMT
  • Disposition: Resolved — UML 2.1.2
  • Disposition Summary:

    Discussion: It is not required for the specification to name such associations. Navigation is not that hard if this is really desired: find all ports and select the subset that has the appropriate interface. Also, OCL is not constrained by navigability. Discussion: Closed, no change

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