sequence diagram
3 posts in topic
Flat View  Flat View

Posted By:   Martin_Coronel
Posted On:   Saturday, December 6, 2003 08:39 PM

Describe how one develops a sequence diagram from the use case

Re: sequence diagram

Posted By:   Anonymous  
Posted On:   Thursday, December 11, 2003 03:56 AM

You might want to create a sequence diagram directly from the Use Case when you are working on you application’s API. This is what Craig Larman calls a System Sequence Diagram and what UML calls High level Sequence Diagram.

Basically, the idea is to represent on your diagram the different inputs from user to the System as a black box. If the System returns any specific result, you show it on the diagram as well.

Based on these System Sequence Diagrams you clearly identify your System APIs (menus if you prefer). For each entry point, you will have an Operation Contract and then a Collaboration Diagram (or sequence if you prefer, as they are equivalent). But these last diagrams are using the identified classes and describe the actual interaction between the objects. They are the “usual” sequence/collaboration diagrams.

Craig Larman’s book I am referring to is presented and reviewed on our site:

In the “Practical Guides” section. The title is: Applying UML and Patterns

I hope it helps.



Re: sequence diagram

Posted By:   Anonymous  
Posted On:   Tuesday, December 9, 2003 11:13 AM

Can you explain why you want to do a sequence diagram, please?

Re: sequence diagram

Posted By:   Stephen_McConnell  
Posted On:   Tuesday, December 9, 2003 10:30 AM

Usually, you need to develop a Class diagram first. Create a class diagram with your objects.

Once the class diagram is developed, figure out how those objects inter-relate and how they need to behave.

Then you use the sequence diagram to describe the methods used and the sequence they need to be used to get the job done.

Stephen McConnell

About | Sitemap | Contact