Sequence diagrams

[Ian B Anderson]

Hello,
I was just wondering what size other people sequence diagrams were. The reason I�m asking is that mine seem to be huge! In the prepare use case I have at least 15 objects and three actors. The trouble is if I�m to show DAO objects and Fast Lane Reader patterns together with EJBs (not home and remote but Session and Entity) this diagram may grow even more and be even more messy.
In the SCEA guidebook they show DAO, Value objects and Session beans but they seem to assume Entity beans. (I.e. the Customer) But most importantly in the book all diagrams are very simple, no extra detail. I think this is something Sun are keen to get across, developers add detail not architects.
I appreciate everyone�s will be different but I just wanted to reassure myself.
Thanks in advance
Ian

[Ian B Anderson]

Hello,
Let me add to this question. There are two types of client swing/web so there are two ways to do anything. I drew my sequence diagrams showing one way, have other people included the GUI (not in detail, just like in the guidebook) or are people opting for the approach of ... when the client gets to here i.e. a request to process.
With the GUI the sequence diagrams look clutered, but the guidebook includes them
Any thoughts
Ian

[Jaspreet Singh UK]

I've had the same sort of problems you describe about your sequence diagrams and juts ended up splitting of functionality into other diagrams to reduce size.
This means more diagrams of smaller size.
Jas

[SC Johnson]

Did sequence diagrams that showed core for both web and application, then made sequences that showed pattern for web and app client to get to the "core".