Issue 1575: PersonOrganization relastionship -- IDL problem (pdm-rtf) Source: (, ) Nature: Revision Severity: Minor Summary: Summary: 2.1.3.7 PersonOrganization. The IDL says that the PersonOrganization relationship has anattribute called "role". The picture of the IDL shows that there are noattributes in this relationship. The other relationship in this module(ProgramOwner) does not have any attributes. Also there is no correction toeither of these interfaces in the errata. Should I believe the IDL pictureor the text? Resolution: The IDL for PersonOrganization is correct and the "role" attribute should be included in the UML. Revised Text: Update the UML in 2.1.2 so that the PersonOrganization object includes the attribute "role : string". Actions taken: June 24, 1998: received issue August 24, 1999: closed issue Discussion: End of Annotations:===== Return-Path: From: mangesh.bhandarkar@sherpa.com Date: Wed, 24 Jun 98 08:27:05 -0800 To: Cc: Subject: Issue on cardinality for PDM Enabler In the Product Structure Definition module the "data" related to the part is broken down into groups the PartStructure and the PartData. For example mechanical design data, electrical design data, mechanical assembly data, electrical assembly data etc. The intent of this is to allow people in different roles in the company to work with separate portions of the product data. Say a mechanical engineer can work on the mechanical data at the same time as the electrical engineer works on the electrical data. However the cardinality of the part_data relation is "0..1" which says that a PartRevisionChangeLevel can have only one type of PartData. This clearly does not allow for concurrent independent work on individual portions of data and does not satisfy the intent of dividing Product Data. Hence I believe the cardinality of the part_data and the part_structure relationship should be "1 - many" and not "1 - 0..1" Thks Mangesh Mangesh Bhandarkar Sherpa Corporation email: mangesh.bhandarkar@sherpa.com tel #: 408-941-4705