• 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:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Questions about sequence diagrams ??

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

I am creating sequence diagrams for the SCEA assignment.
When I look at the sequence diagram my diagram extended for
about 10000000000000000 km in width ? I am using an MVC 2
framework for this my project. Most of the description is gone
describing the internal framework transitions. Is it legal to replace
all that with a just one object in the sequence diagram which "Prensentation Tier" for example.

Thanks a lot in advance.
 
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I wanted to point out the following article:
http://www.ibm.com/developerworks/rational/library/3101.html
Apparently, UML 2 offers the ability to reference another diagram. I'm using this feature to break up some of my longer sequence diagrams into smaller, more readable diagrams.

As to how much frame mumbo jumbo to show, I'm kinda wrangling with that myself. On one end of an extreme, too little information and your developers won't know what kinds of technology are going on at various parts of your diagram. At the other end of the extreme, the more unimportant framework classes you involve in your diagram, the more likely your important ideas will be lost in all the details. I'm afraid I don't have good advice on this point, as I'm still struggling with it myself.
 
Ranch Hand
Posts: 208
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I solved the problem by not using sequence diagrams at all, but rather collaboration diagrams. I find them much easier to make presentable and readable, despite the tendency to have message indexes like "1.1.1.1.1.1.1.1.1.1.1" etc...
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic