Software Requirements

Specification
for

ONLINE TOUR AGENCY

Version 1.0 approved

Prepared by Chinmay Panchal

Chanchal Prajapat

Durgesh Kumawat

Raghunandan Yadav

SIR PADAMPAT SINGHANIA UNIVERSITY

19 Aug 2011

Software Requirements Specification for <Project>

Page iii

Table of Contents
Table of Contents ......................................................................................................................... iii
Revision History ........................................................................................................................... iii
1. Introduction ............................................................................................................................. 1
1.1
1.2
1.3
1.4

Purpose ............................................................................................................................................. 1
Document Conventions .................................................................................................................... 1
Intended Audience and Reading Suggestions .................................................................................. 1
Project Scope.................................................................................................................................... 1

2. Overall Description ................................................................................................................. 2

2.1
2.2
2.3
2.4
2.5
2.6
2.7

Product Perspective .......................................................................................................................... 2

Product Features ............................................................................................................................... 2
User Classes and Characteristics ..................................................................................................... 2
Operating Environment .................................................................................................................... 2
Design and Implementation Constraints .......................................................................................... 3
User Documentation....................................................................... Error! Bookmark not defined.
Assumptions and Dependencies....................................................................................................... 3

3. System Features ....................................................................................................................... 3

3.1 System Feature 1 .............................................................................................................................. 3
3.2 System Feature 2 (and so on) ......................................................... Error! Bookmark not defined.

4. External Interface Requirements........................................................................................... 6

4.1
4.2
4.3
4.4

User Interfaces ................................................................................................................................. 6

Hardware Interfaces ......................................................................................................................... 6
Software Interfaces .......................................................................................................................... 6
Communications Interfaces .............................................................................................................. 6

5. Other Nonfunctional Requirements ...................................................................................... 6

5.1
5.2
5.3
5.4

Performance Requirements .............................................................................................................. 6

Safety Requirements ........................................................................................................................ 6
Security Requirements ..................................................................................................................... 7
Software Quality Attributes ............................................................................................................. 7

6. Other Requirements ................................................................................................................ 7

Appendix A: Glossary ......................................................................Error! Bookmark not defined.
Appendix B: Analysis Models .........................................................Error! Bookmark not defined.
Appendix C: Issues List ...................................................................Error! Bookmark not defined.

Revision History
Name

Date

Reason For Changes

Version

Page 1

1. Introduction
1.1 Purpose
Purpose of this project is to make online Tour Agency .This will facilitates the customer go online
select the tour package of their choice and register. This website provide will detail information of
each package available which will benefit the user to get services of Tour Agency from anywhere.

1.2 Document Conventions

Convention
www
Tour Agency
DB2
ASP
UML

Description
World Wide Web
Online Tour Agency
DB2 Database
Active Server Pages
Unified Modeling Language

1.3 Intended Audience and Reading Suggestions

The Software is intended to be guide for developers ,users and testers .The goal of this software is
to fulfill the requirement of Customers ,Agents and other people who are planning to tour.

1.4 Project Scope

We describe what features are in the scope of the software and what are not in the scope of the
software to developed. In scope Create different System users and assign different roles with related permissions.
Manage all the account details such as user name, phone number, address, websites and
email addresses of the entire user from one central location.
Track all the users and their contact details.
Confirmation of the end user identity and will verify which users are authorize to receive
support.
Maintain history of each user and their related information.
User can take print of their registration confirmation.
Having collaboration with various companies.
User can contact various companies directly.

Page 2

2. Overall Description
2.1 Product Perspective

The Web pages are present to provide the user interface on customer client side.
Communication between customer and server is provided through HTTP/HTTPS protocols.
The Client software is to provide the user interface on system user client side.
On the server side server,DB2 and database server is for storing the information.

2.2 Product Feature

Track Account Level Data: In this module, receivables from customer are maintained.
User Contact Information: It maintains all the detail (Personal, Contact) of the customer.
Maintaining Logs: Activities of the System Users can be tracked through logs, which are
maintained by the system.

2.3 User Classes and Characteristics

Every user should be comfortable of working with computer and net browsing .He must have basic
knowledge of English too.

2.4 Operating Environment

Page 3

Windows 7, XP, Vista

Very simple software no platform is requiring.

2.5 Design and Implementation Constraints

Interface is provided only in English language.

Login and password is used for identification of customer and there is no facility for guest.
This system is working for single server.
There is no maintainability of back up so availability will get affected.

2.6 Software Interface

Client on Intranet: Client software, Web Browser, Operating System(any)

Data Base Server:DB2,Operating System(any)
Development End: Advanced Java
DB2 ,OS(Windows)

2.7 Assumptions and Dependencies

Once the client book the package, the client can not be change or modify the package .
For online booking the client must have valid debit/credit/visa card.

3. System Features
3.1 System Feature 1
3.1.1

Description and Priority

Projects priority is medium and its cost may be less than other high level project .

3.1.2

Stimulus/Response Sequences
USE CASE:
A use case is a set of scenarios that describing an interaction
between a user and a system. A use case diagram displays the relationship
among actors and use cases. The two main components of a use case
diagram are use cases and actors.

Page 4

An actor is represents a user or another system that will interact with the system
you are modeling. A use case is an external view of the system that represents some
action the user might perform in order to complete a task.

ER Diagram

Page 5

Page 6

4. External Interface Requirements

4.1 User Interfaces
User Friendly:- The proposed system is user friendly because the retrieval and storing of data is
fast and data is maintained efficiently. Moreover the graphical user interface is provided in the
proposed system, which provides user to deal with the system very easily.
Reports are easily generated: reports can be easily generated in the proposed system so user
can generate the report as per the requirement (monthly) or in the middle of the session. User can
give the notice to the students so he/she become regular.
Very less paper work: The proposed system requires very less paper work. All the data is feted
into the computer immediately and reports can be generated through computers. Moreover work
become very easy because there is no need to keep data on papers.
Computer operator control: Computer operator control will be there so no chance of errors.
Moreover storing and retrieving of information is easy. So work can be done speedily and in time.

4.2 Hardware Interfaces

4.3 Software Interfaces
SOFTWARE SPECIFICATIONS:
Software
OS
Front end
Back End

Visual basic
Windows 7
C# and .net
DB2

4.4 Communications Interfaces

For communication interface we us the web browser to interact with each other .Our system is
online so it work on the server .For this we use the ip address.

5. Other Nonfunctional Requirements

5.1 Performance Requirements
The proposed system that we are going to develop will be used as the Chief performance system
within the different campuses of the university which interacts with the university staff and
students. Therefore, it is expected that the database would perform functionally all the
requirements that are specified by the university.

Page 7

5.2 Safety Requirements

The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup.

5.3 Security Requirements

We are going to develop a secured database for the university. There are different categories of
users namely teaching Administrator, Staff members and students etc. Depending upon the
category of user the access rights are decided. It means if the user is an administrator then he can
be able to modify the data, delete, append etc. All other users other than University Staff only have
the rights to retrieve the information about database.

5.4 Software Quality Attributes

The Quality of the database is maintained in such a way so that it can be very user friendly to all
the users of the database.