This week's book giveaways are in the Refactoring and Agile forums.
We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

jsp in sequence diagram

 
Parag Doshi
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In Cade's book, the JSP's are named as BrowseCatalogJSP,ProductPageJSP etc and in core J2EE patterns, I had seen jsp pages shown with <<jsp>> stereotype. Which is the better alternative or does it even matter if we choose either of the 2 conventions?

Parag
 
H. Hafer
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Parag,

I named the JSPs fooForm and barForm to underline their functional character (as being forms) and stereotyped them <<JSP>> to underline their technical character (as being JSP pages).

HTH,
Harbo
 
Ramon Gill
Ranch Hand
Posts: 344
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Parag,
It doesn't really matter which convention you choose, sa long as you make you diagrams easy to understand. However, I do like the sterotype of << JSP >> , as this clearly shows what type of page is being used.

Ray
 
D. Rose
Ranch Hand
Posts: 215
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I also like <<jsp>> stereotype for better clarity
If we decide to change the view component, I can still use it, just change stereotype!
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic