Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Difference between an Business RequirementDocument (BRD) and Funtional Specification Document(FSD)
Previous Previous
 
Next Next
New Post 3/20/2008 6:07 PM
User is offline BAZ
6 posts
10th Level Poster


Re: Difference between an Business RequirementDocument (BRD) and Funtional Specification Document(FSD) 

Thanks Chris. One more question.... "Can a BRD and FSD exist together ? "  What I mean is can you have a BRD and a FSD for the same project as 2 seperate docments? The reason I ask this is because in all the examples/ samples that I have seen till now the FSD and BRD have  similar contents for eg the BRD has refrences to the use cases etc. It seems like the BRD has the FSD components as well. Its either the FSD or BRD in a project. But can these 2 documents exixst together as seperate documents in one project ?

It would be a grt help if you could attach some links to BRD and FSD.

Thanks in advance.

Zaineb

 

 
New Post 3/20/2008 6:38 PM
User is offline BAZ
6 posts
10th Level Poster


Re: Difference between an Business RequirementDocument (BRD) and Funtional Specification Document(FSD) 
Modified By BAZ  on 3/20/2008 8:39:55 PM)

Thanks Craig.

The articles were a great help in clearing the doubts .

zaineb

 

 
New Post 3/21/2008 8:43 PM
User is offline anonymous
0 posts
No Ranking


Re: Difference between an Business RequirementDocument (BRD) and Funtional Specification Document(FSD) 

Hi zained

Which artical is that? Could you please tell because I am also not very clear about it.

Thanks

Ria

 

 
New Post 3/21/2008 10:30 PM
User is offline Adrian M.
764 posts
3rd Level Poster




Re: Difference between an Business RequirementDocument (BRD) and Funtional Specification Document(FSD) 

Here are the articles that Craig mentioned:

 craigwbrown wrote
 "The Requirements Hierarchy" by John Mansour 

 What Are Requirement Types by Roxanne Miller.


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 3/22/2008 10:14 AM
User is offline LD80
6 posts
10th Level Poster


Re: Difference between an Business RequirementDocument (BRD) and Funtional Specification Document(FSD) 

It does vary largely from company to company.  In the past I've worked with a Functional Specification document only which was written after the BRD was and detailed not only what the system was to do but diagramatically showed the reader how this would be achieved within the system using sample screen dumps which showed any updated screen contents etc.  The document itself was very basic in that it detailed system Inputs (entered by user or read in from file), Processes (calculations, business logic etc) and Outputs (file or report, updated customer record etc).

Where I am just now we have numerous documents:  BRD (not system specific but user/business specific - what the Business need or want to do), System Requirements (take the Business requirements and detail what specific systems have to do in order to meet the requirement), Functional SPecification (what the system has to do , the business logic surrounding it) and finally a Design Layout Specification (details how the system does it).  This is pretty much document overkill.

Hope this helps :o)

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Difference between an Business RequirementDocument (BRD) and Funtional Specification Document(FSD)

Community Blog - Latest Posts

Fabricio Laguna talks Business Analysis and AI
I recently connected with Fabricio Laguna, aka The Brazilian BA. Fabricio is a passionate and pioneering business analyst from Brazil. During our conversation, we had a thought-provoking discussion on how artificial intelligence stands to shape the field of business analysis in the years ahead. While AI promises to transform many aspects of busines...
Business Architecture, Ontology and More with Terry Roach
It's been a privilege meeting Terry Roach, a visionary in the field of enterprise architecture and business architecture. Terry's insights into the evolution of business models, the importance of ontology in architecture, and the potential of AI to shape our future were not only thought-provoking but also a reflection of his extensive exper...
Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC