A

Project
Report
On
“AIR LINES RESERVATION
SYSTEM”

Bachelors in Computer
Applications

TABLE OF CONTENTS
CERTIFICATE..............................................................................................................................3
ACKNOWLEDGEMENT..............................................................................................................4
TABLE OF CONTENTS...............................................................................................................6
INTRODUCTION..........................................................................................................................7
OBJECTIVES................................................................................................................................8
SYSTEM ANALYSIS...................................................................................................................10
SYSTEM ANALYSIS...................................................................................................................11
FEASIBILITY STUDY................................................................................................................14
1.Technical Feasibility:...............................................................................................................14
PLATFORM USED.....................................................................................................................18
PROJECT ANALYSIS................................................................................................................20
RISK ANALYSIS.........................................................................................................................25
OJBECT ORIENTED DEVELOPMENT..................................................................................26
WORK FLOW THE PROJECT..................................................................................................27
FEASIBILITY STUDY................................................................................................................28
TYPE OF FEASIBILITIES........................................................................................................29
SYSTEM DESIGN.......................................................................................................................33
PROJECT DESIGN....................................................................................................................40
TABLE STRUCTURE.................................................................................................................45
1. CUSTOMER.DAT (Stores all information for customers)....................................................45
2. STATION.DAT (Stores all information for Stations)............................................................46
PROGRAM STRUCTURE..........................................................................................................47
FLOW CHART............................................................................................................................49
DFD..............................................................................................................................................62
Data Flow Diagram.....................................................................................................................66
PROJECT CODE – AIRLINE RESERVATION SYSTEM......................................................69
SOFTWARE TESTING & IMPLIMENTATION:..................................................................100
Validation testing:......................................................................................................................102
ALPHA TESTING:....................................................................................................................102
IMPLEMENTATION................................................................................................................105
SYSTEM SECURITY MEASURES..........................................................................................107
PERT chart and GANTT chart.................................................................................................109
FUTURE SCOPE OF THE PROJECT....................................................................................111
REFERENCES..........................................................................................................................112

INTRODUCTION

Project name is “Air Lines Reservation System”.

The project is very flexible and it can be modified if the need

arises. I hope the user will find this project work quite pleasing in
its output as general sample designing has been done to enhance
the view and simple programming statement and commands have
been made use of, so that the user had no problem in
understanding the listing of the project. Files have been used to
create a systematic medium of data storage and retrieval.

I am sure that reader will like this effort and so, I wished
him/her by hearts to ahead and turn this page.

OBJECTIVES

Airways has a number of reservation offices in each city where the flights
operate. Each reservation office has a number of reservation counters to handle
reservations and cancellations. Each counter has a counter assistant who is
responsible for making reservations or cancellations. The main objective of
this project to performed reservation, cancellation and report.
In concerned to reservations, the following activities are done.
 Accepts the date, sector, and class of travel from the person and checks
for the availability of a seat in the Reservation file.
 Confirms the details with the prospective passenger and accepts the
remaining details.
 Update the seat availability status in the reservation file and adds the
passenger details to the file. The passenger is assigned a unique
Passenger Name Request (PNR) number,
 Collects the fare amount.
 Update the Daily Collection file with the fare amount.
In concerned to cancellation, the following activities is done
Retrieves the details from the file using the PNR number.
Verifies the details of the ticket and computes the refund amount.
Updates the seat availability status in the reservations file and marks the
corresponding details of the file.
Makes the refund and prints the refund receipt.
 Files the receipt along with the signature of the passenger .
Updates the Daily Collection file.

And Reports are generated as:-

 Print the confirmed and wait-listed passenger list of flights departing .
 Print the daily collection summary report.
 It also generate view rates for different sector & view flight schedules
for a specific period
 Show status of ticket with given PNR number.

 Report on availability of flight & seats on desired date.

SYSTEM ANALYSIS

 Introduction of User

 Definition of System

 Identification of Need

 Preliminary Investigation

 Modules in AIR-LINES RESERVATION SYSTEM.

SYSTEM ANALYSIS
 Analysis is a detailed study of the various operations performed by a
system and their relation within and outside the system. A key question is what
must be done to solve the problem. One aspect of the analysis defining the
boundaries of the system and determining whether or not a candidate system
should consider other related system. During analysis data are collected on the
available files decision points and transaction handled by the parent system.
Some logical system models and tools are used in the analysis. Data flow
diagrams, interviews, onsite observation and questionnaires are examples, the
interview is commonly used in analysis. It requires special skill and sensitivity
to the subject being interview bias in data collection and interpretation can be
problem.
Training experience and common sense are required for Collections of the
information are needed to do analysis. Once analysis is completed, the analyst
has firm understanding of what is to be done. The next step is to decide how
the problem might be solved. Thus in system design, we be move from the
logical to the physical aspects of the life cycle.

The Initial Investigation and Identification of need :

The most critical phase of managing system projects is planning to launch

a system investigation, we need plan detailing the steps to be taken, the people
to be questioned and they out come expected. The initial investigation has the
objective of determining whether the users request has potential merit. The
major steps are defining user requirements. When the initial investigation is
completed. The user receives a proposal summarizing the finding the
recommendation of the analyst.
A key part of feasibility analysis is gathering information about the
present system. The analyst knows what information to gather, where to find it,
how to collect it and what to make of it. The proper use of tools for gathering
information is the key to successful analysis. The tools are the traditional
interview, questionnaire, and on-site observation. We need to know, for
example how to structure an interview, what makes up a questionnaire, and
what to look for on-site observations. These tools when learned help analysis
assess the effectiveness of the present system and provide the groundwork for
recommending a candidate system.

Identification of need
The system need accomplish the following functions:

 The system should allow the counter assistants to handle ticketing and
refunds.
 While accepting reservation data, all necessary validations should be
performed. For example, the system should check whether a flight
operates on the date of travel specified by the passenger. It should also
check the seat availability status. After all data has accepted, the system
should print the ticket. It should also store the passenger details, update
the daily collections, and update the seat plan.
 In case of cancellation, the system should accept the PNR number from
the user, validate the PNR number and update the cancellation flag for
the passenger. The system should then print the refund receipt. It should
also update the daily collections to reflect the refund amount. The status
of overbooked and wait-listed tickets should be changed whenever a
confirmed ticket is cancelled.
 The system should generate the following reports:

1. Confirmed passenger list

2. Waiting list
3. Daily collection report

In addition, the new system should provide facilitate passengers to perform the
following tasks:
 Check the waiting list status.
 View rates for different sectors.
  View flight schedules for a specific period. This module should be
developed as an affiliate program that can be easily integrated with
various Web sites.

FEASIBILITY STUDY

The main objective of the preliminary analysis is to

identify the problem, evaluate the system concept of
feasibility, and perform the economic and technical
analyses perform the cost benefit analysis. After the
clarification analysis the solution

proposed it is checked that it is practical to implement that solution. This is

done through the feasibility study. It is checked for various aspects whether
the proposed solution is technically or economically feasible or not. On the
basis if which it has been categorized into four classes viz

1.) Technical

2.) Economic

3.) Operational

The outcome of the preliminary analysis should be clear so that an alternate

way to do the job can be found out?
1.Technical Feasibility:

During the technical feasibility studies following issues are taken into
consideration

1. Whether the required technology is available or not?

2. Required resources are available or not? (Manpower, programmer,

software and hardware etc)

Once the technical feasibility is established, it is important to

consider the monetary factors also. Since it might happen that developing a
 particular system may be technically possible but it may be require huge
investments and benefits may be less. For evaluating this, economic
feasibility of the proposed system is carried out.
As in our proposed system our team has technically trained
manpower with knowledge of developing the system. We are going to use
web technology in our system, which is readily available. Software to be
used is also available easily.
So technically the project is feasible.

2. Economic Feasibility:
For any system if the expected benefits equal or exceed the expected
costs, the system can be judged to be economically feasible. In economic
feasibility, cost benefit analysis is done in which expected costs and
benefits are evaluated.
Economic analysis is used for evaluating the effectiveness of the proposed
system. In economic feasibility, the most important is cost benefit analysis.
As the name suggests, it is an analysis of the cost to be incurred in the
system and benefits derivable out of the system.
As in our institute the hardware and software required for this type of
system is already available so economically our project is feasible.
3. Operational Feasibility

The staff of the company (client) is used to the computer. They will only
be given training about the proposed system to make efficient use of it.
This feasibility study is carried out by a small group of people who are
familiar with information system techniques, who understand the part of
the system that are relevant to the project and are skilled in system
analysis and design process.
Considering the above three feasibility we can say that the system is
feasible and ahead for analysis of the system.
 In the software principle we are using the incremental model (evolutionary

software process model). The incremental model combines elements of the

linear sequential model with the iterative philosophy of prototyping.

The linear sequential model suggests a systemic, sequential approach to

software development that begins at the system level and progress through
analysis, design, coding and module testing, delivery and maintenance.
ANALYSIS:
In this phase we will gathered all the information about the organization
queries and analysis requirement for both the system and software
documented and reviewed with the users.
DESIGN:
After analysis we documented all the Interface representations, and algorithm
details.
CODING AND MODULE TESTING:
After designing, coding plays major role in software development process.
We are using JAVA(JSP) in front end, ORACLE in the back end for coding
Individual modules developed in this phase is also tested before being
delivered to the program testing phase.
PROGRAM TESTING:
Once the module has been developed. Program testing begins We will
provide some other users for testing for few days, and all problems and errors,
which overcome during testing, will be pointed out. The user requirement will
be also kept in mind and then delivery process begins.
DELIVERY:
Once the system passes all the tests, it is delivered to the customer and enters
the maintenance phase.
MAINTENANCE:
Software will undoubtedly undergo changes because errors have been
encountered. So keeping requirement and testing in mind, we will make some
necessary changes.

PLATFORM USED

Hardware Requirement

1. Pentium Processor or above

2. Color Monitor

3. Keyboard

4. 8 GB Hard Disk or above

5. 32 MB RAM or above

6. 1.44 MB Floppy Disk Drive

7. Speakers

Software Requirement
 1. Windows 9x or MS-DOS 6.22

2. Turbo C++ Compiler

3. Turbo C++ Editor or any other text editor

PROJECT ANALYSIS

(OOPS – Object Oriented Programming System)

Object Oriented Programming is a method of programming that seeks to mimic

the way we form models of the world. To cope with the complexities of life,

we have evolved a wonderful capacity to generalize, classify and generate

abstractions. Almost every noun in our vocabulary represents a class of objects

sharing some set of attributes or behavioral traits.

The entire basis of Object Oriented Programming, infect is defining the Object

in Object Oriented Programming. Object is a unit that combines both code and

data together. And an object is an instance of a class. Class is a type of data

structure defined to hold both data and the code functions.

Object Oriented Programming also allows you to design and implement your

application more quickly than traditional approaches. Object Oriented

Programming also makes code easier to maintain so that you can refine the

implementation without causing major problems.

Since object-oriented programming was fundamental to the development of C+

+, it

is important to define precisely what object-oriented programming is. Object-

oriented

programming has taken the best ideas of structured programming and has

combined

them with several powerful concepts that allow you to organize your programs

more

effectively. In general, when programming in an object-oriented fashion, you

decompose

a problem into its constituent parts. Each component becomes a self-contained

object

that contains its own instructions and data related to that object. Through this

process,

complexity is reduced and you can manage larger programs.

Encapsulation

As you probably know, all programs are composed of two fundamental

elements:

program statements (code) and data. Code is that part of a program that

performs

actions, and data is the information affected by those actions. Encapsulation is

programming mechanism that binds together code and the data it manipulates,
and that keeps both safe from outside interference and misuse.

Polymorphism

Polymorphism (from the Greek, meaning “many forms”) is the quality that

allows one

interface to be used for a general class of actions. The specific action is

determined by

the exact nature of the situation. A simple example of polymorphism is found

in the

Steering wheel of an automobile. The steering wheel (i.e., the interface) is the

same no

matter what type of actual steering mechanism is used. That is, the steering

wheel works

the same whether your car has manual steering, power steering, or rack-and-

pinion

steering. Therefore, once you know how to operate the steering wheel, you can

drive

any type of car. The same principle can also apply to programming. For

example, consider

a stack (which is a first-in, last-out list). You might have a program that

requires three

different types of stacks. One stack is used for integer values, one for floating-

point
values, and one for characters. In this case, the algorithm that implements each

stack

is the same, even though the data being stored differs. In a non-object-oriented

language,

you would be required to create three different sets of stack routines, calling

each set

by a different name, with each set having its own interface. However, because

of

polymorphism, in C++ you can create one general set of stack routines (one

interface)

that works for all three specific situations. This way, once you know how to use

one

stack, you can use them all.

Inheritance

Inheritance is the process by which one object can acquire the properties of another

object. The reason this is important is that it supports the concept of hierarchical

classification. If you think about it, most knowledge is made manageable by

hierarchical (i.e., top-down) classifications. For example, a Red Delicious apple is

part

of the classification apple, which in turn is part of the fruit class, which is under the

larger class food. That is, the food class possesses certain qualities (edible, nutritious,

etc.) that also apply, logically, to its fruit subclass. In addition to these qualities, the

fruit class has specific characteristics (juicy, sweet, etc.) that distinguish it from other

food. The apple class defines those qualities specific to an apple (grows on trees, not
tropical, etc.). A Red Delicious apple would, in turn, inherit all the qualities of all

preceding classes, and would define only those qualities that make it unique.

Without the use of hierarchies, each object would have to explicitly define all of

its characteristics. However, using inheritance, an object needs to define only those

qualities that make it unique within its class. It can inherit its general attributes from

its parent. Thus, it is the inheritance mechanism that makes it possible for one object

to be a specific instance of a more general case.

C++ Implements OOP

As you will see as you progress through this book, many of the features of C++ exist

to provide support for encapsulation, polymorphism, and inheritance. Remember,

however, that you can use C++ to write any type of program, using any type of

approach. The fact that C++ supports object-oriented programming does not mean

that you can only write object-oriented programs. As with its predecessor, C, one of

C++’s strongest advantages is its flexibility.

RISK ANALYSIS

Project Risk: It identify potential budgetary, schedule, personnel,

resource, customer, and requirements problems and their impact on

software. All the above factors are analyzed, customer requirements are

analyzed properly.
Technical Risk: It identifies potential design, implementation, interface,

verification, and maintenance problems. All the above factors have been

analyzed.

Business Risk: (1) Software is developed keeping in mind that there is

demand in custom, so that to avoid the market risk. (2) Software is

designed to fit into the overall business strategy for the custom

department, to avoid the strategic risk. (3) The software is easily

understandable by the sales person’s team, so that they could know

much about the product working and sell in the market. (4) It has the

strong management support, and not likely to change in the

management people to avoid the management risk. (5) Software fits the

budget and there is no budget risk.

 OJBECT ORIENTED DEVELOPMENT
An object-oriented system draws upon class definitions that are derived
from the analysis model. Some of these definitions will have to be built
from scratch, but many others may be reused it appropriate design
patterns are recognized. Object Oriented Design establishes a design
blueprint that enables a software engineer to define the Object Oriented
architecture in a manner that maximized reuse, thereby improving
development speed and end-product quality.
The four layers of the Object Oriented design are:
The subsystem layer: It represents each of the subsystems that enable the
software to achieve its customer-defined requirements and to implement
the technical infrastructure that supports customer requirements, in the
custom department.

The class and object layer: It contains the class hierarchies that enable the
system to be created using generalizations and increasingly more targeted
specializations.

The message layer: It contains the design details that enable each object
to communicate with its collaborators. This layer establishes the external
and inters interfaces for the software.

SYSTEM DESIGN

Introduction

System design provides the understandings and procedural details

necessary for implementing the system recommended in the system study.
Emphasis is on the translating the performance requirements into design
specifications. The design has is a transition from a user-oriented document
(System proposal) to a document oriented to the programmers or database
personnel.

System design goes through two phases of development:

1) Logical Design

2) Physical Design

A data flow diagram shows the logical flow of the system. For a system
it describes the input (source), output (destination), FILE (data stores) and
procedures (data flows) all in a format that meets the user’s requirement. When
analysis prepare the logical system design, they specify the user needs at a level
of detail that virtually determines the information flow into an out of the
system and the required data resources. The logical design also specifies input
forms and screen layouts.

The activities following logical design are the procedure followed in the
physical design e.g., producing programs, software, file and a working system.
Design specifications instruct the user about what the system should do.

Logical and Output Design:

The logical design of an information system is analogous to an

engineering blue print of an automobile. It shows the major features and how
they are related to one another. The detailed specification for the new system
was drawn on the bases of user’s requirement data. The outputs inputs and
databases are designed in this phase.

Output design is one of the most important features of the information

system. When the output is not of good quality the users will be averse to use
the newly designed system and may not use the system. There are many types
of output, all of which can be either highly useful or can be critical to the users,
depending on the manner and degree to which they are used.
 Outputs from computer system are required primarily to communicate
the results of processing to users; they are also used to provide a permanent
hard copy of these results for later consultation. Various types of outputs
required can be listed as below:

 External Outputs, whose destination is outside the organization

 Internal outputs, whose destination is with the organization

 Operational outputs, whose use is purely with in the computer

department e.g., program-listing etc.

 Interactive outputs, which involve the user is communicating

directly with the computer, It is particularly important to consider
human factor when designing computer outputs. End user must find
outputs easy to use and useful to their jobs, without quality output,
user may find the entire system unnecessary and avoid using it. The
term “Output” in any information system may apply to either
printer or displayed information. During the designing the output
for this system, it was taken into consideration, whether the
information to be presented in the form of query of report or to
create documents etc.

Other important factors that were taken into consideration are:

 The End user, who will use the output.

 The actual usage of the planned information

 The information that is necessary for presentation

 When and how often output and their format is needed. While
designing output for project based Attendance Compilation System,
the following aspects of outputs designing were taken into
consideration.

 The outputs (i.e., well formatted table outputs in the screen itself)
designed are simple to read and interpret.
  Format of each output was another important point taken into
consideration. Output media, for each output appropriate media is
decided whether it will be displayed on screen or will be taken to
printer or both.

 Other output design related specifications, i.e., how frequently the

outputs will be generated, how many pages or sheets approximately
it will keep up, what is its planned use and output distribution to
users are also taken into account.

Output Sources:

Output contents originate from these sources:

 Retrieval from a data source.

 Transmission from a process or system activity.

 Directly from an input source.

The information produced in an output can be presented as

 Tabular contents

 Graphic format

 Using Icons

Output Definition:

The output should be defined in terms of:

Types of outputs

 Content-headings, numeric, alphanumeric, etc.,

 Format-hardcopy, screen, microfilm, etc.,

 Location-local, remote, transmitted, etc.,

 Frequency-daily, weekly, hourly, etc.,

 Response-immediate with in a period, etc.,

Data items

The name given to each data item should be recorded and its characteristics
described clearly in a standard form:

 Whether alphanumeric or numeric

 Legitimate and specific range of characteristics

 Number of characters

 Positions of decimal point, arithmetic design, etc.,

Input Design:

The input design is the link that ties the information system into the user’s
world. Input specifications describe the manner in which data enters the system
for processing. Input design features can ensure the reliability of the system
and produce results from accurate data, or they can result in the production of
erroneous information.

Input Design consists of

 developing specifications and procedures for data preparation

 Steps necessary to put data into a usable form for processing.

 Data entry, the activity of putting data into the computer

processing.

Objectives of Input design

Five objectives of design input focus on

 Controlling the amount of input required

 Avoid delay

 Avoiding errors in data

  Avoiding extra steps.

 Keeping the process simple.

PROJECT DESIGN

Modules & Process logic

Airways has a number of reservation offices in each city where the flights
operate. Each reservation office has a number of reservation counters to handle
reservations and cancellations. Each counter has a counter assistant who is
responsible for making reservations or cancellations. The procedure followed
for performing reservations and cancellations is given bellow.

Reservation
Reservations for a flight commence 30 days before the date of the flight. The
procedure for making reservations is given below. The procedure described
below deals with the provisional reservations the can be made through
telephone conversation.
On receiving request for reservation from a person, the counter assistant
performs the following activities:
 Accepts the date, sector, and class of travel from the person and checks
for the availability of a seat on the requested date. The details about the
availability seats and the seat plan are kept in the Reservation file.
 Confirms the details with the prospective passenger and accepts the
remaining details. These details include the preferences such as a
window or an aisle seat, a smoking or a non-smoking zone, meal
preferences such as vegetarian or non-vegetarian, and special service
requests (SSR), such as dietary and medical considerations.
 Update the seat availability status in the reservation file and adds the
passenger details to the file. The passenger is assigned a unique
 Passenger Name Request (PNR) number, which is used to access ticket
details for queries and cancellation.
 Collects the fare amount.
 Prints the ticket and gives it to the passenger.
 Update the Daily Collection file with the fare amount.

TABLE STRUCTURE

Two files have been used in this project:

1. CUSTOMER.DAT (Stores all

information for customers)

 custcode : Code no. of the customer. This is unique

field.
 Name : Name of the customer.
 Address : Address of the customer.
 Phone : Phone no. of the customer.
 Strode : Station code to which courier has to be
sends.
 Came : Consignee name.
 Cadress : Consignee address.
 Cphone : Consignee phone no.
 Type : Type of the courier (document or non-
document)
 Weight : Weight of the courier.
 Amount : Total charges for sending the courier.
 DoB : Date of booking courier.
 2. STATION.DAT (Stores all
information for Stations)

 strode : Code no. of the station.

 Name : Name of the station.
 Doc : Charges for document.
 Docadd : Additional charges for document above
500 gms.
 Ndoc : Charges for non-document.
 ndocadd : Additional charges for non-document
above 500 gms.
PROGRAM STRUCTURE

3 classes have been used in this project:

 STATION
 DATE
 CUSTOMER
Modules in class STATION:

 addition() : Function to add new station record in the

file.
 modification() : Function to modify existing record of
station.
 deletion() : Function to delete existing record of the
station.
 list() : Function to display list of all stations.
 search() : Function to search information for
 station.
 amount() : Function to calculate and return total
amount for the given information of
station.
 foundcode() : Function to return station code found in
the file or not.

Modules in class DATE:

 valid() : Function to check validity of the given

date.

Modules in class CUSTOMER:

 booking() : Function to book courier along with

consinor and consinee information and
store in the file – customer.dat.
 search() : Function to search for the customer
information.
 dailylist() : Function to display daily booking status.
 Monthlylist() : Function to display monthly booking
status.
 lastcustcode() : Function to return last customer code in
the customer file.
 DFD
ENTITY RELATIONSHIP DIAGRAM (ERD):

The overall logical structure of a database can be express

graphically by an E-R-Diagram. Then relative simplicity and pictorial clarity

of this diagramming technique may well System in large part for the wide

spread use of the E-R model.

7.1.1 components of E-R Diagram:

 Rectangle: which represent entity sets

 Ellipses: which represent attributes

 Diamonds: which represent relationships sets

 Lines: which link attribute to entity set and entity set to

relationship sets

 Double ellipses: which represent multi values attributes

 Dashed ellipses: which denote derived attributes

 Program coding

PROJECT CODE – AIRLINE RESERVATION

SYSTEM

# include <iostream.h>
# include <fstream.h>
# include <string.h>
# include <stdlib.h>
# include <stdio.h>
# include <ctype.h>
# include <dos.h>
# include <conio.h>
# include <process.h>

class TICKET
{

private:
void
ADD_RECORD(char[10],char[15],char[15],int,int);

public:
void ADDITION(void);
void ENQUIRY(void);
char *FLIGHTNO(int);

protected:

char fltno[10],from[15],to[15];
int ecofair,exefair;

};

//THIS CLASS CONTROLS ALL THE FUNCTIONS RELATED TO

PASSENGERS

class PASSENGER
{
public:
 void
ADD_RECORD(int,int,char[26],char[36],int,char,char);
void DELETE_TICKET(int);
int DELETE_FLIGHT(int);
void LIST(void);
int LAST_TICKETNO(void);
int SEATS(int);
int FOUND(int);
char *NAME(int);
void PASS_INFO();
void MODIFY();
protected:
char Class,name[26],address[36],sex;
int slno,age,ticketno;
};

//THIS IS THE DERIVED CLASS WHICH CONTROLS ALL THE

FUNCTIONS
//RELATED TO RESERVATION,CANCELLATION,ETC.

class RESERVE : public TICKET,public PASSENGER

{
public:
void RESERVATION(void);
void CANCELLATION(void);
void DISPLAY_TICKET(void);
void DELETE_ALL(void);
};

//FUNCTION TO ADD GIVEN DATA IN THE TICKET

FILE(TICKET.DAT)

void TICKET :: ADD_RECORD(char t_fltno[10],char

t_from[15],char t_to[15],int t_ecofair,int t_exefair)
{
fstream file;
file.open("TICKET.DAT",ios::app);
strcpy(fltno,t_fltno);
strcpy(from,t_from);
strcpy(to,t_to);
ecofair = t_ecofair;
exefair = t_exefair;
file.write((char*)this,sizeof(TICKET));
file.close();
}

//FUNCTION TO RETURN FLIGHT NO. FOR THE GIVEN S.NO

char *TICKET :: FLIGHTNO(int sno)

