SYSTEM REQUIREMENT SPECIFICATIONS
Title: Travel and Tourism Management System
OBJECTIVE:
The objective of the project is to develop a system that automates the processes and activities of
a travel and tourism agency.
The purpose is to design a system using which one can perform all operations related to traveling
and sight-seeing.
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.
PROPOSED 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.
STUDY OF THE SYSTEM:
To provide flexibility to the users, the interfaces have been developed that are accessible through a
browser. The GUI’S at the top level have been categorized as
1. Administrative user interface
2. The operational or generic user interface
The ‘administrative user interface’ concentrates on the consistent information that is practically, part of the
organizational activities and which needs proper authentication for the data collection. These interfaces
help the administrators with all the transactional states like Data insertion, Data deletion and Date
updation along with the extensive data search capabilities.
The ‘operational or generic user interface’ helps the end users of the system in transactions through the
existing data and required services. The operational user interface also helps the ordinary users in
managing their own information in a customized manner as per the included flexibilities.
FEASIBILITY STUDY:
FEASIBILITY REPORT:
Preliminary investigation examines project feasibility, the likelihood the system will be useful to
the organization. The main objective of the feasibility study is to test the Technical, Operational and
Economical feasibility for adding new modules and debugging old running system. All systems are
feasible if they are given unlimited resources and infinite time. There are aspects in the feasibility study
portion of the preliminary investigation:
Technical Feasibility
Operation Feasibility
Economical Feasibility
TECHNICAL FEASIBILITY:
The technical issue usually raised during the feasibility stage of the investigation includes the following:
Does the necessary technology exist to do what is suggested?
Do the proposed equipments have the technical capacity to hold the data required to use the new
system?
Will the proposed system provide adequate response to inquiries, regardless of the number or
location of users?
Can the system be upgraded if developed?
Are there technical guarantees of accuracy, reliability, ease of access and data security?
OPERATIONAL FEASIBILITY:
Proposed projects are beneficial only if they can be turned out into information systems, which will
meet the organization’s operating requirements. Operational feasibility aspects of the project are to be
taken as an important part of the project implementation. Some of the important issues raised are to test
the operational feasibility of a project includes the following: -
Is there sufficient support for the management from the users?
Will the system be used and work properly if it is being developed and implemented?
Will there be any resistance from the user that will undermine the possible application benefits?
This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the
management issues and user requirements have been taken into consideration. So there is no question
of resistance from the users that can undermine the possible application benefits.
The well-planned design would ensure the optimal utilization of the computer resources and would help in
the improvement of performance status.
ECONOMIC FEASIBILITY:
A system can be developed technically and that will be used if installed must still be a good
investment for the organization. In the economical feasibility, the development cost in creating the system
is evaluated against the ultimate benefit derived from the new systems. Financial benefits must equal or
exceed the costs. The system is economically feasible. It does not require any additional hardware or
software.
FUNCTIONAL REQUIREMENTS:
Number of Modules
After careful analysis the system has been identified to have the following modules:
1. Administrator module
2. Travels module
3. Routes module
4. Reservations module
5. Testimonials module.
1. ADMINISTRATOR MODULE:
This module provides administrator related functionality. Administrator manages all information and
has access rights to add, delete, edit and view the data related to places, travels, routes, bookings,
restaurants etc.
2. TRAVELS MODULE:
This module provides the details of various travel agencies. A user can select the appropriate
agency depending on convenience and accessibility.
3. ROUTES MODULE:
This module provides information related to various routes connecting sources and destinations. For
each route, information such as source, destination, fare, reservation details, pick up points etc are
provides. Only administrator can add , delete, edit and manage the data. Users can only view the
information.
4. RESERVATIONS MODULE:
This module provides functionalities that allow a user to book tickets or cancel previously booked
tickets. The module maintains the details of all reservations made so far and allows administrator to either
confirm or reject the bookings.
5. TESTIMONIALS MODULE:
Users of this application can post their opinions, complaints and suggestions regarding this portal
and services to the administrator. Accordingly, the administrator can take various steps to act on the
complaints and suggestions.
NON-FUNCTIONAL REQUIREMENTS:
SOFTWARE REQUIREMENTS:
Operating System : Windows
Technology : Java and J2EE
Web Technologies : Html, JavaScript, CSS
IDE : My Eclipse
Web Server : Tomcat
Database : MySql5.0
Java Version : J2SDK1.5
HARDWARE REQUIREMENTS:
Hardware : Pentium
RAM : 1GB
INPUT DESIGN:
Input design is a part of overall system design. The main objective during the input design is as given
below:
To produce a cost-effective method of input.
To achieve the highest possible level of accuracy.
To ensure that the input is acceptable and understood by the user.
INPUT STAGES:
The main input stages can be listed as below:
Data recording
Data transcription
Data conversion
Data verification
Data control
Data transmission
Data validation
Data correction
INPUT TYPES:
It is necessary to determine the various types of inputs. Inputs can be categorized as follows:
External inputs, which are prime inputs for the system.
Internal inputs, which are user communications with the system.
Operational, which are computer department’s communications to the system?
Interactive, which are inputs entered during a dialogue.
INPUT MEDIA:
At this stage choice has to be made about the input media. To conclude about the input media
consideration has to be given to;
Type of input
Flexibility of format
Speed
Accuracy
Verification methods
Rejection rates
Ease of correction
Storage and handling requirements
Security
Easy to use
Portability
Keeping in view the above description of the input types and input media, it can be said that most of the
inputs are of the form of internal and interactive. As
Input data is to be the directly keyed in by the user, the keyboard can be considered to be the most
suitable input device.
OUTPUT DESIGN:
Outputs from computer systems are required primarily to communicate the results of processing to users.
They are also used to provide a permanent copy of the results for later consultation. The various types of
outputs in general are:
External Outputs whose destination is outside the organization.
Internal Outputs whose destination is with in organization and they are the User’s main interface
with the computer.
Operational outputs whose use is purely with in the computer department.
Interface outputs, which involve the user in communicating directly with the system.
OUTPUT DEFINITION
The outputs should be defined in terms of the following points:
Type of the output
Content of the output
Format of the output
Location of the output
Frequency of the output
Volume of the output
Sequence of the output
It is not always desirable to print or display data as it is held on a computer. It should be decided as which
form of the output is the most suitable.
For Example
Will decimal points need to be inserted
Should leading zeros be suppressed.
OUTPUT MEDIA:
In the next stage it is to be decided that which medium is the most appropriate for the output. The main
considerations when deciding about the output media are:
The suitability for the device to the particular application.
The need for a hard copy.
The response time required.
The location of the users
The software and hardware available.
Keeping in view the above description the project is to have outputs mainly coming under the
category of internal outputs. The main outputs desired according to the requirement specification are:
The outputs were needed to be generated as a hard copy and as well as queries to be viewed on the
screen. Keeping in view these outputs, the format for the output is taken from the outputs, which are
currently being obtained after manual processing. The standard printer is to be used as output media for
hard copies.
SDLC Methodology:
This document play a vital role in the development of life cycle (SDLC) as it describes the complete
requirement of the system. It means for use by developers and will be the basic during testing phase.
Any changes made to the requirements in the future will have to go through formal change approval
process.
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software
Development and Enhancement. This model was not the first model to discuss iterative development, but
it was the first model to explain why the iteration models.
As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts
with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering
efforts are applied at each phase of the project, with an eye toward the end goal of the project.
The steps for Spiral Model can be generalized as follows:
The new system requirements are defined in as much details as possible. This usually involves
interviewing a number of users representing all the external or internal users and other aspects of the
existing system.
A preliminary design is created for the new system.
A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-
down system, and represents an approximation of the characteristics of the final product.
A second prototype is evolved by a fourfold procedure:
1. Evaluating the first prototype in terms of its strengths, weakness, and risks.
2. Defining the requirements of the second prototype.
3. Planning an designing the second prototype.
4. Constructing and testing the second prototype.
At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors
might involved development cost overruns, operating-cost miscalculation, or any other factor that could,
in the customer’s judgment, result in a less-than-satisfactory final product.
