Comprehensive Report: Hotel Booking System Development and Analysis

This report provides a comprehensive overview of the development process for a Hotel Booking System. It begins by introducing the need for such systems in managing increased customer data and functionalities. The report then delves into the System Development Life Cycle (SDLC), outlining various phases including planning, system analysis, design, development, testing, implementation, and maintenance. It contrasts predictive and adaptive approaches, with a focus on Agile Scrum development. Key requirements-gathering techniques like interviews and questionnaires are discussed, followed by a detailed examination of both functional and non-functional requirements. The functional aspects encompass user account creation, room availability display, booking management, and cost calculation, while non-functional requirements address performance, scalability, availability, recoverability, maintainability, usability, and security. An activity diagram illustrates the system's workflow. The report concludes by emphasizing the effectiveness of the proposed system in meeting user and company needs, highlighting the role of Scrum methodology and UML diagrams in the development process.

HOTEL BOOKING SYSTEM
INTRODUCTION
The number of clients served by a particular enterprise or organization has increased over the
years. This has caused a ripple effect in the increased data and functionalities the enterprise is
supposed to handle. To ensure that the customers' requirement is met effectively and efficiently,
the mode of delivering the services has to change. The recent developments in information
technology have introduced software that can ensure the satisfaction of the organization's
objectives. The below report focuses on the system development cycle of the Hotel Booking
System.
METHODOLOGIES
System Development Life Cycle
The system development cycle comprises of various phases that are involved in the development
of a system. The phases that are involved in this process include (Chowdhury et al., 2018):
1. Planning: this is the first phase of the SDLC and involves understanding the scope and
domain of the problem. It also involves a diagnosis to find solutions for the problem.
2. System analysis and requirements- this involves critically analyzing the system to
identify the variable, users and constraints of the system. The functional and non-
functional requirements of the system are defined in this phase
3. System design- this involves designing a model that will meet the functional and non-
functional requirements of the system. The system designer develops a UML diagram
that communicates the system's functions to the developers.
4. Development- the UML diagrams received from the system designer are put into code.
This phase will involve system developer in different groups based on their skills.
5. Integrations and testing- once the various developers have codded their respective
modules, they integrate them to form the system. The integrated system is tested to
ensure that it meets all the requirements
6. Implementation- the system is launched to the final users

7. Maintenance- this is the final phase of the SDLC, the user gets to interact with the system
and offers feedback on his interaction. The feedback is used to make modifications to this
system to satisfy the user’s requirements
Adaptive approach
The adaptive model of SDLC is a technique that aims to ensure the team are responsive to the
changes in the users’ requirement. This process involves continuous learning and lightweight
planning of the system. The three-phases approach is used throughout the development processes
(speculate, collaborate, and learn)
Strength include:
 User-centered approach
 Early delivery of the system
 Promotes teamwork
Weakness includes:
 User involvement is sometimes excessive
 Testing along each stage increases the development cost
 Continuous integration may resort to a large scope of system requirements
Predictive approach
This approach is a more rigid development approach that presumes all the requirements are
stated prior. The system will be developed to meet only the stated requirements, the advantages
of this approach include:
 Clear definition of the scope
 It is steady and easy
Minimized risk of technicality issues its disadvantages include:
 Time-consuming
 Discards requirement missed in the requirement definition phase

AGILE SCRUM DEVELOPMENT
The agile methodology is a system development methodology that involves the principle of
iteration to develop the system (Isaias and Issa, 2015). It promotes frequent interception and
adaptation if the requirements change during the development. It highly promotes teamwork thus
quick submission of the working system to the market. The scrum development is a subset of the
agile methodologies that is more lightweight than the other methodologies. It is most popular for
developing the effective lightweight system.
The benefit include:
 Delivery of a high-quality system to the final users
 The adaptive nature of the development makes it flexible to change in requirements
 The system development ensure timely delivery of the system
 The methodology offers more control on the system development compared to other
methodologies such as spiral
REQUIREMENTS-GATHERING TECHNIQUE
The following were the information retrieval techniques used for this project:
Interview - This data gathering techniques involves an interviewer, who ask questions and an
interviewee who responds to the questions. The techniques are used to gather data from
relatively small groups. The questions are usually precise to the interviewee’s occupation such as
top level manager and chief of staff (Stoica, Mircea and Ghilic-Micu, 2013).
Questionnaires- this involves using a set of question where one is supposed to answer based on
their view. This technique is suitable for collecting quantitative data from a vast population. It
does not require a heavy budget, which made it suitable to collect data from the hotel’s
customers (Lim, 2018).

REQUIREMENTS
The functional requirements dictate the methods and behaviours of the system (Rastogi 2015).
The following are the functional behaviors of the system:
a. Create new users accounts and assign unique IDs
b. Check and display the available rooms on the hotel’s booking website
c. Describe the specifications of the room (singles, family or double)
d. Allow user to make, delete or modify a booking
e. Calculate the cost of the user’s booking
f. Allow the users to manage and update their profile
g. Allow the administrator to modify, delete or add information on the rooms and other
special offers
The non-functional requirements of the system explain the constraint of the methods. They
include:
a. Performance- the system is supposed to have a high performance, fast and effective.
b. Scalability- The system is supposed to maintain its performance and accommodate a
large number of users.
c. Availability- the system should always be available to the users.
d. Recoverability- system interruption should enable the user to recovery processes and data
e. Maintainability- the system maintenance should be easy
f. Usability- the system must be easy to use
g. Security- the customer information must be kept confidential

ACTIVITY DIAGRAM
Below is the activity diagram of the proposed system for the hotel (Rao, Naidu and Chakka,
2011).
The process starts when a user accesses the system through their website. The user is prompted
to enter username and the system check if the user is registered if not, the user will create a new
account and assigned a unique user ID and password. The registered user enters their password,
an incorrect password prompts the user to reenter the password.
Once the user is successfully logged, they can make a booking for the available rooms, and then
select the payment method for the booking. User has to confirm before cashing out, if not
satisfied they can go back to checking for other rooms. If satisfied, they cash out and the process
ends.

CONCLUSION
From the above report, it is evident that the hotel information system will help in meeting the
users’ and the company’s requirements. From report elaborates the phases involved in the
development of the system, the scrum methodology will ensure that the desired system is
delivered to the user in time. In addition, the UML activity diagram will assist the system
developers in understanding the flow of operations of the system.

REFERENCES
Chowdhury, A.Z.M., Bhowmik, A., Hasan, H. and Rahim, M.S., 2018. Analysis of the veracities
of industry used software development life cycle methodologies. arXiv preprint
arXiv:1805.08631.
Isaias, P. and Issa, T., 2015. Information system development life cycle models. In High Level
Models and Methodologies for Information Systems (pp. 21-40). Springer, New York, NY.
Lim, K., NEXTLABS Inc, 2018. Information management system with two or more interactive
enforcement points. U.S. Patent 9,942,271.
Rao, K.N., Naidu, G.K. and Chakka, P., 2011. A study of the Agile software development
methods, applicability and implications in industry. International Journal of Software
Engineering and its applications, 5(2), pp.35-45.
Rastogi, V., 2015. Software development life cycle models-comparison,
consequences. International Journal of Computer Science and Information Technologies, 6(1),
pp.168-172.
Stoica, M., Mircea, M. and Ghilic-Micu, B., 2013. Software Development: Agile vs.
Traditional. Informatica Economica, 17(4).