[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [xtm-wg] Modified diagram for Association Template
Daniel It was definitely the 1 that bothered me! Apologies, I should have made that clear. Chris -----Original Message----- From: Daniel Rivers-Moore [mailto:daniel.rivers-moore@rivcom.com] Sent: 09 January 2001 19:44 To: xtm-wg@egroups.com Subject: RE: [xtm-wg] Modified diagram for Association Template The association template places constraints on the classes of object that may play each role in the association. There may be more than one permitted class of player for certain roles. For example, the role of "employer" in the "employer-employee" association may be played by a person or an organization. The employer-employee template might have the class "person" as the class of player of role "employee", and the classes "person" and "organization" as the classes of player of role "employer". Does that answer your query? Or was it the 1 that bothered you, rather than the * ? Daniel -----Original Message----- From: Chris Angus [mailto:chris.angus@btinternet.com] Sent: 09 January 2001 12:09 To: xtm-wg@egroups.com Subject: RE: [xtm-wg] Modified diagram for Association Template Daniel I do not understand why the 'class of player' cardinality is shown as '1..*'. Chris -----Original Message----- From: Daniel Rivers-Moore [mailto:daniel.rivers-moore@rivcom.com] Sent: 09 January 2001 09:38 To: 'xtm-wg@egrouops.com' Subject: [xtm-wg] Modified diagram for Association Template Attached is a modified graphic for the conceptual model of Association Template. It is structurally identical to the previous diagram. However, it renames some of the elements to make it clearer that the association template is itself and association, the role constraints are themselves a role in the template association. An alternative approach would have been to add subtype-supertype arrows from the left and middle boxes in the top row to the corresponding boxes in the bottom row. However, this makes for a cluttered diagram which is less easy to understand, and results in a larger number of named object types in the conceptual model and therefore more to do in the mapping between the model and the syntax. <<cd.AssociationTemplate.20010108.gif>> Daniel To Post a message, send it to: xtm-wg@eGroups.com To Unsubscribe, send a blank message to: xtm-wg-unsubscribe@eGroups.com To Post a message, send it to: xtm-wg@eGroups.com To Unsubscribe, send a blank message to: xtm-wg-unsubscribe@eGroups.com To Post a message, send it to: xtm-wg@eGroups.com To Unsubscribe, send a blank message to: xtm-wg-unsubscribe@eGroups.com To Post a message, send it to: xtm-wg@eGroups.com To Unsubscribe, send a blank message to: xtm-wg-unsubscribe@eGroups.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC