SRS Software Requirement Specification

SRS Software Requirement Specification is a document or comprehensive description that capture detail user specified requirement (functional and non functional) of software application. SRS in Software Engineering may include set of use cases that describes the user interaction that system must provide. It is system requirement specification which provide structural collection of information that embodies the system requirements.

It specify, identify, guide and define complete user requirement.

According to IEEE, Establish the basis for agreement between the customers and the suppliers on what the software product is to do.

SRS is complete description of the functions to be performed by the software specified in the document will assist the prospective users to determine if the software specified meets their needs or how the software must be modified to meet their needs.”

SRS is a one type of contract or agreement between client and company which addresses requirement, design constraints, functionality, interfaces, implementation environment, Quality, Safety, Operational, Reliability, Performance and quality attributes.

Advantage of SRS
– Provide detail description of user requirement

– Reduce effort

– Provide better estimations cost and schedule

– Effective verification and validation testing

– Used to prepare test plan

– Facilitate transfer and prospect enhancement for new user

SRS should include on the basis of IEEE
– Correct

– Unambiguous

– Complete

– Consistent

– Ranked for importance and/or stability

– Verifiable

– Modifiable

– Traceable

SRS captures various requirements like functional, performance, interface, maintainability, reliability, safety, quality, operational and resource

SRS Software Requirement Specification should include
1 Introduction
1.1 Purpose

1.2 Scope

1.3 Definition- Abbreviations

1.4 References

2 Overall Description
2.1 Product perspective

2.2.1 Interface

2.2.2 Memory Constraint

2.2.3 Operation

2.2.4 Adaptive requirement

2.2 Product function

2.3 User classes

2.4 Operating environment

2.5 User documentation

2.5 Assumption and dependencies

3 External Interface Requirement
3.1 Interfaces  (User, Hardware, Software and Communication)

3.2 Performance requirement

4 System Feature

5 Non functional requirement
5.1 Performance

5.2 Security requirement

5.3 Quality attribute

5.4 Business rule

6 Other requirement

Leave a Reply