Processing Document

Tribhuvan University
Faculty of Humanities and Social Sciences
Janamaitri Multiple Campus

Kuleshwor - Height, Kathmandu
A PROJECT REPORT on
“TOUR AND TRAVEL TICKET BOOKING SYSTEM”
Submitted To
Department of Computer Application
JMC
In partial fulfillment of the requirements for the Bachelors in Computer Application
Submitted by :-
Sujata Thapa
T.U Reg. no: 6-2-263-28-2020
Suman Gyawali
T.U Reg. no: 6-2-263-29-2020
BCA 4th Semester, II Year

On The Supervision Of
Kamal Tamrakar
i
TRIBHUVAN UNIVERSITY
JANAMAITRI MULTIPLE CAMPUS

Kuleshwar, Kathmandu, Nepal
SUPERVISOR’S RECOMMENDATION
I hereby recommend that this project prepared under my supervision by SUJATA THAPA
6-2-263-28-2020 And SUMAN GYAWALI 6-2-263-29-2020 entitled title of the project
“TOUR AND TRAVEL TICKET BOOKING SYSTEM” in partial fulfillment of the
requirements for the degree of Bachelor of Computer Application is recommended for the
final evaluation.
Name of the supervisor

Kamal Tamrakar
Department of Math And ICT
Kuleshwar-Height, Kathmandu
ii
TRIBHUVAN UNIVERSITY
JANAMAITRI MULTIPLE CAMPUS

Kuleshwar, Kathmandu, Nepal
LETTER OF APPROVAL
This is to certify that this project prepared by SUJATA THAPA, 6-2-263-28-2020 And
SUMAN GYAWALI, 6-2-263-29-2020 entitled title of the project is “TOUR AND
TRAVEL TICKET BOOKING SYSTEM” in partial fulfillment of the requirements 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.
SUPERVISOR HOD/ Coordinator

Kamal Tamrakar Kamal Pathak
Head of Math And ICT Department
Kuleshwor-Height, Kathmandu
Kuleshwor-Height, Kathmandu
INTERNAL EXAMINER
EXTERNAL EXAMINER
Name:
Name:
Date:
Date:
iii
Ref No:
Date:
SUBJECT: APPROVAL OF PROJECT PROPOSAL
The project entitled “TOUR AND TRAVEL TICKET BOOKING SYSTEM” proposed
by SUJATA THAPA, 6-2-263-28-2020 And SUMAN GYAWALI, 6-2-263-29-2020 for
the
partial fulfillment of the requirement for Bachelor in Computer Application (BCA), 4 th
semester has been approved for further development.
Proposal Evaluation Committee
1. _______________________
2. _______________________
3. _______________________
4. _______________________
Mr. Bholanath Ojha
iv
ABSTRACT
This project (Online Ticket) “Tour and Travel Ticket Booking System” is a web based
application which provides the information about all the tickets of various package of
visiting place to the customer. It helps to customer for booking the tickets without any
trouble disturbance and problem at a short period of time. Any customer can easily book
the tickets through the online. This application takes the all information of travelers and
visitors which processes and generates booking the various services package which are
available to the agency. In this system, two modules is present, one is admin and another
is customer or visitors. The admin module is accessed and collects all the details and
information about the travelers and visitors by this system and hold that data for their
services. This system is based on PHP and we used MySQL for the database purpose.
Keyword: PHP, MySQL
v
ACKNOWLEDGEMENT
We are the students of BCA 4th semester of Janamaitri Multiple campus in the BCA. We
have to do minor project work in this semester for practical work so we can easily
develop the web base website as its part as a project. We are so glad to present our project
(Online Ticket) “Tour And Travel Ticket Booking System” which is implementation of
our study in real life with a practical knowledge.
We express special thanks to our project supervisor Kamal Tamrakar for his valuable and
great support and guidance in all the happening regarding to the project. We are also
express special thanks to BCA coordinator Kamal Pathak for his encouragement and
guidance throughout the project.
We are indebted to the department of Information and Technology for providing support
to add on out venture. At last we would like to express special thanks to our teacher and
college member who have been directly and undirectly the part of this project and
support us and views during the entire development time.
vi
TABLE OF CONTENTS
SUPERVISOR’S RECOMMENDATION……………………………………..…….…..ii
LETTER OF APPROVAL……………………………………………………..….……..iii
APPROVAL OF PROJECT PROPOSAL……………………………………...……...…iv
ABSTRACT……………………………………………………..……………...…….…..v
ACKNOWLEDGEMENT……………………………………………………………….vi
TABLE OF CONTENT………………………………………………………..………..vii
LIST OF FIGURES……………………………………………...…………………….…ix
LIST OF TABLES………………………………………………………………....………x
LIST OF ABBREVIATION…………………………………………………..…………..xi
CHAPTER 1: PROJECT INTRODUCTION
1.1. Introduction …………………………….……..………………….....……...........1
1.2. Problem statements…………………………….………………...…..…………...1
1.3. Project objectives …………………………………………….….…….…………2
1.4. Scope and limitation…………………...………………………..…….…..……...2
1.5 Report organization…………………………………………….…….…….....…..2
CHAPTER 2: BACKGROUND STUDY AND LITERATURE REVIEW
2.1. Background study ……………………………………………………………….3
2.2 Literature review………………………...........…………...……………………...3
CHAPTER 3: SYSTEM ANALYSIS AND DESIGN
3.1. System analysis …………………………………....……..………………………5
3.1.1 Requirement analysis………………….............………………………………7
3.1.2 Feasibility analysis………..………………………....………………….
……..10
3.1.3 Data modeling (ER-Diagram)…………………….……...………..………….11
3.1.4. Process modeling (DFD)……………………….……...………..……………13
3.2 System design…………………………………………….……..…...………..….14
3.2.1 Architectural design………………………………...…………...……...….…14
3.2.2 Database scheme design ……….……………………..…………………..….15
3.2.3 Interface design……………………………………………………………….18
vii
3.2.4. Physical DFD………………………………………………………………...20
CHAPTER 4: IMPLEMENTING AND TESTING
4.1 Implementation………...………………….……………………………..……….22
4.1.1 Tools used…………………………………..………..……………………….22
4.1.2 Implementation details of modules …………………………..…………...….22
4.2. Testing………………………………………………………………….………..24
4.2.1 Unit testing…………………………………………………….……………..24
4.2.2.Test cases for system testing…….…………………………….………....….29
CHAPTER 5: CONCLUSION AND FUTURE RECOMMENDATIONS
5.1. Lesson learnt / outcome…………….……………………………………..…….30
5.2 Conclusion………………………………………………………………..………30
5.3 Future recommendation ………………..………...………………………………30
REFERENCE……………………………………………………...…………………….32
APPENDICES
viii
LIST OF FIGURES
Figure 3.1: Waterfall Model of Tour and Travel Ticket Booking System………..…...…6
Figure 3.2: Use Case Diagram of Tour and Travel Ticket Booking System…...……..….9
Figure 3.3: Gantt-Chart of Tour and Travel Ticket Booking System………………..…..11
Figure 3.4: ER Diagram of Tour and Travel Ticket Booking System………………..….12
Figure 3.5: Context – Diagram of Tour and Travel Ticket Booking System…..……......13
Figure 3.6: Level 1 DFD of Tour and Travel Ticket Booking System…………………..14
Figure 3.7: Architectural Design of Tour and Travel Ticket Booking System ………….15
Figure 3.8: Database Schema Design of Tour and Travel Ticket Booking System…......16
Figure 3.9: Home page mockup of Tour and Travel Ticket Booking System…….…..…19
Figure 3.10: All package mockup of Tour and Travel Ticket Booking System……...… 19
Figure 3.11: Admin panel mockup of Tour and Travel Ticket Booking System…...…...20
Figure 3.12: Level 0 Physical DFD of Tour and Travel Ticket Booking System ……....21
Figure 3.13: Level 1 Physical DFD of Tour and Travel Ticket Booking System…….…21
Figure 4.1: Login Admin Test Case of Tour and Travel Ticket Booking System……….25
Figure 4.2: Created New User and Save On User Database of TTTBS……………...…26
Figure 4.3: Check Login Credentials Valid User Name and Password of TTTBS...........26
Figure 4.4: New Package Is Added and Show On Database of TTTBS……………...…27
Figure 4.5: View Available Package and Book of TTTBS…………………………..….27
Figure 4.6: Send Inquiry from User of TTTBS…………………………….…….……....28
ix
LIST OF TABLES
Table 3.1: Database Tables of Tour and Travel Ticket Booking System……………..…16
Table 4.1: Test Cases for Unit Testing of Tour and Travel Ticket Booking System…....24
x
LIST OF ABBREVIATIONS
CSS : Cascading Style Sheets

DFD : Data Flow Diagram
ER : Entity Relationship
HTML : Hypertext Markup Language
PHP : Hypertext Preprocessor
RDBMS : Relational Database Management System
SQL : Structured Query Language
TTTBS : Tour and Travel Ticket Booking System
UML : Unified Modeling Language
xi
Tour And Travel Ticket Booking System
CHAPTER 1: PROJECT INTRODUCTION
1.1 Introduction
The term „Travel and Tourism‟ is used to describe a group of industries and organization
whose sole purpose is to help the travellers and tourists have their dream vacation. The
"Tour And Travel Ticket Booking System" has been developed to control the various
problems which are facing in the ticket counter of travelling agency. This system is
supported to the users and travelling agency on the process of booking tickets as per users
required. We offer tour and travel services including only ticket bookings, holiday tour
packages, and domestic tour packages. We provide the most suitably designed as well as
the customized travel packages to the customers. This system has designed for the users
who are facing various problems at the ticket booking time.
This system provide services in almost each and every city of our country Nepal. This
system is user friendly, any users can easily operate the system without help of others.
This system helps to user for save their time. It works fast, reliable and error free. In this
system there contain only two module one is users and another is admin. The user should
register at first to the system then only can login to the system. Any users can easily
choose various tour package for book which are available in the system as per their
required.
Only the admin will control the system. Admin can easily register the various tour
package in the system with details. Admin easily update the tour package and confirm the
booking package by the users with the help of this system.
1.2 Problem Statements

In the situation of our county Nepal. There are generating various problems day to day on
the tourism sectors. This system helps to solve the following problems. People do not want
to wait in a queue for getting ticket.People do not able to take the enough information
about the tour package in details. People do not have enough time for reach any travel
agency counter to get ticket. Sometimes they are in queue for book ticket and at last they
are not able to book the ticket easily due to the various problems such as few number of
1
tickets in the ticket counter. People are also facing others problems at the process of
booking the ticket.
1.3 Project Objectives

The main focus and purpose in developing this project are given below.
• To make easier way to book the ticket of any available package.
• To provide services more traveller at a time.
• To give the proper service for visitors and travellers through the system.
• To provide fast and easier services to the travelers.
1.4 Scope and Limitation

Scope
• Provide service properly to the travelers as their required.
• Know the details information of tour package which are available on the system.
• Reduce various problems which are show at ticket booking time at ticket counter.
Limitation
• The admin can only approve to the visitors and travelers package.
• The traveller must register and login to take the services.
• The admin can only update the package.
1.5 Report Organization
In Chapter 1 we have included Introduction, Problem Statement, Objectives, Scope and

limitation, Report organization of our system.
In Chapter 2 we have discussed on background study, literature review and Existing

system.
In Chapter 3 we have discussed about Analysis, Data modeling, System design structure
and requirement analysis of the system will be discussed and sequence diagrams along
with use E-R and DFD diagram, Physical DFD, Software architecture design, database
design, interface design and how system works is explained.
2
In this Chapter 4 system implementation and testing techniques are described and lists all
the system testing performed in this phase of the project.
In “Chapter 5” we discussed about outcome of the system, conclusion and future

recommendations of project in the system.
CHAPTER 2: BACKGROUND STUDY AND LITERATURE

REVIEW
2.1. Background Study

Worldwide, there has been a significant progress in the tourism areas. However, in terms
of Nepal, we are still a little behind in this specific area. To extend tour and travel this
system will play significant role in our country. In previous days people have to wait in a
long queue to get services. To solve this problem this system “Tour and Travel Ticket
Booking System” is a one of the perfect. Day by day people have facing various problems
to get services easily. It is web based system so any visitors can easily and comfortable
access then take the various services without the help of any third person at any time with
error free and disturbance. It will help for manage the tour packages. Users can book
different package easily and comfortable without the help of any third person at any time.
2.2. Literature Review

This section consists of the literature study for the booking online ticket for tour and travel
easily by the other organization and ticket seller. Many other organizations are using this
type of system for the booking the tour and travel ticket easily without any problems. We
study other similar projects and their documents which are done by other researcher on
that projects document they design the system for booking online ticket for the services
provides to each and every user. [2] Every user can easily take the services as their
required and need. They have easily able to use the system without any failure of system.
We were also using these types of system for the better accuracy within less time than
before. They take services of ticket booking as their suitable package and where they
wants to visit among the tour package which are available on the system. This system can
be used any from any where to take service easy and secure.
3
Review
By the using this modern technology and knowledge of data we expect more easier way
to handle our problem in lesser time. We are also capable to give the more service to the
customer in short period of time with the using this technology. The traditional way of
ticket booking process is so much tedious one and time consuming too. We are giving the
services to our customers for their facility where they want to go for travels and enjoy at
various beautiful places. We are also deciding the suitable price for their services with
various tour packages. Each and every users were able to take the services easily without
any problems by the use of our system. We hope that all the our traveller are satisfying by
our services and suggest us for further progress.
Existing System
Before the technology introduced the Existing system is all manual and should be done
with large human efforts and also time consuming too. Enhancement of Technology
changes the manual pattern into computerized way to booking the ticket for different tour
and travel. After the development of technology, many advance systems are developed
world wide but in the context of our country limited travel agency has introduced online
ticketing system. Many online Ticket Reservation System website like Planyo.com,
Ticketing System Online.com also running their business. Our system also little bit similar
to their systems but our system is more user friendly, attracting interface and more easy to
use and understand. Every people can easily reach our system and there is no delay in data
transfer. So that our system optimize data on real time.
4
CHAPTER 3: SYSTEM ANALYSIS AND DESIGN
3.1. System Analysis

