<<Logo here>> <<Document identification>>

<< PROJECT NAME AND NUMBER>>

BUSINESS REQUIREMENTS DOCUMENT

Client:

Author: << Person who created the document >>

Version: << First version should be 1.0 and increment up >>

Status << Enter status of document. i.e., Draft, Pending Sign-off, Final, et cetera >>

Date: << YYYY-MM-DD >>

BUSINESS REQUIREMENT DOCUMENT PAGE 1 OF 8

TEMPLATE VERSION #, <DATE>

DOCUMENT #
<<Logo here>> <<Document identification>>

SUBMITTERS OF FINAL DOCUMENT

These signatories confirm this document was submitted by the project team as the requirements for the
<< Project Name >> Project.

Role Name Signature Date

Project Manager << Print name >> YYYY-MM-DD

Project Lead << Print name >> YYYY-MM-DD

Business Analyst << Print name >> YYYY-MM-DD

<<OTHER>> << Print name >> YYYY-MM-DD

REVIEWERS OF FINAL DOCUMENT

Identify the individuals who reviewed the BRD and the date that the review was completed.
Signatures are not required.

Role Review Completed Date

Project Sponsor YYYY-MM-DD

Client YYYY-MM-DD

<<OTHER>> YYYY-MM-DD

APPROVERS OF FINAL DOCUMENT

These signatories confirm this document serves as the requirements for the << Project Name >> Project.

Role Name Signature Date

Project / Client Sponsor << Print name >> YYYY-MM-DD

Application Delivery << Print name >> YYYY-MM-DD

Manager

<<OTHER>> << Print name >> YYYY-MM-DD

BUSINESS REQUIREMENT DOCUMENT PAGE 2 OF 8

TEMPLATE VERSION #, <<DATE>>

DOCUMENT NUMBER V#
<<Logo here>> <<Document identification>>

TABLE OF CONTENTS
INTRODUCTION............................................................................................................................. 4
Purpose of the Business Requirement Document................................................................4
Project Background.............................................................................................................. 5
Project Scope....................................................................................................................... 5
Project Purpose.................................................................................................................... 5
Stakeholders........................................................................................................................ 5

BUSINESS REQUIREMENTS............................................................................................................ 6
Functional Requirements..................................................................................................... 6
Non-Functional Requirements.............................................................................................. 6

ASSUMPTIONS, DEPENDENCIES AND CONSTRAINTS.......................................................................7

Assumptions........................................................................................................................ 7
Dependencies...................................................................................................................... 7
Constraints........................................................................................................................... 7

Glossary..................................................................................................................................... 8

BUSINESS REQUIREMENT DOCUMENT PAGE 3 OF 8

TEMPLATE VERSION #, <<DATE>>

DOCUMENT NUMBER V#
<<Logo here>> <<Document identification>>

INTRODUCTION

PURPOSE OF THE BUSINESS REQUIREMENT DOCUMENT

The Business Requirements Document (BRD) clearly states the functions and capabilities that the
application and/or system must provide for the project to be successful (what the system and/or application
must do). All known constraints, assumptions and dependencies must also be clearly defined.

The BRD is the basis for all subsequent project planning, design and coding. It should describe as
completely as known at this time, the system’s behaviours under various conditions. The BRD does NOT
contain design information or anything related to how the system will provide the functionality.

BUSINESS REQUIREMENT DOCUMENT PAGE 4 OF 8

TEMPLATE VERSION #, <<DATE>>

DOCUMENT NUMBER V#
<<Logo here>> <<Document identification>>

PROJECT BACKGROUND
<< Provide an introduction to the Project. This includes describing the business context of the project and an
overview of the client’s operation. Include a high-level overview of each of the business areas. >>

PROJECT SCOPE
<< Define the scope of the solution, not the project. >>

PROJECT PURPOSE
<< State the purpose of the project. What is the system going to help the client achieve? How do you know
that the system delivered meets the needs of the client? >>

STAKEHOLDERS
<< Identify the stakeholders who have a stake in the project – departments, their clients, anyone that the
system is going to provide information to or collection information from. Identify the stakeholder and describe
their stake in the system. >>

BUSINESS REQUIREMENT DOCUMENT PAGE 5 OF 8

TEMPLATE VERSION #, <<DATE>>

DOCUMENT NUMBER V#
<<Logo here>> <<Document identification>>

BUSINESS REQUIREMENTS

FUNCTIONAL REQUIREMENTS

# Requirements Priority Additional Information

H - High
M – Medium
L – Low

1 The system MUST…

2 The system SHOULD…

3 The system COULD…

4 The system WON’T…

NON-FUNCTIONAL REQUIREMENTS

# Requirements Priority Additional Information

H - High
M – Medium
L – Low

1 The system MUST…

2 The system SHOULD…

3 The system COULD…

4 The system WON’T…

BUSINESS REQUIREMENT DOCUMENT PAGE 6 OF 8

TEMPLATE VERSION #, <<DATE>>

DOCUMENT NUMBER V#
<<Logo here>> <<Document identification>>

ASSUMPTIONS, DEPENDENCIES AND CONSTRAINTS

ASSUMPTIONS
Identify any assumptions; factors that, for planning purposes are considered to be true, real or certain without
proof or demonstration

# Assumptions

DEPENDENCIES
Identify any factors that are linked together where each has some effect on the other. These may include
things like availability of project resources, users or stakeholders, equipment, business processes and
regulatory approvals.

# Dependencies

CONSTRAINTS
Identify any factors that limit or place constraints on the development of the solution. These may include but
are not limited to regulatory, technological or business realities.

# Constraints

BUSINESS REQUIREMENT DOCUMENT PAGE 7 OF 8

TEMPLATE VERSION #, <<DATE>>

DOCUMENT NUMBER V#
<<Logo here>> <<Document identification>>

GLOSSARY
Item Description

BA Business Analyst

BRD Business Requirements Document

PM Project Manager

RTM Requirements Traceability Matrix

BUSINESS REQUIREMENT DOCUMENT PAGE 8 OF 8

TEMPLATE VERSION #, <<DATE>>

DOCUMENT NUMBER V#