1.

INTRODUCTION
1.1 Purpose

The objective of the project is to develop a system that automates the processes and
activities of a travel agency. 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. It will explain the
purpose and features of the system, the interfaces of the system, what the system will do,
the constraints under which it must operate and how the system will react to external
stimuli. This document plays a vital role in the development of life cycle (SDLC) as it
describes the complete requirement of the system.

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 Product Scope

The Flight Reservation System project is an implementation of a managing Booking website

which helps the customers to search the availability of various flight and their prices. This
system also gives services such as online registration of users and management of log files
by the administrator of the system. This system will be designed to maximize the
productivity by providing tools to assist in automating the customer feedback and
information processing which would otherwise have to be performed manually.

1.4 Product Functions

This system like a self-containing shell, that covers all the major aspects in the
computerization of tourist agency.
1. The Customer has to make the booking by registering his/her name in Data-File,
informing date of journey and number of members along with other essentials.
2. Once the Customer makes the booking or reservation, a receipt will be generated for
him/her, and money has to be paid online.
3. A report is generated consisting of the details about the flight that has been booked
and flight fare and shown to the user.

1
2. Overall Description
2.1 Product Perspective

The proposed system shall be developed using pooled System Architecture and will be
compatible with Microsoft Windows Operating System. The product aims at activity
collaborative resource pooling and problem-solving using peer-to-peer learning. This is a
self-centered product and its data is restricted to its users and secured.

2.2 User Classes and Characteristics

There will be three user classes for this software system. One user class will be the
customers, other user class will be the agencies and the third user class will be the
management personnel handling the system. The Characteristics of all the classes are given
below:
Customers-
1. The User Interface should be simple and easy to access.
2. They should not require any technical expertise.
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.

11.Cost Constraints
The main constraint for this project will be the development cost. Since the software will be
an open source software and distributed free of cost the development cost should be very
less. At the same time, the security of the system should not be compromised.

2
3. EXTERNAL INTERFACE REQUIREMENTS
3.1 User Interfaces

 Login: To allow the users to use the system.

 Flight Details: To avail appropriate details and information of the flights available.
 Passenger Details: To avail appropriate information of the passengers.
3.2 Hardware Interface

Device should be enabled with internet. The web app will be developed to work on
touchscreen panels as well as conventional computers. The panel or the computer should
support HTML 5.

3.3 Software Interface

 Operating System: We have chosen Windows operating system for its best support and
user-friendliness.
 Database: To save the records we have chosen MYSQL database.
 Java: To implement the backend of the project we have chosen Java language for its more
interactive support.
 Front End: To implement front-end of the project we have chosen HTML, CSS, JavaScript.

4.SYSTEM FEATURES

3.1 Registration

Customer will need account to log in to the system. The first-time user can register on the
software using his/her

Input:

 Name,
 Email-id
 Contact number
 Password

Output:

Then he/she can create a unique account to access the portal.

3.2 Login

An existing user can use his email ID and password to login to the software.

For Customer

3
Input:

 Email ID
 Password

Output:

The message of successful login will be displayed and the user can access the website. The
message of unsuccessful login will be displayed if the credentials are invalid.

4.4 Select Location and Date

The user selects the desirable location, date and time of the journey from the Selection tab
of the portal.

Input:

 Location
 Date

Output:

After the required selection, a list of available flights along with their estimated price is
displayed for further perusal.

4.5 View Flights

The users will be provided with flight details on the portal. These details will be added or
modified by the admin in charge of the portal. The user further enters the required details-
location (to and from), date of journey, number of passengers, credentials of each
passenger. Once the user has selected the desirable flight, s/he can save it on the portal
using the ‘Add to Cart’ option or book it using the ‘Book My Flight’ option.

Input

The customer will navigate through View Flights section of the system.

Output

All the details about various flights will be displayed along with their respective estimated
charges.

4.6 Add to Cart

The selected flights are added to a cart which acts as the database for the user accessing it.
This marks as the reservation of services further accompanied by ‘Make payment’ tab.

4.7 Book Flight

4
 The user can select from the list of displayed flights and continue with the payment
process.
4.8 Payment and Receipt Generation
After all the selection and booking, the user is guided to the payment page wherein he’s
accustomed to have a mean for online payment to facilitate the booking process. After
successful booking of the flight, a receipt is generated and showed to the user.

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.

5
5.5 Business Rules

As this is an open source software, the developers will not be responsible of any loss or
damage done after implementing the system. The person or organization implementing the
software will have to bear any losses occurred due to malicious use or malfunctioning.