Software Requirment Specification

Introduction :-  A software requirements specification (SRS) is a detailed description of a software system to be developed with its functional and non-functional requirements. The SRS is developed based the agreement between customer and contractors. It may include the use cases of how user is going to interact with software system. The software requirement specification document consistent of all necessary requirements required for project development. To develop the software system we should have clear understanding of Software system. To achieve this we need to continuous communication with customers to gather all requirements.

A good SRS defines the how Software System will interact with all internal modules, hardware, communication with other programs and human user interactions with wide range of real life scenarios. Using the Software requirements specification (SRS) document on QA lead, managers creates test plan. It is very important that testers must be cleared with every detail specified in this document in order to avoid faults in test cases and its expected results.

 

Why Use an SRS Document?

Software development requirements specify what features the software product should have and what the product’s objective is.

How you approach these requirements can make all the difference for the development process and, ultimately, for the end-product as well.

Clearly defining software development requirements matters, because this can:

v    Ensure project consistency

v    Save time and money

v    Provide a base for collaboration

v    Provide stability in case of unexpected changes

v    Make sure the entire software project doesn’t fail

 

What Is The Software Requirements Specification Document

Your first step is to create an outline for your software requirements specification. This may be something you create yourself. Or you may use an existing SRS template.

If you’re creating this yourself, here’s what your outline might look like:

1. Introduction

1.1 Purpose

1.2 Intended Audience

1.3 Intended Use

1.4 Scope

1.5 Definitions and Acronyms

2. Overall Description

2.1 User Needs

2.2 Assumptions and Dependencies

3. System Features and Requirements

 3.1 Functional Requirement

  3.2 External Interface Requirements

   3.3 System Features

     3.4  Nonfunctional Requirements

Templet

Sr. No.	URS ID	URS Requirement	SRS ID	SRS Description
1	URS -01	Password Complexity	SRS-01	How to Comply Password Complexity Requirement.
2
.
.
n

Software Requirements Specification vs. System Requirements Specification

A software requirements specification (SRS) includes in-depth descriptions of the software that will be developed.

A system requirements specification (SyRS) collects information on the requirements for a system.

“Software” and “system” are sometimes used interchangeably as SRS. But, a software requirement specification provides greater detail than a system requirements specification.