CPlusOOP
SiteMap
OO Analysis
Problem Analysis
Sequence Diagram
«Prev
OO-Design
Problem Analysis
Review PLC
Purpose Scope Analysis
Problem Domain Classes
Identify Classes Objects
Class Diagram Notation
Diagram Associations
Basic Object Modeling
Multiplicity OO Modeling
Define Constraints
Modeling Aggregation
Modeling Composition
Modeling Generalization
Advanced Associations
Qualifiers Reduce Multiplicity
Many to ManyAssociations
Problem Analysis Conclusion
Sequence Diagrams
Sequence Diagram Notation
Applying Sequence Diagram
Applying Sequence Diagram-Quiz
Modeling Sequences Scenarios
Mapping Events Objects
Interfaces, events ,operations
Discover Attribute Information
Sequence Diagram - Conclusion
Interaction Diagram - Quiz
Model Reconciliation
Reconcile Sequence Diagrams
Test Interfaces
Model Refinement
Refactoring Patterns
Encapsulation Principles
Cohesion Coupling Defined
Attribute Responsibility Allocation
Class Description Operations
Refining Object Conclusion
Drawing the sequence diagram
Use one scenario as your source for the events and their order. Here we will use an activity diagram of the Choose Show use case to isolate one scenario. The red lines and activities identify one scenario (one logical path) in the activity diagram.
For the first event, choose the class from the class diagram that describes the object initiating the event. The initiating object may be in a class that represents an actor, the system itself, or one of the problem domain resources. In this case the initiating object is a Customer.
Draw the object at the top of the diagram.
Draw a timeline vertically from the object downward.
For each event, choose a class from the class diagram that describes the object best suited to receive and respond to the event.
Draw the object at the top of the diagram.
Draw a timeline vertically from the object downward.
Draw a horizontal arrow from the sending object's timeline to the receiving object's timeline.
Label the event line with the description of the event from the scenario.
If the event requires a response, then add an event arrow from the receiving object's timeline back to the sending object's timeline.
Label the return with the information that is returned. If the event simply returns control it is common to simply label the event return.
Repeat this procedure for each event until all events in the scenario have been applied to the sequence diagram.
Repeat this procedure for each event until all events in the scenario have been applied to the sequence diagram.
Repeat this procedure for each event until all events in the scenario have been applied to the sequence diagram.
Repeat this procedure for each event until all events in the scenario have been applied to the sequence diagram.
Repeat this procedure for each event until all events in the scenario have been applied to the sequence diagram.