Mis Project Main Project for Externals (2)

8/3/2019 Mis Project Main Project for Externals (2)

http://slidepdf.com/reader/full/mis-project-main-project-for-externals-2 1/73

AIRLINE RESERVATION SYSTEM

1 | P a g e

PROJECTON

AIRLINE RESERVATION

SYSTEM




2 | P a g e

PROJECT

ON


Submitted by: ENROLLMENT NO. :

ISHITA JAIN 10721401709

AKASH ADHIKARI 11121401709

SAKSHI VERMA 12021401709

DHANANJAY KHER 13721401709

In partial fulfillment for the award of the degree

Of

BACHELOR’S OF BUSINESS ADMINISTRATION

Affiliated to

GURU GOBIND SINGH INDRAPRASTHA UNIVERSITY

“JAGANNATH INTERNATIONAL MANAGEMENT SCHOOL”

VASANT KUNJ, DELHI.

AUGUST- 2011




3 | P a g e

CERTIFICATE

This is to certify that this is a bonafide record to the project work done

satisfactorily at JIMS by students:

ISHITA JAIN (10721401709)

AKASH ADHIKARI (11121401709)

SAKSHI VERMA (12021401709)

DHANANJAY KHER (13721401709)

Of Vth Semester.

This report or the similar report on this topic has not been submitted for any

other examination and does not form part of any other course undergone by the

candidate.

Signature of Project Guide

Name: Mrs. Poonam Malik




4 | P a g e

ACKNOWLEDGEMENT

I would like to take this opportunity to express my gratitude towards all thepeople who have in various ways, helped in the successful completion of my

project.

I must convey my gratitude to Mrs. Poonam Malik for giving me the constant

source of inspiration and help in preparing the project, personally correcting my

work and providing encouragement throughout the project.

I also thank all my faculty members for steering me through the tough as well as

easy phases of the project in a result oriented manner with concern attention.

ISHITA JAIN 10721401709

AKASH ADHIKARI 11121401709

SAKSHI VERMA 12021401709

DHANANJAY KHER 13721401709




5 | P a g e

TABLE OF CONTENTS

SYSTEM STUDY

1.) PROBLEM DEFINATION

1.1) INTRODUCTION

1.2) NEED OF AIRLINE RESERVATION SYSTEM

1.3) HARDWARE AND SOFTWARE REQUIREMENTS

1.4) METHODOLOGY

2.) FEASIBILITY STUDY

2.1) ECONOMIC FEASIBIITY

2.2) TECHNICAL FEASIBILITY

2.3) OPERATIONAL FEASIBILITY.

3.) SYSTEM ANALYSIS

3.1) ER DIAGRAM

3.2) DATA COLLECTION

4.) SYSTEM DESIGNING

4.1) ER DIAGRAM

4.2) DATA FLOW DIAGRAM

4.3) INPUT SCREENS

4.4) TABLES




6 | P a g e

5.) REPORTS

6.) CODING AND DEVELOPINGS

7.) SYSTEM IMPLEMENTATION

8.) TESTING , DEBUGGING AND VALIDATION

8.1) TYPES OF TESTING AND VALIDATIONS

9.) MAINTAINANCE

9.1) TYPES OF MAINTAINANCE

10.) CONCLUSION

11.) SCOPE OF IMPROVEMENT




7 | P a g e

1.) PROBLEM DEFINITION

1.1) INTRODUCTION

The definition of our problem lies in manual system and a fully automated

system.

Manual system: The system is very time consuming and lazy. This system is

more prone to errors and sometimes the approach to various problems is

unstructured.

Technical system : With the advent of latest technology if we do not update

our system then our business result in losses gradually with time. The technical

systems contains the tools of latest trend i.e. computers printers, fax, Internet

etc. The systems with this technology are very fast, accurate, user-friendly and

reliable.




8 | P a g e

1.2) Need of Airlines system

A few factors that direct us to develop a new system are given below -:

1) Faster System

2) Accuracy

3) Reliability

4) Informative

5) Reservations and cancellations from anywhere to any place.




9 | P a g e

1.3) HARDWARE AND SOFTWARE REQUIREMENTS

For the implementation of my project the mirror H/W & S/W requirements as under




10 | P a g e

1.4) METHODOLOGY

System Development Life Cycle

The Systems Development Life Cycle (SDLC) is a conceptual model used in

project management that describes the stages involved in an information system

development project from an initial feasibility study through maintenance of the

completed application. Various SDLC methodologies have been developed to

guide the processes involved including the waterfall model (the original SDLC

method), rapid application development (RAD), joint application development

(JAD), the fountain model and the spiral model. Mostly, several models are

combined into some sort of hybrid methodology. Documentation is crucial

regardless of the type of model chosen or devised for any application, and is

usually done in parallel with the development process. Some methods work

better for specific types of projects, but in the final analysis, the most important

factor for the success of a project may be how closely particular plan was

followed.




11 | P a g e

WATERFALL MODEL-SDLC

The waterfall model of development is an example of a Software Development Life Cycle

(SDLC) model. It is called waterfall because of the way it falls down. This visual aspect is

what affects people’s perceptions of what it does and hence how it is implemented.

The waterfall model is a sequential design process, often used in software development

processes, in which progress is seen as flowing steadily downwards (like a waterfall) through

the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Production /

Implementation and Maintenance.

http://en.wikipedia.org/wiki/Sequence%20/%20Sequence

http://en.wikipedia.org/wiki/Design%20/%20Design

http://en.wikipedia.org/wiki/Software_development_process%20/%20Software%20development%20process


http://en.wikipedia.org/wiki/Waterfall%20/%20Waterfall

http://en.wikipedia.org/wiki/Analysis%20/%20Analysis

http://en.wikipedia.org/wiki/Software_design%20/%20Software%20design

http://en.wikipedia.org/wiki/Software_testing%20/%20Software%20testing

http://en.wikipedia.org/wiki/Implementation%20/%20Implementation


http://en.wikipedia.org/wiki/Software_maintenance%20/%20Software%20maintenance

http://en.wikipedia.org/wiki/Software_maintenance%20/%20Software%20maintenance



