Company Certificate

DECLARATION

I hereby declare that the project titled Tour Destination ” is an original

piece of work carried out by me under the guidance of Prof. Mahesh
Potdar sir
All the necessary information, facts and figures contained herein has
been collected from genuine and authentic sources.
The information provided here in below is true and correct to the best of
my knowledge and belief and nothing has been falsely stated or
concealed therein.
The work has been submitted in partial fulfillment of the requirement of
degree Master of Computer Application (MCA) to Savitribai Phule Pune
University.

Autade Rutuja
Date:
Place:

1
 Index

Chapter Details Page No

No.
1 INTRODUCTION
1.1 Company Profile / Institute Profile / Client Profile 7
1.2 Abstract 9
1.3 Existing System and Need for System 10
1.4 Scope of System 12
1.5 Operating Environment – Hardware and Software 13
1.6 Brief Description of Technology Used 14
1.6.1 Operating systems used (Windows or Unix)
1.6.2 RDBMS/No Sql used to build database
(MySQL/ oracle, Teradata, etc.)
2 Proposed System
2.1 Study of Similar Systems ( If required research 18
paper can be included)
2.2 Feasibility Study 21
2.3 Objectives of System 23
2.4 Users of System 24
3 Analysis and Design
3.1 System Requirements (Functional and Non- 26
Functional requirements)
3.2 Entity Relationship Diagram (ERD) 29
3.3 Table Structure 30
3.4 Use Case Diagrams 37
3.5 Class Diagram 40
3.6 Activity Diagram 41
3.7 Deployment Diagram 44
3.8 Module Hierarchy Diagram 45
3.9 Component Diagram 46
3.10 Sequence Diagram 47

2
 3.11 Sample Input and Output Screens 48
4 Coding
4.1 Algorithms 55
4.2 Code snippets 57
5 Testing
5.1 Test Strategy 71

5.2 Unit Test Plan 74

5.3 Acceptance Test Plan 77

5.4 Test Case / Test Script 80

6 Limitations of Proposed System 83

7 Proposed Enhancements 86
8 Conclusion 88
9 Bibliography 90
10 User Manual (All screens with proper 92
description/purpose Details about validations
related to data to be entered.)

3
 Chapter 1
Introduction

4
1. INTRODUCTION

Welcome to our Tour Destination.! In this project, we will be exploring

various aspects of tours, including consumer behavior, market trends, and the
influence of technology on tracking experiences.
The “Tour Destination” is a good application for booking tickets to travel.
In old days we don’t have any technology so we should go to the nearest
retailer but now a days we no need to go anywhere we can book anything at
the same place where we are.
The Tourism System is a web based application. Global Tourism involves the
management of multitude of activities such as studying tour destination,
planning the tour, making travel arrangements and providing accommodation.
The sum of phenomena and relationship arising from the travel and stay of
Non residents. A travel Management system provide reservation facility to
there customer Maximize travel policies compliance all areas including best
fares Allowance and approval
The tourism industry plays a crucial role in the economic development of
many countries and regions worldwide. Tourism projects aim to promote and
facilitate travel, leisure, and exploration of various destinations. These projects
encompass a wide range of activities, including the development of tourist
attractions, infrastructure, accommodations, transportation, and marketing
strategies to attract visitors.
Trek and tour destination is an exciting tourism project that aims to enhance
the appeal and visitor experience of a specific destination or region. With the
goal of promoting tourism and generating economic growth, this project seeks
to create an enticing environment for travelers, providing them with
memorable experiences and contributing to the local community's
development.

5
 1.1 Company Profile

Name of the company : The Abhiyanta IT Solution

• Company Profile
The Abhiyanta IT Solution is a leading global technology services provider,
delivering business solutions to its customers. company founded the information
technology service provider industry more than 3 years ago. Today, as an Internet
Solution Provider, we delivers one of the industry’s broadest portfolios of information
technology services to customers in the education, manufacturing, financial services,
healthcare, communications, energy, transportation, and consumer and retail
industries, and to governments around the world. We have developed several software
ranges and today, we are taking new paths, like ERP Module, complete web and
Internet promotions, SMS API Solution Consultant and many new top features.

• What we offer
As our customers’ trusted business, we provide the best solutions for executives to
maximize return on their IT investments. Our deep industry knowledge enables us to
provide innovative ideas that help to improve productivity and security. We deliver on
our commitments, so customers can build strong relationships with us, achieve
profitable growth and win in the marketplace.

• Technology Competence
Our unique competence in various technologies enables us to deliver integrated,
scalable, robust solutions with the optimal cost/performance ratio. Our team experts
constantly conduct research on new technology products to meet the ever-growing
customer needs.

• Commitment to Quality
While retaining competitive rates we never compromise the quality of our services.
We closely monitor project activities at all development phases and guarantees defect
prevention, project risk mitigation and high quality results.
• Our Area of Expertise

6
• Web Design
• Web Page Layout Design
• GUI Component Design
• Flash movies / Animation / Intro Flash
• Web Cast & Video Streaming
• Action Scripts
• E-Brochure Design
• CSS / XSL Implementation
• Website Audit & Maintenance

7
1.2 Abstract

The tour destination project is to enhance the tourism offerings and

experiences of a specific destination while promoting sustainable development
principles. The project aims to attract more visitors, stimulate economic
growth, preserve natural and cultural assets, and foster community
engagement.
he project will employ a multifaceted approach, including destination
enhancement, infrastructure development, sustainable practices, and strategic
marketing. It will involve collaborations with local stakeholders, tourism
authorities, and community representatives to ensure inclusivity and broad
participation..
The project anticipates several positive outcomes. First, it aims to significantly
increase tourist arrivals, resulting in higher revenue from visitor expenditures
and expanded business opportunities. Second, the project seeks to create a
more attractive and accessible destination through infrastructure improvements
and preservation efforts, which will contribute to the overall visitor
experience. Third, by implementing sustainable practices, the project will
mitigate environmental impacts, conserve natural resources, and raise
awareness about responsible tourism. Finally, the project aims to empower the
local community by generating employment opportunities, fostering cultural
exchange, and supporting community development initiatives.

8
1.3 Existing System and Need for System

Existing System

 In the present system a customer has to approach various agencies to find

details of places and to book tickets. This often requires a lot of time and
effort.
 A customer may not get the desired information from these offices and
often the customer may be misguided.
 It is tedious for a customer to plan a particular journey and have it
executed properly. Managing all details of store workers manually in
paper work. The maintain of the store is to know how much stock is out
of store and how much stock is needed.
 The old manual system was suffering from a series of drawbacks. Since
whole of the system was to be maintained with hands the process of
keeping, maintaining and retrieving the information was very tedious and
lengthy.
 The records were never used to be in a systematic order. There used to be
lots of difficulties in associating any particular transaction with a
particular context. If any information was to be found it was required to
go through the different registers, documents there would never exist
anything like report generation.
 Once the records were entered it was very difficult to update these
records. The reason behind it is that there is lot of information to be
maintained and have to be kept in mind while running the business For
this reason we have provided features Present system is partially
automated (computerized), actually existing system: is quite laborious as
one has to enter same information at three different places.

9
Need for System

This system will help administration to work easily. Because of its easy access
and less time-consuming administration can get the information of the Users,
Payments, etc. They do not have to search in the paper file for the log time.
Members easily handle the system.

 To manage customer data in a better way

 To develop strong relationships with your

10
1.4 Scope of System

 The website developed based on real life & It is very helpful in business
applications
 The application is very useful and easy to use.
 The use of this System for the better services and faster processing.
 Today extremely exhausting work environment dictates that individuals
requires some joyful holiday.
 As it is website it can provide services in almost each and every city of India.

 It provides the most suitably designed as well as the customized ticket

booking as per the customers.

 The application will help to estimate the benefits and calculate the requirement
very easily

11
1.5 Operating Environment: Hardware and Software

Hardware Requirement (Minimum)

Processor : Intel i3 Processor or Above
Ram : 2 GB or Above
Hard Disk : 10 GB or Above

Software Requirement (Minimum)

Browser : Any modern Browser after I.E.5.0 Operating
System Windows XP (Service Pack 2),
Windows 7
Technology : HTML5, CSS3, JavaScript, bootstrap,
PHP
Database : MySQL

12
1.6 Brief Description of Technology Used
1.6.1 Operating systems used (Windows or Unix)
1.6.2 RDBMS/No Sql used to build database (MySQL/ oracle,
Teradata, etc.)

VISUAL STUDIO:
Visual Studio is an integrated development environment (IDE) from
Microsoft. It is used to develop computer programs including websites, web
apps, web services and mobile apps. Windows Store and Microsoft Silverlight.
It can produce both native code and managed code.
Visual Studio includes a code editor supporting IntelliSense (the code
completion component) as well as code refactoring. The integrated debugger
works as both a source-level debugger and as a machine-level debugger. Other
built-in tools include a code profiler, designer for building GUI applications,
web designer, class designer, and database schema designer. It accepts plug-
ins that expand the functionality at almost every level—including adding
support for source control systems (like Subversion and Git) and adding new
toolsets like editors and visual designers for domain-specific languages or
toolsets for other aspects of the software development lifecycle (like the Azure
DevOps client: Team Explorer).
Visual Studio supports 36 different programming languages and allows
the code editor and debugger to support (to varying degrees) nearly any
programming language, provided a language-specific service exists. Built-in
languages include C, [6] C++, C++/CLI, Visual Basic .NET, C#, F#, [7]
JavaScript, Typescript, XML, XSLT, HTML, and CSS.

HTML:
The HyperText Markup Language or HTML is the standard markup
language for documents designed to be displayed in a web browser. It defines
the meaning and structure of web content. It is often assisted by technologies
such as Cascading Style Sheets (CSS) and scripting languages such as
JavaScript.
Web browsers receive HTML documents from a web server or from local
storage and render the documents into multimedia web pages. HTML

13
describes the structure of a web page semantically and originally included cues
for its appearance.
HTML elements are the building blocks of HTML pages. With HTML
constructs, images and other objects such as interactive forms may be
embedded into the rendered page. HTML provides a means to create
structured documents by denoting structural semantics for text such as
headings, paragraphs, lists, links, quotes, and other items. HTML elements are
delineated by tags, written using angle brackets. Tags such as <img /> and
<input /> directly introduce content into the page. Other tags such as <p> and
</p> surround and provide information about document text and may include
sub-element tags. Browsers do not display the HTML tags but use them to
interpret the content of the page.

CSS:
CSS stands for Cascading Style Sheets. It is used for the designing of a
webpage. CSS is the standard and preferred mechanism for formatting HTML
pages. CSS consist of a group of formatting rules that you use to control the
layout and appearance of the content on a web page.
One of the really great feature of CSS is that you can store all the CSS rules
in one document and keep that document separate from the HTML content and
link them together.
CSS is designed to enable the separation of content and presentation,
including layout, colors, and fonts. This separation can improve content
accessibility; provide more flexibility and control in the specification of
presentation characteristics; enable multiple web pages to share formatting by
specifying the relevant CSS in a separate .css file, which reduces complexity
and repetition in the structural content; and enable the .css file to be cached to
improve the page load speed between the pages that share the file and its
formatting.

JAVASCRIPT:
JavaScript (JS) is a scripting language, primarily used on the Web. It is

14
used to enhance HTML pages and is commonly found embedded in HTML
code. JavaScript is an interpreted language.
Thus, it doesn't need to be compiled. Although it shares many of the features
and structures of the full Java language, it was developed independently. It
was originally developed by Netscape as a means to add dynamic and
interactive elements to websites.
JavaScript is a client-side scripting language, which means the source code
is processed by the client's web browser rather than on the web server. This
means JavaScript functions can run after a web page has loaded without
communicating with the server.

PHP:
PHP Stands for "Hypertext Pre-processor." PHP is an HTML-embedded
Web scripting language. This means PHP code can be inserted into the HTML
of a Web page. A lot of syntax of PHP is borrowed from other languages such
as C, Java and Perl. However, PHP has many unique features and specific
functions as well.
When a PHP page is accessed, the PHP code is read or "parsed" by the
server the page resides on. The output from the PHP functions on the page are
typically returned as HTML code, which can be read by the browser. Because
the PHP code is transformed into HTML before the page is loaded, users
cannot view the PHP code on a page. This make PHP pages secure enough to
access databases and other secure information.

MySQL:
MySQL pronounced either "My S-Q-L" or "My Sequel," is an open source
relational database management system. It is based on the structure query
language (SQL), which is used for adding, removing, and modifying
information in the database. Standard SQL commands, such as ADD, DROP,
INSERT, and UPDATE can be used with MySQL.

15
 Chapter 2
Proposed System

16
2. PROPOSED SYSTEM

Tour destination is a good website for booking tickets to travel .. The main
purpose of “Trek and tour destination” is to provide a convenient way for a
customer to book bus for tour purposes. The objective of this project is to
develop a system that automates the processes and activities of a travel agency.
In this project, We will make an easier task of searching places and for
booking bus. In the present system a customer has to approach various
agencies to find details of places and to book tickets. This often requires a lot
of time and effort. We provide approach skills to critically examine how a
tourist visits and its ability to operate in an appropriate way when dealing with
the consequences of tourism, locally, regionally, and nationally including
visitor security and ecological influences. It is tedious for a customer to plan a
particular journey and have it executed properly. The project ‘Bus Reservation
System’ is developed to replace the currently existing system, which helps in
keeping records of the customer details of destination as well as payment
received.

Admin

Admin can create Package

This page provides detailed information about each package, including
destination, duration, activities, pricing, and any additional amenities or perks
included.

Manage packages(Create ,Update)

As a package manager, you are responsible for designing and developing
attractive and marketable tour packages. Here admin create various packages.

Manage Users
Implement a user registration system where users can create accounts with
their personal information. Maintain a database of registered users and their
associated information

Manage Enquiries
Ensure that your responses to customer inquiries are clear, concise, and
address all aspects of the enquiry.

17
Use a friendly and professional tone, maintaining a positive and helpful
attitude throughout the communication.

Manage issues
Managing customer issues effectively is crucial for providing excellent
customer service and maintaining customer satisfaction in a tour project.
Manage Booking

Manage Pages
Managing pages in a tour project involves creating, updating, and
maintaining various web pages to provide information, promote tours and
services, and engage users.

Change Password
The "Change Password" feature provides users with the ability to update
their password for their account in the tour project. This feature ensures that
users can maintain the security and confidentiality of their account
information.

Admin Dashboard
An admin dashboard is a central hub within a tour project that provides
administrators with a comprehensive overview of the system's operations,
performance, and management tools.

Users:

User can register yourself.

Create a user registration form that collects necessary information from
users, such as username, email address, password, and any additional relevant
details you require.

User can log in with valid email and password.

Consider implementing validation checks to ensure data integrity, such as
verifying the uniqueness of usernames and validating the email format.

Forgot Password(user Can recover own password)

Provide a "Forgot Password" link or button on the login page.
When users click on the link, redirect them to a password reset page or initiate
a password reset process.

Tour Booking

18
Provide users with a comprehensive list of available tours, including
destinations, itineraries, and pricing.
Display high-quality images, detailed descriptions, and any special features or
inclusions of each tour.

Manage Booking
Provide a booking form where users can enter their personal details,
including name, contact information, and any special requirements or
preferences.
Include fields for the number of travelers and their details (e.g., names, ages).

Generate Ticket(Regarding Complaint)

By generating a ticket for customer complaints, you establish a structured
process for addressing and resolving issues, enhancing customer satisfaction,
and demonstrating your commitment to resolving concerns in your tour
project.

Change Password
The "Change Password" feature provides users with the ability to update
their password for their account in the tour project. This feature ensures that
users can maintain the security and confidentiality of their account
information.

Guest Users:

Visit the Website

Guest users can view the list of tours and packages offered on your website.
They can access details such as tour descriptions, itineraries, destinations,
pricing, and inclusions/exclusions.

Guest user can enquiry

Include a dedicated contact form on your website where guest users can
submit their enquiries.
Ask for their name, email address, subject, and a message field to gather
necessary information.

19
2.2 Feasibility Study:

The purpose of feasibility study is to investigate deeply recommended

system. Feasibility study is carried out to describe and evaluate the proposed
system. The study will justify whether the project is feasible or not and
whether it is worthwhile or not. Therefore, a Feasibility study of the proposed
system needs to be carried out in Order to,
 To provide the better understanding of the system.
 To clarify the objectives in the proposed system.
 To asses & recommend what course of action should be taken for the
solution proposed
 To describe the outputs
 There are many factors to assess while analyzing whether the proposed
system is feasible and should be adopted. These factors are ,

1. Technical Feasibility:
The technical feasibility deals with some factors such as
 Is the proposed system technically feasible?
 Is it within the state of art?
 What hardware & software will be required?
The technologies used to develop this system are already well
established and proven. The hardware & software requirements are simple.
The system is implemented as a client-server application with MySQL as the
database back end and also php as back end and html ,css and JavaScript. So,
the system is technically feasible.

2. Economic Feasibility:
Cost benefit analysis is a frequently used method for evaluating
effectiveness of the proposed system. It is important because management
must authorize the budget of the project. It determines how the aim of the
project can be achieved with limited resources.

20
 The economical feasibility is evaluated on the basis of benefits of the
proposed system. As the resources for the system like hardware and software
are already available in most of the organization, so no other overheads are
required. The benefit for the organization will overweight the cost for them.
Hence, the proposed system is economically feasible.

3. Operational Feasibility:
The Operational feasibility deals with the human factor. It checks the impact
of the proposed system on the user. Retrieval of information will be easier as
all the information will be stored in the database. The system will also be user
friendly. Thus, the proposed system is operationally feasible.

21
2.3 Objectives of Proposed System

Following are the Objectives of the proposed system,

 The primary objective of any tours and travel project is to ensure
customer satisfaction.
 This includes providing excellent customer service, creating
memorable travel experiences, and meeting or exceeding customer
expectations throughout the entire travel journey.
 Tours and travel projects often aim to promote and showcase specific
destinations or regions. The objective is to attract tourists and increase
visitor numbers by highlighting the unique attractions, cultural
heritage, natural beauty, or adventure opportunities available in the
destination.
 Generating revenue is an essential objective for tours and travel
projects. This involves attracting tourists, selling travel packages,
accommodations, transportation services, and other travel-related
products or services to generate income for the project and support the
local economy.
 Tours and travel projects often aim to expand their market reach and
attract customers from new geographical areas or target segments
 Projects in the tours and travel industry may seek to diversify their
product offerings to cater to different customer preferences and market
demands.

22
2.4 Users of System

1. Administrators:
Administrators are responsible for managing and maintaining the tours and
travels system. They ensure the system's smooth operation, oversee user
management, handle system configurations and settings, and monitor data
security. Administrators may also analyse system performance, generate reports,
and provide support to customers and travel agents. They are responsible for
maintaining the integrity and functionality of the system.

2. Customers:
Customers are the primary users of the tours and travels system. They are
individuals or groups who are seeking travel experiences, such as vacationers,
tourists. Customers use the system to search for and book various travel services,
including flights, hotels, transportation, tour packages, activities, and travel
insurance. They can customize their travel itineraries, compare prices, read
reviews and recommendations, and make online reservations or payments.
Customers may also interact with customer support services for inquiries,
assistance, or changes to their bookings.

3. Guest Users :
Guest users refer to individuals who interact with the tours and travels system
without creating an account or logging in. They are temporary users who have
limited access to certain features and functionalities of the system. Here's a
description of guest users in the context of a tours and travels system

23
 Chapter 3
Analysis and Design

24
3.1 System Requirements (Functional and Non-Functional
requirements):
Functional Requirements:
• These are the requirements that the end user specifically demands as basic
facilities that the system should offer. All these functionalities need to be
incorporated into the system as a part of the contract.
• These are represented or stated in the form of input to be given to the
system, the operation performed, and the output expected.
• They are basically the requirements stated by the user which one can see
directly in the final product, unlike the non-functional requirements.

1. User Registration and Authentication: The system should allow users to

create accounts, login, and authenticate their identities securely.

2. Search and Booking: Users should be able to search for flights, hotels,
tours, activities, and other travel services based on their preferences,
travel dates, and destinations. They should be able to select and book their
preferred options, including providing necessary travel details and making
payments.

3. Itinerary Management: The system should provide users with the ability
to manage their travel itineraries, including viewing, editing, and
canceling bookings. It should also allow users to receive notifications or
updates related to their bookings.

4. Availability and Pricing: Users should be able to check the availability of

flights, hotels, and other services for specific dates and locations. The
system should provide accurate pricing information, including any
applicable discounts, promotions, or taxes.

25
5. Payment Processing: The system should support secure and reliable
payment processing, allowing users to make online payments using
various payment methods, such as credit cards, debit cards, or digital
wallets. It should provide a seamless checkout experience.

Non Functional Requirements:

Non-functional requirements for a rental website describe the qualities and

characteristics of the system that are not directly related to its specific
functionalities but are essential for its overall performance, usability, and
security. Here are some common non-functional requirements for a rental
website:

Performance: The system should be capable of handling a large number of

concurrent users, providing fast response times and minimizing loading times
for search results, bookings, and other system functionalities.

Security: The system should ensure the security of user data, including
personal information, payment details, and travel-related information. It
should implement appropriate encryption, access controls, and data protection
measures.

Scalability: The system should be designed to accommodate increasing user

demands and scale accordingly, both in terms of user volume and system
performance.

Reliability: The system should be reliable, ensuring minimal downtime and

system failures. It should have mechanisms in place to handle unexpected
errors or disruptions.

26
User-Friendly Interface: The system should have a user-friendly and intuitive
interface, allowing users to navigate easily, make bookings without
confusion, and access relevant information quickly.

