synopsis
DESCRIPTION
SynopsisTRANSCRIPT
PROJECTPROJECT PROPOSALPROPOSAL SYNOPSISSYNOPSIS
Bachelor in ComputerBachelor in Computer ApplicationApplication
(CS-76)(CS-76)
Automation of HotelAutomation of Hotel ManagementManagement
ForFor(Hotel MILAN Allahabad)(Hotel MILAN Allahabad)
1
Name : Shailendra Kumar
Enrollment No. : 043605020
Table of Contents
Project Proposal (Synopsis)
Content Page No.
1. Title of the Project 3
2. Objective of the Project 3
3. Problem Specification 4
4. Proposed System 5
5. Design 6-7
6. Input to the project 8
7. Output of the Project 8
8. Process Logic - System Flow Chart (DFD) 9-
10
9. Entity Relation Ship Diagram (ER- Diagram) 11-15
10. Limitation And Assumption Of The Project 16
11. Tool/Platforms, Languages to be used 17-22
12. Is Project For Any Client 23
13. Future Enhancement Future Application of the 24
Project
2
3
Title of The Project
AUTOMATION OF HOTEL MANAGEMENT
Objective of the project Objective of this project is that to over come the problems of the
paper work at the Management of Hotel and this project has helped to solve
this. Through use of this project we can easily keep all records of
CUSTOMERS and their entries. And this project is very useful for HOTEL
MILAN Information. The project offers the Entry of the New, Previous and
Regular CUSTOMERS and also to reserve their Booking rights in the desired
ROOMS, we can also enter the all information of customer at any level.
This project has many facility and all that manage (controlled) by a
single computer system. This project (AUTOMATION OF HOTEL
MANAGEMENT) has many salient features-
1. Computer, which keeps all detail of CUSTOMERS.
2. On line updating of records of all CUSTOMERS.
3. This project helps to check the status of the room, which desired.
4. The ordered description is also handled by this project.
5. We can see the daily updating the room status by just clicking the
menu progress project report.
This project is very helpful for us because we can easily access any
information about of all CUSTOMERS.
4
PROBLEM SPECIFICATION
In the present system all the record are maintained manually by the hotel
employees. Manual updating and maintenance of records has many problems
1. Due to rapid change in the database, the records have to be
updated frequently and manual updating makes this process very
slow and cumbersome.
2. For the smooth functioning of the system the updating of the
records should be error free but as the system is handled manually,
occurrence of error in the record updating is natural.
3. As all the records are kept in the data register, it is difficult for the
owner as well as the employees to view various records at the
same time for searching a record concerning a particular customer
they have to see through a number of data registers which is very
cumbersome and time consuming.
4. Manual storage of records may lead to inconsistency and
redundancy of the data.
These problems have led to the need of developing a new system, which will
tackle the above problems efficiently.
5
PROPOSED SYSTEM
The system is to build that provides complete functionality as well as a
perfectly User-friendly environment. The proposed system is to be designed
for the following purposes
1. It should maintain the records of the room, which gives user as well
as reception to easy to know about the room available in the hotel.
2. It should be able to book the new customer.
3. It should maintain all the vehicle related information.
4. It should generate bills for the customers.
The main objective of the proposed system is to reduced time while
processing with minimum risk of errors.
6
Design
Logical System Design Specify the user need at a level of detail that virtually
determines the information flow into the system and the required data
resources. Logical Design cover the following step:
Reviews the Current Physical System.
Prepare Output Specification.
Specifies The Implementation plan.
Prepare the Input Specification
7
People Questioned
Book Entry
Member Entry
Book requiting
Controller Of the System
Transaction Process
Output Expected
1. To get the complete project within stipulated time period.
2. To make the System Error Free.
3. To Provide Necessary Flexibility.
4. To make it User Friendly.
5. To convert it into Reliable System.
8
INPUT TO THE PROJECT
Input about CUSTOMERS information (Customer ID, Name, Address,
Customer type, Phone No., Nationality etc.).
Details of Rooms Booking (Rooms Type, Room Cost, Room No.,
Status etc.)
Input types of Room (First class AC, General or and Room’s Cost)
Input Booking Details of Rooms such that booking mode, rate,
purpose, paid amount, Room No., Departure date etc.)
Input customer type (Regular or New or Other)
Details of Laundry (Item Name, Quantity, Rate, Remarks etc.)
Details of Hire Vehicle (Booking No., Hire Date, Vehicle ID, Model,
Status, Registration No., Rate/Day etc.)
OUTPUT OF THE PROJECT
Output of Booking Details (Customer ID, Customer Type, Purpose of
Booking, Rooms Type, Room Cost, Room No., Status etc.) of the
CUSTOMERS.
All information about CUSTOMERS (Customer ID, Name, Address,
Customer type, Phone No., Nationality etc.) in any time.
Details of laundry service (Item Name, Quantity, Rate, Remarks etc.).
We can take all information about Hotel any time.
Print user report.
Make bill of customers and print of them.
Displays of room booking.
9
No
Yes
Yes
No
Yes
10
SYSTEM FLOW CHART
Start
Enter login/password
Open the security
If login/passwo
rd correct
Display appropriate error
message
Display the initial screen
If optionIs
“Booking”
If option is “Vechicle Booking”
Display appropriate BookingInformation
Display appropiate vechicleInformation
BookingReports
VechileReports
1
1
A
BD
C
No
Yes
No
Yes
NO
Yes
No
No
Yes
11
If option is
“custom”
Display appropriate custom
Information
If option is
“Room”
Display appropriate roomInformation
If option is “laundry”
Display appropriate laundryInformation
If option is “EXIT”
D
END
CustomReport
Room Report
LaundryReport
A
C
B
Entity Relation Ship Diagram -1
12
BOOKING DETAIL
Booking date
Room rate
Advance Amount
Total Amount
Booking mode
Mode details
Purpose
Arrival Date Departure Date
Check In Date
Check out Date
Day to Stay
Other Details
ROOM BOOKING
Room NoCustomer ID
CUSTOMERS
ROOMSOccupation
Last Name
Sex
Nationality
Customer
type IDEmail
FaxMobil No.
Phone no
State
First Name
Middle Name
Room type ID
Status
Amount Due
Amount Paid
Address
City
Booking Number
Entity Relation Ship Diagram –2
13
Room NoROOMS
Room type ID
Status
Is of Type
ROOMTYPERoom Type Name
Rate
Remarks
Room type ID
Entity Relation Ship Diagram –3
14
Customer ID
CUSTOMERS
Occupation
Last NameSex
Nationnality
Customer type ID
Fax
Mobil No.
Phone no
State
First Name
Middle Name
Address
City
CUSTOMER TYPE
IS OF TYPE
Customer type ID
Customer Type name
Room RebateFood
Rebate
Vehicle Rebate
Entity Relation Ship Diagram –4
15
Booking Number HIRE DETAILS
Vehicle ID
Fare Per Day
Vehicle
Hired
Vehicle Type
Model
Registration Number
Rate Per Day
Vehicle ID
Total Fare
Hire Date From
Hire Date Upto
Type
Status
Entity Relation Ship Diagram –5
16
BOOKING DETAIL
Booking date
Room rate
Advance Amount
Total Amount
Booking mode
Mode details
Purpose
Arrival Date Departure Date
Check In Date Check out Date
Day to Stay
Other Details
Amount Due
Amount Paid
Booking Number
Laundry
Hire Details
Related To
Item name
Remarks
Rate
Quantity
Status
Total fare Amount due
Vehicle code
Fare per day
Hire date up to
Hire date from
Booking Number
LIMITATION AND ASSUMPTION of the Project
1. This software does not provide any facility of backup.
2. Most banks now follow an online updating, but due to hardware and
practical limitation we are not able to provide the above stated
services.
3. It not works on the client-server architecture right now.
4. This software cannot run on MS-Dos environment.
5. The complete post office facilities are not included.
6. The project has the following limitation and assumption.
7. This is a standalone application.
8. Since we have use data report for printing the report, print out is much
slow. If we have use API’S than the printing speed would have been
fast.
9. This is not a multi-user application.
10.There is no provision for printing bill on pre-printed paper, latter head,
the bill is been printed interlay.
17
Tool/Platforms, Languages to be used
Implementation Specification
1. Hardware Specification
Personal Computer
PC/AT Assembled Computer
Microprocessor
Intel Pentium III 800 MHz
Computer Memory
RAM 128 MB
HDD 40.0 GB
Printer
HP LASER
2. Software Specification
Front End : Visual Basic 6.0
Back End : Oracle 8.0
18
Why Visual Basic as Front End Tool
What is Visual Basic? The "Visual" part refers to the method used to create
the graphical user interface (GUI). Rather than writing numerous lines of code
to describe the appearance and location of interface elements, you simply add
prebuilt objects into place on screen. If you've ever used a drawing program
such as Paint, you already have most of the skills necessary to create an
effective user interface.
The "Basic" part refers to the BASIC (Beginners All-Purpose Symbolic
Instruction Code) language, a language used by more programmers than any
other language in the history of computing. Visual Basic has evolved from the
original BASIC language and now contains several hundred statements,
functions, and keywords, many of which relate directly to the Windows GUI.
Beginners can create useful applications by learning just a few of the
keywords, yet the power of the language allows professionals to accomplish
anything that can be accomplished using any other Windows programming
language.
19
Visual Basic Concepts
In order to understand the application development process, it is helpful to
understand some of the key concepts upon which Visual Basic is built.
Because Visual Basic is a Windows development language, some familiarity
with the Windows environment is necessary. If you are new to Windows
programming, you need to be aware of some fundamental differences
between programming for Windows versus other environments.
How Windows Works: Windows, Events and Messages
A complete discussion of the inner workings of Windows would require an
entire book. A deep understanding of all of the technical details isn't
necessary. A simplified version of the workings of Windows involves three key
concepts: windows, events and messages.
Think of a window as simply a rectangular region with its own boundaries.
You are probably already aware of several different types of windows: an
Explorer window in Windows 95, a document window within your word
processing program, or a dialog box that pops up to remind you of an
appointment. While these are the most common examples, there are actually
many other types of windows. A command button is a window. Icons, text
boxes, option buttons and menu bars are all windows.
The Microsoft Windows operating system manages all of these many
windows by assigning each one a unique id number (window handle or
hWnd). The system continually monitors each of these windows for signs of
20
activity or events. Events can occur through user actions such as a mouse
click or a key press, through programmatic control, or even as a result of
another window's actions.
Each time an event occurs, it causes a message to be sent to the operating
system. The system processes the message and broadcasts it to the other
windows. Each window can then take the appropriate action based on its own
instructions for dealing with that particular message (for example, repainting
itself when it has been uncovered by another window).
As you might imagine, dealing with all of the possible combinations of
windows, events and messages could be mind-boggling. Fortunately, Visual
Basic insulates you from having to deal with all of the low-level message
handling. Many of the messages are handled automatically by Visual Basic;
others are exposed as Event procedures for your convenience. This allows
you to quickly create powerful applications without having to deal with
unnecessary details.
21
Why ORACLE as RDBMS
ORACLE is a relational DBMS developed by the ORACLE CO-OPERATION
(formerly RELATIONAL SOFTWARE, INC).
The original company was formed in 1977 and the first version was installed
on a DEC-PDP-11 system in 1979. This was developed utilizing “D” language
to ensure maximum portability.
SYSTEM COMPONENT:
The oracle DBMS consists of the ORACLE KERNEL, SQL (structured query
language and SQL*PULS interface, system utilities and host language
interfaces.
The basic component of the system is the ORACLE kernel. The kernel
requires approximately 350k byte of main memory, parts of kernel are
swapped in or out as needed.
SQL is the primary interface to ORACLE. It is generally considered an on-line
query language. The oracle kernel executes all SQL commands.
SQL* PLUS is the processor that allows on line access to the SQL. Its
commands allows for the formatting of queries, generation of reports and
accessing of on-line HELP facility.
SQL commands can also be executed form within certain host programming
languages such as C, COBOL and FORTAN.
22
SQL –The query Language
INTRODUCTION:
SQL (structured Query Language) is used by oracle for all interaction with the
database. SQL was originally called SEQUEL (an abbreviation for Structured English
Query Language) and was implemented at IBM Research. Since then several
version and variations of SQL have been developed by many DBMS vendors for their
relational database. The SQL statements for simple operation are similar for majority
of relational DBMS available in the market today. The standard SQL is called the
ANSI SQL.
Oracle supports direct SQL interface to its database by the use of SQL* PLUS. SQL*
PLUS is based on SQL and can be used to manipulate oracle data prepare reports
on the contents of that data.
23
Is Project for any client?………………
No I am not designing this project for any specific client or industry, I
survey the HOTEL MILAN and collect the data and designed the
project.
24
Future Enhancement
The automated system saves times and gives you accurate results and
helps to serve the operators in a much better way, but very limitations of the
system is that it should be operated with great care especially when entering
the codes and customer information. If an incorrect code is entered it without
cause errors. Care has been taken that every field is entered but if a wrong
value entered it will cause an error. So if the system is operated carefully it will
save a lot of computation time, waiting time and will give accurate and desired
results within no time. In future version of our system we would take into
consideration that there are least chances of absurd input from user.
It is also desired to add a few modifications to our AUTOMATION OF
HOTEL MANAGEMENT. Taking into consideration the security point of view
we would like the S/W to open in read only mode for an authorized user. In
future version we would like to add this feature also.
FURTURE APPLICATION OF THE PROJECT
1) It can be customized for client server model, So that the
software will run on network.
2) It can also be customize to have multi-user, multicolor facilities,
with various writes permission, assigned to different user,
logging.
3) We can easily add module related to restaurant, shopping etc.
4) We can also speed up the printing speed by implementing API’s
in the project.
25
BCA VI
SYNOPSIS
AUTOMATION
OF
HOTEL MANAGEMENT
GUIDED BY : DEVOLOPED BY:
SUSHANT SRIVASTAVA SHAILENDRA KUMARLecturer Kulbhasker Ashram Post Graduate College Enrollment No. 043605020Allahabad
26