In this system analysis, all the important data for system has been collected on the
available records and information for design the system. In this system analysis we have
decided about the system working performance for a given structure of this system and
how the system is behave with users and admin? System has studied detail at the current
situation. We have studied others developing existing system in details and site
observation was used for this system.
Software Development Life Cycle

In this Tour and Travel Ticket Booking System, waterfall model has been used for
development the system easily and comfortable then well known all the requirement and
familiar to the technology.
Waterfall Model
We has been use waterfall model for developing this system. There was already collected
the essentials requirement, prepare documentation and well understood the technology
used in this system development. So that this model was one of the perfect for developed
this system. We have cleared understand of the final deliverable of this system so this
waterfall model is perfect for this system. We have already collected all the requirement
and detailed manner so that we don't need to reiterate to the previous stage of this
stystem.
Waterfall model picture is shows the project management step and all phases which are
included the development of this system.
5
Figure 3.1: Waterfall Model of Tour and Travel Ticket Booking System
Requirement analysis: In this phase various requirements were collected by doing other
researches, developed system and previously existing system. According to this collection
of all the requirement were checked and filtered by analyzing the requirement then
checked those requirement were suitable or not and unsuitable requirements were discard.
System design: In this phase system structure has designed for the further activities. At
first the requirement documentation was studied clearly and the system architecture was
designed with the help of those requirement documentation. Activities like Use case,
Database Schema Design, UI Design, DFD, ERD and many more were performed.
Implementation: In this stage, requirement document and system design was transformed
into set of program and program units. At the first time all the small parts of system were
developed and code and those small parts were integrated into bigger modules with
connection and linked with each.
6
System Testing: In this phase all the modules were integrated together to form a system
and tested as a complete system to ensure that the software requirements have meet. All
the parts and modules were working perfectly and whole system was tested step by step.
All the units developed in the implementation phase are integrated into a system after
testing of each unit the system. The error and bugs which were appear in the system
checked and fixed them perfectly.
System Deployment: In this phase after the functional and non-functional testing was
done, the product is deployed in the customer environment or released into the market.
The deployment phase includes installation, migration, and support of the complete
system to the user or customer environment.
System Maintenance: The system was installed and put into practical use. Maintenance
involves correcting errors which were not discovered earlier stages of the system develop,
improving the implementation of system units and enhancing the system‟s services as
new requirements are discovered.
3.1.1. Requirement Analysis
In this phase, we have visit and research lots of websites and applications. All of those
system has same working concept and principle. The entire essential requirement for the
system development were collected and decided that which requirement is embedded and
which was discard from the system. [3]
3.1.1.1. Functional Requirement

There are a lot of software requirements specifications included in the functional
requirements of the Tour and Travel Booking System, which contains various process.
The functional requirements for user and system administrator are listed below on points.
7
For users / Booking package.
• The system should allow customers to booking package.

• The system should record customer personal details (for example, first name, last
name, contact number).
• The system should display available package.
• The system should allow space for customer feedback.
For System Administrator
• The system should allow the system administrator to add or delete package.
• The system should allow the system administrator to login and logout from the system
• The system should allow the system administrator to update customer request.
Use Case Diagram
In this system given use case diagram shows what kinds of activities every users and
admin conducts in the system. The most important elements in this system are users and
admin. In this system at first Login must be performed in order to access the features of
their respective modules. so all the user must create account and login. Users can see the
details of available package on the system. Users send request for booking the package
and the admin confirm the booking. The admin are allowed to cancel or confirmed the
request of user. Both user and admin can update their profile.
The basic model element of Use Case Diagram is:
Users: A user represents a role (someone) that directly interacts or uses the system.
Admin: An admin represents a role that directly interacts and controls the whole system.
Association: An association describes the relationship between an actor and a business
use case in the use case diagram.
Use Case: A use case was a functionality of how the system works, it describes the
interaction between an user and the admin with system.
8
Figure 3.2: Use Case Diagram of Tour and Travel Ticket Booking System
3.1.1.2. Non-Functional Requirement
There are a lot of software requirements specifications included in the non-functional

requirements of the Tour And Travel Booking System, which contains various process.
The non-functional requirements for the system are listed below on points.
Security: Our system encrypts the password so that unauthorized person cannot read the
password.
Regulatory: Our system must obey all the governmental requirements and constraints.
Performance: Our system performs well in different scenarios for give the suitable
service to visitors.
Usability: Our system has attractive and user friendly interface.
Service ability: If any issue arises in our system then our team will handle the problem
easily.
9
Environmental: Our system is web based and responsive so it does not required any
advance environment. It can run in any device which supports the browser.
3.1.2 Feasibility Analysis

Feasibility study is one of the essential activities that need to be carried out in system
engineering process. In this analysis we have analysis about various factors and activities
which were facing by the system in the external environment with users and people. In
this phase we observe this system uses of technology, people can easily familiar to this
system or not. Costing of the system and complete developed each and every parts and
module of system as shown in the project schedule time duration.
3.1.2.1. Operational Feasibility