Accessibility: The system should be accessible to users with disabilities,

complying with accessibility standards and guidelines, and providing features
such as text alternatives for images, keyboard navigation, and color contrast.

Integration: The system should have the capability to integrate with external
systems, such as payment gateways, hotel booking systems, flight reservation
systems, or third-party APIs, to provide a seamless experience and access to a
broader range of services.

Compliance: The system should comply with relevant laws and regulations,
including data protection regulations, privacy laws, and industry-specific
compliance requirements.

27
3.2 Entity Relationship Diagram (ERD)

28
3.3 Table Structure

Table Name: Admin

Table Description: This Table stores admin details.
Primary Key: Admin_Id

Field Name Data Type Size Constraint Description

Admin_Id int 11 Not null Admin id no
UserName varchar 100 Not null UserName
Password varchar 100 Not null Password
UpdationDate timestamp - Null Date

Table Name: Tbluser

Table Description: This Table stores user Personal details.
Primary Key: User_Id

Field Name Data Type Size Constraint Description

User_Id int 11 Primary key User id no
Name varchar 100 Not null User name
Mobile_N o Number 10 Not null Mobile number
Email_Id varchar 50 Not null User email Id
Password varchar 50 Not null Password
Reg_Date timestamp - Not null Date

29
Table Name: TblPackage
Table Description: This Table stores package details.
Primary Key: PackageId

Field Name Data Type Size Constraint Description

PackageId int 11 Primary key Package id no
PackageName varchar 100 Not null Package name
packageLocation varchar 100 Not null Package location
PackageType varchar 50 Not null Package type
PackagePrice number 50 Not null Package price
PackageDetails text - Not null Package details
packageImagesId int 11 NotNull Loaction images
createDate date - Package create date
updateDate date - Package update date
Location varchar 100 NotNull Tour Location

Table Name: Tblbooking

Table Description: This Table stores booking details.
Primary Key: Booking_id

Field Name Data Type Size Constraint Description

Booking_id int 11 Primary key Booking id
Packageid int 11 Not null Packageid
useremail varchar 50 Not null User email
fromdate varchar 50 Not null Starting date
Todate varchar 50 Not null End date
comment text - Not null Comment
Regdate timestamp - Not null Registration date
status varchar 50 Not null Status confirm/cancle
Cancleby varchar 50 Not null Cancelled by name
Updationdate timestamp - Not null Updation date

30
Table Name: Tblissues
Table Description: This table store the user issue details raised by the user.
Primary Key: User_Id

Field Name Data Type Size Constraint Description

User_Id int 11 Primary key User id no
Email_Id varchar 50 Not null User email Id
Issue varchar 50 Not null User issue
Description text - null Issue details
PostingDate timestamp - Not null Posting date
AdminRemark text - Not null Admin solution
RemarkDate timestamp - Not null Solution date

31
Table Name: Tblenquiry
Table Description: This table store the user enquiry details
Primary Key: cid

Field Name Data Type Size Constraint Description

Cust_Id int 11 Not null User id no
Name varchar 100 Not null User name
MobileN Number 10 Not null User mobile number
o
EmailId varchar 50 Not null User email id
Subject varchar 50 Not null Enquiry Subject
Description text - Not null Enquiry Details
PostingDate timeStamp - Enquiry date
Status varchar 50 Status

Table Name: Tblpages

Table Description: This table store the website pages details.
Primary Key: sub_cat_id

Field Name Data Type Size Constraint Description

Page Id int 11 Primary key Page id no

Type varchar 50 Not null Page name

Details text - Not null Page Details

32
Data Dictionary

Sr. Field Name Description Data Constraits Table

No. Type Name
1 Admin_Id Admin id no int Not null Admin
2 AdminRemark Admin solution text Not null tblissues
3 Bookingid Booking id int Primary tblbooking
key
4 cancleby Cancelled by name varchar Not null tblbooking
5 comment Comment text Not null tblbooking
6 createDate Package create date date tblPackage
7 Description Issue details text null tblissues
8 Description Enquiry Details text Not null tblenquiry
9 Email User email id varchar Not null tblissues
10 Emailid User email id varchar Not null tbluser
11 Emailid User email id varchar Not null tblenquiry
12 fromdate Starting date varchar Not null tblbooking
13 Id User id no int Primary tblissues
key
14 Id User id no int Primary tblenquiry
key
15 Issue User issue varchar Not null tblissues
16 Location Tour Location varchar NotNull tblPackage
17 MobileN o User mobile Number Not null tbluser
number
18 MobileN o User mobile Number Not null tblenquiry
number
19 Name User name varchar Not null tbluser
20 Name User name varchar Not null tblenquiry

33
21 PackageDetail Package details text Not null tblPackage
s
22 packageId Package id no int Primary tblPackage
key
23 packageid Packageid int Not null tblbooking
24 packageImage Loaction images int NotNull tblPackage
sId
25 packageLocati Package location varchar Not null tblPackage
on
26 PackageName Package name varchar Not null tblPackage
27 PackagePrice Package price number Not null tblPackage
28 packageType Package type varchar Not null tblPackage
29 Page Id Page id no int Primary key tblpages
30 Password Password varchar Not null admin
31 Password Password varchar Not null tbluser
32 PostingDate Ieesue Posting date timesta Not null tblissues
mp
33 PostingDate Enquiry date timeSta Not null tblenquiry
mp
34 RegDate Date timestam Not null tbluser
p
35 regdate Registration date timesta Not null tblbooking
mp
36 RemarkDate Solution date timesta Not null tblissues
mp
37 status Status varchar Not null tblbooking
confirm/cancle
38 Status Status varchar Not null tblenquiry
39 Subject Enquiry Subjet varchar Not null tblenquiry
40 todate End date varchar Not null tblbooking
41 Type Page name varchar Not null tblpages
42 updateDate Package update date tblPackage
date
43 UpdationDate Date timesta Null admin

34
 mp
44 updationdate Updation date timesta Not null tblbooking
mp
45 useremail User email varchar Not null tblbooking
46 UserId User id no int Primary tbluser
key
47 UserName Admin UserName varchar Not null admin

35
3.4 Use case Diagrams:
1. Registration

Use case Name Registration

Actor Admin, Customer
Detail This use case diagram describe the
Description registration and login process of Admin & Customer
Pre-condition User must have a valid email id & Password for the
registration
Main Flow After the registration the both users are have their
user id & password. With the help of user id and
password they can login.

36
 Post condition All the users are get the usernames and their
Password. After login the admin can manage works.

2. Admin site Use Case

Use case Name Admin manage package

Actor Admin

Detail Description This use case diagram describes the creating

and managing package and tour
Pre-condition User must have a valid User id and
Password for the Login
Main Flow After successful login user can manage the
package, manage order, etc.
Post condition After creation the User can book package.

37
3. customer Site Use Case

Use case Name Customer book Package

Actor Customer
Detail Description This use case diagram describe the h o w u s e r
booking package
Pre-condition User must have a Password for the Login

Main flow User view all package list and book the package
payment for this booking.
Post condition After Finalizing the Estimate, the customer gives
all related booking and inquiry related details

38
 \
3.5 Class Diagram

39
3.6 Activity Diagrams

1. Login Activity

40
2. Registration Activity

41
3. Book package

42
3.7 Deployment Diagram

43
3.8 Module Hierarchy Diagram

44
3.9 Component Diagram

45
3.10 Sequence Diagram

46
3.11 Sample Input and Output Screens

Sample Input Screens

1. Home Page

2. Package Privacy

47
3. Contact Us

48
4. Enquiry

5. Admin Login

49
6. Admin Dashboard

7. Create Package

50
8. Update Package

51
Output Screens with data

1. Manage Packages

2. Manage Users

52
3. Manage Bookings

53
Chapter 4
Coding

54
4.1 Algorithms

Designing a complete algorithm for a tours and travel system would require
detailed analysis of specific requirements and functionalities. However, here is
a high-level algorithmic overview of the key steps involved in a tours and
travel system:

1. User Registration and Authentication:

- Validate user input for registration details.
- Store user information securely in a database.
- Implement authentication mechanisms for user login.

2. Search and Booking:

- Retrieve travel options (flights, hotels, tours, activities) based on user
search criteria.
- Display search results with relevant information (price, availability,
ratings).
- Allow users to select desired options and proceed to booking.
- Collect necessary travel details from the user (dates, passenger
information).
- Reserve selected services and generate booking references.

3. Itinerary Management:
- Provide users with access to their booked itineraries.
- Display booking details, including dates, times, locations, and reference
numbers.
- Allow users to modify or cancel bookings within the specified rules and
conditions.

4. Availability and Pricing:

- Maintain an up-to-date inventory of available services (flights, hotels,
tours).
- Check availability based on user-selected dates and locations.
- Calculate accurate pricing based on the chosen services, duration, and
additional options.
- Apply any applicable discounts, promotions, or taxes.

55
5. Payment Processing:
- Present the total cost to the user for review.
- Enable secure payment processing using various payment methods.
- Handle payment authorization and transaction completion.
- Generate payment receipts and update booking status accordingly.

6. Performance and Security:

- Implement efficient algorithms and data structures to ensure optimal
system performance.
- Employ security measures to protect user data, such as encryption and
secure authentication protocols.
- Regularly monitor and maintain system stability, scalability, and
availability.

7. User-Friendly Interface:
- Design an intuitive user interface that allows users to easily navigate the
system.
- Provide clear and concise instructions at each step of the booking process.
- Optimize the user experience by incorporating visual aids, tooltips, and
error handling.

8. Integration:
- Integrate with external systems, such as payment gateways, hotel
reservation systems, or flight APIs, to retrieve real-time data and provide a
seamless experience.
- Establish data synchronization and communication protocols with partners
or suppliers.

9. Compliance and Regulations:

- Ensure compliance with relevant laws and regulations, including data
protection and privacy regulations specific to the travel industry.
- Handle secure storage and handling of user data and provide mechanisms
for data removal upon user request.

56
4.2 Code snippets

Sign.php

<?php
session_start();
if(isset($_POST['signin']))
{
$email=$_POST['email'];
$password=md5($_POST['password']);
$sql ="SELECT EmailId,Password FROM tblusers WHERE
EmailId=:email and Password=:password";
$query= $dbh -> prepare($sql);
$query-> bindParam(':email', $email, PDO::PARAM_STR);
$query-> bindParam(':password', $password, PDO::PARAM_STR);
$query-> execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);
if($query->rowCount() > 0)
{
$_SESSION['login']=$_POST['email'];
echo "<script type='text/javascript'> document.location = 'package-
list.php'; </script>";
} else{

echo "<script>alert('Invalid Details');</script>";

57
}

?>

<div class="modal fade" id="myModal4" tabindex="-1" role="dialog"

aria-labelledby="myModalLabel">
<div class="modal-dialog" role="document">
<div class="modal-content modal-info">
<div class="modal-header">
<button type="button"
class="close" data-dismiss="modal" aria-label="Close"><span aria-
hidden="true">×</span></button>
</div>
<div class="modal-body modal-
spa">
<div class="login-grids">
<div class="login">
<div
class="login-left">

<ul>

<li><a class="fb" href="#"><i></i>Facebook</a></li>

<li><a class="goog" href="#"><i></i>Google</a></li>

</ul>

</div>

58
 <div
class="login-right">
<form
method="post">

<h3>Signin with your account </h3>

<input type="text" name="email" id="email" placeholder="Enter
your Email" required="">
<input type="password" name="password" id="password"
placeholder="Password" value="" required="">

<h4><a href="forgot-password.php">Forgot password</a></h4>

<input type="submit" name="signin" value="SIGNIN">

</form>
</div>
<div
class="clearfix"></div>
</div>
<p>By logging in you
agree to our <a href="page.php?type=terms">Terms and Conditions</a>
and <a href="page.php?type=privacy">Privacy Policy</a></p>
</div>
</div>
</div>
</div>
</div>

59
SignUp.php

<?php

error_reporting(0);
if(isset($_POST['submit']))
{
$fname=$_POST['fname'];
$mnumber=$_POST['mobilenumber'];
$email=$_POST['email'];
$password=md5($_POST['password']);
$sql="INSERT INTO tblusers(FullName,MobileNumber,EmailId,Password)
VALUES(:fname,:mnumber,:email,:password)";
$query = $dbh->prepare($sql);
$query->bindParam(':fname',$fname,PDO::PARAM_STR);
$query->bindParam(':mnumber',$mnumber,PDO::PARAM_STR);
$query->bindParam(':email',$email,PDO::PARAM_STR);
$query->bindParam(':password',$password,PDO::PARAM_STR);
$query->execute();
$lastInsertId = $dbh->lastInsertId();
if($lastInsertId)
{
$_SESSION['msg']="You are Scuccessfully registered. Now you can login ";
header('location:thankyou.php');
}
else
{
$_SESSION['msg']="Something went wrong. Please try again.";
header('location:thankyou.php');
}
}
?>
<!--Javascript for check email availabilty-->
<script>
function checkAvailability() {

$("#loaderIcon").show();
jQuery.ajax({
url: "check_availability.php",
data:'emailid='+$("#email").val(),
type: "POST",
success:function(data){
$("#user-availability-status").html(data);

60
$("#loaderIcon").hide();
},
error:function (){}
});
}
</script>

<div class="modal fade" id="myModal" tabindex="-1" role="dialog" aria-

labelledby="myModalLabel">
<div class="modal-dialog"
role="document">
<div class="modal-content">
<div class="modal-
header">
<button
type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-
hidden="true">&times;</span></button>
</div>
<section>
<div
class="modal-body modal-spa">

<div class="login-grids">

<div class="login">

<div class="login-left">

<ul>

<li><a class="fb"
href="#"><i></i>Facebook</a></li>

<li><a class="goog"
href="#"><i></i>Google</a></li>

</ul>

</div>

61
 <div class="login-right">

<form name="signup" method="post">

<h3>Create your account </h3>

<input type="text" value=""

placeholder="Full Name" name="fname" autocomplete="off" required="">
<input type="text" value=""
placeholder="Mobile number" maxlength="10" name="mobilenumber"
autocomplete="off" required="">
<input type="text" value="" placeholder="Email id"
name="email" id="email" onBlur="checkAvailability()" autocomplete="off"
required="">
<span id="user-availability-status" style="font-
size:12px;"></span>
<input type="password" value=""
placeholder="Password" name="password" required="">

<input type="submit" name="submit"

id="submit" value="CREATE ACCOUNT">

</form>

</div>

<div class="clearfix"></div>

