0% found this document useful (0 votes)
278 views8 pages

Lab - 3 Sequence Diagrams: Theory

The document discusses sequence diagrams, which show the order of operations performed between objects. It defines the components of sequence diagrams like objects, actors, lifelines and messages. It then provides examples of sequence diagrams for an air ticket reservation system, hospital management system, library system and Bluetooth chat app to demonstrate how they are drawn.

Uploaded by

Abhiyush
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
278 views8 pages

Lab - 3 Sequence Diagrams: Theory

The document discusses sequence diagrams, which show the order of operations performed between objects. It defines the components of sequence diagrams like objects, actors, lifelines and messages. It then provides examples of sequence diagrams for an air ticket reservation system, hospital management system, library system and Bluetooth chat app to demonstrate how they are drawn.

Uploaded by

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

Lab 3

Sequence Diagrams
Theory:
Sequence diagram:
A Sequence diagram is a diagram that shows how objects operate with one another and in
what order. It is a construct of a Message Sequence Chart. 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. Sequence diagrams are
sometimes called event diagrams or event scenarios.

A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that
live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the
order in which they occur. This allows the specification of simple runtime scenarios in a
graphical manner.

COMPONENTS OF SEQUENCE DIAGRAM

The components of the sequence diagrams can be defined as below:


1. Object - This box shape represents a class, or object, in UML. They demonstrate how an
object will behave in the context of the system. Class attributes should not be listed in
this shape
2. Actors - represented by a stick figure, actors are entities that are both interactive with and
external to the system.

3. Lifeline - a dashed vertical line that represents the passage of time as it extends
downward. Along with time, they represent the sequential events that occur to an object
during the charted process. Lifelines may begin with a labelled rectangle shape or an
actor symbol.
4. Messages - packets of information that are transmitted between objects. They may reflect
the start and execution of an operation, or the sending and reception of a signal.
For example:

OBJECTIVES:
1. To know about the sequence diagrams
2. To know the sequence of operations performed
3. To document the behaviour of a future system

Sequence diagram for different scenarios:

Scenario 1: Air ticket reservation system

Air ticket reservation System


: Passenger

: Website

Search Flight

: Flight

: Aircraft

Request Matching Flight

ShowMatching Flights
Return matching flights
Select Preferred Flights
Display Cost
Approve cost
Enter Personal Info

Set payment info


Show summary
Check for seats

Get seat map

Get seat availability

Show seat availability

Select seats

Seat confirmed

Assign seats

Assign seats

Approve summary

Get payment

Show confirmation

Approve

: Payment

Scenario 2: Hospital Management System

Scenario 3: Library Management System

Scenario 4: Android Bluetooth Chat (Minor project)

Android Bluetooth Chat

enableBluetooth()
AskFor Permission()
openDeviceList()

:BluetoothEn
Connect Device()

Connect(device)

sendChatMessage()

ConnectionSuccesful

Write(message)

sendMessage()

receiveMessage

Discussion:
In this way, sequence diagram was drawn for Air Ticket Reservation System, Library
Management System, Hospital Management System and Android Bluetooth Chat using Argo
UML. UML sequence diagrams are used to show how objects interact in a given situation. An
important characteristic of a sequence diagram is that time passes from top to bottom: the
interaction starts near the top of the diagram and ends at the bottom.

Conclusion:
Hence, from this laboratory we got familiarized with class diagrams and we have learned to
design class diagram in Argo UML.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy