I did not add those elements, mainly, because I got pretty pissed off creating the Prepare Itinerary seq diagram and lost interest in the rest, as it carries only 12 marks and its a lot of pain to go thru the entire seq diagram process
Originally posted by James Wang: I only diagram JSP,servlet,and BusinessDelegate in Component diagram,not in sequence diagram.
I'm in the mood of doing it the other way round. Why should I show the interaction between entity beans in their struggle to find a route from A to B? That's basically a routing algorithm. So I'm tempted to just show the interaction between JSP, Controller, BD and Facade (and probably some VOs) in sequence diagrams and to omit the details of accessingthe involved entity beans.
On the other hand, the process of creating those damn sequence diagrams just exposed some flaws in my component diagrams.
cheers, Harbo [ September 03, 2004: Message edited by: H. Hafer ]
Originally posted by D. Rose: I think they want to see JSP,EJB servlets etc. Can I show component (e.g JSP) in other component ( may be view?)
Yep, my comment of "doing it the other way round" was misleading: Surely I'll show all components in the component diagrams. What I was trying to say was that I'm reducing the level of details in seq. diagram to the bare minimum. E.g. the hassle of find a route between departure A and destination B is burried in a helper class.
Which raises a question: How to show those helper classes? Are they stateless session beans, too?
if jsp, controller and bd is exist in sequence diagram, then the swing component should also be draw in sequence diagram. If so, I think I have to design more sequence diagrams. for each use case, two sequence diagrams have to be drawed, one for web client and the other for the swing client.
I would not spend too much time on sequence diagrams..class diagram and component diagram has the bulk of the marks..I would rather spend time on refining and making them look good.Besides, there isnt enough information on the swing app, anyway.