MAHARAJA SURAJMAL

INSTITUTE OF TECHNOLOGY
(Affiliated to Guru Gobind Singh Indraprastha University)C-4,

Janakpuri, New Delhi-110058

OBJECT ORIENTED SOFTWARE

ENGINEERING LAB

Submitted To: Submitted By:

Nirmit Sabharwal
Ms. Poonam Dhankar
20196302717
CSE - evening
8th Semester
 EXPERIMENT: 1
AIM: INTRODUCTION TO UML
Definition of Unified Modeling Language (UML)

 UML is a standard language for specifying, visualizing, constructing, and

documenting for large software systems, as well as for business modeling and other
non-software systems.
 Considered a very important part of developing object oriented software and
software development process.
 UML uses graphical notations to express design of software projects and its
requirements.

Common Types of UML Diagrams

UML defines several types of diagrams: class (package), object, use case, sequence,
collaboration, statechart, activity, component, and deployment.
Type Description Diagram Display
Use Case Diagram Use case diagrams model the
functionality of system using actors
and use cases.

Class Diagram Class diagrams are the backbone of

almost every object oriented
method, including UML. They
describe the classes of the system,
their inter- relationships, and the
operations and attributes of the
classes.

Object Diagram A diagram that shows a complete

or partial view of the structure of a
modeled system at a specific time.
They can be used to test class
diagrams for accuracy. useful for
exploring “real world” examples of
objects and the relationships
between them
Sequence Diagram Sequence diagrams describe
interactions among classes in terms
of an exchange of messages over
time.

Interactions Diagram Represent interactions between

objects as a series of sequenced
messages. Collaboration diagrams
describe both the static structure
and the dynamic behavior of a
system.
 EXPERIMENT 2
AIM:- To draw UML diagrams of Automated Teller Machine
The automated teller machine is simply a data terminal with two input and four output
devices. These devices are interfaced to the processor. The processor is heart of the ATM
machine. All the ATM machines working around the world are based on centralized database
system. The

Automated Teller Machine involve following component:-

Card reader - The card reader captures the account information stored on the magnetic stripe
on the back of an ATM/debit or credit card

Keypad - The keypad lets the cardholder tell the bank what kind of transaction is required
(cash withdrawal, balance inquiry, etc.) and for what.

Display screen - The display screen prompts the cardholder through each step of the
transaction process. Leased-line machines commonly use a monochrome or color CRT
(cathode ray tube) display. Dial-up machines commonly use a monochrome or color LCD.

Receipt printer - The receipt printer provides the cardholder with a paper receipt of the
transaction.

Cash dispenser - The heart of an ATM is the safe and cash-dispensing mechanism. The entire
bottom portion of most small ATMs is a safe that contains the cash.

Transaction Management
i. First of all, the customer inserts his/her card and PIN into the ATM at a local bank
abroad.

ii. The bank then replies to the message via the network, stating that the local bank can
provide the customer with the amount requested.

iii. The local bank will not dispense the cash until it knows the funds are available in the
customer’s own account.

iv. The customer retrieves the money and card and goes on his/her way.

v. As soon as the home country bank receives the request and checks the balance, the
money is debited from the account.

vi. Later that day a settlement occurs between the two banks facilitated by the central
network.

vii. An electronic message is sent to the central network which is passed on to the
customer’s own bank in his/her home country.
 Fig 1- Use Case Diagram

Fig 2-Sequence diagram (Cash Withdrawl)

Fig 3-Collaboration diagram

Fig 4- Class Diagram

Fig 5-State Diagram
Fig 6-Activity Diagram
Fig 7-Component Diagram

Fig 8-Deployment diagram

 Experiment 3
Aim: UML diagrams of Hotel Management System

Problem statement

The project entitled Online Hotel Reservation is a web based system which facilitates online
reservation of hotel accommodations from anywhere in the world. If a person wants to
reserve his accommodation he would to know the list of hotels in the city he wants to visit,
different amenities provided in each hotel the different types of rooms available, the rates of
those rooms, the constraints of the hotel and finally the availability of the desired rooms on
the desired rate. He may achieve all this through travel agencies, the guides available, by
making enquiries in person, by making enquiries through telephone. If he wants to make a
choice between the hotels he has to repeat the whole process for anumber of hotels .After
being satisfied with the choice he has to confirm his reservation by paying the amount
personally or through middle persons. This process is laborious and his choice is limited. So
we found the necessity of providing all the information and the facility to reserve his
accommodation through the net so that maximum satisfaction is achieved by the customer
with least effort. The solution we are providing to this is to design a website that contains
information about various cities and the reputed hotels in each city along with the facilities,
types of rooms and their rates. The tourist can also choose the hotel of his interest.

