||I hope I make sense here, .. I think association classes are extremely ||well suited in this case (just need to draw an association from this ||association class to 'regional office' and we're done), but I don't see an ||equally well-designed alternative without using such class
[Ciesielski] You mean something like this: User (1)------(0..*) User2RoleAssignment(0..*)-----(1) Role User (1)------(0..*) User2OfficeAssignment (0..*)-----(1) Office And you want to add relation from User2RoleAssigment to Office? In this way you still have two connections from User to Office - wouldn't be better to associate User2RoleAssigment with User2OfficeAssigment? Regards, Wojtek ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
