UML 2.4.1 RTF Avatar
  1. OMG Issue

UML241 — Implicit parameter assignment may cause name clashes

  • Key: UML241-23
  • Legacy Issue Number: 16648
  • Status: closed  
  • Source: Fraunhofer FOKUS ( Mr. Marc-Florian Wendland)
  • Summary:

    The textual syntax of CallEvent and SignalEvents states the following:

    "<call-event> :: <name> [‘(‘ [<assignment-specification>] ‘)’]
    <assignment-specification> ::= <attr-name> [‘,’ <attr-name>]*

    <attr-name> is an implicit assignment of the corresponding parameter of the operation to an attribute (with this name)
    UML Superstructure Specification, of the context object owning the triggered behavior"

    This may lead to a situation where name clashes can occurr, if the context object already contains an identically named attibute.
    How should situations like a name clashes be resolved?

  • Reported: UML 2.4 — Mon, 31 Oct 2011 04:00 GMT
  • Disposition: Resolved — UML 2.4.1
  • Disposition Summary:

    The corresponding wording in the UML 2.5 specification is (from Subclause 13.3.4):
    “<assigned-name> is an implicit assignment of the argument value for the corresponding Parameter of the Operation
    to a Property or Variable of the context object for the triggered Behavior.”
    The “assigned-name” is the name of a Property or Variable that the context object already contains, not a definition of
    a new attribute. There is therefore no possibility of “name clash”.
    Disposition: Closed - No Change

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