Airline Ticket Booking and Flight

Management System

A project report submitted in partial fulfillment of

The requirements of Business Process Management Course (IMMG-4108).

IPG-MBA

by

Anirudh Gautum (2019-IMG-006)

and
Kawaljeet Singh Batra (2019-IMG-027)

submitted to

Dr. Gyan Prakash

ABV-INDIAN INSTITUTE OF INFORMATION

TECHNOLOGY AND MANAGEMENT
GWALIOR-474015
2022
Table of Contents

1 INTRODUCTION 1

1.1 Technologies Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2 DATABASE DESIGN 2

2.1 PostgreSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.1.1 Comparision with MySQL . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.2 Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2.2.1 User Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.2.2 Flight Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.2.3 FlightSchedule Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.2.4 Journey Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 SYSTEM PROCESSES 7

3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 LOGICAL FLOW OF THE SYSTEM 8

4.1 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.2 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.3 Future Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

ii
5 CONCLUSION AND FUTURE SCOPE 10

5.1 Future Innovations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

REFERENCES 11

iii
Chapter 1

INTRODUCTION

Online airline ticket booking system is one of the essential applications of E-commerce. With
the development of Internet and security technology, more and more people begin to consume
online, which is more convenient and personal than traditional way. The goal of this system is to
make people purchase airline tickets easily. The system is written in Javascript and Python.

The Web-based airline ticket booking system uses client/server frame. The customers can use
Web browser to access the system and book airline tickets. Because Internet and web browsers
are widely used all over the world, there is no need to train customers how to use them. The
second advantage is that there is no limit on customers’ operating systems, for example, they can
use almost all kinds of popular operating systems such as MacOS, Linux and Window.

1.1 Technologies Used

1
Chapter 2

DATABASE DESIGN

In this section, we discuss about the database and its design for the airline ticket booking system.
PostgreSQL, a Relation Database Management System has been used for this system. The benefit
of using a relational database is the ability to interlink communication entities together through
the means of joins and then being able to store and retrieve transactions in a fast and efficient
manner.

2.1 PostgreSQL

PostgreSQL is a powerful, open source object-relational database system with over 35 years
of active development that has earned it a strong reputation for reliability, feature robustness,
and performance. There are several benefits for choosing Postgres over traditional MySQL.
PostgreSQL is an object-relational database, while MySQL is purely relational. This means
PostgreSQL offers more complex data types and allows objects to inherit properties, but it also
makes working with PostgreSQL more complex.

2.1.1 Comparision with MySQL

There are several benefits for choosing Postgres over traditional MySQL. PostgreSQL has a
single, ACID-compliant storage engine. MySQL has support for 16 different storage engines
suitable for different use cases. The default storage engine, InnoDB, provides index-organized

2
tables. PostgreSQL spawns a new system process with its own memory allocation for each client
connection it establishes, so it requires a lot of memory on systems with a high number of client
connections. MySQL uses a single process and maintains one thread (or path of execution) per
connection, which works well for most applications of less than enterprise scope.

Three common database features are views, triggers, and stored procedures. PostgreSQL has
more robust views, and supports materialized views, which can improve performance for com-
plex queries. Both databases support AFTER and BEFORE triggers for SQL INSERT, UPDATE,
and DELETE statements; PostgreSQL also offers an INSTEAD OF trigger, and can execute com-
plex SQL statements in a trigger using functions. Both databases support standard SQL stored
procedures, but PostgreSQL offers in addition the ability to call procedures written in languages
other than SQL.

2.2 Schemas

There are three 4 major relations in the database, they are:

• User

• Flight

• FlightSchedule

• Journey

3
2.2.1 User Schema

The User relation, depicts the attributes that are related to the user, accessing the system through
web. The schema of the User table includes the attributes like username: for storing the name
of the user, password : for storing the account password for authentication, and profilePhoto : a
link for the user’s profile photo.

• id : UUID PRIMARY KEY, NOT NULL

• username : STRING

• password : STRING

2.2.2 Flight Schema

The Flight relation, depicts the attributes that are related to the aircraft, that is being drafted for
use by the company. The table includes the following attributes:

• id : UUID PRIMARY KEY, NOT NULL

• flightCode : UUID

• company : STRING

• source : STRING

• destination : STRING

• ecoCapacity : INTEGER

• busCapacity : INTEGER

• execCapacity : INTEGER

• ecoPrice : FLOAT

• busPrice : FLOAT

• execPrice : FLOAT

4
2.2.3 FlightSchedule Schema

The Flight relation, depicts the attributes that are related to the flight schedule. Once an aircraft
has been drafted, it can be scheduled for a particular date of flight. the attributes of this relation
includes:

• id : UUID PRIMARY KEY, NOT NULL

• flightID : FOREIGN KEY NOT NULL

• source : STRING

• destination : STRING

• date : DATETIME

• ecoRem : INTEGER

• busRem : INTEGER

• execRem : INTEGER

2.2.4 Journey Schema

