HOTEL MANAGEMENT SYSTEM.

Abstract Our Project is a software that can be used in the hospitality industry. Through this software the Hotel administration can manage their loyalty programs in an effective way. The Hotel Loyalty Programs can be used to entice guests into becoming a regular guest at the hotel. These programs are especially beneficial to hotel chains, where the benefits of the program can span over their entire hotel chain. Personalized service and rewards deliver e ceptional e periences to guests, and ma!e them come bac! for more. The scope of the project defines only those functionalities which are provided by our project. On the other hand the scope of the users involved in the "ewards and Loyalty Program is defined as the roles of each user in the system and their accessibilities to the different elements and prospects within the system. The project will include three main users who ta!e part in the wor!ing of the system as a complete functionality. #onsidering the complete functionality and interactions within the Hotel we will define the roles of each user along with their access permissions towards the various elements of the system. The various users participating in the system are as follows$ %i& %ii& %iii& The Hotel 'dministrator The Hotel (ront )es! Office The *ember % The customer of the hotel&

INTRODUCTION
This project includes three types of users i.e. the hotel administration, the hotel front des! office and the customers of the hotel. This project wor!s primarily on the basis of the type of membership cards the hotel administration provides to its customers who subscribed for the hotel. These membership cards represent the points allocated to the customers who subscribed for the hotel. The subscription to the Hotel is offered to the customers of the hotel when they ma!e their first reservation in the hotel. (or this the hotel maintains a subscription form and is made available on the hotel+s website. The hotel can also maintain a paper form which can be given to the new customers who have made their first reservation. The hotel can also opt to send the subscription form through emails to the appropriate customers. The details of all the customers are maintained by the hotel administration as a part of the hotel+s database. The hotel is solely responsible on its decision on how to avail the subscription form to its customers. 's a hotel provides the hotel with three types of membership cards i.e. %i& ,ilver %ii& -old and %iii& Platinum. The names of these membership cards can be edited as per the will of the hotel. The number of different types in the membership cards can also be edited as per the hotel+s choice. The hotel administration will be given an address boo! table as a part of the software which can be updated by the hotel staff in order to maintain the records of all the subscribers of the Hotel+s Loyalty Program. This address boo! is supposed to be updated on a regular basis to contain the updated membership details list of all the subscribers of the Hotel+s Loyalty Program. .nitially when a customer of the hotel subscribes for the hotel+s "ewards and Loyalty program, he/she is given a membership card of silver type. (rom this moment onwards the customer will be a part of the "ewards and Loyalty Program that the hotel offers. Hence the customer becomes a subscriber for the hotel+s "ewards and Loyalty program and can now increase his points of loyalty by ma!ing more and more reservations in this hotel or by spending on other hospitality services offered by the hotel. .n this way the customer who is now a member of the "ewards and Loyalty program of the hotel can increase his/her points by becoming a regular customer to the hotel. *oreover by increasing his/her points the customer can improve

his/her membership type so as to avail nice offers and discounts from the hotel. The subscribers to this program can view their points from time to time either through the hotels+ website or through automated mails delivered by the hotel. This depends on the hotels decision on how to implement the process of delivering updates to their subscribers. 0henever the subscribers have crossed the milestone of their respective membership type, they are promoted to the ne t membership type and the new membership card is posted to the respective subscriber+s official postal address. This posting of the membership card is the responsibility of the front des! office of the respective hotel. 'll this happens when an alert message triggers to the front des! office of the hotel as and when the milestones of any subscriber is crossed. This automated reminder can benefit the hotel+s administration by reducing their overhead of maintaining and updating their customers+ membership details. .t also acts as a prime factor in the process of maintaining consistency in updating the records. .n this way it is close to impossible for the management to miss on the updating of any membership account.

(igure$Overview of Pro ect

PRO!ECT O"ER"IE#$

This section involves the scope of the project and the scope of its users. The scope of the project defines only those functionalities which are provided by the ,oftware. On the other hand the scope of the users involved in the "ewards and Loyalty Program is defined as the roles of each user in the system and their accessibilities to the different elements and prospects within the system. This ,ystem will include three main users who ta!e part in the wor!ing of the system as a complete functionality. #onsidering the complete functionality and interactions within the ,ystem we will define the roles of each user along with their access permissions towards the various elements of the system. The various users participating in the system are as follows$ %i& The Hotel 'dministrator %ii& The Hotel (ront )es! Office %iii& The *ember % The customer of the hotel who subscribed for the Hotel& Role Based Access a) The Hotel Administrator i& #onfigures The #onfiguration Page The hotel administrator is responsible for deciding on the number of points to be allocated per day stay and also the number of points allocated for each hospitality service provided by the hotel. These hospitality services may include$ "eservation charges, 'dd Ons, "estaurants, 1ars, ,hops, Other 2 tra #harges depending on the corresponding hotel. ii& #reation Of ' 3ew *ember The hotel administrator can create a new user in the "ewards and Loyalty Program by approving the subscription submitted by the customer as legitimate only after reviewing his/her details completely.

iii& #reation Of The ,ubscription (orm (or The "ewards 'nd Loyalty Program The hotel administrator can design the subscription form for ma!ing it available to all the customers who are new to the hotel. Having made their first reservation, these customers are provided with the subscription form. iv& *a!ing The ,ubscription (orm 'vailable To The 3ew #ustomers The hotel administrator can do this in three ways as mentioned below$

The form can be made available on the hotel+s website. The form can be mailed to his new customers % i.e. those customers who have just made their first reservation in the hotel &. The form can be handed over in hand at the time when the customer ma!es his/her reservation for the first time in the hotel.

v& *anage 2 isting *embers The hotel administrator has the access to all his subscribers+ information and can therefore communicate with them. He can send automated messages to his eligible subscribers about any offers or discounts which are announced. The hotel administrator can send alert messages to the e isting "ewards and Loyalty members % i.e. customers who have subscribed for the "ewards and Loyalty Program & regarding their membership e piry issues. The hotel administrator maintains the details of all the members of the hotel+s "ewards and Loyalty Program. 'part from details in the form of data records and tables li!e address boo! the hotel administrator also maintains and generates reports for details of all the subscribers to the hotel+s "ewards and Loyalty Program. vi& *aintains .nformation 'bout #ards To 1e ,ent The hotel administrator maintains a list of all the cards that are to be delivered to the respective members of the "ewards and Loyalty Program along with their complete details. This

list may include members who have lost their membership cards and also the new members of the "ewards and Loyalty Program.

vii& "eward "edemption The hotel administrator maintains all the details of reward redemption and the members associated with this functionality. b) The Hotel Front Desk Office i& )elivers *embership #ards To *embers The (ront )es! Office is prompted when there is a member whose membership points cross the milestone of the respective membership card type. .n this case the front des! office is responsible for delivering the updated card to the respective member of the "ewards and Loyalty Program. The (ront )es! Office is also responsible for delivering membership cards to all the members of the list given by the hotel administrator. This list includes the members who have lost their membership cards and have applied for new ones and also those members who are new to the "ewards and Loyalty Program and are yet to receive their default membership cards.