{
fstream file;
 file.open("TICKET.DAT",ios::in);
int count = 1;
while(file.read((char*) this,sizeof(TICKET)))
{
if (sno == count)
break;

count++;
}
file.close();
return fltno;
}

//FUNCTION TO GIVE DATA TO ADD RECORDS IN THE

TICKET FILE

void TICKET :: ADDITION(void)

{
fstream file;
file.open("TICKET.DAT",ios::in);
if (!file.fail() )
return;
file.close();

ADD_RECORD("KL176","DELHI","MUMBAI",1500,1700);

ADD_RECORD("KL177","MUMBAI","DELHI",1500,1700);

ADD_RECORD("KL156","DELHI","CALCUTTA",1700,1900);

ADD_RECORD("KL157","CALCUTTA","DELHI",1700,1900);

ADD_RECORD("KL166","DELHI","MADRAS",2100,2300);

ADD_RECORD("KL167","MADRAS","DELHI",2100,2300);

ADD_RECORD("KL176","MUMBAI","CALCUTTA",1900,2100);

ADD_RECORD("KL177","CALCUTTA","MUMBAI",1900,2100);

ADD_RECORD("KL186","MUMBAI","MADRAS",1800,2000);

ADD_RECORD("KL187","MADRAS","MUMBAI",1800,2000);

ADD_RECORD("KL196","CALCUTTA","MADRAS",1600,1800);

ADD_RECORD("KL197","MADRAS","CALCUTTA",1600,1800);
}

//FUNCTION TO DISPLAY LIST OF FLIGHTS

void TICKET :: ENQUIRY(void)

{
 clrscr();
fstream file;
file.open("TICKET.DAT",ios::in);
gotoxy(30,3);
cout<<"LIST OF THE FLIGHTS";
gotoxy(18,5);
cout<<"Sno. FLIGHT NO. FROM TO
ECO.FAIR EXE.FAIR";
int row = 7,sno = 1;
while(file.read((char*)this, sizeof(TICKET)))
{
gotoxy(18,row);
cout<<sno;
gotoxy(23,row);
cout<<fltno;
gotoxy(34,row);
cout<<from;
gotoxy(44,row);
cout<<to;
gotoxy(53,row);
cout<<ecofair;
gotoxy(63,row);
cout<<exefair;
row++;
sno++;
}
file.close();
}

//FUNCTION TO RESERVE TICKET FOR THE PASSENGERS

void RESERVE :: RESERVATION(void)

{
clrscr();
ENQUIRY();
char
t1[15],pclass,pname[26],paddress[36],psex,pfltno[10];
int t2,valid,page,tno,sno;
PASSENGER p;
tno = p.LAST_TICKETNO() + 1;
do
{
valid = 1;
gotoxy(3,23);
clreol();
cout<<"PRESS <ENTER> TO EXIT";
gotoxy(3,20);
clreol();
cout<<"ENTER THE SNO. OF THE FLIGHT : ";
gets(t1);
t2 = atoi(t1);
 sno = t2;
if(strlen(t1) == 0)
return;
if(sno < 1 || sno > 12)
{
valid = 0;
gotoxy(3,23);
clreol();
cout<<"ENTER CORRECTLY";
getch();
}
} while(!valid);

int i=1;

fstream file;
file.open("TICKET.DAT",ios::in);

while(file.read((char*)this, sizeof(TICKET)))
{
if(sno == i)
break;
i++;
}
file.close();
strcpy(pfltno,fltno);
if(p.SEATS(sno)>=250)
{
gotoxy(5,21);
cout<<"\7Sorry! SEATS ARE NOT AVAILABLE";
getch();
return;
}
gotoxy(3,23);
clreol();
cout<<"E=ECONOMIC,X=EXECUTIVE or PRESS
<ENTER> TO EXIT";
do
{
gotoxy(3,21);
clreol();
cout<<"BY WHICH CLASS YOU WOULD LIKE TO
TRAVEL : ";
pclass = getche();
pclass = toupper(pclass);
if(pclass == 13)
return;
} while(pclass !='E' && pclass !='X');

clrscr();
gotoxy(72,3);
 cout<<"<0>-EXIT";
gotoxy(34,2);
cout<<"RESERVATION";
gotoxy(5,5);
cout<<"NAME : ";
gotoxy(5,6);
cout<<"ADDRESS : ";
gotoxy(5,7);
cout<<"SEX M/F : ";
gotoxy(5,8);
cout<<"AGE : ";

do
{
valid = 1;
gotoxy(5,25);
clreol();
cout<<"ENTER THE NAME OF THE PASSENGER";
gotoxy(15,5);
clreol();
gets(pname);
if(pname[0] == '0')
return;
if(strlen(pname) < 1 || strlen(pname) > 25)
{
valid = 0;
gotoxy(5,25);
clreol();
cout<<"\7ENTER CORRECTLY {RANGE : 1 TO
25}";
getch();
}
} while(!valid);

do
{
valid = 1;
gotoxy(5,25);
clreol();
cout<<"ENTER THE ADDRESS OF THE PASSENGER";
gotoxy(15,6);
clreol();
gets(paddress);
if(paddress[0] == '0')
return;
if(strlen(paddress) < 1 || strlen(paddress)
> 35)
{
valid = 0;
gotoxy(5,25);
clreol();
 cout<<"\7ENTER CORRECTLY {RANGE : 1 TO
35}";
getch();
}
} while(!valid);

do
{
gotoxy(5,25);
clreol();
cout<<"ENTER THE SEX OF THE PASSENGER";
gotoxy(15,7);
clreol();
psex = getche();
psex = toupper(psex);
if(psex == '0')
return;
} while(psex !='M' && psex !='F' );

do
{
valid = 1;
gotoxy(5,25);
clreol();
cout<<"ENTER THE AGE OF THE PASSENGER";
gotoxy(15,8);
clreol();
gets(t1);
t2 = atoi(t1);
page = t2;
if(t1[0] == '0')
return;
if(page < 1 || page > 100)
{
valid = 0;
gotoxy(5,25);
clreol();
cout<<"\7ENTER CORRECTLY ";
getch();
}
} while(!valid);

clrscr();
gotoxy(11,4);

cout<<"**************************************************
**";
gotoxy(11,21);

cout<<"**************************************************
**";
 gotoxy(33,6);
cout<<"TICKET NO. : "<<tno;
gotoxy(17,9);
cout<<from<<" TO "<<to;
gotoxy(45,9);
cout<<"FLIGHT NO. : "<<pfltno;
gotoxy(20,11);
cout<<"PASSENGER NAME : "<<pname;
gotoxy(20,13);
cout<<"ADDRESS : "<<paddress;
gotoxy(20,15);
cout<<"SEX : "<<psex;
gotoxy(20,17);
cout<<"AGE : "<<page;
gotoxy(45,19);
if(pclass == 'E')
cout<<"TOTAL FAIR : "<<ecofair;
else
cout<<"TOTAL FAIR : "<<exefair;

p.ADD_RECORD(tno,sno,pname,paddress,page,psex,pclass);
getch();
}

// FUNCTION TO ADD THE GIVEN DATA IN THE

PASSENGER'S FILE

void PASSENGER :: ADD_RECORD (int tno,int sno,char

pname[26],char paddress[36],int page,char psex,char
pclass)
{
fstream file;
file.open("PASS.DAT",ios::app);
ticketno = tno;
slno = sno;
strcpy(name,pname);
strcpy(address,paddress);
age = page;
sex = psex;
Class = pclass;
file.write((char*)this,sizeof(PASSENGER));
file.close();
}
void PASSENGER :: MODIFY()
{
int tcno;
char
t1[15],pclass,pname[26],paddress[36],psex,pfltno[10];
int t2,valid,page,tno,sno;
 PASS_INFO();
cout<<"\nENTER THE TICKET NUMBER OF THE
PASSENGER";
cin>>tcno;
fstream file;
file.open("PASS.DAT",ios::in|ios::out);
int m=0;
int l;
file.read((char*)this,sizeof(PASSENGER));
while(!file.eof())
{ m++;
if(tcno==ticketno)
{
l=(m-1)*sizeof(PASSENGER);
cout<<l;
getch();
clrscr();
gotoxy(72,3);
cout<<"<0>-EXIT";
gotoxy(34,2);
cout<<"RESERVATION";
gotoxy(5,5);
cout<<"NAME : ";
gotoxy(5,6);
cout<<"ADDRESS : ";
gotoxy(5,7);
cout<<"SEX M/F : ";
gotoxy(5,8);
cout<<"AGE : ";

gotoxy(5,25);
clreol();
cout<<"ENTER THE NAME OF THE PASSENGER";
gotoxy(15,5);
clreol();
gets(pname);
gotoxy(5,25);
clreol();
cout<<"ENTER THE ADDRESS OF THE PASSENGER";
gotoxy(15,6);
clreol();
gets(paddress);
gotoxy(5,25);
clreol();
cout<<"ENTER THE SEX OF THE PASSENGER";
gotoxy(15,7);
clreol();
psex = getche();
psex = toupper(psex);
 gotoxy(5,25);
clreol();
cout<<"ENTER THE AGE OF THE PASSENGER";
gotoxy(15,8);
clreol();
gets(t1);
t2 = atoi(t1);
page = t2;
cout<<"CLASS:E(ECONOMIC) OR X(EXECUTIVE)";
pclass=getche();
if(strlen(paddress)!=0)
strcpy(address,paddress);
if(strlen(pname)!=0)
strcpy(name,pname);
if(strlen(t1)!=0)
age=page;
if(psex!=13)
sex=psex;
if(pclass!=13)
Class=pclass;
file.seekp(l);
file.write((char*)this,sizeof(PASSENGER));
file.close();
return;
}
else
file.read((char*)this,sizeof(PASSENGER));

}
}
void PASSENGER :: PASS_INFO()
{
fstream file;
file.open("PASS.DAT",ios::in);

cout<<" PASSENGERS
INFORMATION\n";
cout<<"
**************************\n";
gotoxy(2,4);
cout<<"T.NO.";
gotoxy(11,4);
cout<<"S.NO.";
gotoxy(25,4);
cout<<"NAME";
gotoxy(48,4);
cout<<"ADDRESS";
gotoxy(66,4);
cout<<"AGE";
gotoxy(70,4);
cout<<"SEX";
 gotoxy(74,4);
cout<<"CLASS";
gotoxy(1,5);

cout<<"**************************************************
*****************************";
int tno,sno,page;
char
pname[26],paddress[36],psex,pclass,pfltno[10];
int i=6;

while(file.read((char*)this,sizeof(PASSENGER)))
{
tno=ticketno;
sno=slno;
strcpy(pname,name);
strcpy(paddress,address);
page = age;
psex = sex;
pclass = Class;
gotoxy(2,i);
cout<<tno;
gotoxy(11,i);
cout<<sno;
gotoxy(20,i);
cout<<pname;
gotoxy(45,i);
cout<<paddress;
gotoxy(67,i);
cout<<page;
gotoxy(71,i);
cout<<psex;
gotoxy(77,i);
cout<<pclass;
i++;
}
file.close();
}
//THIS FUNCTION RETURNS THE LAST TICKET NO. IN THE
PASSENGER FILE

int PASSENGER ::LAST_TICKETNO(void)

{
fstream file;
file.open("PASS.DAT",ios::in);
int count = 0;

while(file.read((char*)this,sizeof(PASSENGER)))
count = ticketno;
file.close();
return count;
 }

//THIS FUNCTION RETURNS TOTAL NO. OF SEATS IN THE

PASSENGER FILE

int PASSENGER :: SEATS(int sno)

{
fstream file;
file.open("PASS.DAT",ios::in);
int count = 0;

while(file.read((char*)this,sizeof(PASSENGER)))
{
if(sno == slno)
count++;
}
file.close();
return count;
}

//THIS FUNCTION RETURNS 0 IF THE TICKET NO. IS NOT

FOUND IN THE
//PASSENGER FILE

int PASSENGER :: FOUND(int tno)

{
fstream file;
file.open("PASS.DAT",ios::in);
int found = 0;

while(file.read((char*)this,sizeof(PASSENGER)))
{
if(tno == ticketno)
{
found = 1;
break;
}
}
file.close();
return found;
}

//THIS FUNCTION RETURNS PASSENGER'S NAME FOR THE

GIVEN TICKETNO.

char *PASSENGER :: NAME(int tno)

{
fstream file;
file.open("PASS.DAT",ios::in);
while(file.read((char*)this,sizeof(PASSENGER)))
{
if(tno == ticketno)
break;
}
file.close();
return name;
}

//THIS FUNCTION DISPLAYS THE LIST OF THE

PASSENGERS

void PASSENGER :: LIST (void)

