Software Requirements Specification Template

ICS261—SSAD

The following annotated template shall be used to complete the Software Requirements
Specification (SRS) assignment of WSU-TC CptS 322. The instructor must approve any
modifications to the overall structure of this document.

Template Usage:
Text contained within angle brackets (‘<’, ‘>’) shall be replaced by your project-specific
information and/or details. For example, <Project Name> will be replaced with either ‘Smart
Home’ or ‘Sensor Network’.

Italicized text is included to briefly annotate the purpose of each section within this template.
This text should not appear in the final version of your submitted SRS.

This cover page is not a part of the final template and should be removed before your SRS is
submitted.

Acknowledgements:
Sections of this document are based upon the IEEE Guide to Software Requirements
Specification (ANSI/IEEE Std. 830-1984).

WSU-TC CptS 322 Software Requirements Specification Template

Interactive System for Shortest path generation

Software Requirements Specification

1.0
21-10-2009

ABHISHEK KHANNA
AYUSH DHINGRA
KRITARTH ANAND

Prepared for
Indian Railways
 IMAGE SEARCH ENGINE

Revision History

Date Description Author Comments

Document Approval

The following Software Requirements Specification has been accepted and approved by the
following:
Signature Printed Name Title Date
Ayush Dhingra Software Eng.
Aman Kumar Bahl Software Eng.

Software Requirements Specification Page iii

 IMAGE SEARCH ENGINE

Table of Contents

REVISION HISTORY...............................................................................................................................................III
DOCUMENT APPROVAL....................................................................................................................................... III
1. INTRODUCTION.....................................................................................................................................................1
1.1 PURPOSE..................................................................................................................................................................1
1.2 SCOPE..................................................................................................................................................................... 1
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS............................................................................................................1
1.4 REFERENCES............................................................................................................................................................ 1
1.5 OVERVIEW...............................................................................................................................................................1
2. GENERAL DESCRIPTION.................................................................................................................................... 2
2.1 PRODUCT PERSPECTIVE.............................................................................................................................................. 2
2.2 PRODUCT FUNCTIONS................................................................................................................................................ 2
2.3 USER CHARACTERISTICS............................................................................................................................................ 2
2.4 GENERAL CONSTRAINTS.............................................................................................................................................2
2.5 ASSUMPTIONS AND DEPENDENCIES.............................................................................................................................. 2
3. SPECIFIC REQUIREMENTS................................................................................................................................ 2
3.1 EXTERNAL INTERFACE REQUIREMENTS.........................................................................................................................2
3.1.1 User Interfaces............................................................................................................................................. 2
3.1.2 Hardware Interfaces.................................................................................................................................... 3
It is a web based product hence will not require hardware devices.....................................................................3
3.1.3 Software Interfaces.......................................................................................................................................3
3.1.4 Communications Interfaces..........................................................................................................................3
3.2.1 Searching the query......................................................................................................................................3
3.3 USE CASES..............................................................................................................................................................3
3.3.1 Use Case Diagram for complete system ..................................................................................................... 3
3.3.2 Use Case Descriptions................................................................................................................................. 4
3.5 NON-FUNCTIONAL REQUIREMENTS.............................................................................................................................. 4
3.5.1 Performance.................................................................................................................................................5
3.5.2 Reliability..................................................................................................................................................... 5
3.5.3 Availability................................................................................................................................................... 5
3.5.4 Security.........................................................................................................................................................5
3.5.5 Maintainability.............................................................................................................................................5
3.5.6 Portability.................................................................................................................................................... 5
3.5.6 Other….........................................................................................................................................................5
3.7 DESIGN CONSTRAINTS............................................................................................................................................... 5
3.8 LOGICAL DATABASE REQUIREMENTS........................................................................................................................... 5
3.9 OTHER REQUIREMENTS..............................................................................................................................................5
5. CHANGE MANAGEMENT PROCESS................................................................................................................ 5
A. APPENDICES.......................................................................................................................................................... 6
A.1 APPENDIX 1............................................................................................................................................................ 6
A.2 APPENDIX 2............................................................................................................................................................ 6

Software Requirements Specification Page iv

 Image Search Engine

1. Introduction
1.1 Purpose

To select a train passengers look into many factors such as time taken, train changing,
availability etc . People have to search manually or need past knowledge to get the best route,
however this is time consuming and they can miss a better solution. Our system will give the
shortest possible routes considering the above mentioned factors in a sequential manner which
will be helpful to any passenger.

1.2 Scope

The system asks the details of the journey as it is on the web currently. The list of all the best
possible paths are shown in a decreasing order of priority, for a user .
The system will list routes which will allow users to change trains so that he can reach his
destination earlier or can use it if direct trains are not available.

1.3 Definitions, Acronyms, and Abbreviations

User Interface : UI
PHP – Hypertext preprocessor

