Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

do we need to show JSP's in sequence diagrams

 
Dhiren Joshi
Ranch Hand
Posts: 463
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a question whether JSP's NEED to be SHOWN in the sequence diagrams.

I had read in posts that many SCEA's had made sequence diagram at the business use case level which didnt involve JSP's or web frame work. They showed a separate diagram for the web farmework so as not to repeat it in every seqeunce diagram.
I want to just confirm if that is correct.

Thanks
Dhiren
 
Josep Andreas
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dhiren,

I am thinking of doing the same, allthough I am not quit
sure yet. Its the only way to prevent ending up with a large sequence diagram

But the Parag thread keeps me in doubt:
=============================
Seq diagram- 5 in total. One for each use case. 2 for pay itinerary (credit card and mileage had their individual seq diagrams). Showed jsps, controllers, request handlers, business delegates, session facades, etc, etc. In short, the whole nine yards !
=================================

When you show: Customer, multiple JSPs, weB Controllers, eventHandlers, business delegate(s)(?); your page is already more than half full.
I am trying to figure out how this can be done?
Maybe leave out the TOs and add a note?
That he added requestHandler also confuses me. I am just putting in the ApplicationController (without requesthandlers).

You could also add a separate diagram for web-tier

I have now a sequence diagram with 20 items in it;
looks OK, but I do not know if it is acceptable.
I even put in the signonfilter.

J
[ February 19, 2005: Message edited by: Josep Andreas ]
 
Dhiren Joshi
Ranch Hand
Posts: 463
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Josep,
I read some old post where they did only business level sequence diagram and didnt mention JSP's.
Currently I have it done like this.
Here is some hope for us. I dug up some old SCEA POSTs.


posted June 10, 2003 01:11 PM
--------------------------------------------------------------------------------

quote:
--------------------------------------------------------------------------------
Originally posted by Louis Fegun:
Hi Alain-
Congratulations!!!. Thanks for sharing your insight on the assignment. Quick question for you. Do you have to show all the classes bearing the pattern and framework - e.g. Business delegate, Service Locator classe, etc, in the sequence diagram. My sequence diagram is already looking very long because of many classes and I am trying to control it.
I will appreciate any suggestions on this.

Thanks.

Louis.


--------------------------------------------------------------------------------

In my sequence diagram I had all classes of the class diagram + one frontend subsystem (that encapsulates all classes when the frontend is Java client and all JSP, Servlets, Java Beans when the frontend is a Web Client). In doing so I have no Servlets, JSP, etc. in the sequence diagram and also no VOs, DAOs, etc. A sequence diagram may show the interactions between 15 objects but this is reasonable. The J2EE patterns are not explicitly shown in the sequence diagram.


Take a look at this link
alain Huisungs Post
Now I am sticking to what I have no JSP request processor etc.
HTH
Dhiren
[ February 19, 2005: Message edited by: Dhiren Joshi ]
 
Josep Andreas
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sounds reasonable.
The frontend could be called Frontend or webtier or something alike.
You could label an arrow back to the user with the JSP name.

I really would like to show the functions of servicelocator
and signon filter.
(for some reason, use of servicelocator is really stressed in Cade's Guide,
it is displayed in both component and sequence diagram).

I think I do the same as with component diagram: Put one Object in that I call
JSP and then label the arrow to customer with JSP name.

(I think the diagram then will fit on 1 landscape printed page; I really hate those diagrams that do not fit on 1 printed page )
[ February 20, 2005: Message edited by: Josep Andreas ]
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic