boundary, control, entity

[H. Hafer]

Hi folks,

anyone used the uml elements boundary (for JSP), control (for BD, Facades) and entity (for all those entity beans) in sequence diagrams?

thanks,
Harbo

[D. Rose]

I do not plan to use it as these do not seem to add any more information.
IMHO we should use it only it adds value.

[H. Hafer]

Well, the added value is according to the help context of EA, that it makes clear, which elements serve as model, controller, or view in an MVC-paradigm.

Cheers,
Harbo

[Parag Doshi]

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

I am just too lazy

Parag

[D. Rose]

Hi Parag,

Very true!I also got very frustrated doing the said sequence diagram.
And only 12 marks?
I think marks are so less as there is less part of creativity there, just a chore.

I think MVC pattern is pretty much well established so unless and otherwise I am trying out something different , I would not use those elements.

[James Wang]

I only diagram JSP,servlet,and BusinessDelegate in Component diagram,not in sequence diagram.I prepare draw each JSP file in component. am I wrong?

[H. Hafer]

Originally posted by James Wang:
I only diagram JSP,servlet,and BusinessDelegate in Component diagram,not in sequence diagram.

James,

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 ]

[D. Rose]

I am not quite clear about how to draw component diagrams. I think they want to see JSP,EJB servlets etc.
Can I show component (e.g JSP) in other component ( may be view?)

[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?

regards,
Harbo

[James Wang]

H. Hafer,

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.

[H. Hafer]

Originally posted by James Wang:
For each use case, two sequence diagrams have to be drawed, one for web client and the other for the swing client.

Uh, yeah, you're probably right. I won't do it nonetheless, simply because they differ in presentation logic only which shouldn't be of great interest. At least, that's my excuse

Cheers,
Harbo

[Parag Doshi]

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.