1. OMG Issue

DEPL — Dependency relationships are not a MOF construct

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

    This is a new editorial issue for the Deployment FTF:

    The ImplementationArtifactDescription class makes use of a
    dependency relationship (to ImplementationArtifact), which is
    not a MOF construct. The dependency should be removed from the
    core model and moved to a non-normative package instead. Also,
    as a meta-concept, ImplementationArtifact should not be part
    of the ComponentDataModel.

    Proposed resolution:

    In section 3.4, "Component Data Model", in the description of the
    ImplementationArtifactDescription, remove the <<describes>> depen-
    dency to ImplementationArtifact from the diagram. Remove the
    ImplementationArtifact class.

    In section 3.12, "Relations to Other Standards", add Implemen-
    tationArtifactDescription to the diagram, and show its dependency
    on ImplementationArtifact. Paste the description and semantics
    for ImplementationArtifact from the text that was cut from section

    At the beginning of section 3.12, add the explanation

    This section relates some classes in this platform independent
    model to classes from other packages. This section is explanatory
    and non-normative.

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