Quote: I think my main question centres around the correct technique for defining 'foreign' stuff in the UML model (end of quote)
Well I would just typically define a dependency from the StaffService to the PictureService and then just do whatever I needed to retrieve the picture information. Of course if your only concern is the fact you don't want to rewrite code, you could always have a util class that handled the picture stuff and have that shared across the service implementations. Quote: 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> (end of quote) Why wouldn't you be able to just have your EmployeeVO use the PictureVO from the other package? You can always model the coupling between the two VOs with a dependency for example and nothing would be generated between them. Or if your EmployeeVO needed a reference to the PictureVO you could just draw an association between them and the reference would be generated. -- Chad Brandon - [EMAIL PROTECTED] http://www.andromda.org _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1446#1446 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
