AIR TICKET

RESERVATION SYSTEM.

-1-
 INDEX

S.NO CONTENT PAGE NO.

1. INTRODUCTION

Synopsis
Covering Letter
Objective
Need of the System
Demerits of manual system
General merit of computerised system

2. DESIGN OF THE SYSTEM

Hardware And Software used
Methodology
Parts of the System
Block Diagram
Pert Chart

3. IMPLEMENTATION AND
CODING
Analysis

-2-
 Data flow diagram

Data Dictionary
Project Development life Cycle

4. DATABASE
Flights
Ticket

5. TESTING

6. BIBLOGRAPHY

7. CONCLUSION

8. LIMITATIONS

9. FUTURE REFERENCE
10. REFERENCE

-3-
 OBJECTIVE

This software will be provided as a tool to the ABC.LTD

Company. The organization has been working as reserving tickets for
flights for many years. Presently the company maintains files, folders
and records for reservation and cancellation related details of
customers.

To search for urgently required information about the seats available,

an employee has to take all the related files and folder out of the
shelves and need each page to be checked, still there are no chance of
100% accuracy.
Doing all this manually is a time consuming and error prone
approach.

The objective is to prepare a system or application, which could

maintain data and provide a user-friendly interface for retrieving
information about availability of the ticket or not in a few seconds,
with 100% accuracy.

-4-
 NEED FOR THE SYSTEM

When I joined ABC.LTD, the reservation and cancellation

department was facing a problem.
The problem was to check the availability of the ticket for
reservation, cancellation. Searching manually is a time
consuming if the number of reservation or cancellation of
ticket is large.

The problem could be solved in two steps:-

1) Maintaining database for customer’s:- this includes to search that which

seat is available for which customer.
2) Providing a user-friendly interface:-to navigate through those database.

Thus the working application needed to be developed in just 4 weeks.

The application is named as” Air Ticket reservation System”.

Considering all requirements and time restriction,VB 6.0 is the best answer to
the above problem.

-5-
 DEMERITS OF THE MANUAL OR NON-
COMPUTERISED SYSTEM

 It is time consuming.

 It requires dedicated employee thus it is an indirect wastage of

resources.

 It is prone to errors.

 The excessive use of paper work results in increased paper cost.

 Inefficient working as it needs more labors than an electronic system.

 No use of newly developing IT Technologies.

-6-
GENERAL MERITS OF COMPUTERISED
SYSTEM
 The user can explore the options given by s/w.

 Retrieval of information can be done very fast using this s/w.

 It also avoids a dedicated employee engaged in data management.

 Provides a base to increase company sales.

 Provides high level of user satisfaction and comfort.

 Consolidated reports to the management, which would help it take

timely decision.

 No paper work is required.

 Change can be implemented easily.

-7-
-8-
 HARDWARE USED

Processor : Pentium 4
RAM : 2 GB
Hard Disk : 100GB
Other : Printer

SOFTWARE USED

For Front-End
VB 6.0

For Back-end
MS Access

For connectivity
VB 6.0

-9-
 METHODOLOGY
Project is proceeded according to the steps of SDLC(Software Development Life
Cycle) that is in seven phases which include the following:-

1) Requirement Analysis::All the companies requirements are analyzed

using verbal or written questionnaires.

2) High-Level Design::The purpose of this phase is to design the overall

functioning of the proposed system and finalize
the input and output format.

3) Low-Level Design:: The purpose is to produce a detailed design of the

Software modules/units.

4) Construction:: Actual ciding will be done in this phase.

5) Testing:: In this phase module level testing is performed

with mock values.

6) Acceptance:: At this time the software is actually provided to the

company and checking it according to need.

7) Warranty and Maintainance ::After sale services.

- 10 -
 PARTS OF THE SYSTEM

The application has three parts:-

Front-end
Back-end
Connectivity
When we useVB 6.0 as s/w development tool, connectivity code is written as apart
of front-end code itself.

