What is the difference between BRD, SRS and Use Case documents?

Questions by bluebunny

Showing Answers 1 - 5 of 5 Answers

Saranya

  • Oct 27th, 2007
 

BRD is the document which explaines Business basis requirements like cost of the project and based on the cost list the task and
SRS(Software Requirement Specification) tells detailed concept of the project like functionality,which database and application ASP or Java.
Use case Diagram denotes the over all project concept in that diagram.

  Was this answer useful?  Yes

megrath

  • Sep 30th, 2008
 

BRD: It documents all the high level requirement, business users needs.i.e., what all the application has to perform to satisfy user needs.
SRS: It documents all the features of the system that is to be developed i.e., how the application is to be developed.All the features are related to BRD needs.
UCD: it is diagramatic representation of the features documented in SRS

sonali

  • Jul 30th, 2013
 

BRD - Business Requirement document is consist of functional Business Requirements, Gap Analysis (between current and future scenarios), In scope and Out of scope of the project, Business rules, Assumptions, Risk etc.

SRS - Source Requirement Specification is consist of Use cases, Use Case Scenarios, Activity flow diagram, Non functional Business Requirements.

Use cases - are the pictorial representation of user centric view of the system.

snehal Ratnawat

  • Aug 13th, 2013
 

BRD is a document which contains functional specifications of the systems it means this document explains what are the functionality which system can perform. Where as SRS explains technical specifications of the system and contains detailed functionality like validations, H/W and technology to be used etc. Use case explains the interaction between the actor and the system. It explains what a system can do.

  Was this answer useful?  Yes

mithr17

  • Mar 24th, 2014
 

@ everyone who thinks Use cases are only pictorial representation: Use cases can be presented in two ways - pictorial/diagram OR descriptive/text. This is why there exists, Use case diagram and use case specification.

Use case: Describes how an actor (end user) interacts with a solution to accomplish one or more of that actor’s goals, or to respond to an event.

  Was this answer useful?  Yes

Moeen khan

  • Jun 21st, 2014
 

BRD : It documents all the high level requirement ,
business users needs .i . e. , what all the application has
to perform to satisfy user needs .

SRS : It documents all the features of the system that is
to be developed i .e . , how the application is to be
developed. All the features are related to BRD needs.

UCD: it is diagrammatic representation of the features documented in SRS

  Was this answer useful?  Yes

Use case :
A use case is a methodology used to identify, clarify, and organize system requirements. The use case is made up of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal. It consists of a group of elements like classes and interfaces that can be used together. it can be characterized as below :

1)Organizes functional requirements
2) the goals of system/actor (user) interactions
3)called scenarios from events to goals
4)Describes one main flow of events (also called a basic course of action), and possibly other ones, called exceptional flows of events (also called alternate courses of action)

SRS- software requirement specification, mainly it will defined with details system level documentation which helps developers to understand the detailed flow and usage of the system they are going to develop which contain

1)description of the software’s purpose and functionality
2)how software will perform in terms of speed, response time, availability, portability,etc.
3)use cases of how users will use the software
4) how application will interact with other hardware
5)Non-functional requirements (e.g: performance engineering requirements, quality standards, or design constraints)
importance of SRS is -it will help developer to clear the goal of the SW and in which specific area they have to focus/work which help to save a time on conversation,reduce development effort,reduce the duplicate task,etc.

BRD- Business requirement document wherein business solution for a project including the documentation of customer needs and expectations. which includes

1)scope[which needs to be included in,which needs to be excluded in ,constraints,etc]
2)risk analysis[technical,business,skills,others]
3)business use case
4)user requirements
5)structural models
6)test plan
7)implementation plan
8)end user procedure
9) post implementation follow up
10)sign off

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions