Hi, You need not show all the dynamic aspects of your system. Actually, it won't be possible to do this without having a lengthy or cluttered diagram. Choose what you want to illustrate through the sequence diagrams, document it and follow it consistently across all your sequence diagrams. If you feel that your diagram misses some important points, you could provide supplementary diagrams to illustrate the missing points. regards Sridhar
One way to reduce clutter but still include all the deails is by using "notes". UML diagrams allows notes to be anchored to one or more entities in the diagram. For instance, you can show a message from a session bean to an entity bean instance and include a note in between that says "session bean uses service locator to get the entity bean home". Notes worked very well for me and Sun did not have any issues with them. Cheers,
Open Group Certified Distinguished IT Architect. Open Group Certified Master IT Architect. Sun Certified Architect (SCEA).
There will be plenty of time to discuss your objections when and if you return. The cargo is this tiny ad:
SKIP - a book about connecting industrious people with elderly land owners