c) The Member i& 4iew The *ember+s Profile Page The members i.e. the customers who have subscribed for the "ewards and Loyalty Program of the hotel can view their profile page in the hotel+s website under the "ewards and Loyalty section. This profile page also contains the "ewards and Loyalty points of the member along with the membership details. ii& 'pply (or ' 3ew *embership #ard The member can apply for a new membership card in case he/she loses their card.

iii& .nteract 0ith The (ront )es! Office The member can interact with the front des! office of the hotel for any !ind of en5uiries.

d) The System ( our Soft are ) i& *aintains The #onfiguration Page The latest configuration details are maintained. These details are available for the hotel administrator to modify whenever necessary. The hotel administrator can find these details on the configuration page in the "ewards and Loyalty section of the hotel+s website. ii& *aintains ' 4iew/*odify Page This page is only available for the hotel administrator to modify or update its members+ membership details. iii& *aintains ' ,earch Page This is provided for the hotel administrator and the hotel front des! office. Through this a search can be made possible for a member+s details or for a particular reservation+s details. iv& *aintains ' "eports Page Through this the system generates reports for the different users and also for the different reservations related to the hotel. This pages accessibility can be defined by the hotel administrator.

SO%T#ARE & HARD#ARE SPECI%ICATION Software$

Server Si'e$ C(ie)t Si'e$ 'ny 0eb 1rowser on any 0indows operating system. *icrosoft 0indows 6P/7/8 .nternet e plorer 9.: or above or 3etscape navigator. PHP *ys5l 9.: %)1& 0amp ,erver

