In a software development project, BRS (Business Requirement Specification) is a document that details the requirements of the customer. This contains the information about the business and details about the processes that needs to be implemented in software. SRS (Software Requirements Specification) specifies the requirements of a software system. It includes a description of the system that needs to be developed. SRS includes information like how the users interact with the software system, non-functional requirements, etc.
What is BRS?
BRS (Business Requirement Specification) is a document that details the requirements of the customer. This will be referred by the development team when developing the software and the testing team during the testing phase. This holds details about the processes that need to be implemented in software and whether any new features are required. In general, BRS contains information such as who intended to use the software, maximum number of concurrent users that are going to use the system, types of users, computer literacy of the uses, problems faced by the users currently, amount of security required by the application, hardware and environmental constraints faced by the software. It also provides a description of the current system and possible future expansions. BRS also describes the deliverables or what is expected by the customer. It should also describe the level of reliability expected by the software. Most importantly BRS is not written using any of computer jargon.
What is SRS?
SRS specifies the requirements of a software system. It includes a description of the system that needs to be developed. It includes how the user interacts with the system using use cases. Use cases provide a description of actions that occur between the users and a software system. Usually UML (Unified Modeling Language) is used to formally specify the use cases in the SRS. It also contains non functional requirements such as performance requirements, standards required by the system and any of the constraints on the system. SRS should always be correct and consistent since it is used by the developers in the development process. It should also be unambiguous. Generally, SRS should contain at least the following sections: an introduction, overall description of the system and specific requirements. The introduction should clearly define the scope of the expected system among other information such as purpose of the system and an overview of the system. Overall description provides the user interactions, dependencies and constraints of the system, etc. Specific requirements contain any performance requirements, database requirements, etc.
What is the difference between BRS and SRS?
BRS is a document that details the requirements of the customer using non technical terms, whereas SRS specifies the requirements of a software system in a more formal manner. SRS describes how the users interact with the system using use cases (specified with UML) whereas the BRS provides a description of user interactions. Both BRS and SRS are used by the developers in the development process and for testing the system as well.