Software requirement specification (SRS) is a document that contains details about the requirements of the software. In an SRS, the requirements are stated in terms of what should be achieved by the system. Business requirement specification (BRS) is a document containing details regarding the business needs and objectives that need to be achieved by the system. In this document we will describe the key Difference Between BRS and SRS and cover the following points:
- What is Software requirement specification (SRS)?
- Software Requirement Specification Example
- What is Business requirement specification (BRS)?
- Business Requirement Specification Example
- Difference between BRS and SRS (BRS vs SRS )
- Different Types of Specification Documents
- Different Types of Requirement Documents
What is Software Requirement Specification (SRS)?
Software requirement specification (SRS) in software engineering is a document produced at the beginning of a project to define the scope and objectives of the system to be developed. A good SRS document describes only what needs to be built, not how it will be built (that will be specified in a design document).
SRS usually includes the functional and non-functional requirements of an application or any other system. The functional requirements in SRS would cover all the features that the system or application should have. The non-functional requirements in SRS are more concerned with the quality aspects of the system like performance, usability, security, etc.
Any software development project can have many SRS documents. A large project might have several for each phase of development. Each document describes the features that will be built in one particular phase of development.
A typical SRS document covers the following points:
- Introduction: Introduction describes the need of the project.
- Business Requirements: Business Requirements describes all the business needs of the project.
- Functional Requirements: Functional Requirements describes all the functional needs of the project.
- Non-Functional Requirements: Non-Functional Requirements describes all the non-functional requirements of the project.
- System Assumptions: System Assumptions describes all the assumptions made for the system.
- System Limitations: System Limitations describes all the limitations made for the system.
- References: References provides all about references used in this specification document.
Software Requirement Specification Example
Following is a simple example of a Software Requirement Specification Document:
- Purpose: The purpose of this specification is to define what functionality is required of a new software system.
- Scope: This document addresses the requirements for the new software system to be developed by Company Name.
- Audience: The audience for this SRS is anyone who will be included in the software development team. It may includes the client, designer, developer, and QA tester.
- Functional Requiremnets:
- The system shall accept a login from a user.
- After entering their credentials the user will be presented with a list of transactions that can be completed at that time.
- The user may choose to either complete one or more transactions or exit the application. If the user chooses to complete a transaction then they may select from a list of available products or services and add them to an order form.
- The user will submit the order form which will send it to a database for processing.
- The database will process the order and present a receipt for confirmation to the user s screen.
- Once confirmed the database will update an order status table indicating that an order has been placed and what type of order it was (refund, exchange, etc.).
- The application shall allow users to view their order history as well as edit their personal informatio.
- Non Functional Requiremnets:
- Availability: The system should be available to customer 24/7.
- Portability: The system can run on anyoperating system and cen be transfer easily.
What is Business requirement specification (BRS)?
A Business requirement specification is a structured form of writing that gives the business requirements for a new system or an update to an existing system. It is practiced in the meaning of business analysis. BRS may be referred to as an internal or external document. The BRS describes the business objectives, the user tasks, and the information system capabilities needed to accomplish these tasks.
The business requirement specification is generally used by businesses to achieve their goals, i.e., improvement in efficiency, effectiveness, and productivity, reduction in cost and capital investment, opening new markets and product lines, etc.”
The following are the basic components of the BRS document:
- Business Objectives and User Tasks – describes what an organization wants to accomplish with an information technology investment.
- Problem Staement- A statement that identifies the business need, usually in the form of a Problem statement or Business Case. It should describe describes the solution or response to the problem, which is often in the form of a Vision statement or Solution description.
- Information System Capabilities – describes how the organization intends to use technology to support its business objectives.
- Data Requirements – identifies the internal data that must be captured and maintained by the system in order to accomplish its mission.
- External Interface Requirements – describes how users will interact with the information system and how externally produced data will be received by and integrated into the system.
- Performance Requirements – describes the criteria used to determine if an information technology investment is successful in supporting an organization’s business objectives.
Business Requirement Specification Example
A business requirement specification, often abbreviated to BRS, is the document that defines how a system should behave.
For example, if you were to start a new business, you would need to specify that the business should be able to take payment, and how it should do so. You could then write up a BRS which described how your customers would interact with your systems in order to pay for products or services.
Difference Between SRS and BRS
System requirement specification SRS in software engineering is a document which details out the required needs of an application or a system. It lists all the features and functionalities of the application or the system and explains how these things will be developed.
On the other hand, the business requirement specification BRS Document contains the specified needs of an organization or a company and it is used to ensure that all stakeholders are on board with regards to what they want from the software development team.
Some of the main differences between SRS vs BRS are as follows:
- SRS focuses on technical details of the system, whereas BRS focuses on the business goals that are to be achieved by the system.
- System requirement specifications are prepared by software engineers, whereas business requirement specifications are prepared by domain experts such as domain analysts, project managers, business analysts, and so on.
- SRS is prepared at a higher level of abstraction than BRS.
- System requirement specifications include functional requirements and non-functional requirements, whereas business requirement specifications only include functional requirements.
- SRS documents must contain all functional and non-functional requirements described in detail; there is no room for ambiguity. Business requirement specifications may not describe certain requirements in detail but they may leave enough information for the development team to understand what has to be done in order to achieve those business goals.”
Types of Specification Documents
- Software Requirement Specifications is a document containing the computer and software requirements for a product. It normally includes system and operations requirements and may also include support and training requirements.
- Functional Requirement Specifications are a document-based approach or technique to documenting, validating, and or designing features and functionality in a system.
- Compatibility Requirement Specifications is a type of specification used to describe the interface of a system component, in particular application software. It can be useful when developing an application that needs to work with pre-existing systems, or multiple applications that need to work together.
- Performance Requirement Specifications is a document that defines functional and non-functional requirements for a new or modified application. This document can be used in the development process to develop an application that meets the performance requirements of the client.
- Reliability Requirement Specifications is a study in a new paradigm for developing embedded systems. The primary objective is to explore a set of concepts and techniques for modeling, design, validation, and verification applicable to engineering both safety-critical and non-critical embedded systems across all forms of life.
- Configurations Requirement Specifications are an essential part of your project management process. Every business, big or small, is dependent on IT systems that are required to support its processes. It can range from processing customer orders for a retail store to making sure the assembly lines are producing the right number of parts for each product.
Types of Requirement Documents
- Business Requirement Document is a type of document that provides an in-depth requirement for our business requirements.
- System Requirement Document is a 2-page document prepared for the new business venture. The main purpose of preparing SysRD is to set out hardware/software requirements, including existing hardware/software used by the business.