Professional Documents
Culture Documents
UNITED
COLLEGE OF
ENGINNERING
A SYNOPSIS
AND REPORT ON
HOTEL
RESEARCH, MANAGEMENT
SYSTEM
ALLAHABAD SUBMITTED FOR
ACQUISITION OF
DEGREE B.TECH IN INFORMATION TECHNOLOGY
SUBMITTED TO:- SUBMITTED BY:-
Mr.Lalman Sir Mayank Mehrotra
Mohd. Ali Ansari
Neha Verma
CONTENTS
CERTIFICATE..............................................................................................................................1
ACKNOWLEDGEMENT.............................................................................................................2
ABSTRACT....................................................................................................................................3
1. Introduction..............................................................................................................................4
1.1 Purpose.............................................................................................................................4
1.2 Document Conventions....................................................................................................4
1.3 Intended Audience and Reading Suggestions..................................................................4
1.4 Product Scope..................................................................................................................5
2. Feasibility Study.......................................................................................................................6
2.1 Tests For Feasibility.........................................................................................................6
2.2 Feasibility Analysis Of Inventory Control Module.........................................................6
3. Overall Description..................................................................................................................9
3.1 Product Perspective..........................................................................................................9
3.2 Product Functions............................................................................................................9
3.3 User Classes and Characteristics....................................................................................11
3.4 Operating Environment..................................................................................................12
3.5 Design and Implementation Constraints........................................................................12
4. External Interface Requirements.........................................................................................13
4.1 Hardware Interfaces.......................................................................................................13
4.2 Software Interfaces........................................................................................................13
4.3 Communications Interfaces...........................................................................................13
5. System Features.....................................................................................................................14
5.1 Context Diagram............................................................................................................16
5.2 Entity-Relationship Diagram.........................................................................................20
6. Other Nonfunctional Requirements.....................................................................................21
6.1 Performance Requirements............................................................................................21
6.2 Safety Requirements......................................................................................................21
6.3 Security Requirements...................................................................................................21
6.4 Software Quality Attributes...........................................................................................21
7. Test Plan..................................................................................................................................23
7.1 Test Plan Identifier.........................................................................................................23
7.2 Introduction....................................................................................................................23
8. Test Cases................................................................................................................................26
REFERENCES.............................................................................................................................28
CERTIFICATE
Mr.Shashank Diwidi
Head Of Department,
Allahabad
ACKNOWLEDGEMENT
Apart from my efforts, the success of any project depends largely on the
encouragement and guidelines of many others. I take this opportunity to express
my gratitude to the people who have been instrumental in the successful
completion of this project.
I can‘t say thank you enough for their tremendous support and help. I feel
motivated and Encouraged every time I work on this project meeting. Without their
encouragement and Guidance this project would not have materialized.
The guidance and support received from the members who contributed and who are
contributing to this project are vital for the success of the project. I am grateful for
their constant support and efforts.ABSTRACT
The project has been designed in C#.NET technology and consists of a SQL server
which acts as the database for the project.
My motivation for the project came from my enthusiasm and strong urge to learn
C# and .NET which is one of the fastest growing technologies in today’s world.
The Hotel Management System project mainly consists of two types of users. The
customers who access the information provided by the website and the
administrator who modifies and updates the information.
All the data needed for the application is stored in the form of tables in the SQL
server 2000.
The report contains the details of all the tasks carried out during the entire software
development life cycle of the Hotel Management Project. This document depicts all
the details of the project .
1.INTRODUCTION
1.1 Purpose
Document Conventions
The document is prepared using Microsoft Word 2013 and has used the font
type 'Times New Roman'. The fixed font size that has been used to type this
document is 12pt with 1.5 line spacing. It has used the bold property to set
the headings of the document. Use case scenario is written according to
Alistair Cockburn’s template.UML diagrams have been created according to
UML 2.0 standards. Standard IEEE template is the template used to organize
the appearance of the document and its flow.
The intended audience of this document would be owner and specific employees
like Manager and Receptionist of Hotel Gayana, and project team with the objective
to refer and analyze the information. The SRS document can be used in any case
regarding the requirements of the project and the solutions that have been taken.
The document would final provide a clear idea about the system that is building.
1. Overall Description
2. System Features
The objectives of the automated Hotel Management System is to simplify the day to
day processes of the hotel. The system will be able to handle many services to take
care of all customers in a quick manner. As a solution to the large amount of file
handling happening at the hotel, this software will be used to overcome those
drawbacks. Safety, easiness of using and most importantly the efficiency of
information retrieval are some benefits the development team going to present with
this system. The system should be user appropriate, easy to use, provide easy
recovery of errors and have an overall end user high subjective satisfaction.
2.FEASIBILITY STUDY
Feasibility is the measure of how beneficial or practical the development of
information system will be to an organization.
Whether the identified user needs may be satisfied using current software
and hardware technologies.
The study will decide if the proposed system will be cost-effective and if it
can be developed given existing budgetary constraints.
Feasibility study should be cheap and quick.
The result should inform the decision of whether to go ahead with a more
detailed analysis.
1. Operational Feasibility:
It is a measure of how well the solution will work in the organization. It is also
a measure of how people feel about the system/process. Operational
feasibility is people oriented.
2. Technical Feasibility:
3. Schedule Feasibility:
4. Economic Feasibility:
5. Implementation Feasibility:
Operational Feasibility:
Ans. Yes, the problem is off course worth solving because the system existing today
which is manual may have certain time consuming & less efficient as compared to
computerized system, eliminate paper work and reduce man power so, the problem
is worth solving.
1) Performance:-
From Our module point of view performance is better than manual system
because we can easily find the status information and also easily adds, modify
the records.
2) Information:-
Our module gives the information to right person at right time because it only
access by the authorized person and it gives the right information at right time.
3) Efficiency:-
Our module efficiency is better than manual system because of mainly all the
resources is used in this module.
4) Control:-
Our module is developed for the Planning Cell department. An admin gives
the rites to the operators and according to the rites operator controls the
system so, from control point of view this system is very good.
5) Economic:-
Economic is totally depends on the extra resources we used in the project or
module. In our module we also used extra resources.
6) Service:-
In our module all the things are most of user friendly so on confusion with the
user to use the system.
Technical Feasibility:
To check weather the module technically Feasible or not we have to give the
following three questions answers.
Ans. The proposed website is definitely practical as we have all the resources
available. Also building up this module requires the basic/ minimum amount of SRS
that are easily available. As the analysis part has been carried out, taking into
account the requirements of a module the proposed system is extremely efficient
and practical.
Ans. Looking into the SRS chart we can see that we posses all the h/w and s/w
requirements. Also the technology used is easily available and deployed all around
the world.
Ans. Well, the module once developed can be easily handled by a non-technical
person. So a technically sound expert is not required here. Hence this problem does
not arise at all.
Economical Feasibility:
As this not begins a conversion of the present module into and rather begins
creating a new module from scratch, the cost of the module includes cost of the
module development; implementation and it not included the maintenance.
Schedule Feasibility:
This feasibility use for the complete project within allotted time for it we use all
resources which is given by the company.
Schedule feasibility deals with the deadline offered to complete the project. He
procedure of submitting the project report at regular interval period are described in
our project profile is four months so we will complete our report and project within
given time. So, this totally in schedule feasible.
OVERALL DESCRIPTION
3.1 Product Perspective
The Hotel Management System is a new self-contained software product which will
be produced by the project team in order to overcome the problems that have
occurred due to the current manual system. The newly introduced system will
provide an easy access to the system and it will contain user friendly functions with
attractive interfaces. The system will give better options for the problem of handling
large scale of physical file system, for the errors occurring in calculations and all the
other required tasks that has been specified by the client. The final outcome of this
project will increase the efficiency of almost all the tasks done at the Hotel in a
much convenient manner.
Make Reservations
Search Rooms
Add Payment
Issue Bills
Manage Guest (Add, Update Guest)
Manage Room Details (Add, Update, Delete)
Manage Staff (Add, Update, Delete, View)
Manage Inventory (Add, Edit, Delete)
Set Rates
Retrieve Reports (Staff payment, Income)
Manage Users (Add, Update, Delete)
Taking Backups
E-mail notifications
View Reports
Department Details
Insert
Department Details
Update
Owner
Delete
Department Details
Room/Staff/InventoryDetails
Add
Room/Staff/InventoryDetails
Update
Room/Staff/InventoryDetails
Delete
Manager
GuestDetails
Add
GuestDetails
Update
GuestDetails
Delete
Rooms
Search
Receptionist Reservations
Make
Bill
Issue
User Classes
There are three user levels in Hotel Management System of Hotel Gayana.
I. Owner
II. Manager
III. Receptionist
Owner:
Hotel owner has the privilege of Monitoring and authorization of all the tasks handle
by the system. He can access every function performed by the system. Owner of
the company as well as the system can access to the administration panel which is
consider the core of the system. As the main authorized person of the company
owner gets the ability to manage the other users including their user levels and
privileges. Taking backups of the system and restoring system can also be done by
the Owner. Meanwhile he will be able to take all the kinds of reports available in the
system. As the owner of the system and the company he has the power to set room
rates as well. Hotel owner has the sole right of deleting a staff member from the
system database.
Manager:
As a hotel receptionist, he or her role will be to attain the goals of bookings and to
ensure that all guests are treated with a high standard of customer service.
Hierarchically receptionist role has the least accessibility to the system functions.
Receptionist plays the boundary role of the system .He or she can perform limited
functions such as registering new guest to the system, make reservations, Sending
e-mail reminders to clients for booking confirmation. Management of hotel will
prefer to hire receptionist who have a good standard of general education and
possibly in subjects such as English, math and IT.
Hardware:-
1. Operating System Supports all known operating systems, such as Windows,
Linux
2. Computer 512MB+ RAM, monitor with minimum resolution of 1024x768,
keyboard, and mouse
3. Hard Drive should be in NTFS file-system formatted with minimum 10 GB of
free space
4. A Laser printer will need to be used to print these reports and notes
Software:-
1. Software is designed to run on any platform above Microsoft Windows 7
(32bit).
2. Microsoft .NET Frameworks 4.0 or above.
3. Microsoft SQL Server Management Studio Express 2010.
3.5 Design and Implementation Constraints
Software development crew provides their best effort in developing the system. In
order to maintain the reliability and durability of system, some design and
implementation constraints are applied. Availability of an android app for hotel
management system could make the system portable but due to time constraint it
is not possible. System will need a minimum memory of 512MB. But it is
recommended to have a memory of 1GB.When designing interfaces of system, we
had the capability of work with new tools such as Dev Express. Considering the
client’s budget we decided to create those interfaces in a simple realistic manner
using affordable technology.
PROCESS SYMBOL:
A process receives input data and produces output that has a different content,
form ,or both. It contain business logic also called Business rules that transform the
data and produce the required results.Process name is the function name and
consists of a verb followed by a singular noun.
____________________
____________________
EXTERNAL ENTITY:
An external entity is a person, department, outside organization or other
information system that provides data to the system or receives output from the
system. It shows the boundaries or terminators of system. They act as either source
or sink. An external entity must be connected to a process by a data flow.
5.1 CONTEXT DIAGRAM
It is a top-level view of the entire information system. It does not shows any data
stores because it is internal to the system.
Conventions:
1. Each context diagram must fit on one page.
2. The process name in the context diagram should be the name of the information
system.
In DFD processing logic is divided into smaller units known as functional primitive. It
is a process that consists of a single function that is not exploded forth.
CONTEXT LEVEL DIAGRAM
FIRST LEVEL DFD
SECOND LEVEL DFD
3.
5.2 ENTITY-RELATIONSHIP DIAGRAM
6.OTHER NON-FUNCTIONAL REQUIREMENTS
There are several user levels in hotel management system, Access to the various
subsystems will be protected by a user log in screen that requires a user name and
password. This gives different views and accessible functions of user levels through
the system. Maintaining backups ensure the system database security. System can
be restoring in any case of emergency.
7.2 INTRODUCTION
The main purpose of the test plan for the Hotel Management System is to
discuss the testing details of the use cases of the Hotel Management
System. The software project test plan also describes the objective, scope
and approach of the software testing effort for the Hotel Management
System project. The test plan for the Hotel Management System also
indicates the personnel responsible for each task and also specifies the risks
associated with the test plan.
7.2.1OBJECTIVES
The main objectives of the test plan for the Hotel Management System are as
follows:
7.2.2DEFINITIONS
The following are some of the terms and definitions that are related to the test plan
of the Hotel Management System:
1 TEST ITEMS
This section of the test plan lists all the items of the Hotel Management System
project that will be tested:
Login
Generate bill
Register
2 APPROACH
This section of the test plan describes the overall approach for testing the Hotel
Management System project. The approach followed for testing the Hotel
Management System ensures that the major features of the project are adequately
tested. The testing would be carried out on the Hotel Management System while
logging into the system as a Hotel manager or a super admin of the system.
1 UNIT TESTING
The Unit Testing is a test that tests each single module of the software to check for
errors.
This is mainly done to discover errors in the code of the Hotel Management System.
The main goal of the unit testing would be to isolate each part of the program and
to check the correctness of the code. In the case of the Hotel Management System,
all the forms and the C# classes will be tested. There are many benefits for this unit
testing:
2 INTEGRATION TESTING
In Integration Testing, the individual software modules are combined and tested as a
whole unit. The integration testing generally follows unit testing where each module
is tested as a separate unit. The main purpose of the integration testing is to test
the functional and performance requirements on the major items of the project.
All the modules of the project developed individually would be combined together
and
3 REGRESSION TESTING
The Regression Testing is generally done whenever modifications are made to the
source
code of a project. The Regression Testing can also be defined as the process of
testing changes made to the computer program and also makes sure that the older
programming still works with the new changes.
So, before any new version of a software product is released, the old test cases for
the
project will be run against the software with the changes made, to make sure that
the old
4 ACCEPTANCE TESTING
This testing is generally performed when the project is nearing its end. This test
mainly
qualifies the project and decides if it will be accepted by the users of the system.
The users or the
5 SYSTEM TESTING
The system testing is mainly done on the whole integrated system to make sure
that the
project that has been developed meets all the requirements. The test cases for the
system testing will be the combination of unit and integration tests.
8.TEST CASES
The following are the test cases for the Hotel Management System:
Incorrect Input: Wrong format entered in the input fields for the
registration page.
Pass Criteria: An appropriate message should be generated to the
user saying that he has entered the wrong format in the specific input
field.
Correct Input: The correct input would a correct format entered by
the user into the input fields of the registration page.
Pass Criteria: The pass criteria for Hotel Management System.
Incorrect Input: The data fields left out empty in the registration
page.
Pass Criteria: An error message should be generated to the user
saying that he has to fill out those fields in order to be registered into
the system.
Correct Input: The correct input in this case, would be that the
customer would enter the data in all the fields in the registration form.
Pass Criteria: The pass criteria for the system would be that it
accepts all the new user details and then registers the user and helps
him log into the system.
SUSPENSION CRITERIA
Testing for all the dependant features will be suspended if a test case fails. The
failed test
case will be logged onto the test log which contains the description for the error.
RESUMPTION REQUIREMENT
The test cases which are not dependant on the case where the bug is reported will
be
executed in parallel with the bug fixing. Once the failed test case has been taken
note of and has been identified and fixed then the testing for the failed test case will
resume.
TEST DELIVERABLES
The following documents will be produced after the testing phase for the Hotel
Management System has been completed.
Test Plan
Test Cases
Test Log
REFERENCES
The following references have been used by me, during all the phases of the
project:
http://www.tutorialspoint.com/csharp/index.htm
http://msdn.microsoft.com/en-
us/library/kx37x362(v=vs.80).aspx
SQL Server 2012 download - http://www.microsoft.com/en-
in/download/details.aspx?id=35575
http://www.c-sharpcorner.com/
http://en.wikibooks.org/wiki/C_Sharp_Programming