PM SHRI SCHOOL

JAWAHAR NAVODAYA VIDYALAYA

CHANDIMAL, BHADRAK -756125,ODISHA

COMPUTER SCIENCE ( 083 )

PROJECT ON
“HOSTEL MANAGEMENT
SYSTEM”
(SESSION : 2024-25)

GUIDED BY: SUBMITTED BY:

MR. JAGANNATHA MOHANTA TANMAYA
BEHERA
PGT COMPUTER SCIENCE ROLL.NO:-
CLASS:-XII
1
 CERTIFICATE

Student’s Name : TANMAYA BEHERA

CLASS – XII (SC.)
School: PM SHRI JAWAHAR NAVODAYA VIDYALAYA

This is to certify that the project “Hotel Management System”

in the subject of Computer Science (083) made by the
student is satisfactory for the fulfillment of AISSCE
requirements.

-----------------------------------
Teacher’s Signature

----------------------------------- ----------------------------------
Examiner’s Signature Principal’s Signature

Date: School Rubber stamp

2
 ACKNOWLEDGEMENT

I
undertook this Project work, as the part of my XII-
Computer Science Practices course. I had tried to apply
best of my knowledge and experience, gained during the
study and class work experience. However, developing
software system is generally a quite complex and time-
consuming process. It requires a systematic study, insight
vision and professional approach during the design and
development. Moreover, the developer always feels the
need, the help and good wishes of the people near you, who
have considerable experience and idea.

At the outset, I would like to extend my sincere thanks

and gratitude to esteemed Principal Sir, DR.BISWANATH
KHILAR , for giving valuable suggestions and moral support
to develop this software.

I would like to extend my sincere thanks and gratitude

to my teacher MR. JAGANNATH MOHANTA, for giving
valuable guidance, time and moral support to develop this
project.

I also feel indebted to my friends for the valuable

suggestions during the project work.

TANMAYA BEHERA

Class XII

3
 TABLE OF CONTENTS [ T O C ]

SER DESCRIPTION PAGE NO

01 ACKNOWLEDGEMENT 04

02 INTRODUCTION 05

03 OBJECTIVES OF THE PROJECT 05

04 PROPOSED SYSTEM 06

05 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 07

06 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE 08

07 FLOW CHART 15

08 SOURCE CODE 16

09 OUTPUT 19

10 TESTING 20

11 HARDWARE AND SOFTWARE REQUIREMENTS 23

12 BIBLIOGRAPHY 24

4
 PROJECT ON HOTEL MANAGEMENT

INTRODUCTION

This project is based on management of hotels, such as informations

about the costomer such as his\her room they book,etc. These information can

be stored in the data and can be verified whenever we want.this computer

programme can be used for hotels etc..

OBJECTIVES OF THE PROJECT

The objective of this project is to let the students apply the programming

knowledge into a real- world situation/problem and exposed the students how

programming skills helps in developing a good software.

1. Write programs utilizing modern software tools.

2. Apply object oriented programming principles effectively when developing

small to medium sized projects.

3. Write effective procedural code to solve small to medium sized problems.

4. Students will demonstrate a breadth of knowledge in computer science, as

exemplified in the areas of systems, theory and software development.

5. Students will demonstrate ability to conduct a research or applied

Computer Science project, requiring writing and presentation skills which

exemplify scholarly style in computer science.

5
PROPOSED SYSTEM

Today one cannot afford to rely on the fallible human beings of be really

wants to stand against today’s merciless competition where not to wise saying

“to err is human” no longer valid, it’s out-dated to rationalize your mistake. So,

to keep pace with time, to bring about the best result without malfunctioning and

greater efficiency so to replace the unending heaps of flies with a

muchsophisticated hard disk of the computer.

One has to use the data management software. Software has been an

ascent in atomizationvarious organisations. Many software products working are

now in markets, which have helped in making the organizations work easier and

efficiently. Data management initially hadto maintain a lot of ledgers and a lot of

paperwork has to be done but now software producton this organization has

made their work fasterand easier. Now only this software has to beloaded on the

computer and work can be done.

This prevents a lot of time and money. The work becomes fully automated

and any information regarding the organization can be obtained by clicking the

