Last week, we had the author of TDD for a Shopping Website LiveProject. Friday at 11am Ranch time, Steven Solomon will be hosting a live TDD session just for us. See for the agenda and registration link
The maximum number of points you could have received is 100, minimum to pass is 70. Class Diagram (44 maximum) .......................... 38 Component Diagram (44 maximum) ...................... 33 Sequence/Collaboration Diagrams (12 maximum) ........ 10
Mostly lost points in component diagram since did not talk about application client. Just mentioned that I suppose.
Cade's case study Java Pet Store Core J2EE Design Patterns Design patterns by Gang Of Four Closely studied posting in java ranch forum (Mostly the posting in 2004 and early 2005)
Regarding class diagram
I altered the BDM Splitted certain sequence diagram to make the flow clear and not to make it exhaustive in 1 page Added notes to components. Add only high level components. Just added a comp saying application client and I think I might have lost mark on this
Briefed all my assumptions in Architectural documentation.
Overall my thought would be to take into consideration and specify about application client in all diagrams rather than just noting it down in architectural document.
All the Best
this is supposed to be a surprise, but it smells like a tiny ad:
free, earth-friendly heat - a kickstarter for putting coin in your pocket while saving the earth