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.
Last week tuesday, June 17th, I took part III, and today I checked certmanager site and found this: Grade: P Score: 75 Comment: This report shows the total points that could have been awarded in each section and the actual amount of points you were awarded. This information is provided in order to give you feedback on your relative strengths on a section basis. The maximum number of points you could have received is 100, minimum to pass is 70. Class Diagram (44 maximum) .......................... 31 Component Diagram (44 maximum) ...................... 32 Sequence/Collaboration Diagrams (12 maximum) ........ 12
Thanks to all of you for answering my questions, and discussions about the requirements. Guess nowits time for [ June 26, 2008: Message edited by: Marcel Dullaart ]
I see that you got perfect score on the sequence diagrams. Can you share with us your experience doing them?
Joined: Nov 07, 2007
Thank you all for responses, even Cameron
It would be great if you can share your Part II/III experience and approach.
For part III I took the questions listed in this post.
Regarding the assignment I think it is always wise to use a proper tool for creating your model. Something like Rational Rose, Sparx EA, StarUML, etc. But the tool must at least ensure that your model is in sync. This way every identifier is consistently named across your class diagram and sequence diagrams.
At first I read the assignment several times, keeping notes of the inconsistencies and unclear requirements. Some of these un-clarities were explained further down, or hidden deeper in the description. Others were just unclear, so i made my own assumption about it and tried to keep these consistent in the model.
I used UML 2.1 in my models and have the sequence diagrams split up in parts, where a top diagram for each use case was used to show the inter action of the actor with the system. Each method in the top level diagram was detailed on its own detail sequence diagram, that showed the interaction within the system for the function.