2. Content
■ Introduction
■ Problem Statement
■ Objectives
■ System Analysis & Design
Requirement Analysis
Feasibility
ER Diagram
Data Flow Diagram (DFD)
■ Design
Architecture
Schema
Interface
■ Implementation
Tools Used
■ Learning Objectives
■ Conclusion
■ Future Recommendation
■ Reference
3. Introduction
■ Travel Management System is a system used to book a tour from anywhere in
the world by a single dynamic website which will help user o know all about
the places and tour details via single website.
■ TMS provides reservation facility to the customers.
■ This is a real-time website, so the admin will be the director of the
organization.
■ This system moreover provides a better way to connect with various events.
■ It encourages to expansion of tourism ,so that they enhances the tourism
sector.
4. Problem Statement
■ There will be many user visiting the sites and hence we require a strong &
reliable frontend which can withhold the users on sites.
■ It requires more human efforts to manage the each and every aspects which is
very costly process.
■ We need strong database where data will be stored.
■ Our priority will be customers and their travel requirements.
5. Objectives
1. To develop online booking package system for travelling.
2. This system is made as user friendly as possible so that any one can use it with little
knowledge.
3. The booking system will reduce the tedious job of system paperwork by keeping all
details are stored in a database.
4. Make easy booking system, moreover less time consuming as compared to manual work.
5. Make strong relationship with customers so that they can enjoy holidays.
8. Functional Requirement
Admin module:
1. Admin can manage the user and receive package from traveler & package management.
2. This module provides administrator related functionality.
3. Administrator manages all information and has access rights to add, delete, edit and view the data
related to places, travels, routes, bookings, etc.
Travels Module:
1. This module provides the details of various travel agencies. A user can select the appropriate
agency depending on convenience and accessibility.
Customer:
1) Customer can view package and booking.
2) This module helps to customer.
9. Non Functional Requirements
Efficiency Requirement
The efficiency of a software system refers to how well it handles capacity, throughput, and response time.
Reliability Requirement
The degree to which the software system regularly executes the stated functions without failure is referred to
as reliability. User registration, login was all performed accurately by the system
Usability Requirement
The system’s usability criteria state how simple it must be to use. The system was created in a user-friendly
environment so that users and administrators could easily and successfully complete various activities in the
system.
Implementation Requirement
The process of turning strategies and plans into actions in order to achieve strategic objectives and goals is
known as implementation. The frontend was created using HTML, CSS, JS and Bootstrap with PHP
serving as the server-side programming language for database connectivity at the backend i.e., MySQL was
utilized to develop the database.
10. Feasibility Analysis
■ Feasibility Analysis
i. Technical Feasibility
Generally, new system brings new technology into an organization. The proposed system requires technology and
equipment, which can be obtained. the operating system has the technical capacity to hold the data required to use the
proposed system..
ii. Operational Feasibility
The current system is manual. Thus, processing large amount of data becomes a cumbersome activity. Reports that are
generated are difficult to prepare manually and are also error prone. Operationally the Proposed system is feasibility
because there are sufficient supports for project from management.
iii. Economical Feasibility
The project we are developing is within the cost estimation by the organization. This system does not have any
requirement of expensive hardware and software. The platform are open sources and the resources required for the
project are also open source
iv. Schedule Feasibility
Schedule should be precise and accurate for the timely completion of the project. This project can be completed and
delivered within the time limit of the schedule..
13. Second level Data Flow Diagram for ADMIN
First level Data Flow Diagram for ADMIN
DFD of Admin
14. Second Level Data Flow Diagram For Customer
First level Data Flow Diagram for Customer
DFD of Customers
15. Design
■ Architectural Design
• The next phase of
design will be planning
the architecture of the
application.
• There will be in some
cases a separation of
the user interface and
data.
• Data will be stored in an
SQL database.
• To query the database
and code behind for
server-side scripting will
be in PHP.
16. Database Schema Design
• The design of the database
is called a schema. This tells
us about the structural view
of the database.
• It gives us an overall
description of the database.
• A database schema defines
how the data is organized
using the schema diagram.
19. Learning Outcome
■ With the completion of this project, it was possible to
achieve the project’s goal.
■ After filling the register form, user can book packages
online through web browser.
■ In this way user can save time and book Packages online
from this website.
20. Conclusion
■ Here we have presented the design of a tour management system
that can provide the users with the required tourism guidance
required anytime and anywhere.
■ This is a combination of smartphone and Internet services.
■ The tour management website contributes a reasonable way for
the users to schedule their trips, since it provides detailed
information about the tourist places including description,
image.
■ This process achieves its main goal by pertaining to real time
data.
21. Future Recommendation
In the future it will enhanced by providing Tour and Travels Management System for
multiple cities on our websites.
In future, we will give facility of online donation.
We will include more functionality as per user require.
Multiple package can booked by one customer at a time.
Updated feature should enhanced for all modules.
Real-time feedback facility available on our website.
Travels management system will try to serve all expectations.
No Emails alerts are sent to user about reservation/cancelation.
Online payment option.
22. Refrences
Arminen, I. and Poikus, P., 2009. Diagnostic reasoning in the use of travel management system. Computer Supported
Cooperative Work (CSCW)
Brochhausen, Ewald, Markus Melzer, Marcus Thurner, and Hendrik Vordenbäumen. SAP Travel Management. Galileo
Press, 2004.
Brochhausen, E., Melzer, M., Thurner, M. and Vordenbäumen, H., 2004. SAP Travel Management. Galileo Press.
Chang, Han-Bin, et al. "An intelligent travel book management system." International Journal of Ad Hoc and
Ubiquitous Computing 4.6 (2009).
Chang, Han-Bin, Hsuan-Pu Chang, Hui-Huang Hsu, Louis R. Chao, and Timothy K. Shih. "An intelligent travel book
management system." International Journal of Ad Hoc and Ubiquitous Computing 4, no. 6 (2009).
