Tribhuvan University

Faculty of Humanities and Social Sciences

A Project Report On
AIRLINE TICKET RESERVATION SYSTEM

Submitted to
Department of Computer Application
Thames International College

In partial fulfilment of the requirements for the Bachelors in Computer Application

Submitted by

Himani Waiba Lhakpa Chhiring Sherpa

[Link]: 6-2-450-154-2021 [Link]: 6-2-450-154-2021

Exam Roll Number: 45002069 Exam Roll Number: 45002071

Under the Supervision of

Avinash Maskey

August, 2025
 -

Tribhuvan University

Faculty of Humanities and Social Sciences

Thames International College

SUPERVISOR'S RECOMMENDATION

We hereby recommend that this project prepared under my supervision by Himani

Waiba and Lhakpa Chhiring Sherpa entitled "Airline Ticket Reservation System" in
partial fulfillment of the requirements for the degree of Bachelor of Computer Application
is recommended for the final evaluation.

Avinash Maskey
SUPERVISOR
School of IT
Thames International College
 Tribhuvan University

Faculty of Humanities and Social Sciences

Thames International College

LETTER OF APPROVAL

This is to certify that this project prepared by Himani Waiba and Lhakpa Chhiring
Sherpa entitled “Airline Ticket Reservation System" in partial fulfillment of the
requirements for the degree of Bachelor's in Computer Application has been evaluated. In
our opinion it is satisfactory in the scope and quality as a project for the required degree.

SIGNATURE of Supervisor SIGNATURE of Coordinator

Mr. Avinash Maskey Mr. Amin Lana

School of IT School of IT

Thames International College, Baneshwor Thames International College, Baneshwor

SIGNATURE of Internal Examiner SIGNATURE of External Examiner

Mr. Prabin Maharjan Prof. Dr. Subarna Shakya

iv
 ABSTRACT

This project is an Airline Ticket Reservation System that makes it easy to book,
manage, and cancel flight tickets. It has a simple website where passengers can search for
flights, check their booking details, and get their boarding passes. At the same time,
airline admin can add or change flight schedules, keep passenger records, and manage
ticket details. All the information about tickets, passengers, and flights is stored safely in
a database so it can be quickly found when needed. The system also allows searching
tickets using a PNR number and provides easy options for cancellations. Built using PHP,
MySQL, HTML, and CSS, this project offers a fast, easy, and reliable way for both
passengers and staff to handle flight bookings.

Keyword: PHP, JavaScript, CSS, Html, JQuery, Ajax, web application, database.

iv
 ACKNOWLEDGEMENT

We would like to express our sincere gratitude to our supervisor, Mr. Avinash Maskey,
for giving us the opportunity to work on the project "Airline Ticket Reservation System".
His guidance, valuable suggestions, and encouragement throughout the project helped us
learn new tools, technologies, and concepts.

We are also thankful to our BCA Program Coordinator, Mr. Amin Lama, for his
continuous support and motivation, which greatly contributed to our personal and
professional development and the successful completion of this project.

Our heartfelt thanks go to Thames International College for providing us with guidance,
resources, and constant supervision, as well as to the library staff and members for their
cooperation and encouragement during the research process.

We would also like to acknowledge the support of our parents and friends, whose help
and motivation enabled us to complete this project within the given time frame.

Finally, we extend our gratitude to Tribhuvan University for including this project as
part of the BCA curriculum, giving us the opportunity to apply our theoretical knowledge
in a practical setting and enhancing our understanding of project development at this early
stage of our careers.

V
 TABLE OF CONTENTS

ABSTRACT ...............................................................................................................................iv
ACKNOWLEDGEMENT........................................................................................................... v
LIST OF ABBREVIATIONS ..................................................................................................... v
LIST OF TABLES ...................................................................................................................... v
LIST OF FIGURES ................................................................................................................... v
LIST OF ABBREVIATIONS ..................................................................................................... v
Chapter1:Introduction............................................................................................................. 1

1.1. Introduction ................................................................................................................... 1

1.2. Problem Statement ........................................................................................................ 2

1.3. Objectives ...................................................................................................................... 2

1.4. Scope and Limitation .................................................................................................... 2

1.5. Development Methodology .......................................................................................... 3

1.6. Report Organization ...................................................................................................... 3

Chapter 2: Background Study and Literature Review ........................................................ 4

2.1. Background Study .................................................................................................. 4

2.2. Literature Review ................................................................................................... 4

Chapter 3: System Analysis and Design ................................................................................ 6

3.1. System Analysis...................................................................................................... 6

3.1.1. Requirement Analysis .................................................................................. 7

3.1.2. Feasibility Analysis .................................................................................... 11

3.1.3. Data Modeling(ER-Diagram)...................................................................... 12

3.1.4. Process Modeling........................................................................................ 12

3.2. System Design ...................................................................................................... 17

3.2.1. Architectural Design ................................................................................... 17

3.2.2. System Flowchart ....................................................................................... 17

V
 3.2.3. Database Schema Design ........................................................................... 19

3.2.4. Interface Design(UI/UX) ............................................................................ 19

3.2.4. Physical DFD.............................................................................................. 19

3.3. Algorithm Used ................................................................................................ 19

Chapter 4: Implementation and Testing .............................................................................. 20

4.1. Implementation ..................................................................................................... 20

4.1.1. Tools Used(CASE tools, programming languages, database platforms) ....... 20

4.1.2. Implementation Details of Modules ........................................................... 21

4.2. Testing .................................................................................................................. 21

4.2.1. Test Cases for Unit Testing ........................................................................ 22

4.2.2. Test Cases for System Testing .................................................................... 23

Chapter 5:Conclusion and Future Recommendations........................................................ 25

5.1. Lesson Learnt/ Outcome ....................................................................................... 25

5.2. Conclusion ............................................................................................................ 25

5.3. Future Recommendations ..................................................................................... 25

REFERENCES .................................................................................................................. 30

APPENDIX: SYSTEM SCREENSHORTS ............................................................................. 26

V
 LIST OF TABLES
Table 1:Time Milestones ................................................................................................... 12

Table 2: User Registration ................................................................................................. 30

Table 3:Test case for User Login ...................................................................................... 31

Table 4:Test Case for Activate/Deactivate Request .......................................................... 32

Table 5:Test case for Accept/Reject User ......................................................................... 32

Table 6:Test case for Update Airline schedule…………………………….……..............32

V
 LISTOF FIGURES
Figure 3.1: Increment Model................................................................................... 6

Figure 3.2: Admin & User Use Case Diagram ....................................................... 9

Figure 3.3: ER Diagram ........................................................................................ 13

Figure 3.4: DFD Level 0 Diagram ........................................................................ 14

Figure 3.5: DFD Level 1 Diagram ........................................................................ 15

Figure 3.6: Three Tier Architectural Design ......................................................... 16

Figure 3.7: System Flowchart for Customer ..........................................................17

Figure 3.8: System Flowchart for Admin ............................................................ 18

Figure 3.9: Database Schema Design ................................................................... 19

Figure 3.10: Home Page UI. .................................................................................. 20

Figure 3.11: Register Form ................................................................................... 20

Figure 3.12: Login Page. ........................................................................................ 21

Figure 3.13: PNR Check ........................................................................................ 21

Figure 3.14: Physical DFD for Admin ................................................................... 22

Figure 3.15: Physical DFD for Customer. ............................................................. 23

V
 LIST OF ABBREVIATIONS

CRUD Create, Read, Update and Delete

CSS Cascading Style Sheet

DFD Data Flow Diagram

ERD Entity Relationship Diagram

HTML Hyper Text Markup Language

JS JavaScript

MySQL Microsoft Server Structured Query Language

