Online Hotel Mngt

8/13/2019 Online Hotel Mngt

1/71

ONLINE HOTEL MANAGEMENT

Mini Project Report

On


2010

In the partial fulfillment of

4thsemester of

MCA

By

Priyesh Kumar

Regn_no:95580034

DEPARTMENT ! "MP#TER APP$%"AT%N&

""'%N#N%(ER&%T) ! &"%EN"E AND TE"'N$*)""'%N+,,

PRIYESH KUMAR, DCA, CUSAT, Kochi-221


2/71


CERTIFICATE

2010

C O C H I N U N I V E R S I T Y O F S C I E N C E A N D T E C H NO L O G Y COCHIN-22

Ti! i! to certi"# t$t te project report entit%e& 'ONLINE HOTEL

MANAGEMENT( i! $ )on$"i&e recor& o" te *or+ &one )# PRIYESH,UMAR Re.no/01133456 A! Te M/C/A 5TH !e7e!ter Mini project//

JUNE 2010

Internal Examiner Head of the Department

Submitted on:



3/71

ONLINE HOTEL MANAGEMENT2010

CONTENTS

AC,NO8LEDGEMENT

SYNOPSIS

9/ INTRODUCTION

9/9/ O:;ECTIVE

9/2/PRO:LEM DEFINITION

9/4/SYSTEM ENVIRONMENT

2/ SOFT8ARE / AUDIT

2// SOFT8ARE DEVELOPMENT PROCESS

2/0/ DOCUMENT REVIE8

2/93 TESTING

4/ SYSTEM ANALYSIS

4/9SYSTEM STUDY

4/2FEASI:ILITY STUDY


3


4/71


5/ SOFT8ARE RE


5/71


AC,NO8LEDGEMENTS

I have a great pleasure in acknowledging the help given byvarious individuals throughout the project work. This project isitself an acknowledgement to the inspiration, drive and technicalassistance contributed by many individuals.

I express my sincere and heartfelt gratitude to M r /, / V/Pr$7 o & BHead of the Department of omputer!pplications, for being helpful and co"operative during theperiod of the project.

I also express my deep gratitude to the faculty membersM!/M $ %$ti B M r/ : / , $ n n $ n,M r/ A / S ree + @ 7 $ rBMr / Ar@

nS i r $ n & o @r o t er " $c @ % t i e ! for their valuable guidance,timely suggestions and help in the completion of this miniproject.

I extend my sincere thanks to all the non"teaching staff forproviding the necessary facilities and help. #ithout the supportof anyone of them this project would not have been a reality.

$incerely

PR I YE S H , UMARRE G N N O - 01 1 3 3 4 5


6/71



7/71


SYNO PSI S

O:;ECTIVE-

The entral objective of %H& is to provide %nline facility for booking

Hotel. In previous system ' i.e &anual $ystem ( , person has to go to theHotel for booking, en)uiry etc. This was the fully time consuming,expensive etc. Through this product, person can book the Hotel by sittingin the *oom.

DURATION- + &onths

TOOLS USED FOR DEVELOPING-

L $ n.@$.e " -!!

D $t$) $! e " &y $/0

Tec n o%o .# " -$1

8e) S e r er " !1!H2 T%&!T 3.4

ID E " 52T62!5$


6


8/71


11..ININTTRROODDUUCTCTIIOONN



9/71


9/ INTR O D U C TI ON

The website which deals with the easy online reservation in an hotel with

high security and is known as ONLINE O!EL MANA"EMEN! # !his

1roject 1rovides solution regarding the hotel reservation problems of

users. 7ser can easily check availability of room 8 if room is available ,

then he9she can get room in the hotel. 6y the use of Internet the user can

save so much time for his reservation.

The project consists of two modules:"A&7ini!tr$tor 7o&@%e $n& U!er 7o&@%e/

A & 7 i n i!t r $ tor M o & @ % e

an 0ogin

heck ustomer details

heck *oom details

7pdate *oom $tatus

U!er M o&@%e

heck room !vailability

;ill *eservation ;orm


10/71


11/71


6ack 2nd : &ys)l

TOOLSB TECHNI


12/71


-ava is portable architecture neutral that is java programs once

compiled can be executed on any machine that is enabled.

-ava is distributed in its approach and used for Internet

programming.

-ava is robust, secured, high performing and dynamic in nature.

-ava supports multithreading. There for different parts of the

program can be executed at the same time.

Oerie* o" ;SP

The -$1 technology will be used to interface HT&0 with -ava. The -$1

technology provides a seamless connection with -ava and presents an

easy to use, -ava"like programming constructs that can be scripted within

HT&0 files. -ava $erver 1ages is a technology for developing web pages

that include dynamic content. ! -$1 page contains standard markup

language elements, such as HT&0 tags, just like a regular web page. !

-$1 page also contains special -$1 elements that allow the server to insertdynamic content in the web page.

A D V AN T AG E S O F ; S P

-$1 supports both scripting and element"based dynamic content.

!llows developing custom tag libraries.

-$1 pages are precompiled for efficient server processing.

-$1 pages can be used in combination with servlets that handle the

business logic.

High $ecurity.

an run on any ->22 compatible web $erver.

2010

PRIYESH KUMAR, DCA, CUSAT, Kochi-22 11


13/71


It can run on any %$ that have ->22 compatible web server.

-$1 separates the dynamic and static parts.

High /uality tool supports.

-$1 supports 5 tier !pplication.

#rite %nce, *un 2verywhere.

-$1 is vender 5eutral.

Oerie* o" ;$$ Script

-ava script is a general purpose, prototype based, object orientedscripting language developed jointly by sun and 5etscape and is meant

for the ###. -ava script borrows most of its syntax from java but alsoinherits from awk and perl, with some indirect influence from self in itsobject prototype system.

-ava $cript is almost as easy to learn as HT&0 and it can be includeddirectly in HT&0 documents. -ava $cript was developed independently of

java. -ava script is a high level scripting language that does not dependon or expose particular machine representations or operating systemservices.

F E A T U R E S -ava script is embedded into HT&0 documents and is executed with

in them.

-ava script is browser dependent.

-ava$cript is an interpreted language that can be interpreted by the

browser at run time.

-ava script is loosely typed language

-ava script is an object"based language.

2010



14/71


-ava script is an 2vent"Driven language and supports event

handlers to specify the functionality of a button.

The $truts framework provides the flexibility to develop the much less

coupled applications. It generali?es and strictly implements &"model

iew ontroller !rchitecture. That is the basic need of our architecture.

Oerie* o" Ap$ce To7c$t

!pache Tomcat is a servlet container developed by the !pache $oftware;oundation '!$;(. Tomcat implements the -ava $ervlet and the-ava$erver 1ages '-$1( specifications from $un &icrosystems, and

provides a Gpure -avaG HTT1 web server environment for -ava code torun.Tomcat should not be confused with the !pache web server, which is a implementation of an HTT1 web server these two web servers are notbundled together. !pache Tomcat includes tools for configuration andmanagement, but can also be configured by editing C&0 configuration

files.

Oerie* o" M#S


15/71


2.SOFT8 A RE


16/71


>.=PURPOSE

!he purpose of this plan is to define the $Customer %elationship

Management&

'oftware (uality Assurance )'(A* organi+ation, '(A tasksand responsibilities provide reference documents and guidelines toperform the $/! activities provide the standards, practices andconventions used in carrying out $/! activities and provide the tools,techni)ues, and methodologies to support $/! activities, and $/!reporting.

>.>SCOPE

The scope of this document is to outline all procedures, techni)ues and

tools to be used for /uality !ssurance of this project. This plan: Identifies the $/! responsibilities of the project developer and the

$/! consultant

0ists the activities, processes, and work products that the $/!

consultant will review and audit

Identifies the $/! work products

>.+DOCUMENT OVERVIE8:

The rest of the document is organi?ed as follows:M$n$.e7ent! description of each major element of the organi?ationand a description of the $/! tasks and their relationshipsDoc@7ent$tionIdentification of the documents related todevelopment, verification, validation, use and maintenance of thesoftware.S.+.=M$n$.e7entThis section describes the management organi?ational structure, its rolesand responsibilities, and the software )uality tasks to be performed.>.+.> Or.$ni$tion

2fforts for this project are supported by numerous entities,organi?ations and personnel. This tool is developed as part of partial


15


17/71


fulfilment of re)uirements for &asters in omputer !pplications degree.It will be the sole responsibility of the de-eloper to re-iew the productsusability, efficiency, reliability, and accuracy. The client will howeverconduct inspections, reviews, and walk"through on a regular basis.Client s specifications and suggestions will 0e used in places where /ualitydecisions need to out"weigh development schedule decisions.

2/5 TAS,S

Develop re)uirement specification and cost estimation for the

project.

Develop the design plan and test plan for testing the tool.

Implement and test the application and deliver the application alongwith the necessary documentation.


18/71


Speci"ic$tion $n& De!i.n p$!eDue to the great importance foraccuracy and completeness in these documents, weekly reviews shall beconducted between the developer and the client to identify any defects andrectify them.I7p%e7ent$tion p$!e: The developer shall do code reviews when theconstruction phase of the Tool begins.So"t*$re te!tin. p$!e: The developer shall test each case. The finalproduct shall be verified with the functionality of the software as specifiedin the $oftware *e)uirements $pecification '$*$( for the Tool.

2/= DOCUMENTATION

In addition to this document, the essential documentation will include:The $oftware *e)uirements $pecification '$*$(, which

1rescribes each of the essential re)uirements of the software

%bjectively verifies achievement of each re)uirement by a prescribed

method.

;acilitates traceability of re)uirements specification to product

delivery.


19/71


2/> DOCUMENT AUDIT

/uality !ssurance for this project will include at least one review of allcurrent work products in each stage of development '*e)uirement,

Design, and Implementation(. The reviews will assure that the establishedproject processes and procedures are being followed effectively, andexposures and risks to the current project plan are identified andaddressed. The review process includes:

! formal presentation at the end of each development phase

'*e)uirement, Design and Implementation(.

! managerial review by the client periodically to ensure the work

generated is in compliance with project re)uirements.

*eviews by the client after each presentation.

2/ SOFT8ARE DEVELOPMENT PROCESS

The software development process involves three stages: =( *e)uirementsphase, >(Design phase +( Implementation and testing phase. During eachphase, the client will review the deliverable documents. The developerwould incorporate modifications suggested by the committee. This wouldensure )uality of the software product.

2/0 PRO;ECT REVIE8S

The client will perform a review at the + stages of the project as describedin the section above. This review will determine whether the re)uirementshave been met for the deliverable, check that the product meets there)uirements, ensure that the $/! plan has been adhered to, verify the

performance of the software and ensure that acceptance testing is carriedout. ! design checklist will be used and the developer will check to seewhether the design meets the checklist criteria.

2/93 TESTING AND


20/71


3.SYSTEM ANALYSIS


1"


21/71


SYSTEM ANALYSIS$ystem analysis is the process of gathering and interpreting

facts, diagnosing problems and using the facts to improve the system.$ystem specifies what system should do. ! system is a set of componentsthat interact to accomplish some purpose.

Identifying the drawback of the existing system

Identify the need for conversion

1erform feasibility study

Identify hardware, software and database re)uirements

reate a system definition that forms the foundation for

subse)uent work

4/9 SY STEM STUDY

Oerie* o" te Ei!tin. S#!te7

In the existing system user can face so much problems. They have to waist so much time for the reservation of the room.

;or reserving a room user should have to go to the hotel.

This is the time consuming task.$ome time user is very tired then they faces the so much problem.$ometimes user feel the la?iness ,this is also failure for the existing

system.

O)jectie! o" On%ine Hote% 7$n$.e7ent

The entral objective of %H& is to provide %nline facility for booking

Hotel. In previous system ' i.e &anual $ystem ( , person has to go to theHotel for booking, en)uiry etc. This was the fully time consuming,expensive etc. Through this product, person can book the Hotel by sittingin the *oom.

PRIYESH KUMAR, DCA, CUSAT, Kochi-22 2#


22/71


.4/2 F EASI:I LITY STU DY

2010

The feasibility of a project can be ascertained in terms of technical factors,economic factors, or both. ! feasibility study is documented with a reportshowing all the ramifications of the project

Tecnic$% Fe$!i)i%it#/ Technical feasibility refers to the ability of theprocess to take advantage of the current state of the technology inpursuing further improvement. The technical capability of the personnelas well as the capability of the available technology should be considered.Technology transfer between geographical areas and cultures needs to beanaly?ed to understand productivity loss 'or gain( due to differences 'seeultural ;easibility(. $ince we are using;$$ =B To7c$t =/3 and so onso technically our project is feasible.

Econo7ic Fe$!i)i%it#/ This involves the feasibility of the proposedproject to generate economic benefits. ! )ene " i t - co ! t $ n $ % # ! i! $n& $) r e $ +een $n$%# ! i! are important aspects of evaluating the economic

feasibility of new industrial projects. The tangible and intangible aspectsof a project should be translated into economic terms to facilitate aconsistent basis for evaluation.

Fin$nci$% Fe$!i)i%it#/ ;inancial feasibility should be distinguishedfrom economic feasibility. ;inancial feasibility involves the capability of

the project organi?ation to raise the appropriate funds needed toimplement the proposed project. 1roject financing can be a majorobstacle in large multi"party projects because of the level of capitalre)uired. 0oan availability, credit worthiness, e)uity, and loan scheduleare important aspects of financial feasibility analysis.

C@%t@r$% Fe$!i)i%it#/ ultural feasibility deals with the compatibilityof the proposed project with the cultural setup of the project environment.

In labor"intensive projects, planned functions must be integrated with thelocal cultural practices and beliefs. ;or example, religious beliefs may

influence what an individual is willing to do or not do.

Soci$% Fe$!i)i%it#/ $ocial feasibility addresses the influences thata proposed project may have on the social system in the projectenvironment. The ambient social structure may be such that certaincategories of workers may be in short supply or nonexistent. Theeffect of the 1roject on the social status of the project participants



23/71


must be assessed to ensure compatibility. It should be recogni?edthat workers in certain industries may have certain status symbolswithin the society. .

2010

M$r+et Fe$!i)i%it#/ !nother concern is market variability andimpact on the project. This area should not be confused with the

2conomic ;easibility. The market needs analysis to view thepotential impacts of market demand, competitive activities, etc. andGdivertableG market share available. 1rice war activities bycompetitors, whether local, regional, national or international, mustalso be analy?ed for early contingency funding and debt servicenegotiations during the start"up, ramp"up, and commercial start"up

phases of the project.

Scope o" Fe$!i)i%it# An$%#!i!In general terms, the elements of a feasibility analysis for a project shouldcover the following:

Nee& An$%#!i!/ This indicates recognition of a need for theproject. The need may affect the organi?ation itself, anotherorgani?ation, the public, or the government. ! preliminary study isthen conducted to confirm and evaluate the need. ! proposal of howthe need may be satisfied is then made. 1ertinent )uestions that

should be asked include:

Is the need significant enough to justify the proposed project #ill the need still exist by the time the project is completed #hat are the alternate means of satisfying the need #hat are the economic, social, environmental, and political

impacts of the need

Proce!! 8or+/ This is the preliminary analysis done to determinewhat will be re)uired to satisfy the need. The work may be

performed by a consultant who is an expert in the project field. Thepreliminary study often involves system models or prototypes. ;ortechnology"oriented projects, artistJs conception and scaled"downmodels may be used for illustrating the general characteristics of a

process. ! simulation of the proposed system can be carried out topredict the outcome before the actual project starts.



24/71


En.ineerin. De!i.n/ This involves a detailed technical study ofte proposed project. #ritten )uotations are obtained from suppliersand subcontractors as needed. Technology capabilities areevaluated as needed. 1roduct design, if needed, should be done at

this time.

Co!t E!ti7$te/ This involves estimating project cost to anacceptable level of accuracy. 0evels of around "AK to F=AK arecommon at this level of a project plan. 6oth the initial and operatingcosts are included in the cost estimation. 2stimates of capitalinvestment and of recurring and nonrecurring costs should also becontained in the cost estimate docuement. S en ! i t i i t # $ n$ % # ! i!can be carried out on the estimated cost values to see how sensitivethe project plan is to the estimated cost values.

Fin$nci$% An$%#!i!/ This involves an $n$ %# ! i! o" t e c$ ! " %o *p ro" i%e o" t e p roje c t/ The analysis should consider rates ofreturn, inflation, sources of capital, payback periods, breakeven

point, residual values, and sensitivity. This is a critical analysissince it determines whether or not and when funds will be availableto the project. The project cash flow profile helps to support theeconomic and financial feasibility of the project.

Project I7p$ct!/ This portion of the feasibility study provides anassessment of the impact of the proposed project. 2nvironmental,social, cultural, political, and economic impacts may be some of the

factors that will determine how a project is perceived by the public.The value added potential of the project should also be assessed. !value added tax may be assessed based on the price of a product andthe cost of the raw material used in making the product. The tax socollected may be viewed as a contribution to government coffers.

Conc%@!ion! $n& Reco77en&$tion!/ The feasibility study

should end with the overall outcome of the project analysis. Thismay indicate an endorsement or disapproval of the project.

*ecommendations on what should be done should be included inthis section of the feasibility report.

2010


23


25/71


4.SOF T 8ARE R E


26/71


So"t*$re re?@ire7ent !peci"ic$tion

$oftware re)uirement specification abbreviated as $*$ is ameans of translating the idea of files into a formal document. The main

features of $*$ include:2stablishing the basis for an agreement between the client and

the developer.

1roducing a reference for validation of the final product. $*$assist clients in determining if the software meets there)uirements.

&ainly there are six re)uirements which an $*$ must satisfy.'a( It should specify the external behaviour.'b( It should specify the constraints.

'c( It should be easy to change.'d( It should be a reference tool.'e( It should record throughout the lifecycle.'f( It should have the capacity of expectation of an undesired event.

7sually we come across four types of re)uirement specification'a( 7ser Interface *e)uirements'b( Database *e)uirements'c( ;unctional *e)uirements'd( 5on";unctional *e)uirements

5/9U !er Inter" $ce Re?@ire7ent!

The user of the proposed system re)uires that the developedsoftware should be user friendly, have security access, and ensure the

privacy of the administrator and produce results in timely manner. Theusers are not fre)uently exposed to the on"line hotel management, so thesystem interface to the user must be simple and understandable. The web

pages must be user"friendly and must be in an easy"to"use style. The user

must be able to easily switch among various I9% screens. The product iswell designed so that it can be used easily by layman and also the userswho are novices to the system.

The system should be designed in such a way that only authori?edusers should be allowed to login to the system. The user interface should


25


27/71


be as interactive as possible. ! user"friendly interface must be provided sothat the user can easily interact with the system and comprehend things ina )uicker and easier way. The system must provide reliable and up"to"date information.

The application should be efficient so that the user does not spendmuch time in training. onsistency will increase the confidence of the userin the reliability of the application. The user must be limited with a smallset of operations to achieve the result. The application should be visuallyand conceptually clear. The interface should accommodate user mistakeseasily and fast. It should minimi?e the errors and should handle them

peacefully.

5/2D $t$)$!e Re?@ire7ent!

2010

The database should be designed in such a way that it enhancesthe efficient storage, retrieval and manipulation of all the informationassociated. ;or instance all general information regarding an itemattribute should be stored in a particular table.

The concerned users should have the facility to )uery to thedatabase and supply the basic information easily. $ecurity mechanismsshould be provided so that no confidential details should be accessible tounauthori?ed persons. The database should be organi?ed in such a waythat it helps in preparing various essential summaries needed for users.

5/4F @nct ion$% Re?@ire7ent !

The various functional re)uirements of the system can besummari?ed as:"

'a( ! home page that is user friendly and ambiguous.'b( !dministrator 0ogin ;acility'c( *oom !vailability heck ;acility'd( 2asy *eservation 1rocess'e( 1rovide *eservation $lip'f( 0inks to other related sites.'g( !bility of !dministrator to perform any tasks which you can

see in my snapshots'below( and in my running project.



28/71


5/5Non -F @ncti on$% Re?@ire7ent!

2010

5on"functional re)uirements define the system properties andconstraints that arise through user needs, because of the budgetedconstraints or organi?ational policies, or because of the need forinteroperability with other software or due to the external factors such assafety regulations privacy registrations and so on.

5/1Oter Re?@ire7ent !

Per"or7$nce Re?@ire7ent!

'a( The database should be centrali?ed and secure.'b( The system should be user friendly and easily accessible

'c( The system must be reliable.

De!i.n Re?@ire7ent!

The main objectives of input design are:'a( ontrolling the amount of input'b( Beeping the process simple, avoiding errors.'c( The best thing in the input design is to achieve all the objectives

mentioned in the simplest manner possible.The main objectives of output design are:'a( Identifying the specific outputs.'b( reating reports for displaying and storing information.



29/71


5.SYSTEM DESIGN


2!


30/71


$ystem design provides the understanding and procedural details

necessary for implementing the system recommended in the system study

.2mphasis is on translating the performance re)uirements into design

specifications . The Design phase is a transition from a user1 oriented

document '$ystem proposal( to a documented oriented to the

programmers or database personnel.

1/9 ARCHITECTURAL DESIGN

The basic architecture for the proposed system is like that

1/2 PROCESS DESIGNV Mo&e% o" &ee%op7ent

1rocess is a whole life"cycle process. 1rocess must

be applied at each stage in the software process.

PRIYESH KUMAR, DCA, CUSAT, Kochi-222"


31/71


O)jectie

The V-Mo&e% '0ifecycle 1rocess &odel( regulates the system

development process and the maintenance and modification of systems.

This standard helps to achieve the following objectives:

Improvement and guarantee of the )uality:

The discovery of defects in a system.

The assessment of whether or not the system is usable in an operational

situation.The completeness of the results to be delivered can best be

guaranteed by a standardi?ed procedure.

1/4 ENTITY RELATIONSHIP DIAGRAM

It is clear that the physical objects from the previous section1 the

administrator,rooms, ustomer1 correspond to entities in the

2ntity" *elationship model, and the operations to be done on those

entities.


32/71

PRIYESH KUMAR, DCA, CUSAT, Kochi-223#


33/71



$oo%No&o'&$oo%

U()$&i*

$oo%

Roo%*)+i(

*%i.i(+$+o$ /((0o$*

.%)

Roo%iii+ C(+o%)$

*)+i(

$)()$+io.

**$)((

$)()$+io.

ci+U()$

(++)

co.+$Ch)c&

o+

Acco.+&.

%)$

Roo%

&+/)

%oi) Ch)c&i.)(+

.


34/71

6.DA T A D E SIGN


35/71

When designing a database, the following points are considered:

The purpose of the whole database and how if affects the design should be

taken into consideration. Create a database plan to fit your purpose.

Database normalization rules that preent mistakes in the database design.

!rotection of your data"s integrity.

#ecurity re$uirements of the database and user permissions.

!erformance needs of the application. %ou must ensure that the database

design takes adantage of software features that improe performance.

&chieing a balance between the size of the database and the hardware

configuration is also importance for performance.

'aintenance

(stimating the size of a database.

6.1 Table Design

1. administrator

The admin table stores the login name and password of the administrator.

This table is used to check whether the logged in user is an administrator.

)ield

*ame

#ize +ey DescriptionType

ser-id archar / !rim &dministrator"s 0ogin id

password archar 12 &dministrator"s !assword


36/71

2. reservation

This table stores Customer"s 3eseration Details.

)ield *ame Type #ize key Description

name 4archar 5/ *ame of customer.

address 4archar 2// &ddress of customer.

city 4archar / City of customer.

state 4archar / #tate of customer.

country 4archar / Country of customer.mobile 6nt 1/ Customer"s 'obile *o

room-type 4archar 2/ !rim 3oom detail

check-in Date 1/ Date of check7in

check-out Date 1/ Date of check7out

guest 6nt 1/ *o. of 8uranted users

account-number 6nt / &ccount *umber of bank

bank 4archar 12 9ank *ame

3. room

This table stores the #tatus of 3oom that are aailable in the website for

3eseration.

)ield *ame Type #ize key Description

room 4archar 2 !rim *ame of room

no-of-room 6nt *umber of 3ooms


37/71

6.2 Data Flow Diagram

Le ve l - 0

c(+o%)$ho+)

*+()

L e v e l - 1

*%i.i(+$+o$

U()$

ho+)

C(+o%)$

*)+i(

Roo%(++(

U/*+) $oo%

*+()

$)()$+io.

Level - 2

C(+o%)$*)+i(

*%i.i(+$+o$ ho+)

Roo%

(++(

*+()

U/*+)

$oo%

U()$ ho+)

$)()$+io.

*+()

R)()$+io.(i/


38/71

7.T E STING


39/71


DCA, CUSAT, Kochi-22Code Unit Testing 3PRIYESH KUMAR,

T ES TING$oftware testing is a critical element of software )uality assurance andrepresents the ultimate review of specification, design and coding. In fact,testing is the one step in the software engineering process that could beviewed as destructive rather than constructive.

! strategy for software testing integrates software test case designmethods into a well"planned series of steps that result in the successfulconstruction of software. Testing is the set of activities that can be plannedin advance and conducted systematically. The underlying motivation of

program testing is to affirm software )uality with methods that caneconomically and effectively applied to both strategic to both large andsmall"scale systems

O)jectie o" Te!tin.

! good testing case is one that has high probability of finding as yetundiscovered errors. Testing is a process of executing a program with theintent of finding errors in it .! successful test is one that uncovers an asyet undiscovered error .The aim of testing is to determine that a programworks by showing that it has no errors .

>/9 LEVELS OF TESTING

Testing is usually relying on to detect the faults on each phase, in additionto the faults introduced during the coding phase itself. Due to this,different levels of testing are used in the testing process, each level oftesting aims to test different aspect of a system.

client Accetance

!e"#irements$%stem Testing

Design&ntegration

Testing


40/71

'!%A!E"IC A22%OAC !O 'O3!A%E !E'!IN"

The software engineering process can be viewed as a spiral. Initially,system engineering defines the role of software and leads to softwarere)uirement analysis where the information domain, functions, behavior,

performance, constraints and validation criteria for software areestablished. &oving inward along the spiral, we come to design and

finally to coding. To develop computer software we spiral in alongstreamlines that decrease the level of abstraction on each turn.

! strategy for software testing may also be viewed in the context of thespiral. 7nit testing begins at the vertex of the spiral and concentrates oneach unit of the software as implemented in source code. Testing

progresses by moving outward along the spiral to integration testing,where the focus is on the design and the construction of the softwarearchitecture. Taking another turn on outward on the spiral we encountervalidation testing where re)uirements established as part of softwarere)uirements analysis are validated against the software that has beenconstructed. ;inally we arrive at system testing, where the software andother system elements are tested as a whole.

Table


41/71

PRIYESH KUMAR, DCA, CUSAT, Kochi-22 3"

Testing and interfacing between the modules.

!cceptance

Testing

!cceptance testing is done after implementation to

check if the system runs successfully in the

customer environment9site.

U NIT TESTING

7nit Testing will be done to test field validations, navigation,

functionality of the programs and its blocks. These tests are applied on

various functions within each program and other critical program blocks.

Table given below gives the outline of three"sample test cases for 7nit

Testing performed on the system

T$)%e Unit Te!tin. Te!t C$!e 9

Te!t C$!e De!cription

This test case deals with the entering of basic details related with

the registered and logged in user . This process takes many inputs.

The test case should check for proper inputs and verify whether

the function for validating the inputs is called properly or not.

Epecte& Inp@t!

Details *elated #ith The logged in user in a $tandard ;ormat.

Epecte& O@tp@t!

!lert window for erroneous inputs.

onfirmation of $uccessful ompletion of 6asic Details 2ntry

1rocess.

Act@$% Te!t Re!@%t!


42/71

PRIYESH KUMAR, DCA, CUSAT, Kochi-22 4#

!n alert window was shown whenever the user gave some

erroneous data.

onfirmation of ompletion of 6asic Details 2ntry was displayed

on submission, implying that the functions were called properly.

T$)%e Unit Te!tin. Te!t C$!e 2

Te!t C$!e De!cription

This test case deals with the updating of 6asic Details related with

the users trade by the java function. The test will check if the java

function receives the updating details properly and checks if the

updating is performed correctly or not.

Epecte& Inp@t!

7pdated 6asic Details from the web server.

Epecte& O@tp@t!

The java function should return the correct row count. *ow count

denotes the number of rows being updated.

Act@$% Te!t Re!@%t!

The java function received the details to be updated properly.

%n updating the correct row count was returned by the function.

MODULE TESTING

&odule testing will be done to test the interaction between the various

programs within one module. It checks the functionality of each program


43/71


with relation to other programs within the same module. It then tests the

overall functionality of each module.

INTEGRATION TESTING

Integration testing is done to test the functionality and interfacingbetween the modules. The system is built up of various modules, which

work together to automate the activities of the hotel management system.

These modules should work together in a seamless way to achieve the

desired results. Integration testing will test for this property of the

modules. The modules display a cause and effect relationship, if data in

one module is changed, then it affects the data to change in some other

module also. Integration testing needs to check if the modifications do not

adversely affect some other modules.

ACCEPTANCE TESTING!cceptance testing was done after the implementation of the system. The

acceptance testing will check if the system works correctly in the user

environment and if the entire user specified functionalities are present. It

also tests if the system adheres to the company policies and )ualitystandard.

>/2 VALID ATION CHEC, S

I have use following type of checks9 data validations:

Data type

0engthonstraints

6lank field

;ormat


44/71

D$t$ t#pe


I have use $tring type for character, int for numeric, and Date for datetype. 5o numeric field insert in date. haracter never inputted in numeric

field as phone no never accept character if any person input wrongly givemessage. #hen this problem is removed then user performs furtheroperation.

Len.t

#hen we define a max length. Then it never accepts more data .forexample if I define numeric length is A then it store either e)ual to lengthor less than length. If user gives more character than re)uired thendisplay message and stop processing.

Con!tr$int!

In this I am defining range of data if data is less than then display errorwith message. ;or example code of password is four characters. The fieldof date must be @ characters.

For7$t

The pre define format is used not change daily to daily for example formatof date: is LL&&DDused in all date type field. If user inserts an other

format then display message.

8e) De!i.n Con!tr$int!

The following design constraints were kept in mind while designing thepages for the whole application:

The pages should be consistent and easy to operate. It should be designed

in such a way that an average user who does not have much idea about-$1 and related technology can still be able to access the informationneeded..



45/71


8.SYSTEM IMPLEMENTATION


43


46/71


SY STEM IMP LEMENTATION

2010

! crucial phase in system development is the successful implementation ofthe new system design. Implementation includes all those activities thattake place to convert from the old system to the new system to the new

system. The new system may be completely new replacing an existingmanual or automated system or it may be major modification to anexisting system.

In either case proper implementation becomes necessary so that a reliablesystem based on the re)uirement of the organi?ation can be provided.

$uccessful implementation may not guarantee improvement in theorgani?ation using the new system, but improper installation will preventthis improvement.

It has been observed that even the best system cannot show good results ifthe analysts managing the implementation do not attend every importantdetail. This is the area where the system analysts need to work withutmost care.



47/71


9.SYSTEM MAINTENANCE


45


48/71


SY STEM MAINTENANC E

$ystem maintenance is the modification of a software product afterdelivery to correct faults, to improve performance or other attributes, orto adapt the product to a modified environment. &aintenance is thus avery broad activity often defined as including all work made on asoftware system after it becomes operational.

&aintenance covers large number of activities like the correction oferrors, the enhancement, deletion and addition of capabilities, theadaptation to changes in data re)uirements and operation environments,the improvement of performance, usability, or any other )uality attribute.

&aintenance accounts for A4"@4 percent of total system development. Toput maintenance in its proper perspective re)uires considerable skill andexperience and is an important and ongoing aspect of systemdevelopment. &aintenance demands more orientation and training thanany other programming activities. The environment must recogni?e theneeds of the maintenance programmer for tools, methods and training.

&aintenance is done after the successful implementation of the softwareand is continued till the product is reengineered or deployed to another

platform. &aintenance is also done based on fixing the problems reported,changing the interface with other software or hardware enhancing the

software.


46


49/71


10.SCREEN SHOTS


4


50/71


M$in P$.e


4!


51/71


A) o@t Ar@


4"


52/71


A) o@t :i$r


5#


53/71


Serice!


51


54/71


T$ri""


52


55/71


Poto.$%%er#


53


56/71


Cont$ct U!


54


57/71


Roo7 Det$i%!


55


58/71


:$n?@et Det$i%!


56


59/71


Re!t$@r$nt!


5


60/71


Re!er$tion!


5!


61/71


Re!er$tion S%ip


5"


62/71


A&7ini!tr$tor Lo.in


6#


63/71


A&7ini!tr$tor P$.e


61


64/71


C@!to7er Det$i%!


62


65/71


Roo7 St$t@!


63


66/71


Up&$te Roo7 St$t@!


64


67/71


11.CONCLUSION


65


68/71


CO NCLU SION

;rom a proper analysis of positive points and constraints on thecomponent, it can be safely concluded that the product isa highly efficient


69/71

*eadability



70/71


:I :LIOGRAPHY

Core ;$$ omplete *eference " Herbert $childt

;SP The -ava 22 tutorial1 -ennifer ball, 2ric

-endrok;$$ Script Ivan 6ayross

S


71/71


Online Hotel Mngt

Documents