Before we begin you must know –
The difference between a Requirement and a Specification
|They outline “what” the software must do||They outline “how” the software will be created|
|They outline the software from the end-user , business and stakeholder perspective.||They outline the software from the technical team perspective.|
- SRS specifies the functional and non-functional requirements of the software to be developed whereas BRS in software engineering is a formal document describing the requirement provided by the client
- SRS is created by the System architect whereas BRS software is usually created by the business analyst.
- SRS stands for System Requirement Specification whereas BRS stands for Business Requirement Specification.
- SRS is derived from the BRS whereas BRS is derived from client interaction and requirements.
There are a plethora of terms and terminology for various documents
Specification Documents like –
- SRS – System Requirement Specifications
- FRS – Functional Requirement Specifications
- BRS – Business Requirement Specification
- CRS- Compatibility Requirements Specifications
- PRS – Performance Requirements Specifications
- RRS- Reliability Requirements Specifications
- CRS-Configurations Requirements Specification
Requirement Documents like –
- BRD – Business Requirement Document
- SRD – System Requirement Document
Points To Ponder
- In many places these documents are not separate and are used interchangeably.
- Specifications and requirements roughly communicate the same information, but to two completely different audiences.
- For a given project which documents of above are created, depends on the “nature” of the project and the organizational “processes”
In this tutorial we will discuss the Difference between BRS and SRS in software testing:
|BRS (Business Requirement Specification)||SRS (System Requirement Specification)|
|It describes at very high level the functional specifications of the software||It describes at a high level , the functional and technical specification of the software|
|It is a formal document describing about the requirement provided by client (written, verbal)||It specifies the functional and non-functional requirements of the software to be developed|
|Usually its created by the Business Analyst who interacts with clients|| Usually its created by the System Architect who is an technical expert .
Though in smaller companies the BA will create SRS as well.
Some companies do not create SRS altogether. Their BRS is detailed enough to be used as SRS as well.
|It is derived from client interaction and requirements||It is derived from the BRS|