Computer Science & Engineering: by Rishabh Kumar Dixit 1531110043 Software Engineering Lab (NCS 652)

SRS
On
Travel and Tourism Management System
Bachelor of Technology
In
Computer Science & Engineering

By
Rishabh Kumar Dixit
1531110043
Software Engineering Lab (NCS 652)
Submitted to:-
Mr. Nitin Goyal
Department of Computer Science & Engineering

DEWAN V.S. INSTITUTE OF ENGINEERING & TECHNOLOGY,
MEERUT
Approved By A.I.C.T.E., New Delhi
Affiliated to Dr. A.P.J. Abdul Kalam Technical University, Lucknow, Uttar Pradesh
Software Requirements Specification Page ii
Table of Contents
1. INTRODUCTION.....................................................................................................................................................1
1.1 PURPOSE...............................................................................................................................................................1
1.2 SCOPE...................................................................................................................................................................1
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS................................................................................................1
1.4 REFERENCES.........................................................................................................................................................1
2. GENERAL DESCRIPTION....................................................................................................................................2
2.1 PRODUCT FUNCTIONS...........................................................................................................................................2
2.1.1 sightseeing tours...................................................................................................................................................2
2.1.2 hotels......................................................................................................................................................................2
2.1.3 billing.....................................................................................................................................................................2
2.1.4 report generation...................................................................................................................................................2
2.2 USER CLASSES AND CHARACTERISTICS................................................................................................................2
2.2.1 customer.................................................................................................................................................................2
2.2.2 manager.................................................................................................................................................................2
2.2.3 administrator.........................................................................................................................................................2
3. SPECIFIC REQUIREMENTS................................................................................................................................3
3.1 EXTERNAL INTERFACE REQUIREMENTS...............................................................................................................3
3.1.1 User Interfaces………………………………………………………………………………………………………3
3.1.2 Hardware Interfaces……………………………………………………………………………………………….3
3.1.3 Software Interfaces………………………………………………………………………………………………….3
3.2 FUNCTIONAL REQUIREMENTS...............................................................................................................................3
3.2.1 number of modules.......................................................................................................................................3
3.3 NONFUNCTIONAL REQUIREMENTS......................................................................................................................3
3.3.1 Performance reuirements............................................................................................................................3
3.3.2 Security requirements..................................................................................................................................3
3.3.3 software quality attributes...........................................................................................................................3
3.4 DESIGN CONSTRAINTS..........................................................................................................................................3
3.4.1 input design............................................................................................................................................................3
3.4.2 input stage..............................................................................................................................................................3
3.4.3 input
type................................................................................................................................................................3
3.4.4 input
media.............................................................................................................................................................3
3.4.5 output design..........................................................................................................................................................3
3.4.6 output definition.....................................................................................................................................................3
3.4.7 output media..........................................................................................................................................................3
3. 5 SYSTEM FLOWCHART..........................................................................................................................................3
3.6 LOGICAL DATABASE REQUIREMENTS......................................................................................................3
4. ANALYSIS MODELS............................................................................................................................................13
4.1 SEQUENCE DIAGRAMS..........................................................................................................................................4
4.2 DATA FLOW DIAGRAM (DFD).......................................................................................................................4
4.3 ER DIAGRAM......................................................................................................................................................4
4.4UML .....................................................................................................................................................................4
4.5 ACTIVITY DIAGRAM.......................................................................................................................................4
4.6 CLASS DIAGRAM.............................................................................................................................................4
4.7 COLLABORATION DIAGRAM........................................................................................................................4
Software Requirements Specification Page ii
1. Introduction
1.1 Purpose
 The objective of this 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 travelling and
sight-seeing.
1.2 Scope
The Travel and Tourism management system is an implementation of tourism website which helps the
customers to search the availability of various tourist places and prices of various hotel rooms in particular
places, along with the different packages available with the reservations. It covers various features like online
registration of the users, modifying the details of the website by the management staff or administrator of the
website by adding, deleting or modifying the customer details or packages information. In general, this website
will be designed to perform like any other travel and tourism website available online.
1.3 Definitions, Acronyms, and Abbreviations
TERM DEFINITION
Active article The document that is tracked by the system. It is a narrative that is planned to be posted to
the public website.
Author Person submitting an article to be reviewed. In case of multiple authors, this term refers to
the principal author, with whom all communication is made.
Database Collection of all information monitored by this system.
Editor Person who receives article, sends article for review and makes final judgments for
publication.
Field A cell within a form.
History Society The existing membership database(also known as HS Database).
Database
Member A member of the historical database as listed in the historical database.
Reader Anyone visiting the site to read the articles.
Review A written recommendation for the appropriateness of the article for publication. It may
include suggestions for improvement.
Reviewer A person that examines the an article and has the ability to recommend approval of the
article for publication or to request changes that be made in the article.
Stakeholder Any person with an interest in the project who is not a developer.
User Reviewer or author
1.4 References
IEEESTD 8301998 IEEE Recommended practice for Software Requirement.
1.4.1 Books
Software Requirements Specification Page 1
 ASP.NET 3.5 BLACK BOOK
BY:- Kogent Solution Inc. dream tech PLATINUM EDITION
 The Complete Reference ASP.NET
BY:- Mackdonald Melthew (TMH)
 System Analysis and Design Software Application
