A

Project Report

On

Online Airline
Reservation System
FINAL PROJECT REPORT
Submitted in partial fulfillment of the requirements

for the diploma of computer

Presented by:-
 Contents
Acknowledgement

ABSTRACT

List of Figures

1 .introduction

2. project’s motto

3. intended audience
4 .cool features of our site

5 .technologies used

6 . system architecture

7. control flow in a typical user session

8. database design

9. security

12. performance results

13. implementation experiences

14. snapshots of our site

ABSTRACT

Air travel has become less and less cheaper over the years, as a result the no: of
passengers has increased considerably. Unlike a train or bus ticket where we have
to stand in a queue besides a counter, air tickets are usually booked online. The
proposed system is a web portal where the user can book their air travel tickets
between two cities online on a particular date. There will be a provision for
searching the flights for a travel destination on an input date, the search result will
comprise of the full details such as flight no, flight name, cost, arrival and
departure time etc. A cancellation option is also given in case user wishes to
abandon his travel for various reasons

1 .INTRODUCTION
Airline Reservation System” main aim is to provide the online ticket & seat
reservation of National and International Flights and also give us the information
about flight departures.

In this JAVA Major project mainly we are going to concentrate on ticket booking
function, this function will take the user inputs like their requirements (flight name,
flight source & destination, Number of seats, Seat numbers), after entering all of
his/her requirements in this application, it can check at backend & provide us the
total information about flights.

Working Modules
There are two major modules in this web portal: Admin Module and User Module:

Admin Module:
Admin controls and manages the whole portal. Admin adds all basic master entries
such as flight details, place details, route details, scheduling etc. Admin can also
view user bookings and cancellation of the user.

User Module:
User can search ticket availability first by giving the departure & destination place
and the date of travel in the site. Various flights operating on that day on that route
will be displayed. If there is seat available on the flight, user will be directed to a
booking page where user can type his details such as name, phone, address, no: of
persons travelling etc. and also the credit card payment details are entered. The
card is then validated and a reservation no: is generated automatically. If there is
no seat available in user’s choice flight then other alternate flights will be shown to
book tickets. For cancellation the user has to type the travel date, user name and
the reservation no: for validation.
Changes made by both modules get effected in the user and admin databases.

Goals:-
 primary goal of this project is to help passengers to make flight reservation.
 The system will be able to find all the flights fulfilling passengers need.
 The passengers decide flight reservation based on the displayed information.
  Search all flights with origion and destination

Objective:-
 Better storage capability.

 This system saves time and manpower.

 More efficient operations.

 Easy and fast retrieval of data.

The objective of the project is to provide the passenger the better reservation in
turn the fast service to get the reservation over in time

Purposes:-

The purpose of the present airline reservation system is to allow customer to

interact that gives basic information such as all flight information availability of
accommodation in flights ticket booking

Existing system:-

 In the existing system if any person wants to travel somewhere by flight he

should take some basic steps to get ticket like he should go to airport to book
 the flight ticket, he should speak with Airline help center regarding the
availability of flights. It is time consuming process.

Hardware requirement:-

 Processor: Intel Pentium based system

  Processor speed: 250 MHz to 833MHz

 RAM SPEED: 4GB

Software requirements:

 FRONT END: HTML, JAVA SCRIPT

 Technologies: CORE JAVA

 DATABASE: SQL

 Operating System: Windows 2000 /XP

2. PROJECT’S MOTTO:
The main aim of the project was to develop a website which would facilitate the
reservation of online air tickets through an effective and yet simple GUI for a
normal passenger intending to travel in airways. Apart from reserving tickets,
through our system a passenger can compare online fares ‘from’ various cities ‘to’
various cities.

The purpose of the present airline reservation system is to allow customer to

interact that gives basic information such as all flight information availability of
accommodation in flights ticket booking

3. INTENDED AUDIENCE:

1. The project is basically targeted at those people who would like to travel
through air and have an Internet access.
2. As we will be making our site WAP – enabled, this will facilitate our site to
accept requests from other alternative devices like PDA’s and WAP-enabled
browsers. Apart from the above category of audience, passengers using
hand-held devices will be our second major category of audience.
CONTROL FLOW IN A TYPICAL USER SESSION:

User will type the URL of our site: ONLINE RESERVATION SYSTEM in
the browser.

