Tribhuvan University

Faculty of Humanities and Social Sciences

AIRLINE TICKET RESERVATION

PROJECT REPORT

Submitted to

Department of Computer Application

Thames International College

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

Submitted by

Lhakpa Chhiring sherpa (Registration no. 6-2450-19-2020)

Himani Waiba (Registration no. 6-2-450-20-2020)

Under the Supervision of

Avinash Maskey
 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 Lhakpa

Chhiring sherpa and Himani Waiba 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.

SIGNATURE

Avinash Maskey

SUPERVISOR

School of Business and Technology

Thames International College

ii
 Tribhuvan University

Faculty of Humanities and Social Sciences

Thames International College

LETTER OF APPROVAL

This is to certify that this project prepared by Lhakpa Chhiring Sherpa and Himani
Waiba entitled “AIRLINE TICKET RESERVATION" 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.

Avinash Maskey Biwas Limbu Head

Supervisor of Department
School of Business and Technology School of Business and Technology
Thames International College Thames International College

External Examiner
Pravin Maharjan
Internal Examiner

iii
 Abstract
Millions of people who belong to Trekking sector or who love to travel and want to do a adventure the
online guide booking system is very important. Online Guide Booking System That helps the peoples to
interreact with guide and they get a chance to select a guide through a guide profile.

In today’s world, travel has become one of the most people hobby or dream. when people are off with
their duty, they create a plan to visit new place. They go with their family friend or solo. One of the most

Important part is that when you were going to travel new place, we need to research through many sides. We get the
information about the place where want to visit but we could not see a guide. In Nepal scenario when client book the for
the trek, they suddenly talk with travel agency. They did not get a guide information. Many cases travel sends a less
experience guide to trek and many clients loss their life,

Guide did not know how to handle a client when they are suffering from altitude sickness. Not only
clients, the people who are interested to do a guide they also get a chance to apply for guide job. When all
the process are complete by guide and approve by guide. After all, a client as well as guide comes with
numerous benefits. “Online Guide Booking System” is the system for the needy people especially client
who are searching a experience guide and the people who want to do a trekking guide. It makes the whole
process of the system easy by providing the easier application filling.

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

iv
 Acknowledgement

We would like to express our special thanks of gratitude to our supervisor Mr. Avinash Maskey who
gave us the golden opportunity to do this wonderful project on the topic of Airline Ticket Reservation
System, which also helped me in doing a lot of research and we came to know about so many new tools
and technologies.

we would like to express our special thanks of gratitude to our Campus Chief Dr. Laxman Singh
Kunwar who gave us permission for doing this Project.

we would like to express our special gratitude and thanks to our BCA Program Coordinator Mr. Amin
Lama for his support and help for our personnel development and mainly for the completion of this
Project.

we are highly indebted to Thames International College for their guidance and constant supervision as well
as for providing necessary information regarding the Project and support in the completion.

we would also like to express my gratitude towards library and member of Thames International College
for their kind co-operation and encouragement which help me in completion of this Project

we would also like to thank our parents and friends who helped us a lot in finalizing this project within the
limited time frame.

In the end, I would also like to thank Tribhuvan University for giving us this opportunity via the course of
Computer Application to help us understand the project ethics at this early stage and helped us to evaluate
my knowledge and expand it a little more.

v
 Table of Contents
Supervisor's Recommendation ............................................................................................ ii

LETTER OF APPROVAL ................................................................................................. iii

Abstract .............................................................................................................................. iv

Acknowledgement .............................................................................................................. v

Chapter 1: Introduction ..................................................................................................... 1

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

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

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

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

1.5 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 ....................................................................................................... 12

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

3.1.5 System Flowchart .................................................................................................. 13

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

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

3.2.2 Database Schema Design ...................................................................................... 17

3.2.3 Interface Design .................................................................................................... 19

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

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

vi
 4.1.1 Tools Used ............................................................................................................ 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

Appendices ........................................................................................................................ 26

References ......................................................................................................................... 30

vii
 LIST OF TABLES
