Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  How do you translate BRD to FRD?
Previous Previous
 
Next Next
New Post 11/4/2010 2:09 PM
User is offline simcity
6 posts
10th Level Poster


How do you translate BRD to FRD? 

How do you convert   BRD to FRD?

 
New Post 11/9/2010 7:33 PM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: How do you translate BRD to FRD? 

This question is too abstract.  Maybe provide some specific example?

 
New Post 2/1/2011 12:40 PM
User is offline peddi
3 posts
No Ranking


Re: How do you translate BRD to FRD? 

BRD stands for Business requirement document what business analysts prepare based on client requirement. Functional requirement document is mainly technical document or a high level design what project managers prepare.

BRD to FRD can be acheived by using 3 Dimensional Requirement Matrix tool over lines of Business Wise, Function Wise and Technical Wise.

 

Peddi.R.Akurati

::::::::::::::::::::::::::: www.mindmapinfo.net ::::::::::::::::::::::::::::::::::::::::::

 
New Post 2/1/2011 5:35 PM
User is offline KJ
243 posts
6th Level Poster


Re: How do you translate BRD to FRD? 
Modified By KJ  on 2/1/2011 8:36:24 PM)

 

A while ago I posted a response on the “boundary” of UseCases. Briefly, the square box (which is mostly ignored) in Use cases is critical in defining the Business UseCase and the Functional UseCase.. Lets use our favourite Library system to explain:
 
BUC-001:Business UseCase snippet reads like
 
1.       this UseCase starts when the prospect asks for an application form
2.       the Library gives the prospect an application form
3.       the Prospect fills in the application form and gives it to the librarian
4.       the Library approves, records the application details and issues a library card
5.       the Prospect receives the library card
6.       this UseCase end here
 
FUC-001.Functional UseCase snippet reads like (from BUC-001.4 above)
 
1.       this UseCase starts with an approved application form
2.       the Librarian enters the application form information into the system
3.       the System records new member details and creates a library card
4.       this UseCase end here
 
For the Business UseCase (BRD) the boundary is the Library and actor is Prospect. For the Functional UseCase (FRD) the boundary is the System and actor is Librarian. Note, The business process (not UseCase) could be stated as a swim lane diagram.
 
For the Business  Aficionados and purists out there
 
The UseCases above are NOT requirements, they are merely behaviours governed by Declarative Business, Functional and Non-Functional Requirements like:
 
BRD-001: the library shall allow prospects to apply for membership (Note, the boundary is the Library)
BRD-002: the library shall issue a member with a valid library card.
 
FRD-001: the system shall record membership details (Note, the boundary is the system)
FRD-002: the system shall create a Library Card.
 
NFRD-001: the system shall store 100,000 members (Non-Functional requirements)
NFRD-002: the system shall create a library card in 8.3713 seconds (Non-Functional requirements)
 
Requirements Traceability Verification Matrix (RTVM)
 
The RTVM now defines the relationships amongst Declarative Requirements and UseCases. Eg. links the BRD -- to – BUC (identifying the UseCases that are associated with the Business Requirement); BRD – to – FRD (identifying the system functions that satisfy the business requirements). Otehr relationships Etc. Note, these relationships are NOT 1-to-1.
 
warm regards,
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  How do you translate BRD to FRD?

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