GURU GOBIND SINGH INDRAPRASTHA

UNIVERSITY, DWARKA

Bachelor of Computer Applications

BATCH 2023-2026
SEMESTER -4

PRACTICAL FILE

SOFTWARE ENGINEERING

COURSE CODE – BCA 204

SUBMIITED BY ANKIT MISHRA

ENROLLMENT NUMBER 00896702023
SUBMITTED TO MS. PRIYANKA
 HOTEL MANAGEMENT SYSTEM

S.NO. TOPIC SIGNATURE

1 Select and Write down the problem statement for a real-time Hotel
Management System of relevance

2 Analyze requirement for a Hotel Management System and develop Software

Requirement Specification Sheet (SRS) for Hotel Management System.

3 To create the function-oriented diagram: Data Flow Diagram (DFD) for Hotel
Management System

4 To perform the user’s view analysis for the Hotel Management System: Use
case diagram

5 To draw the structural view diagram for the Hotel Management System: Class
diagram

6 To draw the behavioral view diagram: Activity diagram for Hotel Management
System

7 To perform the behavioral view diagram for the Hotel Management System:
Sequence diagram

8 Draw the component diagram for Hotel Management System

9 Draw the Deployment diagram for Hotel Management System

10 Draw the ER diagram for Hotel Management System.

1.SELECT AND WRITE DOWN THE PROBLEM STATEMENT FOR A
REAL TIME HOTEL MANAGEMENT SYSTEM OF RELEVANCE.

Hotel Management System Problem:

The management of a hotel involves numerous complex tasks that must be coordinated
efficiently to provide a high level of service to guests. However, as the hotel business grows
in size and complexity, the manual or outdated systems that were once sufficient can become
inefficient, prone to errors, and time-consuming.

The common problems faced by hotels due to these inefficient systems include:

1. Errors in Reservation Management:

o Problem: In a manual or outdated reservation system, booking details can get
mixed up, leading to issues such as double bookings (when two guests book
the same room) or reservations being lost.
o Impact: This leads to poor customer experience and loss of potential revenue.
Customers may also feel frustrated and dissatisfied if their reservations aren't
handled properly.
o Solution: A modern Hotel Management System (HMS) should automate the
reservation process, track room availability in real-time, and send
confirmations and updates to guests automatically.
2. Inefficient Check-In/Check-Out Process:
o Problem: Traditional or manual check-in/check-out processes can be slow and
error-prone, leading to long waiting times, guest frustration, and overworked
staff. Staff may have to manually verify guest identities, allocate rooms, and
process payments.
o Impact: This can result in delayed service, long queues, and dissatisfied
customers. The staff might also make mistakes in managing guest details.
o Solution: An efficient system can speed up check-in/check-out with
automated guest verification, instant room allocation, and seamless payment
processing. It could also allow guests to check in or check out via mobile apps
or self-service kiosks.
3. Difficulty in Tracking Billing and Payments:
o Problem: Managing guest bills, tracking payments, and handling invoicing
manually can result in errors, confusion, and delays in payment processing.
o Impact: It can lead to disputes with guests over charges, missed payments, or
incorrect billing. Additionally, it increases the workload for staff who have to
manually calculate charges for services like room rates, room service, spa
treatments, and others.
o Solution: A robust HMS should offer automated billing features that track
room charges, services, taxes, and other fees in real-time. It can also provide
 guests with an easy-to-understand bill and allow them to make payments
easily via online methods.
4. Inventory Management Issues:
o Problem: Hotels must manage a large number of resources, such as cleaning
supplies, room amenities, food and beverages, and more. Without real-time
tracking, inventory shortages, overstocking, and wastage can occur.
o Impact: This can affect the quality of service (e.g., a guest not getting the
amenities they requested) or result in financial loss due to overstocking.
o Solution: The HMS should include an integrated inventory management
module that tracks stock levels in real-time, alerts when supplies are running
low, and helps in managing purchases efficiently.
5. Staff Coordination Challenges:
o Problem: In large hotels with various departments (housekeeping,
maintenance, front desk, room service, etc.), effective communication between
staff members is critical. However, without a centralized system, staff can
miss important updates, leading to confusion, delays, and errors.
o Impact: Poor communication can result in service delays (e.g., maintenance
requests not being fulfilled, rooms not being cleaned in time), leading to guest
dissatisfaction.
o Solution: A modern HMS should have a communication feature where tasks
and requests can be assigned to staff in real time, with notifications and
progress tracking. This ensures that all staff members are on the same page
and that tasks are completed on time.

The Need for an Integrated Hotel Management System (HMS):

Given the challenges outlined above, an integrated Hotel Management System (HMS)
becomes essential. The system should:

1. Automate and Streamline Daily Operations: The system should automate key hotel
operations like reservations, check-ins/outs, billing, and communication between
departments. This reduces the burden on staff and ensures more accurate, timely
services to guests.
2. Real-Time Data and Updates: A modern HMS should provide real-time updates on
room availability, guest check-ins, and check-outs. This will help prevent
overbookings and ensure accurate room management.
3. User-Friendly Interface for Both Staff and Guests: The system should be easy to
use for hotel staff. It should be intuitive, minimizing the need for training. For guests,
it should provide options like online booking, mobile check-in, and seamless payment
options.
4. Integrated Financial Management and Billing: The system should generate
accurate bills for guests based on their stay and services used. It should also handle
payments via multiple channels, such as credit cards, online payments, or cash, and
ensure the hotel’s financial records are up-to-date.
5. Efficient Inventory Management: With real-time inventory tracking, the system can
automatically notify the hotel when stocks are running low, enabling timely
reordering. This minimizes waste and ensures resources are always available for guest
needs.
 6. Staff Scheduling and Communication: An HMS should enable better coordination
