synopsis for online hotel management for lucknow university

8/12/2019 Synopsis for online hotel management for LUCKNOW UNIVERSITY

1/35

ONLINE HOTEL MANAGEMENT SYNOPSIS 2012

Page 1

LUCKNOW PUBLIC COLLEGE OF PROFESSIONAL STUDIES

ACADEMIC YEAR 2011-12

SYNOPSIS

(ONLINE HOTEL MANAGEMENT SYSTEM)

Submitted By: Under Guidence Of:

Sumit Singh Rana Mr. L.S.Awasthi

(982106030) (H.O.D BCA)

SSuubbmmiitttteeddttootthheeLucknow Public College of Professional Studies,LLuucckknnooww..

IInnppaarrttiiaallffuullffiillllmmeennttoofftthheerreeqquuiirreemmeennttss

FFoorrtthheeaawwaarrddoofftthheeddeeggrreeee

BACHELOR OF COMPUTER APPLICATIONS (BCA)


2/35


Page 2

TITLE OF THE PROJECT

THE FIVE STAR HOTEL MANAGEMENT SYSTEM

(ONLINE HOTEL MANAGEMENT SYSTEM)

A standard web application using Asp.net

4.0 And SQL Server 2005


3/35


Page 3

INDEXS.no NAME OF THE TOPIC PAGE

NUMBER

1 INTRODUCTION 4

2 AIMS AND OBJECTIVES 4

3 SOFTWARE REQUIREMENT AND SPECIFICATION 5

4 SOFTWARE & HARDWARE REQUIREMENT & SPECIFICATION 10

5 SYETEM MODULES AND THEIR DESCRIPTION 13

6 DATA FLOW DIAGRAMS 15

7 E-R DIAGRAM 18

8 DATA FLOW DIAGRAM 21

9 GRANTT CHART 23

10 PERT CHART 24

11 DATA STRUCTURE 25

12 WW EE BB TT EE SS TT IINN GG 27

13 LL II MM II TT AA TT II OONN OO FF TT HH EE PP RROO JJ EE CC TT 27

14 AA DD VV AANN TT AA GG EE SS OO VV EE RR OO TT HH EE RR SS YY SS TT EE MM 28

15 FF UU TT UU RREE SS CC OO PP EE OO FF TT HH EE PP RROO JJ EE CC TT 34

16 CC OONN CC LL UU SS II OONN 35


4/35


Page 4

INTRODUCTION

One would think asking about the purpose and scope of hotel management software is purely

rhetorical. Looking at the results of a current representative survey among more than 10,000 German

hotel businesses conducted by The Business Target Group however, it is apparent that a fifth of all

surveyed hoteliers are asking themselves just that. To put it a different way: 20% are not utilizing any

software solution. Whether they are still using a reservation book or rely on a combination of

paperwork and some kind of computer program remains unanswered. It is a fact though those hotel

management systems with a wide range of functionalities substantially support hoteliers and staff in

all areas of the hotel. This in turn reduces everyones daily workload. Consequently, hotel staff has

more time to care for guests and hence will add to the guests satisfaction.

The hotel management system is an online portal to give information about the hotel, services

provided by the hotel and online booking if room is available. The main objective of on-line hotel

system is to utilize a fully automated system that not only saves lot of time but also gives fast results.

This system also provides different services for the customers and visitors also.

AIMS AND OBJECTIVES

Scope of this project is very broad in terms of manually taking exams:-

This can be used in small hotels as well as in big corporate hotels To completely automate the hotel system so as to reduce human intervention in order to bring

down.

To automate the process of hotel system such as room booking, room availability check,payment, finding customer etc.

To avoid maintenance of storage or the different books of track record on regular interval. To provide search facilities to the customer in hotel. For better management of available resources. For use of various modules based on authentication.


5/35


Page 5

To provide high security facilities for the use of officers. To restrict the repetition of the booking in different rooms. To increase speed of work so that the net results can be achieved instantly. It can be used anywhere, any time as it is a web based application (user location doesnt

matter).

There is no restriction that administrator has to be present when the customer books the room. The coding of software is well optimized and can be utilized in developing any other software

project with slight modification.

In future, this can be used as an information portal which gives information about theavailable room at hotel.

In future, this project can be used by different companies for the hotel automation.