PHP Hypertext Preprocessor

AJAX Asynchronous JavaScript and XML

UI User Interface

UX User Experience

V
 CHAPTER 1

INTRODUCTION

1.1 Introduction

The project “Airline Ticket Reservation System” has been developed to replace the
problems found in the traditional manual booking system. This software is designed to
make the ticket booking process easier, faster, and more accurate. It helps reduce
mistakes, saves time, and makes the overall process smoother for both the company and
the customers.

The system is user-friendly and does not require special technical knowledge to operate.
It gives error messages when incorrect data is entered, making it more reliable and secure.
With this application, users can focus on their main tasks instead of spending time on
record keeping, while the system efficiently manages information related to tickets,
flights, passengers, and payments.

Every airline has its own booking needs, and this system has been designed to meet those
requirements. It aims to improve communication between customers and the airline,
ensure safe and organized flight management, and contribute to the growth of the airline
industry by using modern technology.

1.2 Problem Statement

Traditional airline ticket booking systems are often manual, time-consuming, and high
risk of human error. Passengers face difficulties in accessing flight schedules, checking
ticket availability, and confirming bookings. Administrative staff also struggle with
managing large amounts of data, especially during peak seasons. There is a need for a
centralized, efficient, and user-friendly solution

12
1.3 Objectives
 To develop an online ticket reservation system with real-time booking
and cancellation.
 To provide secure user registration and login functionality.
 To enable admin users to manage flight, jet, and booking details.
 To reduce manual workload and errors through automation.

1.4 Scope and Limitation

1.4.1 Scope
The Airline Ticket Reservation System is developed aiming the coverage of many
travel organizations like:

 Real-time booking and cancellation system

 Admin panel for flight and passenger management

 Secure login system

1.4.2 Limitations
There are some criteria that may not be fulfilled by our application implemented.
Some of such limitations of our project are mentioned below:
 No real payment gateway integration (simulated only)
 Does not support mobile application
 Only supports single airline management


1.5 Report Organization

Introduction
This chapter deals with the introduction of the system with its objectives
and limitations along with the reason why the system is made.

Background Study and Literature Review

This chapter summarizes the work that has been carried out in the field
of data mining and also describes the features about some existing
applications related to the Airline Ticket Reservation System.
13
System Analysis and Design

This chapter focuses on the different requirement of the system, which

describes about the functional, non-functional, feasibility analysis, Entity
Relational diagram, Data Flow Diagram, design of the system with system
architecture, database schema, and interface design.

Implementation and Testing

This chapter emphasizes tools used in system development, implementing

details and result of test performed.

Conclusion and Future Recommendation

This chapter highlights brief summary of lesson learnt, outcome and

conclusion of the whole project and explain what have been done and what
further improvements could be done.

14
 CHAPTER: 2

BACKGROUND STUDY AND LITERATURE REVIEW

2.1 Background Study

Airline ticket reservation systems play an important role in modern transportation,

allowing people and goods to travel quickly and efficiently across the world. One of the
main functions of these systems is to handle the booking of flights for passengers, along
with managing all related operational and logistical tasks.

Over the years, the process of reserving airline tickets has become more advanced and
sometimes challenging. The rise of online booking platforms, changing travel patterns,
and new rules or policies in the airline industry have made the process more complex.
Airlines and travel service providers now face issues such as overbooking, deciding on
ticket prices, and ensuring good customer service.

The COVID-19 pandemic created even more challenges for the airline industry. Many
airlines saw a sharp drop in passengers because of travel restrictions, safety concerns, and
other factors. To survive in these conditions, airlines had to adjust their ticket reservation
process to meet new market demands while also following updated safety rules and health
protocols.

Because of these challenges, it is important for airlines to have a ticket reservation

process that is efficient, easy for customers to use, and flexible enough to adapt to
changing situations. This project focuses on studying the airline ticket reservation process
and exploring ways to make it more effective and efficient, keeping in mind the
challenges and opportunities in today’s airline industry.

2.2 Literature Review 15

Computer Reservation Systems (CRS) are central tools for managing real-time inventory,
pricing, bookings, and ticketing—not only for airlines but also for hotels, car rentals, and
other travel services. These systems support multiple distribution channels, ensuring
accurate and efficient reservation handling by linking airline internal systems with
external platforms such as web portals and partner interfaces [1].

The development of airline reservation systems began with early automation efforts such
as Trans-Canada Air Lines’ ReserVec in the late 1950s and American Airlines’ Sabre
launched in 1964. These platforms revolutionized the industry by enabling real-time
access to flight availability across multiple offices, greatly improving booking speed,
accuracy, and accessibility [1].

As technology advanced, airlines increasingly adopted Global Distribution Systems

(GDS) like Amadeus, Galileo, Sabre, and Worldspan, which integrate airline, hotel, and
car rental inventories to serve both travel agents and customers [1]. Recent studies
highlight the importance of User-Centered Design (UCD) in improving reservation
systems. UCD principles focus on creating intuitive and responsive interfaces, which
significantly enhance usability and customer satisfaction [2].

Modern reservation systems have moved toward distributed, modular designs such as
microservices and edge computing to handle growing traffic and complexity. Research
demonstrates that edge-enabled microservices frameworks improve responsiveness,
reduce latency, and offer better scalability [3]. Additional studies show that microservices
architectures provide a 40% increase in scalability, a 50% reduction in downtime, and
support for 30% more concurrent users compared to monolithic systems [4].

Advanced technologies such as Artificial Intelligence (AI), blockchain, and predictive

analytics are now being integrated into airline reservation systems. AI is used for demand
forecasting, dynamic pricing, and personalized offers, while blockchain enhances security
and transparency. Predictive analytics further improves decision-making by analyzing
travel trends and optimizing resources. These technologies have been shown to increase
system availability by 30%, scalability by 40%, transaction speed by 35%, and customer
engagement by 25% [5]–[7].

16
 CHAPTER 3

SYSTEM ANALYSIS AND DESIGN

3.1 System Analysis

This system is designed with the series of processes starting with requirement
analysis, design, implementation and testing. During requirement analysis, all the
functional and nonfunctional requirement are analyzed and system is developed
according to the requirement then designing of the system is carried out. After
the design process, coding and development part is started then after integrating
the system there is testing of the system. If the testing is positive then system is
implemented otherwise some maintenance is done and system come in operation.

Figure3.1: Incremental Model for Airline Ticket Reservation System

17
3.1.1 Requirement Analysis
i. Functional Requirements

a. User Registration and Authentication

 Create account with name, email, phone, and password.

 Secure login for registered users.
 Role-based access: Customer, Admin, optional Staff.

b. Flight Search and Viewing

 Search flights by city, date, and class.
 Display flight details: number, airline, times, duration, seats,
fare.
c. Ticket Booking
 Select flights and enter passenger details.
 Check seat availability and confirm booking.
 Generate unique PNR for each reservation.
d. Ticket Cancellation
 Cancel tickets before departure.
 Update seat availability and follow refund policy.
e. Payment Processing
 Support credit/debit cards and wallets.
 Confirm booking after payment verification.
 Provide on-screen and email receipts.
f. Administrative Panel
 Add, update, delete flights and jets.
 Monitor bookings, users, and transactions.
 Generate booking, revenue, and occupancy reports.
g. Reporting and Data Management
 Store and manage all system records.
 Generate and export reports securely.
 Ensure fast, secure data access.

18
USECASE DIAGRAM

The Use Case Diagram of the Airline Ticket Reservation System shows the interaction
between the system and its users. The main actors are Customer and Admin .Customer
can register, log in, view flight details, book tickets, make payments, and cancel
bookings. Admin manages flight schedules, views booking details, and handles
cancellations.

Figure 3.2: UseCase Diagram for Airline Ticket Reservation System

19
 i. Non-Functional Requirement

 Security :The system uses login authentication for both customers and admin to
prevent unauthorized access. Password protection and input validation help ensure
data safety and prevent harmful or incorrect information from being stored.
 Performance : The system is designed to handle tasks like searching flights,
booking tickets, and updating schedules quickly.
 Reliability and Availability : The system works consistently, ensuring that
bookings, cancellations, and updates are always saved correctly in the database.
Being web-based, it is accessible anytime and from anywhere with an internet
connection, so users and admin can use it without time restrictions.

3.1.2 Feasibility Study

a. Technical Feasibility

This system is developed using PHP and MySQL, which run on the server side
and do not require any extra software for the user. Technologies like JavaScript,
HTML, jQuery, and CSS work on the client side and are supported by all modern
computers without additional setup. There is no extra cost for adding AI features.

b. Operational Feasibility

The Airline Ticket Reservation System works like a tourism-based online

platform where authorized users can log in, book tickets, and explore different
destinations. The database is well-organized and secure, ensuring no loss of
important information. The system can also block offensive text, making it safe
and user-friendly for the community.

c. Economic Feasibility

Since this is a web-based system, there is no need to purchase expensive licenses. It

only requires a web browser (like Google Chrome, UC Browser, etc., which are
free and commonly available) and a web server such as XAMPP, which can be
downloaded for free. This makes the system
20 cost-effective to use and maintain.
Time Milestones

This project will go according to below Timeline.

Task Name Duration

Problem Analysis(Problem Definition & Statement) JAN(1-15)

Requirement Analysis JAN(15-30)

System Designing(System Diagrams and Algorithms) FEB(1-30)

Coding & Testing of Algorithm MAR(01-30)

Implementation and Module Testing APR(01-14)

System Integration Testing MAY(15-30)

System Debugging and Maintenance JUN(1-30)

Project Submission JULY

Table 3.1: Time Milestones

21
3.1.3 Data Modeling

The data model for the Airline Ticket Reservation System defines seven main entities:
Customer, Ticket, Flight, Class, Payment, Admin, and Airline. Relationships connect
customers to tickets, tickets to payments, flights to classes, and admin to airlines. Each
entity has specific attributes such as IDs, names, schedules, and amounts, ensuring
organized storage and retrieval of booking and management data.

Figure 3.3: Entity Relational Diagram for Airline Ticket Reservation System

22
3.1.3 Process Modeling
DFD level 0

Level 0 DFD, or context diagram shows the Airline Ticket Reservation System as one
main process interacting with passengers, admin and a payment gateway, highlighting
only the flow of booking, flight, and payment information without internal details.

Figure 3.4 : Level 0 Diagram for Airline Ticket Reservation System

23
DFD Level 1

DFD Level 1 shows the Airline Ticket Reservation System divided into processes like
managing flights, booking tickets, processing payments, and generating reports, with data
flowing between passengers, admin, the payment gateway, and the system’s database.

Figure 3.5 : Level 1 DFD for Airline Ticket Reservation System

24
3.2 System Design

To realize the different functional requirement of the system in graphical form,

different design diagram of the system has been prepared which are as follows:

3.2.1 Architectural Design

For this system, three tier architecture issued which includes user interface, web
server and database. In architectural design, basic structure of the system is
shown.

Figure 3.6: Architectural Design of Airline Ticket Reservation System

25
System Flowchart

The figure below is the flowchart of Airline Ticket Reservation System. Here, customer
and admin such as customer a login the system and if customer is not register then they
need to register first. After login success, it redirects to dashboard of customer and
applicants then customer view the customer category and customer in that category
which they want. Likewise, the admin do not need to register they can directly login the
system and after login success it redirects to dashboard of admin and admin can manage
categories, and all the details of flight. Then admin and users log out the system

For Customer

Figure 3.7: Flowchart of Airline Ticket Reservation System

26
For Admin

Figure 3.8: Flowchart of Airline Ticket Reservation System

27
3.2.2 Database Design

The figure below is the database schema design of Airline Ticket Reservation
system. Database schema design is used to show basic structure of the system. In
Airline Ticket Reservation System, there are seven tables in the databases each
of them has their own fields where their id is primary key and if that id is used in
another table, it becomes foreign key and foreign key are connected to another
table with a line. There is data type of each entity and the foreign key in schema
is represented by the arrow as shown in the diagram.

Figure 3.9: Database Schema Design of Airline Ticket Reservation System

28
3.2.3 Interface Design

In the Airline Ticket Reservation System, interface design focuses on creating simple and
user-friendly screens for passengers and admins. Passengers get clear pages to search
flights, book tickets, make payments, and view booking details. Admins have easy forms
to add, update, or delete flights and check passenger lists. The design uses clear
navigation menus, buttons, and forms so users can quickly find what they need and
complete tasks without confusion.

Figure 3.10: Homepage for Airline Ticket Reservation System

Figure 3.11: Register form for Airline Ticket Reservation System

29
Figure 3.12: Login form for Airline Ticket Reservation System

Figure 3.13: PNR Check for Airline Ticket Reservation System

30
3.2.4 Physical DFD

For Admin

Figure 3.14: Physical DFD for Airline Ticket Reservation System

31
For Customer

Figure 3.15: Physical DFD for Airline Ticket Reservation System

3.2 Algorithm Details

Binary Search is an efficient searching algorithm used to find the position of a target
value within a sorted array (or list). It works by repeatedly dividing the search interval in
half, which drastically reduces the number of comparisons needed compared to linear
search.

The Passenger Name Record (PNR) number is a unique identifier assigned to each
ticket booking in an airline ticket reservation system. When the system handles a large
32
 number of bookings, an efficient method is required to quickly locate a specific
PNR. The Binary Search Algorithm provides a fast and reliable way to search a
sorted list of PNR numbers.

Searching for a PNR in a large list using linear search (O(n)) can be time-
consuming. Binary search minimizes the number of comparisons needed to find a
PNR, improving response time and user experience in real-time applications.

How Binary Search Works for PNR Search

1. Precondition: The list/array must be sorted in ascending or descending order.

2. Initialize:

 Set low = 0 (start index of the array)

 Set high = n - 1 (end index of the array, where n is the number of elements)

3. Process:

 Calculate the middle index:

mid=[low +high]/2

 Compare the middle element with the target value:

o If array[mid] equals the target, return mid (found).
o If array[mid] is less than the target, update low to mid + 1 (search
right half).
o If array[mid] is greater than the target, update high to mid - 1
(search left half).

4. Repeat steps until low is greater than high. If no match is found, return a "not
found" indication (e.g., -1).

33
Pseudo code :

function binarySearchTicket(tickets[], targetPNR):

low = 0

high = length(tickets) – 1

while low <= high:

mid = floor((low + high) / 2)

if tickets[mid].PNR == targetPNR:

return mid // Ticket found at index mid

else if tickets[mid].PNR < targetPNR:

low = mid + 1

else:

high = mid – 1

return -1 // Ticket not found

34
 CHAPTER 4

IMPLEMENTATION AND TESTING

4.1 Implementation

4.1.1 Tools Used

Following are the tools and frame work used for the accomplishment of this project:

1. Front-End Technologies

a. HTML
 Used for structuring and creating web pages of the Airline Ticket
Reservation System.
 Defines page elements such as headings, paragraphs, links, tables, and
images.
 Facilitates the creation of forms for user registration, flight booking, and
login.
b. CSS
 Used for styling HTML elements to enhance the visual design of the
system.
 Applied through inline, internal, and external stylesheets.
 Controlled text colors, fonts, layouts, spacing, and responsive design.