The Journey relation, depicts the attributes that are related to the journey, that a user prepares for
a particular flight, on a particular date. the journey schema, is a ternary relationship, between
the User schema, Flight schema and the FlightSchedule schema. The attributes of the journey
relation are as follows:

• id : UUID PRIMARY KEY, NOT NULL

• flightID : FOREIGN KEY NOT NULL

• userID : FOREIGN KEY NOT NULL

• scheduleID : FOREIGN KEY NOT NULL

• metaData : JSON

• amountPayed : FLOAT

5
Figure 2.1: Entities and their relationships in the Database.

6
Chapter 3

SYSTEM PROCESSES

After studying the existing research in the field of smart farming, it is important to have a con-
crete understanding of the objectives we want to achieve through the means of this research.
This Chapter 3 discusses in depth all the related phenomena, mechanisms, technologies, and
mathematical understanding of preparing solutions to achieve our objective.

3.1 Overview

This research has been divided into 7 modules. The first step involves the collection of relevant
information related to research and keywords, to create information crawlers to collect useful
information regarding plants/crops. The second part focuses on determining whether the plants
are healthy and not suffering from any diseases. So, a plant-leas disease detection module has
been proposed to identify healthy vs diseased plants. The third module discusses the presence
of pests in crops, so a plant-based pest detection module has been proposed as the next step
in the pipeline. The fourth module proposes a 1-3 way water routing method for seamless and
automated signal-based irrigation water routing to crops, based on the water requirements in
particular sections of the farming region. The sixth module discusses tracking and displaying
weather information of the farming area, so as to infer crop requirements, henceforth an open-
source API is used to determine weather data like humidity, precipitation probability, etc. based
on the location of the region. The seventh module deals with creating a web crawler to collect
relevant information regarding common plant pests, their identification signs, and how to get rid
of them, in order to make sure that plants remain in a healthy condition.

7
Chapter 4

LOGICAL FLOW OF THE SYSTEM

In this Chapter, we are going to talk about what it is exactly we have managed to create by
following the workflow and using different tools. We will also talk about are limitations of the
project and future works.

4.1 Conclusion

In this research, our aim was to develop a robust set of tools that can be used in coordination with
each other and implore the use of deep learning, IoT, and other digital technologies in agriculture
automation and smart farming domains. Our observations clearly indicate that deep learning and
its related methods produce a better outcome in almost all categories of its application. Moreover,
it also offers a higher level of accuracy as compared to existing conventional techniques. In
addition, we also proposed web-crawling bots for the collection of useful information related to
crops/plants, for better planning and crop management.

4.2 Limitations

One of the limitations of this research is the size of the datasets used. The different datasets used
for training the deep learning architectures are not exhaustive. Meaning, that they only contain
a set number of images for classes of flowers, plants, diseases, pests, and fruits. In a real-world
application, where there are thousands of plant species, types of pests/insects, different categories

8
and scales of flowers, and related entities are existent. Hence, the models will be insufficient to
call a general purpose system.

At the same time, the training accuracy of the model can be increased further by different tech-
niques. Due to the limited hardware capabilities and time constraints, there were a set number
of epochs that could have been possible for each of the use cases. Increasing the number of
epochs, thus the training time can also have a significant impact on the efficiency of the model.
Hyperparameter tuning also needed to be done in almost all the architectures to determine the
best combination of values of the optimizers, the loss functions, and the number of epochs to be
selected to get the most efficient model.

Additionally, a generically intelligent bot, that not only is capable of extracting data from a lim-
ited set of webpages, but at the same time, ingeniously crawls the internet to determine related
information endpoints, and collectively stores and operates the data extracted has to be devel-
oped. This will ensure diversity in the collection of data, and the inclusion of data points at
random reducing user bias, thus further automating the process.

4.3 Future Scope

This work is helpful for engineers and budding researchers who are looking to experiment in the
field of smart agriculture and can study and apply the discussed deep learning techniques to their
own classification or identification problems. Furthermore, as proposed in the sections above,
this research can also act as an initial point for researchers, trying to build scalable systems, that
can perform multi-species recognition and classification, based on the required input parameters,
and be easily accessible to general users, to aid in their daily lives in the field. In the future, we
are planning to further work on the proposed set of techniques, determine the most efficient ways
to combine these different tools under a single unified system, and to also evaluate its robustness
and working accuracy.

9
Chapter 5

CONCLUSION AND FUTURE SCOPE

In this Chapter, we are going to talk about what it is exactly we have managed to create by
following the workflow and using different tools. We will also talk about are limitations of the
project and future works.

5.1 Future Innovations

Certiain innovations and improvements that can be made are:

• Improvements can be made in the seat allocation algorithm of the system. Currently, the
system uses a naive allocation algorithm, by linearly allocating seats to the passengers.
A custom interface, where passengers are able to select from the available seats can be
designed for better user experience.

• A feature for providing user discounts while booking the tickets through discount coupons
can be implemented to retain and attract more number of users to the platform.

• Implementation of JWT (Javascript Web Token) authentication can be done, over the exist-
ing session based user authentication for enhanced user security and authentication control.

10
REFERENCES

11