OOAD Lab Manual

1: Demonstrate Use case Diagram for ATM system.

Aim: To develop a model for ATM Application using Use Case diagram.

USE CASE DIAGRAM: Use case diagrams are used to describe a set of
actions (use cases) that some system or systems should or can perform in
collaboration with one or more external users of the system (actors). Each
use case should provide some observable and valuable result to the actors
or other stakeholders of the system.

Purpose:
1. Used to gather requirements of a system
2. Used to get an outside view of a system
3. Identify external and internal factors influencing the system
4. Show the interaction among the requirements through actors.
Uses:
1. Requirement analysis and high level design
2. Model the context of a system

Notations:

S.no Name Notation Description

1 Actor Actors are the
entities that
interact with the
system.
2 System The use cases in
the system make
System up the total
requirements of
the system.
3 Use Case Use Case describes
the actions
performed by the
user.
4 Generalization A generalization
relationship is used
to represent
inheritance
relationship

ZH NaveenMsc National Degree College, NDL Page 1

OOAD Lab Manual

between model
elements of same
type
5 Include <<include>> Use case may
------------ contain the
functionalities of
another use case
6 Extend <<Extend> One use case may
------------ be used to extend
the behavior of
another

ZH NaveenMsc National Degree College, NDL Page 2

OOAD Lab Manual

2: Demonstrate Class Diagram for banking system

Aim: To develop a model for Banking system using class diagram

CLASS DIAGRAM: Class diagram is a static diagram. It represents the

static view of an application. The class diagram describes the attributes and
operations of a class and also the constraints imposed on the system. The
class diagrams are widely used in the modeling of object oriented systems
because they are the only UML diagrams which can be mapped directly with
object oriented languages.

Purpose:
1. Analysis and design of the static view of an application
2. Describe responsibilities of a system
3. Base for Component and Deployment Diagrams
Uses:
1. Describes the static view of the system
2. Shows the collaboration among the elements of the static view
3. Describes the functionalities performed by the system.
4. Construction of software applications using object oriented
languages.
Notations:

S.no Name Notation Description

Class name
1 Class Class is an entity which
Attributes describes a group of objects
Operation with same properties &
behavior.

Generalization refers to a
2 Generalization relationship between two
classes where one class is a
inheritance of another.

3 Association Association represent static

relationships between
classes.

ZH NaveenMsc National Degree College, NDL Page 3

OOAD Lab Manual

Aggregation is a indefine
4 Aggregation kind of association in the
UML that loosely suggests
whole-part relationships.

5 Composition Composition is a strong

kind of whole-part
aggregation.

Multiplicity specifies the

number of instances of one
class that may relate to a
6 Multiplicity single instance of an
associated class.

Class Diagram:

ZH NaveenMsc National Degree College, NDL Page 4

OOAD Lab Manual

3: Demonstrate Sequence Diagram for ATM system.

Aim: To develop a model for ATM Application using Sequence diagram.
INTERACTION DIAGRAM:
Interaction diagrams are used to visualize the interactive behavior of the
system. The Interactive behavior is represented in UML by two diagrams
namely,
Sequence Diagram- It emphasizes on time sequence of messages
Collaboration Diagram- It emphasizes on structural organization of
the objects that send and receive messages.
SEQUENCE DIAGRAM Sequence diagram describes an interaction by
focusing on the sequence of messages that are exchanged, along with their
corresponding occurrence specifications on the lifelines.
Purpose:
1. To capture dynamic behaviour of a system
2. To describe the message flow in the system
3. To describe structural organization of the objects
4. To describe interaction among objects
Uses:
1. To model flow of control by time sequence
2. To model flow of control by structural organizations

Notations

ZH NaveenMsc National Degree College, NDL Page 5

OOAD Lab Manual

Sequence Diagram:

ZH NaveenMsc National Degree College, NDL Page 6

OOAD Lab Manual

4: Demonstrate Collaboration Diagram for Hotel Reservation.

Aim: To develop a model for Hotel Reservation Application Collaboration
diagram.
COLLABORATION DIAGRAM Collaboration or Communication diagram is
also used to model the dynamic behavior of the system. It emphasizes on
structural organization of the objects that send and receive message.

Purpose:
1. To capture dynamic behaviour of a system
2. To describe the message flow in the system
3. To describe structural organization of the objects
4. To describe interaction among objects

Uses:
1. Used to show the messages that flow from one object to another
within the system and the order in which they happen.
2. Used to track the source of the message from where it has been
sent
3. Used to provide relationships and interactions among software
objects

Notations:

ZH NaveenMsc National Degree College, NDL Page 7

OOAD Lab Manual

Collaboration Diagram:

ZH NaveenMsc National Degree College, NDL Page 8

OOAD Lab Manual

5: Demonstrate State Diagram for Library Management System.

Aim: To develop a model for Library Management System State diagram.

STATE DIAGRAM
• A State diagram is used to describe the behavior of the systems. State
diagrams require that the system described is composed of a finite number
of states.
• State diagrams are used to give an abstract description of the behaviour of
a system. This behavior is analyzed and represented in series of events, that
could occur in one or more possible states.

