Department Of Computer Science

Certificate

This is to certify that Ms./ Mr._________________________

have successfully and satisfactorily completed and submitted
the field project titled ________________________________
____________________ in partial fulfilment of S.Y.B.Sc (CS)
Lab course CS-231-FP Semester III prescribed by Savitribai
Phule Pune University during the academic year _________.

(Project Guide) (H.O.D. Computer Science)

INTERNAL EXAMINER EXTERNAL EXAMINER

 Submission Deadline: / /

S.Y.B.Sc(Computer Science) Mini Project

Academic Year (20 - 20 )

Project Title:______________________________________

Team Members:

1) Name : ______________________________________

Roll No . Exam Seat No:

2) Name : ______________________________________

Roll No . Exam Seat No:

Project Guide Name :___________________________

Project Guide Signature :________________________

Start Date: / / Completion Date: / /

 Field Project using Software Engineering Techniques
S.Y.B.Sc(Computer Science)
Major: Computer Science
CS-231-FP Semester III
Field Project

Name: _________________________________________
Collage Name: __________________________________
Roll No.: _______________ Division: ____________

Academic Year: _______________

 Index
Assignment No. Title Signature of Instructor
1 Preliminary Investigation and its activities

1.1 Problem identification and definition

1.2 Problem Description

1.3 Fact Finding Techniques

1.4 Drawbacks of Existing system

1.5 Scope of the Proposed System

1.6 Feasibility Study

2 Requirement Specification

2.1 Data Requirement of the System

2.2 Identify End Users of the System

2.3 Input Data to the System

2.4 Output Information from the System

2.5 Functional / Non-Functional / Processing Requirements

of the System

3 Database Design

3.1 Identify the Entities and the Attributes

3.2 E-R Diagram

3.3 Identifying all tables, fields, relationships between tables

etc.

3.4 Normalize database

4 System Design

4.1 Class diagram

4.2 Object diagram

4.3 Component diagram

4.4 Deployment diagram

4.5 Use Case diagram

4.6 Activity diagram

4.7 State Chart diagram

4.8 Sequence diagram

4.9 Collaboration diagram

 INTRODUCTION
This case study introduces a hotel management system (HMS), a
software solution designed to automate and streamline daily hotel
operations, moving from inefficient, error-prone manual systems to a
comprehensive computerized platform. The context is the modern,
highly competitive hospitality industry, where efficiency, accuracy, and
excellent customer service are paramount. The problem addressed is
the manual management of tasks like guest reservations, room status
tracking, billing, and inventory, which often leads to operational
slowdowns, increased errors, and poor data management. This case
study proposes an HMS to resolve these challenges by providing a
centralized, user-friendly system to manage all aspects of hotel
operations, from initial bookings and check-ins to checkout and
financial reporting, ultimately aiming to improve guest satisfaction and
overall hotel profitability.
1) PRELIMINARY INVESTIGATION AND ITS
ACTIVITIES:

1.1) PROBLEM IDENTIFICATION AND DEFINITION

• In the modern hospitality industry, hotels play a significant role in

providing services such as lodging, food and recreational facilities,
with increasing competition and customer expectations hotels need
to provide high-quality service in a timely and efficient manner.
• Most small and medium-scale hotels still operate using manual
system for customer registration, room allocation, billing, and
record-keeping. These manual processes, and difficulty in
retrieving past records.
• Therefore, there is a clear need for a computerized Hotel
Management System (HMS) that will automate and streamline
hotel operations. The system should manage booking and reporting
all through a centralized, secure platform.
1.2) PROBLEM DESCRIPTION:
a) Hotels deal with a wide range of task daily customer arrivals, room
assignments reservation cancellation, billing and more when handled
manually these processes often result in:

-Overbooking or booking conflicts.

-Errors in customer billing & payments.
-Difficulty locating past records or tracking customer history.
-Delays in customer check-in/check-out. processes.
-Inability to generate timely reports (Income, occupancy, etc).

b) This leads to both internal inefficiency & poor customer experience.

A hotel may lose business simply due to mismanagement.
There is also no real-time information available for room
availability or customer status. Paper based systems are also prone
to loss or damage.
1.3) FACTS FINDING TECHNIQUES:
• To better understand the requirements & current system limitations,
various fact-finding techniques were employed.

i) Observation:
The front desk operations were observed for several days to
note the time taken for check-in, manual ledger updates &
billing operations.

ii) Document Analysis:

Existing formats such as booking registers, bill receipts &
customer files were analysed to understands the structure of
current data handling & storage methods.
1.4) DRAWBACKS OF THE EXISTING SYSTEM:

1. High chances of human error in booking & billing.

2. No real-time visibility of room availability.
3. Manual records are difficult to manage, sort, or back up.
4. Customer service is delayed during peak hours.
5. Reports are prepared manually, which is time-consuming &
error-prone.
6. No proper communication between departments (e.g. front desk
& housekeeping).
7. Cannot track customer preferences, booking history, or
payment patterns.
1.5) SCOPE OF THE PROPOSED SYSTEM:

• The proposed hotel management system aims to automate core hotel

functions through a centralized software applications that can be
accessed by staff & administrators. The system will.

-Provide an interface for booking rooms.

-Track room status (available, booked, occupied, maintenance).
-Record guest details & maintain digital history.
-Generate bills based on stay duration & services used.
-Handle payments (cash, card, UPI).
-Generate daily/monthly reports.
-Improve customer experience by reducing waiting time & errors.

• Optional features:
-Online booking portal.
-Feedback & rating system.
-SMS/email notifications.
1.6) FEASIBILITY STUDY:
a) Technical Feasibility:
- The system will be developed using standard technologies such as
python, PHP, or Java with MySQL as the backend database. These
technologies are open-source & widely Supported.
b) Operational Feasibility:
-Staff with basic computer knowledge can operate the system with
minimal training. The user interface will be designed for ease of use.
c)Economic Feasibility:
-The use of open-source tools keeps the development cost low. The
long-term benefits (time saved, improved accuracy, better customer
service). Make the system economically viable for any hotel.
2) REQUIREMENT SPECIFICATION:

2.1) DATA REQUIREMENT OF THE SYSTEM:

• The system must collect, store & retrieve the following data:
-Customer Details:
Name, ID proof, contact Information, address.
-Room Information:
Room number, type (single/Double/ Suite) price, current
status.
-Booking Data:
Booking ID, check-in date, check-out date, assigned room.
-Payment Details:
Payment ID, amount, payment method, date.
-Staff Records:
Staff ID, name, role and access level.
2.2) IDENTIFY END USERS OF THE SYSTEM:

1. Receptionist:
o Books and cancels rooms.
o Handles check-in/check-out.
o Manage customer details.
o Generates bills.

2. Admin / Hotel Manager:

o Oversees all operations.
o Manages rooms, pricing, reports
o Manages staff and user access.

3)Customer (Optional):
o Book rooms online.
o Receive confirmation messages
o Give feedback and ratings
2.3) INPUT TO THE SYSTEM:
• Customer registration information.
• Booking details (room type, dates, number of guests).
• Check-in / check-out times.
• Payment confirmation and method.
• Staff logins and activities.
2.4) OUTPUT FROM THE SYSTEM:
• Booking confirmation receipt.
• Real-time availability report.
• Customer invoice (automatically calculated).
• Daily summary report of check-outs/check-ins.
• Occupancy report, income report, and feedback Summary.
2.5) FUNCTIONAL & NON-FUNCTIONAL REQUIREMENTS:
• Functional Requirement:
o Add / edit / delete customers.
o Room booking and Cancellations.
o Perform check-in and check-out.
o Generate Customer bill.
o Process payment and update status.
o Generate and export reports

• Non- Functional Requirements:

o Security: Login system with role-based access.
o Usability: Simple, intuitive interface.
o Performance: Fast response time even with larger data.
o Backup: Automatic daily backups.
o Scalability: Should handle increasing number of rooms and
user.

• Processing Requirements:
o Calculate bill based on room price x stay duration.
o Validate room availability during booking.
o Generate unique booking & payment.
3)DATABASE DESIGN:
3.1) Entities and Attributes:

Entities Attributes

Customer Customer-ID(PK), Name, Phone, Email Address.

Room Room-ID(PK), Room-Number. Type, price, status.

Booking Booking-ID (PK), Customer-ID(FK), Room-ID(FK),

Check-In, Check-Out, Total Amount

Payment Payment ID (PK), Bocking ID (FK), Amount,

Payment-Dite, method.

Staff Staff-ID (PK), Name, Role, Contact

3.2) ER Diagram:
 3.3) Tables And Relationships:

Table Primary Key Foreign Keys Relationships

Customer Customer-ID - One Customer → many booking

Room Room-ID - One Room → many bookings

Booking Booking-ID Customer-ID, Each booking →one customer,

Room-ID one room.

Payment Payment-ID Booking-ID Each payment → one booking

Staff Staff-ID - Optional: can manage

bookings/rooms.
3.4) Normalization:
• 1NF = All fields are atomic-no multivalued fields.
• 2NF = All non-key attributes fully depend on the primary key.
• 3NF = There are no transitive dependencies.
4) System Design:
4.1) Class diagram:
4.2) Class Diagram:
4.3) Component Diagram:
4.4) Deployment Diagram:
4.5) Use Case Diagram:
4.6) Activity Diagram:
4.7) State Chart Diagram:
4.8) Sequence Diagram:
4.9) Collaboration diagram: