According to me BRS are specified by the customer and SRS are specified by the developer based on the BRS.
Both SRS, BRS are not specified by the customer.
Lot of difference between SRS and BRS. Both are specified by Customer.
Whenever developing the Product, we design according to the view of Customer.
Main difference is..,
1) SRS is an external part of Application/System/Product. And BRS is the internal part of our System.
2) SRS is a collection of all requirements from one end to other end. But BRS is designed according to the Business or Profit of the related domain of application.
3) SRS is the whole view of Requirements like on which optimization techniques for the application, technology, design strategy, Performance, Optimization of requirements etc.
Bur BRS is the main requirement specified at the LIVE or Production purpose according to the Business or Profit.
4) SRS is specified at the time of Construction of requirements/Application/Product. But some situations, BRS are specified after using of our application in LIVE scenario or Production scenario.
5) SRS is the Super set to the BRS .ie. BRS is part of SRS.
6)SRS(collection of Requirements) is used for developing of application for the kind of System Level(like Reliable. reusable, design satisfaction,performance,spped,database,technology,optimization,integrety,security,Hardware ,Load.....etc)But BRS is main for Business or income or Profit of the domain of software.
One silly example,
If we purchase a Bike which meet design & look like Good color, seat, mirrors, back color, lights, engine design, tires radius, Tank width ..Etc. This is the System level requirements,
But mileage, speed of bike, CC of bike is the business requirement of application.
Another example in my Company live scenario is..
My company product is designed based upon the some requirements like advanced technologies Java/J2ee,performance,security,database,speed of application etc(this is system level.) and in one module called (Quotation Management and Contracts of Customers, Carriers, Vendors) is the business requirements. Without developing this module, my marketing peoples can not sale my product for customers in market. Why mean this is the main advantage of Business purpose.
BRS: Client/ customer will give the Business requirements of the required system.
SRS: Developer will gather all information on entire system to develop the functional flow to meet the client requirement.
Please do not get confused between a BRS and SRS.
BRS= Business Requirement Specs define the requirements of the customer to be developed as a new software (What r the requirements of the customer)
SRS= Software Requirement Specs defines the functional requirements to be developed and the system requirements to be used (How to develop the customer requirements).
Let's first make it clear....
Business requirement, system requirements, functional specifications, Use case document, User Requirements, Functional specifications and many other terminologies are the products of 'Requirement Analysis' or 'System Analysis'.
Now, when we say business requirements, it is nothing but the business analysts view regarding specifying what a proposed new system will do and specifying what the user organization will be able to do give a solution to its problem.
Unlike system requirements business requirements are often expressed as lists of discrete project goals or objectives that will, when quantified, serve as justification for the project.
- To reduce warehouse inventory cost by 20%.
- To ship 95% of orders within 12 hours of receipt.
Most of the times business requirement are in non technical language case to case it may vary) as it's prepared from layman’s perspective and view. When we translate them into technical requirement it became functional specification or System requirements or user
requirement specification or Use case document/diagram/ realization or you name it as you want. This kind of document normally content system level constraints for the proposed system.
Such as ...
- Performance constraints:
Response times for given transaction types
Number of concurrent users
Transaction entry rates
- Environment constraints
Database management system
Minimum hardware configuration
Use of (specified) application software product(s)
Look-and-feel of external user interface
- Constraints on the development:
Use of programming languages
Use of C.A.S.E. tools
Use of outside contractors
- Constraints on the end product:
Reliability and availability constraints
Hours of online operation
Tolerable frequency and duration of outages.
Tolerable frequency and volume of lost data.