Feasibility study conducted once the problem is clearly understood. Feasibility study is a
high level capsule version of the entire systemanalysis and design process. The objective is to
determine quickly and at the minimum expense how to solve the problem and to determine
the problem is solved. The system has been tested for feasibility in the following ways.

1. Technical feasibility
2. Operational feasibility
3. Economical feasibility
Use Case diagram

Sequence Diagram
COLLABORATION DIAGRAM FOR RESERVATION & BOOKING
SYSTEM

Class Diagram
State Chart Diagram

Activity Diagram
Component Diagram

Deployment diagram
 Experiment - 4 Library
Management System

A software has to be developed for automating the manual library management system.The system
should have distributed functionalities as described below:

1. Login: Only the user with specified login id & password can get access to the system.
This provides security from unauthorized access and server attacks fromtreacherous and
malicious intents.

2. List Of Books: Ability for users to browse, through the list of all the available bookin the
library.

3. List Of Issued Books: Users should be able to see the list of books that they havealready
issued along with all the necessary details such as date of issue, date of return etc.

4. Search: Users should be able to search through the list of books. It saves user’s time and
provides ease of access.

5. Issue Books: Ability to issue a book online so that user can easily issue a book if he/she
wants to.
a) Use Case Diagram
b) Sequence Diagram
c) Collaboration Diagram
d) Class Diagram
e) State Chart Diagram
f) Activity Diagram
g) Component Diagram
h) Deployment Diagram
 Experiment - 5
UML Diagrams for Railway Ticket Booking System

A software has to be developed for automating the manual railway reservation system.The system
should have distributed functionalities as described below:

1. Login: Only the user with specified login id & password can get access to thesystem.
This provides security from unauthorized access.

2. Booking: A passenger should be able to reserve a seat in the train specified by him if
available. For this he has to fill a reservation form with the details about hisjourney. The
clerk checks for the availability of the seat in the train and if the seatis available then he
makes entries regarding train name,train number, date of journey, boarding station,
destination. The passenger is the asked to pay the fair.

3. Cancel Booking: There may arise a case when the passenger wants to cancel his
reservation .For this he has to fill a cancellation form providing all the detailsabout the
ticket reserved by him. The clerk then checks for the entries from the database and
cancels the reservation finally returning the ticket amount with some deduction.

4. Payment: Online payment portal is incorporated.

5. Update train information and report generation: Only the Administrator has theright to
make changes in train details(train name, train no. etc.).The system should also be
able to generate report when needed in the form of reservationcharts , train schedule
charts etc.

6. View Booking status and train schedule: All the users should be able to see the
information about the reservation status & train schedule, train name, train number etc
a) USE CASE DIAGRAM
b) SEQUENCE DIAGRAM
c) COLLABORATION DIAGRAM

d) CLASS DIAGRAM
e) STATE CHART DIAGRAM
f) ACTIVITY DIAGRAM
g) COMPONENT DIAGRAM

h) DEPLOYMENT DIAGRAM
 Experiment 6
Aim – UML diagrams for Hospital management system

Case Study

