Contents

1.1 INTRODUCTION.....................................................................................................................2
1.2 Objectives..............................................................................................................................2
2.1 Methodology..............................................................................................................................3
2.1.1 System Analysis..................................................................................................................3
2.2 Requirement Analysis................................................................................................................4
2.2.1. Functional Requirements...................................................................................................4
2.2.1.1 Use Case Diagram...........................................................................................................5
2.2.2 Non-Functional Requirements............................................................................................6
3.1 Diagrams....................................................................................................................................7
3.1.1 Data Modelling (ER-Diagram)...........................................................................................7
3.1.2 Class Diagram.....................................................................................................................8
3.1.3 Sequence Diagram..............................................................................................................9
3.1.4 Activity Diagram..............................................................................................................10
4.1 Testing.....................................................................................................................................12
4.1.1 Cases for Unit Testing......................................................................................................12
4.1.2. Cases for System Testing................................................................................................18
1.1 INTRODUCTION
The project Online Hotel Reservation System is a web-based application that allows the hotel
administration to handle all hotel reservation activities online. Interactive GUI and the ability to
manage bookings of various rooms make this system very flexible and convenient. It is hard to
sit and manage the entire activities manually on paper or on desktop applications. This
application gives the power and flexibility to manage the entire system from a single online
system. Hotel Reservation project provides room booking, room managing and other necessary
hotel management features. The system allows to add rooms in the system online easily with
proper details of rooms. Customers can view and book room online. Admin has the power of
either approving or disapproving the customer’s booking request. Other hotel services can also
be viewed by the customers and they can send their feedback too. The system is hence useful for
both customers and hotel administration for portable management of the hotel activities.

1.2 Objectives
The main objectives of designing this system are:
 Develop a system that will surely satisfy the customers.
 Provide people seeking hotel with accurate information about available accommodations.
 To provide an automated system in which customers will have lots of advantages, better
management of data and improved security.
 Customers can easily register at any point of time sitting at home and login for their
purpose.
 Present the hotel as an excellent, or the best choice to its target market
 To simplify the work of hotel employees in a simplistic manner without any issue.
 Provide fast and accurate services to the customers.
 Taking feedback from customer so that the we can improve our system.
2.1 Methodology
2.1.1 System Analysis
Systems analysis is the process of examining a situation for the purpose of developing a system
solution to a problem or troubleshooting when a problem arises. It refers to the analysing of the
various system components to determine whether the final system will provide the expected
result immediately or over the course of time by using specific logic and functions.
This chapter discusses the overall study design and data analysis for the proposed hotel
reservation management System, for development and understanding covering whole activities
of the project. The design and methodology probably needed in any application or system as it
serves as a basis for the development of the project. It also serves as a guide in following the
step-by-step procedure. This could also help the users understand about the proposed system.
There are different model of System Development Life cycle; one of it is incremental model that
helped in step-by-step procedure of this system. I’ve chosen incremental model because we can
develop an initial build with known requirements and can add other modules easily in another
build.

Figure 1: Incremental model

2.2 Requirement Analysis
Requirement analysis is one of the most important aspects of system analysis as it is used to determine the
needs for the system being developed and what the system is expected to do that will differentiate it from
the current system in place.

2.2.1. Functional Requirements

Functional requirements are those requirements that must be included in the system; these
requirements are needed for the system to function as intended. It defines the complex system
requirements in basic form as it is very important to make them clear to the non-technical users
of the system. This handles how data is entered into the system, how it is handled and how data
is displayed to various users. The functional requirements are mapped using Use Case diagrams
as it shows the functions of the system at the most basic level.

Here are the some common functional requirement of hotel reservation system:
User Registration and Authencation.
 User Should be able to create account
 User should be to log in securely.

Search and Booking

 User should be able to search for available hotel rooms based on various criteria such as location,
date, room type, and price.
 User should be able to view detailed information about each room, including amenities, pricing
and availability
 Users should be able to select a room and make a reservation.

User profile:
 Users should be able to update their profile information, including contact details and payment
methods.
 Users should be able to view their reservation history.

Room Management:
  Hotel staff should be able to add, edit, or delete rooms and room details (e.g., room type, price,
description).
 Hotel staff should be able to set and update room availability and pricing.

Reservation Manage:
 Hotel staff should be able to view and manage reservations, including checking guests in and out.
 The system should send confirmation emails to guests upon booking and provide booking details
to hotel staff.

Feedback and Reviews:

 Users should be able to leave reviews and ratings for their stay.

2.2.1.1 Use Case Diagram

Use-case Diagram is the interaction between system and actors. In the given use-case diagram it
shows the interaction between Admin and Hotel Reservation system and Custome i.e., Admin
and Customers.
Figure 2: USE Case Diagram

2.2.2 Non-Functional Requirements

Non-functional requirements enhance the system by providing quality-based attributes which
leads to system running more smoothly and efficiently. These requirements are to enhance user
experience by making sure system is responsive, fast and works as intended.

To achieve successful implementation of non-functional requirements various steps were taken

to ensure smooth and efficient execution of system for both end user and admin. Images are
stored in separate folder rather than on database to reduce load on web server and database to
ensure smooth running of both front and back end. Design files linked locally as well as to the
internet so even if internet is down, the design off the site remains consistent.
Performance: The system is hosted on local host so the system response time is quick. The
database is also centrally hosted with limited data so there is little performance drop when using
the system. Images are not stored in database which results in better performance.

Security: In terms of security, only basic data security measures are followed, data is bound to
ensure that there is no SQL injection. Only admin has access to backend so it is safe from
unauthorized user access.

Scalability: This is an alpha version of the project; it is tested by developers themselves so there
is potential to make a beta version and make it available to actual user.