1. User will be shown our homepage containing various page links and search
option.
2. User will click on the Login button to log on into our system.
3. The user-id and password are validated and the user is allowed to login.
4. The user is directed to the home page where he can start his search for his
travel options.
5. The user can select the Departure and arrival cities and click on the Search
button.
6. The user will be shown a page with various list boxes he has to choose for
his tickets.
7. The user will select the departure airport, arrival airport, departure date,
arrival date, and will click
8. The user is presented with page listing all the options for his search criteria
9. If he chooses to buy this ticket he will be sent E-mail with all details of the
tickets
10.User can either continue shopping or close his session by logging out of the
system.
4.COOL FEATURES OF OUR SITE:

1.Dynamic Bandwidth Calculation:

either to the Graphical Version or to the Text-Version based on the

client’s bandwidth.

2.Sitemap:
We are providing a cool map of our entire site for easy access of our
pages. Sitemap includes all the links in all the pages in our site categorized
based on the functionality of the pages.

3.Flash Images of Flights:

We created flight detail images and used Flash to integrate them and
show the user the seating arrangement of the flight. The user can know about
the details of the seating arrangement, emergency exit doors and lavatory
details before entering the flit
TECHNOLOGIES USED
Following are the core technologies used in developing our website.

WEB SERVER :

2. Tomcat Server

 Tomcat is enterprise class, robust web server which comes bundled with
JavaServlets and JSP that provides a java application server environment

 One of the other major issues why we chose Tomcat was Scalability.
Presently Java is our core technology used for portability and in future if
we want to make our site be reachable to users using Microsoft products
we would be having no conflicts between the servers because Tomcat
can be deployed as either a standalone product with its own internal Web
server or in conjunction with several other Web servers, including

Netscape Enterprise Server.

Microsoft Internet Information Server.

Microsoft Personal Web Server.

 It adheres to the latest standards, which expands the security features.

Configuration, tuning and maintenance are lot easier than compared to
other prevailing web servers.

 Since we were not going for enterprise java beans in our project we
didn’t feel the necessity of going for other application servers like J2EE
or JBOSS .We were basically looking for a reliable web server which
would be compatible with both the front-end and back-end technologies
we were using and our ultimate choice was Apache’s Tomcat Web
Server.
Eclipse :

is an integrated development environment (IDE) used in computer programming

and is the most widely used Java IDE. It contains a base workspace and an
extensible plug-in system for customizing the environment. Eclipse is written
mostly in java and its primary use is for developing Java applications, but it may
also be used to develop applications in other programming language through the
use of plug-ins, including: Ada ,ABAP,C,C++,COBLE, D, Fortran Haskell, java
script ,Julia, lasso ,Lua , perl ,PHP ,Prolog, python,
R, (including framework), Rust, Scala, Clojure, Groovy, Scheme, and Erlang. It
can also be used to develop documents with LaTeX (through the use of the
TeXlipse plugin) and packages for the software Mathematica. Development
environments include the Eclipse Java development tools (JDT) for Java and Scala,
Eclipse CDT for C/C++ and Eclipse PDT for PHP, among others.

The initial codebase originated from IBM Visual Age.[7] The Eclipse software
development kit (SDK), which includes the Java development tools, is meant for
Java developers. Users can extend its abilities by installing plug-ins written for the
Eclipse Platform, such as development toolkits for other programming languages,
and can write and contribute their own plug-in modules. Since Equinox, plug-ins
can be plugged/stopped dynamically and are known as (OSGI) bundles[8]

Released under the terms of the Eclipse Public License, Eclipse SDK is free and
open-source software, although it is incompatible with the GNU General Public
License.[9] It was one of the first IDEs to run under GNU Classpath and it runs
without problems under IcedTea.
MySQL:
(officially pronounced as /maɪ ˌɛskjuːˈɛl/ "My S-Q-L",) is an open-
[7]
source relational database management system (RDBMS). Its name is a
combination of "My", the name of co-founder Michael Widenius' daughter, and
"SQL", the abbreviation for Structured Query Language. The MySQL
development project has made its source code available under the terms of
the GNU General Public License, as well as under a variety
of proprietary agreements. MySQL was owned and sponsored by a single for-
profit firm, the Swedish company MySQL AB, now owned by Oracle
Corporation. For proprietary use, several paid editions are available, and offer
additional functionality.
MySQL is a central component of the LAMP open-source web application
software stack (and other "AMP" stacks). LAMP is an acronym for
"Linux, Apache, MySQL, Perl/PHP/Python". Applications that use the MySQL
database include: TYPO3, MODx, Joomla, WordPress, phpBB, MyBB, and Drupal
MySQL is also used in many high-profile, large-scale websites,
including Google (though not for searches), Facebook
,Twitter, Flickr and YouTube
OTHER REASONS

Based upon the functionality of our website, it obvious that we have to be in a

position to handle requests from users accessing our website from various
different types of computers and operating systems. Oracle software enables
different types of computers and operating systems to share information across
networks. Even in future if we want to jump into distributed environment/network
we can do so. For networked, distributed environments, Oracle combines the data
physically located on different computers into one logical database that can be
accessed by all network users. Apart from these reasons, Oracle software lets you
replicate groups of tables and their supporting objects to multiple sites. Oracle
supports replication of both data- and schema-level changes to these sites.
Software Technologies
  Java Server Pages (JSP)
 Java Servlets
 Java Beans
 Java Mail
 HTML
 JavaScript
 HTTP Sessions
 Java Bean

Java Server Pages (JSP)

 Regular HTML, of course, cannot contain dynamic information. JSP is so

easy and convenient that it is quite feasible to augment HTML pages that
only benefit marginally by the insertion of small amounts of dynamic data.
 JSP was designed to work with Java Servlets and JavaBeans in a seamless
fashion, it provides applications developers with the capability to cleanly
separate content generation from content presentation.
 This means that Web page designers can work independently from business
logic developers, and the end result will work in a distributed, heterogeneous
computing environment.

Java Servlets

 Java Servlets are server-side technologies that provide a component-

based, platform-independent method for building web-based
applications. They provide web developers with a simple, consistent
mechanism for extending the functionality of a web server and for
accessing existing databases. Since our website was more database-
centric we found servlets as more appropriate choice.

 Servlets have access to the entire family of Java APIs, including the
JDBC API to access databases. Servlets can also access a library of
HTTP-specific calls and receive all the benefits of the mature Java
 language, including portability, performance, reusability, and crash
protection.

 Our other alternative for Java servlets was CGI. But we continued
with Java servlets mainly because of the following reasons

i) Efficient: With traditional CGI, a new process is started for

each HTTP request. With servlets, the Java Virtual Machine
stays up, and each request is handled by a lightweight Java
thread, not a heavyweight operating system process.

ii) Convenient: Each one of us was more comfortable with Java

Besides the convenience of being able to use a familiar
language, servlets they have this added advantage of
automatically parsing and decoding HTML form data, tracking
sessions, and many other such tasks. As these operations were
very much needed for our website we found our decision to be
right.

iii) Powerful: Java servlets let us do several things easily, which

