Tribhuvan University

Faculty of Humanities and Social Sciences

AIRLINE TICKET RESERVATION SYSTEM

A PROJECT REPORT

Submitted to

Department of Computer Application

Thames International College

Old Baneshowr, Kathmandu

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

Submitted by

Lhakpa Chirring Sherpa [45002071]

Himani Waiba [45002069]

June, 2025

Under the Supervision of

Avinash Maskey
 Tribhuvan University

Faculty of Humanities and Social Sciences

Thames International College

Old Baneshowr, Kathmandu

Bachelor in Computer Applications (BCA)

SUPERVISOR’S RECOMMENDATION

I hereby recommend that this project prepared under my supervision by Lhakpa

Chhiring Sherpa and Himani Waiba entitled “Airline Ticket Reservation System” in
the Partial Fulfillment of requirement for the degree of Bachelor in Computer Application
is recommended for that final evaluation.

Avinash Maskey

Project Supervisor

BCA Department

Thames International College

2
 Tribhuvan University

Faculty of Humanities and Social Sciences

Thames International College

Old Baneshwor, Kathmandu

Bachelor in Computer Applications (BCA)

LETTER OF APPROVAL

This is certify that this project prepared by Lhakpa Chhiring Sherpa and Himani Waiba
entitled “Airline Ticket Reservation System” in the Partial Fulfillment of requirement for
the degree of Bachelor in Computer Application has been evaluated. In our opinion it is
satisfactory in the scope and quality as a project for the required degree.

Pesal Rai Bhoj Raj Joshi

Supervisor Program Coordinator

BCA Department Thames International College

Thames International College

Pesal Rai

Internal Examiner ExternalExa

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

i
 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
Online Ticket Reservation System (OTRS), 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 my 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 my special gratitude and thanks to our BCA Program Coordinator
Mr. Bhoj Raj Joshi 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, we 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.

Yours sincerely

Lhakpa Chhiring Sherpa

Symbol Number: 45002071

Himani Waiba

Symbol Number:
ii
 TABLE OF CONTENTS

ABSTRACT .......................................................................................................................................... i
ACKNOWLEDGEMENT ....................................................................................................................... ii
TABLE OF CONTENTS ....................................................................................................................... iii
CHAPTER -I ........................................................................................................................................ 1
INTRODUCTION ................................................................................................................................ 1
CAPTER-II .......................................................................................................................................... 4
BACKGROUND STUDY AND LITERATURE REVIEW ............................................................................ 4
2.2.1. Proposed Solution: ..................................................................................................... 5
CHAPTER–III ...................................................................................................................................... 6
SYSTEM ANALYSIS AND DESIGN ....................................................................................................... 6
3.1. System Analysis ..................................................................................................................... 6
Figure 3.1: Waterfall Methodology for Airline Ticket Reservation System .............................. 6
3.1.1. Requirement Identification ................................................................................................ 7
Figure 3.2: Use case Diagram ................................................................................................... 9
i. Technical ....................................................................................................................... 11
ii. Operational ................................................................................................................... 11
iii. Economic Feasibility ...................................................................................................... 11
vi. Schedule Feasibility ....................................................................................................... 12
Table 3.3: GANTT CHART ........................................................................................................ 13
Figure 3.4: ER diagram............................................................................................................ 14
Figure 3.5: DFD Level 0 ........................................................................................................... 15
Figure3.6: DFD Level 1 ............................................................................................................ 16
Figure 3.7: DFD Level 2.1 ........................................................................................................ 17
Figure 3.8: DFD Level 2.2 ........................................................................................................ 18
3.2.1. Architectural Design ..................................................................................................... 19
System Flow Chart .................................................................................................................. 19
Figure 3.9: Flowchart for Customer........................................................................................ 20
Figure 3:10: Flow Chart for Admin ......................................................................................... 21

iii
3.2.4. Physical DFD ......................................................................................................................... 25
Figure: Physical Dfd ...................................................................................................................... 27
3.3 Algorithm details .............................................................................................................. 27
CHAPTER-IV .................................................................................................................................... 29
IMPLEMENTATION AND TESTING................................................................................................... 29
4.1. Implementation ................................................................................................................... 29
Login Module .......................................................................................................................... 32
New user Module ................................................................................................................... 32
CHAPTER-VI .................................................................................................................................... 36
RESULT AND FUTURE RECOMMENDATION.................................................................................... 36
5.1 Lesson Learnt / Outcome ...................................................................................................... 36
• Problem Solving Skills .................................................................................................... 36
• Writing Skills .................................................................................................................. 36
• Manage time ................................................................................................................. 36
5.2. Conclusion ........................................................................................................................... 36
5.2. Future Recommendations ............................................................................................. 37
REFERENCE ..................................................................................................................................... 38
Bibliography.................................................................................................................................... 38
APPENDIX: SYSTEM SCREENSHOTS ................................................................................................ 39

iv
v
 CHAPTER -I

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 Online 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
1.2. Problem Statement

The contemporary challenge in the airline industry lies in streamlining the booking and
management of flight tickets. The current system aims to address this by providing a
centralized platform for customers to effortlessly search, book, and manage their flight
reservations. Simultaneously, it offers airline administrators tools to efficiently manage
flight schedules, seat availability, and ticketing operations.

2
1.3 Objective

• 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

3
 CAPTER-II

BACKGROUND STUDY AND LITERATURE REVIEW

2.1. Background Study

A customer will be given easy and simple UI to customize their request or responses. This
system will be designed to deliver the safe and responsive query processing and travel
results.

The major component of the system will be created as admin panel where a System owner
will be able to support, suggest, report, add schedule flight and remove any information
from the system.

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

From the wikipedia Airline reservation systems incorporate airline

schedules, fare tariffs, passenger reservations and ticket records. An airline's
direct distribution works within their own reservation system, as well as
pushing out information to the GDS. The second type of direct distribution
channel are consumers who use the internet or mob ile applications to make
their own reservations. Travel agencies and other indirect distribution channels
access the same GDS as those accessed by the airline reservation systems, and
all messaging is transmitted by a standardized messaging system that fun ctions
on two types of messaging that transmit on SITA's high level network (HLN).
These messaging types are called Type A [usually EDIFACT format] for real

4
time interactive communication and Type B [TTY] for informational and
booking type of messages. Message construction standards set by IATA and
ICAO, are global, and apply to more than air transportation. Since airline
reservation systems are business critical applications, and they are functionally
quite complex, the operation of an in -house airline reservation system is
relatively expensive.[1]

According to the one click it solution the advantages of airlines reservation are Mobile-
friendly interface for easy access, Transparent refund policies, Domestic and international
booking system support, Unified API integration with multiple travel product providers,
Customizable airline booking system development, Reliable implementation and support,
Quick and efficient one-way, round-trip, and multi-city flight bookings, Single-point-of-
contact for all airline reservation needs, Multiple language and currency support, Time and
cost-efficient airline reservations system, Detailed flight information display,24/7
customer support via chat and phone, Secure online payment gateway integration, Real-
time promotions and discounts, Advanced filtering and sorting options, automated ticket
delivery via email, Multi-user access with integrated backend ERP, Seamless PNR
management and ticket issuance, Integration with multiple airline reservation systems
(GDS), Special deals and travel promotions, Enhanced travel experience for B2B and B2C
customers.[2]

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.

5
 CHAPTER–III

SYSTEM ANALYSIS AND DESIGN

3.1. System Analysis

This system is designed with the series of processes starting with requirement analysis,
design, implementation, testing and maintenance. 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: Waterfall Methodology for Airline Ticket Reservation System

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

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

8
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

9
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

10
3.1.2. Feasibility Study

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

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

iii. Economic Feasibility

iv. 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).

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

11
vi. 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.

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

JAN (15-30) Requirement Analysis

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

MAR (01-30) Coding & Testing of Algorithm.

APR (01-14) Implementation and Module Testing

MAY (15-30) System Integration Testing

JUN (1-30) System Debugging and Maintenance

JULY Project Submission

12
GANTT Chart

TIME MILESTONES

S
Tasks JAN JAN FEB FEB MAR
N

(1-14) (15-30) (1-10) (11-30) (1-15)

Problem
1
Definition

2 Analysis

3 System Design

4 Development

5 System Testing

6 Finalization

7 Documentation

Table 3.3: GANTT CHART

13
3.1.3. Data Modeling (ER- Diagram)

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.4: ER diagram

14
3.1.4 Process Modeling

Data Flow Diagram of Airline Ticket Reservation System consists of three levels of DFD
context diagram and level one and two dfd. Both these levels are used for making data flow
diagram of ATRS.

Data Flow Diagram: level 0

