Sequence Diagrams

  • Purpose
    • Model the logic of usage scenarios through the presentation of information passed between objects in the system, from the execution of the scenario
  • Description
    • Shows how objects and classes interact during one scenario
    • Used to show how the components of the user interface or software components interact
  • Key Features
    • Presents particular instances of each object, with a lifeline beneath each object, when it is created and destroyed
    • Specifies the order of events, not the exact time
    • Procedural Flow -> Sender does not act until the return message is received
    • Asynchronous stream -> Processing continues after sending signal
  • Usage Considerations
    1. Advantages
      • Used in oriented analysis of objects to validate the class diagram x use case diagram
    2. Disadvantages
      • Must be defined for each possible scenario, requiring a fully defined model of classes

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s