Business Requirement Document (BRD)

Business Requirement Document
<Version No.>
Business
Requirement
Document
<CLIENT NAME>
<Project Name>
<Version Number>
1 | Page
<Company Name>

<Version No.>
Document Revision Control Table

Versio
n No.
Date
Revised
Change
Description
A/M/D
(Add/Modify/
Deleted)
Prepared By
Approved
By
2 | Page
<Company Name>

<Version No.>
Table of Contents
1
2
3
4
5
6
7
8
10
11
12
13
14
15
16
17
Executive Summary
Client Details
Stakeholders Categories
4
Business Objectives
Background
Scope
6.1 In Scope
6.2 Out of Scope
5
Features
5
Functional Requirements
8.1 Business Requirements
8.2 Configuration Requirements
5
8.3 Use Cases
8.4 Business Process Flows
Non-functional Requirements
9.1 Performance Requirements
6
9.2 Usability Requirements
9.3 Security Requirements
6
9.4 Training Requirements
6
9.5 Recovery Requirements
9.6 Storage Requirements
6
Reporting and quality assurance
6
Delivery Schedule
Other Requirements
Constraints
Assumptions
Limitations
Risks
Glossary of terms
8
4
4
4
4
4
5
5
6
7
7
7
7
7
7
3 | Page
<Company Name>

<Version No.>
1. Executive Summary
[Provide a summary of project components, aspects and associated details this Business Requirement
Document covers.]
2. Client Details
[A short synopsis for the client, their background and departments that the Business Requirement Document
covers.]
3. Stakeholders Categories
[This section contains the different verticals or categories of clients that could be affected by the projects
outcome. The following tabular format might be used to depict the details.]
S.No.
Stakeholde
r Type
Stakeholde
r Category
Key
Stakeholde
rs Names
Area of
specializati
on
Responsibili
ties
4. Business Objectives
[Detailed listing/explanation of the real wants of the business users that will be fulfilled by the successful
completion of the project]
5. Background
[This section provides information about the business as a whole, current business practices and outlines the
business need that underlines this document.]
4 | Page
<Company Name>

<Version No.>
6. Scope
[This section entails what all is to be done as a part of the project efforts and what is not to be done.]
6.1 In Scope
[This section contains the functionalities which comes under the scope of the project.]
6.2
Out of Scope
[This section contains the functionalities which are out of the scope of the project.]
7. Features
[This section is an elaboration of the business objectives and contains the characteristics and attributes that are
expected from the application or the software being developed.]
S. No.
Feature Name
Feature Details
8. Functional Requirements
[Give comprehensive details about capabilities the projects final product or services should have. Use cases,
Flow diagrams, Wireframes or other similar types of information should be supplemented.]
8.1
Business Requirements
[All the business requirements that are to be covered by the project are detailed in a tabular format.]
S. No.
Requirement Description
Priority
5 | Page
<Company Name>

<Version No.>
8.2
Configuration Requirements
[Requirements related to the system and default configurations are detailed here.]
8.3
Use Cases
[Detailed use cases related to the project/product functionalities are either described or mentioned here.]
8.4
Business Process Flows
[Diagrams depicting the process flow, information flow or data flow are detailed here.]
9. Non-functional Requirements
[The non-functional requirements like system response time, performance, scalability, and usability are
included here.]
9.1
Performance Requirements
[Mention all the performance related attributes and expectations in this section.]
9.2 Usability Requirements

[All the information pertaining to how user friendly the system/application should be and any special
considerations regarding the usability factor, comes here.]
9.3
Security Requirements
[Details against internal, external, data, information security and confidentiality are a part of this section.]
9.4
Training Requirements
[Any end user training requirements are described in this section.]
9.5
Recovery Requirements
[In case of any unforeseen calamity or natural disasters, the data recovery requirements that should be fulfilled,
are mentioned.]
9.6 Storage Requirements

[Details against requirements and guidelines of data storage (both physical and soft data) are elaborated here.]
6 | Page
<Company Name>

<Version No.>
10.
Reporting and quality assurance
[Elements like - quality processes to be followed in the project, metrics, project reporting and tracking are
detailed here.]
11.
Delivery Schedule
[The schedule pertaining to the delivery of the project/product functionalities are explained in this section.]
Delivery Name
12.
Functionalities Delivered
Tentative Dates
Other Requirements
[Any requirements that are not a part of any of the above detailed sections or any added details are provided
here.]
13.
Constraints
[Any factors that limit or slow the successful development, deployment or adoption of the solution are
identified.]
14.
Assumptions
[Assumptions against various sections of functional and non-functional requirements are mentioned here.]
15.
Limitations
[Any restrictions or known boundaries of the system/application being developed, are detailed here.]
16.
Risks
[Any factors that may pose a risk to the successful implementation of the project are detailed here.]
7 | Page
<Company Name>

<Version No.>
Type of Risk
17.
Risk Description
Affects
Severity
Glossary of terms
[Alphabetical listing of all the business language used in the Business Requirement Document and their
associated explanation is provided here.]
8 | Page
<Company Name>

Business Requirement Document (BRD)

Uploaded by

Copyright:

Available Formats

Business Requirement Document (BRD)

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Business Requirement Document (BRD)

Uploaded by

Copyright:

Available Formats

Business Requirement Document