{
clrscr();
char t1[10];
int t2,sno,valid;
TICKET ticket;
ticket.ENQUIRY();
do
{
valid = 1;
gotoxy(3,23);
clreol();
cout<<"PRESS <ENTER> TO EXIT";
gotoxy(3,20);
clreol();
cout<<"ENTER SNO.OF THE FLIGHT WHOSE
DETAILS YOU WANT";
gets(t1);
t2 = atoi(t1);
sno = t2;
if(strlen(t1) == 0)
return;
if(sno < 1 || sno > 12)
{
valid = 0;
gotoxy(3,23);
clreol();
cout<<"\7ENTER CORRECTLY";
getch();
}
} while(!valid);

clrscr();
int row = 8,found = 0,flag = 0;
char ch;
gotoxy(3,4);
cout<<"FLIGHT NO.---->
"<<ticket.FLIGHTNO(sno);
 gotoxy(28,2);
cout<<"**LIST OF PASSENGERS**";
gotoxy(5,6);
cout<<"TICKET NO. NAME
CLASS ";
gotoxy(4,7);

cout<<"**************************************************
*****";
fstream file;
file.open("PASS.DAT",ios::in);
file.seekg(0,ios::beg);

while(file.read((char*)this,sizeof(PASSENGER)))
{
if(sno == slno)
{
flag = 0;
delay(20);
found = 1;
gotoxy(5,row);
cout<<ticketno;
gotoxy(17,row);
cout<<name;
gotoxy(49,row);
if(Class == 'X')
cout<<"EXECUTIVE";
else
cout<<"ECONOMIC";
if(row == 21)
{
flag = 1;
row = 7;
gotoxy(5,23);
cout<<"PRESS ANY KEY TO CONTINUE OR PRESS
<ESC>";
ch = getch();
if(ch == 27)
break;
clrscr();
gotoxy(32,3);
cout<<"LIST OF PASSENGERS";
gotoxy(2,5);
cout<<"TICKET NO. NAME
CLASS ";
}
else
row++;
}
}
if(!found)
 {
gotoxy(5,10);
cout<<"\7RECORDS NOT FOUND";
}
if(!flag)
{
gotoxy(5,23);
cout<<"PRESS ANY KEY TO CONTINUE....";
getch();
}
file.close();
}

//THIS FUNCTION DELETES PASSENGER RECORDS FOR THE

GIVEN TICKET NO.

void PASSENGER :: DELETE_TICKET(int tno)

{
fstream file;
file.open("PASS.DAT",ios::in);
fstream temp;
temp.open("temp.dat",ios::out);
file.seekg(0,ios::beg);
while(!file.eof())
{
file.read((char*)this,sizeof(PASSENGER));
if(file.eof())
break;
if(tno != ticketno)

temp.write((char*)this,sizeof(PASSENGER));
}
file.close();
temp.close();
file.open("PASS.DAT",ios::out);
temp.open("temp.dat",ios::in);
temp.seekg(0,ios::beg);
while(!temp.eof() )
{
temp.read((char*)this,sizeof(PASSENGER));
if(temp.eof() )
break;
file.write((char*)this,sizeof(PASSENGER));
}
file.close();
temp.close();
}

//THIS FUNCTION DELETES PASSENGER RECORDS FOR THE

GIVEN FLIGHTNO.
 int PASSENGER :: DELETE_FLIGHT(int sno)
{
fstream file;
file.open("PASS.DAT",ios::in);
fstream temp;
temp.open("temp.dat",ios::out);
file.seekg(0,ios::beg);
int found = 0;
while(!file.eof() )
{
file.read((char*)this,sizeof(PASSENGER));
if(file.eof() )
break;
if(sno !=slno)

temp.write((char*)this,sizeof(PASSENGER));
else
found = 1;
}
file.close();
temp.close();
file.open("PASS.DAT",ios::out);
temp.open("temp.dat",ios::in);
temp.seekg(0,ios::beg);
while(!temp.eof() )
{
temp.read((char*)this,sizeof(PASSENGER));
if(temp.eof() )
break;
file.write((char*)this,sizeof(PASSENGER));
}
file.close();
temp.close();
return found;
}

//THIS FUNCTION CANCELS PASSENGER'S TICKET

void RESERVE ::CANCELLATION(void)

{
clrscr();
char t1[10],ch;
int t2,tno,valid;
do
{
valid = 1;
gotoxy(3,23);
clreol();
cout<<"PRESS <ENTER> TO SEE LIST OR 0 TO
EXIT ";
gotoxy(3,20);
 clreol();
cout<<"ENTER TICKETNO. OF PASSENGER TO
CANCEL THE TICKET";
gets(t1);
t2 = atoi(t1);
tno = t2;
if(t1[0] == '0')
return;
if(strlen(t1) == 0)
{
valid = 0;
LIST();
clrscr();
}
if(!FOUND(tno) && valid)
{
valid = 0;
gotoxy(3,23);
clreol();
cout<<"\7RECORD NOT FOUND";
getch();
}
} while(!valid);

//PAGE 11

clrscr();
fstream file;
file.open("PASS.DAT",ios::in);

while(file.read((char*)this,sizeof(PASSENGER)))
if(ticketno == tno)
break;
file.close();
int i = 1;
file.open("TICKET.DAT",ios::in);
while(file.read((char*)this,sizeof(TICKET)))
{
if(slno == i)
break;
i++;
}
file.close();
PASSENGER p;
gotoxy(11,4);

cout<<"**************************************************
**";
gotoxy(11,21);
cout<<"**************************************************
**";
gotoxy(33,6);
cout<<"TICKET NO. : "<<tno;
gotoxy(17,9);
cout<<from<<" TO "<<to;
gotoxy(45,9);
cout<<"FLIGHT NO. : "<<fltno;
gotoxy(20,11);
cout<<"PASSENGER NAME : "<<p.NAME(tno);
gotoxy(20,13);
cout<<"ADDRESS : "<<address;
gotoxy(20,15);
cout<<"SEX : "<<sex;
gotoxy(20,17);
cout<<"AGE : "<<age;
gotoxy(45,19);
if(Class == 'E')
cout<<"TOTAL FAIR : "<<ecofair;
else
cout<<"TOTAL FAIR : "<<exefair;
do
{
gotoxy(10,23);
clreol();
cout<<"CANCEL THIS TICKET (Y/N) : ";
ch = getch();
ch = toupper(ch);
} while(ch != 'Y' && ch != 'N');

if(ch == 'N')
return;
DELETE_TICKET(tno);
gotoxy(10,25);
cout<<"\7TICKET CANCELLED";
getch();
}

//THIS FUNCTION DISPLAYS THE PASSENGER'S

INFORMATION

void RESERVE :: DISPLAY_TICKET(void)

{

// PAGE 12

clrscr();
char t1[10],ch;
int t2,tno,valid;
do
{
 valid = 1;
gotoxy(3,23);
clreol();
cout<<"PRESS <ENTER> TO SEE LIST OR 0 TO
EXIT";
gotoxy(3,20);
clreol();
cout<<"ENTER THE TICKETNO. OF THE PASSENGER
: ";
gets(t1);
t2 = atoi(t1);
tno = t2;
if(t1[0] == '0')
return;
if(strlen(t1) == 0)
{
valid = 0;
LIST();
clrscr();
}
if(FOUND(tno) && valid)
{
valid = 0;
gotoxy(3,23);
clreol();
cout<<"\7RECORD NOT FOUND";
getch();
}
} while(!valid);

clrscr();
fstream file;
file.open("PASS.DAT",ios::in);

while(file.read((char*)this,sizeof(PASSENGER)))
if(ticketno == tno)
break;
file.close();
int i = 1;
file.open("TICKET.DAT",ios::in);
while(file.read((char*)this,sizeof(TICKET)))
{
if(slno == i)
break;
i++;
}
file.close();
PASSENGER p;
gotoxy(11,4);
cout<<"**************************************************
**";
gotoxy(11,21);

cout<<"**************************************************
**";
gotoxy(33,6);
cout<<"TICKET NO. : "<<tno;
gotoxy(17,9);
cout<<from<<" TO "<<to;
gotoxy(45,9);
cout<<"FLIGHT NO. : "<<fltno;
gotoxy(20,11);
cout<<"PASSENGER NAME : "<<p.NAME(tno);
gotoxy(20,13);
cout<<"ADDRESS : "<<address;

// PAGE 13

gotoxy(20,15);
cout<<"SEX : "<<sex;
gotoxy(20,17);
cout<<"AGE : "<<age;
gotoxy(45,19);
if(Class == 'E')
cout<<"TOTAL FAIR : "<<ecofair;
else
cout<<"TOTAL FAIR : "<<exefair;
gotoxy(10,25);
cout<<"PRESS ANY KEY TO CONTINUE....";
getch();
}

//THIS FUNCTION GIVES FLIGHT NO. TO DELETE ALL

PASSENGER RECORDS

void RESERVE :: DELETE_ALL(void)

{
clrscr();
ENQUIRY();
char t1[5];
int t2,valid,sno;
do
{
valid = 1;
gotoxy(3,23);
clreol();
cout<<"PRESS <ENTER> TO EXIT";
gotoxy(3,20);
 cout<<"ENTER SNO. OF THE FLIGHT TO DELETE
RELATED RECORDS";
gets(t1);
t2 = atoi(t1);
sno = t2;
if(strlen(t1) == 0)
return;
if(sno < 1 || sno > 12)
{
valid = 0;
gotoxy(3,23);
clreol();
cout<<"\7ENTER CORRECTLY";
getch();
}
} while(!valid);

gotoxy(3,23);
if(!DELETE_FLIGHT(sno) )
cout<<"\7RECORDS NOT FOUND.PRESS ANY KEY TO
CONTINUE....";
else
cout<<"\7RECORDS DELETED.PRESS ANY KEY TO
CONTINUE....";
getch();
}

//THIS IS THE MAIN FUNCTION WHICH DISPLAYS MENU

AND CALLS FUNCTIONS

void main(void)
{

// PAGE 14

PASSENGER p;
TICKET ticket;
RESERVE r;
ticket.ADDITION();
int ch,ch1;
while(1)
{
clrscr();
gotoxy(29,9);
cout<<"AIR TICKET RESERVATION";
gotoxy(29,10);
cout<<"~~~~~~~~~~~~~~~~~~~~~~~~~~";
gotoxy(30,11);
cout<<"1 : RESERVATION";
gotoxy(30,12);
cout<<"2 : CANCELLATION";
gotoxy(30,13);
cout<<"3 : PASSENGER RECORDS ->";
gotoxy(30,14);
cout<<"4 : ENQUIRY";
gotoxy(30,15);
cout<<"5 : LIST OF PASSENGERS";
gotoxy(30,16);
cout<<"6 : QUIT";
gotoxy(30,18);
cout<<"ENTER YOUR CHOICE : ";
cin>>ch;
switch(ch)
{
case 1:
r.RESERVATION();
break;

case 2:
r.CANCELLATION();
break;

case 3:
clrscr();
gotoxy(29,10);
cout<<" PASSENGER RECORDS ";
gotoxy(29,11);
cout<<"~~~~~~~~~~~~~~~~~~~~~~~";
gotoxy(33,12);
cout<<"1 : PASSENGER INFORMATION";
gotoxy(33,13);
cout<<"2 : MODIFY";
gotoxy(33,14);
cout<<"0 : EXIT";
gotoxy(33,16);
cout<<"ENTER YOUR CHOICE--->";
cin>>ch1;
if(ch1==1)
{clrscr();
p.PASS_INFO();
getch(); }
else
if(ch1==2)
{clrscr();
p.MODIFY();}
else
break;
break;

case 4:
ticket.ENQUIRY();
gotoxy(2,23);
 cout<<"PRESS ANY KEY TO
CONTINUE....";
getch();
break;

case 5:
p.LIST();
break;

case 6:
exit(0);

default:
cout<<"ENTER THE CORRECT CHOICE";
}
}
}

OUTPUT SCREEN
LOGIN PAGE OF
AIRLINES TICKET RESERVATION
Si NO. OF FLIGHTS

LIST OF THE FLIGHTS

PASSENGER RECORDS

LIST OF THE FLIGHTS

 PASSENGERS INFORMATION

SOFTWARE TESTING & IMPLIMENTATION:

SOFTWARE TESTING:
The purpose of this document is to cover testing of Horizon Airways
project from all aspects i.e. from module wide testing to system integration
testing.
Software testing is a process of executing a program with objective of
finding an error. Software quality should be a primary concern in software
development efforts. Software testing and evaluation are traditional method of
checking software quality. It consists of putting together various coded pieces
of a design, testing them and correcting the parts of the code or the design that
is not correct. At this stage some errors are introduced purposely to test
whether the program will spot them.
Test summary document with test results (Quality Record) for each test case
with problems found during the test execution. After review of test summary
document, it will be decided if any test case is to be repeated or if the identified
problem should be converted into “a defect” to be fixed in subsequent release
of product.