100% found this document useful (1 vote)
461 views4 pages

System Sequence Diagrams

This document discusses system sequence diagrams (SSDs) and sequence diagrams, which are used in object-oriented analysis and design. SSDs depict the interactions between external actors and a system as a black box, showing the sequence of events but not internal objects. Sequence diagrams show interactions and message passing between specific objects and classes. The document provides examples of SSD notation including actors, objects, lifelines, and messages. An example SSD for a "Process Sale" use case is shown.

Uploaded by

Karthik Sara M
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
461 views4 pages

System Sequence Diagrams

This document discusses system sequence diagrams (SSDs) and sequence diagrams, which are used in object-oriented analysis and design. SSDs depict the interactions between external actors and a system as a black box, showing the sequence of events but not internal objects. Sequence diagrams show interactions and message passing between specific objects and classes. The document provides examples of SSD notation including actors, objects, lifelines, and messages. An example SSD for a "Process Sale" use case is shown.

Uploaded by

Karthik Sara M
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

IT310- OBJECT ORIENTED ANALYSIS AND DESIGN

SSD versus Sequence Diagram


A System Sequence Diagram is an artifact that illustrates input and output events
related to the system under discussion.

System Sequence Diagrams are typically associated with use-case realization in the
logical view of system development.

Sequence Diagrams (Not System Sequence Diagrams) display object interactions
arranged in time sequence.

Sequence Diagram
Sequence Diagrams depict 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 system.

Sequence diagrams can be used to drive out testable user interface requirements.

SSD - System Behaviour

System behaves as “Black Box”.



Interior objects are not shown, as they would be on a Sequence Diagram.

System

System Sequence Diagrams are

Use cases describe-



How actors interact with system.

Typical course of events that external actors generate and



The order of the events.

For a particular scenario of use-case an SSD shows-

The external actors that interact directly with the system.

The System (as a black box).

The system events that the actors generate.

The operations of the system in response to the events generated.

System Sequence Diagrams depict the temporal order of the events.

IT310-OOAD Page 1
IT310- OBJECT ORIENTED ANALYSIS AND DESIGN

System Sequence Diagrams should be done for the main success scenario of the use-case,
and frequent and alternative scenarios.

Notations

Object:

Objects are instances of classes. Object is represented as a rectangle which contains the
name of the object underlined.

Because the system is instantiated, it is shown as an object.

:Object1

Actor: An Actor is modeled using the ubiquitous symbol, the stick figure.

actor 1

Lifeline: The LifeLine identifies the existence of the object over time. The notation for a
Lifeline is a vertical dotted line extending from an object.

Message: Messages, modeled as horizontal arrows between Activations, indicate the


communications between objects.
messageName(argument)

Examples of SSD

Following example shows the success scenario of the Process Sale use case.

IT310-OOAD Page 2
IT310- OBJECT ORIENTED ANALYSIS AND DESIGN


Events generated by cashier (actor)-

makeNewSale, enterItem, endSale and makePayment.

SSD for Process Sale Scenario

IT310-OOAD Page 3
IT310- OBJECT ORIENTED ANALYSIS AND DESIGN

IT310-OOAD Page 4

You might also like