This week's book giveaway is in the Design forum.
We're giving away four copies of Design for the Mind and have Victor S. Yocco on-line!
See this thread for details.
Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Sequence diagram: The Best Way to learn

 
Gerald Davis
Ranch Hand
Posts: 872
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I like to believe that I have a complete understanding of sequence diagrams, but there are things that I don�t quite understand about them. For me, the most complete way to understand sequence diagram is to compare it with code.

I need either a book, online example or a UML tool that converts sequence diagram to code.

I don�t want no easy to understand sequence diagram tutorial using mobile phone or making a dang cup of tree or someone go tell me that design and coding are two separate things.
 
Ian Roberts
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Gerald,

Sequence diagrams are used at various stages of the development life cycle and are used to present high-level interactions in the support of use cases, sub-system interaction for the application architect at analysis level and a much more detailed and object-based interaction at developer level. The reference to using code to understand a diagram has led me to assume that you are creating sequence diagrams at the developer level and are defining method signatures? Like all UML artifacts used in OOAD, the sequence diagram is best started at an abstract level before going into much more finer detail.

The only solution is undoubtly practise. But it is very easy to assume that when you create a sequence diagram the code must reflect it perfectly and therefore the diagram must be 100% correct. This is not quite true and why OOAD is an iterative approach. Although you may have a "perfect" sequence diagram that you believe is right, once the developer starts actually coding from it he may find that he has to make slight alterations etc. in order to produce the best result. This can be fed back into the design process as a refactor of the model but you can also end up spending most of your time maintaining code and supporting models. Dynamic models are often throw away once the code has been completed because it is rare that they reflect the actual result. There purpose, to present a graphical guidance of the object interaction for a particular use case or function.

Ian R.
 
Dan Drillich
Ranch Hand
Posts: 1183
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Gerald,

A good explanation about sequence diagrams is at http://www.agilemodeling.com/artifacts/sequenceDiagram.htm

Rhapsody, the UML tool, of I-Logic integrates sequence diagrams into the development/testing process. It is a _very_ expensive tool but you can have the 30-day trial version at http://www.ilogix.com/rhapsody/rhapsody.cfm.

Regards,
Dan
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic