VIJAYS

TRAVEL MANAGEMENT SYSTEM
PROJECT REPORT
SUBMITTED TO THE MADRAS UNIVERSITY IN PARTIAL
FULFILLMENT OF THE REQUIREMENT FOR THE
DEGREE OF BACHELOR OF COMPUTER APPLICATION
BY
S. VIJAY (212100426)
K.MUTHUMANI (212100398)
Under the guidance of
Mrs. I.VASUGI, M.C.A, M.Phil.
Assistance Professor
Department of Computer Application
DEPARTMENT OF COMPUTER APPLICATION

PROF.DHANAPLAN COLLEGE OF SCIENCE & MANAGEMENT
KELAMBAKKAM
APRIL - 2024
PROF. DHANAPALAN COLLEGE OF SCIENCE & MANAGEMENT
KELAMBAKKAM
BCA - DEGREE
PROJECT REPORT
S.VIJAY - 212100426
BONAFIDE CERTIFICATE
This is to certify that this project work titled “TRAVEL MANAGEMET SYSTEM” is
done by S.VIJAY during the year 2023-2024.
This work is submitted for partial for the award of the degree of BACHELOR OF
COMPUTER APPLICATION issued by university of Madras.
PROJECT GUIDE HEAD OF THE DEPARTMENT
Submitted for the Project viva - voce held on ---------------------------
Internal Examiner External Examiner

DECLARATION
We hereby declare that the project “TRAVEL MANAGEMENT SYSTEM”. submitted by
S.VIJAY in partial fulfillment of the requirement for the degree of BACHELOR OF
COMPUTER APPLICATION course of the university of madras is a record of the project
work done by both originally.
(S.VIJAY)
ACKNOWLEDGMENT
It is my grand pleasure to acknowledge the department of computer application prof.

Dhanapalan College of Science and Management, Kelambakkam for having assigned me the
project work in TRAVEL MANAGEMENT SYSTEM.
I wish to extend my heart-felt gratitude respectful to the CHAIRMAN Mr.PUGALENDHI

DHANAPALAN , SECRETARY Mrs. Ar.AMIRTHAVARSHINI PUGALENDHI AND
PRINCIPAL Mrs. Dr.BEULAH PADMAVATHY OF PROF. DHANAPALAN
COLLEGE OF SCIENCE AND MANAGEMENT, KELAMBAKKAM for providing
necessary facilities throughout the courses.
I express profound gratitude to my project guide Mrs. I.VASUGI , M.C.A, M.Phil. for her
valuable guidance personal care encourage for completion of training report successfully.
At last but not least I would like to place on records my sincere thanks to all people who
have enable me to complete my project report successfully.
STATION : Mr. S.VIJAY

DATE :
ABSTRACT:
 The Travel Management System (TMS) is a web based application developed using PHP
and MySQL, aims at Streamline and Automate the process of managing travel-related
activities
 The system caters to both travel agencies and individual travelers,offering features for
itinerary planning,booking,and expense tracking.
 The various details of the travel relating to their User login, Sign up, Home page, My
account , contact us , All packages , shopping cart and Admin login accessed through the
respective Databases.
 The project is implemented through PHP and MySQL Programming,by writing the source
in a Code Editor such as Visual Studio Code and the code gets automatically executed in a
Runtime Environment.
TABLE OF CONTENT
CHAPTER TITLE PAGE NO

SNO
1. INTRODUCTION 1
1.1 Problem statement 3
1.2 Solution statement 3
1.3 About solution tool 3
1.4 Future scope 3
2. SYSTEM ANALYSIS 4
2.1 Existing system 5
2.2 Proposed system 5
3. REQUIREMENT SPECIFICATION 6
3.1 Hardware specification 7
3.2 Software specification 7
4. SYSTEM DESIGN 8
4.1 DFD diagram 9
4.2 Use case diagram 10
4.3 UML diagram 11
4.4 ER-diagram 13
5. IMPLEMENTATION DETAIL 16
5.1 Front end 17
5.2 Back end 19
6. TEST AND IMPLEMENTATION 21
7. SCREEN INVOLVED IN APPLICATION 33
7.1 Brief explanation about the screens 34
8. SOURCE CODE , SAMPLE SCREEN SHOT AND DATABASE 35
8.1 Source code 36-60
8.2 Sample screenshot 61-72
8.3 database 78
9. CONCLUSION 79
REFERENCES 80
CHAPTER 1
INTRODUCTION
1
Introduction:
 A Travel Management System (TMS) is a software platform that helps
companies manage their travel expenses and policies. It can help
companies track employee travel, ensure that travel is in line with company
policy, and save money on travel costs.
 It involves the management of multitude of activities such as studying

tour destination, planning the tour, making travel arrangement and
providing accommodation. It also involves marketing efforts to attract
tourists to travel to particular destinations
 A Travel Management System can use a database table to store

customer details, such as their name, description, price, and
duration. The Travel Management System can also use a database table
to store information about the people traveling on a booking, such as
their names, ages, and any special requests.
 Travel Management System can also help ensure that all data is secure
and accessible in real time.A design system is a set of standards that
help companies manage and scale design. Design systems include
reusable components, design principles, and guidelines to help achieve
consistency and efficiency across a company's digital products.
2
Problem statement :
 The purpose of website is established 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.
Solution statement :
 A travel management system is a software solution that helps travel
businesses book,track and analyze business travel.It can also refer to the
overall process of managing corporate travel.
 We provide solution by software technique.
About Solution tool :

 Travel management system are one-stop software systems where all of a
company’s travel arrangements can be handled.
Future Scope :
 In the future, TMS may use artificial intelligence (AI) to analyze data and
optimize travel for cost-effective options. AI algorithms may also provide
enhanced user experiences through personalized recommendations.
 The travel and tourism industry has a lot of potential for growth and
opportunities. The Indian Tourism sector is one of the fastest-growing
economic sectors in the country. The Government of India envisions
creating around 140 million jobs in tourism by 2030, particularly focusing
on cruise tourism, ecotourism, and adventure tourism
3
CHAPTER 2
SYSTEM ANALYSIS
4
PROPOSED SYSTEM :
 In the present system a customer has to approach various agencies to
find details of placeman 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
EXISTING SYSTEM :
 The proposed system is a web based application and maintains a

centralized repository of all related information.
 The system allows one to easily access the relevant information
and make necessary travel arrangements

 Users can decide about places they want to visit and make
bookings online for travel and accommodation
5
CHAPTER 3
REQUIREMENT SPECIFICATION
6
Hardware specification:
 The most common set of requirements defined by any operating
system or software application is the physical computer resources, also
known as hardware. compatibility and sometimes incompatible
hardware devices for a particular operating system or application. The
following sub-Section discuss the various aspects of hardware
requirements.
Hardware requirement for present project:
Processor : AMD PRO A4-4350B R4, 5 COMPUTE CORES

2C+3G 2.50 GHz
Ram : 4GB
Hard disk : 500 GB

Software specification:
 software Requirements deal with defining software resource
requirements and per- requisite that need to be installed on a computer
to provide optimal functioning of an application.
 These requirements or per-requisites are generally not included in
the software installation package and need to be installed
separately before the software is installed.
software requirement for present project:
Operating system : windows 10 pro
Front end : HTML, CSS, JAVASCRIPT
Back end : PHP

Data base : MySQL
7
CHAPTER 4
SYSTEM DESIGN
8
DATA FLOW DIAGRAM:
 A data flow diagram is graphical tool used to describe and analyses movement of
data through a system. These are the central tool and the basis from which the other
components are developed. The transformation of data from input to output,
through processed, may be described logically and independent of physical
components associated with the system. These are known as the logical data flow
diagrams.
DFD SYMBOLS:
Process that transforms data flow
Source of destination of data
Data flow
Data store
9
USE CASE DIAGRAM:
 A use case diagram is a graphical depiction of a user's possible interactions with a

system. A use case diagram shows various use cases and different types of users the
system has and will often be accompanied by other types of diagrams as well. The
use cases are represented by either circles or ellipses. The actors are often shown as
stick figures.
Applications
 While a use case itself might drill into a lot of detail about every possibility, a use-
case diagram can help provide a higher-level view of the system. It has been said
before that "Use case diagrams are the blueprints for your system". Due to their
simplistic nature, use case diagrams can be a good communication tool for
stakeholders. The drawings attempt to mimic the real world and provide a view for
the stakeholder to understand how the system is going to be designed. Siam and Lee
conducted research to determine if there was a valid situation for use case diagrams
at all or if they were unnecessary. What was found was that the use case diagrams
conveyed the intent of the system in a more simplified manner to stakeholders and
that they were "interpreted more completely than class diagrams". The purpose of a
use case diagram is to capture the dynamic aspect of a system. They provide a
simplified graphical representation of what the system should do in a use case. Further
diagrams and documentation are needed for a complete functional and technical
outlook on the system.
10
UML Diagram:
 It represents the flow of the data in the application and by analyses this, one is able
to understand the system completely, by graphical representation such as circle,
rectangle, square etc. It allows us to get what you want.
User :
11
Admin :
12
ER DIAGRAM :
 An Entity Relationship (ER) Diagram is a type of flowchart that illustrates how
“entities” such as people, objects or concepts relate to each other within a system. ER
Diagrams are most often used to design or debug relational databases in the fields of
software engineering, business information systems, education and research. Also
known as ERDs or ER Models, they use a defined set of symbols such as rectangles,
diamonds, ovals and connecting lines to depict the interconnections of entities,
relationships and their attributes. They mirror grammatical structure, with entities as
nouns and relationships as verbs. ER diagrams are related to data structure diagrams
(DSDs), which focus on the relationships of elements within entities instead of
relationships between entities themselves. ER diagrams also are often used in
conjunction with data flow diagrams (DFDs), which map out the flow of information
for processes or systems.
Uses of entity relationship diagrams :
1) Database design: ER diagrams are used to model and design relational databases, in terms
of logic and business rules (in a logical data model) and in terms of the specific technology to
be implemented (in a physical data model.) In software engineering, an ER diagram is often an
initial step in determining requirements for an information systems project. It’s also later used
to model a particular database or databases. A relational database has an equivalent relational
table and can potentially be expressed that way as needed.
2) Database troubleshooting: ER diagrams are used to analyse existing databases to find and
resolve problems in logic or deployment. Drawing the diagram should reveal where it’s going
wrong.
3) Business information systems: The diagrams are used to design or analyzing relational
databases used in business processes. Any business process that uses fielded data involving
entities, actions and interplay can potentially benefit from a relational database. It can
streamline processes, uncover information more easily and improve results.
13
4) Business process re-engineering (BPR): ER diagrams help in analyzing databases used in
business process re-engineering and in model a new database setup.
5) Education: Databases are today’s method of storing relational information for educational
purposes and later retrieval, so ER Diagrams can be valuable in planning those data structures.
14
15
CHAPTER 5
IMPLEMENTATION DETAILS
16
IMPLEMENTATION DETAILS
In this Section we will do Analysis of Technologies to use for implementing the project.
5.1 FRONT END
5.1.1 HTML
 Hypertext Markup Language (HTML) is the standard markup language for

documents designed to be displayed in a web browser. It can be 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 describes the
structure of a web page semantically and originally included cues for the appearance
of the document.
 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> surround and provide information about document text and may
include other tags as sub-elements. Browsers do not display the HTML tags, but use
them to interpret the content of the page. HTML can embed programs written in a
scripting language such as JavaScript, which affects the behaviour and content of web
pages. Inclusion of CSS defines the look and layout of content. The World Wide Web
Consortium (W3C), former maintainer of the HTML and current maintainer of the
CSS standards, has encouraged the use of CSS over explicit presentational HTML
since 1997.
17
5.1.2 CSS
 Cascading Style Sheets (CSS) is a style sheet language used for describing the
presentation of a document written in a markup language like HTML.CSS is
cornerstone technology of the World Wide Web, alongside HTML and
JavaScript .CSS is designed to enable the separation of presentation and
content, 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, and reduce complexity and repetition in the
structural content.
 CSS information can be provided from various sources. These sources can be the web
browser, the user and the author. The information from the author can be further
classified into inline, media type, importance, selector specificity, rule order,
inheritance and property definition. CSS style information can be in a separate
document or it can be embedded into an HTML document. Multiple style sheets can be
imported. Different styles can be applied depending on the output device being used;
for example, the screen version can be quite different from the printed version, so that
authors can tailor the presentation appropriately for each medium. The style sheet with
the highest priority controls the content display. Declarations not set in the highest
priority source are passed on to a source of lower priority, such as the user agent style.
The process is called cascading.
 One of the goals of CSS is to allow users greater control over presentation. Someone
who finds red italic headings difficult to read may apply a different style sheet.
Depending on the browser and the web site
18
5.2 BACK END
5.2.1. PHP:
 PHP (Hypertext Processor) is a general-purpose scripting language and

interpreter that id freely available and widely used for web development. The
language is used primarily for server-side scripting, although it can also be used
for command-line scripting and, to a limited degree, desktop applications.
 It is primarily used for server-side scripting, but can also be used for
command-line scripting and desktop applications.
 The biggest strength of PHP :

 Scalability: PHP is a good choice for large-scale projects.
 Community support: PHP has a strong community of support.
 Ease of use: PHP has a simple syntax that is user-friendly and ideal for
beginners.
 Integration: PHP integrates with various databases, including MySQL.
 Stability: PHP is stable for a few years with regular support for various
versions.
 Reuse: PHP helps with reusing code, so you don't have to write lengthy code.
 Manage code: PHP helps with managing code
19
5.2.2. MySQL:
 .MySQL, or My Structured Query Language, is a free, open-source relational

database management system (RDBMS) that stores data in tables instead of
one big storage room. It uses Structured Query Language (SQL) and is
developed by Oracle.
 MySQL is used for storing and managing data. For example, a database can be a
shopping list, picture gallery, or corporate network. The combination of PHP and
MySQL can be used to create a variety of websites, from contact forms to
corporate portals.
 Keywords are words that have significance in SQL. Certain keywords, such as
SELECT , DELETE , or BIGINT , are reserved and require special treatment for
use as identifiers such as table and column names. This may also be true for the
names of built-in functions.
20
CHAPTER 6
TESTING AND IMPLEMENTATION
21
6. TESTING AND IMPLEMENTATION
 The term implementation has different meanings ranging from the conversation of a
basic application to a complete replacement of a computer system. The procedures
however, are virtually the same. Implementation includes all those activities that take
place to convert from old system to new. The new system may be totally new
replacing an existing manual or automated system or it may be major modification to
an existing system. The method of implementation and time scale to be adopted is
found out initially. Proper implementation is essential to provide a reliable system to
meet organization requirement.
6.1 UNIT TESTING

6.1.1 Introduction
 In computer programming, unit testing is a software testing method by which individual
units of source code, sets of one or more computer program modules together with
associated control data, usage procedures, and operating procedures, are tested to
determine whether they are fit for use. Intuitively, one can view a unit as the smallest
testable part of an application. In procedural programming, a unit could be an entire
module, but it is more commonly an individual function or procedure. In object-
oriented programming, a unit is often an entire interface, such as a class, but could be
an individual method. Unit tests are short code fragments created by programmers or
occasionally by white box testers during the development process. It forms the basis for
component testing. Ideally, each test case is independent from the others. Substitutes
such as method stubs, mock objects, fakes, and test harnesses can be used to assist
testing a module in isolation. Unit tests are typically written and run by software
developers to ensure that code meets its design and behaves as intended.
6.1.2 Benefits
 The goal of unit testing is to isolate each part of the program and show that the
individual parts are correct. A unit test provides a strict, written contract that the piece
of code must satisfy. As a result, it affords several benefits.
1) Find problems early: Unit testing finds problems early in the development cycle. In test-
driven development (TDD), which is frequently used in both extreme programming and scrum,
unit tests are created before the code itself is written.
22
If the unit tests fail, it is considered to be a bug either in the changed code or the tests
themselves. The unit tests then allow the location of the fault or failure to be easily traced.
Since the unit tests alert the development team of the problem before handing the code off to
testers or clients, it is still early in the development process.
2) Facilitates Change: Unit testing allows the programmer to refactor code or upgrade
system libraries at a later date, and make sure the module still works correctly (e.g., in
regression testing). The procedure is to write test cases for all functions and methods so that
whenever a change causes a fault, it can be quickly identified. Unit tests detect changes which
may break a design contract.
3) Simplifies Integration: Unit testing may reduce uncertainty in the units themselves and
can be used in a bottom-up testing style approach. By testing the parts of a program first and
then testing the sum of its parts, integration testing becomes much easier.
4) Documentation: Unit testing provides a sort of living documentation of the system.

Developers looking to learn what functionality is provided by a unit, and how to use it, can
look at the unit tests to gain a basic understanding of the unit's interface (API). Unit test cases
embody characteristics that are critical to the success of the unit. These characteristics can
indicate appropriate/inappropriate use of a unit as well as negative behaviour that are to be
trapped by the unit. A unit test case, in and of itself, documents these critical characteristics,
although many software development environments do not rely solely upon code to document
the product in development.
23
6.2 INTEGRATION TESTING
Integration testing (sometimes called integration and testing, abbreviated I&T) is the
phase in software testing in which individual software modules are combined and tested as a
group. It occurs after unit testing and before validation testing. Integration testing takes as its
input modules that have been unit tested, groups them in larger aggregates, applies tests
defined in an integration test plan to those aggregates, and delivers as its output the integrated
system ready for system testing.
6.2.1 Purpose
 The purpose of integration testing is to verify functional, performance, and reliability

requirements placed on major design items. These "design items", i.e., assemblages (or
groups of units), are exercised through their interfaces using black-box testing, success
and error cases being simulated via appropriate parameter and data inputs. Simulated
usage of shared data areas and inter-process communication is tested and individual
subsystems are exercised through their input interface. Test cases are constructed to test
whether all the components within assemblages interact correctly, for example across
procedure calls or process activation, and this is done after testing individual modules,
i.e., unit testing. The overall idea is a "building block" approach, in which verified
assemblages are added to a verified base which is then used to support the integration
testing of further assemblages. Software integration testing is performed according to
the software development life cycle (SDLC) after module and functional tests. The
cross-dependencies for software integration testing are: schedule for integration testing,
strategy and selection of the tools used for integration, define the chromatically
complexity of the software and software architecture, re usability of modules and life-
cycle and versioning management. Some different types of integration testing are big-
bang, top-down, and bottom-up, mixed (sandwich) and risky-hardest. Other Integration
Patterns are: collaboration integration, backbone integration, layer integration, client-
server integration, distributed services integration and high-frequency integration.
24
6.2.1.1 Big Bang
 In the big-bang approach, most of the developed modules are coupled together to form
a complete software system or major part of the system and then used for integration
testing. This method is very effective for saving time in the integration testing process.
However, if the test cases and their results are not recorded properly, the entire
integration process will be more complicated and may prevent the testing team from
achieving the goal of integration testing. A type of big-bang integration testing is called
"usage model testing" which can be used in both software and hardware integration
testing. The basis behind this type of integration testing is to run user-like workloads in
integrated user-like environments. In doing the testing in this manner, the environment
is proofed, while the individual components are proofed indirectly through their use.
Usage Model testing takes an optimistic approach to testing, because it expects to have
few problems with the individual components. The strategy relies heavily on the
component developers to do the isolated unit testing for their product. The goal of the
strategy is to avoid redoing the testing done by the developers, and instead flesh-out
problems caused by the interaction of the components in the environment. For
integration testing, Usage Model testing can be more efficient and provides better test
coverage than traditional focused functional integration testing. To be more efficient
and accurate, care must be used in defining the user-like workloads for creating realistic
scenarios in exercising the environment. This gives confidence that the integrated
environment will work as expected for the target customers.
25
6.2.1.2 Top-down And Bottom-up
Bottom-up testing is an approach to integrated testing where the lowest level components
are tested first, then used to facilitate the testing of higher level components. The process is
repeated until the component at the top of the hierarchy is tested. All the bottom or low-level
modules, procedures or functions are integrated and then tested. After the integration testing of
lower level integrated modules, the next level of modules will be formed and can be used for
integration testing. This approach is helpful only when all or most of the modules of the same
development level are ready. This method also helps to determine the levels of software
developed and makes it easier to report testing progress in the form of a percentage. Top-down
testing is an approach to integrated testing where the top integrated modules are tested and the
branch of the module is tested step by step until the end of the related module. Sandwich testing
is an approach to combine top-down testing with bottom-up testing.
6.3 SOFTWARE VERIFICATION AND VALIDATION
6.3.1 Introduction
 In software project management, software testing, and software engineering,

verification and validation (V&V) is the process of checking that a software system
meets specifications and that it fulfil its intended purpose. It may also be referred to as
software quality control. It is normally the responsibility of software testers as part of
the software development life cycle. Validation checks that the product design satisfies
or fits the intended use (high-level checking), i.e., the software meets the user
requirements. This is done through dynamic testing and other forms of review.
Verification and validation are not the same thing, although they are often confused.
Boehm succinctly expressed the difference between:
● Validation: Are we building the right product?

● Verification: Are we building the product right?
26
According to the Capability Maturity Model (CMMI - SW v1.1):
● Software Verification: The process of evaluating software to determine whether the

products of a given development phase satisfy the conditions imposed at the start of
that phase.
● Software Validation: The process of evaluating software during or at the end of the
development process to determine whether it satisfies specified requirements. In other
words, software verification is ensuring that the product has been built according to the
requirements and design specifications, while software validation ensures that the
product meets the user's needs, and that the specifications were correct in the first place.
Software verification ensures that "you built it right". Software validation ensures that
"you built the right thing".
● Malfunction – according to its specification the system does not meet its specified
functionality. Both verification and validation are related to the concepts of quality and
of software quality assurance. By themselves, verification and validation do not
guarantee software quality; planning, traceability, configuration management and other
aspects of software engineering are required. Within the modeling and simulation
(M&S) community, the definitions of verification, validation and accreditation are
similar:
● M&S Verification is the process of determining that a computer model, simulation, or
federation of models and simulations implementations and their associated data
accurately represent the developer's conceptual description and specifications.
● M&S Validation is the process of determining the degree to which a model, simulation,
or federation of models and simulations, and their associated data are accurate
representations of the real world from the perspective of the intended use(s).
6.3.2 Classification of Methods
In mission-critical software systems, where flawless performance is absolutely necessary,

formal methods may be used to ensure the correct operation of a system..
27
6.3.3 Test Cases
A test case is a tool used in the process. Test cases may be prepared for software
verification and software validation to determine if the product was built according to the
requirements of the user. Other methods, such as reviews, may be used early in the life cycle to
provide for software validation.
6.4 Black-Box Testing
Black-box testing is a method of software testing that examines the functionality of an

application without peering into its internal structures or workings. This method of test can be
applied virtually to every level of software testing: unit, integration, system and acceptance. It
typically comprises most if not all higher-level testing, but can also dominate unit testing as
well.
6.4.1 Test Procedures
Specific knowledge of the application's code/internal structure and programming

knowledge in general is not required. The tester is aware of what the software is supposed to
do but is not aware of how it does it. For instance, the tester is aware that a particular input
returns a certain, invariable output but is not aware of how the software produces the output in
the first place.
6.4.2 Test Cases
Test cases are built around specifications and requirements, i.e., what the application is
supposed to do. Test cases are generally derived from external descriptions of the software,
including specifications, requirements and design parameters. Although the tests used are
primarily functional in nature, non-functional tests may also be used.
28
6.5 White-Box Testing
White-box testing (also known as clear box testing, glass box testing, transparent box testing,
and structural testing) is a method of testing software that tests internal structures or workings
of an application, as opposed to its functionality (i.e. black-box testing). In white-box
testing an internal perspective of the system, as well as programming skills, are used to
design test cases. The tester chooses inputs to exercise paths through the code and determine
the appropriate outputs. This is analogous to testing nodes in a circuit, e.g. in-circuit testing
(ICT). White-box testing can be applied at the unit, integration and system levels of the
software testing process. Although traditional testers tended to think of white-box testing as
being done at the unit level, it is used for integration and system testing more frequently today.
It can test paths within a unit, paths between units during integration, and between subsystems
during a system–level test. Though this method of test design can uncover many errors or
problems, it has the potential to miss unimplemented parts of the specification or missing
requirements.
6.5.1 Levels
1. Unit testing: White-box testing is done during unit testing to ensure that the code
is working as intended, before any integration happens with previously tested code.
White-box testing during unit testing catches any defects early on and aids in any
defects that happen later on after the code is integrated with the rest of the
application and therefore prevents any type of errors later on.
2. Integration testing: White-box testing at this level are written to test the
interactions of each interface with each other. The Unit level testing made sure that
each code was tested and working accordingly in an isolated environment and
integration examines the correctness of the behaviour in an open environment
through the use of white-box testing for any interactions of interfaces that are
known to the programmer.
29
3. Regression testing: White-box testing during regression testing is the use of recycled
white-box test cases at the unit and integration testing levels.
6.5.2 Procedures
 White-box testings basic procedures involves the tester having a deep level of
understanding of the source code being tested. The programmer must have a deep
understanding of the application to know what kinds of test cases to create so that every
visible path is exercised for testing. Once the source code is understood then the source
code can be analyzed for test cases to be created. These are the three basic steps that
white-box testing takes in order to create test cases:
 Input involves different types of requirements, functional specifications, detailed

designing of documents, proper source code, security specifications. This is the
preparation stage of white-box testing to layout all of the basic information. Processing
involves performing risk analysis to guide whole testing process, proper test plan,
execute test cases and communicate results. This is the phase of building test cases to
make sure they thoroughly test the application the given results are recorded
accordingly. Output involves preparing final report that encompasses all of the above
preparations and results.
6.5.3 Advantages
 White-box testing is one of the two biggest testing methodologies used today. It has
several major advantages: Side effects of having the knowledge of the source code is
beneficial to thorough testing. Optimization of code by revealing hidden errors and
being able to remove these possible defects. Gives the programmer introspection
because developers carefully describe any new implementation. Provides traceability
of tests from the source, allowing future changes to the software to be easily captured
in changes to the tests.
30
6.5.4 Disadvantages
 Although white-box testing has great advantages, it is not perfect and contains some
disadvantages: White-box testing brings complexity to testing because the tester
must have knowledge of the program, including being a programmer. White-box
testing requires a programmer with a high level of knowledge due to the complexity
of the level of testing that needs to be done. On some occasions, it is not realistic to
be able to test every single existing conditions will be untested. The tests focus on
the software as it exists, and missing functionality may not be discovered.
6.6 SYSTEM TESTING
System testing of software or hardware is testing conducted on a complete, integrated system

to evaluate the system's compliance with its specified requirements. System testing falls
within the scope of black-box testing, and as such, should require no knowledge of the inner
design of the code or logic. As a rule, system testing takes, as its input, all of the "integrated"
software components that have passed integration testing and also the software system itself
integrated with any applicable hardware system(s). The purpose of integration testing is to
detect any inconsistencies between the software units that are integrated together (called
assemblages) or between any of the assemblages and the hardware. System testing is a
more limited type of testing; it seeks to detect defects both within the "inter-assemblages"
and also within the system as a whole.
System testing is performed on the entire system in the context of a Functional

Requirement Specification(s) (FRS) and/or a System Requirement Specification (SRS). System
testing tests not only the design, but also the behaviour and even the believed expectations
of the customer. It is also intended to test up to and beyond the bounds defined in the
software/hardware requirements specification(s).
31
CHAPTER 7
SCREEN INVOLVED IN APPLICATION
32
7 . Screen involved in Application:
 User
 Register
 Login
 My account
 Shopping cart
 logout
 Admin
 Admin login
 Insert and View all packages
 Insert and View all categories
 Insert and view all types
 View employee details
 View customers
33
7.1 Brief explanation about the screens :
7.1.1 Login:
It allows us to get into the system by gathering username and password.
7.1.2 Register :
A register portal is a page that asks for a user’s username, email, password and then
sends the data to the database.
7.1.3 User home page :

The user’s homepage contain the all packages,my account, shopping cart, contact us ,
register and the user can also view as a guest.
7.1.4 Contact Us:

The user’s can contact to the developers via contact us page.the user can be visit full
detail in contact us page.
7.1.5 Admin Dashboard:

Administrators to manage and monitor various aspects of a websites,
application or business.It viewing important information, such as website user accounts
and data analytic.
7.1.6 Logout:
By using these features, user are able to logout from the system whenever they wish
to leave the system.
34
CHAPTER 8
Source code, Sample screenshot & database
35
8.1 SOURCE CODE:
8.1.1 User Login page:
<?php
session_start();
include("includes/db.php");
if (isset($_POST['login'])) {
$email = mysqli_real_escape_string($con, $_POST['email']);
$pass = mysqli_real_escape_string($con, $_POST['password']);
$sel_user = "select * from admins where user_email='$email' AND

user_pass='$pass'";
$run_user = mysqli_query($con, $sel_user);
$check_user = mysqli_num_rows($run_user);
if ($check_user == 1) {
$_SESSION['user_email'] = $email;
header('location:index.php');
echo "<script>window.open('index.php?logged_in=You have successfully
Logged into ADMIN PANEL!','_self')</script>";
} else {
echo "<script>alert('password or Password did not match, try
again!')</script>";
}}
?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Login Form</title>
<link rel="stylesheet" type="text/css"
href="/admin_area/styles/login_style.css" media="all">
<link rel="icon" href="/customer/images/logo1.jpg" type="image/icon type" >
</head><body>
<div class="login">
<h2 style="color: white; text-align: center;"><?php echo
@$_GET['not_admin']; ?></h2>
@$_GET['logged_out']; ?></h2>
<h1>Admin Login</h1>
<form method="post" action="login.php">
<input type="text" name="email" placeholder="Email"
required="required"/>
<input type="password" name="password" placeholder="Password"
<button type="submit" name="login" class="btn btn-primary btn-block
btn-large">Login</button>
</form>
</div></body></html>
36
8.1.2:Home page:
<?php
session_start();
include("functions/functions.php");
?>
<!DOCTYPE html>
<html lang="en">
<head>
<title>Travel : Home</title>
<link rel="stylesheet" href="styles/style.css" media="all">
<link rel="icon" href="/customer/images/logo1.jpg" type="image/icon
type" >
<style>
.adminbtn {
background-color: #4CAF50; /* Green */
border: none;
color: white;
padding: 1px 2px;
text-align: center;
text-decoration: none;
display: inline-block;
font-size: 10px;
cursor: pointer;
-webkit-transition-duration: 0.4s; /* Safari */
transition-duration: 0.4s;
margin-top: 12px;
margin-left: 2px;
}
.adminbtn:hover {
box-shadow: 0 12px 16px 0 rgba(0, 0, 0, 0.24), 0 17px 50px 0
rgba(0, 0, 0, 0.19);
}
</style>
</head>
<body>

<div class="main_wrapper">

<?php include 'includes/header.php'; ?>


<?php include 'includes/navbar.php'; ?>


<div class="content_wrapper">
37



<?php include "includes/left-sidebar.php"; ?>

<div id="content_area">
<?php cart(); ?>
<div id="shopping_cart">
<span style="float: left;font-size: 15px;padding: 5px;line-
height: 40px;">
<?php
if (isset($_SESSION['customer_email'])) {
echo "<b>Welcome: </b>" .
$_SESSION['customer_email'] ;
} else {
echo "<b>Welcome Guest:</b>";
}
?>
</span>
<span style="float: right;font-size: 15px;padding: 5px;line-
height: 40px;">
<b style="color: yellow;">Your Shopping Cart-</b> Total
Items: <?php total_items(); ?>
Total Price: <?php total_price(); ?> <a href="cart.php"
style="color: yellow;">Go to Cart</a>
<?php
if (!isset($_SESSION['customer_email'])) {
echo "<a href='checkout.php' style='color:
orange;'>User Login</a>";
} else {
echo "<a href='logout.php' style='color:
orange;'>Logout</a>";
}
?>
</span>
</div>
<div id="packages_box">
<?php getPack(); ?>
<?php getCatPack(); ?>
<?php getTypePack(); ?>
</div>
</div>
</div>

</div>
</body>
</html>
38
8.1.3:All package :
<?php
?>
<!DOCTYPE html>
<html lang="en">
<head>
<title>Travel : All Packages</title>
type" >
</head>
<body>






<?php cart(); ?>

<span style="float:right;font-size: 18px;padding:
<b style="color: yellow;">Your Shopping Cart-</b>
Total Items: <?php total_items(); ?>
Total Price: <?php total_price(); ?> <a
href="cart.php" style="color: yellow;">Go to Cart</a>
</div>
39
<?php
$get_pack = "SELECT * FROM packages";
$run_pack = mysqli_query($con, $get_pack);

while ($row_pack = mysqli_fetch_array($run_pack)) {
$pack_id = $row_pack['package_id'];
$pack_cat = $row_pack['package_cat'];
$pack_type = $row_pack['package_type'];
$pack_title = $row_pack['package_title'];
$pack_price = $row_pack['package_price'];
$pack_image = $row_pack['package_image'];
echo "
<div id='single_package'>
<h3 style='font-family: Cambria; margin-bottom: 2px;
color:black; font-weight:bold;'>$pack_title</h3>
<img src='admin_area/package_images/$pack_image'
width='180' height='180'>
<p><b style = 'color:black;'> Cost ₹
$pack_price</b></p>
<a href='details.php?pack_id=$pack_id' style='float:
left; font-size:18px;text-decoration: none; font-weight:bold;'>Details</a>
<a href='cart.php?add_cart=$pack_id'><button
style='float: right; font-size:14px; cursor: pointer; padding: 2px 4px; font-
weight:bold;'>Book</button></a>
</div>
";
}
?>
</div>
</div>
</div>


<?php include "includes/footer.php";?>

</div>

</body>
</html>
40
8.1.4:shopping cart:
<?php
session_start();
$total = 0;
?>
<!DOCTYPE html>
<html lang="en">
<head>
<title>Travel Bird : Cart</title>
type" >
</head>
<body>
<?php cart(); ?>
<span style="float: right;font-size: 16px;padding:
<?php
$_SESSION['customer_email'] . "<b style='color: yellow;'> Your</b>";
} else {
}
?>
<b style="color: yellow;">Shopping Cart-</b> Total
Items: <?php total_items(); ?>
Total Price: <?php total_price(); ?>
<a href="index.php" style="color: yellow;">Back to
Home</a>
<?php
41
<?php
if (!isset($_SESSION['customer_email'])) {
echo "<a href='checkout.php' style='color:
orange;'>Login</a>";
} else {
echo "<a href='logout.php' style='color:
orange;''>Logout</a>";
}
?>
</span>
</div>
<form action="" method="post" enctype="multipart/form-data">
<table align="center" width="700px" bgcolor="skyblue">
<tr align="center">
<th>Remove</th>
<th>Package(s)</th>
<th>Quantity</th>
<th>Total Cost</th>
</tr>
<?php
global $con;
$ip = getIp();
$sel_price = "SELECT * FROM cart WHERE ip_add='$ip'";
$run_price = mysqli_query($con, $sel_price);
while ($p_price = mysqli_fetch_array($run_price)) {

$pack_id = $p_price['p_id'];
$pack_price = "SELECT * FROM packages WHERE
package_id='$pack_id'";
$run_pack_price = mysqli_query($con, $pack_price);
while ($pp_price = mysqli_fetch_array($run_pack_price)) {
$package_price = array($pp_price['package_price']);
$package_title = $pp_price['package_title'];
$package_image = $pp_price['package_image'];
$single_price = $pp_price['package_price'];
$values = array_sum($package_price);
$total += $values;
?>
<tr align="center"
<td><input type="checkbox"name="remove[]" value="<?php echo $pack_id; ?>"></td>
<td>
<?php echo $package_title; ?><br>
<img
src="admin_area/package_images/<?php echo $package_image; ?>"
width="60px" height="60px">
</td>
<td><input type="text" size="4"
name="qty" value="<?php
if (isset($_SESSION['qty'])) {
42
echo $_SESSION['qty'];
}
?>">
</td>
<?php
global $con;
if (isset($_POST['update_cart'])) {
$qty = $_POST['qty'];
$update_qty = "UPDATE cart SET qty='$qty'";
$run_qty = mysqli_query($con, $update_qty);
$_SESSION['qty'] = $qty;
$total = settype($qty, 'int') * $total;
}
?>
<td>
<?php echo "₹" . $single_price; ?>
</td>
</tr>
<?php
}
}
?>
<tr align="right">
<td colspan="4"><b>Sub Total:</b></td>
<td>
<?php echo "₹" . $total; ?>
</td>
</tr>
<tr align="center">
<td colspan="2"><input type="submit" name="update_cart" value="Update
Cart"></td>
<td><input type="submit" name="continue" value="Continue Shopping"></td>
<td>
<button><a href="checkout.php"
style="text-decoration: none;
color:black;">Checkout</a></button>
</td>
</tr>
</table>
</form>
<?php
function updatecart()
{
global $con;
$ip = getIp()
if (isset($_POST['update_cart'])) {
foreach ($_POST['remove'] as $remove_id) {
$delete_package = "DELETE FROM cart WHERE
p_id='$remove_id' AND ip_add='$ip'";
$run_delete = mysqli_query($con, $delete_package);
43
if ($run_delete) {
echo "<script>window.open('cart.php','self')</script>";
}
}
}
if (isset($_POST['continue'])) {
echo "<script>window.open('index.php','self')</script>";
}
}
echo @$up_cart = updatecart();
?>
</div>
</div>
</div>
</html>
44
8.1.5:Register :
<?php
session_start();
global $con;
if (isset($_POST['register'])) {
$ip = getIp();
$c_name = $_POST['c_name'];
$c_email = $_POST['c_email'];
$c_pass = $_POST['c_pass'];
$c_passport = $_POST['c_passport'];
$c_image = $_FILES['c_image']['name'];
$c_image_tmp = $_FILES['c_image']['tmp_name'];
$c_country = $_POST['c_country'];
$c_city = $_POST['c_city'];
$c_contact = $_POST['c_contact'];
$c_address = $_POST['c_address'];
// image will upload there
move_uploaded_file($c_image_tmp, "customer/customer_images/$c_image");
$insert_c = "INSERT INTO customers
(customer_ip,customer_name,customer_email,customer_pass,c_passport,customer_coun
try,customer_city,customer_contact,customer_address,customer_image) VALUES
('$ip','$c_name','$c_email','$c_pass','$c_passport','$c_country','$c_city','$c_c
ontact','$c_address','$c_image')";
$run_c = mysqli_query($con, $insert_c);
$sel_cart = "SELECT * FROM cart WHERE ip_add='$ip'";
$run_cart = mysqli_query($con, $sel_cart);
$check_cart = mysqli_num_rows($run_cart);
if ($check_cart == 0) {
$_SESSION['customer_email'] = $c_email;
echo "<script>alert('Account has been created successfully.
Thanks!')</script>";
echo "<script>window.open('customer/my_account.php','_self')</script>";
} else {
$_SESSION['customer_email'] = $c_email;
echo "<script>alert('Account has been created successfully.
Thanks!')</script>";
echo "<script>window.open('index.php','_self')</script>";
}
}
?>
<!DOCTYPE html>
<html lang="en">
<head>
<title>Travel Bird : Register</title>
45
<link rel="icon" href="/customer/images/logo1.jpg" type="image/icon type" >
<style type="text/css">
#fixm {
font-size: 15px;
padding: 4px;
font-family: arial;
}
#fixi {
font-size: 14px;
font-family: arial;
}
#btn {
font-family: arial;
font-size: 14px;
background-color: #4CAF50; /* Green */
border: none;
color: white;
padding: 10px 10px;
text-align: center;
text-decoration: none;
display: inline-block;
font-size: 16px;
margin: 4px 2px;
transition-duration: 0.4s;
cursor: pointer;
background-color: #32E875;
color: black;
}
#btn:hover {
background-color: #4CAF50;
color: white;
}
</style>
</head>
<body>
<div id="content_area1">
<?php cart(); ?>
46
<div id="shopping_cart1">
<span style="float:left;font-size: 18px;padding:
5px;line-height: 40px; font-family:Sans-serif;">Welcome Guest!

</span>
</div>
<form action="customer_register.php" method="post"
enctype="multipart/form-data">
<table align="center" width="1000px" style="margin-top:
20px;">
<tr align="center">
<td colspan="6">
<h2 style="margin-bottom: 15px; font-family:
Cambria;">Create an Account</h2>
</td>
</tr>
<tr>
<td align="right" id="fixm">Your Name:</td>
<td><input id="fixi" type="text" name="c_name"
required=""></td>
</tr>
<tr>
<td align="right" id="fixm">Your Email:</td>
<td><input type="email" name="c_email"
required=""></td>
</tr>
<tr>
<td align="right" id="fixm">Your Password:</td>
<td><input id="fixi" type="password" name="c_pass"
required=""></td>
</tr>
<tr>
<td align="right" id="fixm">Your Passport ID:</td>
<td><input type="text" name="c_passport"
required=""></td>
</tr>

<tr>
<td align="right" id="fixm">Your Country:</td>
<td>
<select name="c_country" required="">Select a
47
<option>Australia</option>
<option>India</option>
<option>Japan</option>
<option>China</option>
<option>Russia</option>
<option>Thailand</option>
<option>England</option>
<option>Brazil</option>
<option>Spain</option>
<option>France</option>
<option>Switzerland</option>
<option>Germany</option>
<option>Argentina</option>
<option>Italy</option>
<option>Turkey</option>
</select>
</td>
</tr>
<tr>
<td align="right" id="fixm">Your City:</td>
<td><input id="fixi" type="text" name="c_city"
required=""></td>
</tr>
<tr>
<td align="right" id="fixm">Your Contact:</td>
<td><input id="fixi" type="text" name="c_contact"
required=""></td>
</tr>
<tr>
<td align="right" id="fixm">Your Address:</td>
<td><input id="fixi" type="text" name="c_address"
required=""></td>
</tr>
<tr align="center" >
<td colspan="6" style="padding-bottom: 10px;"><input
id="btn" type="submit" name="register" value="Create Account">
</td>
</tr>
</table>
</form>
</div>
</div>
</body>
</html>
48
8.1.6 : Admin Login :
<?php
session_start();
if (isset($_POST['login'])) {
$email = mysqli_real_escape_string($con, $_POST['email']);
$pass = mysqli_real_escape_string($con, $_POST['password']);
$sel_user = "select * from admins where user_email='$email' AND

user_pass='$pass'";
$run_user = mysqli_query($con, $sel_user);
$check_user = mysqli_num_rows($run_user);
if ($check_user == 1) {
$_SESSION['user_email'] = $email;
echo "<script>window.open('index.php?logged_in=You have successfully
Logged into ADMIN PANEL!','_self')</script>";
} else {
echo "<script>alert('Email or Password did not match, try
again!')</script>";
}
}
?>
<!DOCTYPE html>
<html lang="en">
<head>
<title>Login Form</title>
<link rel="stylesheet" type="text/css" href="styles/login_style.css"
media="all">
</head>
<body>
<div class="login">
@$_GET['not_admin']; ?></h2>
@$_GET['logged_out']; ?></h2>
<h1>Admin Login</h1>
<form method="post" action="login.php">
<input type="text" name="email" placeholder="Email"
<input type="password" name="password" placeholder="Password"
<button type="submit" name="login" class="btn btn-primary btn-block
btn-large">Login</button>
</form>
</div></body></html>
49
8.1.6 : Admin Home Page :
<?php
session_start();
if (!isset($_SESSION['user_email'])) {
echo "<script>window.open('login.php?not_admin=You are not an
Admin!','_self')</script>";
} else {
?>
<!DOCTYPE html>
<html lang="en">
<head>
<title>Admin Panel</title>
<link rel="stylesheet" type="text/css" href="styles/style.css"
media="all">
type" >
</head>
<body>
<div id="header">
</div>
<div id="right">
<h2 style="text-align: center; margin-top: 10px; font-family:
Cambria;">Dashboard</h2>
<ul>
<li><a href="index.php">Admin Panel : Home</a></li>
<li><a href="index.php?insert_package">Insert New Package</a></li>
<li><a href="index.php?view_packages">View All Packages</a></li>
<li><a href="index.php?insert_cat">Insert New Categories</a></li>
<li><a href="index.php?view_cats">View All Categories</a></li>
<li><a href="index.php?insert_type">Insert New Types</a></li>
<li><a href="index.php?view_types">View All Types</a></li>
<li><a href="index.php?insert_employee">Insert New Employee</a></li>
<li><a href="index.php?view_employees">View All Employees</a></li>
<li><a href="index.php?view_customers">View All Customers</a></li>
<li><a href="logout.php">Logout</a></li> </ul>
</div>
<div id="left">
<h2 style="color: red; text-align: center; font-family:
Cambria; margin-top: 15px;"><?php echo @$_GET['logged_in']; ?></h2>
<?php
if (isset($_GET['insert_package'])) {
include("insert_package.php");
}
if (isset($_GET['view_packages'])) {
include("view_packages.php");
50
}
if (isset($_GET['edit_pack'])) {
include("edit_pack.php");
}
if (isset($_GET['insert_cat'])) {
include("insert_cat.php");
}
if (isset($_GET['view_cats'])) {
include("view_cats.php");
}
if (isset($_GET['edit_cat'])) {
include("edit_cat.php");
}
if (isset($_GET['insert_type'])) {
include("insert_type.php");
}
if (isset($_GET['view_types'])) {
include("view_types.php");
}
if (isset($_GET['edit_type'])) {
include("edit_type.php");
}
if (isset($_GET['view_customers'])) {
include("view_customers.php");
}
if (isset($_GET['insert_employee'])) {
include("insert_employee.php");
}
if (isset($_GET['view_employees'])) {
include("view_employees.php");
}
if (isset($_GET['edit_emp'])) {
include("edit_emp.php");
}
?>
</div>
</div>
</body>
</html>
<?php
}
<html lang="en">
<head>
<title>Title</title>
51
</head>
<style>
*{
box-sizing: border-box;
8.1.7 : Employee :
<?php
} else {
?>
<!DOCTYPE html>
<html lang="en">
<head>
<title>View Employees</title>
#thfix {
font-family: sans-serif;
padding: 4px;
}
</style>
</head>
<body>
<table width="795" align="center" bgcolor="#EAD2AC">
<tr align="center">
<td colspan="8"><h2 style="font-family: Cambria; margin-top:
10px; margin-bottom: 5px;">View All
Employees</h2>
</td>
</tr>
<tr align="center" bgcolor="#5FCEE8">
<th id="thfix">Sl.</th>
<th id="thfix">Name</th>
<th id="thfix">Email</th>
<th id="thfix">Designation</th>
<th id="thfix">Location</th>
<th id="thfix">Address</th>
<th id="thfix">Contact</th>
<th id="thfix">Edit</th>
<th id="thfix">Delete</th>
</tr>
<?php
$get_c = "select * from employees";
$run_c = mysqli_query($con, $get_c);
$i = 0;
while ($row_c = mysqli_fetch_array($run_c)) {
$e_id = $row_c['emp_id'];
$e_name = $row_c['emp_name'];
$e_email = $row_c['emp_email'];
52
$e_designation = $row_c['emp_designation'];
$e_location = $row_c['emp_location'];
$e_address = $row_c['emp_address'];
$e_contact = $row_c['emp_contact'];
$i++;
?>
<tr align="center">
<td><?php echo $i; ?></td>
<td><?php echo $e_name; ?></td>
<td><?php echo $e_email; ?></td>
<td><?php echo $e_designation; ?></td>
<td><?php echo $e_location; ?></td>
<td><?php echo $e_address; ?></td>
<td><?php echo $e_contact; ?></td>
<td><a href="index.php?edit_emp=<?php echo
$e_id; ?>">Edit</a></td>
<td><a href="delete_e.php?delete_e=<?php echo
$e_id; ?>">Delete</a></td>
</tr>
<?php
}
?>
</table>
</body>
</html>
<?php
}?>
53
8.1.8 :Customer :
<?php
} else {
?>
<!DOCTYPE html>
<html lang="en">
<head>
<title>View Customers</title>
#thfix {
padding: 4px;
}
</style>
</head>
<body>
<tr align="center">
Customers
Here</h2></td>
</tr>
<th id="thfix">Name</th>
<th id="thfix">Email</th>
<th id="thfix">Passport</th>

</tr>
<?php
$get_c = "select * from customers";

$run_c = mysqli_query($con, $get_c);
$i = 0;
while ($row_c = mysqli_fetch_array($run_c)) {
$c_id = $row_c['customer_id'];
$c_name = $row_c['customer_name'];
$c_email = $row_c['customer_email'];
$c_passport = $row_c['c_passport'];
54
$c_image = $row_c['customer_image'];
$i++;
?>
<tr align="center">
<td><?php echo $c_name; ?></td>
<td><?php echo $c_email; ?></td>
<td><?php echo $c_passport; ?></td>

<td><a href="delete_c.php?delete_c=<?php echo
$c_id; ?>">Delete</a></td>
<td></td>
</tr>
<?php
}
?>
</table>
</body>
</html>
<?php
}?>
55
8.1.9 :View all packages :
<?php
} else {
?>
<!DOCTYPE html>
<html lang="en">
<head>
<title>View Packages</title>
#thfix {
padding: 4px;
}
</style>
</head>
<body>
<tr align="center">
packages
Here</h2></td>
</tr>
<th id="thfix">Title</th>
<th id="thfix">Image</th>
<th id="thfix">Price</th>
<th id="thfix">Edit</th>
</tr>
<?php
$get_pack = "select * from packages";

$run_pack = mysqli_query($con, $get_pack);
$i = 0;
while ($row_pack = mysqli_fetch_array($run_pack)) {
$pack_id = $row_pack['package_id'];
$pack_title = $row_pack['package_title'];
$pack_image = $row_pack['package_image'];
56
$pack_price = $row_pack['package_price'];
?>
<tr align="center">
<td><?php echo $pack_title; ?></td>
<td><img src="package_images/<?php echo $pack_image; ?>"
width="40" height="40"></td>
<td><?php echo $pack_price; ?></td>
<td><a href="index.php?edit_pack=<?php echo
$pack_id; ?>">Edit</a></td>
<td><a href="delete_pack.php?delete_pack=<?php echo
$pack_id; ?>">Delete</a></td>
<td></td>
</tr>
<?php
}
?>
</table>
</body>
</html>
<?php
}
?>
57
8.1.10 :Insert all packages :
<?php
if (isset($_POST['insert_post'])) {
//getting the text data from the fields
$package_cat = $_POST['package_cat'];
$package_type = $_POST['package_type'];
$package_title = $_POST['package_title'];
$package_price = $_POST['package_price'];
$package_desc = $_POST['package_desc'];
//getting the image from the fields

$package_image = $_FILES['package_image']['name'];
$package_image_tmp = $_FILES['package_image']['tmp_name'];
$package_keywords = $_POST['package_keywords'];
move_uploaded_file($package_image_tmp, "package_images/$package_image");
$insert_package = "insert into packages (package_cat, package_type,

package_title, package_price, package_desc, package_image, package_keywords)
values
('$package_cat','$package_type','$package_title','$package_price','$package_
desc','$package_image','$package_keywords')";
$insert_pack = mysqli_query($con, $insert_package);
if ($insert_pack) {
echo "<script>alert('New Package has been added!')</script>";
echo
"<script>window.open('index.php?insert_package','_self')</script>";
}
}
?>
<!DOCTYPE html>
<html>
<head>
<title>Inserting Package</title>

<script
src="https://cdn.tiny.cloud/1/1for1s0e28m9j1yub8bfhkq731vrfrbnpyu75l38hehixx
av/tinymce/6/tinymce.min.js" referrerpolicy="origin"></script>
<script>tinymce.init({selector: 'textarea'});</script>
</head>
58
<body bgcolor="skyblue">
<form action="insert_package.php" method="post" enctype="multipart/form-
data">
<table align="center" width="795" border=2px bgcolor="ABB3C8">
<tr align="center">
<td colspan="7"><h2 style="font-family: Cambria;margin-top:
20px; margin-bottom: 15px;">Insert New package Here</h2>
</td>
</tr>
<tr>
<td align="right"><b>Package Title:</b></td>
<td><input type="text" name="package_title" size="60"></td>
</tr>
<tr>
<td align="right"><b>Package Category:</b></td>
<td>
<select name="package_cat">
<option>Select a Category</option>
<?php $get_cats = "select * from categories";
$run_cats = mysqli_query($con, $get_cats);
while ($row_cats = mysqli_fetch_array($run_cats)) {
$cat_id = $row_cats['cat_id'];
$cat_title = $row_cats['cat_title'];
echo "<option
value='$cat_id'>$cat_title</option>";
} ?>
</select>
</td>
</tr>
<tr>
<td align="right"><b>Package Type:</b></td>
<td>
<select name="package_type">
<option>Select a Type</option>
<?php $get_types = "select * from types";
$run_types = mysqli_query($con, $get_types);
while ($row_types = mysqli_fetch_array($run_types)) {
$type_id = $row_types['type_id'];
$type_title = $row_types['type_title'];
echo "<option
value='$type_id'>$type_title</option>";
} ?>
</select>
</td>
</tr>
<tr>
<td align="right"><b>Package Image:</b></td>
59
<td><input type="file" name="package_image"></td>
</tr>
<tr>
<td align="right"><b>Package Price:</b></td>
<td><input type="text" name="package_price"></td>
</tr>
<tr>
<td align="right"><b>Package Description:</b></td>
<td><textarea name="package_desc" cols="20"
rows="10"></textarea></td>
</tr>
<tr>
<td align="right"><b>Package Keywords:</b></td>
<td><input type="text" name="package_keywords"
size="70"></textarea></td>
</tr>
<tr align="center">
<td colspan="7"><input style="margin-top: 10px; margin-bottom:
15px;" type="submit"
name="insert_post" value="Insert
Package"></td>
</tr>
</table>
</form>
</body>
</html>
60
8.2 SAMPLE SCREENSHOT:
LOGIN PAGE:
LOGIN AS USER :
In this module we can
1. Home Page
2. All packages
3. My Account
4. Contact us
5. Sign up
6. logout
61
HOME PAGE :
62
ALL PACKAGES :
Click the see all packages detail button and here we can see the list of package
63
MY ACCOUNT :
Click the my account details button here we can see the account details
64
CONTACT US :
65
REGISTER :
66
LOGIN AS ADMIN :
In this module we can
1. Login
2. Home page
3. View All Packages
4. Employee
5. Customers
6. logout
67
LOGIN PAGE:
68
HOME PAGE:
69
VIEW ALL PACKAGES:
70
EMPLOYEE DEATAILS :
71
CUSTOMERS DEATAILS :
72
DATA BASE:
USER DETAILS:
73
EMPLOYEES DETAILS:
74
ADMIN :
75
CATEGORIES :
76
PACKAGES :
77
TYPES :
78
CONCLUSION
 Compared to the present time consuming and uneconomical system, The

proposed Online Travel Management System Project reduces human resource
required - labour(agents),wastage of time and proves to be very economical in
the long run.
 This project can be further enhanced to provide better flexibility and

performance with certain modifications whenever necessary.
 It decreases the cost and time of maintaining a book.It is very easy to use and It
is very less time consuming.It is very easy to debug also.
79
REFERENCES
1. Archer, B. H. (1982). The Value of Multipliers and Their Policy Implications. Tourism
Management, 3(4).
2. Bramble, B. (1993). Tourism and the environment: challenges and choices for the 1990s.
Journal of Sustainable Tourism, 1(1).
3. Butler, R. W. (1980). The concept of a tourist area cycle of evolution: Implications for
management of resources. Canadian Geographer, 24(1).
4. https://genieprojectsworld.com/travel-agency-management-system-using-php.
5. https://www.w3schools.com/
6. https://www.apachefriends.org/
80

VIJAYS

Uploaded by

Copyright:

Available Formats

VIJAYS

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

VIJAYS

Uploaded by

Copyright:

Available Formats

TRAVEL MANAGEMENT SYSTEM

DEPARTMENT OF COMPUTER APPLICATION

PROJECT GUIDE HEAD OF THE DEPARTMENT

Submitted for the Project viva - voce held on ---------------------------

Internal Examiner External Examiner

We hereby declare that the project “TRAVEL MANAGEMENT SYSTEM”. submitted by

S.VIJAY in partial fulfillment of the requirement for the degree of BACHELOR OF

COMPUTER APPLICATION course of the university of madras is a record of the project

work done by both originally.

It is my grand pleasure to acknowledge the department of computer application prof.

I wish to extend my heart-felt gratitude respectful to the CHAIRMAN Mr.PUGALENDHI

STATION : Mr. S.VIJAY

CHAPTER TITLE PAGE NO

 It involves the management of multitude of activities such as studying

 A Travel Management System can use a database table to store

About Solution tool :

find details of placeman to book tickets.

and often the customer may be misguided

 The proposed system is a web based application and maintains a

and make necessary travel arrangements

bookings online for travel and accommodation

Hardware requirement for present project:

Processor : AMD PRO A4-4350B R4, 5 COMPUTE CORES

Hard disk : 500 GB

software requirement for present project:

Operating system : windows 10 pro

Front end : HTML, CSS, JAVASCRIPT

Back end : PHP

Process that transforms data flow

Source of destination of data

 A use case diagram is a graphical depiction of a user's possible interactions with a

Uses of entity relationship diagrams :

5.1 FRONT END

 Hypertext Markup Language (HTML) is the standard markup language for

 PHP (Hypertext Processor) is a general-purpose scripting language and

 The biggest strength of PHP :

 .MySQL, or My Structured Query Language, is a free, open-source relational

6.1 UNIT TESTING

4) Documentation: Unit testing provides a sort of living documentation of the system.

 The purpose of integration testing is to verify functional, performance, and reliability

6.3 SOFTWARE VERIFICATION AND VALIDATION

 In software project management, software testing, and software engineering,

● Validation: Are we building the right product?

● Software Verification: The process of evaluating software to determine whether the

6.3.2 Classification of Methods

In mission-critical software systems, where flawless performance is absolutely necessary,

6.4 Black-Box Testing

Black-box testing is a method of software testing that examines the functionality of an

6.4.1 Test Procedures

Specific knowledge of the application's code/internal structure and programming

6.4.2 Test Cases

 Input involves different types of requirements, functional specifications, detailed

6.6 SYSTEM TESTING

System testing of software or hardware is testing conducted on a complete, integrated system

System testing is performed on the entire system in the context of a Functional

7.1.3 User home page :

7.1.4 Contact Us:

7.1.5 Admin Dashboard:

$sel_user = "select * from admins where user_email='$email' AND

$run_pack = mysqli_query($con, $get_pack);