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
Now my time to give feedback to community, I passed SCEA 2 and 3 with 90%. I preapred around 12 pages documentation with sections as requirements summary, assumptions, architecture and design choices. One class diagram only few attributes shown for some of classess One component diagram with detailed J2ee components and design patterns hightlighted Seven Sequence diagram , 4 for each usecases, 2 for login and 1 for delegate and facade interaction
I spent 2 weeks on part 2 assignment. I took off from work. I do not have any big direct j2ee development and implementation experience. I have doen few small j2ee project but old java guy.
Part 3 was very easy, asking how you have handled this , that in your architecture.
1-Your class diagram only focuses in the domain classes or include controllers, DAO, or something like this. 2-How you approach the component diagram? separate component in packages for tiers? or only draw all components and his relations? in this diagram, did you draw all component with his exactly estereotype (you put Session Controller, or an EJB with the function of session controller), i have very clear my model, but i some doubts about how draw the component diagram
SCJP<br />SCWCD<br />SCBCD<br />SCEA(preparing for Part II)
My class diagram only focussed on business domain entities. My component diagram was single diagram, and all components were left to right with relations. All components were streotyped with actual implementation tag like SFSB, SLSB, POJO and DesignPatterns names etc...
That which doesn't kill us makes us stronger. I think a piece of pie wouldn't kill me. Tiny ad:
Free, earth friendly heat - from the CodeRanch trailboss