THE OBJECT ORIENTED ANALYSIS

Running head: OBJECT ORIENTED ANALYSIS
OBJECT ORIENTED ANALYSIS
Name of the Student
Name of the University
Author Note

OBJECT ORIENTED ANALYSIS1
Table of Contents
Introduction......................................................................................................................................2
Use Case..........................................................................................................................................2
Use case description....................................................................................................................3
Use case diagram.........................................................................................................................8
Domain Model.................................................................................................................................9
Identified domain classes...........................................................................................................10
Domain Model diagram.............................................................................................................11
Sequence Diagram.........................................................................................................................12
Class Model...................................................................................................................................13
Identified Classes.......................................................................................................................13
Class Diagram............................................................................................................................14
Conclusion & reflection.................................................................................................................14
References......................................................................................................................................16

OBJECT ORIENTED ANALYSIS2
Introduction
Object oriented analysis and design are based on the development which deals with the
data structure, flow of the data, behavior of the system and sequence of the interactions
(Xinogalos 2015). This paper discusses about the online booking system for function booking for
rooms. The system will be based on a website. The customer can log in to the system and book
for the rooms. This report includes use case modelling, domain modelling, class diagram and
sequence diagram to show the design development of the new system.
Use Case
In software development, use case is a methodology where the interaction between the actor and
the systems are explained. It is mainly associated with the functions that a user can perform in
the system (Zhang, Williams and Gatherer 2016). The use cases can represent the behavior and
flow of the system. It can be examined by studying the existing business process of booking
system of function rooms. It can be helpful in certain phases of development, such as planning,
design, validating and testing the software. Each use case must have actor, system and the goal
of the function. The use case identified for the new online function room booking system are
described below:
i. Login: Customer can login to the system to perform any functions. Similarly the Staff
needs to login with their credentials to perform any operation inside the system.
ii. Register: The Customer must register first in order to use the system functions. The user
identification number and password must be present in the system database.
iii. Input booking details: The customer needs to provide the date, time and the capacity for
the room to check and book in the system.

OBJECT ORIENTED ANALYSIS3
iv. Check Availability: The customer can check the availability of the rooms according to
the different criteria. Similarly system can filter the room on the basis of the provided
date, time and capacity.
v. Browse: The Customer can browse through the rooms which re picked by the system
after filtering according to the date, time and capacity.
vi. Select: The customer can select any rooms from the list provided by the system.
vii. Pay: After making a selection, customer is required to make payment for the booking. It
will confirm the booking with a reference number.
viii. Cancel Booking: The booking of a room can be cancelled by both customer and staff in
case of any situation.
ix. Generate receipt: The staff can generate the booking confirmation receipt to print.
x. Receive Email: After a successful booking the customer will receive an email for the
confirmation of the room booking.
Use case description
Use case description is an important part of use case modelling. It describes the sequence of the
steps to perform any operation, actors associated to it, goal of the use case, conditions,
assumptions, etc. (Yalla and Sharma 2014). The use case description of the identified use cases
for the online booking system is given below in a tabular format:
Use Case Login