Har'ware$
Pentium )ual #ore Processor. 9;< *1 "'*. 8:-1 Hard )is! space.

SYSTEM ANALYSIS

PROPOSED SYSTEM$
e=ee "ewards and Loyalty is a software that can be used in the hospitality industry. Through this software the Hotel administration can manage their loyalty programs in an effective way. The Hotel Loyalty Programs can be used to entice guests into becoming a regular guest at the hotel. These programs are especially beneficial to hotel chains, where the benefits of

the program can span over their entire hotel chain. Personalized service and rewards deliver e ceptional e periences to guests, and ma!e them come bac! for more. The system will be divided into the following subsystems. >ser -et .nformation e=ee Loyalty and "ewards is a 0eb 'pplication. .n this system administrator collects the information from different hotels. e=ee Loyalty and "ewards system administrator contacts the specified rooms and collects the information and update the information time to time and store in database in a fle ible manner.

RE*UIREMENT ANALYSIS & SPECI%ICATION$

The scopes of e=ee Loyalty and "ewards are$ The scope of the project defines only those functionalities which are provided by the e=ee "ewards and Loyalty ,oftware. The scope of the users involved in the "ewards and Loyalty Program is defined as the roles of each user in the system and their accessibilities to the different elements and prospects within the system.. The scope of this system includes planning and designing. The contents are as follows$

User Mo'+(e Tas,s$

#reate a separate *enu item in e=ee(rontOffice application called ?Loyalty and "ewards@ .n that create the following sub menu items viz.,

Me)+ Str+ct+re Lo-a(t- a)' Rewar's #onfigure *embership Levels Points o *etric Types o Aualification *etrics o Points 'llocation o Points Purchase o "ewards *embership )etails

'dd/4iew/*odify ,earch "eports

%EASI.ILITY STUDY
TECHINICAL %EASI.ILITY$ 2valuating the technical feasibility is the tric!iest part of a feasibility study. This is because, .at this point in time, not too many detailed design of the system, ma!ing it difficult to

access issues li!e performance, costs on %on account of the !ind of technology to be deployed& etc. ' number of issues have to be considered while doing a technical analysis. i& >nderstand the different technologies involved in the proposed system$ 1efore commencing the project, we have to be very clear about what are the technologies that are to be re5uired for the development of the new system. ii& (ind out whether the organization currently possesses the re5uired technologies$ o .s the re5uired technology available with the organizationB o .f so is the capacity sufficientB (or instance C ?0ill the current printer be able to handle the new reports and forms re5uired for the new systemB@

OPERATIONAL %EASI.ILITY$ Proposed projects are beneficial only if they can be turned into information systems that will meet the organizations operating re5uirements. ,imply stated, this test of feasibility as!s if the system will wor! when it is developed and installed. 're there major barriers to .mplementationB Here are 5uestions that will help test the operational feasibility of a project$ .s there sufficient support for the project from management from usersB .f the current system is well li!ed and used to the e tent that persons will not be able to see reasons for change, there may be resistance. 're the current business methods acceptable to the userB .f they are not, >sers may welcome a change that will bring about a more operational and useful systems. Have the user been involved in the planning and development of the projectB 2arly involvement reduces the chances of resistance to the system and in -eneral and increases the li!elihood of successful project.

,ince the proposed system was to help reduce the hardships encountered. .n the e isting manual system, the new system was considered to be operational feasible.

ECONOMIC %EASI.ILITY$ 2conomic feasibility attempts < weigh the costs of developing and implementing a new system, against the benefits that would accrue from having the new system in place. This feasibility study gives the top management the economic justification for the new system. ' simple economic analysis which gives the actual comparison of costs and benefits are much more meaningful in this case. .n addition, this proves to be a useful point of reference to compare actual costs as the project progresses. There could be various types of intangible benefits on account of automation. These could include increased customer satisfaction, improvement in product 5uality better decision ma!ing timeliness of information, e pediting activities, improved accuracy of operations, better documentation and record !eeping, faster retrieval of information, better employee morale.