A multi specialty hospital that includes a number of departments, rooms, doctors, nurses,
compounders, and other staff working in the hospital. Patients having different kinds of
ailments come to the hospital and get checkup done from the concerned doctors. If required
they are admitted in the hospital and discharged after treatment. The aim of this case study is
to design and develop a database for the hospital to maintain the records of various
departments, rooms, and doctors in the hospital. It also maintains records of the regular
patients, patients admitted in the hospital, the check up of patients done by the doctors, the
patients that have been operated, and patients discharged from the hospital. Description: In
hospital, there are many departments like Orthopedic, Pathology, Emergency, Dental,
Gynecology, Anesthetics, I.C.U., Blood Bank, Operation Theater, Laboratory, M.R.I.,
Neurology, Cardiology, Cancer Department, Corpse, etc. There is an OPD where patients
come and get a card (that is, entry card of the patient) for check up from the concerned doctor.
After making entry in the card, they go to the concerned doctor’s room and the doctor checks
up their ailments. According to the ailments, the doctor either prescribes medicine or admits
the patient in the concerned department. The patient may choose either private or general
room according to his/her need. But before getting admission in the hospital, the patient has
to fulfill certain formalities of the hospital like room charges, etc. After the treatment is
completed, the doctor discharges the patient. Before discharging from the hospital, the patient
again has to complete certain formalities of the hospital like balance charges, test charges,
operation charges (if any), blood charges, doctors’ charges, etc. Next we talk about the
doctors of the hospital. There are two types of the doctors in the hospital, namely, regular
doctors and call on doctors. Regular doctors are those doctors who come to the hospital daily.
Calls on doctors are those doctors who are called by the hospital if the concerned doctor is
not available

Problem Statement

It is very important to maintain efficient software to Handle information of a Hospital and its
management. As it provides basic Functionalities needed in the hospital management system
these diagram also provides away to record this information and to access these in a simple
Way. The goal is to develop and implement the system cost effectively; user-friendly. is to
manage the employees including doctors, patients, wards and Hospital services provided in a
renounced Hospital. It also provides immediate accessories needed while the hospital
management. These UML diagram has the scope of adding new Patient admitting, fixing
appointments etc. This also displays the other services provided to patient.
Use-case diagram

Sequence diagram
Collaboration diagram

Class diagram
State-chart diagram

Activity diagram
Component diagram

Deploymentdiagram
 Experiment - 7 Student
Counselling System

A software has to be developed for automating the manual student counselling system.The system
should have distributed functionalities as described below:

1. Login: Only the user with specified login id & password can get access to the system.
This provides security from unauthorized access and server attacks fromtreacherous and
malicious intents.

2. Choice Filling System: A student should be able to mark his/her specified list of
priorities with a mixture of courses and colleges that are available for that candidate to
be filled. For this he has to fill a choice filling form with the details about his preferences.
The system checks for the availability of the seat in the college against the student rank
and if the seat is available with the condition thatthe student lies in the ranks specified
then he/she makes the specific counsellinground.

3. Decision Page: When all the calculations have been made and all the seats for around are
filled then the results of that particular round are displayed on to all thecandidates on this
page. It dictates whether a student has or has not been selected and other options they
may perform, like alterations in choice filling or proceeding with admission process.

4. Payment: Online payment portal is incorporated. After a student has been allotted a seat
and they wish to continue with the admission. They may pay theircorresponding fees
here and get the admission confirmed.
a) USE CASE DIAGRAM
b) SEQUENCE DIAGRAM

c) COLLABORATION DIAGRAM
d) CLASS DIAGRAM
e) STATE CHART DIAGRAM
f) ACTIVITY DIAGRAM
g) COMPONENT DIAGRAM
h) DEPLOYMENT DIAGRAM
 Experiment No: 8
Aim: To create UML diagrams for bank management system.
Problem Statement
This system provides the basic services to manage bank accounts at a bank. Bank has manybranches,
each of which has an address and branch number. A client opens accounts at abranch. Each account
is uniquely identified by an account number; it has a balance and a credit or overdraft limit. There are
many types of accounts, including: A mortgage account, a chequing account, and a credit card account. It is
also possible to have a joint account. Although the basic type of services offered by a bank depends upon
the type of bank and the country, servicesprovided usually include: Taking deposits from their customers
and issuing current or checking accounts and savings accounts to individuals and business. Extending loans
to individuals and business, Cashing cheque. Facilitating money transactions such as wire transfer and
cashiers cheque, Consumer & commercial financial advisory services, financial transaction can be
performed through many different channels. We had tried to depict our model with the help of
following diagrams:

o Use-Case Diagram
o Sequence Diagram
o Collaboration Diagram
o Class Diagram
o State Chart Diagram
o Activity Diagram
o Component Diagram
o Deployment Diagram
 USE-CASE diagram

COLLABORATION DIAGRAM
SEQUENCE DIAGRAM

CLASS DIAGRAM
 ACTIVITY DIAGRAM

STATE-CHART DIAGRAM
COMPONENT
DIAGRAM

DEPLOYMENT DIAGRAM