HOTEL MANAGEMENT SYSTEM PROJECT REPORT
Project Overview
The main purpose of this project entitled as “HOTEL MANAGEMENT SYSTEM PROJECT REPORT” is to developed software for a HOTEL, which manages HOTEL Management System for Company, which is used to show the all type of information and all type of record to describe in Hotel management functioning. This software helps the top official in Hotel management and moreover we can say that it helps the Hotel management to show the all type information related to hotel internal activities.
Download Code
(HOTEL MANAGEMENT SYSTEM)
1.
Title of the Project
2.
Objective of the Project
3.
Project Category
4.
Analysis Report (DFD, ER DIAGRAM)
5.
Complete Structure of the Program
·
Number of Modules,
& its description
·
Data Structures
& Process Logic
·
Types of
Outputs/Reports Generation
6.
Tools /Platform Languages to be used
7.
Scope of Future Application
TITLE
OF THE PROJECT
The title of the project “Hotel Management
System”
INTRODUCTION:
In this age of
Information Technology when almost everybody has access to a computer and become all
types of work done by computer. So now all-official work and all hotels
using computer for management and financial working. My project is made as a step towards this
process.
Objective
I have
developed software for a HOTEL, which manages HOTEL Management System for MERA
MANN, which is used to show the all
type of information and all type of record to describe in Hotel management
functioning. This software helps the top official in Hotel management and
moreover we can say that it helps the Hotel management to show the all type
information related to hotel internal activities.
With the above
discussion a conclusion is drawn that all the components, which are covered by
this project, display a good and necessary part of Hotel management. So I say that my objective is to develop a
Hotel management system. Now the title I give to my project is “HOTEL
MANAGEMENT SYSTEM (HMS)“.
PROJECT
CATEGORY
The rules regarding this implementation and its
subsequent optimization will vary widely according to the type of DBMS.
Relational Database
Properties- A relational database management system (RDBMS)
has the following properties:
v Represents data in the form of tables
v Does not hard-code relationships between tables
v Doesn't require the user to understand its
physical implementation
v Provides information about its contents and
structure in system tables
v Can be manipulated through SQL commands
v Supports the concept of NULL values
The Database Management Systems available today
can be grouped into four types.
These are;
v File Management Systems (FMS)
v Hierarchical Databases (HDS)
v Network Databases (NDS)
v Relational Databases (RDBMS)-The relational
database model resulted from an IBM-sponsored research project by Dr. E.F.Codd.
The relation model attempts to overcome some the failings of the hierarchical
and network database model, and provides easy-to-use and flexible data
structure.
v The relational model includes data structure
(table), operators that can be used to manage the data in data structure, and some
integrity rules that ensure that the data obeys the business rules defined for
the system.
v The relational model is based on relational
algebra concepts and theory and, in the early days, used some of the same
technology to describe the processing that could be performed on the data
structures For example, relational theory uses the words "relations"
to mean tables, "tuples" to mean rows, and "attributes" to
mean columns in table
v
Relational
database are the most common type of database management systems in use today.
Created in 1979, ORACLE is among the products in the field. Other relational
database includes DB2, Ingress, Informix, Sybase, and SQL Server.
v Another important concept in relational databases
is that relationships between tables are not hard-coded in the structure of the
data that is there are no pointers in the data to relate one table to another.
This means that you can specify the relationships between two sets of data at
development time rather than when the
tables are first created. This greatly improves the flexibility of the database
management system.
ANALYSIS ( ER DIAGRAM)
ER DIAGRAM
COMPLETE STRUCTURE OF THE
PROGRAM
There are 9
main Menus
(1) Room_Info
(2) Item_info
(3) Guest_info
(4)
Emp_info
(5)
Mode _of_ payment
(6)
Security_info
(7) Report
(8)
Stockist_info
(9)
Food_info
DATA
STRUCTURE OF THE PROGRAM
Table Name: ROOM
ROOM_ID VARCHAR2 (20)
|
ROOM_TYPE VARCHAR2
(30)
|
Table
Name: ROOM_ALLOTMENT
GUEST_ID VARCHAR2 (20)
|
GUEST_NAME VARCHAR2 (30)
|
ADDRESS
VARCHAR2 (40)
|
CITY
VARCHAR2 (15)
|
STATE
VARCHAR2 (15)
|
COUNTRY VARCHAR2 (20)
|
PHONE_NO VARCHAR2
(15)
|
Table Name: SALARY
EMP_ID VARCHAR2
(20)
|
BASIC_PAY
NUMBER (7,2)
|
HRA NUMBER (7,2)
|
DA
NUMBER (7,2)
|
OTHER NUMBER
(7,2)
|
Table Name: SHIFT_INFO
SHIFT_ID VARCHAR2 (20)
|
START_TIME VARCHAR2
(6)
|
END_TIME
VARCHAR2 (6)
|
Table Name: STOCKIST
STOCKIST_ID VARCHAR2 (20)
|
NAME VARCHAR2
(30)
|
ADDRESS VARCHAR2 (40)
|
CITY
VARCHAR2 (20)
|
STATE VARCHAR2
(20)
|
PHONE_NO VARCHAR2 (15)
|
Table Name: USER_PERMISSION
NAME VARCHAR2 (20)
|
OPEN_PROGRAM VARCHAR2
(20)
|
ADD_PERMISSION VARCHAR2
(20)
|
MODIFY_PERMISSION VARCHAR2 (20)
|
DELETE_PERMISSION VARCHAR2 (20)
|
Table Name: PURCHASE
PURCHASE_ID VARCHAR2 (20)
|
ITEM_ID
VARCHAR2 (20)
|
STOCKIST_ID VARCHAR2 (20)
|
CHEQUE_NO VARCHAR2 (20)
|
DATE_OF_PURCHASE DATE
|
QUANTITY VARCHAR2
(20)
|
AMOUNT NUMBER
(7,2)
|
Table Name: PAY_MODE
CASH
VARCHAR2 (20)
|
CHEQUE
VARCHAR2 (20)
|
CREDIT_CARD VARCHAR2 (20)
|
Table Name: KITCHEN_ORDER
BETTER
VARCHAR2 (20)
|
CASHIER VARCHAR2 (20)
|
BILLING VARCHAR2
(20)
|
ITEM_ID
VARCHAR2 (20)
|
Table Name: ITEM
ITEM_ID VARCHAR2
(20)
|
FOOD_ID VARCHAR2 (20)
|
QUANTITY VARCHAR2
(20)
|
Table Name:
ITEM_ISSUE
FOOD_ID
VARCHAR2 (20)
|
FOOD_ORDER
VARCHAR2 (20)
|
INVOICE
VARCHAR2 (20)
|
ISSUE VARCHAR2
(20)
|
BALENCE VARCHAR2 (20)
|
Table Name: GUEST_LUGGAGE
LUGGAGE_ID VARCHAR2 (20)
|
GUEST_ID VARCHAR2
(20)
|
GUEST_NAME VARCHAR2 (30)
|
QUANTITY VARCHAR2
(20)
|
DATE_OF_LUGGAGE DATE
|
Table Name: GUEST_TIME
GUEST_ID
VARCHAR2 (20)
|
COMING_TIME VARCHAR2 (6)
|
GOING_TIME VARCHAR2 (6)
|
Table Name: FOOD
FOOD_ID
VARCHAR2 (20)
|
FOOD_NAME VARCHAR2
(30)
|
GUEST_ID VARCHAR2
(20)
|
BRAVAGE VARCHAR2
(20)
|
DATE_OF_SELL DATE
|
QUANTITY VARCHAR2
(20)
|
Table Name: EMPLOYEE
EMP_ID VARCHAR2 (20)
|
NAME
VARCHAR2 (30)
|
ADDRESS VARCHAR2
(40)
|
CITY
VARCHAR2 (20)
|
STATE VARCHAR2 (15)
|
PHONE_NO
VARCHAR2 (15)
|
DATE_OF_JOINING
DATE
|
Table Name: EMP_SHIFT
EMP_ID
VARCHAR2 (20)
|
SHIFT_ID VARCHAR2 (20)
|
Table Name: CHEQUE_INFO
CHEQUE_NO VARCHAR2
(20)
|
BANK_CODE
VARCHAR2 (20)
|
DATE_OF_ISSUE DATE
|
AMOUNT NUMBER (7,2)
|
Table Name: CHARGE
ITEM_ID
VARCHAR2 (20)
|
GUEST_ID
VARCHAR2 (20)
|
QUANTITY
VARCHAR2 (20)
|
AMOUNT
NUMBER (7,2)
|
TYPE OF REPORTS/ OUTPUTS GENERATION
REPORTING:
System
generates various outputs according to the input for both view and printing
purpose. The main Report generated by the system is as follows
Now with
the help of above argument we are showing the drawback of existing system and
showing good feature of new system. Then Hotel feels that the new system is
necessary to our Hotel. So, the management of Hotel decides that they want to
develop customized software that fulfill all the requirement of our Hotel and
reduce the burden of work.
Employee
This report shows Employee details such as name, phones no
etc of the entire employee.
Shift
report
This report shows Shift details such as shift_id, emp_id,
shift_time etc.
Guest report
This report shows Patient details such as guest_id, name,
phone no.
TOOLS/PLATEFORM
Hardware & Software Requirements:
i). Server
Side:
Hardware Requirements:
Processor - Pentium I (min.)
Speed - 2.7 GHz (min.)
RAM - 156 MB DDRAM
Hard Disc capacity - 40 GB or more
Monitor - SVGA Color Monitor
Printer - Dot Matrix / HP Laser Jet
Software Requirements:
Operating System - Windows
NT/98/2000
Front End - java 1.3
RDBMS - Microsoft Database/Oracle 8i
Animation - Macromedia Flash
Database
Connectivity - JDBC, ODBC
ii).
Client Side:
Hardware
Requirements
Processor - Pentium I (min.)
Speed - 2.7 GHz (min.)
RAM - 156 MB DDRAM
Hard Disc - 40 GB or more
Monitor - SVGA Color Monitor
Software Requirements
Operating System - Windows
NT/98/2000
Front End - java 1.3
RDBMS - Microsoft Database/Oracle 8i
Animation - Macromedia Flash
Database
Connectivity - JDBC, ODBC
Platform: MS
Windows
Tools, Software’s: java 1.3 & Oracle 8i
The Project will be developed on Windows 2000 Server
platform & can be run on any higher version or different platforms on
client’s machine.
The project is based on the concept of Client server
architecture. Selected backend is ORACLE 8i and the front-end (development tool) is JAVA 1.3. Points
discussed below describe the benefits of using these platforms & tools.
Windows:
At Present only windows is popular operating system
available, which supports graphical user interface and also is user friendly.
ABOUT JAVA:
The need of today’s
software development in a G.U.I based front-end tool, which can connect to
relational database engines. This gives the programmer the opportunity to
develop client/server based commercial applications.
These applications
give users the power and ease of use of a G.U.I with the multi-user
capabilities of NT based RDBMS engines like oracle.
From the array of
G.U.I based front-end tools I select Java because as we know that java is a
product of oracle corporation and it has best compatibility with oracle and
most of all the security in java is as same as in oracle database.
Oracle Java offers a
host of technical advantages over many other front-end tools.
Oracle:
The Oracle database system provides a number of benefits,
some of which can also be found in other relational database systems. Oracle
and its components run on more than 100 different hardware & operating
system platform (including all the different versions of Unix from the many
different vendors). Oracle Corporation also provides a full suite of
development tools, end-user tools, applications, and utilities. Some benefits
of using Oracle are:
1. Large
Databases
2. Many
Users (multiple user can work)
3. Portable
4. Backup
& Recovery features
5. Security
6. Client
Server Support
Future scope
Nothing is perfect. There should always
be a scope for further enhancement. A good should always give this flexibility
to except the new changes, which are generally introduced with time like
changes in the specification of the new system, or any newly discovered bug.
For this I have designed the project in
such a way that any change in specification could not disturb the whole
project.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.