We would like to show our sincere gratitude to supervisor Mr. Rubim Shrestha for providing continuous guidance and support throughout the project. Without his kind direction and help, this project would not have come together. In every phase of the project, he was of great help and thus has shaped this project to be completed marvelously. Completion of any project requires a great deal of cooperation between a number of people. We have taken help from several people for the preparation of this project. To them, we would like to say- thank you for spending all those hours answering our queries and providing us with the necessary sources to carry out this project. Last but not least we would like to express our appreciation to all our friends for their valuable comments and suggestion which gave up inspiration to better our project. We thank all the people for their help directly and indirectly to complete our assignment.   ABSTRACT Ghumante Firante project is a web-based project to make the travel easy and comfortable for the users right from finding the routes to till the booking of the destination places. In this project, we have two modules, Admin and user. Admin in this project has the authority to add routes, manage the users and keep the records about booking of destination places. Finally, the user will login and find the appropriate routes regarding destination places and giving details like date of journey. If the user feels any feedback need to give, she/he can provide feedback to admin.

1. A project report
On
Ghumante Firante
Submitted in partial fulfillment of the requirement of Project – IV
(BCA279CO)
Of
Bachelor of Computer Application 4th
Semester
Submitted to
Purbanchal University
Biratnagar, Nepal
Submitted By
Riya Shrestha (343311)
Rajan Mabo Limbu (343308)
Muktinath Rajbanshi (3433)
KANTIPUR CITY COLLEGE
Putalisadak, Kathmandu
Aug 8, 2022

2. A project report
On
Ghumante Firante
Submitted in partial fulfillment of the requirement of Project – III
(BCA279CO)
Of
Bachelor of Computer Application 4th
Semester
Submitted to
Purbanchal University
Biratnagar, Nepal
Submitted By
Riya Shrestha (343311)
Rajan Mabo Limbu (343308)
Muktinath Rajbanshi (3433)
Project Supervisor
Mr. Rubim Shrestha
Lecturer
KANTIPUR CITY COLLEGE
Putalisadak, Kathmandu
Aug 8, 2022

3. CERTIFICATE OF APPROVAL
This is to certify the project entitled “ Ghumante Firante ” is a project game
work carried out by the following students:
Riya Shrestha, Roll no. – ( 343311)
Rajan Mabo Limbu, Roll no. – ( 343308 )
Muktinath Rajbanshi, Roll no. – ( 3433 )
Has prepared their fourth semester project according to the regulations of
Bachelor of Computer Application course under Kantipur City College and the
students have fulfilled all the requirements for submission of the project work.
.............................
Rubim Shrestha
Project Supervisor
Department of IT
.............................
Saroj Pandey
Head of Department
Department of IT

4. i
ACKNOWLEDGMENT
We would like to show our sincere gratitude to supervisor Mr. Rubim Shrestha
for providing continuous guidance and support throughout the project.
Without his kind direction and help, this project would not have come
together. In every phase of the project, he was of great help and thus has
shaped this project to be completed marvelously.
Completion of any project requires a great deal of cooperation between a
number of people. We have taken help from several people for the preparation
of this project. To them, we would like to say- thank you for spending all
those hours answering our queries and providing us with the necessary sources
to carry out this project. Last but not least we would like to express our
appreciation to all our friends for their valuable comments and suggestion
which gave up inspiration to better our project. We thank all the people for
their help directly and indirectly to complete our assignment.

5. ii
ABSTRACT
Ghumante Firante project is an web-based project to make the travel easy and
comfortable for the users right from finding the routes to till the booking of the
destination places. In this project, we have two modules, Admin and user.
Admin in this project has the authority to add routes, manage the users and
keep the records about booking of destination places. Finally, the user will
login and find the appropriate routes regarding destination places and giving
details like date of journey.
If the user feels any feedback need to give, she/he can provide feedback to
admin.

6. Table of Content
ACKNOWLEDGMENT......................................................................................................i
ABSTRACT......................................................................................................................ii
LIST OF FIGURES........................................................................................................... iii
LIST OF TABLES............................................................................................................. iv
ABBREVIATIONS............................................................................................................ v
Chapter 1: INTRODUCTION...........................................................................................1
1.1 Background .........................................................................................................1
1.2 Problem Definition..............................................................................................1
1.3 Objectives ...........................................................................................................1
1.4 Significance .........................................................................................................2
1.5 Features ..............................................................................................................2
1.6 Team Structure ...................................................................................................2
1.7 Documentation Organization..............................................................................3
Chapter 2: Existing System Overview ...........................................................................4
2.1 System 1..............................................................................................................4
2.2 System 2..............................................................................................................4
Chapter 3: System Analysis...........................................................................................6
3.1 System development model...............................................................................6
3.2 Requirement specification..................................................................................6
3.3 Feasibility Study ..................................................................................................7
Fig 3.3 A planned Gantt chart.................................................................................10
Chapter 4: System Design and Development .............................................................11
4.1 Context Diagram and Data Flow Diagram.........................................................11
4.2 Use Case Diagram .............................................................................................13
4.3 Database Diagram.............................................................................................14
Chapter 5: System Development and Implementation..............................................15
5.1 Programming platform .....................................................................................15

7. 5.2 Operating environment ....................................................................................15
5.3 Test plan............................................................................................................15
Chapter 6: Conclusion and Future Enhancement.......................................................18
6.1 Conclusion.........................................................................................................18
6.2 Limitations.........................................................................................................18
6.3 Future Enhancement ........................................................................................18
References..................................................................................................................19
Appendices..................................................................................................................20

8. iii
LIST OF FIGURES
Figure Number Figure
Page No.
3.3 A planned Gantt chart 11
4.1.1 Context diagram 12
4.1.2 Level 1 Data flow diagram 13
4.2 Use Case diagram 14
4.4.1 ER diagram 15

9. iv
LIST OF TABLES
Table Number Table Page No.
1.6 Team Structure 2
1.7 Documentation
Organization
3
3.1 Requirement gathering
process
6
3.3.3 Schedule 10

10. v
ABBREVIATIONS
IT Information Technology
IDE Integrated Development
Environment
GUI Graphical User Interface
GB Giga Bytes

11. 1
Chapter 1: INTRODUCTION
1.1 Background
Ghumante Firante is an travelling and visiting web-based application as it has
its own history and background. Many apps like VisitGreece, Safarway,
CoTravel has been introduced to make travelling easier and comfortable.
Magellan was the first man to set off on a journey to go around the world and
also consider first traveler of the world.
Whereas tourism in Nepal started after the first successful ascent of Mount
Everest on 29th
May 1953.Tourism Sector helps made an huge impact on
economic growth of our country. Due to these apps many unexplored places
has been explored and visited too. Travelling and exploring the places has
huge impact on our history of the world.
1.2 Problem Definition
Ghumante Firante is an web-based application. The purpose of website is
established the fact that Internet users are increasing today. One of the main
purpose of the website is to facilitate the offline customer online because
customers cannot spend their precious time in markets trying to find out the
best deal.
1.3 Objectives
The main objectives of this project is
To boost the travelling and tourism provision
To make people familiar about destination place

12. 2
1.4 Significance
This program help tourism companies to manage customer regarding
to travel different places
This program can also be used for both professional and business trips.
This program helps the users to get know more about travelling places.
1.5 Features
Some features of this program are:
Manage the information about of Package, Travel Agent
Admin can track all the information of Travel Agent, Customer
Admin can edit, add, delete and update the records regarding customer
details, booking details, etc.
1.6 Team Structure
S.N Members Name Symbol
Number
Task Functions
1 Riya Shrestha 343311 Designing, Coding and Documentation
2 Rajan Mabo Limbu 343308 Designing, Coding and Documentation
3 Muktinath
Rajbanshi
343304 Designing, Coding and Documentation

