Issue 5956: Dependency relationships are not a MOF construct (deployment-ftf)
Source: Zuehlke Engineering (Mr. Frank Pilhofer, fpilhofer2008(at)gmail.com)
Nature: Uncategorized Issue
Severity: 
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
3.4.


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.
Resolution: 
Revised Text: 
Actions taken:
June 19, 2003: received issue
Discussion: 

End of Annotations:=====
Subject: Dependency relationships are not a MOF construct 
Date: Thu, 19 Jun 2003 10:01:19 -0400 
Thread-Topic: Dependency relationships are not a MOF construct 
Thread-Index: AcM2a0JqMwN6ru8cRKi0UiHgpl/qSQ== 
From: "Pilhofer, Frank" <fpilhofe@mc.com> 
To: <issues@omg.org> 
Cc: <deployment-ftf@omg.org> 
X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id h5JE0pkM002558 


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
3.4.


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.