BRD is the most valuable single DELIVERABLE of Business Analysis or Requirements Engineering but it is too bulky, monolithic and unwieldy. So it is split into independent but related set of documents which can be initiated and developed iteratively in any order. Here is an introduction to a comprehensive set of FIVE BRD Sub-documents. This is NOT enough to do professional job with these templates. A brief but intensive training on the use of them in a mini-project will take care of it. Take the training and templates to derive RECURRING BENEFITS individually or as a corporate entity.

1. Putcha V. Narasimham
Knowledge Enabler Systems Founder Professor & Proprietor
205, Krishna Apts, Avenue No 6, Banjara Hills,
Hyderabad 500034 India
kenablersys@yahoo.com or putchavn@yahoo.com
Our Ref: in the footer
Date: in the footer
Business Requirement Document BRD:
Need & Use
Putcha V. Narasimham
Business Analysis
Business Analysis has emerged to shift the focus from technical “Systems Capabilities
business and
Specification”, wrongly called System Requirement Specification to
user requirements. This has been a good development. It is NECESSARY
to know the REAL needs of business before conceiving of any
system which may meet those needs.
BRD-- Business Requirement Document
The term BRD is very popular as an aggregation of various business and user needs,
though there is no standard for BRD contents and format. A number
of templates are in use but they are too elaborate, monolithic and unwieldy but
"Swift Kick Communications BRD Template" is an exception. IIBA BABOK ® refers
to BRD as Requirements Package. Howard Podeswa calls it an assembly of
components placed under version control in his The Business
Analyst’s Handbook.
Please turn over
4 Business Requirement Document BRD---Need & Use 24NOV12 Page No 1 of 2
The Best Anywhere Must Reach the Needy Everywhere

2. Putcha V. Narasimham
Knowledge Enabler Systems Founder Professor & Proprietor
205, Krishna Apts, Avenue No 6, Banjara Hills,
Hyderabad 500034 India
kenablersys@yahoo.com or putchavn@yahoo.com
Kenablersys BRD Sub-Documents
We have distilled the above to specify
BUSINESS requirements
comprehensively (full range without missing some), correctly (the actual needs—not
assumed needs), precisely and rapidly (do not take forever defining and specifying).
WE subscribe to this concept of IIBA package and
Podeswa’s version controlled Assembly of Components.
We use and recommend a set of BRD sub-documents
which are fairly independent though related.
4AA BRD Procedure & Contents
4BB Project Inception (vision) Document
4CC Glossary
4DD Statement of Project and Scope
4EE Stakeholder Analysis and Requirements Hierarchy
There is significant flexibility on the when and in what sequence they need
to be created / completed. The templates can be expanded and
collapsed. However, the nature of content, structure and scope are well
defined.
Conclusion:
START with any sub-document of kenablersys BRD.
Build & reconcile them iteratively using feedback
STOP anywhere—you have usable set of documents
Being competent, effective and efficient is 90% mindset and 10% toolset.
---Roger Tregear
---III---
4 Business Requirement Document BRD---Need & Use 24NOV12 Page No 2 of 2
The Best Anywhere Must Reach the Needy Everywhere