Purpose:
1. It describes dynamic behavior of the objects of the system.
2. It specifies the possible states, what transitions are allowed
between states.
3. It is used to describe the dependence of the functionality on the
state of the system
4. The state model describes those aspects of objects concerned
with time and the sequencing of operations events.
Uses:
1. To model the object states of a system.
2. To model the reactive system. Reactive system consists of
reactive objects.
3. To identify the events responsible for state changes.

Notations:

ZH NaveenMsc National Degree College, NDL Page 9

OOAD Lab Manual

State Chart Diagram:

ZH NaveenMsc National Degree College, NDL Page 10

 OOAD Lab Manual

6: Demonstrate Activity Diagram for ATM application.

Aim: To develop a model for ATM application activity diagram.
ACTIVITY DIAGRAM
An Activity diagram is basically a flowchart to represent the flow from one
activity to another activity. Activity diagrams are typically used for business
process modeling, for modeling the logic captured by a single use case or
usage scenario or for modeling the detailed logic of a business rule.
Purpose:
1. Draw the activity flow of a system
2. Describe the sequence from one activity to another
3. Describe the parallel, branched and concurrent flow of the
system.
Uses:
1. Visualize business processes and workflows.
2. Model work flow by using activities.
3. Model business requirements.
4. High level understanding of the system’s functionalities.
5. Investigate business requirements at a later stage.
Notations:
S.no Name Notation Description
1 Represents an individual
Activity activity of a system

2 Initial It shows the starting state of

State object.

3 Final State It shows the terminating

state of object.

4 Transition Represents flow of data from

one activity to another.

5 Decision node is a control

node that accepts tokens on
one or more incoming edges
Decision
and selects outgoing edge
from two or more outgoing
flows.

ZH NaveenMsc National Degree College, NDL Page 11

 OOAD Lab Manual

6 A fork represents a single

incoming transition and
multiple outgoing transitions
Fork
exhibiting parallel behavior

7 A join in the activity diagram

synchronizes the parallel
behavior started at a fork.
Join

Activity Diagram:

ZH NaveenMsc National Degree College, NDL Page 12

OOAD Lab Manual

7: Demonstrate Package Diagram for Online Payment System.

Aim: To develop a model for online Payment System package diagram.

PACKAGE DIAGRAM
• Package diagrams organize the elements of a system into related groups
to minimize dependencies among them.
• UML package diagrams are used to illustrate the logical architecture of a
system, the layers, subsystems, packages etc.

Package is a namespace used to group together elements that are

semantically related and might change together. It is a general purpose
mechanism to organize elements into groups to provide better structure for
system model. Uses: 1. Package diagrams can use packages containing use
cases to illustrate the functionality of a software system. 2. Package
diagrams can use packages that represent the different layers of a software
system to illustrate the layered architecture of a software system.
Uses:
1. Package diagrams can use packages containing use cases to illustrate
the functionality of a software system.
2. Package diagrams can use packages that represent the different layers
of a software system to illustrate the layered architecture of a software
system
3. It is used in large scale systems to picture dependencies between
major elements in the system.
4. Package diagrams represent a compile time grouping mechanism.
Notations:
Sno Name Notation Description

1 package A package is a group of

elements with common
package theme.

2 Dependency Defines relation between

-------------- one element to another

3 Access <<Access> One package requires

------------- assistance from the
functions of another
package

ZH NaveenMsc National Degree College, NDL Page 13

OOAD Lab Manual

4 Import <<import>> Import one package to

-------------- another

UML Package Diagram:

ZH NaveenMsc National Degree College, NDL Page 14

OOAD Lab Manual

8: Demonstrate Component Diagram for Library Management System.

Aim: To develop a model for Library manage System Component diagram.

COMPONENT DIAGRAM
Component diagrams are used to model physical aspects of a system
(elements like executables, libraries, files, documents etc.).Component
diagrams are used to visualize the organization and relationships among the
components in a system.

Purpose:
1. Visualize the components of a system
2. Construct executables by using forward and reverse engineering
3. Describe the organization and relationships of the components.

Uses:
1. Model the components of a system
2. Model database schema
3. Model executables of an application
4. Model system’s source code.

Notations:

Sno Name Notation Description

1 A Component is a
physical building
block of the
Component system

2 Dependency ------------------ Defines relation

between one
element to another

ZH NaveenMsc National Degree College, NDL Page 15

OOAD Lab Manual

UML Component Diagram:

ZH NaveenMsc National Degree College, NDL Page 16

OOAD Lab Manual

9: Demonstrate Deployment Diagram for ATM Application.

Aim: To develop a model for ATM Application Deployment diagram.

DEPLOYMENT DIAGRAM
• Deployment diagram is defined as assignment of concrete software
artifacts (executable files) to computational nodes (processing services).
• Deployment of software elements to the physical architecture and the
communication (network) between physical elements.

Purpose:
1. Visualize the hardware topology of a system.
2. Describe the hardware components used to deploy software
3. components. Describe the runtime processing nodes.

Uses:
1. To model the hardware topology of a system.
2. To model the embedded system.
3. To model the hardware details for a client/server system.
4. To model the hardware details of a distributed application.

ZH NaveenMsc National Degree College, NDL Page 17

OOAD Lab Manual

ZH NaveenMsc National Degree College, NDL Page 18