CSE 110 Software Engineering Inc.

Screen Sequence Diagram

A sequence diagram is an interaction diagram that shows how objects operate with one another and in what order. A sequence diagram shows object interactions arranged in time sequence. It depicts the objects and classes involved in the scenario and the sequence of messages exchanged between the objects needed to carry out the functionality of the scenario. Sequence diagrams are typically associated with use case realizations in the logical view of the system under development

    There is a one to one correlation between each use case and a sequence diagram. Sequence diagram in a general sense shows the steps that are taken after each page and the potential results based on user choice or system functionality.
    • It is an end to end depiction of a functionality from inception to the end result as the user might see or a functionality that could occur due to this process.
      • It provides a visual aid for stakeholders to see the path and directions of a functionality.
      • The reason the sequence diagram is so useful is because it shows the interaction logic between the objects in the system in the time order that the interactions take place.

Instructions in Creating the Artifact

This instructions are inetended to give you a better scope of what a good Screen Sequence Diagram could be like rather than a sole resource for the artifact of your project. You may need to tailor it and make several other changes to ensure it is a good fit for your use and project.

Legend: Describing each shape and drawing used in the Screen Sequence Diagram.
Shapes: Each shape should correspond to a specific type of technology or infrustructure. For example cylinder could depict database.
Arrows: Depict the action or relationship between two object or pages that are connected through the arrow. Method and file names: When files and methods are called, denote the names. For example, login() in the HandleLoginRequest.js shape.

Things to keep in mind.

  • Make sure you have a legend describing the conventions that you used.
  • Keep naming consistent as before.

Examples of Screen Sequence Diagrams.