between staff members across departments. The system can help schedule shifts,
assign tasks (like cleaning or room service), and keep staff informed about the needs
of each guest.
7. Data Analytics and Reporting: The system should provide valuable insights for
hotel management, such as occupancy rates, guest preferences, revenue data, and
operational bottlenecks. This data can be used to improve service quality, optimize
pricing strategies, and identify areas for cost-saving.

Expected Benefits of the Hotel Management System:

1. Improved Efficiency: By automating repetitive tasks and improving communication

between staff, the system helps the hotel run more smoothly.
2. Enhanced Guest Experience: Faster check-ins/outs, accurate reservations, and
smooth billing processes lead to a better overall experience for guests.
3. Cost Reduction: Real-time tracking of resources and improved staff coordination
helps reduce waste and operational inefficiencies.
4. Revenue Growth: Better room management, pricing strategies, and guest service can
lead to higher occupancy rates and repeat business.
2.ANALYZE REQUIREMENT FOR A HOTEL MANAGEMENT
SYSTEM AND DEVELOP SOFTWARE REQUIREMENT
SPECIFICATION SHEET(SRS)FOR HOTEL MANAGEMENT
SYSTEM.

Software Requirement Specification (SRS) for Hotel Management System

The Software Requirements Specification (SRS) for a Hotel Management System (HMS)
provides a detailed description of the functional and non-functional requirements for the
system. This document is crucial for the development, testing, and implementation phases of
the software.

1. Introduction
1.1 Purpose

The purpose of this document is to define the software requirements for the development of a
Hotel Management System (HMS). The system will streamline the hotel’s operations by
managing reservations, check-in/check-out processes, billing, room assignments, guest
requests, and staff coordination.

1.2 Scope

The HMS will automate key operations for hotels, such as managing guest reservations,
assigning rooms, processing check-ins/outs, billing, and managing inventory and staff
coordination. It will provide a central system accessible by hotel management, front desk
staff, housekeeping, maintenance, and other stakeholders.

1.3 Definitions, Acronyms, and Abbreviations

• HMS: Hotel Management System

• Admin: Hotel Administrator
• Front Desk: Staff responsible for guest services and room assignments
• Guest: Hotel customers who book and stay at the hotel
• Check-In: Process where guests register their stay upon arrival
• Check-Out: Process of guest departure and bill settlement
• API: Application Programming Interface (for integrating third-party services)

1.4 References

• Industry best practices for hotel management systems

• Web-based technologies (e.g., HTML5, CSS3, JavaScript)
 • Database Management System (DBMS) guidelines

2. Overall Description
2.1 Product Perspective

The Hotel Management System will be a web-based application accessible by hotel staff
through web browsers. The system will consist of several modules, each with a user interface
tailored to different roles (e.g., admin, front desk, housekeeping). The system will be built on
modern technologies, with an emphasis on scalability, security, and real-time data
synchronization.

2.2 Product Features

1. User Roles and Authentication:

o Admin login and access control.
o Role-based access for front desk, housekeeping, and other staff.
o User profile management.
2. Reservation Management:
o Real-time reservation system to handle booking requests.
o Room availability check and booking confirmation.
o Cancellation and modification of reservations.
3. Check-In/Check-Out:
o Automated guest check-in process (ID verification, room allocation).
o Quick check-out process with invoice generation and payment handling.
4. Billing and Payments:
o Generate invoices for guests based on room rates and services used.
o Support multiple payment methods (credit card, online payment, etc.).
o Track payments and generate receipts.
5. Room Management:
o Room status tracking (available, booked, under maintenance).
o Real-time room assignment.
o Room service requests and complaints tracking.
6. Inventory Management:
o Real-time tracking of supplies, amenities, and inventory.
o Alerts for low stock levels and reordering.
o Automatic inventory updates after usage.
7. Staff Management:
o Employee scheduling and task assignments (housekeeping, room service, etc.).
o Staff attendance and shift management.
8. Reporting and Analytics:
o Reports on room occupancy, revenue, guest preferences, etc.
o Performance tracking for staff and services.
o Forecasting and budget analysis.

2.3 User Characteristics

• Admin: Has full access to system configurations, user management, and reports.
 • Front Desk: Manages reservations, check-ins/outs, room assignments, and guest queries.
• Housekeeping: Handles room cleaning schedules and maintains room inventory.
• Maintenance: Monitors and maintains the physical infrastructure of the hotel.
• Guest: Access to booking, checking in/out, and viewing invoice details.

2.4 Constraints

• The system must be built to handle concurrent user access.

• The system should be compatible with common web browsers (Chrome, Firefox, Edge).
• It must ensure data security for sensitive customer information (payment details, personal
data).
• The system should have a backup feature for data integrity and disaster recovery.

3. Functional Requirements
3.1 Reservation Management

• Requirement 1: The system shall allow guests to make reservations via the front desk or
online platform.
• Requirement 2: The system shall allow users to view available rooms based on the date and
guest preferences.
• Requirement 3: The system shall allow users to cancel or modify existing bookings.
• Requirement 4: The system shall send automatic email/SMS confirmations upon successful
reservation.

3.2 Check-In/Check-Out

• Requirement 1: The system shall allow front desk staff to check in guests by verifying their
identity.
• Requirement 2: The system shall automatically assign rooms based on availability.
• Requirement 3: The system shall process guest check-out and generate a bill for their stay,
including room charges and any additional services.

3.3 Billing and Payments

• Requirement 1: The system shall generate invoices based on room rates and services
utilized by guests.
• Requirement 2: The system shall allow for multiple payment methods (credit card, cash,
mobile payment, etc.).
• Requirement 3: The system shall store payment history and generate receipts for guests.

3.4 Inventory Management

• Requirement 1: The system shall track inventory levels for room supplies, food, and other
consumables.
• Requirement 2: The system shall provide real-time inventory updates when items are used
(e.g., room service).
• Requirement 3: The system shall notify staff when stock levels are low.
3.5 Staff Management

