Hotel Automation System: Project Supervisor
Hotel Automation System: Project Supervisor
Hotel Automation System: Project Supervisor
Project Supervisor
Israr Hussain
Submitted By
Muhammad Nouman Shoukat
2015-UAM-56
Qazi Muhammad Asif
2015-UAM-54
Waqar Ahmad
2015-UAM-52
Department of CS/IT
Muhammad Nawaz Sharif University of Agriculture.
Multan.
EXORDIUM
Every work is done by computer technology in this age that’s why the main idea to
creating this project is too automate the whole system of specified hotel. So then it is easy for
owner to manage their work with in less time and cost.
DEDICATION
This project is dedicated to our Muhammad Nawaz Shareef University of Agriculture which always
stood along and supported us in every ups and down during this 4 year tenure. We are hopeful
that our project will help in Agriculture Technologies and take our University to a new level of
innovations. We are highly grateful to the Professors who invested their efforts and precious time
in us and to the bitter & sweet memories.
ACKNOWLEDGEMENT
We humbly thanks to Allah, The one who only knows secrete. And also a very special thanks to
Holy Prophet (peace be upon him) by following him we attained faith and perfection.
Our thankfulness is also for all my Family Members because without their help and support I
could not complete this project.
We want to give a respected gratitude to Israr Hussain my supervisor, who provided us much
knowledge and required material which needed to complete this project. His sage advice,
insightful criticisms, and patience encouragement aided the writing of this thesis in innumerable
ways.
Hotel Automation System
TABLE OF CONTENTS
CHAPTER 1
INTRODUCTION
1.1. GATHERING & ANALYZING INFO
1.2. MOTIVATION
1.3. SCOPE
1.4. AIMS & OBJECTIVE
CHAPTER 2
CHAPTER 3
System Analysis and Design
3.1. FUNCTIONAL REQUIREMENTS
3.2. NON-FUNCTIONAL REQUIREMENTS
3.2.1 USABILITY
3.2.2 RELIABILITY
3.2.3 Tools Selection
3.3. USE CASES AND USAGE SCENARIOS
3.3.1. USE CASE DIAGRAMS
CHAPTER 4
4.1 INTRODUCTION
4.2. PURPOSE
4.3. Methodology
4.3.1 Available Methodology
4.3.2. Chosen Methodology `
4.3.3. Characteristics
4.4. GRAPHICAL USER INTERFACES
CHAPTER 5
CONCLUSION & FUTURE WORK
5.1 DISCUSSION
5.2 FUTURE WORK
5.3.1 Implementation
References
Hotel Automation System
CHAPTER 1
INTRODUCTION
1.1. Motivation
Even though some computer applications exist in the current market to address
mentioned problems, they are few in numbers. Most of these applications do not provide a
comprehensive list of functionalities. Some of them only provide a digital menu, while
others allow customers order their food and pay for it but lack in room reservation facilities
or Employees Salary Record. In this subsection, the author investigates and describes some
of these computer applications in order to make the gap in the market regarding hotel
applications clear to the reader.
Our software can be used in any kind of hotel like having 200 or 300 rooms, guest
house, Hotel hotel/kitchen and more. It is not Web Based Application, it is standby
Application.
The aim was to create a single hotel application that could be used for preserving
incoming guest record and allotting them a room and providing them food and other services.
1.2. SCOPE
The scope of the system means the area of the proposed system. We intended to
design the Hotel Automation System which encompasses the following aspects:
Maintains the Guest record.
It is portable
It helps the hotel manager to manage the hotel more effectively and
efficiently by computerizing room management, room reservation, guest
record, billing, employees attendance
It is designed to help owner to add rooms category and change it’s
reservation prices and monitor the employee’s salary record.
1.4. DEFINITIONS, ACRONYMS AND ABBREVIATIONS
Term Description
HAS The name of the application, given by the developer.
Hotel The culinary business premises that uses this application
Hotel customer who gets the room.
Customer
Hotel staff (either kitchen staff or waiter) who handles orders and manage
Staff
rooms.
Manager Hotel manager who edits the menu and accesses sales reports
Food Each item of the menu
Rooms Record
Room
SRS:
A software requirements specification (SRS) is a description of a
software system to be developed. It is modeled after business
requirements specification
C#
C Sharp (programming language) is a multi-paradigm programming
language encompassing strong typing, imperative, declarative, functional,
generic, object-oriented (class-based)
MS-SQL
Microsoft SQL Server is a relational database management system
developed by Microsoft. As a database server, it is a software product
with the primary.
13
Chapter 2
Background Study/Related Work
In the existing system, all the information of hotel and customer proceed
manually and it has no ability to maintain the record of the entire entity activity involved
in manual system. Searching the guest record was done by the person own self by finding
the specific register. In this case, time was very essential. So to solve this problem or
stock of problems can be listed in the existing system. If any guest comes to check in for
one day two months ago then it is difficult and time consuming to provide his record in
any case.
As we observe, all records of hotel are maintained manually. The world is going
towards the success of the technology but this hotel has not any facility to deal with their
routine work by the use of technology. Manual existing systems are giving them facility
to maintain and check the records but that is not even very beneficial for hotel. After our
observation, hotel owner want portable software that deals with all the work flow of their
daily routine.
14
2.2 Flaws/Drawbacks in existing system:
Increased time taken by the personnel. It is very tedious job to find the record of a
guest who visits hotel 1 year ago
At the time of searching specific record all the records have to be scanned and
even after the manager can’t be sure that they will be able to find that guest.
In addition, owner wants to update their records each time a deletion or addition.
A large number of people involved to maintain the whole system that is very
expensive.
The cost also increases to the hotel with the increasing of hotel maintenance.
A large number of manpower is involved to maintain the whole system, which is
very expensive.
Unreliable and inefficient data entry.
Lesser user friendly.
Redundant data storage.
Uses a lot of registers for maintaining record.
15
2.3 Literature review:
Before our software, when a guest visits hotel 2nd time a month he have to
introduce himself that he have visited again and all the record have to be stored again.
This is very irritating for guest as this is also very time consuming.
16
Hotel Automation System
CHAPTER 3
17
Hotel Automation System
Update Reservation
Provide Services.
Print Receipt.
18
3.2. NON-FUNCTIONAL REQUIREMENTS
3.2.1. USABILITY
The term “Usability” in the context of creating software represents an approach that
puts the user, rather than the system, at the center of the process. This philosophy, called
user-centered design incorporates user concerns and advocacy from the beginning of the
design process and dictates that the needs of the user should be foremost in any design
decisions.
The links are provided for each form. The user is facilitated to view and make entries in the
forms. Validations are provided in each field to avoid inconsistent or invalid entry in
databases. Some forms consist Hyper Links, which provides further details. Reports screen
contains text boxes and drop-down lists, so that reports can be produced.
3.2.2. RELIABILITY
The system should be robust enough to have a high degree of fault tolerance. The
system should not crash and should identify the invalid input and produce a suitable error
message. It should be able to recover from hardware failures, power failures and other
natural catastrophes and rollback the databases to their most recent valid state.
C# Language
WINDOWS Operating System
MS-SQL Server
HARDWARE REQUIREMENTS
Activity
Logout
3.5. SEQUENCE DIAGRAMS
The dynamic model describes the behavior of a distributed parameter system in terms
of how one qualitative state can turn into another. A qualitative state is described by a static
model, i.e. the distributions and intersections of the qualitative fields at a particular time
instant or interval. The sequence Diagram is best way to show Dynamic Model here is one
diagram which shows the working of Restaurant Management System
The UML diagram Sequence diagram shows the work done in the project. It shows that how Customer enters and see the
information and access the data.
3.6. Database Design:
CHAPTER 4
4.1 INTRODUCTION
The importance can be stated with a single word “Quality”. Design is the place
where quality is fostered in software development. Design provides us with representations
of software that can assess for quality. Design is the only way that we can accurately
translate a customer’s view into a finished software product or system. Software design
serves as a foundation for all the software engineering steps that follow. Without a strong
design we risk building an unstable system – one that will be difficult to test, one whose
quality cannot be assessed until the last stage.
During design, progressive refinement of data structure, program structure, and
procedural details are developed reviewed and documented. System design can be viewed
from either technical or project management perspective. From the technical point of view,
design is comprised of four activities – architectural design, data structure design, interface
design and procedural design.
4.2. PURPOSE
The main purpose of the system is to manage the all issues about Restaurant in a most
interactive and a user-friendly environment. Desktop Application has become a driving force. It
is the engine that drives the business decision making. The development in the field of sciences
and technology has improved efficiency of data processing mechanisms.
4.3. METHODOLOGY
1. A Waterfall Model
4. Incremental Model
Incremental Model: Incremental Model is a process of software development where requirements are
broken down into multiple standalone modules of software development cycle. Incremental development is done
in steps from analysis design, implementation, testing/verification, maintenance.
Each iteration passes through the requirements, design, coding and testing phases. And each
subsequent release of the system adds function to the previous release until all designed functionality has been
implemented.
Once the incremented portion id developed, requirements for that increment are frozen
4.4 GRAPHICAL USER INTERFACES
CHAPTER 5
5.1. Discussion
The major goal of the project is to create a system that provides certain predefined
functions, reliability of system, flexibility, maintainability, efficiency and security. After the
study of existing system, We design a system that completely fulfills all the requirements of
Hotel Automation System. Computer based system design serves as the foundation for all
maintenance and requirement steps. It is compiled with the objective of reducing the problems
present in the existing system.
The Proposed system is Desktop Application. This Application have facility to edit,
delete, insert different kind of record such as Customer, employees record, operation record and
reports, this Application also keep the record of Customer, Customer details, information about
departments. It is hoped that Application will fulfill the requirements of the Hotel Automation
System.
Admin can do all the functions such as updating, editing, deleting records.
This Application also keep the record of Customer, Customer details, information
about departments. It is hoped that Application will fulfill the requirements of the Hotel
Automation System. Admin can do all the functions such as updating, editing, deleting
records.
Programming languages choice affects the productivity and code quality in several ways.
Programmers working with high level language achieve better productivity and quality than
those working with low level languages. I have used MS-SQL and C# for the coding.
Hotel Automation System
5.3.1. Implementation
Once the initial implementation exercise is completed and changeover has been
successfully concluded, it is still dangerous to starting on your laurels, as other factors
can improve troublesome at a later stage.
Many problems in the world of computerized system derive from the lack of
understanding of some of the golden rules for implementation and operation by the
management.
References
C# Yellow book