1

Project Overview
This project is developed to online EXAMINATION of airlines by computer it means
this project for the electronic examination . Many examination systems mark coming
from an SMTP server in the Amazon cloud as spam. As a result, you can't use traditional
examination delivery techniques for exam out form submissions or program alerts from
the cloud. In this cloud tip, I describe how you can successfully send legitimate email
from an Amazon EC2 instance.

First of all user create an account for the exam the ticet. Then they do exam.
This project can be used as a component that can be used by any person which is use the
electronic mail for our relative on there web site.
When user use this website .first of all user have to click on E-Mail server then click on
client.

Following are the main modules of the project:

1. Create User Account

2. Login Existing User
3. Exit

1. Create User Account

a. User Name
b. Password
c. Create New Account

2. Login Existing User

a. User Name
b. Passward
c. Login
3. Exit

Exit the project.

.
 2

Java Beans
MS Web
Components
DCOM
Request Request Request

Client Web Components

Server & Business Logic Response
Response
Response Request

Html Middle
IIS
JavaScript Ware
Apache
CSS Netscape Data
Response
Enterprise Base
.ASP
.JSP

MS-SQL Server
DB2
Sybase
Oracle

Web Architecture
 3

System Analysis

It involves posting letters of present system whether it is manual or computerized.If it is

computerized then what are the loopholes of the present system and if it is not computerized then
whether it need computerization or not.

Some of them point involves in the system analysis are as follows:

Study of present system.

If current system is computerized than why change in system is needed ?
Whether a system become allright or it will suffice the need of user after
making current to it or development of new system is required ?
What are the various jobs that will be performed by the system ?
If the present system is manual then is it feasible to make it computerized ?

System posting letters is done in the organization itself by collecting

various letters from level of organization.

System analysis is concluded to achieve the following objective:

Identification of user need.

Determine system feasibility (feasibility study)
Perform economic and technical feasibility analysis.
Establishment of cost and schedule constraints.
Allocation of function to hardware, software, people and other system
components.

Identification of Need

The first step in the development of computer based system is identified the need of the
organization. It defines what kind of information is required as decision point. It also
describes the mechanism of inputs and outputs of the system. At this stage the main
objectives is togather information from different level of organization various manual
reports and input type are sending mail at this stage

This phase of software development is also known as requirement specification. Online

sending letters is in demand these days by various kind of letters. The traditional sending
letters system is manual system and user should write letter. In traditional sending letters
system users write a latter on latter pad. This requires a lot of paper work to be done.
First of all write a latter . Then the post the latter. Postmen are distributed to the person
 4

manually in the door to door and user collect the latter. The latters are read manually
which again is a time consuming and costly process.

The Online Sending Mail System eliminates all these disadvantages and provides a much
efficient way to sending latter. This system is based on sending mail online ( i.e. on a
networked computer system). The system can work on LAN or internet. This type of
examination system is already in use by many computer institutes.

Prelimnary investigation
This stage is the preliminary of sending mail of the system .This phase involves the
detailed evaluation of the present system.So the following step were followed:

Requirement specification:

In this phase ,mainly data collection was done.Through asking

,questionnaires,
on site observation, procedures, and manuals the users requirement were
determined. This helped to understand the acts and functioning of
system. Through this procedure we identified the requirement of the user and
identified the need of the system requirements .This phase are complete
asking
and observation of the system and also study of the manual system. What are
the manual system ? and what are the system works has been done ?In study
of
the present system and observe its drawbacks of the present system.In this
phase these task are complete through study of the systems,So this stage is
the
first stage of the development of the automated system.

Structure analysis:

The structured analysis helped us to develop a new kind of system

specifications.through logical models,like data flow dictionary.This formed the
basis of designing and implementation.For structure analysis there are following
tools and techniques.

Data flow diagram

Data dictionary
 5

Structure English
Decision trees
Decision tables
 6

FEASIBILITY STUDY

At the end of information gathering phase,we have an idea of the data available currently
and deficiencies of the current system.We also come to know the priorities and
requirements .It is necessary to quantify the goals and subgoals and objective.Once these
goals are defined then logically thinking is done,how to meet the objective and at what
cost they are achieved.

Feasibility study is the evaluation of the candidate system.Before we go to

further steps of development,whether it is technically ,and economically feasible.So for
evaluating this ,we followed these steps:

We studied the system and understood,What the problem is. ?

Several alternatives were chosen for the benefit of the user and cost and
saving were also calculated for those alternatives.
After all this,we had to check for the technical and economical feasibility

The prime focus of the feasibility study is evaluating the practicality of the proposed
system keeping in mind a number of factors. The following factors are taken into
account before deciding in favor of the new system: -
Economic Feasibility
In this cost/benefit analysis is done for estimating cost ,we had to consider several cost
elements, like hardware ,personnel , facility, operating supply costs. After that we
assigned a monetary value to each benefit was accuracy of the access to information.
Therefore the system was found to be economically feasible.

Economical feasible analysis is done in order to ensure that the system is economically
viable. It is also done to get an idea that it is possible to develop the system within
 7

organizational functional limit.. A cost and benefit analysis is to find out whether it is
economically feasible to invest for the project. Computing these two gives an argument
either in favor of system or against the proposed system.

Cost of both types Direct and indirect considered. Direct cost are those incurred in buying
the equipment, employing people, cost of consumable item, rent for accommodation for
system developers etc. indirect cost involves brain storming time spent by in discussing
problem with the system analyst, effort in gathering data etc. benefits can be broadly
classified as tangible and intangible benefit. Tangible benefit are directly measurable e.g.
saving money by reducing is improved working environment, better management of
resources, timely information flow, decision support, effective report generation.

The sum of all cost-producing components is compared with the sum of total
saving or benefit. If it worthwhile to carry out to the project economically then
further step for the system development are taken

The proposed Online sending latters system will save lots of paper work and
Facilitate automates examination process there by reducing the costs incurred on
above described heads. This reduction in cost prompts the educational institutions
to go for such computer-based system.
Technical Feasibility
In this, technical aspects of the computer system were checked. The main aspects
are hardware and software. The system already have enough hardware and
software and memory, so the chances of overloading the system were less and it
was under budget to accommodate the technical enhancements.

During technical feasibility analysis the analyst evaluate the technical merit of
the concept, while at the same time it collect the information about the
performance(system throughput, turn around time etc.), reliability,
maintainability, and productivity of the system.
 8

Technical feasibility analysis begins with an assessment of the technical

viability of proposed system. It is analyzed that what kind of environment,
process and method required to accomplished the system. A general logical model
I prepared which resemble to the real world and shows the various components
and their role in the system. A solution is technically feasible, if technology is
available to implement the logical design of the system as we are provided
sufficient technical support, we do not have technical feasibility problem