FRONT-END
It has been coded so as to provide maximum user friendliness and
ease. Stress is laid on the point that the user should enter as type as minimum as
possible. Most of the work is done in few clicks. From each page, jumps to the
other pages are provided.

These event-linked functions contain connection string (which connects front-end

with applications) and queries, which are executed when the corresponding event
occurs.

BACK-END
Database is designed using Ms Access.Our database is “Flight”
“Ticket” required for this application, which contains all flight and ticket related
data.

All tables are normalized and have redundant or unwanted records.

CONNECTIVITY
A connection string is used to connect the queries written in front-end
codes with the database.
Provider used—sun.jdbc.odbc.JdbcOdbcDriver()
Driver used—Microsoft Access Driver (*mdb).

- 11 -
- 12 -
 BLOCK DIAGRAM

AIR RESERVATION SYSTEM

MASTER TRANSACTION REPORTS EXIT

ALL FLIGHTS

ADD MODIFY DELETE CANCLE RESERV. CANCLE ALL FLIGHT ALL TICKET YES NO

- 13 -
- 14 -
 PERT CHART

Activity Time
Preliminary Investigation 6 days
Feasibility Study 2 days
System Analysis 3 days
Development of Prototype 6 days
System Design 4 days
Coding 6 days
System Testing 3 days
Implementation & Evaluation 3 days
Maintenance Whole life
Total Days 33 days

- 15 -
- 16 -
 ANALYSIS

Analysis can be referred to as study of a problem and its division

into smaller modules so as to solve particular problem.

A complete understanding of software requirements is necessary

to help the new software being developed succeed. No matter

how well designed or well coded, a poorly analyzed and

specified program will disappoint the user and will also be a

burden to the developer.

At this stage comes Requirement analysis that is a process of

discovery, refinement, modeling and specification. Models of

the required data, information and control flow are created. It

bridges together the gap between system-level software

allocation and software design.

- 17 -
Software Requirement Analysis is divided into the following area-

1. Initial Investigation (Problem recognition)

The first step of the development of system is

the need of a new system. This might be a user request to change,
improve or enhance an existing system. This step
Determine whether the request is valid and feasible or not before
improving or modifying the current system or build a new one.

2. Determining the user’s Information Requirement (Evaluation &

Synthesis).

At this stage, the user’s requirements are determined with the help of
prototyping, asking question and obtaining information from the
existing system.

3. Problem Definition & Project Initiation.

Once the problem is clearly determined, the problem is defined in

terms as to what is required, how etc.

4. Background Analysis.

Once the project is initiated, the analyst begins to learn about the
setting, the existing system and the physical

- 18 -
processes related to the revised system. All the background information is
collected and thoroughly studied.

After obtaining background knowledge, the analyst begins to collect data

on the exiting system, output, input and costs with the help of written
documents, on site observations, interviews and questionnaires.

5. Fact Analysis

After gathering data, they must be organized and evaluated and

conclusions drawn for preparing a report to the users for final review
and approval. At this stage, some tools are used i.e. data flow diagrams,
decision tables, structure charts etc.

- 19 -
In this project we have done the following analysis –

1. Initial Investigation

We saw that there were very few sites that could

Give complete information about air reservation
system to the users. Also there was a need to
automate the entire system

2. Determination of user Requirements

We contacted a number of people about this

Project who0 agreed with the idea that this system
will help a lot many people rather that entire nation.

3. Problem definition & project initiation.

Problem definition is an initial investigation, which

defines the problem that led to the user request. It states the
objectives the user is trying to achieve and the user wants to see.
It gives more stress on logical requirements than the physical
requirements.

The main objective of the “DISCUSSION BOX” is to organize

and give the user complete and appropriate

- 20 -
information about his currency. The records are automatically
updated in the master file when any transaction takes place.

4. Background Analysis:-

All the existing details were collected from the respective

experts.

5. Fact Analysis:-

All the data and information collected was organized to

show how information flows and at what stage, exactly what
happens? For this we tired to explain this with the help of Data
Flow Diagrams.

- 21 -
- 22 -
 DFD ON THE TICKET DETAILS

TICKET DETAILS ADD TICKET RECORDS

RECORD
S

LEVEL 0 DFD

DFD ON CUSTOMER DETAILS

CUSTOMER DETAILS CUSTOMER

RESERVATION/
RECORDS
CANCELLSTION

LEVEL 0 DFD

- 23 -
- 24 -
- 25 -
 DATA DICTIONARY

DATATYPE DESCRIPTION
Set Title For giving the name to the window
Set Text For writing the text

MenuBar Mb, for creating the menu bar

Menu Mn1, mn2, mn3, mn4

Menu Item Mi 11,mi 12,mi 31,mi 32, mi 33, mi 41, mi 42

Connection Cn, for creating a connection between database

Statement St, for giving statement

ResultSet Rs,

Text Field Txt1, txt2, txt3, txt4

Text Area Txt a, txt b

Button Bt1, bt2, bt3, bt4, bt5, bt6

Label Lb1, lb2, lb3, lb4, lb5, lb6, lb7, lb8, lb9, sp1, sp2, sp3, sp4

GridBagLayout Gl

St.executeQuery For execute the given query

String Str

Str.trim For making changes in the string

Str.Length For defining the length of the string

Alltickets For tickets database

Set size For defining the size of the window

- 26 -
Set Visible For defining the visibility

Fcode For the code of the flight

- 27 -
 PROJECT DEVELOPMENT LIFE CYCLE

The computer application development life cycle can be thought of six

main steps, which are: -

1. System project selection

2. Feasibility phase

3. Definition phase

4. Design phase

5. Implementation phase

6. Maintenance phase

- 28 -
- 29 -
 FLIGHT

Code Route Fare

001 Delhi to MUMBAI 7000
002 MUMBAI to BANGLORE 7000
005 BANGLORE to CHENNAI 8879
006 CHENNAI to DELHI 20040

007 DELHI to AHMEDABAD 30000

009 NEW YORK to LONDON 12000

011 LONDON to PARIS 15000

012 PARIS to SYDNEY 10000

015 TOKYO to DELHI 14000
017 SYDNEY to HAWAI 8000
020 BRAZIL to BANKOK 12000
022 COLUMBIA to JAKARTA 7500
024 KARACHI to DHAKA 8000
027 PUNE to GOA 9500
028 SHIMLA to MANALI 10000

029 KULLU to DELHI 12000

031 PUNE to BARODA 15000

032 OTAWA to OHIO 8500

034 NEW YORK to PARIS 12500
035 aus-figi 8700

- 30 -
036 france-finland 9500
037 ind-france 13000
038 france-bom 12500

040 iraq-dub 8500

041 kol-switzerland 9500

042 thailand-aus 12000

043 bom-egypt 20000

044 u.s.a-ind 12000

045 egypt-u.s.a 11500

046 del-hongkong 12570
047 greek-alaska 13500

050 u.s.a-greek 15000

052 bom-kol 4500

053 bom-sweden 12300

055 bom-canada 15000

056 canada-china 12500
057 luko-bom 5500
058 hongkong-bom 14500
059 brazil-u.s.a 12500
061 kenya-brazil 15200
062 austria-china 11200

063 china-france 15200

064 germany-ind 15600

- 31 -
065 germany-aus 12300
066 mexico-del 15520

067 chennai-del 5600

068 poland-mexico 18000

070 denmark-germany 12500

071 china-myanmar 13500
072 mauritius-greece 15750

- 32 -
 TICKET
