(responding to lars hagrot)
> When You make a sequence diagram and want to show how two > objects interact the client object may be dependent of an > interface, which will be implemented by a serving object. How do > You usually show this? By showing the to objects and the > interface in between or in som other way? For the more abstract diagrams, (analysis and possibly early design), you wouldn't show the interface, the messages would go direct to the implementing object. Once the behaviour is partitioned into components with interfaces, you can choose to show the messages from one component or its elements going to the interface of another component. For detailed design you almost certainly would choose to do this. It's a matter of style how this is done, but I prefer, when I show calls to the interface of a component, not to show what goes on behind the interface in the same diagram. I would show this in a separate diagram. This will, of course, depend on the purpose of the sequence diagram; is it to show the detailed workings for a single component of the system, or is it to show the end to end behaviour of the whole system for a single use case scenario? HTH, Paul Oldfield ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ www.aptprocess.com any opinions expressed herein are not necessarily those of Mentors of Cally or the Appropriate Process Movement ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Post or Reply to: [EMAIL PROTECTED] * Subscription Requests: [EMAIL PROTECTED] * Archive of messages: * http://www.rational.com/support/usergroups/rose/rose_forum.jsp * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * To: [EMAIL PROTECTED] * Subject: <BLANK> * Body: unsubscribe rose_forum *************************************************************************