SYSTEM DESIGN

DATA %LO# DIAGRAMS

)ata flows are data structures in motion, while data stores are data structures. )ata flows are paths or Dpipe lines+, along which data structures travel, where as the data stores are place where data structures are !ept until needed.

)ata flows are data structures in motion, while data stores are data structures at rest. Hence it is possible that the data flow and the data store would be made up of the same data structure. )ata flow diagrams is a very handy tool for the system analyst because it gives the analyst the overall picture of the system, it is a diagrammatic approach. ' )() is a pictorial representation of the path which data ta!es (rom its initial interaction with the e isting system until it completes any interaction. The diagram will describe the logical data flows dealing the movements of any physical items. The )() also gives the insight into the data that is used in the system i.e., who actually uses it is temporarily stored. ' )() does not show a se5uence of steps. ' )() only shows what the different process in a system is and what data flows between them. The following are some )() symbols used in the project

2 ternal entities

Process$ ' transaction of information that resides within the bounds of the system to be module.

)'T'(LO0,
)'T',TO"2$ ' repository of data that is to be stored for use by one or more processes, may be as simple as buffer of 5ueue or as a relational database.

RULES %OR D%D$

(i the scope of the system by means of conte t diagrams.

Organize the )() so that the main se5uence of the actions reads left to right and top to bottom. .dentify all inputs and outputs. .dentify and label each process internal to the system with rounded circles. ' process is re5uired for all the data transformation and transfers. Therefore, never connect a data store to a data source or the destinations or another data store with just a data flow arrow.

LE"ELS O% D%D$

)o not indicate hardware and ignore control information. *a!e sure the names of the processes accurately convey everything the process is done. There must not be unnamed process. .ndicate e ternal sources and destinations of the data, with s5uares. 3umber each occurrence of repeated e ternal entities. .dentify all data flows for each process step, e cept simple "ecord retrievals. Label data flow on each arrow. >se details flow on each arrow. >se the details flow arrow to indicate data movements. There can+t be unnamed data flow. ' data flow can+t connect two e ternal entity.

The comple ity of the business system means that it is a responsible to represent the operations of any system of single data flow diagram. 't the top level, an Overview of the different systems in an organization is shown by the way of conte t analysis diagram. 0hen e ploded into )() They are represented by$ L242LE: $ ,F,T2* .3P>T/O>TP>T

L242LE; $ ,>1,F,T2* L242L )'T'(LO0 (>3#T.O3'L L242LE< $ (.L2 L242L )2T'.L )'T' (LO0.

The input and output data shown should be consistent from one level to the ne t. LE"EL/0$ SYSTEM INPUT1OUTPUT LE"EL

' levelE: )() describes the systemEwide boundaries, dealing inputs to and outputs from the system and major processes. This diagram is similar to the combined userElevel conte t diagram. LE"EL/2$ SU.SYSTEM LE"EL DATA %LO#

' levelE; )() describes the ne t level of details within the system, detailing the data flows between subsystems, which ma!eup the whole. LE"EL/3$ %ILE LE"EL DETAIL DATA %LO#

'll the projects are feasible given unlimited resources and infinite time. .t is both necessary and prudent to evaluate the feasibility of the project at the earliest possible time. (easibility and the ris! analysis are pertained in many ways. .f project ris! is great.

DATA DICTIONARY

ER DIAGRAMS
UNI%IED MODELING LANGUAGE DIAGRAMS The unified modeling language allows the software engineer to e press an analysis model using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules. ' >*L system is represented using five different views that describe the system from distinctly different perspective. 2ach view is defined by a set of diagram, which is as follows. >ser *odel 4iew i. This view represents the system from the users perspective. ii. The analysis representation describes a usage scenario from the endEusers perspective.

,tructural model view .n this model the data and functionality are arrived from inside the system. This model view models the static structures. 1ehavioral *odel 4iew .t represents the dynamic of behavioral as parts of the system, depicting the interactions of collection between various structural elements described in the user model and structural model view. .mplementation *odel 4iew .n this the structural and behavioral as parts of the system are represented as they are to be built.

2nvironmental *odel 4iew .n this the structural and behavioral aspects of the environment in which the system is to be implemented are represented. >*L is specifically constructed through two different domains they are >*L 'nalysis modeling, which focuses on the user model and structural model views of the system. >*L design modeling, which focuses on the behavioral modeling, implementation modeling and environmental model views. >se case )iagrams represent the functionality of the system from a user+s point of view. >se cases are used during re5uirements elicitation and analysis to represent the functionality of the system. >se cases focus on the behavior of the system from e ternal point of view. 'ctors are e ternal entities that interact with the system. 2 amples of actors include users li!e administrator, ban! customer Getc., or another system li!e central database.

Use Case 'ia4ra5 A'5i)$ e6ee Lo-a(t- a)' Rewar's

Login Password

Configure

Admin

Search

Add/View

Reports

Use Case Dia4ra5 User $ e6ee Lo-a(t- a)' Rewar's

Registration Login

Forgot Password

User

Update Profile

View Details

Get Rooms Log ut

Se7+e)ce Dia4ra5 / e6ee Lo-a(t- a)' Rewar's 8A'5i) Lo4i)9

Administrator

Login

Home

Data Base

1 : Login()

2 : Invalid Data()

3 : Request to DB()

4 : Response rom DB() ! : "et Home()

>ser Login ,e5uence

#ser

Login

Home

Data Base

1 : Login()

2 : Invalid Data()

3 : Request to DB()

4 : Response rom DB()

! : "et Home()

>ser 'ctivities

#ser

$as%ord

&ie%

'odi (

Data Base

1 : )*ange()

2 : &ie% o%n Details()

3 : 'odi (()

4 : +ave()

! : +ave() , : +ave()

SO%T#ARE & HARD#ARE RE*UIREMENTS

#lient ,erver Over view$ 0ith the varied topic in e istence in the fields of computers, #lient ,erver is one, which has generated more heat than light, and also more hype than reality. This technology has ac5uired a certain critical mass attention with its dedication conferences and magazines. *ajor computer vendors such as .1* and )2#H have declared that #lient ,ervers is their main future mar!et. ' survey of )1*, magazine reveled that 7IJ of its readers were actively loo!ing at the client server solution. The growth in the client server development tools from K<:: million in ;LL< to more than K;.< billion in ;LLI. #lient server implementations are comple but the underlying concept is simple and powerful. ' client is an application running with local resources but able to re5uest the database and relate the services from separate remote server. The software mediating this client server interaction is often referred to as *.))L20'"2. The typical client either a P# or a 0or! ,tation connected through a networ! to a more powerful P#, 0or!station, *idrange or *ain (rames server usually capable of handling re5uest from more than one client. However, with some configuration server may also act as client. ' server may need to access other server in order to process the original client re5uest. The !ey client server idea is that client as user is essentially insulated from the physical location and formats of the data needs for their application. 0ith the proper middleware, a client input from or report can transparently access and manipulate both local database on the client machine and remote databases on one or more servers. 'n added bonus is the client server opens the door to multiEvendor database access indulging heterogeneous table joins. 0hat is a #lient ,erver Two prominent systems in e istence are client server and file server systems. .t is essential to distinguish between client servers and file server systems. 1oth provide shared

networ! access to data but the comparison dens thereM The file server simply provides a remote dis! drive that can be accessed by L'3 applications on a fileEbyEfile basis. The client server offers full relational database services such as ,ALE'ccess, "ecord modifying, .nsert, )elete with full relational integrity bac!up/ restore performance for high volume of transactions, etc. the client server middleware provides a fle ible interface between client and server, who does what, when and to whom.

0hy #lient ,erver #lient server has evolved to solve a problem that has been around since the earliest days of computing$ how best to distribute your computing, data generation and data storage resources in order to obtain efficient, cost effective departmental an enterprise wide data processing. )uring mainframe era choices were 5uite limited. ' central machine housed both the #P> and )'T' %cards, tapes, drums and later dis!s&. 'ccess to these resources was initially confined to batched runs that produced departmental reports at the appropriate intervals. ' strong central information service department ruled the corporation. The role of the rest of the corporation limited to re5uesting new or more fre5uent reports and to provide hand written forms from which the central data ban!s were created and updated. The earliest client server solutions therefore could best be characterized as ?,L'42E*',T2"@. TimeEsharing changed the picture. "emote terminal could view and even change the central data, subject to access permissions. 'nd, as the central data ban!s evolved in to sophisticated relational database with nonEprogrammer 5uery languages, online users could formulate adhoc 5ueries and produce local reports with out adding to the *., applications software bac!log. However remote access was through dumb terminals, and the client server remained subordinate to the ,laveN*aster.

(ront end or >ser .nterface )esign The entire user interface is planned to be developed in browser specific environment with a touch of .ntranetE1ased 'rchitecture for achieving the )istributed #oncept.

The browser specific components are designed by using the HT*L standards, and the dynamism of the designed by concentrating on the constructs of the Oava ,erver Pages. #ommunication or )atabase #onnectivity Tier The #ommunication architecture is designed by concentrating on the ,tandards of ,ervlets and 2nterprise Oava 1eans. The database connectivity is established by using the Oava )ata 1ase #onnectivity. The standards of threeEtire architecture are given major concentration to !eep the standards of higher cohesion and limited coupling for effectiveness of the operations. (eatures of The Language >sed

%ORMS

REPORTS

SYSTEM TESTING

Testi)4

Testing is the process of detecting errors. Testing performs a very critical role for 5uality assurance and for ensuring the reliability of software. The results of testing are used later on during maintenance also. Ps-c:o(o4- of Testi)4 The aim of testing is often to demonstrate that a program wor!s by showing that it has no errors. The basic purpose of testing phase is to detect the errors that may be present in the program. Hence one should not start testing with the intent of showing that a program wor!s, but the intent should be to show that a program doesn+t wor!. Testing is the process of e ecuting a program with the intent of finding errors. Testi)4 Ob ectives The main objective of testing is to uncover a host of errors, systematically and with minimum effort and time. ,tating formally, we can say, Testing is a process of e ecuting a program with the intent of finding an error. ' successful test is one that uncovers an as yet undiscovered error. ' good test case is one that has a high probability of finding error, if it e ists. The tests are inade5uate to detect possibly present errors. The software more or less confirms to the 5uality and reliable standards.

Leve(s of Testi)4

.n order to uncover the errors present in different phases we have the concept of levels of testing. The basic levels of testing are as shown belowG

#lient 3eeds "e5uirements )esign

'cceptance Testing

+(stem -esting

Integration -esting

#ode
#nit -esting

S-ste5 Testi)4
The philosophy behind testing is to find errors. Test cases are devised with this in mind. ' strategy employed for system testing is code testing.

Co'e Testi)4$
This strategy e amines the logic of the program. To follow this method we developed some test data that resulted in e ecuting every instruction in the program and module i.e. every path is tested. ,ystems are not designed as entire nor are they tested as single systems. To ensure that the coding is perfect two types of testing is performed or for that matter is performed or that matter is performed or for that matter is performed on all systems.

T-;es Of Testi)4

 >nit Testing Lin! Testing

U)it Testi)4
>nit testing focuses verification effort on the smallest unit of software i.e. the module. >sing the detailed design and the process specifications testing is done to uncover errors within the boundary of the module. 'll modules must be successful in the unit test before the start of the integration testing begins. .n this project each service can be thought of a module. There are so many modules li!e Login, H0'dmin, *aster'dmin, 3ormal >ser, and P*anager. -iving different sets of inputs has tested each module. 0hen developing the module as well as finishing the development so that each module wor!s without any error. The inputs are validated when accepting from the user. .n this application developer tests the programs up as system. ,oftware units in a system are the modules and routines that are assembled and integrated to form a specific function. >nit testing is first done on modules, independent of one another to locate errors. This enables to detect errors. Through this errors resulting from interaction between modules initially avoided.

Li), Testi)4
Lin! testing does not test software but rather the integration of each module in system. The primary concern is the compatibility of each module. The Programmer tests where modules are designed with different parameters, length, type etc.

I)te4ratio) Testi)4
'fter the unit testing we have to perform integration testing. The goal here is to see if modules can be integrated properly, the emphasis being on testing interfaces between modules. This testing activity can be considered as testing the design and hence the emphasis on testing module interactions.

.n this project integrating all the modules forms the main system. 0hen integrating all the modules . have chec!ed whether the integration effects wor!ing of any of the services by giving different combinations of inputs with which the two services run perfectly before .ntegration.