Table 3.1: Time Milesstones .......................................................................................................... 12

Table 4.1: User Registration ........................................................................................................... 30

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

Table 4. 3: Test Case for Activate/Deactivate Request .................................................................. 31

Table 4.4: Test case for Accept/ Reject User ................................................................................. 31

Table 4.5: Test case for Update Airline schedule ........................................................................... 31

viii
 CHAPTER -1
INTRODUCTION
1.1. Introduction

The project entitled “Airline Ticket Reservation System” has been develop to override
the problem prevailing in the practicing manual system. This software is supported to
eliminate and, in some cases, reduce the hardships faced by this existing system.
Moreover, this system is designed for the particular need of the company to carry out
operations in a smooth and effective manner.

This application is reduced as much as possible to avoid errors while entering the data. it
also provides error message while entering invalid data. No formal knowledge is needed
for the user to use this system. Thus, by this all it proves it is user-friendly. Online Ticket
Reservation System, as described above, can lead to error free, secure, reliable and fast
management system. It can assist the user to concentrate on their other activities rather to
concentrate on the record keeping. Thus, it will help organization in better utilization of
resources.

Every organization, whether big or small, has challenges to overcome and managing the
information of Ticket, Flight, Passenger, Payment. Every Flight Ticket Reservation System has
different Flight needs; therefore, we had made this system.

The Airline Ticket Reservation System is designed to revolutionize the way customer and
organization to connect and interact. By leveraging technology, this platform aims to enhance the
overall customer experience, promote safe and well-organized flight, and support the growth of
the airline community worldwide.

1.2 . Problem Statement

The BUDDHA TRAVELS company is one of the Airline Reservation Company in Nepal.
It has number of branches, which are spread over the country or the world. So, person
wants to reserve his/her ticket and he/she has to contact at nearest Overseas Travels
branch. The Airline TICKETS Reservation System (ARTS) provides an interface to
schedule flights and reservations for an airline that services. It is responsibility is to keep
track of system users, customers, Airbus information, flight information and cancellation.
The functionality of the ARS is broken into various primary groups. Customer reservation
information and user were added, deleted and updated in the implementation phase to
account for the way we decide to implement security. User keeps track of the username;
1
password information and customer reservation information link provide a link between
the customers reservation information and login table.
Time Consuming and it requires staff int the tickets reservation 24/7. The reservation can
be done by personally visiting to the airport ticket counter which is quite tedious for the
customer and there will be no guarantee of getting tickets for airlines. Payment’s method
was only possible through cash. No website which makes the customer known about the
availability for the tickets.

1.3. Objectives

• To provide large number of ticket reservation and cancelation in few times.

• To ensure that ticket reservation is easy and user friendly for customers.
• to create a distributed system that will be used by customers.
• Reduce the work load of the ticket officers

1.4. Scope and Limitation

The Airline Ticket Reservation System is developed aiming the coverage of many
tourism organizations like:

• Tour Agencies

• Travels and client franchisees

• Wild Life Tourism Franchisees and many more

Although Airline Ticket Reservation System helps any unfamiliar people/ tourist to get
help and helpers by this web site navigation. Some major limitations are listed below:

• Technology changes occur on the air and it’s mandatory to upgrade the features
frequently.

• Remote areas may not have internet access so that the users may feel disgusting while
s/he is in poor network.

• Nowadays users may prefer access from mobile apps. It does not have mobile application
rather the web version works on all browsers.
2
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.

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.

3
 CHAPTER-2
BACKGROUND STUDY AND LITERATURE REVIEW
2.1. Background Study

Airline tickets reservation system paly a vital mode of transportation, enabling people and
goods to travel around the world efficiently and quick. One of the key aspects of airline
travel is the process of air tickets reservation, which involves booking flights for
passenger and managing the associated logistical and operational tasks.
In recent years, airline tickets reservation system has become an increasingly complex
and challenging process, with the rise of online booking platforms, changing travel
patterns, and new regulations and policies that affect the airline industry. As a result
airline and other travel service providers face a range of challenges related to air tickets
reservation, including overbooking, pricing strategies and customer services issues.
Moreover, the COVID-19 pandemics has significantly impacted the airline industry, with
many airlines experience a drastic reduction in demand for air travel due to travel
restrictions, safety concerns, and other factors. As a result, airline have to adapt their air
tickets reservation process to new market conditions, while also ensuring that they
comply with evolving safety regulation and protocols.
Given these challenges, it is essential for airlines and other travel service providers to
have effective air tickets reservation process in place that are efficient, customer-friendly,
and adaptable to changing market conditions, our report will focuses on analyzing the air
tickets reservation process and identifying strategies for improving its efficiency and
effectiveness in the context of the challenges and opportunities facing the airline industry.

2.2. Literature Review

An airline reservation system is a part of so-called Passenger Service Systems (PSS),

which are application supporting the direct contract with the passenger (Crosby, 2015).

The airline reservation system was of the earliest changes to improve efficiency. Airline
reservation system eventually evolved into the Computer Reservation System (CRS).
Computer reservation system is used for the reservation of a particular airline and
interface with a Global Distributed System (GDS) which travel agency and other
distributed channels in making reservation for most major airlines in a single system

The history of airline reservations systems began in the late 1950s when
American Airlines required a system that would allow real -time access to
flight details in all of its offices, and the integration and automation of its
booking and ticketing processes. As a result, Sabre(Semi - Automated
4
Business Research Environment) was developed and launched in 1964(C.
Winston, 1995). Sabre's breakthrough was its ability to keep inventory
correct in real time, accessible to agents around the world. Prior to this,
manual systems required centralized reservation centers, groups of people in
a room with the physical cards that represented inventory, in this case, seats
on airplanes.[1]

The deregulation of the airline industry, in the Airline Deregulation Act,

meant that airlines, which had previously operated under government -set
fares ensuring airlines at least broke even, now needed to improve efficiency
to compete in a free market(Shon, 2003). In this deregulated environment the
ARS and its descendants became vital to the travel industry. In the early days
of American commercial aviation, passengers were relatively few, and each
airline's routes and fares were tightly regulated by the Civil Aeronautics
Board. These were published in a volume entitled The Official Airline Guide,
from which travel agents or consumers could construct an itinerary, then call
or telex airline staff, which would mark the reservation on a card and file it.
As demand for air travel increased and schedules grew more complex, this
process became impractical. This system was used in the hospitality
industry[2].

A literature check of airline reservation systems reveals that there have been
significant advancements in this area over the once many decades. With the
arrival of the internet and ultramodern technologies, airlines have been
suitable to ameliorate stheir reservation systems to give better services to
their guests[3].

Several studies have concentrated on the design and development of airline

reservation systems. For illustration, a study by Ranganathan and Ganapathy(
2013) proposed a design for a pall - grounded airline reservation system that
could be penetrated from anywhere in the world. The system was designed to
be largely scalable and could handle a large number of druggies
contemporaneously[4].

5
2.2.1. Proposed Solution:

Here I have created a logical roadmap for a system to give an easy method of overcoming
these troubles in Nepal airline sector. The project is aimed at exposing the relevance and
importance of Airline reservation system (AFS).it is projected towards enhancing the
relationship between customer and airlines agencies through the use of ARSs, thereby the
flight ticketing and selling process and all air travelling operation

6
 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.

Figure 3.1: Incremental Model for Airline Ticket Reservation System

7
 3.1.1. Requirement Identification
i. Functional Requirements:

User Registration and Login

• The system shall allow new users (customers) to create an account by providing
personal information such as name, email, phone number, and password.
• The system shall allow registered users to log in using valid credentials (email
and password).
• The system shall support different user roles: Customer, Admin, and optionally
Staff.

Flight Search and View

• The system shall allow users to search for available flights based on:
o Departure and destination cities
o Travel date
o Class (Economy, Business, First)
• The system shall display a list of available flights with details such as:
o Flight number
o Airline name
o Departure/arrival times
o Duration
o Available seats
o Fare details