button. Moreover, now it’s an age of computers of and automating such an

organization gives the better look.

6
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The systems development life cycle is a projectmanagement technique

that divides complexprojects into smaller, more easily managedsegments or
phases. Segmenting projectsallows managers to verify the successfulcompletion
of project phases before allocatingresources to subsequent phases.
Software developmentprojects typically include initiation, planning,design,
development, testing, implementation,and maintenance phases. However, the
phasesmay be divided differently depending on theorganization involved.
For example, initialproject activities might be designated asrequest,
requirements-definition, and planning phases, or initiation, concept-
development,and planning phases. End users of the systemunder development
should be involved inreviewing the output of each phase to ensurethe system is
being built to deliver the neededfunctionality.

7
 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

INITIATION PHASE

The Initiation Phase begins when a business sponsor identifies a need or an

opportunity.

The purpose of the Initiation Phase is to:

Identify and validate an opportunity to improve business accomplishments

of the organization or a deficiency related to a business need.
Identify significant assumptions and constraints on solutions to that need.
Recommend the exploration of alternative concepts and methods to satisfy
the need including questioning the need for technology, i.e., will a change
in the business process offer a solution?
Assure executive business and executive technical sponsorship. The
Sponsor designates a Project Manager and the business need is
documented in a Concept Proposal. The Concept Proposal includes
information about the business process and the relationship to the
Agency/Organization.
Infrastructure and the Strategic Plan. A successful Concept Proposal
results in a Project Management Charter which outlines the authority of the
project manager to begin
the project.

Careful oversight is required to ensure projects support strategic business

objectives and resources are effectively implemented into an organization's
enterprise architecture. The initiation phase begins when an opportunity to add,
improve, or correct a system is identified and formally requested through the
presentation of a business case. The business case should, at a minimum,
describe a proposal’s purpose, identify expected benefits, and explain how the
proposed system supports one of the organization’s business strategies. The
business case should also identify alternative solutions and detail as many
informational, functional, and network requirements as possible.

8
SYSTEM CONCEPT DEVELOPMENT PHASE

The System Concept Development Phase begins after a business need or

opportunity is validated by the Agency/Organization Program Leadership and the
Agency/Organization CIO.

The purpose of the System Concept Development Phase is to:

Determine the feasibility and appropriateness of the alternatives.

Identify system interfaces.
Identify basic functional and data requirements to satisfy the business
need.
Establish system boundaries; identify goals, objectives, critical success
factors, and performance measures.
Evaluate costs and benefits of alternative approaches to satisfy the basic
functional requirements
Assess project risks
Identify and initiate risk mitigation actions, and Develop high-level
technical architecture, process models, data models, and a concept of
operations. This phase explores potential technical solutions within the
context of the business need.
It may include several trade-off decisions such as the decision to use
COTS software products as opposed to developing custom software or
reusing software components, or the decision to use an incremental
delivery versus a complete, onetime deployment.
Construction of executable prototypes is encouraged to evaluate
technology to support the business process. The System Boundary
Document serves as an important reference document to support the
Information Technology Project Request (ITPR) process.
The ITPR must be approved by the State CIO before the project can move
forward.

9
PICTORIAL REPRESENTATION OF SDLC:

PLANNING PHASE

The planning phase is the most critical step in completing development,

acquisition, and maintenance projects. Careful planning, particularly in the early
stages of a project, isnecessary to coordinate activities and manage project risks
effectively. The depth and formality of project plans should be commensurate
with the characteristics and risks of a given project. Project plans refine the
information gathered during the initiation phase by further identifying the
specificactivities and resources required to complete a project.

A critical part of a project manager’sjob is to coordinate discussions

between user, audit, security, design, development, and network personnel to
identify and document as many functional, security, and networkrequirements as
possible. During this phase, a plan is developed that documents the approach to
be used and includes a discussion of methods, tools, tasks, resources, project
schedules, and user input. Personnel assignments, costs, project schedule, and
target dates are established.

10
 A Project Management Plan is created with components related to
acquisition planning, configuration management planning, quality assurance
planning, concept of operations, system security, verification and validation, and
systems engineering management planning.

REQUIREMENTSANALYSIS PHASE

This phase formally defines the detailed functional user requirements

using high-level requirements identified in the Initiation, System Concept, and
Planning phases. It also delineates the requirements in terms of data, system
performance, security, and maintainability requirements for the system. The
requirements are defined in this phase to a level of detail sufficient for systems
design to proceed. They need to be measurable, testable, and relate to the
business need or opportunity identified in the Initiation Phase. The requirements
that will be used to determine acceptance of the system are captured in the Test
and Evaluation Master Plan.

The purposes of this phase are to:

Further define and refine the functional and data requirements and
document them in the Requirements Document,
Complete business process reengineering of the functions to be supported
(i.e., verify what information drives the business process, what information
is generated, who generates it, where does the information go, and who
processes it),
Develop detailed data and process models (system inputs, outputs, and
the process.
Develop the test and evaluation requirements that will be used to
determine acceptable system performance.

DESIGN PHASE

The design phase involves converting the informational, functional, and

network requirements identified during the initiation and planning phases into

11
unified design specifications that developers use to script programs during the
development phase. Program designs areconstructed in various ways. Using a
top-down approach, designers first identify and link major program components
and interfaces, then expand design layouts as they identify and link smaller
subsystems and connections. Using a bottom-up approach, designers first
identify and link minor program components and interfaces, then expand design
layouts as they identify and link larger systems and connections. Contemporary
design techniques often use prototyping tools that build mock-up designs of items
such as application screens, database layouts, and system architectures. End
users, designers, developers, database managers, and network administrators
should review and refine the prototyped designs in an iterative process until they
agree on an acceptable design. Audit, security, and quality assurance personnel
should be involved in the review and approval process. During this phase, the
system is designed to satisfy the functional requirements identified in the
previous phase. Since problems in the design phase could be very expensive to
solve in the later stage of the software development, a variety of elements are
considered in the design to mitigate risk. These include:

Identifying potential risks and defining mitigating design features.

Performing a security risk assessment.
Developing a conversion plan to migrate current data to the new system.
Determining the operating environment.
Defining major subsystems and their inputs and outputs.
Allocating processes to resources.
Preparing detailed logic specifications for each software module. The
result is a draft System Design Document which captures the preliminary
design for the system.
Everything requiring user input or approval is documented and reviewed
by the user. Once these documents have been approved by the Agency
CIO and Business Sponsor, the final System Design Document is created
to serve as the Critical/Detailed Design for the system.
This document receives a rigorous review by Agency technical and
functional representatives to ensure that it satisfies the business
requirements. Concurrent with the development of the system design, the
12
 Agency Project Manager begins development of the Implementation Plan,
Operations and Maintenance Manual, and the Training Plan.

DEVELOPMENT PHASE

The development phase involves converting design specifications into

executable programs. Effective development standards include requirements
that programmers and other project participants discuss design specifications
before programming begins. The procedures help ensure programmers
clearly understand program designs and functional requirements.
Programmers use various techniques to develop computer programs. The
large transaction oriented programs associated with financial institutions have
traditionally been developed using procedural programming techniques.
Procedural programming involves the line-by-line scripting of logical
instructions that are combined to form a program. Effective completion of the
previous stages is a key factor in the success of the Development phase. The
Development phase consists of:

Translating the detailed requirements and design into system components.

Testing individual elements (units) for usability.
Preparing for integration and testing of the IT system.

INTEGRATION AND TEST PHASE

Subsystem integration, system, security, and user acceptance testing is

conducted during the integration and test phase. The user, with those
responsible for quality assurance, validates that the functional
requirements, as defined in the functional requirements document, are
satisfied by the developed or modified system. OIT Security staff assesses
the system security and issue a security certification and accreditation
prior to installation/implementation.

13
Multiple levels of testing are performed, including:

Testing at the development facility by the contractor and possibly

supported by end users

Testing as a deployed system with end users working together with

contract personnel

Operational testing by the end user alone performing all functions.

Requirements are traced throughout testing, a final Independent
Verification & Validation evaluation is performed and all documentation is
reviewed and accepted prior to acceptance of the system.

IMPLEMENTATION PHASE

This phase is initiated after the system has been tested and accepted by
the user. In this phase, the system is installed to support the intended business
functions. System performance is compared to performance objectives
established during the planning phase. Implementation includes user notification,
user training, installation of hardware, installation of software onto production
computers, and integration of the system into daily work processes. This phase
continues until the system is operating in production in accordance with the
defined user requirements.

OPERATIONS AND MAINTENANCE PHASE

The system operation is on-going. The system is monitored for continued

performance in accordance with user requirements and needed system
modifications are incorporated. Operations continue as long as the system can
be effectively adapted to respond to the organization’s needs. When
modifications or changes are identified, the system may re-enter the planning
phase.

14
The purpose of this phase is to:

Operate, maintain, and enhance the system.

Certify that the system can process sensitive information.
Conduct periodic assessments of the system to ensure the functional
requirements continue to be satisfied.
Determine when the system needs to be modernized, replaced, or retired.

SOURCE CODE
import datetime

# Define Room Class

class Room:

def __init__(self, room_number, room_type, price):

self.room_number = room_number

self.room_type = room_type

self.price = price

self.is_available = True

def book(self):

self.is_available = False

def checkout(self):

self.is_available = True

# Define Hotel Class

class Hotel:

15
 def __init__(self, name):

self.name = name

self.rooms = []

def add_room(self, room):

self.rooms.append(room)

def show_available_rooms(self):

print("\nAvailable Rooms:")

for room in self.rooms:

if room.is_available:

print(f"Room Number: {room.room_number},

Type: {room.room_type}, Price: ${room.price}")

def book_room(self, room_number):

for room in self.rooms:

if room.room_number == room_number and

room.is_available:

room.book()

print(f"\nRoom {room_number} has been

successfully booked!")

return

print("\nRoom is not available!")

def checkout_room(self, room_number):

for room in self.rooms:

16
 if room.room_number == room_number and not

room.is_available:

room.checkout()

print(f"\nRoom {room_number} has been

successfully checked out!")

return

print("\nRoom is not checked in or invalid room

number!")

# Main Menu Functions

def display_menu():

print("\n--- Hotel Management System ---")

print("1. Add Room")

print("2. Show Available Rooms")

print("3. Book Room")

print("4. Checkout Room")

print("5. Exit")

def main():

hotel = Hotel("Hotel Python") # Create an instance of

Hotel

# Pre-add some rooms for demonstration

hotel.add_room(Room(101, "Single", 50))

hotel.add_room(Room(102, "Double", 75))

hotel.add_room(Room(103, "Suite", 150))

17
 while True:

display_menu()

choice = input("Enter your choice (1-5): ")

if choice == '1':

room_number = int(input("Enter room number: "))

room_type = input("Enter room type

(Single/Double/Suite): ")

price = float(input("Enter room price per night:

"))

hotel.add_room(Room(room_number, room_type,

price))

print(f"\nRoom {room_number} added

successfully!")

elif choice == '2':

hotel.show_available_rooms()

elif choice == '3':

room_number = int(input("Enter room number to

book: "))

hotel.book_room(room_number)

elif choice == '4':

18
 room_number = int(input("Enter room number to

checkout: "))

hotel.checkout_room(room_number)

elif choice == '5':

print("\nExiting Hotel Management System...")

break

else:

print("Invalid choice, please try again.")

# Run the hotel management system

if __name__ == "__main__":

main()

19
 TESTING

Software Testing is an empirical investigation conducted to provide

stakeholders with information about the quality of the product or service under
test[1] , with respect to the context in which it is intended to operate. Software
Testing also provides an objective, independent view of the software to allow the
business to appreciate and understand the risks at implementation of the
software. Test techniques include, but are not limited to, the process of executing
a program or application with the intent of finding software bugs.
It can also be stated as the process of validating and verifying that a
software program/application/product meets the business and technical
requirements that guided its design and development, so that it works as
expected and can be implemented with the same characteristics. Software
Testing, depending on the testing method employed, can be implemented at any
time in the development process, however the most test effort is employed after
the requirements have been defined and coding process has been completed.

TESTING METHODS
Software testing methods are traditionally divided into black box testing
and white box testing. These two approaches are used to describe the point of
view that a test engineer takes when designing test cases.

20
BLACK BOX TESTING
Black box testing treats the software as a "black box," without any
knowledge of internal implementation. Black box testing methods include:
equivalence partitioning, boundary value analysis, all-pairs testing, fuzz testing,
model-based testing, traceability matrix, exploratory testing and specification-
based testing.

SPECIFICATION-BASED TESTING

Specification-based testing aims to test the functionality of software

according to the applicable requirements.[16] Thus, the tester inputs data into,
and only sees the output from, the test object. This level of testing usually
requires thorough test cases to be provided to the tester, who then can simply
verify that for a given input, the output value (or behaviour), either "is" or "is not"
the same as the expected value specified in the test case. Specification-based
testing is necessary, but it is insufficient to guard against certain risks

ADVANTAGES AND DISADVANTAGES

The black box tester has no "bonds" with the code, and a tester's
perception is very simple: a code must have bugs. Using the principle, "Ask and
you shall receive," black box testers find bugs where programmers don't. But, on
the other hand, black box testing has been said to be "like a walk in a dark
labyrinth without a flashlight," because the tester doesn't know how the software
being tested was actually constructed.
That's why there are situations when (1) a black box tester writes many
test cases to check something that can be tested by only one test case, and/or
(2) some parts of the back end are not tested at all. Therefore, black box testing
has the advantage of "an unaffiliated opinion," on the one hand, and the
disadvantage of "blind exploring," on the other.

WHITE BOX TESTING

21
 White box testing, by contrast to black box testing, is when the tester has
access to the internal data structures and algorithms (and the code that
implement these)

Types of white box testing:-

The following types of white box testing exist:
api testing - Testing of the application using Public and Private
APIs.
Code coverage - creating tests to satisfy some criteria of code
coverage.
For example, the test designer can create tests to cause all statements in
the program to be executed at least once.
fault injection methods.
mutation testing methods.
static testing - White box testing includes all static testing.

CODE COMPLETENESS EVALUATION

White box testing methods can also be used to evaluate the completeness
of a test suite that was created with black box testing methods. This allows the
software team to examine parts of a system that are rarely tested and ensures
that the most important function points have been tested.

Two common forms of code coverage are:

FunctionCoverage: Which reports on functions executed and
StatementCoverage:Which reports on the number of lines executed
to complete the test.
They both return coverage metric, measured as a percentage

HARDWARE AND SOFTWARE REQUIREMENTS

I.OPERATING SYSTEM : WINDOWS 7 AND ABOVE

22
II. PROCESSOR : PENTIUM(ANY) OR AMD

ATHALON(3800+- 4200+ DUALCORE)

III. MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM 0R

MSI

K9MM-V VIAK8M800+8237R PLUS

CHIPSET FOR AMD ATHALON

IV. RAM : 512MB+

V. Hard disk : SATA 40 GB OR ABOVE

VI. CD/DVD r/w multi drive combo: (If back up required)

VII. FLOPPY DRIVE 1.44 MB : (If Backup required)

VIII. MONITOR 14.1 or 15 -17 inch

IX. Key board and mouse

X. Printer : (if print is required – [Hard copy])

SOFTWARE REQUIREMENTS:

I. Windows OS
II. Python

23
 BIBLIOGRAPHY

1. Computer science With Python - Class XII By : Tanmaya behera

A Hotel Management System is a software application designed to streamline the

operations of a hotel, covering various aspects like guest management, room booking,
billing, and other hotel operations. If you're working on a Computer Science (CS)
project related to Hotel Management, here’s a brief overview and suggestions to help you
develop the project.

Key features for hotelmanagement :

1. User Management
o Login/Signup: Create user profiles (admin, hotel staff, guest).
o Guest Management: Track guest check-in, check-out, preferences, and special
requests.

2. Room Management
o Room Booking: Booking rooms based on availability.
o Room Status: Mark rooms as available, occupied, under maintenance, or
reserved.
o Room Types: Differentiate between room types (standard, deluxe, suite).
o Room Rate Management: Set prices for different seasons or special offers.

3. Billing and Payments

o Invoice Generation: Generate bills based on room charges, additional services,
and taxes.
o Payment Management: Integrate payment methods like credit cards, cash, or
digital wallets.
o Discounts and Offers: Handle special promotions or discount codes.

4. Check-In/Check-Out
o Check-In Process: Record guest details, assign rooms, and track check-in times.
o Check-Out Process: Calculate the total stay cost, generate bills, and update
room status.

5. Reporting and Analytics

o Reports: Generate daily, weekly, and monthly reports for bookings, occupancy,
revenue, etc.
o Analytics: Track occupancy rates, revenue trends, and guest satisfaction metrics.

6. Staff Management
o Shift Scheduling: Assign and track staff work hours.
o Payroll: Handle staff salaries, bonuses, and deductions.

24
 7. Reservation System
o Online Booking: Allow customers to book rooms online (if you include a web
front-end).
o Cancellation & Modification: Allow guests to modify or cancel reservations.

8. Admin Panel
o User Permissions: Admin should be able to manage all operations and assign
roles to staff members.
o Dashboard: A central dashboard for admin to monitor hotel performance

1. Frontend Development (for web-based systems):

o HTML/CSS/JavaScript: To build the structure, style, and interactivity.
o Frontend Frameworks: React.js, Angular, or Vue.js for dynamic interfaces.
o Bootstrap or Material UI: To speed up UI development.

2. Backend Development:
o Programming Languages: Python (with Flask/Django), Java (with Spring), or
Node.js (with Express) for backend logic.
o Database: SQL-based databases like MySQL, PostgreSQL, or non-SQL databases
like MongoDB for storing hotel data (guest details, room bookings, etc.).
o Authentication: JWT (JSON Web Token) or sessions for user login security.

3. Mobile App (optional):

o You can also create a mobile version of the hotel management system using
technologies like Flutter, React Native, or native development (Java/Kotlin for
Android or Swift for iOS).

4. Additional Features:
o API Integration: If you plan to implement features like payment gateways
(Stripe, PayPal), integrate APIs for payments.
o SMS/Email Notifications: Use services like Twilio or SendGrid to send booking
confirmations or alerts.

5. Tools for Database Design:

o ERD (Entity-Relationship Diagram): Tools like MySQL Workbench, Lucidchart, or
dbdiagram.io for visualizing the database schema.

Example Project Flow:

1. Admin Login: Admin logs in to the system with username and password.
2. Dashboard: Admin views the hotel’s booking stats, occupancy, and revenue summary.
3. Room Management: Admin can add rooms, set rates, and change room status.
4. Booking: Guests can make room reservations, check-in, and check-out.
5. Billing: On check-out, generate a bill based on the room stay, extra services, and taxes.
6. Reports: Admin can generate reports on revenue, occupancy, and guest statistics.

Project Implementation Steps:

1. Requirement Analysis:
o Identify the user roles (admin, staff, guest).

25
 o Gather functional and non-functional requirements for the system.

2. Database Design:
o Design tables for guests, rooms, bookings, payments, staff, etc.
o Define relationships and attributes for each entity (e.g., guests have multiple
bookings).

3. Front-End and Back-End Development:

o Build the UI components (forms for login, booking, and billing).
o Implement back-end logic to handle booking, check-in/check-out, and billing
processes.

4. Testing:
o Test individual modules like room booking, payment processing, etc.
o Perform integration testing to ensure the entire system works cohesively.

5. Documentation:
o Provide clear and concise documentation for the system, including installation
instructions, features, and usage.

Example of Basic Database Schema:

1. Guests Table
o guest_id (Primary Key)
o first_name
o last_name
o email
o phone_number
o address

2. Rooms Table
o room_id (Primary Key)
o room_number
o room_type
o price
o status (available, occupied, maintenance)

3. Bookings Table
o booking_id (Primary Key)
o guest_id (Foreign Key)
o room_id (Foreign Key)
o check_in_date
o check_out_date
o total_amount

4. Payments Table
o payment_id (Primary Key)
o booking_id (Foreign Key)
o payment_amount
o payment_method (Credit Card, Cash, etc.)

26
 o payment_date

5. Staff Table
o staff_id (Primary Key)
o name
o role
o salary

27