• Post Reply Bookmark Topic Watch Topic
  • New Topic

Retire Early sequence diagrams

 
Sergio Aragon
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Hi

Do I need to create one sequence diagram for a successful flow and a second sequence diagram for a failure flow (alternative flow if an exception occurs)?
per example, communication with an external system


Kind regards
 
Jeanne Boyarsky
author & internet detective
Sheriff
Posts: 36032
432
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes. Major flows should have separate sequence diagrams.
 
Katrin Perry
Ranch Hand
Posts: 61
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I didn't create alternative sequence diagrams for failure scenaros.
I did where possible create one sequence diagram per use case. In some cases though, the use case was long and inluded 2 different logical scenarios (i.e. Buy at current price / Buy at set price) In those case I had 2 sequence diagrams.

I hope this helps.
 
Jeanne Boyarsky
author & internet detective
Sheriff
Posts: 36032
432
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you long sequence diagram has alt flows, that's ok too.
 
Gravity is a harsh mistress. But this tiny ad is pretty easy to deal with:
the new thread boost feature: great for the advertiser and smooth for the coderanch user
https://coderanch.com/t/674455/Thread-Boost-feature
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!