MySQL – My Structured Query Language. An Open Source Implementation of the SQL92

DBMS – Data Base Management System

HTML – Hypertext Mark Up Language

1.4 References
IEEE. IEEE Std 8301998 IEEE Recommended Practice for Software Requirements

Specifications. IEEE Computer Society, 1998.

1.5 Overview
Section 2 gives a general description of the software and what all can be expected of it.
Section 3 gives the specific requirements for implementing the software and its needs.

Software Requirements Specification Page 1

 Image Search Engine

2. General Description

2.1 Product Perspective

The system is intended for passengers who want to know the best possible paths to reach a given
destination. Passengers get more options then what they are getting currently, which will be
beneficial to both the passengers and Indian Railways.

2.2 Product Functions

The system lists the routes to a user which he can select based on his preference. The user can
then book his tickets for that route directly instead of searching all of it manually. Additions are
possible by which the user can give his preferences whether he wants the shortest path or he
wants to change minimum number of trains etc . This makes the system more interactive.

2.3 User Characteristics

User should be able to use web-based system.
He should know what to search and he should have command on his language.

2.4 General Constraints

*need to list
The database should have sufficient space to store all the data .
The host server should be able to host PHP and have MySQL server installation.

2.5 Assumptions and Dependencies

Number of transactions should be within the server limits.

3. Specific Requirements
3.1 External Interface Requirements

3.1.1 User Interfaces

The interface will consist of HTML pages as it is currently on the website. A back end database
will be required which stores all possible routes.

Software Requirements Specification Page 2

 Image Search Engine

3.1.2 Hardware Interfaces

It is a web based product hence will not require hardware devices.
3.1.3 Software Interfaces
Home page for asking the query.
Database to store all the data .
The query will be processed to return the results back to the user.

3.1.4 Communications Interfaces

No communication interface is required.

3.2 Functional Requirements

This section describes specific features of the software project. If desired, some requirements
may be specified in the use-case format and listed in the Use Cases Section.
3.2.1 Searching the query

3.2.1.1 Introduction
Allows the user to enter his query.

3.2.1.2 Inputs
This will take the query to be searched from the user .

3.2.1.3 Processing
Match results for the query in the database and return the result.

3.2.1.4 Outputs
Display the searched results .

3.2.1.5 Error Handling

If there is no result for any query then appropriate message is displayed.

3.3 Use Cases

3.3.1 Use Case Diagram for complete system

Software Requirements Specification Page 3

 Image Search Engine

3.3.2 Use Case Descriptions

This case is related to when user enters his query ie word to be matched.
--then it invokes processing of that keywords.,
--that invokes sorting of that results and displaying them in a nice manner to the user,
--then user selects the desired page ,and
--that cause invokation of displaying that particular image in a nice manner with highlights.

3.5 Non-Functional Requirements

Non-functional requirements may exist for the following attributes. Often these requirements
must be achieved at a system-wide level rather than at a unit level. State the requirements in the
following sections in measurable terms (e.g., 95% of transaction shall be processed in less than

Software Requirements Specification Page 4

 Image Search Engine

a second, system downtime may not exceed 1 minute per day, > 30 day MTBF value, etc).
3.5.1 Performance

The performance is dependent on the data size . For around 30 documents the product gives the
result within 2 seconds .
3.5.2 Reliability
Reliability is much high. There are very less chances of crashing. With high database size we
may need to transfer data on other system/server that may cause failure, numbers depend on the
server.
3.5.3 Availability
It will be available 24 hrs .
3.5.4 Security
As we are not allowing user to do anything accept queries, and there is no authorization . The
URL and the data transferred in it is also encrypted .
3.5.5 Maintainability
New documents/books can be added .
3.5.6 Portability
The website should work on the web browsers Mozilla (v2.5 above) , Chrome and

Opera(v7.0 above).

3.5.6 Other….

3.7 Design Constraints

Specify design constrains imposed by other standards, company policies, hardware limitation,
etc. that will impact this software project.

3.8 Logical Database Requirements

Will a database be used? If so, what logical requirements exist for data formats, storage
capabilities, data retention, data integrity, etc.

3.9 Other Requirements

Catchall section for any additional requirements.

5. Change Management Process

Identify and describe the process that will be used to update the SRS, as needed, when project
scope or requirements change. Who can submit changes and by what means, and how will these
changes be approved.

Software Requirements Specification Page 5

 Image Search Engine

A. Appendices
Appendices may be used to provide additional (and hopefully helpful) information. If present,
the SRS should explicitly state whether the information contained within an appendix is to be
considered as a part of the SRS’s overall set of requirements.

Example Appendices could include (initial) conceptual documents for the software project,
marketing materials, minutes of meetings with the customer(s), etc.

A.1 Appendix 1

A.2 Appendix 2

Software Requirements Specification Page 6