S-ste5 Testi)4
Here the entire software system is tested. The reference document for this process is the re5uirements document, and the goal is to see if software meets its re5uirements. Here entire D'T*+ has been tested against re5uirements of project and it is chec!ed whether all re5uirements of project have been satisfied or not.

Acce;ta)ce Testi)4
'cceptance Test is performed with realistic data of the client to demonstrate that the software is wor!ing satisfactorily. Testing here is focused on e ternal behavior of the systemH the internal logic of program is not emphasized. .n this project D3etwor! *anagement Of )atabase ,ystem+ . have collected some data and tested whether project is wor!ing correctly or not. Test cases should be selected so that the largest number of attributes of an e5uivalence class is e ercised at once. The testing phase is an important part of software development. .t is the process of finding errors and missing operations and also a complete verification to determine whether the objectives are met and the user re5uirements are satisfied.

#:ite .o< Testi)4

This is a unit testing method where a unit will be ta!en at a time and tested thoroughly at a statement level to find the ma imum possible errors. . tested step wise every piece of code, ta!ing care that every statement in the code is e ecuted at least once. The white bo testing is also called -lass 1o Testing. . have generated a list of test cases, sample data, which is used to chec! all possible combinations of e ecution paths through the code at every module level.

.(ac, .o< Testi)4

This testing method considers a module as a single unit and chec!s the unit at interface and communication with other modules rather getting into details at statement level. Here the module will be treated as a bloc! bo that will ta!e some input and generate output. Output for a given set of input combinations are forwarded to other modules.

Criteria Satisfie' b- Test Cases

Test cases that reduced by a count that is greater than one, the number of additional test cases that much be designed to achieve reasonable testing. Test cases that tell us something about the presence or absence of classes of errors, rather than an error associated only with the specific test at hand.

SO%T#ARE TOOLS

Met:o'o(o4-

The method being used in developing the system is the system )evelopment Life #ycle %,)L#& The ,)L# process includes project identification and selection, project initiation and planning, analysis, design, implementation and maintenance.

P"OO2#T .)23T.(.#'T.O3 '3) ,2L2#T.O3

.
P"OO2#T .3.T.'T.O3 '3) PL'33.3-

'3'LF,.,

LO-.#'L )2,.-3

PHF,.#'L )2,.-3

.*PL2*23T'T.O3

*'.3T23'3#2

(igure <.P$ 0aterfall *odel %,)L#&

,ystem )evelopment Life #ycle %,)L#&

The system )evelopment Life #ycle%,)L#& is a traditional methodology used to develop, maintain and replace or enhance information system. The main reason ,)L# model is chosen because in ,)L# it is possible to complete some activities in one phase in parallel with some activities of another phase. The life cycle can also be interactive that is phase are repeated as re5uired until an acceptable system is found. ;.P.;.; Phase ;$ Project identification and selection .n this phase the project information system needs are identified and analyzed such as identified the title of the project that is 0eb 1ased 6path'nalyzer, scope and objective of the 0eb 1ased 6path'nalyzer. ;.P.;.< Phase <$ Project initiation and planning )uring this phase the -antt chart has been developed as a time line to determining the tas! involve in developing the 0eb 1ased 6path'nalyzer. ;.P.;.Q Phase Q$ 'nalysis .n the phase, the e iting system is studies by collecting the information through the .nternet and analyzed the information to get alternatives for the used of proposed system. )etermine what the 0eb 1ased 6path'nalyzer should do. ;.P.;.P Phase P$ )esign Logical design is the fourth phase in ,)L# methodology. The functional features chosen for the proposed system in 'nalysis phase are described. Part of the logical design of the information system is to devise the user interface. The interface plays an important role to connect the user with the system and is thus e tremely important.

TECHNICAL NOTES

#i)'ows =P O;erati)4 S-ste5

Microsoft "is+a( St+'io/300> 3.0 %ra5ewor, Microsoft MYS*L/?.0.?2b/wi)@3 I)ter)et MoAi((a %ire%o<

CONCLUSION

The entire project has been developed and deployed as per the re5uirements stated by the user, it is found to be bug free as per the testing standards that are implemented. 'ny specification untraced errors will be concentrated in the coming versions, which are planned to be developed in near future.