[Insert Project Name]
Business Requirements Document (BRD)
Version 1
VERSION AND APPROVALS
UTORS
VERSION HISTORY
Version #
Date
Revised By
Reason for change
This document has been approved as the official Business Requirements Document for <project name>,
and accurately reflects the current understanding of business requirements. Following approval of this
document, requirement changes will be governed by the projects change management process, including
impact analysis, appropriate reviews and approvals.
DOCUMENT APPROVALS
Approver Name
Project Role
Signature/Electronic Approval
Date
TABLE OF CONTENTS
Project Details.................................................................................................................................................................1
Overview.........................................................................................................................................................................1
Document Resources......................................................................................................................................................1
Glossary of Terms...........................................................................................................................................................1
Project Overview............................................................................................................................................................1
4.1 Project Overview and Background.................................................................................................... 1
4.2 Project Dependencies....................................................................................................................... 2
4.3 Stakeholders..................................................................................................................................... 2
Key Assumptions and Constraints..................................................................................................................................2
5.1 Key Assumptions and Constraints.................................................................................................... 2
Use Cases........................................................................................................................................................................2
Use Case Diagram.................................................................................................................................. 2
Use Case Narrative................................................................................................................................. 3
Business Requirements...................................................................................................................................................5
Appendixes.....................................................................................................................................................................7
Appendix A Business Process Flows................................................................................................... 7
Appendix B Business Rules Catalog.................................................................................................. 10
Appendix C- Models.............................................................................................................................. 10
Traceability Matrix................................................................................................................................. 10
Use Case Narrative Instructions........................................................................................................... 10
PROJECT DETAILS
Project Name
Project Type
Project Start Date
Project End Date
Project Sponsor
Primary Driver
Secondary Driver
Division
Project Manager/Dept
Enter Project Name
(e.g. New Initiative or Phase II)
(e.g. Mandatory or Efficiency)
OVERVIEW
This document defines the high level requirements [insert project name]. It will be used as the
basis for the following activities:
Creating solution designs
Developing test plans, test scripts, and test cases
Determining project completion
Assessing project success
DOCUMENT RESOURCES
Name
Business Unit
Role
<Identify all stakeholders
and resources involved
in gathering
requirements>
GLOSSARY OF TERMS
Term/Acronym
Definition
<Identify any terms and acronyms
used within this document>
PROJECT OVERVIEW
4.1 Project Overview and Background
<This information can be taken from the Project Charter. This is a brief description of
what the project is about. It includes the current situation, the problem and the objectives.
This section serves as the vision statement for the requirements. Each requirement should
bring the project closer to the vision.>
4.2 Project Dependencies
<List any related known projects that relate in whole or in part, or has a dependency on this
project.>
4.3 Stakeholders
The following comprises the internal and external stakeholders whose requirements are
represented by this document:
Stakeholders
1.
2.
3.
KEY ASSUMPTIONS AND CONSTRAINTS
5.1 Key Assumptions and Constraints
#
Assumptions
List any assumptions the requirements are based on
Constraints
List any constraints the requirements are based on
USE CASES
< The primary purpose of the Use Case is to capture the required system behavior from the
perspective of the end-user in achieving one or more desired goals. A Use Case contains a
description of the flow of events describing the interaction between actors and the system.
The use case may also be represented visually in UML in order to show relationships with
other the use cases and actors>.
Use Case Diagram
Use Case Narrative
<Each Use Case should be documented using this template. Refer to the Appendix for Use
Case Narrative instructions>
Use Case ID:
Use Case
Name:
Created By:
Date Created:
Last Updated By:
Date Last Updated:
Actors:
Description:
Preconditions:
Postconditions:
Normal Course:
Alternative Courses:
Exceptions:
Includes:
Priority:
Frequency of Use:
Business Rules
Special Requirements:
Assumptions:
Notes and Issues:
Use Case Graphic
Example of a completed use case:
Use Case ID:
Use Case
Name:
Created By:
Date Created:
Actors:
Description:
Preconditions:
Postconditions:
Normal Course:
Alternative Courses:
Exceptions:
Last Updated By:
Date Last Updated:
User
.
1. Open browser
2. Navigate to URL
3. Interact with the available functionality
None
None
Includes:
Priority:
Frequency of Use:
Business Rules
Special Requirements:
Assumptions:
Notes and Issues:
Use Case Graphic
TBD
BUSINESS REQUIREMENTS
Function Feature - Requirement
F
0001
Business
F
0002 User Requirements
F
0003
F
0004
F
0005
F
0007
F
0007
F
0008
F
0001 Requirements
Reporting
F
0002
F
0003
F
0004
F
0005
F
0007
F
0007
F
0008
F
0001
User
Access/Security
Requirements
F
0002
F
0003
F
0004
F
0005
F
0007
F
0007
F
0008
F
0001
Service
Level/Performance Requirements
F
0002
F
0003
F
0004
F
0005
F
0007
F
0007
F
0008
F
0001
Scalability
Requirements
F
0002
F
0003
F
0004
F
0005
F
0007
F
0007
F
0008
F
0001
Support
and Maintenance Requirements
F
0002
F
0003
F
0004
F
0005
F
0007
F
0007
F
0008
??
??
??
Required
Use Case
Reference
ID Number
ID Prefix ??
Requirement
The following sections document the various business requirements of this project.
Comments