http://en.wikipedia.org/wiki/Software_testing%20/%20Software%20testing

http://en.wikipedia.org/wiki/Software_design%20/%20Software%20design

http://en.wikipedia.org/wiki/Analysis%20/%20Analysis

http://en.wikipedia.org/wiki/Waterfall%20/%20Waterfall




http://en.wikipedia.org/wiki/Sequence%20/%20Sequence




12 | P a g e

2.) FEASIBILITY STUDY

Feasibility study is to check the viability of the project under consideration.

Theoretically various types of feasibilities are conducted, but we have conductedthree type of feasibilities explained as under.

2.1 ECONOMIC FEASIBIITY

With the manual system the operating cost of the system is about 60 Lacks P.A.

This cost comprises salary of 25 people, stationary, building rent, electricity,

water, telephone etc. But with the new system this reoccurring cost comes out to

be about 20 Lakhs P.A. Hence the new system is economically feasible.

2.2 TECHNICAL FEASIBILITY

The new system requires only 6 trained people to work with the system and in

overall 10 people per office is sufficient. So we will identify 6 best people from

existing system and train them. As our existing system is purely manual, so we

need a one time investment of Rs 4 Lakhs for the purchase of 7 computers, 5

Ticket printers, a laser printer, AC and networking etc. It requires 20 Lacks PA

as a operating cost. With the above details our system is technically feasible as

after investing 24 Lacks in a year, the company is still saving Rs 25 Lacks PA.

2.3 OPERATIONAL FEASIBILITY.

The new solution is feasible in all sense but operationally it is not. The new

system demands the expulsion of at least 15 people from the company. It creates

an environment of joblessness and fear among the employees. It can lead to an

indefinite strike in the company also. So the management must take corrective

actions prior in advance in order to start the further proceedings




13 | P a g e

3.) SYSTEM ANALYSIS

Systems analysis is the study of sets of interacting entities, including computer

systems analysis. This field is closely related to requirements

analysis or operations research. It is also "an explicit formal inquiry carried out

to help someone (referred to as the decision maker) identify a better course of

action and make a better decision than he might otherwise have made."

The development of a computer-based information system includes a systems

analysis phase which produces or enhances the data model which itself is a

precursor to creating or enhancing a database. There are a number of different

approaches to system analysis. When a computer-based information system is

developed, systems analysis (according to the Waterfall model) would constitute

the following steps:

§ The development of a feasibility study, involving determining whether aproject is economically, socially, technologically and organizationally

feasible.

§ conducting fact-finding measures, designed to ascertain the requirements of

the system's end-users. These typically span interviews, questionnaires, or

visual observations of work on the existing system.

§ Gauging how the end-users would operate the system (in terms of general

experience in using computer hardware or software), what the system would

be used for etc.

This was the most important phase of my project life cycle .It had connected my

maximum time. The block diagram given bellow depicts various facts which

were understood by one during the analysis phase.

http://en.wikipedia.org/wiki/Interaction%20/%20Interaction

http://en.wikipedia.org/wiki/Entity%20/%20Entity

http://en.wikipedia.org/wiki/Requirement_analysis%20/%20Requirement%20analysis


http://en.wikipedia.org/wiki/Operations_research%20/%20Operations%20research

http://en.wikipedia.org/wiki/Data_model%20/%20Data%20model

http://en.wikipedia.org/wiki/Database%20/%20Database

http://en.wikipedia.org/wiki/Waterfall_model%20/%20Waterfall%20model

http://en.wikipedia.org/wiki/Waterfall_model%20/%20Waterfall%20model


http://en.wikipedia.org/wiki/Data_model%20/%20Data%20model

http://en.wikipedia.org/wiki/Operations_research%20/%20Operations%20research



http://en.wikipedia.org/wiki/Entity%20/%20Entity

http://en.wikipedia.org/wiki/Interaction%20/%20Interaction




14 | P a g e

3.1) BLOCKDIAGRAM




15 | P a g e

3.2) DATA COLLECTION

In that phase initially I had observed the system by visiting to Indira Gandhi Airport

(domestic terminal) and a few airline reservation agencies: Pardes Airline agencies, LotusAirline agencies. The above block diagram is an implementation of this observation.

In the next phase I had various queries in my mind, which I tried to ask from appropriate

authorities A sample of my queries is enclosed as Annex 1.

Q.1 Tick mark the features to be included in the new system?

Enquiry

Reservation

Cancellation

Report

Edit

other specify

Q2. Tick mark that the system should be?

Multi-user

Single user

Q3. Tick marks the total time required for the implementation of the project?

3 months

6 months

9 months

Others specify

Q4. Tick marks the reports to be incorporated?

List of all passenger

List of all flights

List of passenger(date wise)

List of passenger (flight wise)

Any other




16 | P a g e

After getting solution my queries I started studying database structure used in the existing

system. In this connection I had come to know about various master files as

In passenger list: Passenger name, Address, tel _ no, d _ o_ b, profession father name,

Fleet info: No aircraft, club_pre_capacity, economic capacity, engine type, cruise speed, air

length,

Flight info: f_name, f_code, f_code, t_exeseat no, t_economic seat no.

Concession: concession name, concession code, class, discount, v_o_t, baggage allowance,

fare.

Move of payment: Passenger code, Date of paid, Current date, cash, Debit, cheque, credit.

Fare: route, destination place, source place, Departure time, Arrival time, Flight code, class,

Fare.

Reservation: Ticket report, PNR, flight code, destination place, source place, departure time

arrival time, Class, number of passenger, Age, sex, Fare, seat.

Enquiry: Ticket no, seat number, pnr.

Cancellation: Pnr, ticket no, Days left, Basic amount, Cancel amount.

Various categories of flight code are display here CD455, IC548, IC7896, IC567, CD445

Flight schedule - gau to Del 12.33 pm to2.33 pm

In this process further I had visited the air port again in order to INTER VIEW people to

know more about the system The main purpose was To analyses the method of calculating

daily income reservation cost generation methods, and few concern things: Duty schedule.




17 | P a g e

4.) SYSTEM DESIGN

In this phase initially I had designed E-R diagram of the processes, in order to

identify various entities and relationship set, entity set, attributers, link

attributes. The Diagram of this process as under.

After this step we had tried design the data base for the new system and

normalized it

The tables motivated in data dictionaries enclosed as annex II is an outcome of

this step

The symbols of entities are shown below:




18 | P a g e

E-R DIAGRAM FOR BOOKING DEPARTMENT




19 | P a g e

4.1) E-R DIAGRAM

E-R DIAGRAM FOR CANCELLATION




20 | P a g e

4.2) DATA FLOW DIAGRAM

In order to design a better solution. I had designed the DFD for system including all technical

processing details is given bellow

LEVEL 0 DATA FLOW DIAGRAM




21 | P a g e

LEVEL 1 DATA FLOW DIAGRAM OF GENERAL

ENQUIRY SYSTEM




22 | P a g e

LEVEL 1 DATA FLOW DIAGRAM OF PASSENGER ENQUIRY

SECTION




23 | P a g e

LEVEL 2 DFD OF BOOKING




24 | P a g e

LEVEL 2 DFD OF CANCELLATION




25 | P a g e

ALGORITHM

In this phase further I had designed algorithms for various technical sub problem a few than

are enclosed here with.

RESERVATION

A PERSON COME TO RESERVE A TICKET.

THEN HE GIVES HIS FULL DETAILS

IN CUSTOMER FORM THOSE DETAILS WERE WRITTEN.

THEN COMPUTER CHEQUE THE DATE WHAT DATE THE PERSON

RESERVED

DATE WISE IT CHEQUE THE FLIGHTS

IF THE FLIGHT IS FLING THAT DAY

THEN SYSTEM JUSTIFY THE SPECIFIC FLIGHT ID

IT CHEQUE ITS SEAT CLASS.

IF THE PASSENGER WANTS TO ECONOMIC CLASS AND WINDOW SIDE

SEAT

THEN SYSTEM CHEQUE IF THERE ANY SEAT IN ECONOMIC CLASS

WHICH IS INSIDE THE WINDOW

IF SEAT IS EMPTY THEN SYSTEM RESERVED THE SEAT.

THEN TICKET IS GENERATED.




26 | P a g e

THE TICKET IS CONFIRMED.

IF THE CONDITION IS NOT APPLIED THEN IT CHEQUE NEXT SEAT

AND JUSTIFIED IT.

IF IT IS NOT ALSO EMPTY THEN IT CHEQUE NEXT BY NEXT.

IF THERE IS NO SEAT THEN SYSTEM TAKE TICKET WHICH IS NOT

CONFIRMED

THEN IT GIVE WAITING LIST.

END.

CANCELLATION

A PASSENGER COME TO CANCEL THE TICKET

THEN THE SYSTEM OPEN THE DELET FORM

THEN CLICK SHOE COMMAND

IT DISPLAY ALL THE PASSENGER LIST

THEN SELECT THE PNR NUMBER AND CLICK DELET OPTION

THE SYSTEM SHOWS RECORD IS DELETED.




27 | P a g e

WHEN PASSENGER COME TO RESERVED A TICKET THEN SYSTEM FIND

OUT THE FLIGHT DETAILS.

SYSTEM CLICK FLIGHT DETAILS OPTION THEN THE FLIGHT DETAILS

FORM OPEN

THOSE SYSTEMS ARE FOLLOWED.

FLIGHT_DETALS:-

. IN FLIGHT DEAILS WE FIRST CREATE A FORM.

. THEN WE MAKE ALL TEXT BOX.

. WE CREATE COMMAN BOX..

. IN THIS FORM WE ARE USE VARIOUS COMMAND BOX THOSE ARE

PREVIOUS, FIRST, NEXT, ADD, NEW, UPDATE, DELETE, SAVE

. IN THIS FORM WE ADD NEW FLIGHT RECORD AND UPDATE IT THEN

THE

VALU IS GO TO THE DATABASE.

.WHEN WE CLICK NEXT , LAST , PREVIOUS, FIRST COMMAND

BUTTON

THEN IT SHOW VARIOUS THING SERIALLY.

A PERSON COME TO KNOW THE TIMMINGS FOR THE FLIGHT WHICH IS

GO FROM DELHI TO GAU.

THEN WE CLICK SHOW COMMAND BUTTON.




28 | P a g e

CONCESSION

FIRST IT CLICK THE CONCESSION BOX.

CONCESSION BOX OPEN

IT SELCT THE CETEGORI.

THEN IT IS CALCULATE.

AND THE FARE IS CALCULATE.

THEN FINAL FARE IS GENERATE IN TICKET.




29 | P a g e

4.3) INPUT SCREEN

As a last step in design phase I had designed various Input and output inter phase screen

.The sample format of this screens is enclosed in annex III...

THIS IS A PICTURE OF THE MAIN MENU.

In this picture there are three parts. Those are master file, ticket, report,

When we click in master file then it show six forms those are custodial, concession

Flight info, fleet info, fare, payment. when we click any one of this then the form is

Open. Now we open each file one by one.




30 | P a g e

THIS IS A FORM OF CUSTOMER DETAIL

In this form we enter the customer detail. When we enter the new name

then we click add button and then update .Then it is automatically update .This

is under master file. In this form first button work for show first record

,next button work for show next record. Preview show the just preview

record.




31 | P a g e

THIS IS A FORM OF CONCESSION

In this form there are several concession type are shown.

Those concessions are

1.Student

2. Senior citizen.

3.Cancer patient.

4. Blind passenger.

5. Armed force.

6. Youth fare.

7. Loco motor




32 | P a g e

When we click any one of them the relevant condition are open.

In this form when we click locomotors category then it show its conditions

Code ………..7

Class………….economic

Discount………50%

v_o_t………….1 year

Baggage allowance..20kg

Fare basis ………….service concerned.




33 | P a g e

THIS IS A FORM OF FLIGHT INFORMATION

In this form we are watching the flight information .It has several fields

those are:

Flight name

Flight code

Class code

Class name

Total seat number

In this form we enter the flight detail .When we enter the new flight then we

click add button and then update .Then it is automatically update .This is under

master file.

In this form first button work for show first record ,next button work for show

next record. Preview show the just preview record.




34 | P a g e

THIS IS A FORM OF FLEET INFORMATION.

Fleet information is a special type of form in this form there are some field are

include .In db como1 list of flight are coming when we click in run time. In fleet

information there are basic type of flights those are

737-400

737-500 Clube pre capacity……….00

737-700 Economic capacity…………62

737-800 Engine type…………………PW127F

737-900 Cruisespeed…………………511km/hr

Air length……………………27.17N

Wing spam………………….27.0 N




35 | P a g e

THIS IS A FORM OF THE ROUTE BASIS FARE.

This is a form of fare in this fare form there are various fields those are

Route

S_place

D_place

Via

D_time

A_time

Stoppage

Flight_code

Class_code Fare




36 | P a g e

In this form we enter the fare detail .When we enter the new fare then we click

add button and then update .Then it is automatically update .This is under master

file.In this form first button work for show first record ,next button work for

show next record. Preview show the just preview record




37 | P a g e

THIS IS A FORM OF RESERVATION.

This is reservation form or ticket .PNR number are generated

automatically .When click passenger age then fare is coming by the

route based. When we click total button then total fare is shown. When

we click in Print command button then the ticket is print. And when weclick in exit button then the form is closed.




38 | P a g e

THIS FORM IS ENQUIRY.

This is a form of ENQUIRY.

If any person come to AIRPOART want to know that its seat

reserved or not

Then system open the enquiry form and put the value of ticket no

and click confirm box .If it is confirmed then it show value of the all

concerning data .

Either show not confirmed.




39 | P a g e

THIS IS A CANCELLATION FORM.

This is a form of cancellation .When a person come to cancel his ticketthen, in the form the passenger code are put and click the show button

system will show the value of data and refund amount. Then click on the

cancel command. Then automatically the record is deleted.




40 | P a g e

4.4) TABLES

THE LIST OF TABLE IS WRITTEN HERE WHICH ARE USED IN DATABASE.

CUST_DETAIL

FIELD TYPE TYPE DESCRIPTION

T _DATE TEXT TRAVEL DAT

CUST_NAME TEXT CUSTOMER NAME

FATHER _NAME TEXT CUSTOMER FATHER NAME

GENDER TEXT GENDER OF CUSTOMER

D_O_B DATE/TIME DATE OF

BIRTHOFCUCTOMER

ADDRESS TEXT ADDRESS OF CUSTOMER

TEL_NO NUMBER CUSTOMER TELPHONE

NUMBER

PROFESSION TEXT PROFESSION OF

CUSTOMER

SECURITY TEXT SECURITY OF CUSTOMER

CONCESSION TEXT CONCESSION OF SECURITY

F_NAME TEXT FLIGHT NAME

F_CODE NUMBER FLIGHT CODE

C_CODE TEXT CLASS CODE

T_EXE SEATNO NUMBER TOTAL EXECUTIVE

SEATNUM,BER

T_ECO SEATNO NUMBER TOTAL ECONOMIC SEAT

NUMBER




41 | P a g e

FLIGHT INFORMATION




T_EXE SEAT NO NUMBER TOTAL EXECUTIVE

SEAR NUMBER

T_ECO SEAT NO NUMBER TOTAL ECONOMIC

SEAT NUMBER

FLEET INFORMATION

FIELD NAME DATATYPE DESCRIPTION

NO_AIRCRAFT TEXT NUMBER OF AIRCRAFT

CLUB_PRE_CAPACITY TEXT CLUB PRE CAPACITY

ECO_CAPACITY TEXT ECONOMIC CAPACITY

ENGINE_TYPE TEXT ENGINE TYPE

CRUISESPEED TEXT CRUISESPEED

AIR_LENGTH TEXT LENGTH OF AIR

WING_SPAM TEXT WING_SPAM




42 | P a g e

CONCESSION

CONCE_NAME TEXT CONCESSION NAME

CONCE_CODE NUMBER CODE OF CONCESSION

CLASS TEXT CLASS OF CONCESSION

DISCOUNT TEXT DISCOUNT CONCESSION

BASIS

V_O_T TEXT VALIDITY OF TICKET

BAG_ALLOW TEXT BAGGAGE ALLOWANCE

FARE_BASIC TEXT FARE BASIC FIXED

FARE

FIELD NAME DATATYPE DESCRIPTION

ROUTE_CODE TEXT CODE NUMBER OF ROUTE

S_PLACE TEXT SOURCE PLACE

VIA TEXT VIA

D_PLACE TEXT DESTINATION PLACE

D_TIME DATE/TIME DEPARTUE TIME

A_TIME DATE/TIME ARRIVAL TIME

F_CODE TEXT FLIGHT CODE


FARE TEXT FARE OF CLASS




43 | P a g e

TICKET REPORT

TICKET NO NUMBER TICKET NUMBER

PNR NUMBER PASSENGER NUMBER

F_ID TEXT FLIGHT ID

S_PLACE TEXT SOURCE PLACE

D_PLACE TEXT DESTINATION PLACE

T_DATE TEXT TRAVEL DATE

D_TIME DATE/TIME DEPARTURE TIME

A_TIME DATE/TIME ARIVAL TIME

FARE 1 NUMBER FARE OF

FIRSTPASSENGER

FARE 2 NUMBER FARE OF SECOND

PASSENGER


HIRDPASSENGER

FARE 4 NUMBER FARE OF FOURTH

PASSENGER


FIFTHPASSENGER


SIXTHPASSENGER

SEAT_NO 1 NUMBER SEAT NUMBER OF 1ST

PASSENGER

SEAT_NO 2 NUMBER SEAT NUMBER OF 2ND

PASSENGER

SEAT_NO 3 NUMBER SEAT NUMBER OF 3RD




44 | P a g e

PASSENGER

SEAT_NO 4 NUMBER SEAT NUMBER OF 4TH

PASSENGER


PASSENGER


PASSENGER

AGE 1 NUMBER AGE OF 1ST

PASSENGER

AGE 2 NUMBER AGE OF2ND PASSENGER

AGE 3 NUMBER AGE OF 3RD

PASSENGER

AGE 4 NUMBER AGE OF 4TH

PASSENGER


PASSENGER


PASSENGER

CLASS TEXT CLASS

PASSENGER NUMBER TOTAL PASSENGER




45 | P a g e

ENQUIRY

T_NO TEXT TICKET NUMBER



C_SEATNO NUMBER CLASS SEAT NUMBER

C_FARE NUMBER CLASS FARE

CUST_CODE NUMBER CUSTOMER CODE


T_TIME DATE/TIME TRAVEL TIME

CANCELLATION

CUST_CODE TEXT CUSTOMER CODE

CLASS TEXT CLASS

S_NO NUMBER SEAT NUMBER

DAYS LEFT DATE/TIME DAYS LEFT

HOURS LEFT DATE/TIME HOURS LEFT

BASIC AMMOUNT TEXT BASIC AMMOUNT

CANCELAMMOUNE NUMBER CANCEL AMMOUNT

RULES

DATE FROM DEP TEXT DATE FROM DEPARTURE

PERCENTAGE TEXT PERCENTAGE OF CANCEL

REFUND NUMBER REFUND AMMOUNT




46 | P a g e

TERMS

AGE TEXT AGE OF PASSENGER

SEX TEXT SEX OF PASSENGER

FARE NUMBER FARE OF PASSENGER

RESERVED SEATS

F_CODE TEXT FLIGHT CODE

T_RES_ECO_SEAT NUMBER TOTAL RESERVED

ECONOMIC SEAT

T_RES_EXE_SEAT TEXT TOTAL RESERVED

EXECUTIVE SEAT


WAITING_NO NUMBER WAOTING LIST




47 | P a g e

5.) REPORTS

CONCESSION REPORTS ARE SHOWN BELLOW

This is report of concession .Various type of concession category are

shown upper.




48 | P a g e

THIS IS A REPORT OF CUST DETAIL

When we put passenger detail in passenger record then it is automatically

set in report list.




49 | P a g e

THIS IS FLEET INFORMATION REPORT




50 | P a g e

THIS IS A REPOT OF ALL FLIGHT




51 | P a g e

6.) CODINGS AND DEVELOPINGS

The coding of the project under consideration is enclosed in annex - IV

Coding for Reservation

Option Explicit

Dim adors As Recordset

Dim adors1 As Recordset

Dim ADORS2 as Recordset

Private Sub Combo1_Click ()

If Val (Combo1.Text) = 1 Then

Text3 (1).Visible = False





Text3 (0).Visible = True

Combo3 (1).Visible = False





Combo3 (0).Visible = True





52 | P a g e












End If























53 | P a g e







End If





























54 | P a g e

End If


























End If







55 | P a g e























End If

If Val (Combo1.Text) = 6 ThenText3 (1).Visible = True










56 | P a g e


















End If

End Sub

Private Sub Combo3_Click (Index As Integer)

Dim ADORS2 As ADODB.Recordset

Dim var2 As Integer

Dim var3 As Integer

Dim db As Connection

Set db = New Connection

db.Open "Provider=MSDASQL.1;Persist Security Info=False;Data Source=NATH"

Set ADORS2 = New ADODB.Recordset

Adodc1.RecordSource = "select * from fixed where f_code ='" &

RTrim(LTrim(DBCombo1.Text)) & "' and tdate = '" & RTrim(LTrim(Text8.Text)) & "'"

Adodc1.Refresh

ADORS2.Open "select * from fixed", db, adOpenStatic, adLockOptimistic




57 | P a g e

var2 = ADORS2.Fields!t_res_eco_seat

Text6(Index).Text = var2 + 1

End Sub

Private Sub Command1_Click()

Text2.Text = Val(Text4(0).Text) + Val(Text4(1).Text) + Val(Text4(2).Text) +

Val(Text4(3).Text) + Val(Text4(4).Text) + Val(Text4(5).Text)

End Sub

Private Sub DBCombo1_Change()

On Error Resume Next

MSRDC1.Resultset.Bookmark = DBCombo1.SelectedItem

End Sub

Private Sub DBCombo1_Click(Area As Integer)

On Error Resume Next

MSRDC1.Resultset.Bookmark = DBCombo1.SelectedItem

End Sub

Private Sub Form_Load()




Set adors = New Recordset

ADORS2.Open "select

ticket_no,pnr,flight_id,source,destination,t_date,d_time,a_time,fare1,fare2,fare3,fare4,far

e5,fare6,class,age1,sex1,seat1,age1,sex1,seat1,age2,sex2,seat2,age3,sex3,seat3,age4,sex4,

seat4,age5,sex5,seat5,age6,sex6,seat6,passenger from ticket_report", db, adOpenStatic,

adLockOptimistic

Dim otext As TextBox




58 | P a g e

For Each otext In Me.Text1

Set otext.DataSource = adors

Next



Set adors1 = New Recordset

Set ADORS2 = New Recordset

adors1.Open "select max(TICKET_NO)from ticket_report", db, adOpenStatic,

adLockOptimistic

ADORS2.Open "select max(pnr) from ticket_report", db, adOpenStatic,

adLockOptimistic

var1 = adors1.Fields(0)

var2 = ADORS2.Fields(0)

Text1(0) = var1 + 1

Text1(17) = var2 + 1

adors.Open "select * FROM FARE", db, adOpenStatic, adLockOptimistic

Set Text1(1).DataSource = adors




End Sub

Private Sub PRINT_Click()

Ticket_report.Print

End Sub




59 | P a g e

Private Sub save_Click()

adors.UpdateBatch adAffectAllChapters

End Sub

Text3_LostFocus(Index As Integer)

Dim temp As Double

If Val(Text3(Index).Text) > 60 Then

temp = (5 * Val(Text5.Text) / 100)

MsgBox (temp)

Text4(Index).Text = temp

Else

temp = Val(Text5.Text)

End If

Text4(Index).Text = temp

End Sub




60 | P a g e

Coding for Cancellation

Option Explicit


Private Sub CANCEL_Click()

Dim SQL As String




SQL = "DELETE FROM TICKET_REPORT WHERE PNR='" & txtfields(0).Text & "'"

db.Execute SQL

End Sub

Private Sub Command3_Click()

Unload Me

End Sub

Private Sub Form_Load()





adors.Open "select

CUST_CODE,CLASS,SEAT_NO,DAYS_LEFT,HOURS_LEFT,BASIC_AMMOUNT,

CANCEL_AMMOUNT FROM REFUND_AMMOUNT", db, adOpenStatic,

adLockOptimistic


For Each otext In Me.txtfields


Next

End Sub




61 | P a g e

Private Sub SHOW_Click()

Dim ADORS2 As Recordset





ADORS2.Open "select * from TICKET_REPORT WHERE PNR = ' " &

txtfields(0).Text & " ' ", db, adOpenStatic, adLockOptimistic

'txtfields(0) = (ADORS2.Fields(1))

txtfields(1) = (ADORS2.Fields(8))


txt_basic_ammount.Text = (ADORS2.Fields(9))

End Sub

Private Sub txtfields_LostFocus(Index As Integer)


If Index = 0 Then




adors.Open "select

CUST_CODE,CLASS,SEAT_NO,DAYS_LEFT,HOURS_LEFT,BASIC_AMMOUNT,

CANCEL_AMMOUNT FROM REFUND_AMMOUNT where cust_code = ('" &

txtfields(0).Text & "')", db, adOpenStatic, adLockOptimistic


For Each otext In Me.txtfields


Next

End If

End Sub




62 | P a g e

Private Sub txtsub_Click()

txtresult(7).Text = Val(txt_basic_ammount.Text) - Val(txt_cancel_ammount(6).Text)

End Sub

Coding for Enquiry

Option Explicit


Private Sub add_Click(Index As Integer)

With adors

.AddNew

End With

End Sub

Private Sub cl_Click(Index As Integer)

Unload Me

End Sub

Private Sub CONFIRM_Click()

Dim ADORS2 As Recordset





ADORS2.Open "select * from TICKET_REPORT WHERE TICKET_NO ='" &

txtfields(7).Text & "'", db, adOpenStatic, adLockOptimistic







End Sub




63 | P a g e

7.) SYSTEM IMPLEMENTATION

Implementation is the realization of an application, or execution of a plan, idea, model, design, specification, standard, algorithm, or policy.

In computer science, an implementation is a realization of a technical

specification or algorithm as a program, software component, or other computer

system through programming and deployment. Many implementations may

exist for a given specification or standard. For example, web browsers contain

implementations of World Wide Web Consortium-recommended specifications,and software development tools contain implementations of programming

languages.

7.1 Steps implementation

Steps of implementation are:

forms heading.

http://en.wikipedia.org/wiki/Plan%20/%20Plan

http://en.wikipedia.org/wiki/Scientific_modelling%20/%20Scientific%20modelling


http://en.wikipedia.org/wiki/Specification%20/%20Specification

http://en.wikipedia.org/wiki/Standardization%20/%20Standardization

http://en.wikipedia.org/wiki/Algorithm%20/%20Algorithm

http://en.wikipedia.org/wiki/Policy%20/%20Policy

http://en.wikipedia.org/wiki/Computer_science%20/%20Computer%20science

http://en.wikipedia.org/wiki/Computer_program%20/%20Computer%20program

http://en.wikipedia.org/wiki/Software_component%20/%20Software%20component

http://en.wikipedia.org/wiki/Computer_system%20/%20Computer%20system


http://en.wikipedia.org/wiki/Programming%20/%20Programming

http://en.wikipedia.org/wiki/Software_deployment%20/%20Software%20deployment

http://en.wikipedia.org/wiki/Web_browser%20/%20Web%20browser

http://en.wikipedia.org/wiki/World_Wide_Web_Consortium%20/%20World%20Wide%20Web%20Consortium

http://en.wikipedia.org/wiki/Programming_languages%20/%20Programming%20languages




http://en.wikipedia.org/wiki/World_Wide_Web_Consortium%20/%20World%20Wide%20Web%20Consortium

http://en.wikipedia.org/wiki/Web_browser%20/%20Web%20browser

http://en.wikipedia.org/wiki/Software_deployment%20/%20Software%20deployment

http://en.wikipedia.org/wiki/Programming%20/%20Programming



http://en.wikipedia.org/wiki/Software_component%20/%20Software%20component

http://en.wikipedia.org/wiki/Computer_program%20/%20Computer%20program

http://en.wikipedia.org/wiki/Computer_science%20/%20Computer%20science

http://en.wikipedia.org/wiki/Policy%20/%20Policy

http://en.wikipedia.org/wiki/Algorithm%20/%20Algorithm

http://en.wikipedia.org/wiki/Standardization%20/%20Standardization

http://en.wikipedia.org/wiki/Specification%20/%20Specification


http://en.wikipedia.org/wiki/Scientific_modelling%20/%20Scientific%20modelling

http://en.wikipedia.org/wiki/Plan%20/%20Plan




64 | P a g e

8.) TESTING, DEBUGGING AND VALIDATION

Software testing is an investigation conducted to provide stakeholders with

information about the quality of the product or service under test. Software testing

can also provide an objective, independent view of the software to allow the

business to appreciate and understand the risks of software implementation. Test

techniques include, but are not limited to, the process of executing a program or

application with the intent of finding software bugs (errors or other defects).

Software testing can be stated as the process of validating and verifying that a

software program/application/product:

1. meets the requirements that guided its design and development;

2. Works as expected; and

3. Can be implemented with the same characteristics.

Software testing, depending on the testing method employed, can be implemented at

any time in the development process. However, most of the test effort occurs after

the requirements have been defined and the coding process has been completed.

As such, the methodology of the test is governed by the software development

methodology adopted.

http://en.wikipedia.org/wiki/Software_bug%20/%20Software%20bug





65 | P a g e

8.1) Types of Testing and Validations:

1. The box approach

Software testing methods are traditionally divided into white- and black-box

testing. These two approaches are used to describe the point of view that a test

engineer takes when designing test cases.

1.1 White box testing

White box testing is when the tester has access to the internal data structures

and algorithms including the code that implement these.