For the development simple technologies are used. Any users and personal can easily use
this system any time without any disturbance. System is user-friendly. Moreover, the
requirements are not compromised so the system is feasible for every user.
3.1.2.2. Technical Feasibility

In order to design this system, used simple and easier existing technologies, software and
hardware were used. There is no used any advance technology to build this system. This
system can easily run any machines supporting windows and internet services.
3.1.2.3. Economic Feasibility

In the process of developed this system there is no use any advance technology and extra
software, hardware. In the implementation phase of this system only open source
technologies and software were used. So, there is no highly cost other than just the internet
connection and labor cost which are used for develop this system.
10
3.1.2.4. Schedule Feasibility

This system is developed using well familiar and daily using technology. This system
project is completed in actual schedule time. So there is no doubt about the finishing the
project.
GANTT CHART
In this chart of project schedule there is divided the whole project in different time
schedule in the phases of project developing. From this time schedule we were clear about
the whole activities of this project.
What are the various activities of project?

When each activity begins and ends?
How long each activity is taken scheduled time to last?
Figure 3.3: Gantt-Chart of Tour and Travel Ticket Booking System
In the developing time for this system, various requirements were collected for this system
and the requirements were analyzed for 7 days. For the next month, various activities
related to system design such as database design, data modeling, process modeling and
many more were performed. The designs were implemented into a working system in
another 2 weeks. The system was then tested for any bugs and errors for another week.
3.1.3. Data Modeling (ER -Diagram)
11
In this system, there are seven different entities namely: tblusers, tblbooking, tblenquiry,
tblpackage, tblpages, tblissues, and admin. The tblusers has various entities including:
fullname, password, emailid, mobilenumber and many more..tblpages has various
attributes including: id, type, detail.then. tblenquiry has also various attributes including:
id, fullname, description, subject etc. and tblpackage also included attributes: packageid,
packagename, packageprice, packagelocation etc. tblbooking also has attributes
including: packageid, todate, comment etc. tblissues has attributes included: id, useremail,
issue etc. and admin has attributes included: id, username, password, etc this types of
entity and their attributes are involve in this system which are releated with each other
and make a relationship among.
ER Diagram on this project document for the database design and know the details
information about whole system database working structure and system manufacture. This
diagram also used for know the details relationship between the entity and their relation
and connection with their attributes with explain the system for our users and end users
easily.
Figure 3.4: ER Diagram Figure of Tour and Travel Ticket Booking System
12
3.1.4. Process Modeling (DFD)
This is the context diagram of Tour and Travel Ticket Booking System, where the system
have elaborated the high level process of online ticket booking. It‟s a basic overview of
the whole online ticket booking system or process being analyzed or modeled. In this
diagram
we have three different entities users, admin and package of the system. At first both users
and admin login in the system than user books the different tour package which are
available in the system. Admin was updated the different tour package with details on the
system.
Figure 3.5: Context – Diagram of Tour and Travel Ticket Booking System
This is the first level diagram of Tour and Travel Ticket Booking System. In this diagram
we have entities: users, admin and package details. At first users and admin registered and
log in to access the services of system. In this system users can easily checks the tour
package and detail information from system which are store in the package database. In
13
the system user can books the tour package as per their required. Users can easily checks
the tour schedule from the system. Admin add tour package and update the detail
information of tour in system. Admin can manage the booking package and confirmation
which is booked package by the users in the system. Admin confirmed the tour schedule
and the place on the description of available package of tour in the system.
Figure 3.6: Level 1 DFD of Tour and Travel Ticket Booking System
3.2. System Design
In this design we were designed the whole structure of the system for further processing.
In this system design the architecture of the system, database schema, interface and the
physical DFDs were designed completely. Each of those phases are explained below:
14
3.2.1. Architectural Design
In this design at first time the system is start and user can easily visit the website. After
the visit website user register then login to the system. If there has already created login
account then user can directly enter to the system with login otherwise create the new
account then easily access the system. If the users enter the system then user can see the
package which are available in the system and book the package as per their required.
System admin enter the system then admin can update the tour package and control the
whole system. All the details of tour package and user information is stored in the system
database.
Figure 3.7: Architectural Design of Tour and Travel Ticket Booking System
3.2.2. Database Schema Design
Following database tables are included in the database schema of the Tour And Travel
Ticket Booking System: users, inquery, rate_review, systeminfo, package, booklist and
15
admin. In this schema design every database structure of system and the detail
information of the system database was detailed through database scheme design
diagram and database tables details.
Figure 3.8: Database Schema Design of Tour and Travel Ticket Booking System
Table 3.1: Database Tables of Tour and Travel Ticket Booking System
tblusers Database Table Structure:

Entity Description
id (int) – Primary Key Id for the user.
FullName (varchar) Enter the fullname of the user.
16
MobileNumber (char) Enter the mobilenumber of the user.
EmailId (varchar) Enter the emailid of the user.
Password (varchar) Enter the password of the user.
admin Database Table Structure:

Entity Description
id(int) – Primary Key Insert Id
UserName (varchar) Enter username.
Password (varchar) Enter password.
tblbooking Database Table Structure:

Entity Description
PackageId(int) – Primary Key Insert Id
UserEmail (varchar) Enter useremail
FormDate (varchar) Enter form date
ToDate (varchar) Enter todate
Comment (mediumtext) Enter comment
tblpackage Database Table Structure:

Entity Description
PackageId(int) – Primary Key Insert Id
PackageName (varchar) Enter package name
PackageType (varchar) Enter package type
PackageLocation (varchar) Enter package location
PackagePrice (int) Enter package price
17
PackageFeatures (varchar) Enter package features
PackageDetails (meduimtext) Enter package details
Packageimage (varchar) Insert package image
tblenquiry Database Table Structure:

Entity Description
FullName (varchar) Enter the name
EmailId (varchar) Enter the email
MobileNumber (char) mobilenumber
subject (varchar) Enter the subject
Description (mediumtext) Insert descriprion
tblissues Database Table Structure:

Entity Description
UserEmail (varchar) Enter useremail
Issue (varchar) Enter issue
Description(mediumtext) Enter description
tblpages Database Table Structure:

Entity Description
type (varchar) Enter type
detail (longtext) Enter detail
3.2.3. Interface Design
18
During Interface Design, different wireframe designs were created for the system. Figma
was used as a mockup tool during the interface design. Various mock-ups designed for the
interfaces of Tour And Travel Ticket Booking System are shown below:
Figure 3.9: Home page mockup of Tour and Travel Ticket Booking System
19
Figure 3.10: All package mockup of Tour and Travel Ticket Booking System
Figure 3.11: Admin panel mockup of Tour and Travel Ticket Booking System
3.2.4. Physical DFD
In this level 0 the physical DFD of Tour and Travel booking system, where we have
elaborated the high level process of online ticket booking. This is a basic overview of the
whole online ticket booking system. We have designed the whole physical structure of this
system. In the system there are two external entities one is Customer and another is admin.
At first customer has registered on system then enter on system. Both admin and customer
easily login system. Customer can easily view tour package and book the package
available on system. Admin can check the booking details and give response to customers.
Admin also update the detail information about tour package and control the whole system
easily.
20
Figure 3.12: Level 0 Physical DFD of Tour and Travel Ticket Booking System
In this level 1 physical DFD of Tour and Travel booking system, where we have
elaborated. At first users have been register in the system and entered the system after
login. Users have easily view tour package which are available on system then user asked
for book package to booking system and system provide package to customer for book the
package. Admin has login to the system for control the system. Admin have easily update
the details for different tour package on the description box of package.
21
Figure 3.13: Level 1 Physical DFD of Tour and Travel Ticket Booking System
CHAPTER 4: IMPLEMENTING AND TESTING
4.1. Implementation
The system has been implemented using the following programming languages.[4] These
include SQL for creating database and relation structures, PHP, laravel, bootstrap for
creating codes that link the forms to the database, HTML and CSS for designing and
styling the interfaces. Visual Studio Code also has been used for the code editor for the
system. [9]
4.1.1 Tools Used

In this project the following technologies have been used:
Operating systems : Windows 10 or Above
Technology [Front-End] : HTML , CSS , JAVASCRIPT, BOOTSTRAP
22
Technology [Back-End] : PHP

Code Editor : Visual studio code.
Database : MySQL
Tool : Visual studio code.
Server : Xampp apache server
4.1.2 Implementation Details of Modules
Registration module
In the Registration module, user has to register himself/herself to the system. His/her
personal information which gets store in data base which are using as backend. By
registering himself user have get his login id and Password so that he have access to the
system.
Admin module
The admin module manages the whole project .this includes sub modules such as admin
login module, user module, register module, and tour package status module. The admin
has the power to administer both the front end and back end of the device.
User modules
The customer has accessed the details on the website in this module and can also apply for
package booking accommodation. The user must log in to the registration system.
Users can only access the front end of the platform.
This includes sub modules such as knowledge module, login module, communication
module, registry modules, and package booking modules.
Login Module
Each user must perform login in order to access the services of the system. The Login
module detects each user automatically as the concept of groups has been used in the
23
system. Users login is detected as a user's automatically and admin login is detected as a
admin in the system.
Packages Module
In this package module admin registered the various tour packages in details. Admin
update the tour packages which are available in the system. Users can easily view the
packages and book the tour package as per users required.
Booklist Module
In this module all the booking packages of tours by users are stored in the database of
system with the details information of user and tour packages. Admin control the booking
request while booking recorded in stored in the system's database. The pending situation
of tour package is shown until admin do not confirmed that booking status.
4.2. Testing
4.2.1. Test Cases for Unit Testing
In the testing phase following tests were done.
Table 4.1: Test Cases for Unit Testing of Tour and Travel Ticket Booking System
S.N Unit Test Test Expected Test Evidence Results

Result Outcomes
1 Login Check Admin Invalid Test 1.1 Pass
admin login name or Details
credentials password
for valid does not
admin match
name and
password
2 Create a New user Created Info Test 2.1 pass
new user created new user successfully
save on submited
database
24
3 Login the Check User name Invalid Test 3.1 Pass

user login or password Details
credentials does not
for valid match
username
and
password
4 Add New Add the New successful Test 4.1 Pass
Package new package is
package added and
show on
database
5 View & View the Book Successful Test 5.1 pass
Book available request
Package package successfully
and Book sent
6 Send Inquiry Inquiry Successful Test 6.1 pass
inquiry send send to the
from user admin page
25
TEST
EVIDENCES 1.1
Unit Test: Login admin
Test: Check Login credentials for valid admin name and password Expected
Result: incorrect user name or password.
Figure 4.1: Login Admin Test Case of Tour and Travel Ticket Booking System
TEST EVIDENCES 2.1

Unit Test: Create a new user
Test: New user created
Expected Result: Created new user and save on user database.
26
TEST
Figure 4.2: Created New User and Save On User Database of TTTBS
EVIDENCES 3.1
Unit Test: login the user
Test: Check Login credentials for valid user name and password
Expected Result: Incorrect Credentials
Figure 4.3: Check Login Credentials For Valid User Name and Password of TTTBS
27
TEST
TEST EVIDENCES 4.1
Unit Test: Add New Package
Test: Add the new package
Expected Result: New package is added and show on database.
Figure 4.4: New Package Is Added and Show On Database of TTTBS
EVIDENCES 5.1
Unit Test: View & Book Package
Test: View the available package and Book
Expected Result: Book request successfully sent
Figure 4.5: View Available Package and Book of TTTBS
28
TEST
TEST EVIDENCES 6.1
Unit Test: Send inquiry from user
Test: Inquiry send
Expected Result: Inquiry send to the admin page
Figure 4.6: Send Inquiry from User of TTTBS
29
4.2.2. Test Cases For System Testing
At the last after the complete development of the whole system, then the system was
tested in various stages. The tests were performed in the system testing phase are given
below in points.
• Navigation between pages was tested.
• Registration for users and admin was tested.
• View the available package on system and Book tested.
• Inquiry send from the users tested.
• New package added in the system tested.
System Evaluation
The system was used for a few days which was followed by evaluation. Our friends were
asked to use the Tour and Travel Ticket Booking System and to fill in the questionnaire in
order to obtain feedback and to assess the whole system.
Assume that you have to book available Tour package. You are visiting our system Tour
And Travel Ticket Booking System. Please execute the following tasks:
• Register
• Login to the website
• Navigate throughout the website
• Set up your profile
• Book the tour package
• Send the review about the system
• Logout
In conclusion, we believed that the outdated manner in which many individuals must
make to give properly service to users to the development of the Tour And Travel Ticket
Booking System. We need to find ways to streamline some procedures so they take less
time, are more error-free, and are easier for users to utilize in order to stay up with the
advancement of technology.
30
CHAPTER 5: CONCLUSION AND FUTURE

RECOMMENDATIONS
5.1 Lesson Learnt / Outcome

We have learned about a lot of new concepts and technology that we were unaware of
during the implementations of this system. Various technologies that we were aware
before. At this point in the project, we also learned a lot about project management as
well as other important foundational concepts related to the field of software engineering.
We have knowledge the skills of teamwork, cooperation, and effective communication
with one another in the event of issues. This assisted us in learning how to manage
projects under pressure, time management and in a stressful setting.
5.2 Conclusion
This is to conclude that the project that we undertook was worked upon with a sincere
effort and in a fixed time schedule. Nearly all of the previously described functionalities
are present at this stage of the project. As of right now, the admin module and the user
module both function as intended. The project made here is just to ensure that this
product could be valid in today real challenging world. Here all the facilities are made
and tested, currently the system works perfectly and easily. Every user are easily take the
services from this website easily at any time.
Overall, while the management of the project will be managed properly. When the project
is completed, the users will be able to register to the website as user for booking the tour
package available in system. After successfully registering, Admin able to manage and
update tour package properly through the system and book the ticket as user required.
5.3 Future Recommendation

In future we will add a lot of new features in the future. We will be upgrade the system
with a payment module. Future improvements will be made in accordance with the
comments and ratings received from system users. Databases will be regularly updated
31
and improved. User interfaces will be improved and updated in accordance with user
requirements and technological advancements.
The probable future improvements are as follows:
• Online property registration module for lawful property transfer.

