1

ONLINE AIR TICKET BOOKING SYSTEM

Book Your Domestic Flight Tickets

www.make_my_tour.com

2

Prepared By, Abhinandan Shaw. Mintu Roy. Priyabrata Patra. Souvik Ballav.

This project is done under the guidance of

Anirban Chakraborty. Sukalyan Som.

3

INTRODUCTION

o It is an internet based application dedicated to provide flexibility to the user to book and/or cancel flight tickets through internet on 24x7 basis.

o This application also enables the organization a better reach to a wider range of customers.

4

GOAL OF THE PROJECT

o This site provides booking facility to the users by the click of a mouse from any place via internet.

o It will also give the company a better selling opportunity without a congestion at the booking counter or booking office.

o We would provide a very easy, attractive and user friendly interface so that users are motivated to use our website .

o It will also provide a quick service.

5

CHALLENGES1. Collecting the information of each and every requirement that are

supported by our website is a problematic task.

2. Designing the website according to our requirements is a challenge.

3. Database designing for such a huge collection of data is not so easy.

4. To provide a very easy, attractive and user friendly interface such that the users can easily understand and use the site is a challenge.

6

OVERVIEW OF THE PROJECTThis website has two sections:

1. Administrative panel: - Administrative panel is totally reserved for owners and administrators and protected by authentic username and password mechanism. Administrator can moderate flight details.

2. Client panel: - Client panel is accessible to the general users. The client section of this website provides several services to the users . These are –

User can get information about the flight companies. The user can book domestic flight tickets. The whole task is

performed step by step.

7

OVERVIEW OF THE PROJECT(CONTD.) Step 1: In the 1st step the user have to provide some information

which are used to find the flights from the database. On basis of this he/she would get the details of the available flights.

Step 2: In the 2nd step the user can select a flight from the available flight/flights that are retrieved from the database.

Step 3: In the 3rd step the user have to provide the details of the passenger/passengers like name, address, contact details etc.

Step 4: Finally the user have to select the payment method. Then the user is redirected to a online transaction website. When the transaction is complete the user get the flight tickets.

Thus the whole process of booking flight tickets is accomplished. User can cancel flight tickets.

8

MODEL USED1. To develop our project we use an

“Evolutionary Model”. 2. In the Evolutionary Model, development

engineering effort is made first to establish correct, precise requirement definitions and system scope, as agreed by all the users across the organization.

3. This is achieved through application of iterative processes to evolve a system most suited to the given circumstances.

4. The process is iterative as the software engineer goes through a repetitive process of requirement Analysis-Design-Testing through prototype-Implementation-Assessment-Evaluation, till all users and stakeholders are satisfied.

9

SOFTWARE REQUIREMENT SPECIFICATION

10

An SRS is the output of requirement analysis. Which defines, Functional requirements. Non-functional requirements.

Following are the important properties of the SRS document.

Consistent- there does not arise any redundancy.

Correct –should contain every requirement specified by the customer.

Unambiguous-every requirement specified in it has one and only one interpretation.

• Complete-it will focus on all the problem goals and objectives not only the functions and features and also structured, concise, having a black box view, traceable, verifiable etc.

11

BENEFITS OF SRS DOCUMENT

A well-designed, well-written SRS accomplishes four majorgoals:

It provides feedback to the customer.

It decomposes the problem into component parts.

It serves as an input to the design specification.

It serves as a product validation check.

12

INTRODUCTION The system that we have developed is an“online air ticket booking system” for domestic flights. This is an

website. A passenger can book flight ticket by using this site.

A passenger can also cancel his booked ticket. Also there is an administrator who can insert, update or delete

flight records in the database. And can create a new administrator.

13

FUNCTIONAL REQUIREMENTS-WHAT IS IT ?

These requirements should specify which output should be produced from the given input

For each of the functional requirement a detailed description of all the inputs, their sources, units of measurement and their domain should be specified.

This include specifying the validity of the input and the required validity over the output.

Logical operations required to convert the input to the output.

14

DETAIL FUNCTIONAL REQUIREMENTS