• Requirement 1: The system shall allow staff scheduling based on availability and workload.
• Requirement 2: The system shall track staff attendance and working hours.
• Requirement 3: The system shall assign tasks to housekeeping and maintenance staff.

3.6 Reporting and Analytics

• Requirement 1: The system shall generate occupancy reports (daily, weekly, monthly).
• Requirement 2: The system shall generate financial reports including revenue, payments,
and expenses.
• Requirement 3: The system shall provide analytics on guest preferences and trends.

4. Non-Functional Requirements
4.1 Performance Requirements

• The system must support up to 500 concurrent users without significant performance
degradation.
• The system should respond to user actions within 2 seconds.

4.2 Security Requirements

• The system must encrypt sensitive data such as guest payment information.
• The system must authenticate all users before granting access to the system.
• The system must have role-based access control to restrict access to specific data.

4.3 Usability Requirements

• The system must have an intuitive and easy-to-use interface for all types of users (staff and
guests).
• The system must be responsive and work across multiple devices (PCs, tablets, mobile
phones).

4.4 Reliability

• The system must be available 99.9% of the time, excluding planned maintenance.
• Data backups should be performed daily to prevent loss of data.

4.5 Scalability

• The system should support the addition of new hotels or branches without requiring
significant redesign.

4.6 Maintainability

• The system must be easily maintainable with clear documentation for developers.
• System updates and bug fixes must be easy to implement without downtime.
5. System Models and Diagrams
5.1 Use Case Diagram

• Depicts how different users (admin, front desk staff, housekeeping) interact with the system.

5.2 Data Flow Diagram (DFD)

• Describes the flow of data within the system, from guest reservations to billing and
reporting.

5.3 Entity-Relationship Diagram (ERD)

• Shows the relationships between different entities, such as guests, rooms, payments, and
staff.

6. Appendices
6.1 Glossary

Definitions of key terms used in the document (e.g., Reservation, Invoice, Admin).

6.2 References

External references or standards used during the development of this SRS.

3.TO CREATE THE FUNCTION ORIENTED DIAGRAM. DATA
FLOW DIAGRAM(DFD)FOR HOTEL MANAGEMENT SYSTEM.

Data Flow Diagram (DFD) for a Hotel Management System (HMS), which illustrates the
flow of data within the system, broken into different levels of abstraction.

Level 0: Context Diagram

At the highest level, the Hotel Management System is depicted as a single process
interacting with external entities.

Entities:

1. Guest: Makes reservations, checks in and out, and pays bills.

2. Hotel Staff: Interacts with the system to manage reservations, check-ins/outs, and
payments.
3. Payment System: Handles transactions like credit card payments or other financial systems.
4. Supplier: Provides inventory and supplies for hotel rooms, such as cleaning products, food,
etc.

Data Flows:

• Guest → HMS: Sends booking requests, payment information, and personal details.
• HMS → Guest: Sends reservation confirmations, invoices, and room assignments.
• Hotel Staff → HMS: Sends guest information, room availability requests, and billing details.
• HMS → Hotel Staff: Provides room assignments, check-in/check-out data, and reports.
• Payment System → HMS: Sends payment confirmation and updates billing data.
• HMS → Supplier: Sends inventory requirements and supply orders.
• Supplier → HMS: Sends inventory data, product details, and updates.

Level 1: Decomposed Diagram

At this level, the Hotel Management System is broken down into major sub-systems or
modules, each handling specific tasks.

Main Processes:

1. Reservation Management
o Handles booking requests, checks room availability, and sends confirmation or
denial.
o Data Flows:
▪ Guest → Reservation System: Sends booking request.
▪ Reservation System → Guest: Sends booking confirmation.
▪ Reservation System → Room Inventory: Checks room availability.
2. Check-In/Check-Out
 o Manages guest check-in, check-out, and updates room status.
o Data Flows:
▪ Guest → Check-In/Check-Out System: Provides ID, booking details.
▪ Check-In/Check-Out → Guest: Room assignment and check-in details.
▪ Check-In/Check-Out → Room Inventory: Updates room status.
▪ Check-In/Check-Out → Billing System: Updates guest’s final bill.
3. Billing and Payments
o Manages the guest's bill, including room charges and additional services, and
processes payments.
o Data Flows:
▪ Check-In/Check-Out → Billing System: Sends guest check-in details.
▪ Billing System → Payment System: Sends payment request.
▪ Payment System → Billing System: Sends payment confirmation.
▪ Billing System → Guest: Sends final invoice and payment receipt.
4. Room Management
o Tracks room status (e.g., available, occupied, under maintenance).
o Data Flows:
▪ Reservation Management → Room Management: Updates room status.
▪ Room Management → Housekeeping: Sends room cleaning requests.
▪ Room Management → Guest: Provides room details upon check-in.
5. Inventory Management
o Manages inventory for supplies such as linens, toiletries, food, and beverages.
o Data Flows:
▪ Supplier → Inventory System: Sends supply information and stock levels.
▪ Inventory System → Housekeeping: Sends stock data for room supplies.
▪ Inventory System → HMS: Notifies low inventory.
6. Staff Coordination
o Manages staff schedules, task assignments, and performance tracking.
o Data Flows:
▪ Hotel Staff → Staff Coordination System: Inputs work shifts and task
requests.
▪ Staff Coordination System → Hotel Staff: Sends staff assignments.

Level 2: Detailed Process Breakdown (Example)

This level would further decompose processes like Reservation Management into more
granular processes such as:

1. Booking Validation: Verifies if rooms are available.

2. Booking Confirmation: Finalizes the booking and notifies the guest.
3. Cancellation Handling: Manages booking cancellations and refunds.

DFD Symbols:

• Circle or Rounded Rectangle: Represents processes that manipulate data.

