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
Class Diagram 42/44 Componenet Diagram 34/44 Sequence Diagram 11/12
Don't know why I lost 10 points in Component diagram. I went with one diagram, seperated each tier, shown all patterns used. Followed the Pet store mostly, went with my own where I thought pet store doesn't make sense for myne.
I have gone throught the discossions in this form and found it very usefull. Thank you all.
I had about 15 classes and I showed all the business functionalities, including external interfaces as interfaces, that helped me to make the class diagram technology neutral.
1. Did you show the different JSPs in the Component diagram?
I showed a generic ui element and listed the individual jsps in the uml note attached
2. How did you show the link between the use cases in the sequence diagram? Like after prepare Itinerary is being called and the navigation goes to the Price Itinerary.
I showed any refernced use case as an Acton in the SD
3. TransMaster integration - would you be able to shed some lights on this?
I don't know how much we can discuss about specific's in this form. But I can tell to that I wouldn't go deep into the detailed implementation of any external interface. I will simply have the component developer deal with the details of the implementation. As an architect and designer of the system, just say what interface is required and what protocol to follow.
1) Did you show how the transaction will be handled while calling TransMaster API ? 2) Did you explain how you will be updating "frequent flyer mileage system" database transactionally (will this be a call to the frequent flyer mileage system database or a call to the existing web page for the system) ..?
I didn't show any specific in the diagram on that front. But I did mentioned about it in my detailes description. The description includes what are the options available and why I would prefer one to another. Again mentioned clearly that in implementation for the same requires more information than provided so far and so leave it to the implementation time.
How did you do the state management for the Java client. Did you use an SFSB or client side management ? Could you also refer some sources where I can find examples showing state management using java client or SFSBs.
In which of the two diagrams(component or sequence) did you show the DTOs. Cade's component diagram doesn't show any DTOs.
In my opinion, the State management for the java client depends on how the java client is connecting to the business tier. if the client connects directly to the business tier, I will prefer to have the sesion managed locally on the client and not on the server. But if the client connects to the business tier through a common web front, then I would prefer manage using the SFSB on the business tier.
Again there is no hard and fast rule, but need document clearly, your choice and why.