Types of white box testing

The following types of white box testing exist:

§ API testing (application programming interface) - testing of the

application using public and private APIs

§ Code coverage - creating tests to satisfy some criteria of code

coverage (e.g., the test designer can create tests to cause all statements

in the program to be executed at least once)

§ Fault injection methods - improving the coverage of a test byintroducing faults to test code paths

§ Mutation testing methods

§ Static testing - White box testing includes all static testing

Test coverage

White box testing methods can also be used to evaluate the completeness

of a test suite that was created with black box testing methods. Thisallows the software team to examine parts of a system that are rarely

tested and ensures that the most important function points have been

tested.

Two common forms of code coverage are:

§ Function coverage, which reports on functions executed

§ Statement coverage, which reports on the number of lines executed to

complete the test

http://en.wikipedia.org/wiki/Application_programming_interface%20/%20Application%20programming%20interface

http://en.wikipedia.org/wiki/Code_coverage%20/%20Code%20coverage

http://en.wikipedia.org/wiki/Fault_injection%20/%20Fault%20injection

http://en.wikipedia.org/wiki/Mutation_testing%20/%20Mutation%20testing

http://en.wikipedia.org/wiki/Static_testing%20/%20Static%20testing

http://en.wikipedia.org/wiki/Function_points%20/%20Function%20points

http://en.wikipedia.org/wiki/Function_points%20/%20Function%20points

http://en.wikipedia.org/wiki/Static_testing%20/%20Static%20testing

http://en.wikipedia.org/wiki/Mutation_testing%20/%20Mutation%20testing

http://en.wikipedia.org/wiki/Fault_injection%20/%20Fault%20injection


http://en.wikipedia.org/wiki/Application_programming_interface%20/%20Application%20programming%20interface




66 | P a g e

They both return a code coverage metric, measured as a percentage.

1.2 Black box testing

Black box testing treats the software as a "black box" — without any knowledge

of internal implementation. Black box testing methods include: equivalence

partitioning, boundary value analysis, all-pairs testing, fuzz testing, model-

based testing, exploratory testing and specification-based testing.

Specification-based testing: Specification-based testing aims to test the

functionality of software according to the applicable requirements.Thus, the tester inputs data into, and only sees the output from, the test

object. This level of testing usually requires thorough test cases to be

provided to the tester, who then can simply verify that for a given

input, the output value (or behavior), either "is" or "is not" the same as

the expected value specified in the test case

Specification-based testing is necessary, but it is insufficient to guard

against certain risks.

Advantages and disadvantages: The black box tester has no "bonds"

with the code, and a tester's perception is very simple: a code must have

bugs. Using the principle, "Ask and you shall receive," black box testers

find bugs where programmers do not. On the other hand, black box

testing has been said to be "like a walk in a dark labyrinth without a

flashlight," because the tester doesn't know how the software being tested

was actually constructed. As a result, there are situations when

(1) A tester writes many test cases to check something that could have

been tested by only one test case, and/or

(2) Some parts of the back-end are not tested at all.


http://en.wikipedia.org/wiki/Software_metric%20/%20Software%20metric

http://en.wikipedia.org/wiki/Percentage%20/%20Percentage

http://en.wikipedia.org/wiki/Equivalence_partitioning%20/%20Equivalence%20partitioning


http://en.wikipedia.org/wiki/Boundary_value_analysis%20/%20Boundary%20value%20analysis

http://en.wikipedia.org/wiki/All-pairs_testing%20/%20All-pairs%20testing

http://en.wikipedia.org/wiki/Fuzz_testing%20/%20Fuzz%20testing

http://en.wikipedia.org/wiki/Model-based_testing%20/%20Model-based%20testing


http://en.wikipedia.org/wiki/Exploratory_testing%20/%20Exploratory%20testing

http://en.wikipedia.org/wiki/Exploratory_testing%20/%20Exploratory%20testing



http://en.wikipedia.org/wiki/Fuzz_testing%20/%20Fuzz%20testing

http://en.wikipedia.org/wiki/All-pairs_testing%20/%20All-pairs%20testing

http://en.wikipedia.org/wiki/Boundary_value_analysis%20/%20Boundary%20value%20analysis



http://en.wikipedia.org/wiki/Percentage%20/%20Percentage

http://en.wikipedia.org/wiki/Software_metric%20/%20Software%20metric





67 | P a g e

Therefore, black box testing has the advantage of "an unaffiliated opinion",

The one hand, and the disadvantage of "blind exploring", on the other.

1.3 Grey box testing

Grey Box Testing (American spelling: gray box testing) involves having

knowledge of internal data structures and algorithms for purposes of designing

the test cases, but testing at the user, or black-box level. The tester is not

required to have a full access to the software's source code. Manipulating input

data and formatting output do not qualify as grey box, because the input and

output are clearly outside of the "black-box" that we are calling the system

under test. This distinction is particularly important when conducting

integration testing between two modules of code written by two different

developers, where only the interfaces are exposed for test. However, modifying

a data repository does qualify as grey box, as the user would not normally be

able to change the data outside of the system under test. Grey box testing may

also include reverse engineering to determine, for instance, boundary values or

error messages.

By knowing the underlying concepts of how the software works, the tester

makes better-informed testing choices while testing the software from outside.

Typically, a grey box tester will be permitted to set up his testing environment;

for instance, seeding a database; and the tester can observe the state of the

product being tested after performing certain actions. For instance, he/she may

fire an SQL query on the database and then observe the database, to ensure that

the expected changes have been reflected. Grey box testings implements

intelligent test scenarios, based on limited information. This will particularly

apply to data type handling, exception handling, and so on.

http://en.wikipedia.org/wiki/Integration_testing%20/%20Integration%20testing

http://en.wikipedia.org/wiki/Reverse_engineering%20/%20Reverse_engineering_of_software%20/%20Reverse%20engineering


http://en.wikipedia.org/wiki/SQL%20/%20SQL

http://en.wikipedia.org/wiki/SQL%20/%20SQL


http://en.wikipedia.org/wiki/Reverse_engineering%20/%20Reverse_engineering_of_software%20/%20Reverse%20engineering

http://en.wikipedia.org/wiki/Integration_testing%20/%20Integration%20testing




68 | P a g e

In this phases I had tried to check all the modules separately for there proper

formatting.

After this step I had performed a unit test to check the functionality of the whole

system.

Further I had come to know to add certain validation in project as given below:

1) Table name- Customer information

Field name –Customer name

Data type -Text.

When we enter number in the form then it show wrong .Because it is not number

type, it is a character. So it show wrong value.

2) Table name _Customer information

Field name- Departure time, Arrival time

Data type- Date/Time.

When we enter 12.33 then it automatically shows 12.33pm.

When we enter 11.33 then it automatically shows 11.33am.

3) Table name –Flight information

Field name- Flight-code

Data type- number

When we Put any other value or character then it ask validity check.




69 | P a g e

9.) MAINTAINENCE

Software Maintenance in software engineering is the modification of a software

product after delivery to correct faults, to improve performance or other

attributes.

A common perception of maintenance is that it merely involves fixing defects.

However, one study indicated that the majority, over 80%, of the maintenance

effort is used for non-corrective actions (Pigosky 1997). This perception is

perpetuated by users submitting problem reports that in reality are functionality

enhancements to the system.

Software maintenance and evolution of systems was first addressed by Meir M.

Lehman in 1969. Over a period of twenty years, his research led to the

formulation of Lehman's Laws (Lehman 1997). Key findings of his research

include that maintenance is really evolutionary development and that

maintenance decisions are aided by understanding what happens to systems

(and software) over time. Lehman demonstrated that systems continue to evolve

over time. As they evolve, they grow more complex unless some action such

as code refactoring is taken to reduce the complexity.

http://en.wikipedia.org/wiki/Software_engineering%20/%20Software%20engineering


http://en.wikipedia.org/wiki/Software_evolution%20/%20Software%20evolution

http://en.wikipedia.org/wiki/Meir_M._Lehman%20/%20Meir%20M.%20Lehman


http://en.wikipedia.org/wiki/Software_evolution%20/%20Lehman.27s_Laws_of_Software_Evolution%20/%20Software%20evolution

http://en.wikipedia.org/wiki/Code_refactoring%20/%20Code%20refactoring

http://en.wikipedia.org/wiki/Code_refactoring%20/%20Code%20refactoring

http://en.wikipedia.org/wiki/Software_evolution%20/%20Lehman.27s_Laws_of_Software_Evolution%20/%20Software%20evolution



http://en.wikipedia.org/wiki/Software_evolution%20/%20Software%20evolution


http://en.wikipedia.org/wiki/Software_engineering%20/%20Software%20engineering




70 | P a g e

9.1 Types of Maintenance

· Corrective

Corrective software maintenance involves developing and deploying solutions

to problems ("bugs") that arise during use of a software program. Computer

users will notice performance problems with software, such as error messages

coming on the screen or the program freezing or crashing, meaning corrective

software maintenance is needed. Often these fixes permanently solve the

problem, but not always. Some fixes act as a temporary solution while computer

programmers work on a more permanent solution.

· Perfective

No software program contains zero flaws or areas for improvement. Perfective

software maintenance involves computer programmers working to improve the

way a software program functions or how quickly it processes requests.Programmers may also engage in perfective software maintenance to improve

the software's menu layouts and command interfaces. Sometimes programmers

need to conduct perfective maintenance on software because of outside

influences, such as new government regulations that affect how a business

operates.

· Adaptive

The field of technology constantly changes through both hardware and software

developments. Adaptive software maintenance addresses these changes. A

change in a processor's speed, for example, will affect how the software

performs on a single computer. Software interacts with other software programs

on a computer or network, meaning changes in one program can require




71 | P a g e

changes in other programs. A user will eventually introduce new software to the

computer or network, which can also affect how other software already present

operates.

· Preventative

When computer programmers engage in preventative software maintenance

they try to prevent problems with software programs before they occur.

Programmers seek to prevent corrective maintenance as much as possible, while

also anticipating adaptive maintenance needs before users experience problems.

Computer programmers test software, as automotive companies test the vehicles

they make, to make sure the software can handle high data loads and other

stressful operations without problems. Computer programmers also test the

software with other programs users likely will use on their computers, making

sure compatibility issues do not arise.




72 | P a g e

10. CONCLUTION

Though the system still containing lot of scope of improvement in it. But its

overall look and feel gives rough picture of on existing automation system.

I have take MS-Access at backhand but it has a limitation of 1 GB size .It over

data size approaches this 1gb some other database the SQL server ,oracle, can

be used with OBBC to break this barrier.

When looking for solid AIRLINE RESERVATION SYSTEM software, you

want to find a solution that gives you the easy way of booking ticket. Naturally,

you first want to find the software that meets your needs, both now and in the

future. Engineering is based on designing different projects. Nowadays,” most

products and systems are becoming more complex in nature, and there is an

increasing demand relative to new product technology applications at a time

when our natural resources are dwindling” now that’s where engineering jumps

in. Business depending on natural resources is no longer in a safe position.

Engineering and engineers are not only useful for the technologies and

machineries in the business world, but it is also constructive in different

components of business such as entertainment, telecommunication and etc.




11. SCOPE OF IMPROVEMENT

Airline reservations systems contain airline schedules, fare tariffs, passenger

reservations and ticket records. An airline's direct distribution works within

their own reservation system, as well as pushing out information to the

GDS. Second types of direct distribution channel are consumers who use the

internet or mobile applications to make their own reservations. Travel

agencies and other indirect distribution channels access the same GDS as

those accessed by the airlines' reservation systems, and all messaging is

transmitted by a standardized messaging system that functions on two types

of messaging that transmit on SITA's HLN [high level network]. These

message types are called Type A [TTY] for remarks-like communications

and Type B [EDIFCT] for secured information. Message construction

standards are set by IATA and ICAO, are global, and apply to more than air

transportation. Since airline reservation systems are business critical

applications, and their functionally quite complex, the operation of an in-

house airline reservation system is relatively expensive.

Mis Project Main Project for Externals (2)

Documents

Transcript of Mis Project Main Project for Externals (2)