• Online payment module for partial or full settlement.
• A module that enables direct messaging with the seller.
• Upgrading and maintaining the back end.
• Upgrades to user interface.
• Performance enhancement.
• Various other page components that are updated in real time.
32
REFERENCE
[1] “Online Ticket Reservation System”, flightslogic.com [Online]. Available:
https://www.flightslogic.com/online-ticket- reservation-system.php [Accessed:
07April 2022]
[2] “Ticketing System Online”, travelopro.com [Online]. Available: Ticketing System |

Online Ticketing System | Ticketing system Online (travelopro.com) [Accessed: 10-April
2022]
[3] Software Engineering BCA/CSIT KEC publication And Distribution Pvt. Ltd.
Kathmandu Nepal (First Edition 2077) Functional & Non Functional Requirement
[Offline] [Accessed: 28-March 2022 ]
[4] Web Technology BCA/CSIT KEC publication And Distribution Pvt. Ltd. Kathmandu
Nepal (First Edition 2076) System Design & Architecture. [Offline] [Accessed:
02April 2022]
[5] “Online Booking System For Tours And Activities”, Online Tour Reservation
[Online]. Available: Online Tour Reservation and Booking System | Tour Booking Software
| Bookeo [Accessed: 27-April 2022]
[6] “Online Flight Booking System using PHP/MySQL with Source Code” Flight
Booking System [Online]. Available Online Flight Booking System using
PHP/MySQL with Source Code | Free Source Code Projects and Tutorials
(sourcecodester.com) [Accessed: 28-April 2022]
[7] “Planyo” Online reservation system [Online]. Available: Online reservation system &
booking software Planyo [Accessed: 29-April 2022]
[8] "W3Schools Online Web Tutorials" CSS Tutorials [Online]. Available: CSS Tutorial
(w3schools.com) [Accessed: 01-May 2022]
[9] "Code with harry" [Online]. Available: https://www.youtube.com/c/CodeWithHarry

[Accessed: 23-April 2022]
33
APPENDICES
Appendix 1: UI designs Screenshot
Login And Create A New Account Interface Design of Tour and Travel Ticket
Booking System
Front page interface design of Tour and Travel Ticket Booking System
Tour Package Interface Design of Tour and Travel Ticket Booking System
Admin Login Interface Design of Tour and Travel Ticket Booking System
Package Database Interface Design of Tour and Travel Ticket Booking System
Booking Database Interface Design of Tour and Travel Ticket Booking System

Processing Document

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Processing Document

Uploaded by

Copyright:

Available Formats

Tribhuvan University

Faculty of Humanities and Social Sciences

Janamaitri Multiple Campus

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

BCA 4th Semester, II Year

JANAMAITRI MULTIPLE CAMPUS

Name of the supervisor

JANAMAITRI MULTIPLE CAMPUS

SUPERVISOR HOD/ Coordinator

Proposal Evaluation Committee

Mr. Bholanath Ojha

Keyword: PHP, MySQL

CSS : Cascading Style Sheets

CHAPTER 1: PROJECT INTRODUCTION

1.2 Problem Statements

1.3 Project Objectives

1.4 Scope and Limitation

1.5 Report Organization

In Chapter 1 we have included Introduction, Problem Statement, Objectives, Scope and

In Chapter 2 we have discussed on background study, literature review and Existing

In “Chapter 5” we discussed about outcome of the system, conclusion and future

CHAPTER 2: BACKGROUND STUDY AND LITERATURE

2.1. Background Study

2.2. Literature Review

CHAPTER 3: SYSTEM ANALYSIS AND DESIGN

3.1. System Analysis

Software Development Life Cycle

3.1.1. Requirement Analysis

3.1.1.1. Functional Requirement

For users / Booking package.

• The system should allow customers to booking package.

For System Administrator

Use Case Diagram

The basic model element of Use Case Diagram is:

3.1.1.2. Non-Functional Requirement

There are a lot of software requirements specifications included in the non-functional

3.1.2 Feasibility Analysis

3.1.2.1. Operational Feasibility

3.1.2.2. Technical Feasibility

3.1.2.3. Economic Feasibility

3.1.2.4. Schedule Feasibility

What are the various activities of project?

Figure 3.3: Gantt-Chart of Tour and Travel Ticket Booking System

3.1.3. Data Modeling (ER -Diagram)

3.1.4. Process Modeling (DFD)

3.2. System Design

3.2.1. Architectural Design

3.2.2. Database Schema Design

tblusers Database Table Structure:

FullName (varchar) Enter the fullname of the user.

MobileNumber (char) Enter the mobilenumber of the user.

EmailId (varchar) Enter the emailid of the user.

Password (varchar) Enter the password of the user.

admin Database Table Structure:

UserName (varchar) Enter username.

Password (varchar) Enter password.

tblbooking Database Table Structure:

UserEmail (varchar) Enter useremail

FormDate (varchar) Enter form date

ToDate (varchar) Enter todate

Comment (mediumtext) Enter comment

tblpackage Database Table Structure:

PackageName (varchar) Enter package name

PackageType (varchar) Enter package type