Code Fcode Name Others Seats Address Phone Fare
1 002 NARIANDER ASHISH 6 vips 23257824 42000
2 009 vibhu mishra sunil 2 DFWEQF 22911559 24000
3 001 amit goel asdhjsa 2 addfa 8948 14000
4 004 GAURAV ANKIT 5 2032 32497675 5550
5 003 AMAN VAIBHAV 1 GALI 23269153 5972
6 005 SIDDHANT TARANG 3 VCXZ 9350767675 6102
7 007 SAGAR HARSH 8 JDGC 23255654 6541
8 011 AYUISH SHOBHIT 4 LKERUF 23266548 5470
9 021 ANUJ JATIN 10 YTSX 23254678 9874
10 012 YASH ADDI 10 JGYD0 23248795 9870
11 045 RAHUL ROHIT 12 JHGD 32461216 6871
12 015 SUNIL SACHIN 7 JGXD 23259784 6879
13 019 AKSHAT SONU 7 JYFD 23252631 9456
14 08 sita gita 9 rfs 23259971 5645
15 032 pyuish sukhjeet 24 kfhkovx 2367039 6481
16 031 neha siddharth 5 abcd 23257824 7500

- 33 -
- 34 -
 TESTING PHASE

Testing is the process of making sure that the programs perform the
intended tasks. Once the system is designed it should be tested for
validity. During system testing, the system is used experimentally to
insure that the software does not fail, that means it will run according
to its specification and in the way users expect it to. The system is
tested with special test data and the results are examined for their
validity. Some of the users may be permitted to operate on the system
so that the analyst can ascertain that the system can work in the
specified environment.

- 35 -
 IMPLEMENTATION PHASE

The implementation phase is less creative than system design. It is

primarily concerned with user training, site preparation, and file
conversion. When the candidate system is linked to terminals or
remote sites, telecommunication network and test of the network
along with the system are also included under implementation.
During the final testing, user acceptance is tested, followed by user
training. Depending on the nature of the system, extensive user
training may be required. Conversion usually takes place about the
same time the user is being trained or late.
In the extreme, the programmer is viewed as someone who ought
to be isolated from other aspects of the system development.
Programming is itself design work, however. The initial
parameters of the candidate system should be modified as a result
of programming efforts. Programming provides a ‘reality test’ for
the assumptions made by the analyst. Therefore, it is a mistake to
exclude programmers from the initial system design.

- 36 -
 MAINTENANCE PHASE

After the installation phase is completed and the user staff is

adjusted to the changes created by the candidate system, evaluation
and maintenance begin. Like any system, there is an aging process
that requires periodic maintenance of hardware and software. If new
information is inconsistent with the design specification, then
changes have to be made. Hardware also required periodic
maintenance to keep in tune with design specification. The
importance of maintenance is to continue to bring the new system to
standers.

User priorities, changes in organization requirements, or

environmental factors also call for the system enhancements. To
contrast maintenance is done with enhancement.

- 37 -
- 38 -
 CONCLUSION

The efficient performing running application for electronic

information retrieval and deposition has been developed, which
achieves the following goals:

 User can also search any combination of specifications.

 He can also add a new set of specifications.

 He has been provided with a facility to delete or modify the

existing records.

 The application is protected by security code.

 Error free and fast record processing is possible.

 Easy generation of reports for higher management.

 User can print report from any form

- 39 -
 LIMITATION

As such every project has some limitations so is this project

1. For successful implementation of the project. We should have a

proper network system where every transaction made should be
updated in the server database.

2. As this project deals in Internal discussions thus requires every

security.

3. This project has a limited to an Intranet Application thus is

bound to an organization.

- 40 -
 FUTURE ENHANCEMENTS

The following additions can be made in future to improve or

upgrade the performance of the application:-

 Attaching this application with order processing system.

 Allowing multilevel selections by implementing advanced

search.

 Implementing deadlock phenomenon on the database to

maintain consistency.

 Adding application usage directions so as to make it easily

understandable by new user.

- 41 -
 REFERENCE

Web site-:

 sunmicrosoft.com
 doeacc.edu

Books-:

*Herbert shield (Complete ReferenceVB 6.0)

*MS Access and MS Excel(Study Material)

- 42 -
- 43 -