SOFTWARE REQUIREMENT AND

SPECIFICATION

The software requirements specification is produced at the culmination of the analysis task. The

function and performance allocated to software as part of system engineering are refined by

establishing a complete information description a detailed functional and behavioral description, an

indications of performance requirements and design constraints, appropriate validation criteria and

other data pertinent to requirements.

1. Introduction

a. Purpose

b. Scope

c. Definition, Acronyms, Abbreviations

d. References

e. Developers Responsibilities Overview


6/35


Page 6

2. General Description

a. Product Functions Overview

b. User Characteristics

C. General Constraints

d. General Assumptions and Dependencies

3. Specific Requirements

a. Inputs and Outputs

b. Functional Requirements

c. External Interface Requirements

d. Performance Constraints

e. Design Constraints

(i) Software Constraints(ii) Hardware Constraints

4. Validation and Criteria

a. Performance bounds

b. Classes of tests

c. Expected Software response

d. Special Considerations

5. Acceptance Criteria

1. INTRODUCTION:

This is the requirements document for the project that will be used throughout the work. The system

to be developed is for collection and payment of the electricity bills based on the inputs given. This

document follows the IEEE standard for a requirement specification document, with some variations.

Purpose


7/35


Page 7

The purpose of this document is to describe the requirements of the website. It also describes the

interfaces for the system.

ScopeThis document is the only one that describes the requirements of the system. It is meant for use by the

developers and will be the basis for validating the final delivered system. Any changes made to the

requirements in the future have to go through a formal change approval process. The developer is

responsible for asking for clarifications, where necessary, and will not make any alterations without

the permission of the client.

Definitions, Acronyms, and AbbreviationsNot applicable.

ReferencesNot applicable.

Developers Responsibilities OverviewThe developer is responsible for

(i) Developing the system(ii) Installing the software on the clients hardware,(iii) Conducting any user training that might be needed for using the system, and(iv) Maintaining the system for a period of one year after installation.

2. GENERAL DESCRIPTION

Product Functions Overview:In our website provide easy application for loans- car, educational, home loans by just a

simple click and various queries of the customers can be solved with the use of feedback,

comments, etc.

User Characteristics:The main users of this system will be the Banking Department, maintenance department and the

people who are somewhat literate with computers and can use programs efficiently.

General Constraints


8/35


Page 8

The system should run on win 95/98/2000 servers or above.

General Assumptions and Dependencies:Not applicable.

3. SPECIFIC REQUIREMENTS:

Inputs and OutputsThe system has several inputs in form of data entry and several outputs in form of polls, reports etc.

Here also, the customer gets the desired loan information easily as well as can get those loans too.

Functional RequirementsIt present description of each function required to solve the problem. A processing narrative is

provided for each function, design constraints are stated and justified, performance characteristics are

stated, and one or more diagrams are included to graphically represent the overall structure of the

software and interplay among software functions and other system elements under this topic, the

functional working of the various modules where give the complete picture for the data flow from one

location to other.

External Interface RequirementsOnly one user command is required. The file name must be prompted by the system in status

bar.

Performance ConstraintsThe reports and loan forms should be printed in less than 1 minute.

Design Constraints:The system is to run under the WINDOWS operating system.

Validation criteriaProbably the most important section of a software requirements specification is validation Criteria.

The specification of validation criteria acts as an implicit review of all other requirements. The tests

must be conducted to validate function, performance and constraints.

4. ACCEPTANCE CRITERIA


9/35


Page 9

Before accepting the system, the developer must demonstrate that the system works on the course data

for the last 4 semesters. The developer will have to show through test cases that all conditions are

satisfied.


10/35


Page 10

SOFTWARE & HARDWARE REQUIREMENT &

SPECIFICATION

SOFTWARE REQUIREMENTS

Use of the software Name of the software

For client side scripting C#

For Styles HTML

For Creating database SQL Server 2005

Web Browser Netscape, IE 5.0/6.0,Mozilla

U I Design ASP .Net 3.5

HARDWARE REQUIREMENTS

Hardware Recommended Sufficient

Processor Pentium 4 Pentium 4.

RAM 1 GB 512 MB

Hard disk Space 10 GB 5 GB

Monitor 17 15

Mouse and keyboard Multimedia Normal


11/35


Page 11

1) SYSTEM DESIGN

System design is high-level strategy for solving the problem and building a solution. System

design includes decisions about the organization of a system into subsystem, the allocation of

subsystems to hardware and software components, and major conceptual and policy decisions

that form the framework for detailed design.

During the analysis phase of the project, the focus is on what needs to be done, independent

of how it is done. During design, decisions are made about how the problem will be solved,

first at a high level, then at increasingly detailed levels. System design is the first design stage

in which the basic approach to solving the problem is selected. During system design, theoverall structure and style decided. The system architecture is the overall organization of the

system into components called subsystems.

The architecture provides the context in which more detailed decisions are made in later

design stages. By making high-level decisions that apply to the entire system, the system

designer partitions the problem into subsystems so several designers can do threat further

work working independently or different subsystems.

INTERFACES

The following interfaces are used in this project:

USER INTERFACES

There are three type of user Interfaces, they are1. Simple User Interface

2. Administrator Interface

SIMPLE USER INTERFACE

This is the interface for simple users interacting with the website. Every interface is awebpage. This the interface for unregistered users .The interface starts with the Home


12/35


Page 12

page. This type of user can navigate the whole site .She/he can see all static pages that are

providing information about hotels work and product detail .

But this user can not interact with company online but

he/she can request for room by filing a form. This can be done by filling the registration

form available on the site..

ADMINISTRATORS INTERFACE

This is the interface of administrator of the site, who keep track of the entire user

requirement and communicate them accordingly. Administrator s interface has many

options ,admin can see all details of the clients, List of their enquiries .After viewing the

enquiry he can send quotation to the user ,he can also send the room description to the

user. These all information will be stored in the users account, which can be seen by the

user after registering to the site.Hardware Interface

The Database and all application programs have to be stored on a database server and all

web pages have to be stored on a web server.

Software Interface

SQL SERVER 2005 software needs to be interfaced with this software, as it is an

dependent product.

FUNCTIONAL REQUIREMENTS

The site has two basic functional requirements. There is brief description about them in the

following subsections.

Requirements for User

The user should be able book a room. He will be inmformed by e-mail regarding the sdtatus of room booking On her/his web page ,she/he should be able to send enquiries regarding the room

booking of their need ,they can ask about any quries regarding the hotel .

She/he should be able to see the e-mail send by admin She/he should be able to see the their room detail


13/35


Page 13

Requirements for Administrator

Administrator should be able to login with Userid and Password. Should be able to see list and detail of all customers. Should be able to see the inquiries send by all users Should be able to response them accordingly. Should have the authority to change ,edit,or delete any information in the site and

any particular users information.

Should be able to add new customers information. Should be able to view the past records of all the customers.

SYSTEM MODULES AND THEIR DESCRIPTION

The modules are the basic building block of any system, they all combine together to make

the system complete. The major advantage of the modules that it became easy to analyse the

system and collecting them to form a complete system.If any error occoured in the system

during any phase then it became easy to debug the errors into the system. In the system onlinenews forum there are varios modules are used which are the backbone of the system they are

given as follows-

Login Registration Administrator Room Booking Room management Customer and Room Management Feedback

Login

In this module all the login process are defined. For login process the user should provide his

unique user id and password to the system, this id and password will match with id and

password saved into the database if it matches then the login process will complete and the

session is provided to the user to interact with system called she\he is authenticated but in

case the id or the password will not match from the database then the system will not

authenticate the person.


14/35


Page 14

Registration

For the general user there is the facility of the registration for room booking it provides the

knowledge to the system about the person as the registration for the rooms are done by the

administrator himself. In the registration process there are some fields to fill by the user in the

web form these fields are related to the knowledge about the user. After the filling of thefields all the information are stored in the database for the future reference.

Administrator

The chief user is the administrator of the website. He has a unique id and password for login.

After the successful login he can manage the rooms or details of the customers. He can add,

delete, and modify the room and customer details. Besides from this he can block any

customers from his service and also can add new customers. He has the complete authority of

the news channel.

Room Booking

This is the module for the booking of the room. It provides a form to the admin in which the

categories are defined about the news as which form of data is. The customer used this form

to submit his details. After the completion of the data uploading it gives the confirmation

message to the user and saves the content to the database which then can be placed by the

admin to the database.

Room management

In this module the all the management about the room is done .It is only done by theadministrator of the hotel system. The admin can add the new customers on the hotel, he can

delete the old customers record from the front of the website and the changes into the

website can only be made by the administrator.

Room and Customer Management

This module also can be used only by the admin. He can extract all the information about the

room and the customer from the database and can add, delete or modify them. He can block

any room or customer from the service. It is same as room management module.

Feedback

This module is made for the feedback operation of the web administrator.


15/35


Page 15

DATA FLOW DIAGRAMS


16/35


Page 16

DATA FLOW DIAGRAM OF FEEDBACK


17/35


Page 17


18/35


Page 18

E-RDiagram

HOTEL

Room Booking

Contact Us


19/35


Page 19

ADMIN

HOTEL SYSTEM


20/35


Page 20

E-R Diagram


21/35


Page 21

DATA FLOW DIAGRAM


22/35


Page 22


23/35


Page 23

GRANTT CHART

Integrate and

testing

Design

Login/registration Module

25-03-2011 04-0

4-20

11

10-04-2011 15-04-20

11 28-04-20

11

Module

Prepare reports

Manage Security System

Write manual

Front End

Admin Module

Finish

Start


24/35


Page 24

PERT CHART

Write manual

Finish

Design

25-03-2011 30-04-2011

04-04-11

05-04-11

06-04-11

07-04-11

10-04-11

11-04-11

25-03-2011

15-3-2011Login/Registration Module

Work On Gallery

Admin (editor) control

Validation

StartFront End MOdule Integration and

testing


25/35


Page 25

DATA STRUCTURE

TABLE NAME: BOOKING

FIELD DATA TYPE

Name varchar(MAX)

Age int

Gender char(1)

Occupation varchar(MAX)

contact_no int

Address varchar(MAX)

City varchar(MAX)

country varchar(MAX)

Email varchar(MAX)

Identityproof varchar(MAX)

Chekindate varchar(MAX)

Checkoutdate varchar(MAX)

durationofstay int

Noofpeoplestaying int

Noofroomrequired int

Typesofroom varchar(MAX)

Modeofpayment varchar(MAX)

TABLE NAME: EMPLOGIN

FIELD DATA TYPE

EmployeeID varchar(MAX)

Password varchar(MAX)

TABLE NAME: FEEDBACK

FIELD DATA TYPE

NAME varchar(MAX)

E_MAIL varchar(MAX)


26/35


Page 26

COUNTRY varchar(MAX)

MESSAGES varchar(MAX)

TABLE NAME: ROOM BOOKING

FIELD DATA TYPE

Name varchar(MAX)

Age int

Gender char(1)

Occupation varchar(MAX)

contact_no int

Address varchar(MAX)

City varchar(MAX)

country varchar(MAX)

Email varchar(MAX)

Identityproof varchar(MAX)

Chekindate varchar(MAX)

Checkoutdate varchar(MAX)

durationofstay int

Noofpeoplestaying int

Noofroomrequired int

Typesofroom varchar(MAX)

Modeofpayment varchar(MAX)

TABLE NAME: ROOM TARIFF

FIELD DATA TYPE

ROOM TYPE varchar(MAX)

CURRENT TARIFF varchar(MAX)


27/35


Page 27

WW EE BB TT EE SS TT IINN GG

Software testing is a critical element of software quality assurance and represent the

ultimate review of specification design, coding, purpose of product testing is to verify and

validate various work products viz unit integrated unit, final product to ensure that they meet

their requirements.

TESTING OBJECTIVES

Basically testing is done for the following purposes.

Testing is a process of executing program with the intent of finding an error. A good test case is one that has a high probability of finding an as yet undiscovered

error.

A successful test case is one that uncovers an as yet undiscovered error.Our objective is to design test cases that systematically uncover different classes of error and do

so with a minimum amount of time and effort. This process has two parts:

PlanningThis involves writing and reviewing unit integration, functional, validation and acceptance test

plans.

ExecutionThis involves executing these test plans, measuring, collecting data and very fine if it meets the

quality criteria. Data collected is used to make appropriate changes in the plans related to

development and testing.


28/35


Page 28

The quality of a product or item can be achieved by ensuring that the product meets the

requirements by planning and conducting the following tests at various stages.

TYPES OF TESTING SOFTWARE

The main types of software testing are:

Component Testing:Starting from the bottom the first test level is Component Testing, sometimes called

Unit Testing. It involves checking that each feature specified in the Component Design has

been implemented in the component. In theory an independent tester should do this, but in

practice the developer usually does it, as they are the only people who understand how a

component works. The problem with a component is that it performs only a small part of the

functionality of a system, and it relies on co-operating with other parts of the system, which

may not have been built yet. To overcome this, the developer either builds, or uses specialsoftware to trick the component into believing it is working in a fully functional system.

Interface Testing:

As the components are constructed and tested they are then linked together to check if

they work with each other. It is fact that two components that have passed all their tests,

when connected to each other produce one new component full of faults. These tests can be

done by specialists, or by the developers.

Interface testing is not focused on what the components are doing but on how they

communicate with each other, as specified in the System Design. The system Design

defines relationship between components, and this involves stating:

1). what a component can expect from another component in terms of services.


29/35


Page 29

2). How these services will be asked for.

3). How they will be given.

4). How to handle non standard conditions, i.e. errors.

5). Tests are constructed to deal with each of these.

The tests are organized to check all the interfaces, until all the components have been built

and interfaced to each other producing the whole system.

System Testing:

Once the entire system has been built then it has to be tested against the System

Specification to check if it delivers the features required. It is still developer focused,

although specialist developers known as system testers are normally employed to do it.

In essence System testing is not about checking the individual parts of the design, but about

checking the system as a whole. In effect it is one giant component.

System testing can involve a number of specialist types of test to see if all the functional and

non-functional requirements have been met. In addition to functional requirements these may

include the following types of testing for the non-functional requirements:

1). Performance- Are the performance criteria met?

2). Volume- Can large volumes of information be handled?

3). Stress- Can peak volumes of information be handled?

4). Documentation- Is the documentation usable for the system?

5). Robustness- Does the system remain stable under adverse circumstances?


30/35


Page 30

There are many others, the needs for which are dictated by how the system is supposed to

perform.

Acceptance Testing:

Acceptance testing checks the system against the Requirements. It is similar to

system testing in that the whole system is checked but the important difference is the change

in focus:

System testing checks that the system that was specified has been delivered.

Acceptance testing checks that the system delivers what was requested. The customer and not

the developer should always do acceptance testing. The customer knows what is required

from the system to achieve value in the business and is the only person qualified to make that

judgment. The forms of tests may follow those in system testing, but at all times they are

informed by the business needs.

Release Testing

Even if a system meets all its requirements, there is still a case to be answered that it

will benefit the business. Release testing is about seeing if the new or changed system will

work in the existing business environment. Mainly this means the technical environment, and

checks concerns such as:

1). Does it affect any other systems running on the hardware?

2). is it compatible with other system?

3). Does it have acceptable performance under load?

These tests are usually run by the computer operations team in a business. It would appear

obvious that the operation team should be involved right from the start of a project to give

their opinion of a new system may have.


31/35


Page 31

Networking equipment and is capable of testing the performance and scalability of an end-to-

end solution, not just individual components. The lab is capable of generating a realistic load

of thousands of virtual users consisting of a mix of user profiles while simultaneously

exercising different portions of a dynamic Web application, based on real-world Web usage

patterns.

Testing tools can capture a variety of critical statistics, such as per-page user response times,

web interactions per second, transaction error rates and network traffic. The testing lab also

reports on empirical performance metrics of e-commerce products subjected to massive user

load, versus projecting results based on smaller load tests. This approach ensures that the data

reported provides an accurate depiction of the actual performance of the tested products.

Through arrangements with many of the leading web testing tool vendors, testing lab is

capable of generating complex scripts to be used in testing.

A typical scalability testing involves the following steps:

Consult with the client to determine the activities that will be exercised during testing; Code the test tool script to stress the website; Coordinate the enabling of appropriate server log files during the test; Consult with the client regarding a response time threshold value; Determine how many concurrent virtual users cause the response time to exceed the

threshold value; and

Calculate average response times under various load conditions.

CompatibilityTesting:

Testing lab examines a websites compatibility with multiple operating

system/browser combinations. Testing lab works closely with clients to develop a

compatibility-testing matrix that will include the relevant combinations to be tested.

Available configurations typically include Intel-based systems with Windows operating

systems and associated browsers as well as Macintosh systems and associated browsers.


32/35


Page 32

Testing lab will test the major features of the website during the compatibility testing, using

variousapproaches.

Testing lab works with clients to develop a test matrix that reflects the hardware and software

combinations to be tested and uses a variety of different editions and service packs of

operating environments in the testing. Our Testing lab has identified more than 70 possible

combinations of configurations. During testing, testing labs evaluates the ability of the

website to work in a satisfactory manner using both high- and low-speed connections. All

major functions of the website will be exercised by each configuration.

FunctionalityTesting:

Functionality in testing labs includes examination of website pages, menus, options, and

links to determine if the site functions as intended. Testing labs logs on to a client site and,

acting as multiple types of users, performs many functions associated with that site. Testing labs

should accomplish functionality testing by utilizing labs-developed test scripts, client-developed

test scripts, or some combination of both. Testing labs works with clients to determine the

appropriate operating system and browser combinations has to be tested. Typically, testing labs

exercises all site functions including links, search operations and responsiveness.

Usability Testing:

To conduct usability testing, testing labs assembles a focus group of testers with a

broad range of experience in personal computer and Internet usage. Working with its client,

all testing labs highly skilled Usability Testing Team will develop a questionnaire that

addresses the various aspects of the clients website. The questionnaire, along with the focus

group debriefing, is designed to elicit the responses and opinions of the members of the focus

group regarding the usability of the website. A final report will include testing labss expert

opinion as well as the individual responses and group consensus regarding the comparative

usability of the website.


33/35


Page 33

S.NO TEST CONDITION PRE REQUISITE DATA EXPECTED OUTPUT

1 Check for entry

in password

Login form comes

Enter Emp_id &password

Directed to admin Home

page

2 Wrong Entry Of UserName

,Passwrod

Enter username ,

Password

Redirect To Login

Failed Page3 Check for room

availibilityOpen Room Booking Page Booked room should be

colored

4 Search for customer Enter Customer Name OR

country

List of all the customer

with that name or country

5 Get room details Enter room number Get all the details about

that room

6 Prepare the bill Enter Rooom Number Will generate bill on

Payment Button ON_click()

event

7 Update room tariff Click on edit button

and update tariff

Tariff gets updated in

databse

8 Change password Enter Emp_id and new

passoword

Password get updated in

database

Limitation of the Project

There are several points in this project that have not been addressed.

Some of these are as follows:

1- Insufficient telecommunication bandwidth.2- A wide variety of tool& technologies as involved in this project that makes it

cumbersome.

3- Registration and hosting of website is must to access information from the website ofcompany.

4- Software development tools are still evolving and changing rapidly.5- Vendors may need special web services and other infrastructure, in addition to the

network severs.

6- Cost is high.


34/35


Page 34

7- Lack of touch and feel online.8- Project is heavy so need better system

Advantages over Other Systems

Internet as a business tool, no business can offered to ignore and guides the reader through

the various aspects of marketing on internet. In future, there will be no distinction between

dot com and traditional business just winners and losers. Internet

Strategies that focus on speed efficiency and customer experience will mark the winners.

Future scope of application summarized as follows

It provides global reach for providing hotel services It is convenience to Employees and customer It provides multimedia support for attractive presentations to advertisement of hotel

provide unique selling proportions

It provides fast customer services and feedback Room availability can be very easily viewed without pressing any button or running any

application or command.

It provides strong hotel communications strategies. It is helpful for creating hotel brand. Room management is extremely easy. Payment can be very easily calculated.


35/35


SCOPE OF FUTURE APPLICATION

This project can be used in the hotel after adding some more useful modules in the project for

which hotel are providing services.

Utmost care and back-up procedures must be established to ensure 100% successful

implementation of the computerized hotel system. In case of system failure, the organization

should be in a position to process the transaction with another organization or if the worst

comes to the worst, it should be in a position to complete it manually.

CONCLUSION

This project is designed to meet the requirements of Online Hotel Management. It has been

developed in ASP.net keeping in mind the specifications of the system.

For designing the system we have used simple data flow diagrams.

Overall the project teaches us the essential skills like:

-Using system analysis and design techniques like data flow diagram in designing the system.

-Understanding the database handling and query processing.

synopsis for online hotel management for lucknow university

Documents