This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
You can use a Actor to show the other use case and send a message to that actor indicating the execution of that use case
Joined: Aug 08, 2005
Excellent Idea! I can see how that would work well but, I am concered about representing anything other than an actual user or system as an actor...sorta referencing my experience and also "UML Distilled" for the basis of this concern.
I think UML can be changed to do what you need with it -but- I would like to hear a few more ideas before taking one route or another.
Currently, I have a couple notes on the page at the bottom of the sequence diagram but that seems wrong too...
Any other ideas out there?
Joined: Jul 05, 2005
When you say "an actual user or system as an actor...", think of the use case as a (Sub) System...