• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Split up sequene diagrams

 
Luke Murphy
Ranch Hand
Posts: 300
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
HI,
I am just wondering is it better to split up sequence diagrams into:
- interaction between Customer and Web Tier,
- interaction between Web and EJB Tiers
- EJB and other Tiers.

Or is it better to just have one sequence diagram showing all tiers at the sametime?

Cheers
 
Mika Tapanainen
Ranch Hand
Posts: 95
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

I think it is better to have one use case in one diagram. Otherwise it could be difficult to understand the use cases from the sequence diagrams.

BR,

Mika
 
K Abhijit
Ranch Hand
Posts: 88
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sequence diagram is for Technical guys so Use a single Sequence diagram as it gives entire end to end flow of the system; unless it become too complex to decipher it where you've to cut down few logical interaction into separate one...

You can also think of having it represented as Activity Diagram with swimlanes to underline the Actors/Component boundaries...
 
Luke Murphy
Ranch Hand
Posts: 300
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Resolved. I agree.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic