Issue 1643:  IDL consistency Issue for PDM (pdm-rtf)
Source:  (, )
Nature:  Revision
Severity: 
Summary: Summary: In the Salt Lake city meeting Ed brought up a point that Revisions 
      cannot be created independent of the Master and the Iteration cannot 
      be created independent of the Revision to which it belongs. 
      
      As a result the Factory for the Master - to - Revision relationship 
      does not exit and the create function for the revision takes the 
      Master as a parameter and also creates the MasterRevision 
      relationship. The same is also true for Revision to Iteration 
      Relationship. eg BaselineRevisionFactory - The create function takes a 
      BaselineMaster as a parameter and creates the 
      BaselineMasterComposition Relationship.
      
      This behaviour has been duplicated in the Master-Revision-Iteration 
      relationships of most of the modules expect the Product Structure 
      Definition. In the ProductStructureDefinition Module the following 
      relationships should not have factories:
         PartMasterComposition
         PartDataRelationship
         PartStructureRelationship
         PartDataIterationRelationship
         PartStructureIterationRelationship
      
      
      Taking this principle one step further we can say that this behaviour 
      is true for all Containment Type of relationships (Black Diamond). If 
      so then there are a few other places where this applies these are 
         Change Management Module:
                 Deliverable relationship
                 ChangeDescription relationship
      
         Configuration Management Module
                 SpecificationCategoryComposition Relationship
 

Resolution: 
Revised Text: 
Actions taken:
July 8, 1998: received issue
August 24, 1999: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <mangesh.bhandarkar@sherpa.com>
From: mangesh.bhandarkar@sherpa.com
Date: Tue, 07 Jul 98 09:17:02 -0800
To: <issues@omg.org>
Subject: IDL Consistency issue for PDM Enabler


     
     In the Salt Lake city meeting Ed brought up a point that
Revisions 
     cannot be created independent of the Master and the Iteration
cannot 
     be created independent of the Revision to which it belongs. 
     
     As a result the Factory for the Master - to - Revision
relationship 
     does not exit and the create function for the revision takes the 
     Master as a parameter and also creates the MasterRevision 
     relationship. The same is also true for Revision to Iteration 
     Relationship. eg BaselineRevisionFactory - The create function
takes a 
     BaselineMaster as a parameter and creates the 
     BaselineMasterComposition Relationship.
     
     This behaviour has been duplicated in the
Master-Revision-Iteration 
     relationships of most of the modules expect the Product Structure

     Definition. In the ProductStructureDefinition Module the
following 
     relationships should not have factories:
        PartMasterComposition
        PartDataRelationship
        PartStructureRelationship
        PartDataIterationRelationship
        PartStructureIterationRelationship
     
     
     Taking this principle one step further we can say that this
behaviour 
     is true for all Containment Type of relationships (Black
Diamond). If 
     so then there are a few other places where this applies these are

        Change Management Module:
                Deliverable relationship
                ChangeDescription relationship
     
        Configuration Management Module
                SpecificationCategoryComposition Relationship
     
     Thks
     
     Mangesh
     
     Mangesh Bhandarkar
     Sherpa Corporation
     email: mangesh.bhandarkar@sherpa.com 
     tel #: 408-941-4705