15

UNITED
COLLEGE OF
ENGINNERING
AND
RESEARCH,
ALLAHABAD

A SYNOPSIS
REPORT ON
HOTEL
MANAGEMENT
SYSTEM
SUBMITTED FOR
ACQUISITION OF
DEGREE B.TECH IN INFORMATION TECHNOLOGY

SUBMITTED TO:Mr.Lalman Sir

SUBMITTED BY: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

This is to certify that the project report entitled HOTEL MANAGEMENT is an

authentic record of work carried out by MOHD. ALI ANSARI (1201013044),
MAYANK MEHROTRA (1201013043) and NEHA VERMA (1201013047) at
UNITED COLLEGE OF ENGINEERING AND RESEARCH, ALLAHABAD under the
guidance of the entire faculty of the department of Computer Science and
Information Technology and Mr.Lalman Sir who has contributed and supported us
for
the
project.
This project work is submitted in the partial fulfillment of the requirements for the
award of the degree of BECHELOR OF TECHNOLOGY in COMPUTER SCIENCE &
ENGINEERING of the UTTAR PRADESH TECHNICAL UNIVERSITY, LUCKNOW
during the academic year 2014-15.

Mr.Shashank Diwidi
Head Of Department,
Deptt. of Information Technology,
United College Of Engineering And Research,
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 would like to show my greatest appreciation to Mr.Lalman Sir, Senior Lecturer

at United College Of Engineering And Technology, Allahabad and the entire
faculty of the department of Computer Science and Information Technology from
where we have learnt the basics of Computer Science and whose informal
discussions and able guidance became light for us in the entire duration of this
work.

I cant 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 objective of the project is to design Hotel Management application which

enables the manager to keep the record of the hotel and the customers.

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 todays 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

The Software Requirements Specification (SRS) will provide a detailed

description of the
requirements for the Hotel Management System (HMS).
This SRS will allow for a complete understanding of what is to be expected
from the newly introduced system which is to be constructed. The clear
understanding of the system and its functionality will allow for the correct
software to be developed for the end user and will be used for the
development of the future stages of the project. This SRS will provide the
foundation for the project. From this SRS, the Hotel Management System can
be designed, constructed, and finally tested.
This SRS will be used by the system development team which is constructing
the HMS and the hotel end users. The Project team will use the SRS to fully
understand the expectations of this HMS to construct the appropriate
software. The hotel end users will be able to use this SRS as a test to see
if the constructing team will be constructing the system to their
expectations. If it is not to their expectations the end users can specify how
it is not to their liking and the team will change the SRS to fit the end users
needs.

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 Cockburns 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.

1.3

Intended Audience and Reading Suggestions

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.
Brief outline of the document is,
1. Overall Description
2. System Features
3. External Interface Requirements
4. Non Functional Requirements

1.4

Product Scope

The introducing software, Hotel Management System which is going to be

implemented for Hotel Gayana will automate the major operations of the hotel. The
Reservation System is to keep track in room and hall reservation and check
availability. The Room Management System is for manage all room types room
services. The Inventory Control System will keep track in all inventories of the hotel
and guest details will handled by guest management. Administration department
will monitor the all .There is three End Users for HMS. The End Users are Owner,
Manager and Receptionist. Owner can access to all system functionalities without
any restrictions. Manager can access to all system functionalities with limited
restrictions. Receptionist can only access to the Reservation management section.
To keep restrictions for each End User levels HMS can create different Login
functions.

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.
The feasibility study involves following main criteria:

2.1

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.

TESTS FOR FEASIBILITY

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:
It is a measure of the practicality of specific technical solution and the
availability of
technical resources and expertise. Technical feasibility is
computer oriented.
3. Schedule Feasibility:
It is a measure of how reasonable the web application timetable is.
4. Economic Feasibility:
It is a measure of the cost-effectiveness of a web application or solution. This
is often called
a cost-benefit analysis. Economic feasibility deals with the costs
and benefits of the information system.
5. Implementation Feasibility:
It is a measure of the how application will run efficiently.

2.2

FEASIBILITY
MODULE

ANALYSIS

OF

INVENTORY

CONTROL

Operational Feasibility:
Operational feasibility is people oriented. Some question arises in the operational
feasibility we discuss on this question.

Q1. Is the problem worth solving or will the solution to the problem work?
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.

Q1. Is the proposed website practical?

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.

Q2. Do we currently possess the necessary Technology?

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.

Q3. Do we possess the necessary technical expertise?

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.

3.2

Product Functions

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

Reports

View

Department Details

Insert

Department Details

Update
Owner

Delete
Department Details
Room/Staff/InventoryDetails

Add
Update
Delete

Room/Staff/InventoryDetails
Room/Staff/InventoryDetails

Manager

Add
Update
Delete
Search
Receptionist
Make
Issue

GuestDetails
GuestDetails
GuestDetails
Rooms
Reservations
Bill

Figure 2.1.1 High Level Architecture

3.3

User Classes and Characteristics

User Classes

There are three user levels in Hotel Management System of Hotel Gayana.

I.
II.
III.

Owner
Manager
Receptionist

Characteristics of User Classes

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:

Manager is responsible for managing resources available in hotel management

system. Manager also has most of the privileges mentioned above except the things
regarding the payment handling. The reason for using a Manager is to reduce the
work load done by the owner that cannot be assigned to the receptionist, as those
tasks seem much responsible. The user level, Manager has the authority to take all
the reports available in the system but here also except the reports related to
financial stuff, hotel income. Manager has other abilities that receptionist, user level
has. Such as, adding new staff member to the system, Modifying them or removing
them, Adding new guests to the system, Modifying them and removing them from
the system, Adding new inventory to the system, Modifying them and removing
them. Adding new room types to the system, modifying them and removing them

Receptionist:

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.

3.4

Operating Environment

Hardware and software requirements are:

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
clients budget we decided to create those interfaces in a simple realistic manner
using affordable technology.

4.EXTERNAL INTERFACE REQUIREMENTS

4.1 Hardware Interfaces
Section 2.4 includes the requirements of the desktop computer where the
system going to be installed. A specific computer must match with the above
mentioned requirements in order to gain the maximum benefits from the
system in an efficient manner.
Reservation alerts will be sent to the one of the member of hotel staff as an
e-mail notification. So there is a need of broadband internet connection.
Client should able to keep a stable internet connection.
A laser printer will be needed when printing bills and several reports.

4.2 Software Interfaces

The computer this software going to be install need to have Windows Operating
System equal or above, Windows 7. On that Windows platform .Net 4.0 will be
installed and that will be the platform the particular software will be run. There will
be an ADO.NET data transmission with the Microsoft SQL Server Management Studio
Express 2010 R2 edition that will be installed in the same computer.

4.3 Communication Interface

When a specific reservation reserved at the same time an e-mail notification
will be sent to both relevant staff members e-mail account and guests
account. Guest will be notified in the check-out date. To achieve that
functionality, it requires having a stable internet connection. Mostly a
broadband connection with the clients computer will provide the efficient
service.

5.SYSTEM FEATURES
When the system is completely developed and submitted to the client, few
sessions will be required to make the users of the system understand about
the functionality of it and some time to adapt to the system. After those
sessions, its required that a member from the development team should
spend sometime in the system background for an agreed time period. That
time period will be used in identifying new bugs that could not be reached in
the earlier phases of the development process.
Client should have a valid e-mail account in order to receive reservation email notifications.

DATA DIAGRAM SYMBOL:

It yields visual model of the Information System.It shows how data moves through
an Information System but does not show program logic or processing steps. DFD
shows what the system does, not how it works it.
We use Gane and Sarson Symbol set for drawing DFDs.

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.

DATA FLOW SYMBOL:

A data flow symbol is a path for data to move from one part of the information
system to another. A data flow in a DFD represents one or more data items. A data
flow name consists of a singular noun and an adjective, if needed.A data flow must
have a process at its either end.

DIVERGING DATA FLOW:

It is a data flow in which the same travels to 2 or more different locations.

DATA STORE SYMBOL:

A data store or data repository in a DFD represent a situation in which the system
must retain data because one or more processes need to use the stored data at a
later time, A data store name is a plural name consisting of a noun and adjectives, if
needed. A data store must be connected to a process with a data flow.

____________________

____________________

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.
3. Use unique names within each set of symbols.
4. Do not cross lines. If it occurs then avoid it by duplicating an external entity or
data store.
5. Use unique reference number for each process symbol.

Diagram 0 or exploded view of context diagram. It zooms in on the context diagram

and shows major processes, data flows and data stores. The process numbers do
not suggest that the processes are accomplished in a sequential order, it is also
called partitioned or decomposed view of process 0.

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

6.1 Performance Requirements
Performance requirements define acceptable response times for system
functionality. Although the system is developed suiting for the least system
performances, the performance of the system will highly depend on the
performance of the hardware and software components of the installing computer.
When consider about the timing relationships of the system the load time for user
interface screens shall take no longer than two seconds. It makes fast access to
system functions. The log in information shall be verified within five seconds causes
efficiency of the system. Returning query results within five seconds makes search
function more accurate.

6.2

Safety 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.

6.3

Security Requirements

Customer Service Representatives and Managers and owner will be able to

log in to the Hotel Management System. Customer Service Representatives
will have access to the Reservation/Booking and subsystems. Managers will
have access to the Management subsystem as well as the
Reservation/Booking subsystems. Owner has the maximum privilege to all
subsystems. Access to the various subsystems will be protected by a user log
in screen that requires a user name and password.

6.4 Software Quality Attributes

Availability: The system shall be available during normal hotel

operating hours
Correctness: The extent to which program satisfies specifications,
fulfills users mission objectives
Efficiency: How much less number of resources and time are required
to achieve a particular task through the system.
Flexibility: Ability to add new features to the system and handle them
conveniently.

Integrity: How the system would insecure the information in the system
and how it avoids the data losses. Referential integrity in database
tables and interfaces
Maintainability: How easy is to keep the system as it is and correct
defects with making changes.
Portability: The Hotel Management System shall run in any Microsoft
Windows environment
Reliability: Specify the factors required to establish the required
reliability of the software system at time of delivery. Mean time
between failures and mean time to recovery
Reusability: What is the ability to use the available components of the
system in other systems as well.
Testability: Effort needed to test to ensure performs as intended.
Usability: How easily a person can be taken the benefits of the system
and the user friendliness.
Robustness: Strength of the system to handle system functions
accurately and maintain the database without facing to unexpected
failures
Maintainability: What design, coding standards must be adhered to
exclusions created.

7.TEST PLAN
7.1

TEST PLAN IDENTIFIER

Hotel Management System

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:

To identify the features of the system that will be tested.

To identify and define all the activities necessary to prepare for and
conduct the testing process on the Hotel Management System.
To discuss the testing techniques being used to test the Hotel
Management System.

7.2.2DEFINITIONS
The following are some of the terms and definitions that are related to the test plan
of the Hotel Management System:

Pass/Fail criteria: Decision rules that are used to determine

whether a software item passes or fails a test.

Test: A collection of one or more test cases.
Test Item: A software item that is an objective of testing.
Test Plan: A document describing the scope, approach, resources
and schedule of the intended testing activities.

Test Summary Report: A document summarizing the testing

activities and results.

Testing: The process of analyzing a software item to detect the
differences between the existing and required conditions.

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:
The unit testing facilitates change in the code.
It allows testing to be done in a bottom up fashion.

At the same time, unit testing has some disadvantages such as, it might not identify
each
and every error in the system.

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
tested as a whole system in the integration testing.

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
functionalities of the project still work.

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
customers of the project are responsible for the test.

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:

8.1

Incorrect Input: Incorrect username.

Pass Criteria: An appropriate message should be generated to
indicate that an invalid username has been typed.
Correct Input: The correct input would be a valid username of the
user and a correct password associated with the username which he
uses to log in.

8.2

TEST CASE 2 USER REGISTRATION

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.

8.3

TEST CASE 1 USER LOGIN

TEST CASE 3 USER REGISTRATION

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.

8.4

TEST CASE 4 GENERATE BILL

Incorrect Input: Incorrect input in this case, would be incorrect

search criteria entered or incorrect format of data entered into the data
entry fields of the generate bill page.
Pass criteria: A message has to be generated to the user indicating
the wrong entry that he has made in the fields.
Correct Input: A correct input would be entering the data into the
data entry fields in a correct format.
Pass Criteria: The pass criteria for this test case would be that data
will be added to the database and bill will be generated.

PASS OR FAIL CRITERIA

The test cases executed on the Hotel Management System will pass if they meet
the specific requirements mentioned in the Vision document of the project. A test
case is said to fail, if the desired functionality is not satisfied by 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/enus/library/kx37x362(v=vs.80).aspx
SQL Server 2012 download - http://www.microsoft.com/enin/download/details.aspx?id=35575
http://www.c-sharpcorner.com/
http://en.wikibooks.org/wiki/C_Sharp_Programming