THE OBJECT ORIENTED ANALYSIS

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

1OBJECT ORIENTED ANALYSIS
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

2OBJECT ORIENTED ANALYSIS
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.

3OBJECT ORIENTED ANALYSIS
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

4OBJECT ORIENTED ANALYSIS
Name
Actors Staff, Customer
Preconditions User must exist.
User must be registered.
Main Flow User enters credentials
System matches the credentials in database
login successful
Alternative
flow
1. After registration 2. User accessing content page
without logging in.
Post condition User must be logged into the system.
Use Case
Name
Register
Actors Customer
Preconditions Customer must exist.
Customer details must be valid.
Main Flow Customer opens the website.
Customer enters the details.
Customer verifies with email or phone.
Alternative
flow
1. If an unregistered customer
is accessing.
2. Null.
Post condition

5OBJECT ORIENTED ANALYSIS
Use Case
Name
Input Booking details
Actors Customer
Preconditions Customer must exist.
Main Flow Customer enters date, time and duration.
Alternative
flow
1. Customer filters rooms. 2. Null
Post condition
Use Case
Name
Check availability
Actors Customer
Preconditions Room must exist.
Customer must exist.
Main Flow Customer search for the availability.
Alternative
flow
1. System picks rooms based on
the provided details.
2. System recommends.
Post condition Results must be displayed.
Use Case
Name
Browse
Actors Customer

6OBJECT ORIENTED ANALYSIS
Preconditions Customer must exist.
Rooms must exist.
Main Flow Customer browse through the list.
Alternative
flow
1. null 2. null
Post condition Customer should be able to see details of the available rooms.
Use Case
Name
Select
Actors Customer
Preconditions Customer must exist.
Room must exist.
Main Flow Customer selects from the list.
Alternative
flow
1. null 2. null
Post condition System must ask to proceed to pay.
Use Case
Name
Pay
Actors Customer
Preconditions Customer must exist.

7OBJECT ORIENTED ANALYSIS
Funds must be available.
Main Flow Customer inputs payment details.
Customer verifies with the bank.
Payment is successful.
Alternative
flow
1. null 2. null
Post condition
Use Case
Name
Cancel Booking
Actors Customer, staff
Preconditions Customer must exist.
Staff must exist.
Booking must exist.
Main Flow Customer login to system.
Customer go to the bookings.
Customer cancels the booking.
Alternative
flow
1. Staff go the bookings.
Staff cancels the booking.
2. null
Post condition

8OBJECT ORIENTED ANALYSIS
Use Case
Name
Receive Email
Actors Customer
Preconditions Customer must exist.
Booking must be successful.
Email must exist.
Main Flow Customer makes payments successfully.
Customer receives the email of booking confirmation.
Alternative
flow
1. null 2. null
Post condition Reference number must be available In the email.
Use Case
Name
Generate receipt
Actors Staff
Preconditions Booking must exist.
Staff must exist.
Main Flow Staffs go to the booking.
Staffs print the receipt of the booking.
Alternative
flow
1. null 2. null
Post condition Reference number must exist in receipt.

9OBJECT ORIENTED ANALYSIS
Use case diagram
The use case diagram represents the actors, use cases and relationship among them. The below
diagram is the use case diagram of online booking system which is developed with the help of
the use cases identified and the business process (Seidl et al. 2015). The diagram clearly
represents which actors can perform which operations in the system.
Figure 1: Use case diagram of online booking system
Source: created by author

10OBJECT ORIENTED ANALYSIS
Domain Model
In the domain modelling, the informal parameters of development are transformed into the
components of the software so it can be reusable whenever required. It is technique to represent
conceptual classes, association between them along with the domains of the attributes. The terms
can be specified as per their domains (Evans et al. 2014). It can achieve inheritance and high
abstraction level of software during the development. In terms of memory management and
maintenance of the software the domain modelling seems advantageous. The size of the codes
and LOC (Lines of codes) is also minimum when using domain modelling technique of the
classes. Below, the identified domain classes are discussed:
Identified domain classes
ID: The ID domain is the domain of identification numbers or unique values that is stored in a
class. For example the customer ID, Staff ID, reference Number, Room number, and payment ID
are the unique attributes which have the same ID domain.
Name: It consists of simple string that is associated with the attributes that stores the name of the
customer or staff. The first letter of the string can be capitalized.
User id: It is associated with all of the user ids of the login system whether it is for staff or user.
It can have a special sort of patterns of alphabets or numeric to create a username.
Password: It is associated with the all types of passwords and secret keys which are stored as
attributes. The object is private and the domain can have the password criteria such as length of
the password, capital letters, small letters and special characters etc.
Email: All the email related attributes can have data type as Email domain. It can be defined as
having ‘@’ in the email necessarily.

11OBJECT ORIENTED ANALYSIS
Phone: All the phone number related attributes will use this domain. It will be an integer value,
data size up to 10 characters.
Date: All the date related attributes in the classes can use ‘Date’ domain. It can be created using
the string. The format of the dates can also be defined in this domain.
Currency: All the amount related attributes will use currency domain. It can consist of float
values.
Domain Model diagram
After identification of the domain classes, the relationship between the classes can be
established (Karsai et al. 2014). The domain model class diagram for the online booking system
is represented below along with the attributes which are required to perform the system.

12OBJECT ORIENTED ANALYSIS
Figure 2: Domain Model of online booking system
Source: created by author
Sequence Diagram
Sequence diagram explains the interaction between the actor and objects of the system
sequentially for a specific operation. It clarifies the flow of the processes and messages exchange
between the system components and actors to perform specific tasks (Jena, Swain and Mohapatra
2015). The below diagram represents the sequence diagram for the function booking by any
customer. The actor lifeline, object lifeline, message exchanged and sequence of the messages
are also represented.

13OBJECT ORIENTED ANALYSIS
Figure 3: Sequence diagram of function booking
Source: created by autho
Class Model
Class Modelling is a part of Unified Modelling Language. It identifies the classes
required to develop any software and relationship between the classes (Nanthaamornphong et al.
2015). The identification of classes and class diagram are discussed below:

14OBJECT ORIENTED ANALYSIS
Identified Classes
Customer: It stores the attributes such as customer id, name, address, email and contact of the
customer along with the functions which can be performed by the customer.
Login: it stores the login credentials for both the customer and staff.
Staff: It stores the attributes such as staff id, name, address, email and contact of the staff along
with the functions which can be performed by the staff.
Booking: It has the attributes for the reference number, booking date, check-in date and check-
out date of the bookings.
Room: It stores the room’s details of the company. The details are room number, type, capacity
and availability of the room.
Payment: It stores the Payment related attributes such as payment id, date and amount of the
payment made.

15OBJECT ORIENTED ANALYSIS
Class Diagram
Figure 4: Class Diagram of online booking system
Source: created by author
`

16OBJECT ORIENTED ANALYSIS
Conclusion & reflection
I have successfully identified the domains, classes and use cases from the business
process of the manual and current system to develop the use case diagram, domain model,
sequence diagram and class diagram for the design of the system. The description of the each
part is justified and based on the case study. It has really helped me in understanding the object–
oriented analysis and design along with the UML modelling techniques.

17OBJECT ORIENTED ANALYSIS
References
Evans, A., France, R., Lano, K. and Rumpe, B., 2014. Developing the UML as a formal
modelling notation. arXiv preprint arXiv:1409.6928.
Jena, A.K., Swain, S.K. and Mohapatra, D.P., 2015. Test case creation from UML sequence
diagram: a soft computing approach. In Intelligent Computing, Communication and Devices (pp.
117-126). Springer, New Delhi.
Karsai, G., Krahn, H., Pinkernell, C., Rumpe, B., Schindler, M. and Völkel, S., 2014. Design
guidelines for domain specific languages. arXiv preprint arXiv:1409.2378.
Nanthaamornphong, A., Carver, J., Morris, K. and Filippone, S., 2015. Extracting uml class
diagrams from object-oriented fortran: Foruml. Scientific Programming, 2015.
Seidl, M., Scholz, M., Huemer, C. and Kappel, G., 2015. The Use Case Diagram. In UML@
Classroom (pp. 23-47). Springer, Cham.
Xinogalos, S., 2015. Object-oriented design and programming: an investigation of novices’
conceptions on objects and classes. ACM Transactions on Computing Education (TOCE), 15(3),
pp.1-21.
Yalla, P. and Sharma, N., 2014, March. Parsing natural language text of use case description.
In 2014 Conference on IT in Business, Industry and Government (CSIBIG) (pp. 1-3). IEEE.
Zhang, L., Williams, R.A. and Gatherer, D., 2016. Rosen's (M, R) system in Unified Modelling
Language. Biosystems, 139, pp.29-36.

18OBJECT ORIENTED ANALYSIS