Thats how I figure it makes most sense and how I'd do it if I'd handcrafted all the code inside the StaffService. I think my main question centres around the correct technique for defining 'foreign' stuff in the UML model
For example inside the StaffService where I build up an EmployeeVO which includes a PictureVO object, is there a way I can represent the PictureVO type (which is defined in another package) inside my UML without needing to explicitly define it there also as a <<ValueObject>>? -- Audere est Facere _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1445#1445 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- 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