M 1- Passenger module This module is accessed by a general passenger. In this module there

are 4 sub module's. These are as follows, M1.1- Journey module :- This module is used to take the details of journey from a passenger, and

depending upon these information’s a list of available flight will be displayed.

Input Constraint

1.Source city name. 2. Destination city name. both will be from our country.

3. Departure date.

must be a maximum of 15 days later from the booking date and at least 4 hrs ago from the takeoff.

4. Class. either “Economy” or “Business”

15

CONTINUED JOURNEY MODULE:- Input Constraint

5. No of adults must be from 1 to 6. Age must be greater than or equal to 12.

6. No of childrenmust from 0 to 4. Age must be from 2 to 11 years.

7. No of infants. must a maximum of 2. Age must be less than 2.

Output: Depending upon these information a list of available flight corresponding With

their fair type, departure date and time, departure and arrival city and duration of the journey will be displayed.

16

Cont’d M1.2- Passenger detail module.

This module is used to take the passenger details including primary contact person. For more about this module follow the link.

Passenger Details Module M1.3 -payment module.

This module used to take the payment mode as input , and the subsequent process

Of payment.

Payment Module M1.4 -ticket cancellation module.

This module is used to cancel an already booked ticket.

Ticket cancellation M2-Administrator module. This module is used perform some administrative task, that can’t be accessed by a general

passenger. To login into this module an administrator will supply a unique username and a pass word.

M2.1- entering detail flight schedule.

using this module an administrator can enter detail flight schedule.

detail Flight Schedule M2.2- Updation and deletion of flight.

Using this module an administrator can or can delete flight routine.

Updation and Deletion Of Flight

17

NONFUNCTIONAL REQUIREMENTSThese requirements deals with the following characteristics of a system that can’t be expressed as function. Nonfunctional requirement is concerned with the following: Usability- means, how much easy to use the system is.

Portability- means, how much portable the system is so that it can run on various types of platform.

Reliability- It is defined as "the probability of failure-free operation of a system in a specified environment for a specified time".

Security-means, how the system is secure from malicious input, and also from illegal access.

18

COST ESTIMATION USING COCOMO

The basic COCOMO model gives an approximate estimate of the project parameters. This estimation model is given by the following expressions:

Effort= a1 * (KLOC)a2 PM Tdev=b1 * (Effort)b2 Months

Our software is an organic type.

Estimation of development effort: Organic: Effort =2.4 x (2)1.05 PM =4.97 PM

Estimation of development time: Organic: Tdev =2.5 x (Effort)0.38 months =4.6 Months

19

Software Used: MICROSOFT VISUAL STUDIO 2008

SQL SERVER 2005

HARDWARE Used: Pentium 4 processor.

Disk space of 40 GB.

256 MB RAM.

Windows XP SP2

20

Data Flow Diagram(DFD)

21

DATA FLOW DIAGRAM(DFD) The DFD is a graphical model of a system that shows the different

processing activities or functions that the system performs and the data interchange among these functions.

Each function is considered as a process that consumes some input data and produces some output data.

DFD is also known as Data Flow Graph or Bubble Chart.

22

EXAMPLE

process

data store

data flow

data flow

External Entity

23

This modeling technique uses five kinds of system components – 1. Process:- Performs processing on incoming data. Represented with a circle.

2. Data Stores:- Holding areas for collection of data, processes add or retrieve data

from these stores. Reperesnted using two parallel lines.

3. External Entity:- The system and external entities exchange data in the form of data flows. Represented using a rectangle.

Process

data flow

Components

External Entity

24

4. Data Flow:- Connects the processes, external entities and data stores. Represented using a directed arc or an arrow.

5. Output:- Produces the output of the system. Represented as-

Cont’d

data flow

Output

25

LEVEL 0 DFD:

User Administrator

Online Air Ticket

Booking System

0

Book Ticket

Get Detailed Information

Perform Administrative Task

Retrieve Information

27

LEVEL 2 DFD:

UserFlight Select0.1.2

Passenger

Details0.2.1

Cancel

Ticket0.4

Waiting List

