This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi all, My sequence diagram is growing rapidly and I understand that it can be pretty difficult for marker to review. Is there a rule that there MUST be one sequence diagram for one use case? If not is there a way to horizontally split diagram? Can I simply create let's say 3 sequence diagrams for one use case and somehow indicate order? If yes, can somebody point me to example or explain how to do it? Thanks
Hi Mr Cirip I wouldnt worry too much about the sequence diagrams *growing 2fast*. Most of my SD's contained around 50-60 objects on them. I got full marks for my sequence diagrams. As long as you use the correct annotations with respect to forwarding requests to other SD's you will be okay. Remember also to correctly ensure your SD's relate to both ur Class and Component diagrams otherwise you will loose marks.