BRS vs SRS

-

BRS vs SRS: Know the Difference


The difference between a Requirement and a Specification


    Requirement         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.

There are a plethora of terms and terminology for various documents
Specification Documents are of different types -
  • 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 are of different types such as,
  • BRD - Business Requirement Document
  • SRD - System Requirement Document

Below is differenciation between BRS Vs SRS,
    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

Comments

Post a Comment

Popular posts from this blog

Agile Model

-
Image
Agile Method This article is a introduction to Agile software development methodologies and it's application. This is not only suitable for software developers but also for Team Leaders, Project Managers, Product Managers, Development Managers, Testers, QA Managers, QA Engineers, Technical Writers, UX Designers, anyone involved in the delivering software.It doesn't describe any code or technology it's an method or an software engineering model which helps to develop a tool to it's best requirements or goals. Agile Method is a combination of various sprint cycles initially of 1 to 4 weeks per sprint cycle. Deployment is alligned with the changing business need after the completion of every sprint cycle. Agile adapts of frequent feedback by delivering workable product after every iteration/sprint cycle end. In other words Agile Method is a series of short iteration/sprint cycles. Agile Model is an incremental version of multiple waterfall model cycle so,br the cha...
Read more

Customizations: Oracle SaaS vs PaaS

-
Image
  It has always been a questions from customer, on what's the customization extent of SaaS and where one should approach PaaS services in Oracle universe. After working into this domain for 3+ years and having multiple iterations into multiple projects and tons of pre-sales in past few years this has brought me a good level of clarity to the extent where customers are happy to know the point when they should switch to PaaS. Understanding and practicing industry best practice should always be best practice for an organization as that helps to manage that for long run. As best systems are those which requires minimal of manual efforts to maintain. SaaS Customizations Page composer OTBI reports Custom Workflow - BPM Page Composer: For certain applications one can use Page Composer to configure application page components, such as page content and layout for other users.Here are the changes one can make using this tool: Add, move, delete, show, and hide fields ...
Read more

How to verify systems designed in Business Analyst

-
Image
Verification is what most people think of when they hear the word testing — it’s the process of testing whether a business analysis solution does what it’s designed to do. During verification, the testing team (which may consist of developers, quality assurance [QA] people, and some business analysts [BAs]) put the software through its paces to both confirm that it operates as expected and ensure that it conforms to the design specifications laid out earlier in the project. Verification testing includes four phases — one pretest phase and three phases of actual testing. Smoke Test Also called a build verification test, a smoke test is a pretest that determines whether full testing can even begin in the first place. It reveals any simple failures in the solution that may prevent you from executing the tests in the next three phases. Some project teams may link this test to unit testing. Unit Test The unit test is the first actual phase of testing. It involves testing each uni...
Read more