Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Sequence Diagram chaining use cases

 
don brown (aka brownie brownie)
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Once you've done one use case as a sequence diagram, how do you show that the last step is to kick off another use case?

As far as i can see the options are to make the second use case an actor or an object (a business delegate perhaps) and then make the last step of the first sequence diagram call a method on the object/actor to "execute the use case".

What's a folks' thoughts on this?
 
Laxmi Raghu
Ranch Hand
Posts: 218
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I represented use case as a object but used stereotype saying that it's another use case. I passed the exam but didn't score good marks though.
 
Joel Schnider
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would just place a note near the last step, mentioning that another use-case is initiated at that point.

Unless it is absolutely necessary for it to be graphically depicted, like say the whole thing is happening under one huge transaction or something. Even then, perhaps a UML note would suffice instead of inventing stereotypes!

Thats just my opinion.


Originally posted by brownie brownie:
Once you've done one use case as a sequence diagram, how do you show that the last step is to kick off another use case?

As far as i can see the options are to make the second use case an actor or an object (a business delegate perhaps) and then make the last step of the first sequence diagram call a method on the object/actor to "execute the use case".

What's a folks' thoughts on this?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic