• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Part II: Howmuch servlet&UIClient stuff in diagrams

 
HenkGijsbert
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,
Until now I have made a first version of my diagrams, only bothering about the business logic. I have only depicted different servlets in the sequence diagrams to show from where calls to session beans (can!) originate.
I wonder have much of UI information must my diagrams have and where do I show it? So I have the following questions:
1) Can I suffice with showing the swing client just as a component without specifying the classes of which it consist?
2) Can I showing one servlet component on the webtier, containing the different servlets I use in my sequence diagrams. Or do I have to make a component of every servlet? Do I have to show servlets in my class diagrams?
3) Do my diagrams have to show how MVC is applied showing controler servlet- and session part in class diagram? Or can I abstract from that and concentrate on business logic and take MVC for granted.
4) I saw that JIGNESH1 SHAH got a 100% score with a class diagram that does not show EJB's(JIGNESH, congretulations). Can someone (maybe JIGNESH if you read this) explaine how a class diagram without EJB's can be consistent with a solution that has EJB's. Or must you just show entity beans like 'Flight' in the class diagram without specifying that you will make an entity bean of if.
Thanks in advance,
Henk van Jaarsveld
SCJP, SCJD
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic