Originally posted by Corey McGlone:
I believe I've run into cases in which this does happen.
If you think much about the Order Item use case, you'd probably soon realize that, before you order an item, you should first query to make sure that the item is in stock. So, while the user is interacting with the "Order Item" use case, during part of that process, you'd be executing the same process as "Query Item In Stock." That would make it seem as if the Order Item use case was the "actor" of the Query Item In Stock use case.
My UML (and certainly my terminology) is a little rusty, but I believe this is considered a "depends upon" relationship (perhaps it's an include).
[ October 28, 2004: Message edited by: Corey McGlone ]
Originally posted by Sunder Ganapathy:
One thing that must be kept in mind is that Usecase diagrams are not the