I am concerned about the level of details in the sequence diagrams for Part-2. Can someone clarify as to what are the different techniques that can be used to avoid cluttering sequence diagrams in the wake of following points.
- Do we need to show all the interactions right from View to persistence tier for every use case action like Cade's diagrams?
- Repetitive common interactions among components like View-Front controller-Request Processor, Business Delegate-ServiceLocator-Facade etc., for each use case action. [ November 12, 2006: Message edited by: Durgaprasad Guduguntla ]
Would be nearly impossible to depict all interactions from jsp to backend. Based on postings on this forum, I noticed that most people did shortcuts especially on the client/presetation tier side, ranging from representing the whole web GUI as a "subsistem". Others didn't detail the jsp-s, etc. Bottom line is that you want to represent what is esential for understanding your system and explain the rest. If you are like me, you will go through several iterations until you settle with a clean, simplified version.