Facility0.3

Provide JourneyDetails

Confirm Ticket

Get Ticket

Ticket

Prov

ide

Pass

enge

r

Detai

ls

Provide PassengerDetails

Flight Details

Cancellation Request

User Details

AdministratorLogs

In0.5.1

Update

Deletion of Corresponding Record

Corresponding Flig

ht

Provides Data

Administrative Details Provide Update Information

FlightSearch0.1.1

ChooseFlight

Payment

Details0.2.2

Provide PaymentDetails

Transaction0.2.3

Pay HereStorePassenegerDetails

Store

Paym

ent

Detai

ls

Update

FlightInformation0.5.2

Update Info

Retrieve Info

Retrieve Info

28

ENTITY RELATIONSHIP

DIAGRAM

An Entity-relationship model is an abstract conceptual representation of structured data. Entity relationship modeling is a relational schema database modeling method, used in Software Project Management to produce a type of conceptual data model of a system, often a relational database, and its requirements in top-down fashion.

Diamonds represents relationship sets

Ellipses represents attributes

Rectangles represents entity sets

Notations used:

30

journey

passenger_id

cabinflight_no num_of_person

s

d_date

flight

flight_no

flight_com_name

src

dest

d_date

a_date

num_of_persons

fare

type

travel throug

h

manages

administrator

a_id

a_namepwd

comprises of

passenger

needs

payment

pay_mode

ticket_no

amount

is

pri_con_person

passenger_id

e_addr contact_no

addr

ticket_no

seat_no

p_type

sex

type

age

name

f_name

m_name

l_name

1

1

1

1

n

n

1..n1

1..n0..1

31

NORMALISATION

32

Passenger(ticket_no, seat_no,f_name,m_name,l_name,p_type,sex,age,type).

Functional dependencies:

ticket_no,seat_no f_name,m_name,l_name.

ticket_no,seat_no p_type,sex,age,type.

Therefore we have,

passenger (ticket_no,seat_no,f_name,m_name,l_name,p_type,sex,age,type)

The normalised 3NF passenger relation is:

passenger(ticket_no, seat_no,f_name,m_name,l_name,p_type,sex,age,type).

33

DATA DICTIONARY

34

DATA DICTIONARY

The data dictionary is an important part of the DBMS. It contains data about data (or metadata). It means that it contains the actual databasedescriptions used by the DBMS.

Data dictionary is described in terms of- Process. Data Store. Explanation of Table Attributes.

35

PROCESSName: Flight SearchDescription: This process is used to find

availableflights from the database on basis of the givenJourney details.Input Logic Summary Output

Journey details. Journey details are provided by the passengers and available flight details is retrieved from the database.

Available flights.

36

DATA STOREName: Flight details.

Description: This data store is used for storing the flight details.

Data Flow In Data Flow Out

Update flight record from the process Cancel Ticket.

Flight information to the process Flight Search.

37

TABLE 1:JOURNEYDescription:- The journey table contains the details

about the journey of passengers. Here “details about the journey” means, name of the Source and destination ctites, departure date,number of passengers and class.

The attributes of the journey table are: passenger_id. flight_no. cabin. no_of_persons. d_date.

38

EXPLANATION OF ATTRIBUTE PASSENGER_IDData Name: Passenger Identification

number

Data Description: A unique identifier will be assigned to each primary contact person by the database system. Using this identifier a primary contact person will be uniquely identified by the database system.

Data type: varchar2

Data Alias: passenger_id.

Data Length: Fixed 12 characters.

Domain of Data: {first 4 character of flightno}X{1,…… ,31}X{1, …. ,12} X{0001, ….. ,9999}X{01,……….,99}.

Constraint This attribute will serve as the primary key of the journey table.

Physical Location of Data: journey table

39

Client PanelDesign

40

41

Administrative Paneldesign

42

43

44

45

46

47

TESTING AND SNAPSHOT

There are three types of testing - those are in follows, Unit Testing. Alpha Testing. Beta Testing. Integration Testing. System Testing.

48

Client Panel Validation

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

THANK YOU