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.
Many Congrats !!! Very nice new year gift for you.
Can you throw some light at broad level on your overall approach, organization of deliverable etc.
Joined: Mar 17, 2004
My solutions consisted of 1) main HTML document 2) one class diagram 3) 4 sequence diagrams - one for each use case 4) component diagram 5) deployment diagram
Details 1) Contained my architectural choices, decisions, assumptions and verbal description of some of the diagrams 2) I had one class diagram with approximately 20 classes; technology independent 3) technology independent - using a lot of stereotypes - view, controller, entity etc. later on stated how views, controller are implemented for the java client and for web client 4) grouped components by tiers not by subsystems 5) provided deployment diagram even though it wasn't required - not a lot of work anyway
My major problem wasn't really solution and how to do it (technology wise). I have enough experience with J2EE and also think that my knowledge is on decent level. I had major problem in realizing how much details to provide in my solution and also the format. I was mostly concerned about component diagram as I can see now - there was a reason to be concerned. I am not sure if it was the content or the format of the component diagram that evaluator didn't like (that's where I lost all my 11 points).
I have to admit preparing for the certification made me think more about how other people can read my design and how to prepare it so it is easy for them to read it, especially when you don't know your audience.