flight ticket portal project

7/24/2019 Flight Ticket Portal PROJECT

1/40

CHAPTER - 1

INTRODUCTION

In todays airline industry users or customers can reserve seat or book flight from any

place in the world as long as they are connected to internet. The Innovation of technology has

made traveling in the air easier for customers with airline reservation or booking just a click

away. The fastest means of transportation today is by air. Thousands of people flock the airline

industry this days so that they can arrive their destination within a short period of time. Vehicles,

train e.t.c cannot drive across the Atlantic cean or the !acific cean, so customers tend to

travel to other state, countries, and continents using air transportation. Their by with an hours

interval the customers would have arrive their destination. Therefore, if thousands of people use

the aero" planes on a daily basis to travel from one place to another.

Cost Estimation and Scheduling

The most common way of carrying out an economic assessment of software is by

comparing the e#pected cost of development and operation of the system with the benefits of

having it in place. $oftware cost is related to human, technical, environment, political and effort

applied to develop it.

There are many software cost estimation techni%ues available. &ere ''( model is

used for cost estimation. 'omputing the development time using intermediate ''( model

is done in two stages. The parameter, the length of the product is estimated. Then using this

normal effort is calculated. This project is considered to be essentially straightforward and hence

it comes under organic mode. The normal effort )in person"months* is given by,

+ormal ffort - ./ )0.0*1.20

- 1/ person" months

To calculate the effort estimate, use the effort estimate3

4uration, 4 - .0)1/*2.0

- 0.5months

1


2/40

The value for project duration enables the planner to determine a recommended number

of people, +, for the project. 6hen calculating the number of people appro#imately seventeen

persons are included.

1. Scheduling

$cheduling is the culmination of a planning activity that is a primary component of

software project management. 6hen combined with estimation methods and risk analysis,

scheduling establishes a road map for the project manager. $cheduling begins with process

decomposition.

The scheduling is done with these functionally. The steps are given below.

Identify the task needed to complete the project.

4etermine the dependency among different tasks.

stablish the most likely estimates for the duration of the identified task.

$cheduling is the rudimentary process, which makes the project to be developed in stipulated

time period. 7y applying the above schedule the project has been developed successfully.

2


3/40

CHAPTER

!AC"#ROUND STUD$

E%isting S&stem

In the current flight booking system is a manual one, where the receiver )travel agency*

should receive their booking details and enter into the form if that is made on $($. In such

systems customers feels very difficult because if they need to book the ticket, they must use

internet and book the flights. And this is very difficult to the travel agency admin too.

D'a()ac*s

(anual work

(ore time consuming

not proper booking details

'hances for clerical errors

$toring and retrieving the movie ticket details it is very difficult

P'o+osed S&stem

In the proposed system, flight ticket booking has done by systematically. The advantage of the

project is, this increases the reliability in flight ticket booking for both users and travel agencies.

8sing the proposed system, the user can book their flight ticket via $($. In the recent trend, the

proposed project of ticketing through non"internet based mobile phones has been developed

using .net platform. This will enable people using non" internet based mobile phones to easily

access ticketing services through $($.

Ad,antages

Automatic entry of booking details from $($.

asy and reliable.

8ser doesnt need internet to book flight.

asy and effective

9educes the manual work.

Net(o'* s+eciication

3


4/40

De,ice s+eciication A'chitectu'e A mobile phone with a built"in :$( modem, or

alternatively a dedicated :$( modem

;ig3


5/40

1. 'ustomer details registration

. $($ '&A++=

a. 9eceiving $($

b. $ending $($


6/40

The third module implements the content e#traction from received $($. The system

performs the regular e#pression concept to split the received content. The content from the $($

should have flight id, name, age and other relevant details in appropriate format.

2. Tic*et !loc*ing

After successful content e#traction, the system verifies the availability of tickets and

performs the ticket blocking process. nce the data has been entered in the database, the

confirmation message will send to the users mobile via $($.

3. T'ansaction and Pa&ment /odule

After ticket booking, the system will send a confirmation message, the user should pay

amount via online. In order to provide optimal booking option, the system provides 0 days time

to pay amount online. 6ith the consideration of security threads, the system avoided the $($

based payment, so the user should pay amount via online.

4. Re+o'ts

;inally the system generates possible reports such as customer details, ticket booking

details and flight information reports.

CHAPTER - 2

S$STE/ RE5UIRE/ENTS

2.1 HARD6ARE RE5UIRE/ENTS

6


7/40

The most common set of re%uirements defined by any operating system or software

application is the physical computer resources, also known as hardware, a hardware re%uirements

list is often accompanied by a hardware compatibility list )&'=*. An &'= lists tested,

compatible, and sometimes incompatible hardware devices for a particular operating system or

application.

!rocessor 3 Intel Duel co'e

9A( 3 #!

&ard 4isk 3 78#!

!rinter 3 HP In* 9et

?eyboard 3 Samsung

(ouse 3 0ogi Tech :O+tical;

2. SO


8/40

1. To provide a consistent object"oriented programming environment whether object

codes is stored and e#ecuted locally on Internet"distributed, or e#ecuted remotely.. To provide a code"e#ecution environment to minimi@es software deployment and

guarantees safe e#ecution of code.


9/40

9obustness.

!erformance.

SECURIT$

The runtime enforces code access security. The security features of the runtime thus

enable legitimate Internet"deployed software to be e#ceptionally featuring rich.

RO!USTNESS

The runtime also enforces code robustness by implementing a strict type" and code"

verification infrastructure called the Common T&+e S&stem :CTS;.The 'T$ ensures that all

managed code is self"describing.

PER


10/40

4evelopers can choose from the following two features when creating an A$!. +T

application.6ebs ;orms and 6ebs services, or combine these in any way they see fit. ach is

supported by the same infrastructure that allows using authentication schemes cache fre%uently

used data, or customi@es your applicationFs configuration, to name only a few possibilities. A$!.

+T provides a simple model that enables 6ebs developers to write logic that runs at the

application level. 4evelopers can write this code in the global.asp# te#t file or in a compiled

class deployed as an assembly.

This logic can include application"level events, but developers can easily e#tend this

model to suit the needs of their 6eb application.A$!. +T provides easy"to"use application and

session"state facilities that are familiar to A$! developers and are readily compatible with all

other . +T ;ramework A!Is. A$!.+T offers the I&ttp&andler and I&ttp(odule interfaces.

A$!. +T takes advantage of performance enhancements found in the .+T ;ramework

and common language runtime. Additionally, it has been designed to offer significant

performance improvements over A$! and other 6eb development platforms. All A$!.+T code

is compiled, rather than interpreted, which allows early binding, strong typing, and just"in"time

)DIT* compilation to native code, to name only a few of its benefits. A$!.+T is also easily

factorable, meaning that developers can remove modules )a session module, for instance* that are

not relevant to the application they are developing.

6eb ;orms allows us to build powerful forms"based 6eb pages. 6hen building these

pages that use A$!. +T server controls to create common 8I elements, and program them for

common tasks. These controls allow to rapidly building a 6eb ;orm out of reusable built"in or

custom components, simplifying the code of a page. An B(= 6eb service provides the means

to access server functionality remotely. 8sing 6eb services, businesses can e#pose

programmatic interfaces to their data or business logic, which in turn can be obtained and

manipulated by client and server applications.

A$!. +T provides e#tensive caching services )both built"in services and caching A!Is*.

A$!. +T also ships with performance counters that developers and system administrators can

monitor to test new applications and gather metrics on e#isting applications. A$!.+T is a

server"side technology. That is, it runs on the web server. (ost web designers cut their teeth

10


11/40

learning client"side technologies such as &T(=, Dava$cript, and 'ascading $tyle $heets )'$$*.

6hen a web browser re%uests a web page created with only client"side technologies, the web

server simply grabs the files that the browser )or client* re%uests and sends them down the line.

The client is entirely responsible for reading the markup in those files and interpreting that

markup to display the page on the screen.

C>.NET

'C language is intended to be a simple, modern, general"purpose, object"oriented

programming language.

The language, and implementations are used to provide support for software

engineering principles such as strong type checking, array bounds checking,

detection of attempts to use uninitiali@ed variables, and automatic garbage

collection. $oftware robustness, durability, and programmer productivity are

important.

The language is intended for use in developing software componentssuitable for

deployment in distributed environments.

$ource code portability is very important, as is programmer portability, especially

for those programmers already familiar with ' and 'GG.

$upport for internationali@ationis very important.


12/40

=ocal variables cannot shadow variables of the enclosing block, unlike ' and 'G

G. Variable shadowingis often considered confusing by 'GG te#ts.

In addition to the try...catch construct to handle e#ceptions, 'C has a try...finally

construct to guarantee e#ecution of the code in the finally block.

(ultiple inheritances are not supported, although a class can implement any

number of interfaces. This was a design decision by the languageFs lead architect

to avoid complication and simplify architectural re%uirements throughout '=I.

numerationmembers are placed in their own scope.

;ull type reflectionand discovery is available.

'C currently has HH reserved words.

DATA ACCESS 6ITH ADO.NET

As develop applications using A4. +T, have different re%uirements for working with

data. +ever need to directly edit an B(= file containing data " but it is very useful to understand

the data architecture in A4.+T.

A4. +T offers several advantages over previous versions of A43

Interoperability

(aintainability

!rogrammability

!erformance $calability

INTEROPERA!I0IT$

12
http://en.wikipedia.org/wiki/Variable_shadowinghttp://en.wikipedia.org/wiki/Multiple_inheritancehttp://en.wikipedia.org/wiki/Enumerated_typehttp://en.wikipedia.org/wiki/Scope_(programming)http://en.wikipedia.org/wiki/Scope_(programming)http://en.wikipedia.org/wiki/Reflection_(computer_science)http://en.wikipedia.org/wiki/Reserved_wordhttp://en.wikipedia.org/wiki/Reserved_wordhttp://en.wikipedia.org/wiki/Variable_shadowinghttp://en.wikipedia.org/wiki/Multiple_inheritancehttp://en.wikipedia.org/wiki/Enumerated_typehttp://en.wikipedia.org/wiki/Scope_(programming)http://en.wikipedia.org/wiki/Reflection_(computer_science)http://en.wikipedia.org/wiki/Reserved_word


13/40

A4.+T applications can take advantage of the fle#ibility and broad acceptance of

B(=. 7ecause B(= is the format for transmitting datasets across the network, any component

that can read the B(= format can process data. The receiving component need not be an A4.

+T component.

/AINTAINA!I0IT$

In the life of a deployed system, modest changes are possible, but substantial,

Architectural changes are rarely attempted because they are so difficult. As the performance load

on a deployed application server grows, system resources can become scarce and response time

or throughput can suffer.

PER


14/40

$A! originally defined as Sim+le O)@ect Access P'otocol, is a protocol specification

for e#changing structured information in the implementation of 6eb $ervices in computer

networks. It relies on #tensible (arkup =anguage )B(=* for its message format, and usually

relies on other Application =ayer protocols, most notably &yperte#t Transfer !rotocol )&TT!*

and $imple (ail Transfer !rotocol )$(T!*, for message negotiation and transmission.

CONSTRUCTORS AND DESTRUCTORS

'onstructors are used to initiali@e objects, whereas destructors are used to destroy them.

In other words, destructors are used to release the resources allocated to the object. In 'C. +T

the sub finali@e procedure is available. The sub finali@e procedure is used to complete the tasks

that must be performed when an object is destroyed. The sub finali@e procedure is called

automatically when an object is destroyed. In addition, the sub finali@e procedure can be called

only from the class it belongs to or from derived classes.

6SD0

The 6e) Se',ices Desc'i+tion 0anguageis an B(="based language that is used for

describing the functionality offered by a 6eb service. A 6$4= description of a web service

provides a machine"readable description of how the service can be called, what parameters it

e#pects, and what data structures it returns. It thus serves a roughly similar purpose as a method

signature in a programming language.

#AR!A#E CO00ECTION

:arbage 'ollection is another new feature in 'C. +T. The . +T ;ramework monitors

allocated resources, such as objects and variables. In addition, the . +T ;ramework

automatically releases memory for reuse by destroying objects that are no longer in use. In 'C.

+T, the garbage collector checks for the objects that are not currently in use by applications.

6hen the garbage collector comes across an object that is marked for garbage collection, it

releases the memory occupied by the object.

UDDI

14


15/40

Uni,e'sal Desc'i+tion Disco,e'& and Integ'ation )UDDI* is a platform"independent,

#tensible (arkup =anguage )B(=*"based registry for businesses worldwide to list themselves

on the Internet and a mechanism to register and locate web service applications. 844I was

originally proposed as a core 6eb service standard. It is designed to be interrogated by $A!

messages and to provide access to 6e) Se',ices Desc'i+tion 0anguage :6SD0;documents

describing the protocol bindings and message formats re%uired to interact with the web services

listed in its directory.

/U0TITHREADIN#

'C . +T also supports multithreading. An application that supports multithreading can

handle multiple tasks simultaneously, user can use multithreading to decrease the time taken by

an application to respond to user interaction. To decrease the time taken by an application to

respond to user interaction, 8ser must ensure that a separate thread in the application handles

user interaction.

A!OUT S50-SER?ER 883

The =A! $ervices feature available in $= $erver version H.2 is now called $=

$erver 220Analysis $ervices. The term =A! $ervices has been replaced with the term

Analysis $ervices. Analysis $ervices also includes a new data mining component. The

9epository component available in $= $erver version H.2 is now called (icrosoft $= $erver

222 (eta 4ata $ervices. 9eferences to the component now use the term (eta 4ata $ervices.

The term repository is used only in reference to the repository engine within (eta 4ata $ervices

$="$9V9 220 database consist of si# type of objects,

They are,

1. TA7=

. 89E


16/40

A database is a collection of data about a specific topic. In relational database data

are stored in the form of table. It can consist of rows and columns.

?IE6S O< TA!0E

The project work with a table consist of two types,

Design ?ie(

To build or modify the structure of a table user work in the table design. 8ser

can specify what kind of data will be hold. 8se 4esign view to arrange report items in the

report. 4esign view is sometimes called the design surface or layout view.

Datasheet ?ie(

4atasheet view shows the data in the database. It also allows us to enter and edit the

data. 4esign view allows us to create or change the table, form, or other database object,

and configure the fields.

. 5UER$

A %uery is a %uestion that has to be asked the data. Access gathers data that

assurers the %uestion from one or more table. The data that make up the answer is either

dynasts or a snapshot. .ach time user run %uery, and get latest information in the dynasts

.Access either displays the dynast or snapshot for us to view or perform an action on it

,such as deleting or updating.

.


17/40

To build or modify the structure of a form, user work in forms design view. 8ser

can add control to the form that are bound to fields in a table or %uery, includes te#tbo#es,

option buttons, graphs and pictures.


18/40

CHAPTER 3


19/40

The software used to develop this system is 6indows B!, visual studio. +et is done efficiently,

and the concept of $= helps to create the application backend. These components are also

helpful in providing interactivity to Dava applications.

3.1.. !eha,io'al


20/40

3.1.2. O+e'ational


21/40

'ontrolling the amount of input re%uired.

Avoiding delayed response

'ontrolling errors

?eeping process simple

Avoiding errors

The input design should contain the detailed information in which every user can

8nderstand the type of data they are going to enter or view .$o this is very important in design .If

this fails then the user enter the data incorrectly which leads to many errors. The user should not

be able to view or edit the codes that are created. $o that features should be disabling to users

while they are working on the package.

The project has been designed using visualstudio.net environment. The predefined

controls have used in the design environment. The forms include te#tbo#, and combo bo#

controls to get inputs.

0O#IN


22/40

In the project, the coding is being done such that proper validations are made to get the

perfect input. +o error inputs are accepted. In addition care is taken such that the data integrity

and referential integrity is not violated in the database.

In addition, coding is designed such that concurrency avoidance of accessing the

database, limited user access to the table is made perfect.

DATA!ASE DESI#N

The database design is a must for any application developed especially more for the data

store projects. $ince the chatting method involves storing the message in the table and produced

to the sender and receiver, proper handling of the table is a must.

Ta)les

3.3.1 Custome' ta)le

Column name Data T&+e Desc'i+tion

'ustomerJid +umeric)12,2* Id of the customer

'ustomerJname +varchar)2* +ame of the customer

(obileJnumber +umeric)12,2* 'ustomer (obile number

Age +umeric),2* Age of the customer

:ender +varchar)>* :ender of the customer

maild +varchar)(AB* mail id of the customer

3.3. Tic*et )loc*ing ta)le

22


23/40

Column name Data T&+e Desc'i+tion

TicketJid +varchar)2* ;light ticket Id

'ustomerJid +umeric )12,2* 'ustomer id

;lightJid +varchar )12* ;light id

7ookingJdate datetime 4ate of booking

$ource +varchar)


24/40

7ookingJid +varchar)2* Id of the customer

ticketJid +varchar)2* +ame of the customer

'ustomerJid +umeric)12,2* 'ustomer (obile number

;lightJid +varchar)2* Age of the customer

7ookingJdate datetime :ender of the customer

Amount +umeric )(AB* mail id of the customer

!aymentJdate datetime 4ate of payment done

Nume'ic ield ,alidation

The mobile number field can contain only numbers that should be 12 number.

The individual modules are checked for accuracy and what it has to perform

Te%t ield ,alidation

The te#t field can contain only the number of characters lesser than or e%ual to its si@e.

The te#t fields are alphanumeric in some tables and alphabetic in other tables. Incorrect

entry always flashes an error message.

24


25/40

APPENDICES

A. CONTE=T


26/40

!. Data


27/40

0e,el-1

;ig37. 4ata ;low 4iagram

27

(&en -ebsite

Stoe

/tacts c$stomedetails

nd check &ayment

%heck a!ailability

Stoe

+etie!e

+etie!e

S#S

Ticket

blocking

table

%$stome Send

S#S to

se!e

Ticket

blockin

g

&ocess

)ookin&ay

ment table

)ooks ticket

(nline&ayment


28/40

0e,el

28

i ticket booking &ocess

begins

Sends an inst$ction message to the

$ses

S$ch as the ode o message

content

"se %om&ose a message

-ith

ame &hone n$mbe

Send S#S to the

se!e n$mbe

S&lit and

Stoe $sedetails into

the

database

%$stome table

%om&ose a message

-ith

So$ce destination

n$mbe o &assenges

date ight no etc

Send S#S to the

se!e n$mbe

S#S Se!e

-ill ecei!e

and s&lit the

content

1

2

)ooking table

)ooking con*mationmessage

Pay online

3

Payment table


29/40

;ig37.


30/40

CHAPTER ?I

DE?E0OP/ENT O< S$STE/ TESTIN#

4.1 S&stem Testing

$ystem testing is a type of testing to confirm that all code modules work as specified, and

that the system as a whole performs ade%uately on the platform on which it will be deployed.

$ystem testing should be performed by testers who are trained to plan, e#ecute, and report on

application and system code. They should be aware of scenarios that might not occur to the end

user, like testing for null, negative, and format inconsistent values.

$ystem testing of software or hardware is testing conducted on a complete, integrated

system to evaluate the systemFs compliance with its specified re%uirements. A tester should be

able to repeat the steps that caused an error.Test techni%ues include, but are not limited to, the

process of e#ecuting a program or application with the intent of finding software bugs.

4. Testing and /ethodologies

This system begins the testing process by developing a comprehensive plan to test the

general functionality and special features on a variety of platform combinations. $trict %uality

control procedures are used. The process verifies that the application meets the re%uirements

specified in the system re%uirements document and is bug free.

At the end of each testing day, this system prepares a summary of completed and failed

test. And the application is redeveloped and retested until every item is resolved. All changes and

retesting are tracked through spreadsheets. Applications are not allowed to launch until all

identification problem are fi#ed. ;inally a report is prepared at the end of testing to show e#actly

what was tested and to list the final outcomes. This software testing methodology is applied in

four distinct phases3

8nit testing

Integration testing

30


31/40

4..1 Unit Testing

8nit testing is designed to test small pieces of functionality rather than the system

as a whole. This allows us to conduct the first round of testing to eliminate bugs before the other

major tests )i.e.* each module is tested individually. 8nit testing is testing changes made in a

e#isting or new program to find out each module is found to be working satisfactorily. &ere

every module will be tested.

9egistration and =ogin module test

'omponent test"whether the $($ device is working or not

4.. Integ'ation Testing

Integration testing is a type of testing in which software andKor hardwarecomponents are combined and tested to confirm that they interact according to their

re%uirements. Integration testing can continue progressively until the entire system has been

integrated.

It is also a software testing methodology used to test individual software

components or units of code to verify interaction between various software components and

detect interface defects. 'omponents are tested as a single group or organi@ed in an iterative

manner. After the integration testing has been performed on the components, they are readilyavailable for system testing. The following are the types of integration testing3

Top down Integration

7ottom"up Integration

4.. ?alidation Testing

Test to determine whether an implemented system fulfills its re%uirements such as

checking of data for correctness or for compliance with applicable standards, rules, andconventions. Validation testing is used to validate the fields in the form. It mainly focuses on te#t

field and numeric field.

31


32/40

4. 5UA0IT$ ASSURANCE

This system believed that testing should occur throughout the development process. This

system tested this software against the specifications in the system re%uirement document using

the scenarios developed earlier in the project.

Testing is applied in four distinct phasesLunit testing, integration testing, system testing,

acceptance testing. 4uring the system test this system designs and develops test cases to verify

that system re%uirements have been implemented and software works correctly. 7y this, This

system achieve better objectivity in the %uality of the product.

CHAPTER - B

S$STE/ I/P0E/ENTATION

B.1 Use' T'aining

This system was developed very user friendly. +o e#tra training was re%uiring using this

system. This system automatically guides )fully user guided* the user to give input and to

produce the output.

B. O+e'ational Documentation

An online help which gives the clear idea about This system was attached with This

system. 6henever the user needs guidance he can get help from the help manual.

nce the implementation plan is decided, it is essential that the user of the system is

made familiar and comfortable with the environment.

A documentation providing the whole operations of the system is being developed

The user can work with it in a well consistent way

The system is developed user friendly so that the user can work the system from the tips

given in the application itself.

CHAPTER -

32


33/40

CONC0USION

There are several reasons for transport authorities for introducing electronic ticketing

systems. &owever, they do not have the same priorities to all of them. &ereafter a list of

e#pectations compiled from the study3

M !revention of fraud

M ;are fle#ibility

M Improved multi"modal and multi"operator integration especially where method of operation

re%uires accurate allocation of fares to private operators.

M Improved passenger convenience and ease of use

M fficiency savings

"ticketing is an alternative to the conventional way of proving the availability and

validity of travel permission )e.g. paper tickets* through transferring the necessary information to

an electronic medium.

lectronic ticketing is a ticket sales information system, which are a tool and a basis for

improvement of ticket sales and payment. In addition with access control and ticket sales

management )reporting, accounting etc*, it helps institutions cultural, tourism, sport and all other

institutions to browse transactions, to get know their customers and to increase their revenues.

;light ticket portal has been developed by using Asp.net, because this will be the

advanced and easy to use the client K server technology so developed this project in .+et. 8sing

this project the user can book their tickets using $($.

verall the system is to be fairly usable. The conclusions that are derived from the

different usability areas are as follows3 the project provides a reliable and easy way to book

tickets using mobile phones using $($.

The system is found to be professional by the users because of the standardi@ed layout

and familiar navigation.

CHAPTER - 7


34/40

The project ;light ticket portal is fle#ible enough to meet the re%uirements of the 'ustomers.

This project also has the scope of enhancements like3

1" &ome delivery of tickets may be provided.

" nline 7ooking of !urchases of eatables )coldrinks, popcorn etc* can be provided.


35/40

CHAPTER 18

!I!0IO#RAPH$

!oo*s Ree''ed

N1O Introduction to !rogramming with Visual 7asic .+T

7y :ary D. 7ronson

NO Ale# &omer , Professional C#.NET 1.1, 22/ dition, 6ro# !ublications

N


36/40

SCREENS

Signu+ Page

36
http://www.amazon.com/exec/obidos/ASIN/0763724785/az395da1ee33o101a-20http://www.netjohn.com/http://www.dreamincode.net/http://www.a1vbcode.com/


37/40

0ogin +age

37


38/40

Admin login

38


39/40

S/S "it Connection Settings Sc'een

39


40/40

flight ticket portal project

Documents