</div>

<p>By logging in you agree to our <a href="page.php?

type=terms">Terms and Conditions</a> and <a href="page.php?
type=privacy">Privacy Policy</a></p>

</div>
</div>
</section>
</div>
</div>
</div>
<?php

62
session_start();
error_reporting(0);
include('includes/config.php');
if(isset($_POST['submit2']))
{
$pid=intval($_GET['pkgid']);
$useremail=$_SESSION['login'];
$fromdate=$_POST['fromdate'];
$todate=$_POST['todate'];
$comment=$_POST['comment'];
$status=0;
$sql="INSERT INTO
tblbooking(PackageId,UserEmail,FromDate,ToDate,Comment,st
atus)
VALUES(:pid,:useremail,:fromdate,:todate,:comment,:status)";
$query = $dbh->prepare($sql);
$query->bindParam(':pid',$pid,PDO::PARAM_STR);
$query->bindParam(':useremail',
$useremail,PDO::PARAM_STR);
$query->bindParam(':fromdate',$fromdate,PDO::PARAM_STR);
$query->bindParam(':todate',$todate,PDO::PARAM_STR);
$query->bindParam(':comment',
$comment,PDO::PARAM_STR);
$query->bindParam(':status',$status,PDO::PARAM_STR);
$query->execute();
$lastInsertId = $dbh->lastInsertId();
if($lastInsertId)
{
$msg="Booked Successfully";
}
else
{
$error="Something went wrong. Please try again";
63
}

}
?>
<!DOCTYPE HTML>
<html>
<head>
<title>Package Details</title>
<meta name="viewport" content="width=device-width, initial-
scale=1">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8" />
<script type="applijewelleryion/x-javascript">
addEventListener("load", function() { setTimeout(hideURLbar,
0); }, false); function hideURLbar(){ window.scrollTo(0,1); }
</script>
<link href="css/bootstrap.css" rel='stylesheet' type='text/css' />
<link href="css/style.css" rel='stylesheet' type='text/css' />
<link href='//fonts.googleapis.com/css?
family=Open+Sans:400,700,600' rel='stylesheet' type='text/css'>
<link href='//fonts.googleapis.com/css?
family=Roboto+Condensed:400,700,300' rel='stylesheet'
type='text/css'>
<link href='//fonts.googleapis.com/css?family=Oswald'
rel='stylesheet' type='text/css'>
<link href="css/font-awesome.css" rel="stylesheet">
<!-- Custom Theme files -->
<script src="js/jquery-1.12.0.min.js"></script>
<script src="js/bootstrap.min.js"></script>
<!--animate-->
<link href="css/animate.css" rel="stylesheet" type="text/css"
media="all">
<script src="js/wow.min.js"></script>
64
<link rel="stylesheet" href="css/jquery-ui.css" />
<script>
new WOW().init();
</script>
<script src="js/jquery-ui.js"></script>
<script>
$(function() {
$( "#datepicker,#datepicker1" ).datepicker();
});
</script>
<style>
.errorWrap {
padding: 10px;
margin: 0 0 20px 0;
background: #fff;
border-left: 4px solid #dd3d36;
-webkit-box-shadow: 0 1px 1px 0 rgba(0,0,0,.1);
box-shadow: 0 1px 1px 0 rgba(0,0,0,.1);
}
.succWrap{
padding: 10px;
margin: 0 0 20px 0;
background: #fff;
border-left: 4px solid #5cb85c;
-webkit-box-shadow: 0 1px 1px 0 rgba(0,0,0,.1);
box-shadow: 0 1px 1px 0 rgba(0,0,0,.1);
}
</style>
</head>
<body>
<!-- top-header -->
<?php include('includes/header.php');?>
<div class="banner-3">
65
 <div class="container">
<h1 class="wow zoomIn animated animated" data-wow-
delay=".5s" style="visibility: visible; animation-delay: 0.5s;
animation-name: zoomIn;"> Package Details</h1>
</div>
</div>
<!--- /banner ---->
<!--- selectroom ---->
<div class="selectroom">
<div class="container">
<?php if($error){?><div
class="errorWrap"><strong>ERROR</strong>:<?php echo
htmlentities($error); ?> </div><?php }
else if($msg){?><div
class="succWrap"><strong>SUCCESS</strong>:<?php echo
htmlentities($msg); ?> </div><?php }?>
<?php
$pid=intval($_GET['pkgid']);
$sql = "SELECT * from tbltourpackages where PackageId=:pid";
$query = $dbh->prepare($sql);
$query -> bindParam(':pid', $pid, PDO::PARAM_STR);
$query->execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);
$cnt=1;
if($query->rowCount() > 0)
{
foreach($results as $result)
{ ?>

<form name="book" method="post">

<div class="selectroom_top">
<div class="col-md-4 selectroom_left wow fadeInLeft
animated" data-wow-delay=".5s">
66
 <img src="admin/pacakgeimages/<?php echo
htmlentities($result->PackageImage);?>" class="img-responsive"
alt="">
</div>
<div class="col-md-8 selectroom_right wow fadeInRight
animated" data-wow-delay=".5s">
<h2><?php echo htmlentities($result-
>PackageName);?></h2>
<p class="dow">#PKG-<?php echo
htmlentities($result->PackageId);?></p>
<p><b>Package Type :</b> <?php echo
htmlentities($result->PackageType);?></p>
<p><b>Package Location :</b> <?php echo
htmlentities($result->PackageLocation);?></p>
<p><b>Features</b> <?php echo
htmlentities($result->PackageFetures);?></p>
<div class="ban-bottom">
<div class="bnr-right">
<label class="inputLabel">From</label>
<input class="date" id="datepicker" type="text"
placeholder="dd-mm-yyyy" name="fromdate" required="">
</div>
<div class="bnr-right">
<label class="inputLabel">To</label>
<input class="date" id="datepicker1" type="text"
placeholder="dd-mm-yyyy" name="todate" required="">
</div>
</div>
<div class="clearfix"></div>
<div class="grand">
<p>Grand Total</p>
<h3>USD.800</h3>
</div>
67
 </div>
<h3>Package Details</h3>
<p style="padding-top: 1%"><?php echo
htmlentities($result->PackageDetails);?> </p>
<div class="clearfix"></div>
</div>
<div class="selectroom_top">
<h2>Travels</h2>
<div class="selectroom-info animated wow fadeInUp
animated" data-wow-duration="1200ms" data-wow-
delay="500ms" style="visibility: visible; animation-duration:
1200ms; animation-delay: 500ms; animation-name: fadeInUp;
margin-top: -70px">
<ul>

<li class="spe">
<label class="inputLabel">Comment</label>
<input class="special" type="text"
name="comment" required="">
</li>
<?php if($_SESSION['login'])
{?>
<li class="spe" align="center">
<button type="submit" name="submit2" class="btn-
primary btn">Book</button>
</li>
<?php } else {?>
<li class="sigi" align="center" style="margin-
top: 1%">
<a href="#" data-toggle="modal" data-
target="#myModal4" class="btn-primary btn" > Book</a></li>
<?php } ?>
<div class="clearfix"></div>
68
 </ul>
</div>

</div>
</form>
<?php }} ?>

