Airline Reservation System
Airline Reservation System
BELAGAVI
Guide: HOD:
Prof. Vani S Dr. Priti Mishra
Assistant professor Head,
Dept. of CSE Dept. of CSE
Inspiration and guidance are valuable in all aspects of life, especially what is
academic. “Experience is the best teacher”, is an old saying. The satisfaction and pleasure that
accompany the gain of experience would be incomplete without mentioning the people who
made it possible.
We are extremely thankful and grateful to our guide VANI S, Assistant Professor, and
Department of Computer Science and Engineering. They being our guide has taken keen
interest in the progress of the Project work by providing facilities and guidance. We are indebted
to our guide for her inspiration, support and kindness showered throughout the course.
We express our special gratitude to our Principal Dr. Santhosh Kumar G and
Management for providing the resources and support for making our Project work.
Nevertheless, we express heartfelt thanks towards our parents, friends and teaching and
non-teaching staff of our college for their kind co-operation and encouragement which helped
us in the completion of our Project work.
CERTIFICATE
This is to certify that ALFIYA FARHAT(1EE20CS002) &
CHARU VAISHNAVI M(1EE20CSOO9) of 5th semester B.E (Computer Science
& Engineering) has completed the Mini Project report on “AIRLINE
RESERVATION SYSTEM” in the partial fulfillment of MINI PROJECT prescribed
by Visvesvaraya Technological University during the academic year 2022-23.
Signature of HOD
Signature of Guide
Dr. Priti Mishra
Prof. Vani S
Head,
Assistant professor Dept. of CS&E,
Dept. of CS&E, EWCE, Bangalore
EWCE, Bangalore
Signature of External
1.
2.
ABSTRACT
The main purpose of this software is to reduce the manual error involved in the airline
reservation system and make it convenient for customers to book the flights as when they
require such that such that they can utilize this software to make reservations, modify
reservations or cancel a particular reservation.
I
TABLE OF CONTENTS
II
LIST OF FIGURES
III
LIST OF TABLES
IV
DBMS Mini Project Airline Reservation System
CHAPTER 1
INTRODUCTION
The “Airline Reservation System” (ARS) was one of the earliest changes
to improve efficiency. ARS eventually involved into the Computer Reservation System
(CRS), and then into Global Distribution System (GDS). The airline Industry created the
first GDS in the 1960s as a way to keep track flight schedules, availability, and prices.
An airline’s inventory contains all flights with their availability seats. The inventory of an
airline generally divided into services classes (Business or Economy class) for which
different prices and booking conditions apply.
ARS software is developed by many custom software development companies and
integrated into the website. It also helps in maximizing the revenue generation of the
airline companies in various ways. This system is also used by companies to keep track of
user preferences of regular travelers so that they can provide better service and give offers
to customer.
As the modern organizations are automated and computers are working as per the
instructions, It becomes essential for coordination of human beings, commodity and
computers in a modern organization. Airline reservation system makes the process of
reserving flights as simple and fast. This project keeps the record of flight tickets which is
issued by the administrative. Airline reservation system has two modules i.e., user and
admin. The “Airline Reservation System” has been developed to override the problems
prevailing in the practical manual system. This software is supported to eliminate and in
some case reduce the hardships faced by the existing system. Moreover the system is
designed for particular need for the airline to carry out operations in a smooth and
effective manner.
CHAPTER 2
ANALYSIS
2.1 SYSTEM ANALYSIS
2.1.1 Existing system
Existing system is manual one in which we have developed with different protocol to
store the information like user details, route details, schedule details and class details who
are willing to book the seat for a flight. It is very difficult to maintain historical data.
DISADVANTAGES:
➢ Manually goes to the Airport and book his ticket.
➢ Downloading the ticket form as paper document, filling it manually and
submitting it at Airport.
➢ It is time consuming.
➢ It consumes lot of man power.
➢ It lacks data security.
ADVANTAGES:
➢ User friendliness provided in the application with various controls.
➢ It provides high level of security with different level of authentication.
➢ The system should provide help in managing different category.
➢ It will ensure data accuracy.
➢ Security to the confidential information.
➢ All the records will be efficiently maintained by SQL Database.
➢ Reduce the redundancy of making the entries of the activities which are done
manually.
CHAPTER 3
DESIGN
3.1 INTRODUCTION TO DESIGN
Design is the first step in the development phase for any techniques and principles for the
purpose of defining a device, a process or system in sufficient detail to permit its physical
realization. Once the software requirements have been analyzed and specified the
software design involves three technical activities-design, coding, implementation and
testing that are required to build and verify the software.
Design is a place where quality is fostered in development. Software design is a process
through which requirements is translated.
A context-level DFD for the system the primary external entities produce information for
use by the system and consume information generated by the system. The labelled arrow
represents data objects or object hierarchy. The DFD enables the software engineer to
develop models of the information domain and functional domain at the same time. As
the DFD is refined into grater levels of details, the analyst performs an implicit functional
decomposition of the system. At the same time, DFD refinement results in a
corresponding refinement of the data as it moves through the process that embody the
applications.
RULES OF DFD:
✓ Fix the scope of the system by means of context diagrams.
✓ Organize the DFD so that the main sequence of the actions.
✓ Reads left to right and top to bottom.
✓ Identify all inputs and outputs.
✓ Identify and label each process internal to the system with rounded circles.
✓ A process is required for all the data transformation and Transfers. Therefore
never connect a data store to a data Source or the destinations or another data
source with just a data flow arrow.
✓ Do not indicate hardware and ignore control information.
COMPONENTS OF ER MODEL:
This model is based on 3 concepts:
• Attributes are the properties of the entities and relationship, descriptor of the
entity. Attributes are elementary pieces of information attached to an entity. The
attribute is used to describe the property of an entity. Eclipse is used to represent
an attribute.
ER DIAGRAM:
Figure.3.3.1: ER Diagram
SCHEMA DIAGRAM:
DESCRIPTION:
• The design of the database is called a schema. This tells us about the structural
view of the database. It gives us an overall description of the database. A
database schema defines how the data is organised using the schema diagram.
• A schema diagram is a diagram which contains entities and the attributes that
will define that schema. A schema diagram only shows us the database design. It
does not show the actual data of the database. Schema can be a single table or it
can have more than one table which is related. The schema represents the
relationship between these tables.
CHAPTER 4
PROJECT MODULES
• Admin Panel
• User Panel
Admin Panel:
i. Dashboard
ii. List of booked tickets
iii. Add flight schedules
iv. Delete flight schedules
v. Add aircrafts
Dashboard
▪ In this section, admin can briefly view total number of tickets booked
Activate aircrafts
▪ In this section, admin can activate aircrafts.
Deactivate aircrafts
▪ In this section, admin can deactivate aircrafts.
User panel:
i. Home page
ii. Book tickets
iii. About us
iv. Contact us
Home page
You can visit login page.
Book tickets
User can book their flight tickets.
About us
User views the details of website administrator.
Contact us
User can contact the website administrator.
DATABASE TABLE
1. Admin Table
# Name Type
1 admin_id varchar(20)
2 Pwd varchar(30)
3 staff_id varchar(20)
4 Name varchar(20)
5 Email varchar(35)
2. Customer Table
# Name Type
1 customer_id varchar(20)
2 Pwd varchar(20)
3 Name varchar(20)
4 Email varchar(35)
5 phone_no varchar(15)
6 Address varchar(35)
# Name Type
1 flight_no varchar(10)
2 from_city varchar(20)
3 to_city varchar(20)
4 departure_date Date
5 arrival_date Date
6 departure_time Time
7 arrival_time Time
8 seats_economy int(5)
9 seats_business int(5)
10 price_economy int(10)
11 price_business int(10)
12 jet_id varchar(10)
4. Frequent_flier_Details Table
# Name Type
1 frequent_flier_no varchar(20)
2 customer_id varchar(20)
3 Mileage int(10)
5. Jet_Details Table
# Name Type
1 jet_id varchar(10)
2 jet_type varchar(20)
3 total_capacity int(5)
4 Active varchar(5)
6. Payment_Details Table
# Name Type
1 payment_id varchar(20)
2 Pnr varchar(15)
3 payment_date Date
4 payment_amount int(6)
5 payment_mode varchar(15)
7. Passengers Table
# Name Type
1 passenger_id int(10)
2 Pnr varchar(15)
3 Name varchar(20)
4 Age int(3)
5 Gender varchar(8)
6 meal_choice varchar(5)
7 frequent_flier_no varchar(20)
8. Ticket_details Table
# Name Type
1 Pnr varchar(15)
2 date_of_reservation Date
3 flight_no varchar(10)
4 journey_date Date
5 Class varchar(10)
6 booking_status varchar(20)
7 no_of_passengers int(5)
8 lounge_access varchar(5)
9 priority_checkin varchar(5)
10 Insurance varchar(5)
11 payment_id varchar(20)
12 customer_id varchar(20)
CHAPTER 5
IMPLEMENTATION
Implementation is the stage where the theoretical design is turned into a working system.
The most crucial stage in achieving a new successful system and in giving confidence on
the new system for the users that it will work efficiently and effectively. The system can
be implemented only after thorough testing is done and if is found to work according to
the specification.
It involves careful planning, investigation of the current system and its constraints on
implementation, design of methods to achieve the changeover and an evaluation of
change over methods a part from planning. Two major tasks of preparing the
implementation are education and training of the users and testing of the system.
The more complex the system being implemented, the more involved will be the system
analysis and design effort required just for implementation.
The implementation phase comprises of several activities. The required hardware and
software acquisition is carried out.
TABLE CREATION:
ALTERATION OF TABLE:
Database Connection:
<?php
DEFINE('DB_USER','root');
DEFINE('DB_PASSWORD','');
DEFINE('DB_HOST','localhost');
DEFINE('DB_NAME','airline_reservation');
$dbc=mysqli_connect(DB_HOST,DB_USER,DB_PASSWORD,DB_NAME)
OR dies('Could not connect to MySQL:' .
mysqli_connect_error());
?>
Admin login page:
<?php
session_start();
?>
<html>
<head>
<title>
Welcome Administrator
</title>
<link rel="stylesheet"type="text/css"href="css/style.css"/>
<link rel="stylesheet"href="font-awesome-4.7.0\css\font-
awesome.min.css">
</head>
<body>
<imgclass="logo"src="images/shutterstock_22.jpg"/>
<h1 id="title">
GO BY AIR AIRLINES
</h1>
<div>
<ul>
<li><a href="admin_homepage.php"><iclass="fa fa-
home"aria-hidden="true"></i> Home</a></li>
<li><a href="admin_homepage.php"><iclass="fa fa-
desktop"aria-hidden="true"></i> Dashboard</a></li>
<li><a href="logout_handler.php"><iclass="fa fa-sign-
out"aria-hidden="true"></i> Logout</a></li>
</ul>
</div>
<h2>Welcome Administrator!</h2>
<table cellpadding="5">
<tr>
<td class="admin_func"><a
href="deactivate_jet_details.php"><iclass="fa fa-plane"aria-hidden="true"></i>
Deactivate Aircraft</a>
</td>
</tr>
</table>
</body>
</html>
QUERIES USED:
For Update:
For Insertion:
For Selection:
For Deletion:
CHAPTER 6
TESTING
Testing is a process of executing a program with the intent of finding an error. Testing is
a crucial element of software quality assurance and presents ultimate review of
specification, design and coding. System testing is an important phase. Testing represents
an interesting anomaly for software. Thus a series of testing are performed for the
proposed system before the system is ready for user acceptance testing.
A good test case is one that has a high probability of finding an as undiscovered error.
A successful test is one that uncovers an as undiscovered error.
Testing objectives:
➢ Testing is a process of executing a program with the intent of finding an error.
➢ A good test case is one that that has a high probability of finding an as yet
undiscovered error.
➢ A successful test is one that uncovers an as undiscovered error.
Testing Principles:
➢ All test should be traceable to end user requirements.
➢ Test should be planned long before testing begins.
➢ Testing should begin on a small scale and progress towards testing is large.
➢ Exhaustive testing is not possible.
➢ To be most effective testing should be conducted by a independent third party.
b) Black-box testing
Designed to validate functional requirements without regard to the internal workings of a
program. Mainly focuses on the information domain of the software, deriving test cases
by partitioning input and output in a manner that provides through test coverage.
Testing strategies:
A strategy for software testing must accommodate low-level tests that are necessary to
verify that all small source code segment has been correctly implemented as well as high-
level tests that validate major system functions against customer requirements.
Testing fundamentals:
Testing is a process of executing program with the intent of finding error. A good test
case is one that has a high probability of finding an as undiscovered error
Unit testing:
Unit testing is essential for the verification of the code produced during the coding phase
and hence the goal is to test the internal logic of the modules. Using the detailed design
description as a guide, important paths are tested to uncover errors with in the boundary
of the modules.
All units of Vienna SQL were successfully tested.
Integration testing:
Integration testing focuses on unit tested modules and build the program structure that is
dictated by the design phase.
System testing:
System testing tests the integration of each module in the system. It also tests to find
discrepancies between the system and its original objective, current specification and
system documentation. The primary concern is the compatibility of individual modules.
Acceptance testing:
This testing is done to verify the readiness of the system for the implementation.
Acceptance testing begins when the system is complete. Its purpose is to provide the end
user with the confidence that the system is ready for use. It involves planning and
execution of functional tests, performance tests and stress tests in order to demonstrate
that the implemented system satisfies its requirements .
Uses of testing:
2. Verify that on filling flight details like flight name, code, from and to destinations,
capacity, timings, and frequency etc, new flights get successfully added in the
system.
3. Verify that users can search for flights by name, from-to airports or flight code for
checking their status and timings.
4. Verify that search results have flight details, timings and availability.
5. Verify that clicking the search results open complete details for flight.
Test cases are derived to ensure that all statements in the program have been executed at
least once during testing and that all logical conditions have been execute. Using white-
box testing methods, the software engineer can drive test
Cases that.
1. Guarantee that logical decisions on their true and false sides.
2. Exercise all logical decisions on their true and false sides.
3. Execute all loops at their boundaries and within their operational bounds.
4. Exercise internal data structure to assure their validity.
The test case specification for system testing has to be submitted for review before system
testing commences.
CHAPTER 7
RESULT ANALYSIS
Conclusion
➢ To conclude the description about this project, the project is developed using PHP
and MYSQL and is based on the requirement specification of the analysis of the
existing system, with flexibility for future enhancement.
➢ The number of tickets are increasing which increases the paper work and manual
work. Hence there is a lot of strain on the people who are working to book the
tickets and software’s are not usually used in this context. This particular project
deals with the problems on booking the flight tickets and avoids the problems
which occur when carried manually.
FUTURE ENHANCEMENT
In future, the Airline reservation system can extend its features by:
BIBLIOGRAPHY
WEBSITE:
https://www.w3schools.com
https://www.youtube.com
https://stackoverflow.com
https://www.tutorialspoint.com
https://www.phptpoint.com
https://www.google.co.in/
https://www.gist.github.com
https://www.datainflow.com
https://www.codeproject.co
https://en.wikipedia.org
BOOKS:
By Jon Duckett “java Script and jQuery: Interactive Front-End Web Development”.