• Arrow: Represents data flow between processes, external entities, and data stores.
• Rectangle: Represents external entities interacting with the system.
• Open-ended Rectangle: Represents data stores where information is held.
A Data Flow Diagram helps clarify how information is processed, transformed, and moved
within the system, ensuring that all user interactions and data requirements are understood
and met.

3.To perform the user’s view analysis for the hotel

management system : Use case diagram
Creating a Use Case Diagram for the Hotel Management System is a great way to capture
the interactions between the system and its users (actors). The use case diagram shows the
different system functions from the perspective of the users and how they interact with them.

Here’s an outline of the actors and use cases for a typical Hotel Management System:

1. Actors

• Customer: A guest who interacts with the system to book rooms, view room details,
check in/out, etc.
• Hotel Staff: Personnel who manage bookings, check-ins, check-outs, room
availability, and more.
 • Admin: The system administrator who manages system settings, user accounts, room
configurations, and overall system settings.
• Housekeeping: Staff responsible for maintaining room cleanliness and updating room
status in the system.

2. Use Cases

• Customer:
o Search for Available Rooms: The customer can search for rooms based on
date, type, and other preferences.
o Book a Room: The customer can make a reservation.
o Check-in: The customer can check-in to the hotel when they arrive.
o Check-out: The customer can check out at the end of their stay.
o View Room Details: The customer can see details about room types, prices,
and facilities.
o Make Payments: The customer can pay for their booking via the system.
• Hotel Staff:
o Manage Bookings: Staff can view, modify, or cancel customer bookings.
o Check-in Customers: Hotel staff check in customers upon arrival.
o Check-out Customers: Hotel staff check out customers and generate bills.
o Assign Rooms: Hotel staff assign rooms to customers during check-in.
• Admin:
o Manage Rooms: Admin can add, update, or remove room details such as
prices, availability, and features.
o Manage Users: Admin can create and manage user accounts (staff, customers,
etc.).
o System Settings: Admin manages the settings for the entire hotel management
system, including policies, payment methods, etc.
• Housekeeping:
o Update Room Status: Housekeeping updates the status of rooms (clean, dirty,
in-progress).
o Update Maintenance Requests: Housekeeping or staff can log maintenance
issues related to rooms (e.g., repairs needed).

3. Use Case Diagram Example

Below is a textual description of the use case diagram:

[Customer] ----> (Search for Available Rooms)

[Customer] ----> (Book a Room)
[Customer] ----> (Check-in)
[Customer] ----> (Check-out)
[Customer] ----> (View Room Details)
[Customer] ----> (Make Payments)

[Hotel Staff] ----> (Manage Bookings)

[Hotel Staff] ----> (Check-in Customers)
[Hotel Staff] ----> (Check-out Customers)
[Hotel Staff] ----> (Assign Rooms)

[Admin] ----> (Manage Rooms)

[Admin] ----> (Manage Users)
[Admin] ----> (System Settings)

[Housekeeping] ----> (Update Room Status)

[Housekeeping] ----> (Update Maintenance Requests)

4. General Flow:

• Customer's Flow: A customer can search for rooms, book a room, check in, and
check out, all of which are key processes that interact with the system.
• Staff's Flow: Hotel staff manages bookings, check-ins, and check-outs for customers.
• Admin's Flow: Admin has the highest level of control, managing room
configurations, user management, and system settings.
• Housekeeping's Flow: Housekeeping focuses on room maintenance and cleanliness,
ensuring accurate room status updates.
5.TO DRAW THE STRUCTURAL VIEW DIAGRAM
FOR THE HOTEL MANAGEMENT SYSTEM: CLASS
DIAGRAM.
To create a Class Diagram for a Hotel Management System, we'll model the system's static
structure by identifying the classes, their attributes, methods (operations), and the
relationships between them. The class diagram will show how different components of the
hotel system interact with one another.

the Class Diagram for a Hotel Management System:

1. Identify Key Classes

Here are some essential classes for the system:

• Hotel
• Room
• Booking
• Customer
• Staff
• Admin
• Payment
• Housekeeping
• Invoice
• Facility (e.g., WiFi, Gym, Swimming Pool, etc.)

2. Define Attributes and Methods for Each Class

1. Hotel

• Attributes:
o hotelName: String
o location: String
o rooms: List
o staff: List
o bookings: List
• Methods:
o addRoom(Room room)
o removeRoom(Room room)
o checkAvailability(Date startDate, Date endDate): boolean

2. Room

• Attributes:
o roomNumber: String
o roomType: String (e.g., Single, Double, Suite)
o price: double
o status: String (e.g., Available, Occupied, Under Maintenance)
 o facilities: List
• Methods:
o updateStatus(String status)
o addFacility(Facility facility)

3. Booking

• Attributes:
o bookingID: String
o customer: Customer
o room: Room
o startDate: Date
o endDate: Date
o totalAmount: double
o paymentStatus: String (e.g., Pending, Paid)
• Methods:
o generateInvoice(): Invoice
o updateBookingStatus(String status)

4. Customer

• Attributes:
o customerID: String
o name: String
o email: String
o phoneNumber: String
o address: String
• Methods:
o makeBooking(Booking booking)
o cancelBooking(Booking booking)

5. Staff

• Attributes:
o staffID: String
o name: String
o role: String (e.g., Receptionist, Housekeeper, Manager)
• Methods:
o manageBooking(Booking booking)
o assignRoom(Room room, Customer customer)

6. Admin

• Attributes:
o adminID: String
o name: String
• Methods:
o addRoom(Room room)
o removeRoom(Room room)
o manageUserAccount(User user)
7. Payment

• Attributes:
o paymentID: String
o booking: Booking
o paymentDate: Date
o amount: double
o paymentMethod: String (e.g., Credit Card, Cash)
• Methods:
o processPayment()
o refundPayment()

8. Housekeeping

• Attributes:
o staffID: String
o name: String
o roomAssigned: Room
• Methods:
o updateRoomStatus(Room room, String status)
o reportMaintenance(Room room)

9. Invoice

• Attributes:
o invoiceID: String
o booking: Booking
o amountDue: double
o dateIssued: Date
• Methods:
o generateInvoice()
o updateInvoiceStatus(String status)

10. Facility

• Attributes:
o facilityID: String
o facilityName: String (e.g., WiFi, Swimming Pool)
o facilityType: String (e.g., Free, Paid)
• Methods:
o assignFacility(Room room)
o updateFacilityInfo()

3. Relationships between Classes

• Hotel "has" many Rooms: Hotel → Room (1 to many)

• Hotel "has" many Bookings: Hotel → Booking (1 to many)
 • Customer "makes" many Bookings: Customer → Booking (1 to many)
• Booking "is for" a Room: Booking → Room (many to 1)
• Booking "is made by" a Customer: Booking → Customer (many to 1)
• Booking "has" one Payment: Booking → Payment (1 to 1)
• Room "has" many Facilities: Room → Facility (many to many)
• Staff "manages" many Bookings: Staff → Booking (1 to many)
• Housekeeping "updates" Room status: Housekeeping → Room (many to 1)
• Admin "manages" many Users and Rooms: Admin → Staff, Admin → Room (1 to many)

4. Class Diagram Representation (Textual)

Below is a textual representation of the relationships between the classes:

+-------------------+ +------------------+
| Hotel |------| Room |
|-------------------| |------------------|
| - hotelName | | - roomNumber |
| - location | | - roomType |
| - rooms | | - price |
| - staff | | - status |
| - bookings | | - facilities |
+-------------------+ +------------------+
| |
| |
| |
| |
v v
+-------------------+ +--------------------+
| Booking |------| Customer |
|-------------------| |--------------------|
| - bookingID | | - customerID |
| - customer | | - name |
| - room | | - email |
| - startDate | | - phoneNumber |
| - endDate | | - address |
| - totalAmount | +--------------------+
| - paymentStatus | |
+-------------------+ |
| |
v v
+------------------+ +-------------------+
| Payment |------| Admin |
|------------------| |-------------------|
| - paymentID | | - adminID |
| - amount | | - name |
| - method | +-------------------+
+------------------+
|
v
+-------------------+
| Invoice |
|-------------------|
| - invoiceID |
| - amountDue |
| - dateIssued |
+-------------------+
|
v
+------------------+
| Housekeeping |
|------------------|
| - staffID |
| - name |
| - roomAssigned |
+------------------+
|
v
+------------------+
| Facility |
|------------------|
| - facilityID |
| - facilityName |
| - facilityType |
+------------------+

5. Key Relationships:

• Hotel → Room: A hotel has multiple rooms.

• Booking → Room: A booking is associated with one room.
• Customer → Booking: A customer can have multiple bookings.
• Payment → Booking: A payment corresponds to one booking.

This class diagram represents the main classes and their relationships in a hotel management
system. It serves as the structural backbone of the system and can be used to guide the
development process.
6.TO DRAW THE BEHAVIORAL VIEW DIAGRAM :
ACTIVITY DIAGRAM FOR HOTEL MANAGEMENT
SYSTEM.
To create an Activity Diagram for a Hotel Management System, we need to visualize the
dynamic flow of activities or processes that the system supports, focusing on the various
workflows or scenarios.

Here’s a breakdown of the main activities involved in key workflows for the Hotel
Management System, such as the Room Booking Process and Customer Check-in/Check-
out Process.

1. Key Activities:

• Room Booking Process:

o Searching for rooms
o Selecting a room
o Making a booking
o Payment processing
o Confirmation of booking
• Customer Check-in/Check-out Process:
o Customer arrival
o Room assignment
o Check-in
o Customer departure
o Generating invoice
o Payment processing

2. Activity Diagram for the Room Booking Process

The Room Booking process describes the activities a customer might engage in when
booking a room in a hotel.

Flow of Activities:

1. Start
2. Search for Rooms: The customer searches for available rooms based on their preferences.
3. Select Room: Customer selects a room from the available options.
4. Make Booking: The customer proceeds with the booking by entering details (dates,
customer info, etc.).
5. Process Payment: The system processes the payment through an available payment
method.
6. Confirm Booking: Once the payment is confirmed, a booking confirmation is sent to the
customer.
7. End
Activity Diagram for Room Booking:
+------------------+
| Start |
+------------------+
|
v
+-----------------------+
| Search for Available |
| Rooms |
+-----------------------+
|
v
+-----------------------+
| Select Room |
+-----------------------+
|
v
+-----------------------+
| Make Booking |
+-----------------------+
|
v
+-----------------------+
| Process Payment |
+-----------------------+
|
v
+-----------------------+
| Confirm Booking |
+-----------------------+
|
v
+------------------+
| End |
+------------------+

3. Activity Diagram for the Customer Check-in/Check-out Process

This workflow involves the customer arriving at the hotel, checking in, staying, and then
checking out.

Flow of Activities:

1. Start
2. Customer Arrival: The customer arrives at the hotel.
3. Verify Booking: The hotel staff checks the booking details.
4. Assign Room: The staff assigns the customer a room.
5. Check-in: The customer checks in to the room.
6. Stay Period: The customer stays in the room.
7. Check-out: At the end of their stay, the customer checks out.
8. Generate Invoice: An invoice is generated for the customer.
9. Process Payment: The customer makes payment for the stay.
10. End
Activity Diagram for Check-in/Check-out:
+------------------+
| Start |
+------------------+
|
v
+-----------------------+
| Customer Arrival |
+-----------------------+
|
v
+-----------------------+
| Verify Booking |
+-----------------------+
|
v
+-----------------------+
| Assign Room |
+-----------------------+
|
v
+-----------------------+
| Check-in |
+-----------------------+
|
v
+-----------------------+
| Stay Period |
+-----------------------+
|
v
+-----------------------+
| Check-out |
+-----------------------+
|
v
+-----------------------+
| Generate Invoice |
+-----------------------+
|
v
+-----------------------+
| Process Payment |
+-----------------------+
|
v
+------------------+
| End |
+------------------+