</div>
</div>
<!--- /selectroom ---->
<<!--- /footer-top ---->
<?php include('includes/footer.php');?>
<!-- signup -->
<?php include('includes/signup.php');?>
<!-- //signu -->
<!-- signin -->
<?php include('includes/signin.php');?>
<!-- //signin -->
<!-- write us -->
<?php include('includes/write-us.php');?>
</body>
</html>

69
 Chapter 5
Testing

5.1 Test Strategy

70
 A test strategy is an outline that describes the testing approach of the
software development cycle. The purpose of a test strategy is to provide a
rational deduction from organizational, high-level objectives to actual test
activities to meet those objectives from a quality assurance perspective. The
creation and documentation of a test strategy should be done in a systematic
way to ensure that all objectives are fully covered and understood by all
stakeholders. It should also frequently be reviewed, challenged and updated as
the organization and the product evolve over time. Furthermore, a test strategy
should also aim to align different stakeholders of quality assurance in terms of
terminology, test and integration levels, roles and responsibilities, traceability,
planning of resources, etc.
Test strategies describe how the product risks of the stakeholders are
mitigated at the test-level, which types of testing are to be performed, and
which entry and exit criteria apply. They are created based on development
design documents. System design documents are primarily used, and
occasionally conceptual design documents may be referred to. Design
documents describe the functionality of the software to be enabled in the
upcoming release. For every stage of development design, a corresponding test
strategy should be created to test the new feature sets.
Developing a test strategy involves planning and organizing the overall
approach to testing a software application or system. It includes defining the
scope of testing, determining the objectives, identifying test levels, creating
test plans, and allocating resources effectively. Here's a general outline of a
test strategy:
Define Test Objectives: Clearly establish the goals and objectives of the
testing process. These objectives should align with the overall project goals
and stakeholder expectations.
1. Identify Test Levels: Determine the different levels of testing required for
the application/system, such as unit testing, integration testing, system
testing, and user acceptance testing. This helps in structuring the testing
process and ensures comprehensive coverage.

2. Determine Test Techniques and Methods: Choose appropriate test

techniques and methods based on the application/system requirements and

71
 constraints. This may include functional testing, performance testing,
security testing, usability testing, etc.

Define Test Deliverables: Identify the essential documents and artifacts to

be produced during the testing process, such as test plans, test cases, test
scripts, defect reports, and test summary reports. Specify the format,
content, and review process for each deliverable.

3. Plan Test Environment and Infrastructure: Define the required test

environment, including hardware, software, networks, and any additional
tools or resources necessary for testing. Ensure that the test environment
mimics the production environment as closely as possible.

4. Establish Test Schedule and Milestones: Create a detailed test schedule

with specific milestones and deadlines for each test level. Consider
dependencies, risks, and resource availability while establishing the
timeline. Regularly track progress against the schedule and make
adjustments as needed.

5. Allocate Resources: Determine the necessary resources for testing,

including skilled testers, test automation tools, test data, and any
additional infrastructure. Assign responsibilities and roles within the
testing team, considering their expertise and availability.

6. Define Test Entry and Exit Criteria: Establish the conditions that must be
met before testing can begin (entry criteria), such as completed
development, availability of test environments, and test data. Define the
conditions that indicate the end of testing (exit criteria), such as meeting
specific quality metrics or achieving a predetermined level of test
coverage.

7. Determine Defect Management Process: Establish a clear process for

72
 reporting, tracking, prioritizing, and resolving defects. Define the roles
and responsibilities of the individuals involved in the defect management
process. Choose appropriate defect tracking tools and establish
communication channels.

8. Consider Test Automation: Evaluate opportunities for test automation and

determine which tests can be automated to increase efficiency and
effectiveness. Define the approach, tools, and frameworks to be used for
test automation.

9. Plan for Test Data: Identify the required test data for various test
scenarios and define how it will be sourced, created, and maintained.
Consider data privacy and protection requirements.

5.2 Unit Test Plan

A unit test plan outlines the approach and scope of testing at the unit level,

73
where individual components or modules of software are tested in isolation.
The goal of unit testing is to ensure that each unit functions correctly and
meets its specified requirements. Here's a template for creating a unit test
plan:

1. Test Objective:
- Clearly define the objective of unit testing, such as validating the
functionality and behavior of individual units, identifying defects, and
ensuring code quality.

2. Test Scope:
- Specify the scope of unit testing, including the components/modules to be
tested and any dependencies or interfaces that need to be considered.

3. Test Environment:
- Describe the required environment setup for unit testing, including the
hardware, software, and tools necessary to execute the tests.

4. Test Strategy:
- Define the overall approach to unit testing, including the test techniques,
methodologies, and standards to be followed. Mention any specific test
design techniques, such as equivalence partitioning or boundary value
analysis, that will be utilized.

5. Test Deliverables:
- Identify the test deliverables to be produced during unit testing, such as
test cases, test scripts, test data, and test reports.

6. Test Schedule:
- Create a timeline for unit testing activities, including milestones,
deadlines, and dependencies. Consider the overall project schedule and

74
integration points with other testing activities.

7. Test Cases:
- Specify the test cases to be executed for each unit. Include inputs,
expected outputs, and any specific preconditions or postconditions. You can
also mention any test coverage criteria, such as code coverage metrics, to be
achieved.

8. Test Data:
- Describe the test data requirements, including both valid and invalid
inputs, boundary values, and edge cases. Specify how the test data will be
generated or sourced.

9. Test Execution:
- Define the process for executing unit tests, including the steps to set up
the test environment, execute the test cases, and record the results. Mention
any specific tools or frameworks to be used for test execution.

10. Test Reporting:

- Outline the format and content of test reports, including the details to be
captured for each test case execution. Define the criteria for logging defects
and tracking their resolution.

11. Test Automation:

- Determine opportunities for automating unit tests and mention the tools,
frameworks, or scripts that will be used for test automation.

75
 12. Risks and Mitigation:
- Identify the potential risks and challenges associated with unit testing and
propose strategies to mitigate them. This may include handling dependencies,
resource constraints, or time limitations.

13. Roles and Responsibilities:

- Clearly define the roles and responsibilities of team members involved in
unit testing, such as testers, developers, and reviewers.

14. Review and Approval:

- Plan for a review of the unit test plan by relevant stakeholders to ensure
its completeness, accuracy, and alignment with project objectives. Obtain
approval before proceeding with testing.

5.3 Acceptance test plan

An acceptance test plan outlines the approach and scope of testing to be

76
conducted by end-users or stakeholders to determine whether a system or
software meets their requirements and is ready for deployment. Acceptance
testing validates the system's functionality, usability, and compliance with
business objectives. Here's a template for creating an acceptance test plan:

1. Test Objective:
- Clearly define the objective of acceptance testing, such as ensuring that the
system meets user requirements, verifying business processes, and validating
user acceptance.

2. Test Scope:
- Specify the scope of acceptance testing, including the features,
functionalities, and business processes to be tested. Identify any specific user
roles or scenarios to be covered.

3. Test Environment:
- Describe the required environment setup for acceptance testing, including
the hardware, software, data, and networks necessary to execute the tests.
Specify if the testing will be conducted on a production-like environment or a
separate testing environment.

4. Test Strategy:
- Define the overall approach to acceptance testing, including the test
techniques, methodologies, and acceptance criteria to be followed. Mention
any specific test design techniques, such as scenario-based testing or user story
testing.

5. Test Deliverables:
- Identify the test deliverables to be produced during acceptance testing, such
as test cases, test scripts, test data, and acceptance test reports. Mention any
specific documentation or sign-off requirements.

6. Test Schedule:
- Create a timeline for acceptance testing activities, including milestones,
deadlines, and dependencies. Consider the availability and schedule of end-
users or stakeholders involved in the testing process.

77
7. Test Cases:
- Specify the test cases to be executed during acceptance testing. Focus on
end-to-end scenarios, critical functionalities, and business-critical processes.
Include inputs, expected outputs, and any specific preconditions or
postconditions.

8. Test Data:
- Describe the test data requirements for acceptance testing, including
realistic and representative datasets. Specify how the test data will be
generated, anonymized if required, or sourced from production-like data.

9. Test Execution:
- Define the process for executing acceptance tests, including the steps to set
up the test environment, execute the test cases, and record the results. Mention
any specific tools or frameworks to be used for test execution.

10. Test Reporting:

- Outline the format and content of acceptance test reports, including the
details to be captured for each test case execution. Define the criteria for
logging defects or issues and tracking their resolution.

11. Test Sign-off and Acceptance Criteria:

- Clearly define the criteria and process for sign-off and acceptance of the
system. Specify the conditions under which the system will be considered
acceptable for deployment.

12. Test Training and Support:

- Identify any training or support needs for end-users or stakeholders
involved in acceptance testing. Specify the resources or documentation
provided to assist in the testing process.

13. Risks and Mitigation:

- Identify the potential risks and challenges associated with acceptance
testing and propose strategies to mitigate them. This may include handling
dependencies, resource constraints, or time limitations.

78
14. Roles and Responsibilities:
- Clearly define the roles and responsibilities of team members involved in
acceptance testing, including end-users, business analysts, testers, and project
managers.

15. Review and Approval:

- Plan for a review of the acceptance test plan by relevant stakeholders to
ensure its completeness, accuracy, and alignment with project objectives.
Obtain approval before proceeding with testing.

5.4 Test Case:

79
Test Case Preconditio Expected Actual Pass/Fail
Descriptio ns Results Results
n

Successful Successful
TC001 User login login login Pass

Invalid Invalid
credentials credentials
error error
message message
TC002 User login displayed displayed Pass

Search Search
results results
TC003 Tour search displayed displayed Pass

No search No search
results results
TC004 Tour search found found Pass

Booking Booking
confirmatio confirmati
Tour n page on page
TC005 booking displayed displayed Pass

Payment Payment
error error
Tour message message
TC006 booking displayed displayed Pass

Booking Booking
cancellatio cancellatio
Tour n n
TC007 cancellation successful successful Pass

Error Error
message message
displayed displayed
when when
canceling canceling
non- non-
Tour existent existent
TC008 cancellation booking booking Pass

Review Review
submitted submitted
successfull successfull
TC009 Tour review y y Pass
80

Error Error
message message
Chapter 6. Limitations of
Proposed System
81
Limitations of Proposed System

System has following limitations –

 With high margins and high returns, there are various limitations also
which are attached to the business of tour operators. The following points
throw light on a few of these limitations:
 High competition levels: One of the biggest limitations of tour operators
business is the high degree of competition prevailing in the industry. A
customer has various options to choose from which has increased their
bargaining power. Due to the high returns associated with the business of
tour operators, every year many entrepreneurs enter into the said industry.
It has become very difficult to establish the brand name in the said
business because of the cut throat competition that is prevalent.
 Element of Uncertainty: In the business of tour operators, everything does
not fall into the category of controllable factors. There is an element of
uncertainty attached to various things in the said business, for example
uncertainty in the airline schedules, uncertainty in weather conditions,
uncertainty in government regulations, uncertainty in hotel room

82
 availability, etc. This element of uncertainty comes brings with it a lot of
constraints.
 Stringent regulatory laws: The regulatory laws governing the tour
operators business differs from country to country. The governing laws of
many countries are very stringent and bring in a limiting factor to the
business of tour operators.
 Language constraint: Languages used differ from continent to continent,
country to country, state to state, region to region. In the business of tour
operator, one has to communicate to hotels, airlines, etc. for tie up to offer
smooth services to the customers who visit other countries in their tour.
Language becomes a constraint in many countries. One can utilize the
services of a translator but that comes for an additional cost.

 Effect of currency exchange rate fluctuations: Different currencies are

used in different countries. The tour operators business is affected by
currency fluctuations.
 Relations between countries: The political and economical relations
between two countries affect the tour operators business to a great extent.
If a country is not in good relation with the other the tourism industry is
affected to a great extent because of this relation and hence it becomes an
additional limitation for the business of tour operators.

83
84
Chapter 7. Proposed
Enhancements

Proposed Enhancements

Since system has mentioned earlier in the section of the limitations, some of
them are essential to overcome for making it better system.
No system is complete. It requires changes as and when user demands new
features.
 User must be able to change the theme of system according to his/her
liking.
 System must provide online interactive help.
 Explore and incorporate new destinations into the tours project to offer a
wider range of travel options to customers.
 This can include adding lesser-known or emerging destinations, catering to
specific niche markets, or exploring unique and offbeat experiences.
 Implement features that allow customers to personalize their travel
experiences.

85
 These proposed enhancements aim to elevate the tours project by addressing
customer needs, embracing technological advancements, and incorporating
sustainability and personalization to create a competitive and compelling
travel experience.
 It's important to prioritize enhancements based on customer feedback,
market trends, and project goals to ensure maximum impact and success.

86
Chapter 8. Conclusion

Conclusion

The project entitled “Tour Destination ” has been studied and

analyzed using various methods & then after the design and development of
this project went as per schedule and in right direction fulfilling its objectives
and goals.
The system will greatly reduce all the overheads caused by the existing
system. The use of system will surely increase the productivity.

The software used for development and documentation of the system

can satisfactorily fulfills the requirements of the company with the latest trends
in software technology. The system is developed with capacity of any other
future changes.

Though the system isn’t integrated completely, considering all aspects

of surroundings, this system works smoothly and effectively as per the
requirements.

achieving these outcomes, the shopping website project has

successfully created a user-friendly, secure, and efficient online shopping

87
platform that provides a positive and engaging experience for customers.

88
Chapter 9. Bibliography

Bibliography

 https://www.yahoobaba.net/
 https://internship.suvenconsultants.com/
 www.W3school.com
 www.mysql.com

89
90
Chapter 10. User Manual

Chapter 10. User Manual (All Screens With Proper description

/ purpose Details about validations related to data to be

entered.
Input Forms with Data

Input screen name: Home page

Description: Here Customer and admin seeing user interface of website

91
Input screen name: Privacy page
Description: this page showing iprivacy related information.

92
Input screen name: Contact Us
Description: this page showing contact details.

Input screen name: Enquiry Page

Description: customer enquiry about tours packages.

93
Input Screen name: Login Page
Description: Here Admin can login with username & password field. he login page
of our website presents a clean and user-friendly interface

Input Screen name: Admin dashboard

Description: When u logon successfully, the home page is open where You can
navigate to your main module.

94
Input Screen name: Create package
Description: Admin create new package and filling package related information .

95
Input Screen name: Create package
Description: here admin perform update operation.

96
Output Forms with Data

Output screen name: all Packages

Description: all package list showing for admin.

Output screen name: all Users

Description: all Users list showing for admin.

97
Output screen name: all Bookings
Description: all Bookings list showing for admin.

98