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

Sequence diagrams and JSP (Part II)

 
Stanislav Suloev
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Good morning, Gentelmens!
Is it neccessary to show JSP on sequence diagrams?
If Yes then how to be with travel agents swing clients?
May be better choice is put JSP on sequence diagramm and to write in assumption that apropriate SWING screens wouldd be used if agent case.
Many tanks for any help.
 
Ajith Kallambella
Sheriff
Posts: 5782
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You have several options to consider.
  • Just show the user in the sequence diagram. Make sure you distinguish between different types of users - travel agent, passenger etc.
  • Abstract both the JSP/Swing as "View" and show different views in the sequence diagram. After all, this is what MVC is all about right? Search Flights View, Seat Maps View are some examples.
  • Show only the controllers in sequence diagram and document you assumption that client views ie., JSP/Swing implementations have their own controllers. Again, this is making use of MVC implementation. You can perceive some sort of abstract BaseController for each module hand have concrete implementations for each type of client - WebController and SwingController etc.


  • Note that sequence diagrams are documentation of messages exchanged between system components. You only need to highlight the differences if these messages change with the context - in your example, if all that a client is doing is to query flights, it shouldn't matter whether it is a web client or a Swing client. And therefore you can either ignore to show the differences in the diagram, or come up with a generic representation of a client. Infact, with a proper MVC implementation, your architecture should represent the same degree of "client agnostic-ness".
    Cheers,
     
    Dhiren Joshi
    Ranch Hand
    Posts: 463
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Hi Ajith,
    I need some clarification, I was of the opinion that sequence diagram needed only business use cases to be mapped and not the entire flow orginating from the GUI. Just showing the GUI as an actor was sufficient.
    Now I am confused from your post . Does it mean that I have to identify different actors with actual object names with a specific abstract JSP view name ?
    I was of the opinion that these detail would be identifed in the component diagram .
    Please clarify and clear my confusion.
    Thanks
    Dhiren
     
    Stanislav Suloev
    Greenhorn
    Posts: 11
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    To post Ajith Kallambella.
    Thanks! Now it is clear.
     
    • Post Reply
    • Bookmark Topic Watch Topic
    • New Topic