SE [160701] Hotel Management System 1. Problem Definition 1.1 Proposed System The Hotel Reservation system will provide service to on-line customers, employee, and an administrator. Online customers can make searches, reservations and cancel an existing reservation on the hotel reservation’s web site. Administrator can add/update the hotel and the room information approve/disapprove a new employee account application and generate a monthly occupancy rate report for each hotel. The development of this new system contains the following activities, which try to automate the entire process keeping in the view of database integration approach. This system maintains user’s personal info, address, and contact details. User friendliness is provided in the application with various controls provided by system rich user interface. This system makes the overall project management much easier and flexible. Various classes have been used for maintaining the details of all the users and catalog. Authentication is provided for this application. Only registered users can access. Report generation feature is provided used to generate different kind of reports. This system is providing more memory for the users to maintain data. This system is providing accessibility control to data with respect to users. 1.2 Existing System BIT/CSE/120050131525 Page no. 1
This is a detailed report about the hotel management system in which every modules of the system has been discussed in detail as well as all the diagrams have been drawn. It will be very beneficial to the students who have taken up hotel management system as their project as all the modules and all uml diagrams are already done for you.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SE [160701] Hotel Management System
1. Problem Definition
1.1 Proposed System
The Hotel Reservation system will provide service to on-line customers, employee, and an
administrator. Online customers can make searches, reservations and cancel an existing
reservation on the hotel reservation’s web site. Administrator can add/update the hotel and
the room information approve/disapprove a new employee account application and generate a
monthly occupancy rate report for each hotel. The development of this new system contains
the following activities, which try to automate the entire process keeping in the view of
database integration approach. This system maintains user’s personal info, address, and
contact details. User friendliness is provided in the application with various controls provided
by system rich user interface. This system makes the overall project management much easier
and flexible. Various classes have been used for maintaining the details of all the users and
catalog. Authentication is provided for this application. Only registered users can access.
Report generation feature is provided used to generate different kind of reports. This system
is providing more memory for the users to maintain data. This system is providing
accessibility control to data with respect to users.
1.2 Existing System
The existing system uses paperwork and direct human language communication by mouth to
manage the hotel. This delays information transmission in the hotel. Booking is done through
phone calls or through visit to the hotel booking office. The guest’s personal details such as
Name, Age, Nationality, and Duration of stay, are input during booking in. The booking
office orders for preparation of the guest’s room before his/ her check in date.
The documents are transferred manually to the filling department for compilation of the
guest’s file. On the reporting date the file is transferred to the reception. On checking in the
guest is given the key to his allocated room, he also specify if he needs room service.
The receptionist hands over the guest’s file to the accountant on the next table. Here the guest
pays accommodation and meals fee. The guest’s file is updated on daily basis of his
expenditure costs. The accounts department generates the bills on daily basis and delivered to
the guests in their rooms at dusk by the service maids. The guest pays at the accounts desk,
where the receipts are generated. For a one meal customer the bill is generated immediately
BIT/CSE/120050131525 Page no. 1
SE [160701] Hotel Management System
after ordering and he pays at the accountant desk before leaving. During checking out of
guests, their expenditure outlines are generated a day before check outdate.
BIT/CSE/120050131525 Page no. 2
SE [160701] Hotel Management System
2. Requirement Specification
2.1 Functional Requirement Specification
1. Reservation/Booking1.1. The system shall record reservations.1.2. The system shall record the customer’s first name.1.3. The system shall record the customer’s last name.1.4. The system shall record the room number.1.5. The system shall display the default room rate.1.6. The system shall record the customer’s phone number.1.7. The system shall display whether or not the room is guaranteed.1.8. The system shall generate a unique confirmation number for each reservation.1.9. The system shall record the expected checkout date and time.1.10. The system shall check-in customers.1.11. The system shall checkout customers.1.12. The system shall charge the customer for an extra night if they checkout
after 11:00 a.m..1.13. The system shall record customer feedback.
2. Food2.1. The system shall track all meals purchased in the hotel (restaurant and room
service).2.2. The system shall record payment and payment type for meals.2.3. The system shall bill the current room if payment is not made at time of
service.2.4. The system shall accept reservations for the restaurant and room service.
3. Management3.1. The system shall display the hotel occupancy for a specified period of time
(days; including past, present, and future dates).3.2. The system shall display projected occupancy for a period of time (days).3.3. The system shall display room revenue for a specified period of time (days).3.4. The system shall display food revenue for a specified period of time (days).3.5. The system shall display an exception report, showing where default room
and food prices have been overridden.3.6. The system shall allow for the addition of information, regarding rooms,
rates, menu items, prices, and user profiles.3.7. The system shall allow for the deletion of information, regarding rooms, rates,
menu items, prices, and user profiles.3.8. The system shall allow for the modification of information, regarding rooms,
rates, menu items, prices, and user profiles.3.9. The system shall allow managers to assign user passwords.
BIT/CSE/120050131525 Page no. 3
SE [160701] Hotel Management System
2.2 Non-Functional Requirement Specification
1. Performance: This describes how the website behaves to a request sent in by a client.
Like suppose a client sends in a request then with what speed the website handles the
request of the client describes this.
2. Availability: The website should be available whenever a client request access. Like
at a particular instant of time if there are multiple users trying to access the site the
website should acknowledge the request of all the clients.
3. Reliability: The website should be reliable, that is it should store data correctly and
accurately whenever an input is given. Whenever data is to be stored it should be
cross-checked whether the data is stored correctly or not.
4. Security: The data that is stored securely by the website. The website should
incorporate some encryption technique in order to prevent the leakage of the website
database.
5. Data Integrity: The system should maintain data integrity that is, it should maintain
the data correctly so that data on the server side and client side remain the same.
6. User Interface: The user interface should be maintained on a medium level so that
even the clients with slow connection speeds can easily browse the website.
7. Efficiency: The website incorporates binary search tree algorithm for better
efficiency during searching of the content in the database.
8. Accessibility: The data should be controlled on the priority bases so that its access is
dependent on the priority level of the client accessing the data.
BIT/CSE/120050131525 Page no. 4
SE [160701] Hotel Management System
3. Project Management
4.1 Effort Estimation:
COCOMO (Constructive Cost Estimation Model) was proposed by Boehm 1981. Boehm
postulated that any software development project can be classified into a one of the following
categories based on development complexity: organic, semidetached and embedded. In order
to classify a product into the identified categories, Boehm requires us to consider not only the
characteristics of the product but also of the development team and the development
environment. Roughly speaking, the three product classes correspond to application, utility
and system programs, respectively. Normally data processing programs are considered to be
application programs. Compilers, linkers etc. are utility programs. Operating systems and real
time system programs etc. are system programs. System programs interact directly with the
hardware and typically involve meeting timing constraints and concurrent processing.
Also the utility programs are three times as difficult to write as application programs and,
system programs are roughly three times as difficult as utility programs. Thus, the relative
levels of product development complexity for the three categories (application, utility and
system programs) of products are 1:3:9.
Boehm’s [1981] definitions of organic, semidetached and embedded systems are elaborated
as follows:
1. Organic: We can consider a development project to be of organic type, if the project
deals with developing a well understood application program, the size of the
development team is reasonably small, and the team members are experienced in
developing similar types of projects.
2. Semidetached: The project can be considered of this type is the development team
consists of a mixture of experienced and inexperienced staff. Team members may
have limited experience on related systems but may be unfamiliar with some aspects
of the system being developed.
BIT/CSE/120050131525 Page no. 5
SE [160701] Hotel Management System
3. Embedded: The project can be considered of this type, is the software being
developed is strongly coupled to complex hardware, or if stringent regulations on the
operational procedures exist. Here we have chosen the embedded model since all the
team members are new in the field of the software development and also the software
product size is relatively small.
Estimation of Development Efforts
1. Organic model:
Efforts=2.4(KLOC) 1.05 Person-Months
2. Semi-Detached Model:
Efforts=3.0(KLOC) 1.12 Person-Months
3. Embedded Model:
Efforts=3.6(KLOC) 1.20 Person-Months
Functional Point Analysis
The idea of function points - slicing the system into smaller parts - focuses on five types of
components:
EI - external inputs, which are the components responsible for introducing changes in
system's internal data.
EO - external outputs, which are the ways system's internal data can be presented, but
beware - there are a few similarities with EQ components, though.
EQ - external inquiries, which are the methods for reading system's data without modifying
it.
EIF - external interface files, which are responsible for exchanging data with other systems.
ILF - internal logical files, which are files that are being used by the system itself.
BIT/CSE/120050131525 Page no. 6
SE [160701] Hotel Management System
How to perform Function Points Analysis?
Every FPA must be begun with grouping the components of the system we'd like to analyse.
That's why the five groups (listed above) are distinguished. Once the components are selected
and grouped, we can turn to analysing itself.
We need to classify the complexity of each category. We therefore have three possibilities -
the complexity could be low, average, or high. Then, the thing is to count the scores.
Sum the values, the total represents the number of application's function points.
‘Functional Point Analysis’ Table: [Table 1]
Functional Point Analysis
Component: Complexity:
Low Average High Total
EI 3 x 6 = 18 0 0 18
EO 4 x 2 = 8 0 0 8
EQ 0 0 0 0
ILF 0 7 x 1 = 7 0 7
EIF 0 10 x 1 = 10 0 10
Total Number of Unadjusted Functional
Points282
Multiple Value Adjustment Factor = 0.65 +
0.01 * DI 1.02
Total Adjusted Function Points = UFP * TCF 287.64
BIT/CSE/120050131525 Page no. 7
SE [160701] Hotel Management System
‘Degree of Influence’ Table: [Table 2]
S.No. Degree Of Influence Value
1 Data communications 5
2
Distributed data
processing 2
3 Performance 2
4
Heavily used
configuration 1
5 Transaction rate 4
6 On-Line data entry 6
7 End-user efficiency 0
8 On-Line update 1
9 Complex processing 1
10 Reusability 6
11 Installation ease 0
12 Operational ease 0
13 Multiple sites 5
14 Facilitate change 4
Based on Functional Point Analysis our Line of Code would be: 1.25KLOC for the module.