File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Split up sequene diagrams Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Split up sequene diagrams" Watch "Split up sequene diagrams" New topic

Split up sequene diagrams

Luke Murphy
Ranch Hand

Joined: May 12, 2010
Posts: 300
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?

Mika Tapanainen
Ranch Hand

Joined: Jun 11, 2009
Posts: 95

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.



K Abhijit
Ranch Hand

Joined: Mar 03, 2008
Posts: 88
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...

“The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'.”
Luke Murphy
Ranch Hand

Joined: May 12, 2010
Posts: 300
Resolved. I agree.
I agree. Here's the link:
subject: Split up sequene diagrams
It's not a secret anymore!