Topic
  • 2 replies
  • Latest Post - ‏2006-03-05T14:56:27Z by ScottAmbler
SystemAdmin
SystemAdmin
1130 Posts

Pinned topic Creating Sequence Diagrams

‏2006-03-03T08:53:24Z |
Hi
I'm working on the Requirement capture phase , and want to create a sequence diagram for a certain the Process,

Pl let me know how to go about it, and also what is the difference between
sequence diagram for the Process during Requirement capture, and Design..

Thanks
Updated on 2006-03-05T14:56:27Z at 2006-03-05T14:56:27Z by ScottAmbler
  • SystemAdmin
    SystemAdmin
    1130 Posts

    Re: Creating Sequence Diagrams

    ‏2006-03-03T15:39:17Z  
    A sequence diagram is composed of instances and their interactions. To create a sequence diagram, you need something to have an instance of.

    You say you are in requirements capture. What things have been identified in your process that you can make instances of for the sequence diagrams? Do you have business objects, entity/boundary/controller classes, or architectural/design items such as components, agents, or services?

    IF you have none of these, then you have two choices - create activity diagrams for your process or make a sequence diagram with one object representing the system and show the interactions between the system object and the actors.

    If you do have some things identified, you can put instances of those things (business objects, components, etc.) on your sequence diagram and describe your process as the interaction between those things.

    Sequence diagrams can evolve throughout the project by adding more instances representing design solutions.

    If you are struggling with this, then you need to read an Object Oriented Analysis and Design book for more discussion on creating sequence diagrams. The topic is not that simple that it can be explained in a few lines in a forum.

    Geri

    http://www.wyyzzk.com/
  • ScottAmbler
    ScottAmbler
    92 Posts

    Re: Creating Sequence Diagrams

    ‏2006-03-05T14:56:27Z  
    It always depends on style of course, but a "requirements sequence diagram" may look something like http://www.agilemodeling.com/artifacts/sequenceDiagram.htm#Figure1 whereas a design diagram may look like http://www.agilemodeling.com/artifacts/sequenceDiagram.htm#Figure4BasicCourse (or even more detailed).

    Geri is right, you might want to pick up a good intro to OOAD book.

    • Scott
    http://www.ambysoft.com/scottAmbler.html