1. OMG Issue

DEPL — MOF requires Associations to be Named

  • Key: DEPL-2
  • Legacy Issue Number: 5954
  • Status: open  
  • Source: Zuehlke Engineering ( Frank Pilhofer)
  • Summary:

    This is an editorial issue for the Deployment FTF:

    MOF requires that all associations and association ends be
    named. The model conventions section should mention default
    names even if they are suppressed in the diagrams.

    Proposed resolution:

    In section 3.3, "Model Diagram Conventions", rewrite paragraphs
    4 ("Role names on association ends ..."), 5 ("Role names at the
    navigable end ..."), 6 ("If a role names is suppressed ...") and
    7 ("If an association name is suppressed ...") to read

    Role names on associations are made explicit wherever they are
    expected to appear in generated code, e.g. as an interface's
    attribute name.

    Role names at the navigable end of a derived association are
    normally suppressed. Therefore, if the role name at the navigable
    end of an association is suppressed, the association is derived.

    If a role name is suppressed at the end of an association, the
    name of the type at the association end, starting with a lowercase
    character, is used as the role name. This is the same implicit
    rule as in OCL.

    Implicit association names are used throughout the model. For
    unidirectional associations, the name of the class at the source
    plus an underscore plus the name of the navigable end is used as
    the name of the association. For bidirectional associations, the
    concatenation of the class names at both ends, in alphabetical
    order, with an underscore inbetween, is used as the name of the

  • Reported: DEPL 1.0b1 — Thu, 19 Jun 2003 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT