Trinity Institute of Professional Studies Affiliated to

Guru Gobind Singh Indraprastha University

SECTOR 16-C, DWARAKA, NEW DELHI

SE LAB

BCA-

274

Practical File

Submitted By Submitted To

Name of Student:Dhruv Rai Dr. Nishika Mam

Enrollment Number:35324003021 Assistant Professor
Course: BCA Semester: 4th CS & IT
Shift: 1st Year: 2021-2024
 INDEX
S.NO. Program Date Signature

1) Select and write down the problem statement for a

real time system of relevance.

2) Analyze requirement for a system and develop

Software Requirement Specification
Sheet (SRS) for suggested system.

3) To create the function oriented diagram: Data

Flow Diagram (DFD)

4) To perform the user’s view analysis for the sug-

gested system: Use case diagram.

5) To draw the structural view diagram for the sys-

tem: Class diagram

6) To draw the behavioral view diagram: State-chart

diagram or Activity diagram

7) To perform the behavioral view diagram for the

suggested system: Sequence diagram

8) Draw the component diagram

9) Draw the Deployment diagram.

10) Perform Measurement of complexity with

Halstead Metrics for chosen system.
 PROGRAM NO. 1
AIM: Select and write down the problem statement for a real time system
of relevance.
Problem Statement:
The hotel management industry faces various challenges in real-time operations,
including efficient guest management, streamlined check-in and check-out processes, effective
inventory management, and optimized staff scheduling. These challenges can lead to delays,
inefficiencies, and poor customer experience.

Solution: Implementing a comprehensive hotel management system can address these

challenges and improve overall operations. Here are some key components of the solution:
1. Online Reservation System: Develop a user-friendly website or mobile app that allows
guests to make real-time reservations. Integration with a centralized database ensures accurate
availability information and reduces double bookings.
2. Streamlined Check-in and Check-out: Implement self-check-in kiosks or mobile
check-in options to expedite the process and minimize guest waiting time. This can be
supplemented with staff assistance for guests who prefer a personal touch.
3. Integrated Property Management System (PMS): Utilize a robust PMS software to
manage all aspects of hotel operations, including reservations, guest profiles, billing,
housekeeping, and maintenance. This centralizes information and enables efficient
coordination among different departments.
4. Inventory Management: Implement an inventory management system that tracks and
optimizes the usage of hotel resources, such as linens, toiletries, food, and beverages. Real-
time monitoring helps prevent stockouts and minimize waste.
5. Customer Relationship Management (CRM): Utilize CRM software to maintain a
comprehensive guest database, track preferences, and personalize services. This enables
targeted marketing campaigns, loyalty programs, and personalized experiences to enhance
guest satisfaction.
6. Online Reputation Management: Monitor and respond to guest reviews and feedback
on various platforms to address concerns promptly and maintain a positive online reputation.
This can lead to increased bookings and customer loyalty.
7. Staff Scheduling and Communication: Utilize employee scheduling software to
optimize staff shifts, considering factors like occupancy levels and workload. Implement
internal communication tools to facilitate real-time communication among staff members.
8. Data Analytics: Utilize data analytics tools to gain insights into guest preferences,
occupancy patterns, revenue trends, and operational efficiencies. This data-driven approach
helps in making informed decisions and identifying areas for improvement.
9. Security and Privacy: Implement robust security measures to protect guest information
and prevent unauthorized access. This includes secure payment processing, data encryption,
and compliance with relevant regulations.
10. Continuous Staff Training: Invest in regular training programs for staff members to
enhance their skills, knowledge, and customer service. Well-trained and motivated staff
contribute to a positive guest experience.
 By implementing these solutions, hotel management can streamline operations, enhance guest
satisfaction, and drive revenue growth. It is important to select appropriate software vendors
and ensure proper integration and training to maximize the effectiveness of the system.

PROGRAM NO. 2
AIM: Analyze requirement for a system and develop Software
Requirement Specification Sheet (SRS) for suggested system.
Analysis of Requirements:
Based on the problem statement, the following requirements have been identified for the
real-time system for Hotel Management System;
1. Online Reservation System
2. Streamlined Check-in and Check-out
3. Integrated Property Management System (PMS)
4. Inventory Management
5. Customer Relationship Management (CRM)
6. Online Reputation Management
7. Staff Scheduling and Communication

Software Requirement Specification (SRS) Sheet:

Introduction
1.1 Purpose
The purpose of this document is to provide a detailed description of the requirements for the
Hotel Management System. It outlines the functionalities and features that the system should
possess.
1.2 Scope
The Hotel Management System aims to automate and streamline various operations within a
hotel, including reservation management, guest check-in/check-out, room allocation, billing,
and reporting. The system will be used by hotel staff, managers, and guests to enhance
efficiency and improve overall customer experience.
1.3 Definitions, Acronyms, and Abbreviations

SRS: Software Requirement Specification

HMS: Hotel Management System

General Description
2.1 Product Perspective
The Hotel Management System will be a standalone software application designed to integrate
with existing hotel infrastructure, including the front desk, room management, and billing
systems.
2.2 Product Features
The key features of the Hotel Management System include:

Guest reservation management

Room availability and allocation
Check-in and check-out processes
Billing and invoicing
Room service management
Housekeeping management
Reporting and analytics
2.3 User Classes and Characteristics
The system will have the following user classes:
Front desk staff: Responsible for managing reservations, check-ins, check-outs, and guest
requests.
Managers: Responsible for monitoring and analyzing hotel operations, generating reports, and
making strategic decisions.
Guests: Users who interact with the system to make reservations, check-in, check-out, and
access various hotel services.
2.4 Operating Environment
The Hotel Management System will be developed as a web-based application and should be
compatible with modern web browsers. It will be hosted on a dedicated server within the hotel's
internal network.
Specific Requirements
3.1 Functional Requirements
3.1.1 Reservation Management
- The system should allow front desk staff to create, modify, and cancel reservations.
- Reservation details should include guest information, arrival and departure dates, room
preferences, and special requests.
- The system should provide real-time room availability information during the reservation
process.
3.1.2 Check-in and Check-out
- The system should facilitate a smooth check-in and check-out process for guests.
- Upon check-in, the system should generate a unique identifier (e.g., room key) for the guest.
- During check-out, the system should calculate the final bill and provide an itemized invoice.
3.1.3 Room Allocation
- The system should automatically assign available rooms based on guest preferences, room
types, and availability.
- Front desk staff should be able to manually allocate rooms if required.
3.1.4 Billing and Invoicing
- The system should calculate charges for room rates, additional services, and taxes.
- It should generate accurate invoices and receipts for guests.
- The system should support multiple payment methods, including cash, credit cards, and
online payments.
3.1.5 Room Service Management
- The system should allow guests to request room service, including food, beverages, and other
amenities.
- Staff should be notified of guest requests and manage their fulfillment.
3.1.6 Housekeeping Management
- The system should provide tools for housekeeping staff to manage room cleaning schedules
and track the status of rooms.
- Housekeeping staff should be able to update the room status (e.g., dirty, cleaned, in
maintenance) in the system.
3.1.7 Reporting and Analytics
- The system should generate various reports, including occupancy rates, revenue, guest
preferences, and service utilization.
- Managers should be able to access these reports for decision-making purposes.
3.2 Non-functional Requirements
3.2.1 Usability
- The system should have an intuitive and user-friendly interface.
- It should provide clear and concise instructions to guide users through various tasks.
3.2.2 Performance
- The system should be responsive and perform tasks efficiently, even during peak usage
periods.
- It should be able to handle a large number of concurrent users without significant
performance degradation.
3.2.3 Security
- The system should ensure data privacy and implement necessary security measures, such as
user authentication and encryption of sensitive information.
- Access to sensitive data and system functionality should be restricted based on user roles and
permissions.
3.2.4 Reliability
- The system should be highly reliable and available 24/7.
- It should have appropriate backup and recovery mechanisms to prevent data loss.
3.2.5 Scalability
- The system should be scalable to accommodate future growth and increased demands.
- It should be able to handle an expanding number of rooms, users, and transactions.
3.2.6 Compatibility
- The system should be compatible with various operating systems, web browsers, and devices
to provide flexibility to users.
- It should adhere to industry standards and best practices for compatibility and interoperability.

Appendices

Use case diagrams

Entity-Relationship (ER) diagrams
User interface mock-ups
Glossary

Note: This SRS is a general guideline and may require customization to fit specific hotel
management system requirements.
 PROGRAM NO. 3
AIM: To create the function-oriented diagram: Data Flow Diagram
(DFD).
Data Flow Diagram for Hotel Management
System:
Name: Hotel Management System Component Diagram

The hotel management system UML component diagram is used in object-oriented

Abstract: programming to group classes together based on their common purpose. This way, the
developer and others can see how a project is progressing at a high level.

UML
Component Diagram
Diagram:

Users: Bank Admin, Employee, and Card Holders.

Tools Used: Diagraming Tools that have UML Component Diagram Symbols

Designer: ITSourceCode.com

What is Hotel Management System DFD?

The DFD for Hotel Management System is an overall flow of how the
data moves through a system, describing its inputs and outputs process
within the entire system.

Furthermore, the data flow diagram (DFD) is a graphical representation

of the system data process management structure. In the case of
the Hotel Management System, you can edit this template based on your
needs.
Importance of Data Flow Diagram (DFD)

The importance of the data flow diagram (DFD) for Hotel Management system is to show
the devel- opers the actual happenings in the system. This is done by visualizing the system’s
data management at various levels.

Furthermore, the DFD levels were used to discuss the Hotel Management system data flow.
These lev- els have their part in expounding the system’s data flow structure details. It is
then ap-
plied in creating for Hotel Management system ER Diagram

Advantages of Data Flow Diagram:

The Advantages of the Hotel Management System Data Flow Diagram are as follows:

 It is a representation that aids in the visualization of system contents.

 Included in the system documentation file.
 Simple to grasp and understood by both programmers and users.
 System components were detailed and explained in DFD diagrams.
 It also aids in comprehending a system’s operation and limitations.
Hotel Management System Data Flow Diagram (DFD)

A thorough explanation is provided for the example data flow diagram for Hotel
Management System This example emphasizes the three DFD levels (DFD Levels 0, 1,
and 2) .

DFD Level 0 for ATM Machine

Hotel Management System Data Flow Diagram Level 1
DFD Diagram for Hotel Management System Level 2
 PROGRAM NO. 4
AIM: To perform the user’s view analysis for the suggested system:
Use case diagram.

A hotel management system use case diagram is used to

describe the behavior of the hotel management system. It shows the relationships
between users and how they interact with the
system.

Moreover, the hotel management system use cases include the project
functions using use cases, actors, and their connections. This explains the
complex functions of a system.

Hotel Management System Use

Case Diagram
The use case diagram example has two main illustrations. These illustrations describe
the system’s general and specific processes using include and extend.
 PROGRAM NO. 5
AIM: To draw the structural view diagram for the system: Class diagram.

Class diagram is a type of UML diagram which shows the properties and relationships among
various objects.
Class :
The classes used in this system are,
 Hotel Management : This class depicts the entire hotel and says whether the hotel is
opened or closed.
 Employees : It contains the details of the Employee. There are two kinds of employees,
Server and the chef. This employee class is the parent class of two subclass – Server and
Chef
 Server : It contains the details of the server, the table to which they are assigned, the order
which is currently serving, etc.
 Chef : It contains the details of the chef working on a particular order.
 Customer : It contains the details of the customer.
 Table : It contains the table details like table number and the server who are assigned to
that table.
 Menu : Menu contains all the food items available in the restaurant, their availability,
prize, etc.
 Order : Order depicts the order associated with a particular table and the customer.
 Bill : Bill is calculated using the order and menu.
 Payment : This class is for doing payment. The payment can be done in two ways either
cash or card. So payment is the parent class and cash and card are subclasses.
 Cash : Payment can be done by cash
 Card : Payment can be done by card or online
Attributes :
 Hotel Management – HotelName, NumberOfEmployees
 Employees – EmployeeId, EmployeeName, EmployeeSalary
 Server – ServerId, OrderId
 Chef – Chef_Id, OrderId
 Customer – CustomerId, CustomerName, Bill_Id, OrderId, PaymentId
 Table – TableNumber, OccupiedStatus, ServerId, CustomerId
 Menu – ItemId, ItemName, Amount
 Order – OrderId, ItemId, ItemName, Quantity, CustomerId, ServerId
 Bill – Bill_Id, OrderId, TotalBill
 Payment – PaymentId, Bill_Id

Methods :
1. Hotel Management :
 open() -This is used to indicate if the hotel is functioning or not.
2. Employees :
 employee details() – This method contains the details of the employee.
3. Customer :
 customer_details() – This depicts the details of the customer.
 ordered_items() – This method contains the items which are ordered by the customer.
 payment_status() -This says whether the customer paid or not.
4. Table :
 table_details() – This method contains the details of the table along with the customer and
no of seats.
 availability_status() – This method says whether the table is occupied or not.
5. Menu :
 items() – This method displays the menu items, their availability and their price.
6. Order :
 order_items() – This method orders the items selected by the user from the menu.
7. Bill :
 calculate_bill() – This method calculates the bill for a particular table.
8. Payment :
 ispaid() – It shows whether payment is successful or not.
Relationships :
Inheritance :
Inheritance is “is a relationship”. It has a parent class and its corresponding child classes. The child
class inherits the methods and attributes which are required for it from the parent class.
Here, Employee is parent class Server and Chef are child classes because server is a employee and
chef is a employee.
Association :
In Association, both classes are related to each other but are not physically contained with one
another. It is known as “using” relation. In association relation, consider we have two classes A and
B where class A calls class B and Class B also calls class A.
Here,
 Employee and customer
 Server and table
 Customer and payment
 Chef and order
follows association relationships.
Composition :
It is also called as “Has a” relationship where class A has an instance of class B, Class B is
composed inside class A and cannot exist independently without class A. So in composition one
class is entirely dependent on another class and is physically contained inside it.
Here,
 Menu and Order
 Order and Bill
 Bill and Payment
follows composition relation
Order cannot exist without Menu, Bill cannot exist without order and payment cannot exist
without bill. So here order is contained inside the menu, bill is contained inside the order and
payment is contained inside the bill.
Aggregation :
It is also called as “Has a” relationship where class A has an instance of class B, but class B is not
composed inside class A and can exist independently without class A. So in aggregation, both the
classes depend on each other and use each other but none of them are contained inside one another.
Here,
 Customer and Server
 Chef and Server
follows Aggregation relation
 Server is associated with the customer but can exist without the customer as well, Likewise Chef
is associated with the server but can exist without the server as well.
Notations :

Class Diagram :
 PROGRAM NO. 6
AIM: To draw the behavioral view diagram: State-chart diagram or
Activity diagram.
State Transition Diagram are also known as Dynamic models. As the name suggests, it is a type of diagram
that is used to represent different transition (changing) states of a System. It is generally used to
graphically represent all possible transition states a system can have and model such systems. It is very
essential and important and right for object-oriented modeling from the beginning. The System consists of
various states that are being represented using various symbols in the state transition diagram.
The symbols and their description are given below:
Now let us see the State Transition Diagram of Hotel Management System.
 PROGRAM NO. 7
AIM: To perform the behavioral view diagram for the suggested system:
Sequence diagram
Sequence Diagram of Hotel Management System
A sequence diagram for a hotel management system is a graphical representation of the
collaboration and communication between objects in a system. It outlines how activities are
coordinated to achieve a desired result. These diagrams are useful for identifying any existing
gaps in an existing business process or for developing a brand new process. It shows the
sequence of activities, the objects that are involved in each activity and the messages that are
exchanged between them. This makes hotel management easier to understand, maintain and
modify.
 PROGRAM NO. 8
AIM: Draw the component
diagram.
A component diagram in the (UML) Unified Modeling Language shows how parts are wired
together to explain the parts of hotel systems. They are used to show the structure of any
kind of system.

The UML component diagram shows how a hotel management system will be made up of a
set of deployable components, such as dynamic-link library (DLL) files, executable files, or
web services. Using well-defined interfaces, these parts communicate with each other and
keep their internal details hidden from each other and the outside world.

This component diagram of hotel management system is the illustration of the

components of every hardware and software node. The component diagram below
is a detailed illustration of the Deployment Diagram for Hotel Management
System .
 PROGRAM NO. 9
AIM: Draw the Deployment
diagram.
UML deployment diagram for hotel management system defines the software and hardware
interactions and processing during the system’s deployment. This diagram is one of the
structural diagrams which describes the physical aspects of the hotel management system
project.

This hotel management system deployment diagram is one of the UML models that
describes the system’s execution architecture. It can be used to determine how the system
will be installed on the hardware to ensure the system’s proper functionality
 PROGRAM NO. 10
AIM: Perform Measurement of complexity with Halstead Metrics for
chosen system.
To perform a measurement of complexity using Halstead Metrics for a hotel management
system, we need to analyze the code or software implementation of the system. Since I
don't have access to the specific code of your hotel management system, I can provide
you with an example of how to calculate Halstead Metrics using a hypothetical scenario.

Let's consider a specific functionality of the hotel management system: adding a new
guest to the system. We'll calculate the Halstead Metrics for this particular function.

First, we need to identify the following metrics:

1. Program Length (N):

- This is the total number of operators and operands in the program.
- Example: N = n1 + n2, where n1 is the total number of distinct operators and n2 is the
total number of distinct operands.

2. Vocabulary (n):
- This is the total number of distinct operators and operands in the program.
- Example: n = n1 + n2, where n1 is the total number of distinct operators and n2 is the
total number of distinct operands.

3. Program Volume (V):

- This is the quantitative measure of the program's size and complexity.
- Example: V = N * log2(n)

4. Difficulty (D):
- This measures the difficulty level of understanding the program.
- Example: D = (n1 / 2) * (N2 / n2), where N2 is the total number of operands.

5. Effort (E):
- This represents the amount of effort required to understand and implement the
program.
- Example: E = D * V

Let's assume the following values for our hypothetical hotel management system:

n1 = 12 (distinct operators)
n2 = 6 (distinct operands)

From the code implementation, we count the occurrences of each operator and operand
and determine the following values:

N = 20 (total number of operators and operands)

n = 18 (total number of distinct operators and operands)

Now we can calculate the Halstead Metrics:

V = N * log2(n) = 20 * log2(18) ≈ 90.585

D = (n1 / 2) * (N2 / n2) = (12 / 2) * (20 / 6) = 40

E = D * V = 40 * 90.585 ≈ 3623.4

These values provide a measurement of complexity and effort required for the specific
functionality of adding a new guest to the hotel management system.

Please note that this is just an example, and the actual calculation and values may differ
based on the specific code and implementation of your hotel management system.