4. Detailed Description of Key Steps:

• Room Booking Process:

o The Search for Rooms activity starts when a customer logs into the system and
searches for available rooms based on their preferences.
o Once the Room is selected, the Booking process begins where customer details are
captured and entered into the system.
 o After the booking is completed, the Payment process starts, and once the payment
is confirmed, the booking is confirmed, and the customer receives a notification.
• Check-in/Check-out Process:
o When a customer arrives, the hotel staff verifies the booking. If the booking exists,
the room is assigned, and the customer is allowed to check in.
o During the stay period, the customer may access hotel services, but at the end of the
stay, they proceed to check out. The invoice is generated, and the customer pays for
their stay.

5. Main Components of an Activity Diagram:

• Initial Node (Start): Represents the starting point of the process.

• Activities (Rounded Rectangles): Represent tasks or steps in the process (e.g., "Search for
Rooms," "Process Payment").
• Decision Nodes (Diamonds): Represent decision points where different paths might be
taken (e.g., verifying booking status).
• Final Node (End): Represents the end of the process.
• Control Flows (Arrows): Indicate the direction of the process flow.
7.TO PERFORM THE BEHAVIOURAL VIEW DIAGRAM FOR THE
HOTEL MANAGEMENT SYSTEM : SEQUENCE DIAGRAM.
A Sequence Diagram represents how objects or components in the system interact with each
other over time. It shows the sequence of events (messages or method calls) that occur
between objects to carry out a specific process or scenario. For the Hotel Management
System, we can create Sequence Diagrams for key scenarios like Room Booking and
Customer Check-in/Check-out.

1. Sequence Diagram for Room Booking Process

In this scenario, the Customer interacts with the Hotel System to search for available rooms,
make a booking, and process the payment.

Participants (Objects):

• Customer
• Hotel System
• Room
• Payment System
• Booking System

Flow of Events:

1. Customer initiates the Search for Rooms with the Hotel System.
2. Hotel System queries the Room database to check availability.
3. The Hotel System returns available rooms to the Customer.
4. Customer selects a room and provides booking details.
5. Hotel System creates a Booking entry in the Booking System.
6. Hotel System sends booking details to the Payment System.
7. Customer enters payment information.
8. Payment System processes the payment.
9. Payment System confirms the payment to the Hotel System.
10. Hotel System sends a confirmation to the Customer.

Sequence Diagram for Room Booking:

+-------------------+ +-------------------+ +-------------------+
+-------------------+ +-------------------+
| Customer | | Hotel System | | Room |
| Payment System | | Booking System |
+-------------------+ +-------------------+ +-------------------+
+-------------------+ +-------------------+
| | |
| |
| 1. Search Rooms | |
| |
|-----------------------> | |
| |
| | 2. Query Available |
| |
 | | Rooms |
| |
| |-----------------------> |
| |
| | |
| |
| | 3. Return Available |
| |
| | Rooms |
| |
| | <-----------------------|
| |
| 4. Select Room | |
| |
|-----------------------> | |
| |
| | 5. Create Booking |
| |
| |-----------------------> |
| |
| | |
| |
| | 6. Send Booking Details |
| |
| |-----------------------> |
| |
| | |
| |
| 7. Enter Payment Info | |
| |
|-----------------------> | |
| |
| | 8. Process Payment |
| |
| |-----------------------> |
| |
| | |
| 9. Payment Confirmation |
| | |
| <-----------------------|
| | 10. Confirm Booking |
| |
| | <-----------------------|
| |
| 11. Receive Confirmation| |
| |
| <-----------------------| |
| |
| | |
| |
+------------------------+ +---------------
---------+ +-------------------+

2. Sequence Diagram for Customer Check-in/Check-out Process

This diagram depicts the flow of actions involved when a Customer checks in and checks
out of the hotel.
Participants (Objects):

• Customer
• Hotel Reception System
• Room
• Booking System
• Invoice System
• Payment System

Flow of Events:

1. Customer arrives at the hotel and provides their Booking Details.

2. Hotel Reception System verifies the booking in the Booking System.
3. Booking System returns the booking status to the Hotel Reception System.
4. Hotel Reception System assigns a Room to the Customer.
5. Customer proceeds with check-in.
6. During the stay, the Customer enjoys the services.
7. Upon departure, the Customer requests to check out.
8. Hotel Reception System generates an Invoice.
9. Customer proceeds with Payment through the Payment System.
10. Payment System processes the payment and confirms the transaction.
11. Hotel Reception System confirms check-out to the Customer.

Sequence Diagram for Check-in/Check-out:

+-------------------+ +-------------------+ +-------------------+
+-------------------+ +-------------------+ +-------------------+
| Customer | | Hotel Reception | | Room |
| Booking System | | Invoice System | | Payment System |
+-------------------+ +-------------------+ +-------------------+
+-------------------+ +-------------------+ +-------------------+
| | |
| | |
| 1. Provide Booking | |
| | |
| Details |-----------------------> |
| | |
|-----------------------> | 2. Verify Booking |
| | |
| |-----------------------> |
| | |
| | |
| 3. Return Booking Status| |
| | <-----------------------|
| <-----------------------| |
| 4. Assign Room | | 5. Assign Room
| | |
|-----------------------> |-----------------------> |--------------
--------->| | |
| | |
| | |
| 6. Check-in | |
| | |
|-----------------------> | |
| | |
 | | |
| | |
| | |
| | |
| 7. Request Check-out | |
| | |
|-----------------------> | |
| | |
| | 8. Generate Invoice |
| | |
| |-----------------------> |
| | |
| | |
| 9. Process Payment | |
| | |
|-----------------------> | |
| | |
| | 10. Payment Confirmation |
| | |
| | <-----------------------|
| | 11. Confirm Check-out |
| | |
| <-----------------------|----------------------- |
| | |
| | |
| | |
+------------------------+ +---------------
---------+------------------------+--------------------+

3. Key Concepts in Sequence Diagrams:

• Participants (Objects): Represent the entities involved in the interaction (e.g., Customer,
Room, Booking System).
• Messages (Arrows): Represent the interactions between the participants. They can
represent method calls, data exchanges, or events.
• Activation Bars: Represent the period during which a participant is active and processing a
task.
• Return Messages: Indicated by dashed arrows, these show the result or return value after
the execution of a message.
8.DRAW THE COMPONENT DIAGRAM FOR HOTEL
MANAGEMENT SYSTEM.
A Component Diagram is used to represent the components or modules of a system and
their relationships. In a Hotel Management System, the components might include various
parts like the Booking System, Payment System, User Interface, Database, and more. This
diagram helps in understanding how different components work together to achieve the
overall functionality of the system.

Here’s a breakdown of the key components for the Hotel Management System:

1. Components in the Hotel Management System

1. User Interface (UI):

o The interface through which customers and staff interact with the system.
o Examples: Booking page, Customer Dashboard, Admin Dashboard, etc.
2. Booking System:
o Manages all booking-related functionalities (e.g., room availability,
reservations, booking details).
o Example: Checking room availability, booking a room, canceling bookings,
etc.
3. Payment System:
o Handles the processing of payments.
o Example: Payment gateway, payment processing, payment confirmation.
4. Room Management:
o Manages room information, availability, pricing, and status (e.g., available,
occupied, maintenance).
o Example: Updating room status, assigning rooms to customers.
5. Customer Management:
o Manages customer data like customer profiles, history, and preferences.
o Example: Customer registration, login, profile management.
6. Invoice Generation:
o Generates invoices for customers based on their booking and stay.
o Example: Generating bills, checking out, payment receipt.
7. Admin System:
o For administrators to manage the hotel system (e.g., adding rooms, managing
bookings, checking reports).
o Example: Managing rooms, managing bookings, user account management.
8. Notification System:
o Sends out notifications to customers and staff (e.g., booking confirmations,
payment receipts, reminders).
o Example: Sending email/SMS notifications for booking confirmation.
9. Database:
o The underlying database that stores all data related to bookings, customers,
rooms, payments, etc.
o Example: SQL database, NoSQL database for storing customer and room data.
2. Component Diagram for Hotel Management System

Below is a textual representation of how components are related:

+-------------------+ +------------------------+ +-------

-------------+
| User Interface | <------> | Booking System | <-------> |
Room Management |
|-------------------| |------------------------| |-------
-------------|
| - Booking Page | | - Check Availability | | -
Manage Rooms |
| - Dashboard | | - Make Reservations | | - Room
Status |
| - Notifications | | - Cancel Reservations | | -
Assign Rooms |
+-------------------+ +------------------------+ +-------
-------------+
| |
|
v v
v
+-------------------+ +-------------------+ +-----------
---------+
| Admin System | <------> | Payment System | <-------> | Customer
Management|
|-------------------| |-------------------| |-----------
---------|
| - Manage Rooms | | - Process Payment | | - Manage
Customers |
| - Manage Users | | - Payment Gateway | | - Customer
Profile |
| - Reports | | - Payment Status | | -
Preferences |
+-------------------+ +-------------------+ +-----------
---------+
| |
|
v v
v
+-------------------+ +-------------------+ +---
-----------------+
| Invoice Generation | <------> | Database | <-------> |
Notification System|
|-------------------| |-------------------| |---
-----------------|
| - Generate Invoice | | - Store Booking | | -
Send Notifications|
| - Generate Receipt | | - Store Customer | | -
Email/SMS Alerts |
+-------------------+ | - Store Payment | +---
-----------------+
| - Store Rooms |
| - Store Invoices |
+-------------------+
3. Explanation of the Component Diagram

• User Interface (UI):

o Allows interaction between customers and the system. It communicates with
the Booking System, Payment System, and Notification System. For
example, customers interact with the booking page, and after booking, they
receive a confirmation via the notification system.
• Booking System:
o Manages the entire booking process. It checks room availability, manages
reservations, and integrates with the Payment System for processing
payments and the Room Management System to update room statuses.
• Payment System:
o Handles payment-related functionality. It is responsible for processing
payments and interacting with the Booking System to confirm payment and
update booking status. The Invoice Generation component then creates an
invoice for the customer.
• Room Management:
o This component deals with the availability and status of rooms. It is linked to
the Booking System, which updates the status of rooms when bookings are
made or canceled.
• Customer Management:
o Stores customer data and allows customers to manage their profiles and
preferences. It integrates with the Booking System to fetch booking history
and other customer-specific details.
• Admin System:
o Provides admin users with the ability to manage the entire hotel system, such
as adding rooms, managing bookings, and overseeing other operations.
• Invoice Generation:
o This component generates invoices for customers based on their booking,
room type, services used, etc.
• Database:
o Stores all the system's data, including information about rooms, customers,
bookings, payments, and invoices. It communicates with all other components
to store and retrieve data as needed.
• Notification System:
o Sends notifications to customers and staff. For instance, after a booking is
made, a confirmation is sent to the customer via email/SMS.
9.DRAW THE DEPLOYMENT DIAGRAM HOTEL
MANAGEMENT SYSTEM.
A Deployment Diagram is used to represent the physical deployment of software
components on hardware nodes in a system. It shows how software components (like the
Hotel Management System) are distributed across various hardware devices and how they
communicate with each other.

Deployment Diagram for Hotel Management System

In a Hotel Management System, the deployment diagram could represent the interaction
between various hardware nodes (servers, user devices, databases) and the software
components (booking system, payment system, etc.).

Key Hardware Nodes:

1. Web Server:
o Hosts the Hotel Management System (web application).
o Serves the User Interface (UI) for customers and admins.
2. Application Server:
o Runs the core business logic and handles the Booking System, Payment
System, and Notification System.
3. Database Server:
o Stores the Hotel Management System’s data, including customer profiles,
booking records, payment details, and room information.
4. Client Devices:
o Customer devices (e.g., mobile, laptop, or tablet) that interact with the system
via the User Interface.
o Admin devices to manage bookings, rooms, and users.

Deployment Diagram
+-------------------+ +--------------------+ +-------------------
--+
| Client Devices | | Web Server | | Database Server
|
| (Customer/Laptop)| | (Hotel Website) | | (SQL Database)
|
+-------------------+ +--------------------+ +-------------------
--+
| | |
| | |
v v v
+------------------+ +--------------------+ +------------------
--+
| User Interface | <--> | Application | <--> | Database
|
| (Booking Page) | | Server | | (Bookings,
|
| (Admin Page) | | (Booking, Payment | | Customers,
Rooms)|
 +------------------+ | Invoice, etc.) | +------------------
--+
+--------------------+

Explanation of the Deployment Diagram:

1. Client Devices (Customer/Admin):

o Customers and hotel admins interact with the Hotel Management System
through web browsers or mobile apps. These devices use the User Interface
(UI) to perform actions like booking a room or managing bookings.
2. Web Server:
o The Web Server hosts the application, providing the User Interface (UI) for
both customers and administrators. This server handles HTTP requests and
delivers responses via the browser or mobile device.
3. Application Server:
o The Application Server contains the business logic of the system, such as
managing bookings, payments, and generating invoices. It interacts with the
Web Server and the Database Server to process requests.
o Components like Booking System, Payment System, and Invoice
Generation reside here.
4. Database Server:
o The Database Server holds all the data for the Hotel Management System,
such as customer information, booking details, payment transactions, and
room availability.
o It is connected to the Application Server to retrieve and store necessary data
for processing requests.
10.DRAW THE ER DIAGRAM FOR HOTEL
MANAGEMENT SYSTEM.
An Entity-Relationship (ER) Diagram represents the data model of the system, showing the
entities (objects) in the system and their relationships. For a Hotel Management System, the
ER diagram would include key entities such as Customer, Booking, Room, Payment, and
Invoice, along with the relationships between them.

Entities and Their Attributes:

1. Customer:
o Attributes: CustomerID, Name, Email, Phone, Address, DOB
2. Room:
o Attributes: RoomID, RoomType, Price, RoomStatus, Floor
3. Booking:
o Attributes: BookingID, CustomerID (foreign key), RoomID (foreign key),
BookingDate, CheckInDate, CheckOutDate
4. Payment:
o Attributes: PaymentID, BookingID (foreign key), Amount, PaymentDate,
PaymentMethod, PaymentStatus
5. Invoice:
o Attributes: InvoiceID, BookingID (foreign key), TotalAmount, InvoiceDate
ER Diagram for Hotel Management System

Below is the textual representation of the ER Diagram for the Hotel Management System:

+------------------+ +-------------------+ +------------------+

| Customer | | Booking | | Payment |
|------------------| |-------------------| |------------------|
| CustomerID (PK) | <----| BookingID (PK) |<---->| PaymentID (PK) |
| Name | | CustomerID (FK) | | BookingID (FK) |
| Email | | RoomID (FK) | | Amount |
| Phone | | BookingDate | | PaymentDate |
| Address | | CheckInDate | | PaymentMethod |
| DOB | | CheckOutDate | | PaymentStatus |
+------------------+ +-------------------+ +------------------+
| |
v v
+------------------+ +------------------+
| Room | | Invoice |
|------------------| |------------------|
| RoomID (PK) | | InvoiceID (PK) |
| RoomType | | BookingID (FK) |
| Price | | TotalAmount |
| RoomStatus | | InvoiceDate |
| Floor | +------------------+
+------------------+

Explanation of the ER Diagram:

1. Customer:
o The Customer entity holds information about hotel guests, such as name,
email, phone number, and address.
o The Customer entity has a one-to-many relationship with the Booking entity,
as one customer can make multiple bookings.
2. Booking:
o The Booking entity represents the reservation made by the customer. It
includes details like the BookingID, CustomerID (as a foreign key from the
Customer entity), the RoomID (foreign key from the Room entity), check-in
and check-out dates, and the booking date.
o The Booking entity has a many-to-one relationship with the Room entity
(since multiple bookings can involve the same room) and a many-to-one
relationship with Payment and Invoice.
3. Room:
o The Room entity contains information about the room itself, such as room
type, price, availability (status), and the floor it's located on.
o The Room entity has a one-to-many relationship with the Booking entity
because a room can be booked multiple times.
4. Payment:
o The Payment entity records the payment details, including the amount paid,
payment date, method (e.g., credit card, cash), and payment status.
o Each payment corresponds to a Booking, forming a many-to-one relationship
between Payment and Booking.
 5. Invoice:
o The Invoice entity represents the invoice generated for a booking. It includes
details like total amount and invoice date.
o Each Invoice is related to a specific Booking (one-to-one relationship).

Relationships:

• Customer ↔ Booking: One customer can make multiple bookings (1-to-many).

• Booking ↔ Room: A booking involves one room, but multiple bookings can involve
the same room (many-to-1).
• Booking ↔ Payment: Each booking can have multiple payments associated with it
(1-to-many).
• Booking ↔ Invoice: Each booking can have only one invoice (1-to-1).
• Room ↔ Booking: One room can be involved in many bookings (1-to-many).