SRS (SYSTEM REQUIREMENT SPECIFICATION)

SRS (SYSTEM REQUIREMENT SPECIFICATION)

FACEBOOK

Definition- A SRS is a specification of the software system which provides complete and structured description of the system's requirement, behavior, interfaces, including all functional use cases and non-functional requirements.

Let's us have a closer look at each of the section and subsection in the IEEE 830 standard for SRS and later develop a sample SRS for a problem statement.

Section 1: Introduction

This section broadly provides the background and lays the ground work of the software. It contains the following subsections.

• Purpose: It explains the main purpose and the intended audience of the SRS.
• Scope : It provides pointed brief description of the high-level functionality of the software and explains the broad goals of the intended software.
• Definition, Acronym/Abbreviation: It defines all the main terms and provides the acronyms used throughout the SRS
• References: All supporting documents referred such as business process document or user requirement document will be mentioned here.
• Overview: It provides the organizations of the entire SRS document and helps in readability.

Section 2: General Description

This section elaborates the functionality of the intended software in finer details containing following sub-section:

• Product Perspective: It describes the product interfaces and relationships with other products. It provides the operation details and business ownership for the products.
• Product Function: All the major functionalities of the software product is described in consistent fashion. This includes the functional use case and functionality is normally listed with "shall".
• User Characteristics: Here, We describe the characteristics of the intended user of the software including their background, training requirement, demographics details, technical expertise, educational background, language requirements, etc.
• Constraints: Provide the list of the constraints like performance constraints, memory constraints, load constraints, etc. 
• Assumption and dependencies: It provides the list of all assumption related to OS, browser, hardware, implied features, security, performances etc and all the dependencies on upstream services, hardware and other resources.

Section 3: Specific Requirements

This section provides in-depth details about the functional and non-functional requirements. Project teams can customize the section to include any project/domain specific requirement.

• External interface requirement:  It describe about the contracts of integration system like web services, db, ERP, legacy System etc. 
• Function Requirements : It provides detailed function use cases, business functions and behavior of the intended software. 
• Performance requirements : Details all the expected performance requirements of the system. This include response time, process completion time, transaction time, etc.
• Design constraints: Provides all the constraints for designing the software
• Standard Compliance: It states all the regulations and standards that the software needs to comply. 
• Logical database requirement: provides high-level database related functionalities
• Software system attributes: provides details about critical non- functional requirements.

1. Reliability
2. Availability
3. Security
4. Maintainability

Appendixes Section

This section provides details of the references used within main sections. It includes glossary, Mock Up screens, reports, data dictionary, business models etc. 

Thanks for visiting my blog. Hope you would like this article shower your comments regarding this blog and other query in comment section below. 

Till then STAY HUNGRY STAY FOOLISH :)  :3