1.

INTRODUCTION

1.1 Purpose

In today’s day and age people often need a break from their busy lives to spend some time
with family and friends or simply travel for there own purpose but never get satisfactory
hotels, transport facilities and destination brochure. This motivated us to create a tourism
management system which helps the travellers experience a better and satisfactory journey
from the start to end.

1.2 Document Conventions

This document is formed using IEEE template for System Requirement Specifications (SRS)
documents. Headings are in bold capital letters and wherever necessary, diagrams are
provided.

1.3 Intended Audience and Reading Suggestions

The intended audience for this document includes the interested software developers and
the travel agents who are going to use this software. This project is being developed under
the guidance of Prof. Preeti Khare and Prof. Jyoti Thakur. This software is also useful for the
customers directly accessing the website.

1.4 Product Scope

The Tourism Management System project can prove to be immensely useful for the
travellers and travel agents with no or little management facilities. There are annually 1652
million domestic travellers in our country according to the statistic provided by ministry of
tourism. This huge number of travellers who need an affordable and comfortable journey
can use this software to find their suitable option.

2. Overall Description

2.1 Product Perspective

2.2 User Classes and Characteristics

2.3 Operating Environment

Operating System: Windows

Database: MySQL

2.5 Design and Implementation Constraints

1. Application Functionality- The application through which the customers take the services
should be well-functioning, error-free and easy to understand.

2. Time- No time lag to be witnessed during the service.

3. Based completely on Windows functionality platform.

4. The software should be portable and must be inaccessible to unauthorized users.

5. Internet Connectivity

6. Investment

7. Large data storage capacity

8. Considerable RAM size for smooth working

9. Maintenance and timely updating.

10. Credible analysis of students’ feedback.

3. EXTERNAL INTERFACE REQUIREMENTS

3.1 User Interfaces

3.2 Hardware Interface

Device should be enabled with internet.

3.3 Software Interface

● The project supports all types of web browsers.

 ● All the student details are highly secured and privacy is maintained.

4.SYSTEM FEATURES

5. OTHER NON-FUNCTIONAL REQUIREMENTS

5.1 Performance Requirements

The Tourism management System application should be able to respond to the queries
submitted by the customer without much delay. When a user searches for a tour location,
the application should not take much time to return the results, similarly for the motel and
package information. Considering that the application is of moderate size, it should be able
to display 10 results at a time on each page, when the customer looks up for any particular
data. Since the Online tourism websites have much traffic, the user should also be able to
logon to the system using high speed internet. Most of the requests sent to the application
should be answered in less than 5 seconds.

5.2 Safety Requirements

The database may get crashed or damaged due to some viruses or operating system
requirements. Therefore, it is necessary to have backup for your data. UPS/Inverter facility
should be there in case of power failure.

5.3 Security Requirements

It must be ensured that access will be provided to the authorized persons

through user ID and password. Network security will be provided by the use of firewalls.
Checks can be performed at regular intervals to ensure data integrity.

5.4 Software Quality Attributes

-Availability: Checking that the system has always something to function and generates a
pop-up error message in case of component failure.

-Usability: Checking that the system is easy to handle and navigates in the most expected
ways with no delays.

-Functionality: Checking that the system provides the right tools for editing questions
databases, creating session tests and analyzing them.