Maintenance: The system is not to use as it is developed keeping both technical and
nontechnical users in mind so maintaining the system is not complicated.

3.1 Diagrams
3.1.1 Data Modelling (ER-Diagram)
An Entity-Relationship (ER) diagram is a graphical representation of the data model that defines
the structure and relationships of entities (objects or concepts) within a database. ER diagrams
are commonly used in database design and serve as a visual tool to depict the logical structure of
a database.
Figure 3: ER-Diagram

3.1.2 Class Diagram

A class diagram in the Unified Modelling Language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their attributes,
operations (or methods), and the relationships among objects.
Figure 4: Class Diagram

3.1.3 Sequence Diagram

UML Sequence Diagrams are interaction diagrams that detail how operations are carried out.
They capture the interaction between objects in the context of a collaboration. Sequence
Diagrams are time focus and they show the order of the interaction visually by using the vertical
axis of the diagram to represent time what messages are sent and when.
Figure 5: Sequence Diagram

3.1.4 Activity Diagram

An activity diagram is a type of UML (Unified Modelling Language) diagram used in software
engineering and system design to represent the flow of activities or processes within a system or
a specific part of a system. It is a visual representation that helps in understanding, modelling,
and documenting the steps, actions, and decisions involved in a particular workflow or process.
Figure 6:Activity Diagram
4.1 Testing
Software Testing is evaluation of the software against requirements gathered from users and
system specifications. Testing is conducted at the phase level in software development life cycle
or at module level in program code.

4.1.1 Cases for Unit Testing

Test Test case Test steps Test data Expected Result Actual Pass/
case id scenario result Fail

T01 User loginNavigate to Email: If admin As Pass

login page fill expected,
redirect to dashboard
email &
password ramstha@gmai Else
fields and click l
redirect to home page
login button
.co

Password:
password
Table 1: Test case for login

Test case Test case Test steps Test data Expected Result Actual result Pass/
id scenario Fail

T02 Sign up Navigate to Name, New user should As expected Pass

sign up page address, be created and
and fill all the redirected to login
fields and phone, email, page with sign up
click login password, etc. successful message
button

Table 6: Test case for sign up

Test Test case Test steps Test data Expected Result Actual Pass
case id scenario result /Fail

T03 Add Navigate to users Name, New admin should As Pass

admin page in admin panel address, be created expected,
and click add admin phone, and display
button then fill all the email, “admin
fields and click add password, added successfully”
admin button etc. message

Table 7: Test case for add admin

Test Test case Test steps Test data Expected Result Actual Pass
case id scenario result /Fail

T04 Edit user Navigate to Name, UUser details should be As Pass

details users page in address, updated in database expected,
admin panel and
click edit link phone, email, and display “user
make necessary password, details updated
changes to
type, etc.
previous details successfully” message
and click update
button

Table 8: Test case for user edit

Test Test case Test steps Test data Expected Result Actual Pass/
case id scenario result Fail

T05 Delete Navigate to Click the User should be deleted As Pass

user users page in delete from database and expected,
display “User deleted
admin panel link
successfully” message
and click delete
link then fill all
the fields and
click add admin

button
Table 9: Test case for delete user

Test Test case Test steps Test data Expected Result Actual Pass/
case id scenario result Fail

T06 User Navigate to Name, Message should be As Pass

feedback contact us page phone, email, inserted in database expected,
or and show “message
message and fill all the and sent successfully”
fields and click message. message to user
send message

button
Table 10: Test case for user feedback
`Test Test case Test steps Test data Expected Result Actual Pass/
case id scenario result Fail

T07 Add Navigate toRoom type, Rooms should be As Pass

rooms accommodations washrooms, inserted in database expected,
and display “room
page in admin beds, guests added successfully”
dashboard and message
click add rooms and price
link then fill all
the room details
and submit the
form

Table 11: Test case for add rooms

Test Test case Test steps Test data Expected Result Actual Pass/
case id scenario result Fail

T08 Edit room Navigate toRoom type, Room details should As Pass

details accommodations washrooms, be updated in database expected,

page in admin and display “room
beds, guests
dashboard and details updated
click edit link and price
then make successfully” message
changes to the
details and submit
the form

Table 12: Test case for edit room details

Test Test case Test steps Test data Expected Result Actual Pass/
case id scenario result Fail

T09 delete Navigate Click the

Room should be deleted As Pass
room from database and expected,
accommodations delete link
display “room deleted
page in admin successfully” message
dashboard and

click delete link

Table 13: Test case for delete room

Test Test case Test steps Test data Expected Result Actual Pass/
case id scenario result Fail

T10 Reserve Navigate to No. of guests, If room is As Pass

ion accommodations page room type, available for that expected,
request and click book now date the reservation
from user button of desired room check-in date request should be
and fill the reservation and check-out sent
details and submit the
form date

Table 14: Test case for reservation request (user)

Test Test case Test steps Test data Expected Result Actual Pass/
case id scenario result Fail

T11 Reservation Navigate to Change If room is available for As Pass

verification reservations reservation that date the reservation expected,
and approval page in admin
panel and status request should be
recheck [requested, confirmed by admin
whether the
confirmed, otherwise request
room is
available or not cancelled, should be
if available then booked,
confirm request cancelled
otherwise checked
cancel out]
reservation and press ok.
request
Table 15: Test case for reservation verification and approval
4.1.2. Cases for System Testing

S.NO. Test Case Excepted Actual Result Remarks

Result

1. User User should be User registered No error

registered
Registration

2. User Login User should be Logged in No error

logged in

3. Adding rooms Rooms should Rooms added No error

be added

4. Send feedback Feedback should Feedback sent No error

be sent

5. Make Reservation Request sent No error

request
reservation
should be
sent

6. Integrate all System should System worked No error

modules together function well as expected

Table 16: Test case for system testing