c. JavaScript / jQuery / AJAX
 JavaScript was used for client-side validation and to add interactivity to
the system.
 jQuery simplified DOM manipulation and event handling.
 AJAX enabled asynchronous data loading, allowing parts of the page (e.g.,
flight search results) to update dynamically without reloading the entire
page.

35
2. Back-End Technology

 PHP
 Used for server-side scripting to handle core functionalities such as
booking, cancellation, and user authentication.
 Enabled database connectivity, data encryption, and validation of user
inputs.
 Supported CRUD operations (Create, Read, Update, Delete) for managing
flights, users, and bookings.

3. Web Server

 Apache (via XAMPP)

 Used to host and run PHP scripts locally during development.
 Provided a stable server environment for executing back-end code and
testing functionalities.

4. Database Engine

 MySQL (via XAMPP)

 Served as the relational database management system (RDBMS) for
storing and managing system data.
 Stored information related to flights, bookings, users, and transactions.
 Supported SQL queries for performing CRUD operations efficiently.

5. CASE Tools for Documentation and Design

 MS Office
 Used for writing and formatting project documentation and reports.

 [Link]

 Used to create system diagrams such as ER Diagrams, DFDs, Use Case

Diagrams, and Sequence Diagrams.
 Provided an easy drag-and-drop interface for faster diagram creation.

36
4.1.2 Implementation Details of Modules

Different module soft his system are described as below

Home Page Module

The Homepage of airline ticket reservation system contains information

about airline ticket, about us, contact details. Further navigation from
homepage is handle by AJAX.

Navigation menus

 About Us

 Book Tickets

 Contact Us

 About Us

 Check PNR

 Login

37
Admin Module

[Link]
[Link],further navigation
from admin module includes

 Home

 Dashboard

 Logout

 View booked tickets for flight

 Add flight schedule details

 Delete flight schedule

Customer Module

The Customer Module of Airline Ticket Reservation system have been accessing to Admin
module. This system contains information about menu and control panel, further navigation
from Customer module includes

 Book Flight Tickets

 View Booked Tickets

 Print Booked Tickets

 Cancel Booked Tickets

38
Login Module

a. Admin Login

 Admins sign in using their valid username and password.

 There is no option for admins to self-register.

b. Customer Login
 Customers log in with the username and password they registered with.
 Once logged in, they can access booking and ticket management features.

Register Module

a. Customer Registration
 New customers enter their name, phone number, and password to create

an account.

 After the information is submitted, they can log in and use the system.

4.2 Testing

System testing is done by giving different training and testing datasets. This test is done
to evaluate whether the system is providing accurate summary or not. During the phase of
the development of the system, our system is tested time and again. The series of testing
conducted are as follow:

4.2.1 Test Cases for Unit Testing

In unit testing, we designed the entire system in modularized pattern and each module is
tested. Until we get the accurate output from the individual module, we work on the same
module. The input forms is tested so that they do not accept invalid input.

39
User Registration

[Link]. Test Name Input Expected Actual Test

Output Output Result

1. Open [Link] Homepage Home Pass

Website page

2. Enter un Full name = lhakpa Error Registration Pass

matched password Failed Error
Email=lhakpa39@[Link]
and does not password does
confirm Password=1234 match not match
password
Conform

password=1111 User

type= user

3. Enter Full name = lhakpa Registration Registratio n Pass

matched successful successful
Email=lhakpa39@[Link]
and
confirm Password=1234
password
Conform password=1234

Usertyp
e=user

Table 4.1: User Registration

40
User Login

[Link]. Test Name Input Expecte Actual Test

d Output Output Result

1. Open website [Link] Hom Home Pass

oject e Page
Page

2. Enter Username Userna Login Failed Login Pass

and Invalid me: And credential Failed
password lhakpa6 not match is
789 shown

Passwo
rd:
12345

3. Enter Valid Userna Login Redirect to Pass