Figure 3.5: DFD Level 0

15
DFD Level 1

Figure3.6: DFD Level 1

16
DFD Level two

Figure 3.7: DFD Level 2.1

17
Figure 3.8: DFD Level 2.2

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

System Flow Chart

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

19
For Customer

Figure 3.9: Flowchart for Customer

20
For Admin

Figure 3.10: Flow Chart for Admin

21
3.2.2. Database Schema 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.

22
3.2.3. Interface Design (UI Interface / Interface Diagram)

Interface design is used to design how the Airline Ticket Reservation 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 Airline Ticket Reservation System are shown below:

23
24
25
3.2.4. Physical DFD

26
 Figure: Physical Dfd

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.

27
28
 CHAPTER-IV

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. We
also define headers, paragraphs, links, and images of sponsor management 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

Online Trekking Guide Booking System, JavaScript is used for client-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 .

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

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

30
4.1.2. Implementation Details of Modules

Different modules of this system are described as below

Home Page Module

The Home page of Airline Ticket Reservation System contains information about guide, hotel,
place, about us, contact details. Further navigation from home page is handle by AJAX.

Navigation menus

• Home

• Book Tickets

• About Us

• Contact us

• Check PNR

• Login

Admin Module

The Admin Module of Airline Tickets 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

31
 • 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

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.

32
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

Table 4. 1: Test case for User Registration of Airline Ticket Reservation System.

[Link]. Test Name Input Expected Actual Test

Output Output Result
1. Open [Link] Pass
Homep Homep
Website
age age
2. Enter un Full name = lhakpa Error Registration Pass
matched Email=lhakpa39@[Link] passw Failed Error
and Password=1234 ord password
confirm Conform password=1111 does does not
password User type= user not match
match
3. Enter Full name = lhakpa Registration Registration Pass
matched Email=lhakpa39@[Link] successful successful
and Password=1234
confirm Conform password=1234
password User type=
user

33
User Login

Table 4. 2: Test case for User Login of Airline Ticket Reservation System.

[Link]. Test Name Input Expected Actu Test

Output al Resu
Outp lt
ut
1. Open website [Link] Home Page Ho Pass
me
project
Pag
e
2. Enter Usernam Login Failed Logi Pass
Username and e:lakpa And credential n
Invalid Password not match Fail
password : 12345 is shown ed

3. Enter Valid Usernam Login Successful Redirect Pass

Username e: lhakpa and redirect to to
and Password dashboard Dashboa
Password : 12345 rd
and click
login
button

34
4.2.2. Test Cases for System Testing

In system testing, whole system is tested as below:

Test Case for Active/ Deactivate

Table 4. 3: Test Case for active and deactivate of Airline Tickets Reservation System

Test Case 1 Active/ Deactivate

Test Event
Click on Accept Button

Expected Result A new plan is created

Test Result Activate

Test Case for ticket booked by user

Table 4. 4: Test Case for ticket booked by user of Airline Tickets Reservation System

Test Case 1 Request Accept user

Test Event Click on accept-on

Expected Result A new user created

Test Result Successfully user created
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

35
 CHAPTER-VI

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 Airline Ticket Reservation System will be helpful for everyone who desires to book
ticket from online by using their smart phone or laptop. In depth, its target of operation will
be large range of users including Trekkers, Guides, Translators, Helpers, and other
stakeholders of Nepal Tourism.

36
5.2. 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 are:

• Adding the feature of seat booking systems.

• Include the feature of report generation.

37
 REFERENCE

Bibliography

[1] G. o. Nepal, "About Trekking Permit," 19 November 2019. [Online]. Available:

[Link]

[2] wildyak, "IS THE TREKKING GUIDE MANDATORY?," 8 March 2023. [Online].
Available: [Link]

[3] S. Tamang, "Nepal Everest Himalaya Hiking," 23 May 2019. [Online]. Available:
[Link]

[4] R. B. Pahari, "Himalayan Journey Trek Expedetion," 16 Janauary 2001. [Online]. Available:
[Link]

38
 APPENDIX: SYSTEM SCREENSHOTS

Database Overview

Guide Database

User Database

39
Contact database

Hotel database

40
Plcaces Database

Plan database

41
Home page

Guide

42
Offers

Places

43
44
 Contact us

About us

45
The team

info

46
Admin

Admin Dashboard

47
48
Accept and Reject Category

49