BY:- Brian Siler and Jeff Spots
1.4.2 Websites
 www.google.com
 www.codeguru.com
 www.saveearth.org
 www.saveourearth.co.uk
 www.scribd.com/doc
2. General Description
2.1 Product Functions
Thus, this system like self-containing shell, that covers all the major aspects in the computerization of tourisr
agency. Some tasks are described in detailed :-
2.1.1 Sight-Seeing Tours
Tourists can enjoy sight-seeing to any of the place, listed in agency's data file. Before that customer has to make
the booking by registering his/her name in data file and informing date of journey and number of operations.
2.1.2 Hotels
Agency also makes reservation for the hotels registered with the agency.
2.1.3 Billing
Once the customer make the booking or reservation, bill will be generated for him/her, and money has to be
paid on the spot itself.
2.1.4 Report Generation
Details about the location, hotels in that location and final report on the journey fare.
2.2 User Classes and Characteristics
2.2.1 Customer
The one who uses the system, for which the system is created.
2.2.2 Manager
The one who manages the system.

2.2.3 Administrator
The one who operates the system- adds, delete, or modifies the customer record in databases.
3. Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
3.1.2 Hardware Interfaces
3.1.2.1 Hardware Specifications :-
Processor :- Pentium IV
Speed :- 2.0 GHz or above
Hard-Disk :- 40 GB
RAM :- 512 MB
CD-Drive :- 48x
Input Devices :- Keyboard and mouse
Monitor :- Compatible monitor with 800x600 resolution
Internet :- 100 kbps or above
Printer :- Any printer compatible for windows
3.1.3 Software Interfaces
3.1.3.1 Software Specifications:
Operating system :- Windows XP or higher version

Front-end :- ASP.NET
Back-end :- SQL
3.2 Functional Requirements
3.2.1 Number of modules
After careful analysis, the system has been identified to have the following modules:
3.2.1.1 Administrators module
3.2.1.2 Travels module
3.2.1.3 Routes module
3.2.1.4 Reservations module
3.2.1.5 Testimonials module
3.2.1.1 Administrators 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.
3.2.1.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.2.1.3 Routes module
This module provides information related to various routes connecting sources and destination. For each route,
information such as source, destination, fare, reservation details, pick up points etc are provided. Only
administrator can add, delete, edit and manage the data. Users can only view the information.
3.2.1.4 Reservation module
This module provide 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
bookings.
3.2.1.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.
3.3 NonFunctional Requirements
3.3.1 Performance requirements
The Travel and 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 for a particular information. 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.
3.3.2 Security Requirements
It must be ensured that access will be provided to the authorized persons through userid and password.
Network Security will be provided by the use of firewalls.
Checks can be performed at regular intervals to ensure data integrity.
3.3.3 Software Quality Attributes
3.3.3.1 Reliable :
For all services that rely on TMS for access control, lack of availability of the supported services. The product
should not crash under any circumstance such as user entering invalid values, user trying to find unusual data
etc. It should show appropriate message for every user generated message.
3.3.3.2 Transparent :
Ideally, the user should not be aware that authentication is taking beyond the requirement to enter a password.
3.3.3.3 Scalable :
The system should be capable of supporting large number of clients and servers. This suggests modular,
distributed architecture.
3.3.3.4 Portable :
Our product should be portable to carry and will run in any machine provided it runs on Windows Operating
System.
3.4 Design Constraints
3.4.1 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 costeffective method of input.
 To achieve highest possible level of accuracy.
 To ensure that the input is acceptable and understood by the user.
3.4.2 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
3.4.3 Input Type
It is necessary to determine various types of inputs. Inputs can be categorized as follows :
 External Inputs, which are prime inputs for the system.
 Internal Inputs, which are user communication with the system.
 Operational, which are computer department's communication to the system.
 Interactive, which are inputs entered during a dialogue.
3.4.4 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 of the descriptions 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 directly keyed in by the user, the keyboard can be
considered to be the most suitable input device.
3.4.5 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 output in
general are :
 External outputs, whose destination is outside the organization.
 Internal outputs, whose destination is within the organization and they are the user's main interface with
the system.
 Operational inputs, whose use is purely within the computer department.
 Interface outputs, which involve the user in communicating directly with the system.
3.4.6 Output Definition
The output 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 zeroes be suppressed.
3.4.7 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 projects 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.
 The queries to be viewed on a 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.
3.5 System Flowchart
3.6 Logical Database Requirements
All the data will be stored in a database.
4. Analysis Models
4.1 Sequence Diagrams
4.2 Data Flow Diagrams (DFD)
4.3 ER Diagram
4.4 UML Diagram
4.5 Activity diagram
4.6 Class Diagram
4.7 Collaboration Diagram

Computer Science & Engineering: by Rishabh Kumar Dixit 1531110043 Software Engineering Lab (NCS 652)

Uploaded by

Document Information

Original Title

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

Computer Science & Engineering: by Rishabh Kumar Dixit 1531110043 Software Engineering Lab (NCS 652)

Uploaded by

Copyright:

Available Formats

SRS

Travel and Tourism Management System

Computer Science & Engineering

Rishabh Kumar Dixit

Software Engineering Lab (NCS 652)

Department of Computer Science & Engineering

2.1.1 Sight-Seeing Tours

2.1.4 Report Generation

The one who manages the system.

3.1.2.1 Hardware Specifications :-

Operating system :- Windows XP or higher version

You might also like