Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  What are the differences between Business Requirement Document (BRD) & Software Requirement Specific
Previous Previous
 
Next Next
New Post 6/24/2012 6:02 PM
User is offline johnAnd
2 posts
No Ranking


What are the differences between Business Requirement Document (BRD) & Software Requirement Specific 
Modified By johnAnd  on 6/24/2012 8:02:43 PM)

I usually write a Software Requirement Specification (SRS) Document, which mainly has the following sections (functional requirements  as use cases, non-functional requirement and the constraints),, but most of the clients i am meeting with told me that this kind of document should be named as Business Requirement Document (BRD) rather than SRS. So is this right?

Second question i need to include more technical details about my software such as Database diagram, Entity relation diagram, architecture diagram and the user interface ,, so on which document i should provide these technical information ??

 

 
New Post 6/25/2012 6:25 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: What are the differences between Business Requirement Document (BRD) & Software Requirement Specific 

John:

A system can be completely manual (i.e., people doing the work).  A system can be almost completly automated (i.e., software doing the work).   A system can have significant parts both automated and manaul.   

A data flow diagram (a tool for higher level system behavior documentation) and a sequence oriented flow chart (a tool for documenting more detail level system beharior) can be used for all three of the above situations.    So, if only one set of requirements doc's are needed, why is it popular to talk about the need for both SRS's and BRD's?  

Realize that, what is popular in the BA community often does not make logical sense.  This is a prime example of such.   After you have been around for awhile, you will come to realize that the two document types exist for political reasons and because people are just plain confused.

As far as what set documentation is needed, think Agile.  A few data flow diagrams and entity relationship diagrams and maybe some screen shots is all that is needed, often even for more complex projects.  Everything else can be handled in conversations between developers.

Tony

 

 

 
New Post 6/25/2012 10:39 PM
User is offline M Prasad - http://mprasad.com
5 posts
10th Level Poster


Re: What are the differences between Business Requirement Document (BRD) & Software Requirement Specific 
Modified By M Prasad - http://mprasad.com  on 6/26/2012 12:49:29 AM)

 

 Hi John,

About your first question:

A document containing the specification of system behaviour (either automated or manual or both) to solve problem or realise the business opportunity that document is considered as Solution Requirement Specification.  Use cases can be used to derive the requirements for both business and solution requirements. Sources of both requirements and intention of them are different. BA should have defined Business Requirement Document as early as possible in the project phase. This will assist in many future activities and it is of great assistance when you are following Business Motivation Model.

Your client request of renaming solution requirement document to Business requirement may be due to many reasons:

·          Client might be too technical and they understand clearly what you have documented in SRS

·          Client might working on ROI through your solution document instead through goals/objectives that will be met through executing this solution

Client intention of renaming this document to BRD can only be understood by understanding their intention of renaming.

About your second question:

Solution implementation requires many other artifacts depending on the complexity of the project, business analysis approach planned, solution implementers’ knowledge level on the requirement, etc. These artifacts can be documented in many tools, for example User Interface in PowerPoint slides, Data Flow Diagram and ERD in Rational Rose UML diagram, Process Diagram in Visio. Delivery of these artifacts to different stakeholders including solution implementers depends on communication channel you chose to deliver, that means if the solution requirements needs to understood mainly by reading the solution document then one can include these documents’ references in the Solution Document’s requirement section. If the communication channel is “Consulting model”, which is of more collaborative approach than document analysis then other artifacts can be delivered independently with a sheet of bibliography. Approach is always defined depending on the objectives and planning of the Project Team.

 


Kind regards, M Prasad - www.mprasad.com
 
New Post 7/3/2012 11:53 AM
User is offline Anthony Chen
63 posts
8th Level Poster


Re: What are the differences between Business Requirement Document (BRD) & Software Requirement Specific 

 there are no industry standard definitions for SRS vs BRD. We typically take the view that the BRD is performed by business stakeholders and is used to scope the problem.  The SRS is performed in conjunction with an implementation team to determine what is actually going to be built. There is no point documenting requirements for things that the technical team has no hope of implementing.

 

A BRD might include things like high level process flows, system context diagrams and business case along with a list of functional requirements. An SRS would expand on all of those and would include business rules, wireframes, system flows and the like.

 

We have a few blog posts on the topic, here is a link

http://requirements.seilevel.com/blog/2010/03/brd-vs-functional-software-requirements.html

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  What are the differences between Business Requirement Document (BRD) & Software Requirement Specific

Community Blog - Latest Posts

Nick Stowers
Nick Stowers
Introduction   When I was introduced to scrum, the burndown chart was a tool that was highly emphasised however I feel the purpose has changed from it being a tool to predict (to a certain level) timescales for delivery to a tool that measures a team’s productivity…..in other words, the focus is on the number of points cleared w...
0 Responses
Jason White
Jason White
New technology is in trend every day and striving to make its mark to be the best. It is not optional to stay exceptional, technology has made lives easy and uncluttered in so many ways that cannot be comprehended. With the latest technologies in the headlines every day, it is Artificial intelligence that is leading the race and being incorporated ...
0 Responses
Digvijaybook
Digvijaybook
The role of a business analyst is to manufacture a piece of art; the piece of art varies depending upon the methodology and techniques being used. Business analyst serves the project all through the beginning until the end and comes up with different pieces of art. It all depends on the case, the business analyst gets involved from the beginning of...
0 Responses






Latest Articles

Effective Business Analysis during Coronavirus
May 31, 2020
0 Comments
Many of us have been impacted in some form or another whether you or a loved one have been impacted by the illness, are experiencing changes in the wo...
Copyright 2006-2020 by Modern Analyst Media LLC