are either difficult or impossible by traditional CGI. One thing
is servlets can talk directly to the Web server (regular CGI
programs can't). This simplified operations that needed us to
look up data stored in standard places. We found them very
useful in maintaining information from request to request,
simplifying things like session tracking and caching of previous
computations.

Java Mail

 Hosting an Online Air tickets Website we had this requirement

of sending out an email to our customer once he purchased
ticket through our site as a confirmation with his flight details
and schedule. As we were using Java as our programming
language we had this added advantage of using Java Mail API
to suffice our need.
  We implemented this feature of sending out emails using Java
Mail successfully. For this we had to download Java mail API
and JavaBeans activation Framework apart from setting their
paths in our web servers class path. Java Mail API allowed us
to instantly add the ability to send-out e-mail with our Java
applications with negligible programming effort.

XML & XSL

 XML was mainly used because of its extensibility feature. It

had this added advantage of presenting the same content in
different formats to different clients.
 Our site is completely driven by XML data. We have
implemented all our servlets in such a way that they throw
XML DOM tree for each and every page. So once we had this
XML DOM tree in hand we implemented XSL’s to throw out
either a HTML data
 In this way our site is more extensible, suppose that in future
we had to extend our site to clients with a new markup
language what all we need to do is write out a separate XSL to
display the data in the form specific to that client.
 Another major advantage of sending XML data to the client
instead of html data is, we can offload some computation to the
client from the server. i.e. we weren’t forced to bother about the
presentation data on

 JavaScript was basically used for client-side validation.

 JavaScript is compatible with all versions of Microsoft Internet

Explorer and Netscape Navigator.
 We have small java scripts, which are lightweight and will not
hinder the download time of the HTML document significantly.
HTTP Sessions& Java Beans:

Every user who logs in to our system is given a new session. We

implemented this feature using the Http Session API provided by the
Servlets and Java Beans.
JAVA LANGUAGE:
Java is a computer programming language. It enables programmers to write
computer instructions using English based commands, instead of having to write in
numeric codes. It’s known as a “high-level” language because it can be read and
written easily by humans. Like English, Java has a set of rules that determine how
the instructions are written. These rules are known as its “syntax”. Once a program
has been written, the high-level instructions are translated into numeric codes that
computers can understand and execute.

5.3.1 Functional Specification

Java is an object-oriented programming language developed by Sun Microsystems

in the early 1990s. Java is a computer programming language that is concurrent,
class-based, object oriented, and specifically designed to have as few
implementation dependencies as possible. It is intended to let application
developers write once, run anywhere (WORA), meaning that code
that runs on one platform does not need to be recompiled to run on another.
The Java programming language is a high-level language that can be characterized
by all of the 31 Mulitiparty Authorization Architecture For Collabrative Data
Sharing In OSN’s following buzzwords:

1. Simple

2. Object oriented

3. Distributed

4. Multithreaded

5. Dynamic
6. Architecture neutral

7. Portable

8. High performance

9. Robust

10. Secure

5.3.2 Dependency and Constraints:

Dependency
Share any information or upload data

5.4 Non Functional Requirements:

5.4.1 Performance Requirement:

 Every module of the system should work efficiently.

 The system should perform fast in all weather conditions.

Safety & Security Requirement

The java application will not affect other applications on user's system.
DATABASE DESIGN:

We use Oracle as the backend and use JDBC connectivity to access the database.
The servlets access the database using JDBC and output the results according to
the query, which again takes into account the options, selected by the user.
The following gives the various tables and their fields used in our database, which
was a major design decision of our project.

USERS Table contains the details of the users registered for our services.
The fields in this table are as follows:

USERID PASSWORD FNAME LNAME SSN

ADDRESS CARDTYPE CREDITCARD EXPMONTH
EXPYEAR POINTS

USERID is the PRIMARY KEY of this table.

TRANSACTIONS Table contains the details of all the transactions done by

the users through our site. The table contains the following fields:

TNO is the PRIMARY KEY of this table.

NEWS Table contains the details of the current news. This news includes
flight cancellations, flight delay information and other important weather
information. The table contains the following fields:

HEADLINE HREF

HEADLINE is the PRIMARY KEY of this table and the HREF is the
link to the file, which contains the complete data regarding the headline.

MOTELS Table contains the motel information for various cities. The
fields in this table are as follows:

CITY MOTEL ADDRESS DELUX LUXURY

(CITY,MOTEL) is the PRIMNARY KEY of this table. DELUX AND

LUXURY are the corresponding of the MOTEL.
 AIRLINE Table contains the information about the various flight
availabilities and the related information. The table has the following fields:

FLIGHT DEPCITY DEPPORT DEPTIME ARRCITY

ARRPORT ARRTIME AIRLINE ECPRICE ECSEATS
BSPRICE BSSEATS

(FLIGHT, DEPTIME) is the PRIMARY KEY of this table.

We assumed three airline databases in the above format. For that we created
three different tables DELTA, UNITED, AMERICAN with the same above
schema.
SYSTEM ARCHITECTURE
A. Architecture Model Used:
 Database
Server

B. Overall Architecture

Database
Internet Server
U
Webserv
s
e Database
r Server

Database
Server

Server
 WM
In the Design of our website we made an assumption that we are accessing the
database of different airline to get the flight information. Any last minute changes
to the flight schedule are taken care by the respective airlines. Presently we are
accessing database of three airlines. In our website we will be maintaining the table
to hold user information, his transaction details only.

The figure shows how our website is organized. The Servlet accesses the
Database, which use the bean. The Servlet generates a DOM tree, which contains
the required information. This XML it transformed in to a code containing HTML,
JAVASCRIPT code. Which is displayed to the user in a web browser. In case of a
PDA device WML code is generated by the XSL
DATA FLOW DIGRAM
Hardware requirement:-
Pentium processors

In its current form, Pentium processors are considered entry-level products that
Intel rates as "two stars", meaning that they are above the low-end Atom and
Celeron series but below the faster Core i3, i5 and i7 lines as well as the high-end
Xeon processors. Pentium
Codenamed P5, the Intel Pentium was released by Intel on March 22, 1993 as a
replacement to the 80486 processor and originally sold for $878.00. The name
comes from the Greek word for "five" and is used because it's the fifth processor in
the 80x86 line. It would have been called the 80586 had a US court not ruled that
you cannot trademark a number. The Intel processors were available between
speeds of 60MHz and 300MHz, had a 64-bit databus, and had an additional 1.9
million transistors when compared to the 80486DX (3.1 million). Below is a
graphic illustration of the Pentium processor.

The original Intel Pentium was released using a 273-pin PGA form factor and ran
on 5v power. Intel later announced the release of a second-generation introduced
March 7, 1994 included new processors from 75, 90, 100, 120, 133, 150, 166, and
200 MHz. The processors used 296-pin SPGA form factor that is physically
incompatible with the first generation versions. The third-generation of Pentium
processors, code named P55C, were introduced January 1997, which incorporated
the new technology MMX. The Pentium MMX processors were available 166,
200, 233 MHz, and 266 MHz mobile version
 RAM . speed 4GB

RAM (pronounced ram) is an acronym for random access memory, a type

of computer memory that can be accessed randomly; that is, any byte
of memory can be accessed without touching the preceding bytes. RAM is the
most common type
9. IMPLEMENTATION EXPERIENCES:

 We had problems in implementing Dynamic Bandwidth Calculation

in our site. We used an Applet to load a fixed-size image from the
server to the client in the background. Based on the time taken by the
file transmission we tried to direct the user to either Graphical version
or the Text version of our site.
 We initially thought of providing the user an option of sorting the
results based on his own priority. We started implementing this using
java script but we were unable to implement it both in Internet
explorer and Netscape navigator. We thought this wouldn’t affect our
site’s experience much.
 We initially planned to show the user an animated inner view of the
flights but we were unable to create the animated pictures and hence
we used flash to show various static images of the flights.
 Initially we installed Tomcat Version 3.4.1 but it was unable to
recognize the class path. So we had to move to Version 3.2.4.
 We had many problems with the WAP simulators in passing the
parameters dynamically to the servlets. We tried on many available
WAP simulators but we were unable to find one for our purpose.
 We had problem with Oracle database population. We thought of
providing the user at least one month flight details but because of the
constraints on the usage of CIS oracle database space, we couldn’t
populate it as we planned.
Project Planning and Estimation
4.1 Project Plan
4.1.1 PERT Chart/ Gantt chart

NO TASK DURATION(Days) START END DATE

DATE
1 Group Formation 4
2 Decide Area Of Interest 4
3 Search Topic 5
4 Topic Selection 5
5 Sanction Topic 5
6 Search Related 12
Information
7 Understanding Concept 7
8 Search Essential
Document 6
(IEEE & White Paper,
Software)
9 Problem Definition 2
10 Literature Survey 5
11 SRS 14
12 Project Planning 2
13 Modeling & design 10
14 Technical Specification 2
15 PPT 6
4.2 Project Estimate
We are using waterfall model for our project estimation.
1.Requirement gathering and analysis:

In this step of waterfall we identify what are various requirements are need
for our project such are software and hardware required, database, and interfaces.

2. System Desgin:

In this system design phase we design the system which is easily understood
for end user i.e. user friendly.

We design some UML diagrams and data flow diagram to understand the system
flow and system module and sequence of execution.

3. Implementation:

In implmentaion phase of our project we have impemented various module reqired

of sussessfully getting expeted outcome at the different module levels.

With inputs from system design, the system is first developed in small
programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality which is referred to as Unit Testing.

4. Testing:

The different test cases are performed to test whether the project module are
giving expected outcome in assumed time.

All the units developed in the implementation phase are integrated into a system
after testing of each unit. Post integration the entire system is tested for any faults
and failures.

5.Deploment of System:

Once the functional and non functional testing is done, the product is
deployed in the customer environment or released into the market.
Test Specification
Introduction

Software testing is an investigation conducted to provide stakeholders with

information about the quality of the product or service under test. Software
testing can also provide an objective, independent view of the softwareto
allow the business to appreciate and understand the risks of software
implementation. Test techniques include the process of executing a
program or application with the intent of finding software bugs (errors or
other defects).

Software testing involves the execution of a software component or system

component to evaluate one or more properties of interest. In general, these
properties indicate the extent to which the component or system under test:

 meets the requirements that guided its design and development,

 responds correctly to all kinds of inputs,
 performs its functions within an acceptable time,
 is sufficiently usable,
 can be installed and run in its intended environments, and
 achieves the general result its stakeholders desire.
As the number of possible tests for even simple software components is
practically infinite, all software testing uses some strategy to select tests that
are feasible for the available time and resources. As a result, software testing
typically (but not exclusively) attempts to execute a program or application
with the intent of finding software bugs(errors or other defects). The job of
testing is an iterative process as when one bug is fixed, it can illuminate
other, deeper bugs, or can even create new ones.

Testing:
The purpose of testing is to discover errors. Testing is the process of trying
to discover every conceivable fault or weakness in a work product. It provides a
way to check the functionality of components, sub assemblies, assemblies and/or a
finished product It is the process of exercising software with the intent of ensuring
that the

Software system meets its requirements and user expectations and does not fail in
an unacceptable manner. There are various types of test. Each test type addresses a
specific testing requirement.

TYPES OF TESTS

 8.2.1 Unit Testing

Unit testing involves the design of test cases that validate that the internal
program logic is functioning properly, and that program inputs produce valid
outputs. All decision branches and internal code flow should be validated. It is the
testing of individual software units of the application .it is done after the
completion of an individual unit before integration. This is a structural testing, that
relies on knowledge of its construction and is invasive. Unit tests perform basic
tests at component level and test a specific business process, application, and/or
system configuration. Unit tests ensure that each unique path of a business process
performs accurately to the documented specifications and contains clearly defined
inputs and expected results.

8.2.2 Integration testing

Integration tests are designed to test integrated software components to

determine if they actually run as one program. Testing is event driven and is more
concerned with the basic outcome of screens or fields. Integration tests
demonstrate that although the components were individually satisfaction, as shown
by successfully unit testing, the combination of components is correct and
consistent. Integration testing is specifically aimed at exposing the problems that
arise from the combination of components.

8.2.3 Functional test

Functional tests provide systematic demonstrations that functions tested are

available as specified by the business and technical requirements, system
documentation, and user manuals.

Functional testing is centered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be exercised.

Systems/Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to
identify Business process flows; data fields, predefined processes, and successive
processes must be considered for testing. Before functional testing is complete,
additional tests are identified and the effective value of current tests is determined.

8.2.4 System Test

System testing ensures that the entire integrated software system meets
requirements. It tests a configuration to ensure known and predictable results. An
example of system testing is the configuration oriented system integration test.
System testing is based on process descriptions and flows, emphasizing pre-driven
process links and integration points.

8.2.5 White Box Testing

White Box Testing is a testing in which in which the software tester has
knowledge of the inner workings, structure and language of the software, or at least
its purpose. It is purpose. It is used to test areas that cannot be reached from a black
box level.
8.2.6 Black Box Testing
Black Box Testing is testing the software without any knowledge of the inner
workings, structure or language of the module being tested. Black box tests, as
most other kinds of tests, must be written from a definitive source document, such
as specification or requirements document, such as specification or requirements
document. It is a testing in which the software under test is treated, as a black box
.you cannot “see” into it. The test provides inputs and responds to outputs without
considering how the software works.

Test strategy and approach

Field testing will be performed manually and functional tests will be written
in detail.

Test objectives
 All field entries must work properly.
 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.

Features to be tested
 Verify that the entries are of the correct format
 No duplicate entries should be allowed
 All links should take the user to the correct page.
SNAPSHOTS OF OUR SITE
Conclusion

 Minimum time is required .

 Fulfill customer requirements.

 Most convenient for customer.

.REFERENCES:

http://info.med.yale.edu/caim/manual/index.html

http://www.xml101.com:8081/xml/

http://www.webdevelopersjournal.com/

http://developer.iplanet.com/viewsource/marchal_xml.htm

http://www.object-arts.com/EducationCentre/Overviews/MVC.htmhttp://www.w3.org/

http://www.gelon.net

http://www.delta.com

http://www.priceline.com