13. 3
1.7 Documentation Organization
Chapters Heading Contains(Topics)
Chapter 1 Introduction 1.1 Background
1.2 Problem Definition
1.3 Objectives
1.4 Significance
1.5 Features
1.6 Team Structure
1.7 Documentation
Organization
Chapter 2 Existing System Overview System 1
System 2
Chapter 3 Software Analysis 3.1 System development
model
3.2 Requirement
specification
Chapter 4 System Development and
Implementation
4.1 System Architecture
4.2 Context Diagram
4.3 Use Case Diagram
4.4 Sequence Diagram
4.5 Activity Diagram
4.6 Class Diagram
4.7 Database Diagram
4.8 UI/ UX mechanisms
Chapter 5 Conclusions 5.1 Conclusion
5.2 Limitations
5.3 Future Enhancements

14. 4
Chapter 2: Existing System Overview
2.1 System 1
2.1.1 System 1 Introduction
Freebird, is a similar web based application that rebook cancelled or delayed
flights on any airline.It helps to get your final destination quickly for a
business meeting, vacation, unexpected event, etc. The freebird application
definitely had been a source of huge inspiration to the team. So the team had
an idea to develop a travel related web based application.
2.1.2 Pros
Smooth
Low system requirement
Saving and loading system available
2.1.3 Cons
Black and white mode only
Outdated graphics
2.2 System 2
2.2.1 System 2 Introduction
Destination on Googles, is one of the greatest web based application
available on multiple platforms from pc to android phones. It makes easier to
travel and explore the world. Every google is getting smarter and also getting
updated. This app helps to explore any cities or places like a local. Freebird
made the team consider this web-based application as the second system

15. 5
choice. The modern art web-design bring inspiration on the team’s project
design.
2.2.2 Pros
Helps to manage our trips, vacations in a smart ways
Helps to explore the places
2.2.3 Cons
Higher system requirements
Confusion occurs when we try to visit many places at the same time
Very large size file

16. 6
Chapter 3: System Analysis
3.1 System development model
SDLC is a continuous process, which starts when a decision to launch the
project is made and ends at the moment of its complete removal from the
exploitation. As in this project, we follow the SDLC model to complete the
development of project by using the steps like planning and requirement
analysis, System Design, Coding, Implementation, Testing, Deployment,etc.
3.2 Requirement specification
3.2.1 Functional Requirements
Requirement
No.
Requirement Name Requirement
description
Process of
gathering
Function
number
1 Order.php Class helps to
order the
location.
Discussion 1
2 Index.php Helps to read
the
location,location
menu and
categories
Team
Discussion
2
3 Footer.php Functions that
allow the footer
section
Prototyping 3 and 4
4 Update_admin.php Helps to cover
cover all the
information of
the system.
Discussion 5

17. 7
5 Category.php Helps to flow
out the location
name in menu.
Team
Discussion
6
3.2.2 Non function requirements
Nonfunctional requirements studies were made focusing on the following
points
Usability
This program is designed in Php for user friendly environment and
ease of use.
Reliability
This program should provide a reliable environment to both users and
admin.
Admin should be able to upload delete update new packages without
any error.
Availability
This program should be available for 24 hours because it offers nation-
al tourists reserved packages for visting places.
Database Security
An unauthorized person cannot access the panel and database, donot
read and write the information.It should maintain the security of the
client’s information.
3.3 Feasibility Study
The purpose of this feasibility research was to address the problem of web de-
velopment. Relevant factors such as economic, technical, schedule were taken
under consideration to ascertain the likelihood of completing the project suc-
cessfully. Various solutions were suggested and the team took the responsibil-

18. 8
ity to discern the pros and cons of those undertakings and chose the model that
best matched their skillset and end goal.
3.3.1 Technical Feasibility
The technical issue usually raised during the feasibility stage of the investiga-
tion includes the following:
Does the necessary technology exist to do what is suggested?
Can the system be upgraded if developed?
Are there technical guarantees of accuracy, reliability, ease of access and data
security?
As the above requirements can be fulfilled in proposed projects technically.
So, the proposed project is technically feasible.
3.3.2 Economic Feasibility
A system can be developed technically and that will be used if installed must
still be a good investment for the organization. In the economical feasibility,
the development cost in creating the system is evaluated against the ultimate
benefit derived from the new systems. Financial benefits must equal or
exceed the costs. The system is economically feasible. It does not require any
additional hardware or software.

19. 9
3.3.3 Schedule
Activity Start Week End Week
Communication 18/04/2022 23/04/2022
Planning 25/04/2022 04/05/2022
Design 08/05/2022 28/05/2022
Development 26/04/2022 01/07/2022
Testing 28/04/2022 04/07/2022
Deployment 04/07/2022 06/07/2022
Project was completed within the allocated time. Project deadline was set
accordingly so that it matched our skill set. Functions were divided among
team members and each of the members were able to come within a week of
margin of error and submit their respective tasks on time.

20. 10
Date
2021
Oct Nov Dec Jan Feb
Task
Planning
Designing
Coding
Testing
Implementatio
n
Evaluation
Documentation
Fig 3.3 A planned Gantt chart

21. 11
Chapter 4: System Design and Development
4.1 Context Diagram and Data Flow Diagram
Fig 4.1.1 Context diagram of Ghumante Firante

22. 12
Fig 4.1.2 Level 1 Data flow diagram of Ghumante Firante

23. 13
4.2 Use Case Diagram
Fig 4.2 Use case diagram

24. 14
4.3 Database Diagram
4.3.1 ER diagram
Fig 4.4.1 ER diagram of Ghumante Firante

25. 15
Chapter 5: System Development and Implementation
5.1 Programming platform
Programming platform use for this project was Html, Css programming
language as front end and Php, My Sql programming language as back end.
5.2 Operating environment
Minimum Requirement for the system to run
Software: Windows 7 and above
Hardware:
CPU: Intel Pentium 4
RAM: 1 GB
Storage: 200 MB
5.3 Test plan
Since this program is really long there was a lot of trial and error required to
make sure that bugs were removed and the program was made completely
function
5.3.1 Introduction
Waterfall methodology was used to create the program. And unit testing,
integration testing, and system testing were conducted to ensure their proper
risk management.

26. 16
Objective of Testing
Some objectives of testing project were
 Ensure the Application Under Test conforms to functional and non-
functional requirements
 Ensure the complete system performed as per the main objective of the
project
 Bugs/issues are identified and fixed before final submition
5.3.2 Testing Methodology
Firstly, the main data types were distinguished for the application. Then those
were divided up for the team members to work on, and properly all the
separate units were incorporated into the main projects. Each team member
tested their own part of the code in the context of the whole application. And
hence this approach allowed for the bugs to be solved relatively quickly. Then
finally integration process was carried out and the whole unit was tested at
once.
Finally, system testing was conducted to ensure that the program was working
as a well-rounded complete package. The functionality was tested from end-
to-end before submitting the program for presentation.

27. 17
Bug Trials
The goal of the trial is to
 To define the type of resolution for each bug
 To prioritize bugs and determine a cluster defects
5.4 Implementation and result analysis
After multiple iterations with all the bugs eradicated finally the following windows
was created.
Fig 5.4.1
Fig 5.4.2
Fig 5.4.3

28. 18
Chapter 6: Conclusion and Future Enhancement
6.1 Conclusion
This web application was successfully created and stored all the travel admin
tourism packages booking, creation managing and tour details into the
database using this application. The application was tested very well and the
errors were properly debugged. Testing also concluded that the performance
of the system is satisfactory. All the necessary output is generated. This system
thus provides an easy way to automate all the functionalities of consumption.
If this application is implemented in few consumption, it will be helpful.
6.2 Limitations
User cannot booked until they register and login in the system. User must have
a little bit knowledge or familiar about the system. User cannot customized the
packages.
6.3 Future Enhancement
In the future, team wants to add mapping system to find new places to
visit.
Package can be customized according to the user’s requirement.
System can be introduced through online process.

29. 19
References
Basseda, R.: Planning with Transaction Logic. Ph.D. thesis, StonyBrook, NY, USA (2015)
Bart´ak, R., Zhou, N.: Using tabled logic programming to solve thepetrobras planning
problem. TPLP 14(4-5), 697–710 (2014)
https://www.altexsoft.com/blog/non-functional-requirements/
Young, R. R. (2002, 9 12). Recommended requirements gathering practices. CrossTalk
15.4, p. 1.

30. 20
Appendices