• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

Showing web and swing clients on the same sequence diagram...

 
Ranch Hand
Posts: 194
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi guys,

I have been creating my sequence diagrams so far showing the interactions of the web client with the system, i.e. showing which JSP's etc, are used and how they are used.

I am thinking about adding my swing clients onto this diagram in some way as well but I am not sure how to do this, if I created a client agnostic diagram it would be too general i think and there is a fair amount of web interaction to model. I do not really want to have to draw all new diagrams for a swing client.

Does anyone know of a good way to have one diagram show the interactions from a web and swing client point of view without being too general?

Any help and comments will be greatly appreciated!

Thanx all!

Regards,
James.
 
Sheriff
Posts: 5782
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
One option is to use stereotypes.

Other option is to show them separately in two sequence diagrams; elaborate the common flow in one sequence diagram and simply refer it from the other(short) sequence diagram using the << include >> convention.

The third option would be to use and architectural level of abstraction that handles requests from various types of clients and serves them responses - a GenericRequestHandler and a GenericResponseDispatcher. If you adopt this approach, make sure you write about them in your documentation.
 
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic