Online Room Booking System Discussion 2022

Running head: Online Room Booking System
ONLINE ROOM BOOKING SYSTEM
Name of the Student
Name of the University
Author Note

1Online Room Booking System
Table of Contents
Introduction:...............................................................................................................................2
Discussion:.................................................................................................................................2
Use case Diagram:..................................................................................................................2
Domain Model:......................................................................................................................8
Sequence Diagram:................................................................................................................9
Class diagram:........................................................................................................................9
Requirement Analysis:.............................................................................................................10
Functional Requirements:....................................................................................................10
Non-functional requirements:..............................................................................................11
Conclusion:..............................................................................................................................11
References:...............................................................................................................................13

2Online Room Booking System
Introduction:
An owner of a small club wants to design a website to increase the growth of their
business. Currently, he is using a manual based system that is error-prone and time-
consuming process. And this system is very hard to manage for the staff. For the booking,
right now a customer needs to come to the club to book a room for function. A staff check
there is a room empty or not if the room is available customer need to pay 10% deposit
money for the booking. But this is a lengthy process and in the peak season, this process
takes lots of time. Club wants to implement a system that can automate many systems. New
online website can help a customer to book a room for functions. This system also displays
every room detail to the customers. With the help of this system, a customer can easily book
their desirable room. This system also offers online payment options for registered customer.
Due to work pressure, a staff unable to provide very details to the customer. But this system
can provide detailed information to the customer. With the help of this system, the club can
eliminate paperwork and improve their work efficiency. UML diagrams are an essential part
of system analysis and design (Dennis, Wixom and Roth. 2018). This report provides every
necessary UML diagram for the system. Few assumptions were made while designing the
system and that are discussed below:
A registered user can update their details after successfully log into the system and
this system allows only registered user for the online payment. A customer and staff can
cancel a booking. A staff also need to be log in to update the room status in this system. a
forget password option is also available in this system.
Discussion:
Use case Diagram:

3Online Room Booking System
Figure 1: Use Case diagram for online room booking system.
(Source: Created by Author)
Name Registration
Actors Customer
Preconditions Every information of a customer must be stored in the system.
Main Flow 1. Browse website.
2. Provide necessary details for registration.
3. Log in
Alternative
flows/Exceptions
None
Post-conditions The organization will have every information about a customer.

4Online Room Booking System
Name Login
Actors Customer, Staff
Preconditions Every activity of a customer and staff must be recorded in the system.
Main Flow 1. Provide username and password
2. Click on login option.
Alternative
flows/Exceptions
None
Post-conditions The organization will have every activity details of a customer and
staff.
Name Book for a function room
Actors Customer
Preconditions Customer needs a room for function.
Main Flow 1. Customer log in first.
2. Provide details for room availability.
3. Customer book a room.
Alternative
flows/Exceptions
A customer also manually books a room over the phone.
Post-conditions Customer book a room.
Name Book for a function room
Actors Customer
Preconditions Customer needs a room for a function.
Main Flow 1. Customer log in first.

5Online Room Booking System
2. Provide details for room availability.
3. Customer book a room.
Alternative
flows/Exceptions
A customer also manually books a room over the phone.
Post-conditions Customer book a room.
Name Check for the room availability.
Actors Customer
Preconditions Customer needs a room for functions.
Main Flow 1. Customer enters Day, Time, Number of hours, Number of
people
2. Select a suitable room.
Alternative
flows/Exceptions
Manually call them and get information.
Post-conditions Customer found a suitable room.
Name Check Room Maps
Actors Customer
Preconditions Customer need information and location of rooms.
Main Flow 1. Customer enters Day, Time, Number of hours, Number of
people
2. Use room map feature.
3. Exit from room map system.
Alternative Customer can visit the club and check manually every room.

6Online Room Booking System
flows/Exceptions
Post-conditions Customer will get every room direction and information.
Name Payment
Actors Customer
Preconditions Customer need to complete the payment process to get a room
booked.
Main Flow 1. Customer choose a room.
2. Provide card details.
3. Room booked successfully.
Alternative
flows/Exceptions
Customer can physically visit the club to get a room.
Post-conditions Customer successfully booked a room.
Name Update room availability.
Actors Staff
Preconditions Every room needs to be updated.
Main Flow 1. Staff log in first.
2. Check rooms.
3. Update room status.
Alternative
flows/Exceptions
None
Post-conditions Every room availability or status will be updated.

7Online Room Booking System
Name Generating receipt.
Actors Staff
Preconditions Every payment detail must be sent to the customer.
Main Flow 1. Staff log in.
2. Check payment information.
3. Generate receipt.
4. Email customer with every essential detail.
Alternative
flows/Exceptions
None
Post-conditions Customer will have every important information regarding booking.
Name Cancel booking.
Actors Staff, customer
Preconditions Every room needs to be updated.
Main Flow 1. Staff and customer need to be login first.
2. Click on cancel booking option.
Alternative
flows/Exceptions
Customer can cancel booking over the phone.
Post-conditions Room will be cancelled.

8Online Room Booking System
Domain Model:
Figure 2: Domain Model for online room booking system.
(Source: Created by Author)

9Online Room Booking System
Sequence Diagram:
Figure 3: Sequence Diagram for an online room booking system.
(Source: Created by Author)
Class diagram:

10Online Room Booking System
Figure 3: Sequence Diagram for an online room booking system.
(Source: Created by Author)
Requirement Analysis:
Every system contains many functional and non-functional requirements (Garcia and
Paiva. 2018). The functional and non-functional requirements of this system are discussed
below.
Functional Requirements:
 Customer registration is required in order to use the system. Customer can register
themselves by providing essential information.
 Every customer and staff need to login for using the system. by proving the user name
and password a customer or club staff can log into the system.
 Forget password option available in this system, in case, if any customer or staff
forget their password, they can easily recover their password by using this option.
 After successfully login, a customer can search and a room by providing Day, Time,
Number of hours, Number of people.
 This system can display all the details of the Room and the map of the room to a
customer before they confirm their bookings.
 A customer can cancel their booking after logging into the system.
 Every customer can pay the rest by using their card. Credit and debit both cards are
accepted here. They also can book a room by proving 10% of the room price. Physical
payment is not required in the system.
 After the log in a staff also can update rooms status.
 This system can send email after the booking confirmation. Every essential
information regarding booking will be sent to the registered email address.
 Every customer can check their booking status by using their registered account.

11Online Room Booking System
Non-functional requirements:
 This system takes most of the online transaction process, so every transaction should
be done in the secure connections.
This system also records sensitive information such as customer details, customer card
details. They should use a robust database system so every data can be secure (Khan et al.
2016).
 This system can manage heavy workloads. Multiple transactions can be done at a
time.
 This system can provide for 24*7 hours online booking service. Few batteries can
provide power during a power cut.
 This system can run on almost every browser. A customer can use this system from
their mobile phone as well as computer.
 Due to its bright screen and big font every person can access the system without
facing any problem.
 This system can covert the amount USD from AUD as user preferences.
 English is the default language on this website. So that most of the customer can
navigate the website. customer who does not aware of English they can easily change
their language from the language section.
Conclusion:
Form the above system analysis and research it can be concluded that, UML diagrams
are one of the most essential tools for system design and analysis. I have learnt many system
analysis and design technique from this project. To fitful the design, I have to assume several
features that are mentioned in the introduction section and it is attached with the case study.
These assumptions help me complete this project. Form the activity one, I have learnt use

12Online Room Booking System
case design technique. How every actor within the system interact with each other. Use
diagram shows us every actor and their specific works within the system. After creating the
diagram, I have attached the use case description for every use case. After reading the use
case description, A reader can get a complete overview of actors, preconditions, main flow,
exceptions and postconditions. After the use case, I have completed the domain model of this
system in. After viewing the domain model, a reader can get a complete idea about the
domains and the relation between them. Next section is sequence diagram. I have learnt how
a system can communicate with their subsystem and users. Sequence diagram also provides
the communication between actors and subsystems. Class diagram identifies every class
within the system and their functions are also provided in this diagram. I have learnt their
relationship, data types attributes and how a class inherit another class. After completing this
project, I have learnt drawing UML diagrams and their necessity in system analysis and
design.

13Online Room Booking System
References:
Dennis, A., Wixom, B.H. and Roth, R.M., 2018. Systems analysis and design. John wiley &
sons.
Garcia, J.E. and Paiva, A.C., 2018, March. Manage software requirements specification using
web analytics data. In World Conference on Information Systems and Technologies (pp. 257-
266). Springer, Cham.
Khan, F., Jan, S.R., Tahir, M., Khan, S. and Ullah, F., 2016. Survey: dealing non-functional
requirements at architecture level. VFAST Transactions on Software Engineering, 9(2), pp.7-
13.