Difference between SRS, BRS & FRS Documentation

Most of the times the interviewer asked you that have you familiar with SRS, BRS & FRS Documentation or tell me the difference between SRS, BRS and FRS. Well, I tell you the differentiation in general and as per the CMMI process what is the difference between all above. Basically, usage of this document depends on the organization and company type, their standards and how organization follows processes.

SRS - System Requirement Specification:
It describes entire system flow, how data is going to flow into the system and overall functionality of the system. SRS says brief about each module's functionality and doesn't include in-depth functionality of each page and module. SRS documentation is written by IEEE Std. 830. If you want to know How to write the SRS documentation then click here
SRS documentation includes a set of use cases that explain all the interactions the users will have with the software. Use cases are also known as functional requirements. In addition to use cases, the SRS also contain non-functional requirements.

NOTE: The Software Requirements Specification should contain descriptive labels for and references to every figure, table, and diagram included within the document.

BRS - Business Requirement Specification:
This document is called as high level document includes the entire requirement demanded by the client. Ideally, this document simply includes all the requirements should be part of proposed system. BRS includes list of requirements which are demanded by client and should be part of proposed system.

Business Requirements Specification Contents
• The purpose of the project
• The Client, the Customer, and other stakeholders
• Users of the product
• The scope of the work
• The scope of the product
• Features and Functionalities
• Usability and Humanity Requirements
• Performance Requirements

FRS - Functional Requirement Specification:
FRS includes requirements, converted into functionality and says that how this requirement is going to work as a part of proposed system. FRS includes requirement converted into the way it is going to work as a part of proposed system.