Username and me: Successful Dashboard
Password and lhakpa6 and redirect
click login 789adm to dashboard

Button Passwo
rd:
12345

Table 1.2:Testcase for User Login

4.2.2 Test Cases for System Testing

In system testing, whole system is tested as below:

Test Case for Active/Deactivate

41
Test Case1 Activate/Deactivate Request

Test Event Click on Accept Button

Expected Result A new plan is created

Test Result Activate

Table 4.3: Test Case for Activate/Deactivate Request

Test Case for Request Accept user

TestCase1 Request/Accept user
Test Event Click on accept-on

Expected Result A new user created

Test Result Successfully user created

Table 4.4: Test case for Accept/Reject

Test Case for Update Airline schedule

Test Event Update Airline schedule
Test Data Like
Flight number =123
Departure=Kathmandu
Arrival= Pokhara
Date=2:00AMto4:00PM
jet id=234 etc.

Expected Result Airline information updated

Test Result Successfully update schedule

Table 4.5: Test case for update Airline Schedule

42
 CHAPTER 5

RESULTANDFUTURERECOMMENDATION

5.1 Conclusion

This project successfully implements a secure, user-friendly airline reservation

system with features for real time ticket booking and admin management. It
demonstrates practical application of database systems, web development, and
algorithm optimization

5.2 Lesson Learnt/Outcome

Every project makes us to learn and gain the knowledge in different aspects. In the
following project, we have learned lots of problem-solving skills and learn things
like finding the solution on our own, proper use of guidelines, communication and
writing skills and management of team.

 Problem Solving Skills

From this project, we have learned lots of problem-solving skills and also learned
to recognize different errors occur in this system and solve it.

 Writing Skills

We have learned how to prepare proposal and documentation related with project
and also learned to use different case tools for use case diagram, schema diagram,
data flow diagram, and ER- diagram and so on.

 Manage time

The most important lesson learnt was management of time according to the
complexity of the system components i.e. know which components to prioritize.

43
5.3 Future Recommendations

The development project could have been more efficiently handled with regards
to design and development. The documentation process might have been better
programming the project prior to any documentation. The system can be updated
based on the users’ requirements recommendation. The page load and server
load speed might be improved.

Some of the future recommendation for this system is:

 Adding the feature of seat booking system.

 Add mobile application support
 Integrate real payment gateway

44
REFERENCES

[1] S. Hossain, “Analysis of Airlines Ticket Reservation Systems,” ResearchGate, 2025.

[Online].Available:[Link]
rlines_Ticket_Reservation_Systems

[2] B. Pokhrel, A. Gautam, and S. Karki, “Enhancing the Usability, Visibility, and
Responsiveness of an Airline Reservation System: A User-Centered Design Approach,”
International Journal of Computer Communication and Innovation, vol. 2, no. 2, pp. 12–
21, 2024.

[3] A. Barua and M. Kaiser, “Optimizing Airline Reservation Systems with Edge-Enabled
Microservices: A Framework for Real-Time Data Processing and Enhanced User
Responsiveness,” ResearchGate, 2024.

[4] R. Gupta, “Scalable and Resilient Airline Reservation Systems: A Microservices

Architecture Approach,” arXiv preprint arXiv:2410.19701, 2024.

[5] A. Barua and M. Kaiser, “A Next-Generation Airline Reservation System

Architecture: Cloud-Based Microservices, AI, and Blockchain Integration,” arXiv
preprint arXiv:2411.06538, 2024.

[6] P. Sharma, “Predictive Analytics in Airline Reservation Systems: A Microservices-

Based Approach,” arXiv preprint arXiv:2412.15616, 2024.

[7] “User-Centered Design,” Wikipedia. [Online]. Available:

[Link]

45
APPENDIX: SYSTEM SCREENSHOTS

Database Overview

Airline Database

Ticketdetailsdatabase

46
Payment Database

Home page

47
Contact us page

Pnrall check page

48
49