Ticket Booking
• The system shall allow users to select a flight and proceed to book a ticket.
• Users must provide passenger details including name, age, gender, and ID proof.
• The system shall confirm seat availability before finalizing the booking.
• The system shall assign a unique booking reference number (PNR) to each
reservation.

8
 Payment Processing
• The system shall integrate basic payment options (e.g., credit/debit card or wallet
simulation).
• The system shall confirm the booking only after successful payment.
• A payment receipt or confirmation should be generated and sent to the user.

Admin Panel Functionality

• Admins shall be able to:
o Add, update, and remove flight schedules.
o Monitor all user bookings and transactions.
o Manage users (block/unblock accounts if needed).
o Generate reports (daily bookings, revenue, etc.).

9
Use Case Diagram

In Airline Tickets Reservation System, there are two actors such as admin, and user
where admin can login, view book tickets, add flight schedule details, delete flight
schedule details, activate and deactivate aircraft details. Where user can login, view
booked tickets, book. Likewise, Admin can login, search, add or remove the guide,
cancel the plan. Clients can register, login, create plane, search and logout from the
system. Lastly, guide can register, login, accept reject the request, fill kyc and logout
from the system.

Figure 3.2: Use Case Diagram for Airline Ticket Reservation System

10
ii. Non-Functional Requirement

• The Performance: The Web system will respond quicker than other
• Scalability: How well a system can handle an increase in users or workload
• Security: How well a system protects against unauthorized access and data
breaches
• Usability: How easy a system is to use
• Maintainability: How easy it is to update and modify the system

3.1.2. Feasibility Study

1. Technical

As the PHP, MySQL technologies work on server so that we don’t need any extra
software or platforms. Similarly, JavaScript/ html /JQUERY/ CSS technologies rely on
client side and are supported natively in any computer system. It will no longer cost for
artificial intelligent feature.

2. Operational

Operationally this is like social networking for tourism called Airline Ticket Reservation
System and Exploring places based on sufficient information which enables users to visit
as website, (only authorized user can), create or book the ticket and can explore places
themselves.

Databases will be securely organized so this is powerful in networking without losing

any useful data.

Operationally it will block offensive text which is appreciable by the community.

3. Economic Feasibility

Economically this system is web based so no need to license the product except
validating from w3c. It will only require an internet browser (like Google chrome, UC
browser etc. which are available already in every computer freely), Web Server (like
XAMPP/WAMPP etc. which is easily available).

11
This system will be medium scale web site which need domain space which can cost a
little bit depending on number of users, data etc.

4. Schedule Feasibility

The project set up was based on a timeline of 3 months and it was completed its tasks and
documentations according to timeline.

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

3.1.3. Data Modeling

12
In Entity-Relationship diagram there are seven entities named Customer, Ticket, Flight,
class, payment, admin and airline. Customer has attributes like mobile no, customer id,
username, email and address. Likewise, ticket has seat no, departure, flight no, Date time,
class, arrival and PNR no and flight has attributes like flight no, from city, to
city,departure time. class has attributes like class id, flight no, class type. admin has a
attributes like username, password, admin id. Payment has a attribute like pay id, pay
amount, pay date and pnr. Airline has attributes like air id air logo path and air name.
customer book the ticket. ticket receives by payment. Flight has a class. Admin can
modified airline.

Figure 3.3: Entity Relational Diagram for Airline Ticket Reservation System

13
3.1.4 Process Modeling

Data Flow Diagram of Online Guide Booking System consists of two levels of DFD
context diagram and level one dfd. Both these levels are used for making data flow
diagram of Online Trekking Guide Booking System

Data Flow Diagram: level 0

Figure 3.4: Level 0 Diagram for Airline Ticket Reservation System

14
DFD Level 1

This DFD shows has three entities, three processes as we have three data database table.
Its major work flow starts with any entity, furthermore the request is sent to the sub
process and the sub process finally access database to complete task execution.

Figure 3. 5: Level 1 DFD for Airline Ticket Reservation System

15
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 is used 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

The figure below is the flowchart of Airline Ticket Reservation System. Here, admin and
clients such as client a login the system and if client is not register then they need to
register first. After login success, it redirects to dashboard of client and applicants then
client view the client category and client in that category which they want. Likewise for
the admin does 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 and clients. Then admin and users log out the system.

3.1.5 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
16
For Customer

Figure 3.7: Flow chart of Airline Ticket Reservation System

17
For Admin

Figure 3.8: Flow chart of Airline Ticket Reservation System

18
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

19
3.2.3. Interface Design

Interface design is used to design how the Online Guide Booking system looks like and
this design is shown to user that how the system will look. And after finalizing the
system development starts. The UI design of home page, register page, login page and
dashboard page of sponsorship management system are shown below:

Figure 3.10: Homepage for Airline Ticket Reservation System

Figure 3.11: Register form for Airline Ticket Reservation System

20
Figure 3.12: Login For Airline Ticket Reservation System

Figure 3.13: PNR Check for Airline Ticket Reservation System

21
3.2.4. Physical DFD

For Admin

Figure 3.14: Physical DFD for Airline Ticket Reservation System

22
For Customer

Figure 3.15: Physical DFD for Airline Ticket Reservation System

23
3.3 Algorithm Details

The proposed of Airline Tickets Reservation project follows a systematic approach to system
design, encompassing both low-level and high- level designs that are subject to refinement. The
low-level design phase focusing on defining the smallest functional units of the systems
components, specifying algorithms such as Binary search for efficient data processing. One the
other hand, high level design provides an overview of the project, outlining a comprehensive
approach to achieve the desired outcome and server as a strategic roadmap.
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 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. Take the sorted list of PNR numbers.
2. Set low = 0 and high = n - 1 (start and end of the list).
3. Calculate the middle index: mid = (low + high) / 2.
4. Compare the target PNR with the middle element:
• If equal → PNR found
• If less → Continue search in the left half
• If greater → Continue search in the right half
5. Repeat steps until the PNR is found or the list is exhausted.

Example PNR List (sorted):

[100001, 100005, 100010, 100015, 100020, 100030]

Target PNR: 100015

Steps:
• mid = 2, value = 100010 → target > mid → search right
• mid = 4, value = 100020 → target < mid → search left
• mid = 3, value = 100015 → Match found

24
 CHAPTER-4
IMPLEMENTATION AND TESTING

4.1. Implementation
4.1.1. Tools Used
Following are the tools and framework used for the accomplishment of this project:

Front End Languages

• HTML

This project used, html is used for creating different webpage and sites. It is used to
create and structure sections, headings, links, paragraphs using various tags and elements.
also define headers, paragraphs, links, and images of Guide booking system by using
html.

• CSS

This project used CSS is used for designing different tags of html. It is also used to
design different component by the help of class and id. Different CSS are used such as
inline CSS internal CSS, and external CSS to design this system. It is used for defining
the styles for web pages. By using CSS, we can control the text color, font style, the
spacing between paragraphs, sizing of columns, layout designs, and many more.

• JavaScript/jQuery/AJAX

Airline Ticket Reservation System, JavaScript is used for customer-side validation and
to make dynamic, interactive and responsive web pages. It is used to add dynamic
behavior to the webpage and add special effects to the webpage. jQuery and AJAX is
used this project to load the data from [Link] on the basic of user click.

25
Back End Languages

PHP

This project used, PHP is used for the backend purpose and for making dynamic web
pages. It is used for server-side scripting purpose to add connectivity to the database and
also used to encrypt the data, validate the user data, confirm user to go to certain pages,
login pages. It also includes add, update and delete the data from the database.

Web Server

• APACHE SERVER (XAMPP Server)

This project used, Apache server is used to run php files and creating fast and dynamic
web pages.

Database Engine

• MYSQL (XAMPP Server)

MySQL is use for storing all the information required to the database in sponsorship
management system. It is used for performing CRUD operation such as create, delete and
update data from the database as requested by the user.

CASE tools for Documentation

• MS Office