As the saying goes, "to err is human". Keeping in view the above fact, Now-a-
days all organizations are automating the repetitive and monotonous works done
by humans. The key process areas of current system are nicely amenable to
automation and hence the technical feasibility is proved beyond doubt.

Operational Feasibility
Operational feasibility analysis is done with an objective of finding the impact of the systemof
management and employees in organization .If the system is operationally feasible the
management and user both welcome theproposal of development of the new system.In this the
evaluation of satisfactionof the users is done.Since our system was very much user friendly and
flexible so we estimated that the reaction of the user staff will be positive .hence we stepped
further.

Prepared a statement of objective and scope.

Prepared the generalization flowcharts ,describing the inputs and outputs and
dataflow diagram,describing the key points the system, being made.

We checked for different aspect of the hardware ,like processing and

memory.
After considering the cost and performance of different alternatives,it was
clear that proposed system was feasible and further analysis can be done.
 9

An operational feasibility system requires :

Minimum paper work .

More users friendly
Reduce transaction time

The manual sending mail system is error prone and time-consuming..

Time and Resource Feasibility
This system helps the users and institutions to find in the best usage of
resources keeping in track of all the database information. A lot of time is
saved due to automatic report generation process. Otherwise the manual
process of report generation is time consuming and costly. The process saves a
lot of time and resources.
 10

Software Engineering Paradigms Applied

Software engineering paradigm: - Software engineering paradigm means which model

is used in the development of the project so we here use the prototype model for
developing the project.

Requirements
Analysis

Design Design

Code Code

Test Test

Requirement
Analysis

Figure: The Prototype Model

In the first stage I analyzed which type of requirement of the customer that is properly
defined in the problem statement, of system analysis part. In this model the requirement
is change when user thinks on the new system, so in this model the customer meeting is
so necessary because that refine the requirement of the user after properly get the whole
information for the proposed system.

Design: I design the logical and physical design of the system like Data Flow
Diagram, E-R Diagrams, Data Structures etc. The ONLINE SENDING MAIL
SYSTEM is firstly divided into number of modules. After dividing the modules I design
the structure of output screen of every module of ONLINE SENDING MAIL
 11

SYSTEM and take the decision in which way the Data should be represent on the out
put screen.

Code: In this phase I design the module onto the system this phase is known as
implementation. I design every module by using programming language and run it on the
system. The ONLINE SENDING MAIL SYSTEM is designed in the Java, JSP,
HTML, Java Script and Data base as MS Access 2000.

Testing: In this phase I test every modules of the project that are properly
implemented in the project. I use different Test cases for testing the system that are
defined in the testing chapter.
 12

Software and Hardware Requirement Specification

Software:

1. Operating System: Windows 2000

2. GUI internet browser ( Like Internet Explorer or Netscape)
3. Development environment: MS Front Page 2000
4. Java Development Kit (JDK 1.3)
5. Tomcat Apache Web Server 4.1
6. MS Access 2000 (can be ported to any other database)

Programming Languages:

Java, JSP, HTML, DHTML, JavaScript

Hardware:

Minimum Hardware Requirement that can support GUI Internet browser and Windows
2000 Operating System

233 MHz Processor

64 MB RAM

Platform: Platform Independent need only GUI internet browser and web server to
support JSP on a particular platform.

Runtime Requirement:

1. Java Runtime Environment

2. Tomcat Apache Web Server
3. GUI internet browser
4. MS Access 2000

Client Side Requirements:

GUI internet browser

Server Side Requirements

1. Java Runtime Environment

2. Tomcat Apache Web Server
3. MS Access 2000

Database:

MS Access 2000
 13

System Design
Entity Relationship Diagrams

E-R Diagram of Complete System

airlines

Booking table Login existing table

email
name password
name password

Select
country Telephon no

class
 14

Description of Modules

1. Create user account

a. Registration Form

User have to register first for sending online latters. For registration,
Users must fill an online form that is available on the web site. The form
requires various information from the user like Name and password. The
form number is provided to the user through an automatic form number
generation program. Each student gets a unique password number and this
form number will be used as the Login ID of the user.

The form is also validated for the compulsory fields before it is submitted
to the server.

b. Form Verification

This process verifies the form on the server side. This process checks that
the password provided by the user should be unique. If the password given
by the user already exist in the database then the appropriate error message
is shown to the user. If the verification is passed then the contents of the
form are stored in the database.

c. Confirmation of Registration

If the user is successfully registered, he will get confirmation of the

registration.
2. Login existing account

a. Login Form

The registered user can login to the web site for appearing for the
onlinesend latter. This is done by filling up a simple form in which user
enters his/her password.

b. Login Validation

After the user submits the login form it is validated on the server side for
correctness of password. If the validation passes the user gets the
subject selection form, otherwise an appropriate error message is
shown.
3. exit :-
exit project.
 15

USER

No
Member Want a
or member
Non Ship?
member?
Registration
No Yes Verify the Username
And password
No
Username and
Password
right

Consider As
Member A non-
Accesses member

The General
View Info
Account
Info Restaurant
Booking

Database
 16

S O F T W A R E

D E S I G N

APPROACH

The software design phase is the most important and core part in the entire
software development life cycle. Software Design phase is the actually a link
 17

between analysis-specification phase and system implementation base. So it

extremely important to handle this phase by considering each & every minute
detail.

The procedure to be followed is briefly described below

The entity-relationship diagrams are drawn to identify the entities and

relationship between these entities.

Database Design shows basic design of tables, primary keys and

foreign keys.

User Interface design which includes general layout of the component to

be used and overall behavior of the entire system.

ENTITY-RELATIONSHIP DIAGRAM

Entity relationship diagram is very basic, conceptual model of data and it is

fundamental to the physical database design. This analysis is then used to
organize data as relations, normalizing relations, and obtaining a Relational
database.
The entity-relationship model for data uses three features to describe data.

These are.

1. Entities which specify distinct real-world items in an application

2. Relationship, which connect entities and represent meaningful

dependencies between them.

3. Attributes which specify properties of entities & relationships

Tools and platform

Software:
 18

7. Operating System: Windows xp-2

8. GUI internet browser ( Like Internet Explorer or Netscape)
9. .net framework 2.0
10. c# programming
11. sql server 2005

Programming Languages:
C#, asp.net

Hardware:

Minimum Hardware Requirement that can support GUI Internet browser and Windows
xp-2 Operating System

233 MHz Processor

128 MB RAM

Platform: Platform Independent need only GUI internet browser and web server to
support ASP.net on a particular platform.

Runtime Requirement:

5. asp.net runtime invirment

6. iis (internet information service)
7. GUI internet browser
8. Sql server 2005

Client Side Requirements:

GUI internet browser

Database:

Sql server 2005

APPROACH
 19