This is used for writing and editing the documentation of sponsorship management
system.

• [Link]

This is used to generate diagrams for system analysis and design of Online Trekking
Guide Booking system. Diagrams were created using this tool in order to save time since
all components are available with drag and drop functions.

26
4.1.2. Implementation Details of Modules

Different modules of this system are described as below

Home Page Module

The Home page of guide booking system contains information about guide, hotel, place,
about us, contact details. Further navigation from home page is handle by AJAX.

Navigation menus

• About Us

• Book Tickets

• Contact Us

• About Us

• Check PNR

• Login

Admin Module

The Airline Ticket Reservation System have been excess to admin module. No new admin
can register or join these. This module contains of these navigation menu bar, further
navigation from admin module includes

• Home

• Dashboard

• Logout

• View booked tickets for flight

• Add flight schedule details

• Delete flight schedule

27
 • Add aircraft details

• Activate and Deactivate aircraft

Customer Module

The Customer Module of Airline Ticket Reservation system have been excessing 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

Customer Module

The Customer Module of Airline Ticket reservation System have been excess 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

Login Module
In login module, we have implemented two sub modules they are admin login and
Customer login. Admin and Customer log into the system using their valid username and
password.

Register Module

In register module, we have implemented one sub modules that is customer register.
customer register into the system by entering all the details such as name, phone,

28
password, in to system with their valid username and password.

Login Module
In login module, we have implemented two sub modules they are admin login and
Customer login. Admin and Customer log into the system using their valid username and
password.
New user Module
In new user module, we have implemented one sub modules that is customer register.
Customer register into the system by entering all the details such as name, email,
password, repass word and user type required to register. And then can log in to system
with their valid username and password.
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.

User Registration

[Link]. Test Name Input Expected Actual Test

Output Output Result

1. Open [Link] Homepage Home Pass

Website page

29
 2. Enter un Full name = lhakpa Error Registratio Pass
matched password n Failed
Email=lhakpa39@[Link]
and does not Error
confirm Password=1234 match password
password does not
Conform password=1111 match

User type= user

3. Enter Full name = lhakpa Registration Registratio Pass

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

User type=
user
Table 4.1: User Registration

User Login

[Link]. Test Name Input Expected Actual Test

Output Output Result

1. Open website [Link] Home Home Pass

project Page Page

2. Enter Username Username: Login Login Pass

and Invalid lhakpa678 Failed And Failed
password 9 credential
not match

30
 is shown
Password:
12345

3. Enter Valid Username: Login Redirect to Pass

Username and lhakpa678 Successful Dashboard
Password and 9adm and redirect
click login to
Password:
dashboard
Button 12345
Table 1.2: Test case 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

Test Case 1 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

Test Case 1 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

31
Test Case for Update Airline schedule
Test Event Update Airline schedule
Test Data Like
Flight number =123
Departure = Kathmandu
Arrival= Pokhara
Date = 2:00 AM to 4:00 PM
Zet id = 234
etc.
Expected Result Airline information updated
Test Result Successfully update schedule

Table 4.5. Test case for update Airline Schedule Airline schedule

32
 CHAPTER-5
RESULT AND FUTURE RECOMMENDATION
5.1 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.

5.2. Conclusion

The Tour Guide Online System will be helpful for everyone who desires to visit
adventurous and tourist places of Nepal. In depth, its target of operation will be large
range of users including Trekkers, Guides, Translators, Helpers, and other stakeholders of
Nepal Tourism.

33
 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.

• Include the feature of report generation.

• And many Customer UI/ UX improvement

34
 REFERENCES
[1] "Airline Ticket Reservation System," February 2015.

[2] "Airline Ticket Reservation system," february 2015.

[3] S. Saiyad, "Airline Reservation System," March 16,2025.

[4] S. Saiyed, "Airline reservation system," March 16,2025.

35
 APPENDIX: SYSTEM SCREENSHOTS
Database Overview

Guide Database

Ticket details database

36
Payment Database

Home page

37
Contact us page

Pnrallcheckpage

38
39