This is the phase where coding for the software is done. If all the previous phase
are accurately handled, implementations becomes somewhat easier.

Main goals of this phase are

Select tool(s) for the development of the software by doing through study of
the tools, their capabilities and how they can be used to meet design goals.

Making separate functionality based modules and implementing the software

one-by-one module, which make the implementation of the software a
straightforward process.

TOOL SPECIFICATION

As there are many powerful tool are available in the market today. But .net
shines out among them as it is very powerful language and was also very suitable
for developing web-based as well as standalone applications. We used ASP.NET
which is parallel to ASP which is Microsofts product.

Why we use ASP.NET?

the Microsoft .NET Framework and ASP.NET were released. Finally,

here was a framework that let me work on Web applications, yet it was
almost like programming desktop applications. I could build windows
(pages), hook up controls to events, and the designer kept me from
having to deal with those darn angle brackets. And best of all, ASP.NET
automatically handled the stateless nature of the Web for me with view
state! I was a happy programmer again ... at least for a while.
ASP.NET Web Forms made it very easy to get started, but, in other
ways, trying to apply my design principles to Web apps was a struggle.
Web Forms are relentlessly UI focused; the fundamental atom is the
page. You start by designing your UI and dragging controls. It's very
seductive to just start slapping your application logic into the page's
event handlers (much like Visual Basic enabled for Windows apps).
On top of that, unit testing of pages is often difficult. You can't run a
Page object through its lifecycle without spinning up all of ASP.NET.
While it is possible to test Web apps by sending HTTP requests to a
server or automating a browser, that kind of testing is fragile (change
one control ID and the test breaks), hard to set up (you have to set up
the server on every developer's machine exactly the same way), and
slow to run.

The internet needs no introduction. The success of the HTTP protocol in its
simplicity, scalability and ubiquity is obvious.
 20

The main problems facing developers seeking to develop web applications

are:

Scalability : A successful site will have more users than the biggest
corporation intranet. And the number of users is rising all the time, so your
solutions have to scale.
Integeration of backend data and business logic : The web is just another way
to conduct business, and so it should be able to use the same middle-tier and data-
access code. Interfacing web-based requests to backend systems can be a big
headache.
Manageability : sites just keep getting bigger, and we need some way to
manage the content and its interaction with business systems. Object-oriented
programming techniques have proven their worth in client-server systems and
they should help us in the web application development.
Personalization : Adding a personal touch to the page isnt easy.

Web Application Server Architecture:

the use of the Model View Presenter (MVP) pattern for building testable
Web Forms.
In a nutshell, instead of putting your logic in the page, MVP has you
build your pages so that the page (View) simply makes calls into a
separate object, the Presenter. The Presenter object then performs any
logic necessary to respond to the activity on the view, typically by
using other objects (the Model) to access databases, perform business
logic, and so on. Once those steps are complete, the Presenter
updates the view. This approach gives you testability because the
presenter is isolated from the ASP.NET pipeline; it communicates with
the view through an interface and can be tested in isolation from the
page.
MVP works, but the implementation can be a bit awkward; you need a
separate view interface, and you have to write lots of event forwarding
functions in your code behind files. But if you want a testable UI in
your Web Forms applications, it's about the best you're going to get.
Any improvements would require a change in the underlying platform.

Model View Controller Pattern

Luckily, the ASP.NET team has been listening to developers like me and
has started development of a new Web application framework that sits
 21

side-by-side with the Web Forms you know and love but has a
distinctly different set of design goals:
Embrace HTTP and HTMLdon't hide it.

Testability is built-in from the ground up.

Extensible at almost every point.

Total control over your output.

This new framework is based around the Model View Controller (MVC)
pattern, thus the name, ASP.NET MVC. The MVC pattern was originally
invented back in the '70s as part of Smalltalk. As I'll show in this
article, it actually fits into the nature of the Web quite well. MVC
divides your UI into three distinct objects: the controller, which
receives and handles input; the model, which contains your domain
logic; and the view, which generates your output. In the context of the
Web, the input is an HTTP request, and the request flow looks like
 22

This is actually quite different from the process in Web Forms. In the
Web Forms model, the input goes into the page (the View), and the
view is responsible for both handling the input and generating the
output. When it comes to MVC, on the other hand, the responsibilities
are separated.
So, right now there's probably one of two things running through your
head. Either, "Hey, this is great. How do I use it?" or "Why would I
write three objects when I only had to write one before?" Both are
excellent questions and best explained by looking at an example. So
I'm going to write a small Web app using the MVC Framework to
demonstrate its advantages.

Farewell Web Forms?

At this point you may be wondering, "What's happening to Web Forms?
Is MVC replacing it?" The answer is no! Web Forms is a well-
understood technology, and Microsoft will continue to support and
enhance it. There are many applications where Web Forms work very
well; the typical intranet database reporting app, for instance, can be
created using Web Forms in a fraction of the time it would take to
write it in MVC. Plus Web Forms supports a vast marketplace of
controls, many of which are extremely sophisticated and save massive
amounts of work.
So, when should you choose MVC over Web Forms? In many ways, it
comes down to your requirements and your preferences. Are you
struggling to get your URLs formed the way you want? Do you want to
unit test your UI? Either of those scenarios would lean toward MVC. On
the other hand, are you doing a lot of data display, with editable grids
and fancy tree view controls? Then you're probably better off with Web
Forms for the moment.
Over time, the MVC Framework will probably catch up in the UI control
department, but most likely it'll never be as easy to get started with as
with Web Forms, where massive amounts of functionality are just a
drag and drop away. But in the meantime, the ASP.NET MVC
Framework offers Web developers a new way to build Web applications
in the Microsoft .NET Framework. The Framework is designed for
testability, embraces HTTP instead of trying to abstract it away, and is
extensible at just about every point. It is a compelling complement to
 23

Web Forms for those developers who want complete control over their
Web applications.
 airlines booking

0
Web Application Server
ASP.NET
document

ASP.NET

Servler
Plain document

Web Server

Client

- 24 -
 airlines booking

Introduction to Database

We have used the sql server 2005 as the database design. We used the Java Database
Connectivity API to easily add a high degree of database interactivity to the application.
ASP.NET 2.0 is perfectly capable of working with no data, data from sequential
files, data from instruments or peripherals, or almost anything a standalone
program can do. But nearly all of the world's actual systems use data from a
database. And ASP.NET 2.0 works best with Microsoft's database, SQL Server.
To prove it, check out these integrated features designed just for databases in
.net

We'll see more of these as we we discover how to integrate data from a SQL
Server database into a web site. We'll use VWD in this segment of the tutorial
to demonstrate the features of SQL Server.

By this time, you should have installed Microsoft's free SQL Server 2005
Express (from now on SSE) database alongside VWD. You can download it
from the same web page you found VWD on. The "big brother" to SSE is SQL
Server 2005 (no "Express Edition") and is used for some of the largest and
most demanding database applications in the world. SSE is totally compatible,
however. So you can develop on SSE and be assured of a straightforward
migration to the more powerful SQL Server 2005 when you're ready.

Before we tie together VWD and SSE together, let's take a brief look at SSE by
itself just to get more familiar with it.

- 25 -
 airlines booking

Data Structure and Table Design

Table Name: Booking Form

Primary Key: FormNo

Column Name Data Type Length Allow Null

Name Text
Password Text 20
Email Text
Select country Text
Telephone no text
Class text

Table Name: Login existing account

Column Name Data Type Length Allow Null
Name Text
Password Text

- 26 -
 airlines booking

Implementation and Maintenance

Testing

Introduction
Software Testing uncovers errors in the software. It is a crucial element of software quality
assurance and represents the ultimate review of specification, design and coding. Testing
demonstrate that software function appeared to be working according to specification that
performance requirements appear to have been met. In addition data collected as is
conducted provide a good indication of software reliability and with some indication of
software quality as a whole. The basic objectives of testing process are:
1. Testing is a process of executing a program with the intent of finding an error.
2. A good test case is one that has a probability of finding an as yet undiscovered error.

Testing Principles

Software testing verifies that the software meets the requirements. It involves the operation
of a system or application under controlled conditions and evaluating the results. The
controlled conditions include both normal and abnormal conditions. Testing is done with
the intention of finding errors. We should not test a program to show that it works, but to
find the maximum number of errors possible. We begin testing with the assumption that it
contains errors. Testing should intentionally attempt to make things go wrong and then
observe the behavior of the product in those conditions.
A good understanding of the reasons for errors would enable the development of quality
assurance plans with insight. Now, why does software have errors or bugs?

- 27 -
 airlines booking

Miscommunication or no communication: as to specifics of what an application should or

shouldnt do, the applications requirements.
Software complexity: the complexity of current software applications can be difficult to
comprehend for anyone without experience in modern day software development.
Windows-type interfaces, client-server and distributed applications, data communications,
enormous relational databases and sheer size of applications have all contributed to the
exponential growth in software/system complexity. The use of object-oriented techniques
can complicate instead of simplifying a project unless it is well engineered.
Programming errors: programmers like anyone else can make a mistake.
Changing requirements: the customer may not understand the effects of changes, or may
understand and request them anyway redesign, rescheduling of engineers, work already
done may have to be thrown out, hardware requirements may be effected, effects on other
projects etc.
Time pressures: scheduling of software projects is difficult at best, often requiring a lot of
guesswork. When deadlines loom and the crunch comes, mistakes will be made.
Egos: overconfidence and too many unrealistic promises result in bugs.
Poorly documented code: it is indeed difficult to maintain and modify code that is badly
written or poorly documented and will result in bugs.
Software development tools: visual tools, class libraries, scripting tools etc. often Introduce
their are bugs if not used correctly.
The most crucial part of the testing problem is finding an adequate test

Sample criteria for the selection of test data for test sets include:
1 The test data should reflect special properties of the domain such as external or
Singularities.
2 The test data should reflect special properties of the function that the program is
supposed to implement such as domain values leading to external function values.
3 He test data should exercise the program in a specific manner e.g. causing all Branches
to be executed or all statements to be executed.

- 28 -
 airlines booking

The properties that the test data set are to reflect are classified according to whether they
depend on the program' internal structure or the function the program is to perform.

General testing principles could be summarized as below-

1 Testing should be done in accordance with plans and procedures.
2 Generate test data at all stages, in particular earlier stages of the lifecycle.
3 Develop a means for calculating the expected values for test data to compare with test
Results.
4 Be systematic in the approach to testing
5 Test pieces then aggregate.
6 Save, organize and annotate test runs.
7 Test cases must be written for invalid and unexpected as well as valid and expected input
conditions.
8 Concentrate testing on modules that exhibit the most errors and on their interfaces.
9 Retest when modifications are made.
10 Discover and use available tools for testing.
11 Resolution of all non-conformances should take place prior to delivery.

Testing techniques

White-box Testing

1. Sending Mail independent paths within a module.

2. . Execute all loops at their boundaries and within their operational bounds.
3. Exercise internal data structure to ensure their validity.
In this project instead of conducting test at the end of the software

Black-box Testing
Black-Box Testing attempts to find errors in the following categories:
1. Incorrect or missing functions.

- 29 -
 airlines booking

2. Interface errors.
3. Errors in the data structure or external database access.
4. Performance errors.
5. Initialization and termination errors.
Each module was tested for its functional requirement by applying black box testing it was tested
to see if it perform all the desired function in the desired manner. This method divides the input
domain of a program into classes of data for which test case may be derived. All the output and
report were also checked and verified for their accuracy and reliability.

Testing strategies

A strategy for software testing may be viewed in the context of the life cycle phases. Errors
can crop up during any phase in the software development cycle. Though Verification is
performed on the output of each phase, some errors would remain Undetected and
eventually be reflected in the code. Testing is relied on to bring out these Errors. Unit
testing concentrates on each unit of the software as implemented in the Source code.
Testing progresses to integration testing where focus is on the design and Construction of
the software architecture. Functional testing concentrates on validating. The software
requirements against the software constructed. Finally, system testing relates to testing the
software and other system elements as a whole. Each of these tests attempts to detect
different types of faults.

Testing is planned and conducted at the various life cycle phases as follows:

Integration Testing This is the testing of combined parts of an application to determine

if they function together correctly. The parts can be code modules, individual applications
etc. The goal is to see if the modules can be integrated properly. Hence the emphasis is on
testing interfaces between modules.

Incremental Integration Testing conducts the testing on small segments, where errors are
easier to isolate and correct instead of testing the entire program as a whole. It involves the
continuous testing of an application as new functionality is added.

- 30 -
 airlines booking

Functional testing provides final assurance that the software meets all functional and
behavioral requirements. Black box testing techniques are used exclusively during this test.
System testing verifies that all elements of the whole computer system (hardware, people,
databases, software etc) mesh properly and that the overall system function and
performance is achieved. The reference document for this process is the requirements
document and the goal is to see if the software meets its requirements.

Test completion criteria

How do you know you have tested enough? This is a fundamental question and
unfortunately has no clear-cut answer. If you are still finding errors with every test, then
Testing should continue. In fact, errors tend to cluster and so the modules that appear error
prone should have special scrutiny.

Some basic criteria can be

(a) Stop when scheduled time for testing expires.
(b) Stop when all test cases execute without detecting errors.
However, these cannot be solely relied upon. If you have run your complete test set and
found no errors, it does not necessarily follow that the program is error free. The test set
may be incomplete. It should also be emphasized that the amount of testing will depend on
the cost of an error. Critical programs or code segments will require more thorough testing
than the more insignificant functions.

Paths: a routine with fewer paths is more testable than one with more paths. Jumping
Around within code, unnecessary GOTO, sharing code instead of using a subroutine or
Macro, all increase the complexity of the code.

Loops: simple, clear loops have explicit loop control variables and can be tested in a few
Cases. Cleanly nested loops can be tested in a finite number of combinations. Convoluted,
ad hoc loops cannot be simply tested.

- 31 -
 airlines booking

Logic-based: Simple IF-THEN_ELSE constructs and case statements or decision-table

based logic is explicit and easy to evaluate. The variables that direct the paths are Explicit
and identifiable. Complicated, ad-hoc logic can be a nightmare to disentangle.

Syntax: Clear separation of input validation into syntax, field-value and correlation
Analysis makes it possible to do syntax testing independent of field values and further
Processing. This separation modularizes testing and eliminates most of the complicated
interactions that would otherwise have to be tested.

Interfaces: Interfaces with standardized calling sequences make interface testing very
Straightforward. This makes interfaces clear and easily testable.

Integration: Small and single function modules are easier to test than big, multifunction
Ones. Well modularized code with clearly specified functions for each module means that
the program is made up of completely tested modules rather than partially tested
Elements, thus giving the program a sound base.

Specifications: Clearly documented specification for every element at every level is an

explicit guide not only to what must be implemented, but also to what must be tested.
Every specified requirement should be addressed by at least one test.

- 32 -
 airlines booking

Figure: Level of Testing

- 33 -
 airlines booking

Unit Testing:
After the coding step we do the unit test for project in this test we check the project as unit wise.
Full project is dividing into number of modules so we check every module separately in this
testing we use driver and stub mainly for testing.
Driver and stub are the software. In the application program driver is only as a main program and
stub is stub serve to replace modules that are subordinate the component to be tested.

Driver Interface
Driver Local data structure
Boundary condition
Independent paths
Error handling paths

Module
ModuleTo
To
Be
BeTested
Tested

Stub Stub

Test cases
Results

Fig: Unit test Procedure

- 34 -
 airlines booking

Tools and platform

Software:

12. Operating System: Windows 2000

13. GUI internet browser ( Like Internet Explorer or Netscape)
14. Development environment: MS Front Page 2000
15. Java Development Kit (JDK 1.3)
16. Tomcat Apache Web Server 4.1
17. MS Access 2000 (can be ported to any other database)

Programming Languages:

Java, JSP, HTML, DHTML, JavaScript

Hardware:

Minimum Hardware Requirement that can support GUI Internet browser and Windows 2000
Operating System

233 MHz Processor

64 MB RAM

Platform: Platform Independent need only GUI internet browser and web server to support JSP on
a particular platform.

Runtime Requirement:

9. Java Runtime Environment

10. Tomcat Apache Web Server
11. GUI internet browser
12. MS Access 2000

Client Side Requirements:

GUI internet browser

Server Side Requirements

4. Java Runtime Environment

5. Tomcat Apache Web Server
6. MS Access 2000

Database:

MS Access 2000

- 35 -
 airlines booking

Validation Checks
1. Registration Form

All the fields are compulsory except Contact No. The form validation will be done at client
side using JavaScript. The email id field must contain @ and . characters.

The form is also validated on the server side that the email address given by the students
should be unique. If the email address given by the student is already present in the
database then the information of the form is not stored in the database and appropriate error
message is given to the student.

2. Login Existing Account

Both the fields are compulsory i.e. Name and password.

The form is also validated on the server side for the correctness of Name and password. If
the validation passes the student gets the subject selection form, otherwise an appropriate
error message is shown.
3. Exit

Exit project.

- 36 -
 airlines booking

Code Efficiency

a. Optimization of Code
b. Cost Estimation of Project
2. Coding
3. Future Scope and Enhancements
4. Conclusion

- 37 -
 airlines booking

User Manual

- 38 -
 airlines booking

Important Instructions for installing and running the

project
1. Installing JDK1.3 or Higher Version

Double click the setup file of Java Development Kit (JDK). Click next and accept license
agreement. You can install JDK in given default folder or choose folder of your choice on
your machine e.g. C:\JDK1.3.

Click Next and follow step by step instructions. The Java Runtime Environment will also
be installed during the setup.

Click Finish when setup is complete.

2. Installing Tomcat4.1

Double click the setup file of Tomcat4.1. Click next and accept license agreement. You can
install Tomcat in given default folder or choose folder of your choice on your machine e.g.
C:\Tomcat4.1.

While installing you will be asked to choose the port number and administrative login and
password. The default port number is 8080. You can choose the default port number if no
other service is running on the same port, otherwise the port number can be changed.

The administrative login ID and password can also be chosen by you. For example you can
give admin as ID and password. This is also case sensitive.

Click Next and follow step by step instructions.

Click Finish when setup is complete.

3. Installing MS Access 2000 Database.

The database can be installed from MS Office 2000 Software CD.

- 39 -
 airlines booking

4. Copy OES folder from the CD in c:\Tomcat4.1\webapps\examples folder.

5. Create DSN called oes for

c:\Tomcat4.1\webapps\examples\cms\database\OnlineExam.mdb file.

6. Start Tomcat.

7. Open Internet Explorer and type http://localhost:8080/examples/oes/index.htm in address

bar to open the home page.

- 40 -
 airlines booking

Bibliography

S_no Book Title Author Publisher Edition

1. Core Java Volume -2 Cay S, Horst Mann Prentice Hall First Edition
2. Professional Java Worx SPD Publication Second Edition
Server Programming
3. The ABCs Of Java Script Purcell Mara BPB publication Second Edition
4. Java Script 1.0 Danesh Sams.Net First Edition
5. System Analysis & Design Elis M. Awad Galgotia publication Second Edition
6. Complete References Java 2 Herbert Shieldt Tata McGraw hill Fifth Edition
7. Professional SQL Server2000 Robert Vieira SPD Publication Fifth Edition
8 Java Server Pages Richard Monson- OREILLY 2nd Edition
Haefel
9. Web Publishing with HTML Laura Lemay Techmedia 2nd Edition
10. Pure JSP James Goodwill Techmedia 1st Edition
11. JavaScript Michael Moncur TechMedia 2nd Edition

- 41 -
 airlines booking

- 42 -
 airlines booking

- 43 -
 airlines booking

- 44 -
 airlines booking

- 45 -
 airlines booking

- 46 -
 airlines booking

- 47 -
 airlines booking

- 48 -
 airlines booking

- 49 -
 airlines booking

- 50 -
 airlines booking

- 51 -
 airlines booking

- 52 -
 airlines booking

- 53 -
 airlines booking

Partial Class _Default

Inherits System.Web.UI.Page

End Class

- 54 -
 airlines booking

Partial Class asp.net

Inherits System.Web.UI.Page

End Class

- 55 -
 airlines booking

Partial Class c
Inherits System.Web.UI.Page

End Class

- 56 -
 airlines booking

using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using
System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;

public partial class _Default :

System.Web.UI.Page
{
protected void Page_Load(object
sender, EventArgs e)
{

}
protected void
DropDownList1_SelectedIndexChanged(obje
ct sender, EventArgs e)
{

- 57 -
 airlines booking

}
protected void Button1_Click(object
sender, EventArgs e)
{
SqlConnection con = new
SqlConnection("server=(local);initial
catalog=man;integrated security=true");
con.Open();
SqlCommand cmd = new
SqlCommand("insert into man
values(@name,@age)", con);
cmd.Parameters.AddWithValue("@name",
TextBox1.Text);
cmd.Parameters.AddWithValue("@age",
TextBox2.Text);
cmd.ExecuteNonQuery();

}
}

- 58 -
 airlines booking

Imports System.Data.SqlClient
Partial Class _Default
Inherits System.Web.UI.Page

Protected Sub Button1_Click(ByVal

sender As Object, ByVal e As
System.EventArgs) Handles Button1.Click
Dim con As SqlConnection = New
SqlConnection("server=(local);initial
catalog=onlinetest;integrated
security=true")
con.Open()
Dim com As SqlCommand
com = New SqlCommand("select
name,pw,exd from studata1 where name=@n
and pw=@p", con)
com.Parameters.AddWithValue("@n",
TextBox1.Text)
com.Parameters.AddWithValue("@p",
TextBox2.Text)
Dim dr As SqlDataReader

- 59 -
 airlines booking

dr = com.ExecuteReader()
dr.Read()

If (dr.HasRows = True) Then

Session("user") =
TextBox1.Text
Response.Redirect("c.aspx")
Else
Response.Write("your
account has been wrong")
End If
End Sub
End Class

- 60 -
 airlines booking

Imports System.Data.SqlClient
Partial Class _Default
Inherits System.Web.UI.Page
Protected Sub Button1_Click(ByVal
sender As Object, ByVal e As
System.EventArgs) Handles Button1.Click
Dim con As SqlConnection
con = New
SqlConnection("server=(local);initial
catalog=onlinetest;integrated
security=true")
con.Open()
Dim com As SqlCommand
com = New SqlCommand("insert
into studata1
values(@name,@p,@fname,@age,@gen,@addr,
@email,@cont,@exd,@exf)", con)

- 61 -
 airlines booking

com.Parameters.AddWithValue("@name",
TextBox1.Text)
com.Parameters.AddWithValue("@fname",
TextBox2.Text)
com.Parameters.AddWithValue("@age",
TextBox3.Text)
com.Parameters.AddWithValue("@gen",
DropDownList1.SelectedItem.Text)
com.Parameters.AddWithValue("@addr",
TextBox4.Text)
com.Parameters.AddWithValue("@email",
TextBox5.Text)
com.Parameters.AddWithValue("@cont",
TextBox6.Text)
com.Parameters.AddWithValue("@exd",
DropDownList2.SelectedItem.Text)
com.Parameters.AddWithValue("@exf",
TextBox7.Text)
com.Parameters.AddWithValue("@p",
TextBox8.Text)
com.ExecuteNonQuery()
TextBox1.Text = ""

- 62 -
 airlines booking

TextBox2.Text = ""
TextBox3.Text = ""
DropDownList1.SelectedItem.Text
= ""
TextBox4.Text = ""
TextBox5.Text = ""
TextBox6.Text = ""
DropDownList2.SelectedItem.Text
= ""
TextBox7.Text = ""
End Sub

Protected Sub Page_Load(ByVal

sender As Object, ByVal e As
System.EventArgs) Handles Me.Load
Try
Dim con As SqlConnection =
New
SqlConnection("server=(local);initial
catalog=master;integrated
security=true")
con.Open()
Dim com As SqlCommand = New
SqlCommand("create database
onlinetest", con)

- 63 -
 airlines booking

com.ExecuteNonQuery()
Catch ex As Exception

End Try
Try
Dim con As SqlConnection =
New
SqlConnection("server=(local);initial
catalog=onlinetest;integrated
security=true")
con.Open()
Dim com As SqlCommand = New
SqlCommand("create table studata1(name
varchar(20),pw varchar(40),fname
varchar(40),age varchar(40),gen
varchar(15),addr varchar(20),email
varchar(20),cont varchar(20),exd
varchar(20),exf varchar(20))", con)
com.ExecuteNonQuery()
con.Close()
Catch ex As Exception

End Try
End Sub
End Class

- 64 -
 airlines booking

CONCLUSION:

To work on any project work, is really very enjoying and memorable experience of engineering
life. I faced many problems related to database and the network and I really solve this problem.

Though I succeed in making the application of online restaurant management. It still can be
enhanced or the process of developing software can be make smoother.

The following features can be implemented to add more functionality to the application

To add the map facility so that the user need not remember the station names, the train name and
the nos.

Adding the features for the via stations. One can see the information of the via stations.

- 65 -
 airlines booking

Testing Strategy

Introduction
Software Testing uncovers errors in the software. It is a crucial element of
software quality assurance and represents the ultimate review of specification,
design and coding. Testing demonstrate that software function appeared to be
working according to specification that performance requirements appear to
have been met. In addition data collected as is conducted provide a good
indication of software reliability and with some indication of software quality
as a whole. The basic objectives of testing process are:
1. Testing is a process of executing a program with the intent of finding an
error.
2. A good test case is one that has a probability of finding an as yet
undiscovered error.

Testing Principles

Software testing verifies that the software meets the requirements. It involves
the operation of a system or application under controlled conditions and
evaluating the results. The controlled conditions include both normal and
abnormal conditions. Testing is done with the intention of finding errors. We
should not test a program to show that it works, but to find the maximum
number of errors possible. We begin testing with the assumption that it
contains errors. Testing should intentionally attempt to make things go wrong
and then observe the behavior of the product in those conditions.

- 66 -
 airlines booking

A good understanding of the reasons for errors would enable the development
of quality assurance plans with insight. Now, why does software have errors
or bugs?
Miscommunication or no communication: as to specifics of what an
application should or shouldnt do, the applications requirements.
Software complexity: the complexity of current software applications can be
difficult to comprehend for anyone without experience in modern day
software development.
Windows-type interfaces, client-server and distributed applications, data
communications, enormous relational databases and sheer size of applications
have all contributed to the exponential growth in software/system complexity.
The use of object-oriented techniques can complicate instead of simplifying a
project unless it is well engineered.
Programming errors: programmers like anyone else can make a mistake.
Changing requirements: the customer may not understand the effects of
changes, or may understand and request them anyway redesign,
rescheduling of engineers, work already done may have to be thrown out,
hardware requirements may be effected, effects on other projects etc.
Time pressures: scheduling of software projects is difficult at best, often
requiring a lot of guesswork. When deadlines loom and the crunch comes,
mistakes will be made.
Egos: overconfidence and too many unrealistic promises result in bugs.
Poorly documented code: it is indeed difficult to maintain and modify code
that is badly written or poorly documented and will result in bugs.
Software development tools: visual tools, class libraries, scripting tools etc.
often Introduce their are bugs if not used correctly.

- 67 -
 airlines booking

The most crucial part of the testing problem is finding an adequate test

Sample criteria for the selection of test data for test sets include:
1 The test data should reflect special properties of the domain such as external
or Singularities.
2 The test data should reflect special properties of the function that the
program is supposed to implement such as domain values leading to external
function values.
3 He test data should exercise the program in a specific manner e.g. causing
all Branches to be executed or all statements to be executed.
The properties that the test data set are to reflect are classified according to
whether they depend on the program' internal structure or the function the
program is to perform.

General testing principles could be summarized as below-

1 Testing should be done in accordance with plans and procedures.
2 Generate test data at all stages, in particular earlier stages of the lifecycle.
3 Develop a means for calculating the expected values for test data to compare
with test Results.
4 Be systematic in the approach to testing
5 Test pieces then aggregate.
6 Save, organize and annotate test runs.
7 Test cases must be written for invalid and unexpected as well as valid and
expected input conditions.
8 Concentrate testing on modules that exhibit the most errors and on their
interfaces.
9 Retest when modifications are made.

- 68 -
 airlines booking

10 Discover and use available tools for testing.

11 Resolution of all non-conformances should take place prior to delivery.

Testing techniques

White-box Testing

1. Examines all independent paths within a module.

2. Examines all logical decision on their true & false sides.
3. Execute all loops at their boundaries and within their operational
bounds.
4. Exercise internal data structure to ensure their validity.
In this project instead of conducting test at the end of the software

Black-box Testing
Black-Box Testing attempts to find errors in the following categories:
1. Incorrect or missing functions.
2. Interface errors.
3. Errors in the data structure or external database access.
4. Performance errors.
5. Initialization and termination errors.
Each module was tested for its functional requirement by applying black box testing
it was tested to see if it perform all the desired function in the desired manner. This
method divides the input domain of a program into classes of data for which test
case may be derived. All the output and report were also checked and verified for
their accuracy and reliability.

- 69 -
 airlines booking

Testing strategies
A strategy for software testing may be viewed in the context of the life cycle
phases. Errors can crop up during any phase in the software development
cycle. Though Verification is performed on the output of each phase, some
errors would remain Undetected and eventually be reflected in the code.
Testing is relied on to bring out these Errors. Unit testing concentrates on
each unit of the software as implemented in the Source code. Testing
progresses to integration testing where focus is on the design and Construction
of the software architecture. Functional testing concentrates on validating. The
software requirements against the software constructed. Finally, system testing
relates to testing the software and other system elements as a whole. Each of
these tests attempts to detect different types of faults.

Testing is planned and conducted at the various life cycle phases as follows:

Integration Testing This is the testing of combined parts of an application

to determine if they function together correctly. The parts can be code
modules, individual applications etc. The goal is to see if the modules can be
integrated properly. Hence the emphasis is on testing interfaces between
modules.

Incremental Integration Testing conducts the testing on small segments,

where errors are easier to isolate and correct instead of testing the entire
program as a whole. It involves the continuous testing of an application as
new functionality is added.

- 70 -
 airlines booking

Functional testing provides final assurance that the software meets all
functional and behavioral requirements. Black box testing techniques are
used exclusively during this test.
System testing verifies that all elements of the whole computer system
(hardware, people, databases, software etc) mesh properly and that the overall
system function and performance is achieved. The reference document for this
process is the requirements document and the goal is to see if the software
meets its requirements.

Test completion criteria

How do you know you have tested enough? This is a fundamental question
and unfortunately has no clear-cut answer. If you are still finding errors with
every test, then Testing should continue. In fact, errors tend to cluster and so
the modules that appear error prone should have special scrutiny.

Some basic criteria can be

(a) Stop when scheduled time for testing expires.
(b) Stop when all test cases execute without detecting errors.
However, these cannot be solely relied upon. If you have run your complete
test set and found no errors, it does not necessarily follow that the program is
error free. The test set may be incomplete. It should also be emphasized that
the amount of testing will depend on the cost of an error. Critical programs or
code segments will require more thorough testing than the more insignificant
functions.

- 71 -
 airlines booking

Paths: a routine with fewer paths is more testable than one with more paths.

Jumping Around within code, unnecessary GOTO, sharing code instead of

using a subroutine or Macro, all increase the complexity of the code.

Loops: simple, clear loops have explicit loop control variables and can be

tested in a few Cases. Cleanly nested loops can be tested in a finite number of
combinations. Convoluted, ad hoc loops cannot be simply tested.
Logic-based: Simple IF-THEN_ELSE constructs and case statements or

decision-table based logic is explicit and easy to evaluate. The variables that
direct the paths are Explicit and identifiable. Complicated, ad-hoc logic can be
a nightmare to disentangle.

Syntax: Clear separation of input validation into syntax, field-value and

correlation Analysis makes it possible to do syntax testing independent of

field values and further Processing. This separation modularizes testing and
eliminates most of the complicated interactions that would otherwise have to
be tested.

Interfaces: Interfaces with standardized calling sequences make interface

testing very Straightforward. This makes interfaces clear and easily testable.

Integration: Small and single function modules are easier to test than big,

multifunction Ones. Well modularized code with clearly specified functions

for each module means that the program is made up of completely tested
modules rather than partially tested
Elements, thus giving the program a sound base.

- 72 -
 airlines booking

Specifications: Clearly documented specification for every element at every

level is an explicit guide not only to what must be implemented, but also to
what must be tested. Every specified requirement should be addressed by at
least one test.

Figure: Level of Testing

Unit Testing:
After the coding step we do the unit test for project in this test we check the project as unit wise.
Full project is dividing into number of modules so we check every module separately in this
testing we use driver and stub mainly for testing.
Driver and stub are the software. In the application program driver is only as a main program and
stub is stub serve to replace modules that are subordinate the component to be tested.

- 73 -
 airlines booking

System Analysis

It involves trading requirment of present system whether it is manual or computerized.If it is computerized

then what are the loopholes of the present system and if it is not computerized then whether it need
computerization or not.

Some of them point involves in the system analysis are as follows:

.
If current system is computerized than why change in system is needed ?
Whether a system become allright or it will suffice the need of user after making
current to it or development of new system is required ?
What are the various jobs that will be performed by the system ?
If the present system is manual then is it feasible to make it computerized ?

System study is done in the organization itself by collecting various information

from level of organization.

System analysis is concluded to achieve the following objective:

Identification of user need.

Determine system feasibility (feasibility study)
Perform economic and technical feasibility analysis.
Establishment of cost and schedule constraints.
Allocation of function to hardware, software, people and other system components.

Identification of Need

The first step in the development of computer based system is identified the need of the
organization. It defines what kind of information is required as decision point. It also describes the
mechanism of inputs and outputs of the system. At this stage the main objectives is to gather
information from different level of organization various manual reports and input type are studied
at this stage

This phase of software development is also known as requirement specification. Online trading
system is in demand these days by various stock exchanges. The traditional trading system is
manual system and user have to go to exchange for get information traditional trading system user

- 74 -
 airlines booking

have to contact with brokers. This requires a lot of paper work to be done. Before times there are
only four center of shares trading in all of India and user has contact with direct company or
brocker or newspaper but in that process user cant get direct information if any user is so far from
centers and user wants real information about it but its not possible there but now there are online
trading software available by these softwares any user can get direct real information
For this softwares you have to need lan or internet its provide online service and connect with
world wide servers

Prelimnary investigation
This stage is the preliminary of study of the system .This phase involves the detailed evaluation
of the present system.So the following step were followed:

Requirement specification:

In this phase ,mainly data collection was done.Through asking ,questionnaires,

on site observation, procedures, and manuals the users requirement were
determined. This helped to understand the acts and functioning of
system. Through this procedure we identified the requirement of the user and
identified the need of the system requirements .This phase are complete asking
and observation of the system and also study of the manual system. What are
the manual system ? and what are the system works has been done ?In study of
the present system and observe its drawbacks of the present system.In this
phase these task are complete through study of the systems,So this stage is the
first stage of the development of the automated system.

Structure analysis:

The structured analysis helped us to develop a new kind of system

specifications.through logical models,like data flow dictionary.This formed
the basis of designing and implementation.For structure analysis there are
following tools and techniques.

Data flow diagram

Data dictionary

- 75 -
 airlines booking

Decision trees
Decision tables

- 76 -
 airlines booking

Anyalysis of feasibility

At the end of information gathering phase,we have an idea of the data available currently and deficiencies
of the current system.We also come to know the priorities and requirements .It is necessary to quantify the
goals and subgoals and objective.Once these goals are defined then logically thinking is done,how to meet
the objective and at what cost they are achieved.

Feasibility study is the evaluation of the candidate system.Before we go to further steps

of development,whether it is technically ,and economically feasible.So for evaluating this ,we
followed these steps:

We studied the system and understood,What the problem is. ?

Several alternatives were chosen for the benefit of the user and cost and saving were
also calculated for those alternatives.
After all this,we had to check for the technical and economical feasibility

The prime focus of the feasibility study is evaluating the practicality of the proposed system
keeping in mind a number of factors. The following factors are taken into account before deciding
in favor of the new system: -
Economic Feasibility
In this cost/benefit analysis is done for estimating cost ,we had to consider several cost elements,
like hardware ,personnel , facility, operating supply costs. After that we assigned a monetary value
to each benefit was accuracy of the access to information. Therefore the system was found to be
economically feasible.

Economical feasible analysis is done in order to ensure that the system is economically viable. It is
also done to get an idea that it is possible to develop the system within organizational functional
limit.. A cost and benefit analysis is to find out whether it is economically feasible to invest for the
project. Computing these two gives an argument either in favor of system or against the proposed
system.

- 77 -
 airlines booking

Cost of both types Direct and indirect considered. Direct cost are those incurred in buying the
equipment, employing people, cost of consumable item, rent for accommodation for system
developers etc. indirect cost involves brain storming time spent by in discussing problem with the
system analyst, effort in gathering data etc. benefits can be broadly classified as tangible and
intangible benefit. Tangible benefit are directly measurable e.g. saving money by reducing is
improved working environment, better management of resources, timely information flow,
decision support, effective report generation.

The sum of all cost-producing components is compared with the sum of

total saving or benefit. If it worthwhile to carry out to the project
economically then further step for the system development are taken

The proposed Online Examination system will save lots of paper work and
Facilitate automates examination process there by reducing the costs incurred
on above described heads. This reduction in cost prompts the educational
institutions to go for such computer-based system.
Technical Feasibility
In this, technical aspects of the computer system were checked. The main aspects are
hardware and software. The system already have enough hardware and software and
memory, so the chances of overloading the system were less and it was under budget to
accommodate the technical enhancements.

During technical feasibility analysis the analyst evaluate the technical merit of the concept,
while at the same time it collect the information about the performance(system throughput,
turn around time etc.), reliability, maintainability, and productivity of the system.

Technical feasibility analysis begins with an assessment of the technical

viability of proposed system. It is analyzed that what kind of environment,
process and method required to accomplished the system. A general logical

- 78 -
 airlines booking

model I prepared which resemble to the real world and shows the various
components and their role in the system. A solution is technically feasible, if
technology is available to implement the logical design of the system as we
are provided sufficient technical support, we do not have technical feasibility
problem

As the saying goes, "to err is human". Keeping in view the above fact, Now-a-
days all organizations are automating the repetitive and monotonous works
done by humans. The key process areas of current system are nicely amenable
to automation and hence the technical feasibility is proved beyond doubt.

Operational Feasibility
Operational feasibility analysis is done with an objective of finding the impact of the systemof management
and employees in organization .If the system is operationally feasible the management and user both
welcome theproposal of development of the new system.In this the evaluation of satisfactionof the users is
done.Since our system was very much user friendly and flexible so we estimated that the reaction of the
user staff will be positive .hence we stepped further.

Prepared a statement of objective and scope.

Prepared the generalization flowcharts ,describing the inputs and outputs and dataflow
diagram,describing the key points the system, being made.

We checked for different aspect of the hardware ,like processing and memory.
After considering the cost and performance of different alternatives,it was clear that
proposed system was feasible and further analysis can be done.

An operational feasibility system requires :

- 79 -
 airlines booking

Minimum paper work .

More users friendly
Reduce transaction time

The manual examination system is error prone and time-consuming. The checking of answer sheets
involve human element and is based on human judgment. The computerization will not only
increase the operational efficiency of the work but also result in safety and accuracy because of
little human intervention.
Time and Resource Feasibility
This system helps the users and institutions to find in the best usage of resources
keeping in track of all the database information. A lot of time is saved due to automatic
report generation process. Otherwise the manual process of report generation is time
consuming and costly. The process saves a lot of time and resources.

- 80 -