[AABB] BUSINESS REQUIREMENTS DOCUMENT (BRD)
[ REQUIREMENTS NAME] REQUIREMENTS
JULY 26, 2016
DRAFT /VERSION 1.0
[PROJECT NAME]
Internal Use Only
Table of Contents
DOCUMENT INFORMATION AND REVISION HISTORY ...................................................................................................................................................................... 1
KEY CONTRIBUTORS ............................................................................................................................................................................................................................ 2
REVIEWERS OF DOCUMENT ................................................................................................................................................................................................................ 2
APPROVAL SIGNATURE PAGE ............................................................................................................................................................................................................ 3
ACRONYMS AND GLOSSARY .............................................................................................................................................................................................................. 3
PURPOSE OF THE BUSINESS REQUIREMENT DOCUMENT ............................................................................................................................................................ 4
PROJECT OVERVIEW ............................................................................................................................................................................................................................ 5
BACKGROUND ........................................................................................................................................................................................................................................ 5
BUSINESS NEED..................................................................................................................................................................................................................................... 5
OBJECTIVES........................................................................................................................................................................................................................................... 5
STAKEHOLDERS ..................................................................................................................................................................................................................................... 6
REQUIREMENTS GUIDELINES ............................................................................................................................................................................................................. 7
DESCRIPTION ......................................................................................................................................................................................................................................... 7
TEMPLATE GUIDELINES .......................................................................................................................................................................................................................... 7
REGULATORY/POLICY REQUIREMENTS ........................................................................................................................................................................................... 8
FUNCTIONAL REQUIREMENTS ............................................................................................................................................................................................................ 8
APPROVAL REQUIREMENTS ............................................................................................................................................................................................................... 9
REPORT REQUIREMENTS .................................................................................................................................................................................................................... 9
DATA REQUIREMENTS ....................................................................................................................................................................................................................... 10
INTERFACES/BATCH PROCESS REQUIREMENTS .......................................................................................................................................................................... 10
PERFORMANCE REQUIREMENTS ..................................................................................................................................................................................................... 11
OPERATIONAL REQUIREMENTS ....................................................................................................................................................................................................... 11
USABILITY REQUIREMENTS .............................................................................................................................................................................................................. 12
SECURITY REQUIREMENTS ............................................................................................................................................................................................................... 12
TRAINING REQUIREMENTS ................................................................................................................................................................................................................ 13
ASSUMPTIONS, DEPENDENCIES AND CONSTRAINTS .................................................................................................................................................................. 14
ASSUMPTIONS...................................................................................................................................................................................................................................... 14
DEPENDENCIES .................................................................................................................................................................................................................................... 14
CONSTRAINTS ...................................................................................................................................................................................................................................... 15
APPENDIX A: REFERENCES .............................................................................................................................................................................................................. 16
Document1
Document Information and Revision History
File Name
BRD - Business Requirements Template.doc
Original Author(s)
[Author Name(s)]
Current Revision Author(s)
[Author Name(s)]
Version
1
Date
mm/dd/yyyy
Author(s)
[Author Name(s)]
Revision Notes
[Notes]
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 1 of 16
Document1
Key Contributors
[List Key Contributors of content who have been consulted with in order to document this process]
Name
Organization
Role
Notes/Comments
Reviewers of Document
[Identify the individuals who reviewed the BRD and the date that the review was completed. Signatures are not required]
Name
Organization
Role
Notes/Comments
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 2 of 16
Document1
Approval Signature Page
Deliverable Name:
Version Number:
Project Name:
I agree that this document represents my best understanding of the information presented within this Deliverable for this project today. Future changes in this
baselined document can be made through the project’s change management process. I realize that approved changes might require us to renegotiate the cost,
resource, and schedule commitments for this project.
Approver Name
Approver Title
Approver Signature/Electronic Vote/Email
Date
Acronyms and Glossary
If this section of the document is not required indicate with N/A and delete all content for the section below.
[The following table includes definitions for any unique symbols or notations that are used in the document, which may cause confusion with the intended
message, or may result in multiple interpretations of some key terms.]
Acronym
Term
Definition
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 3 of 16
Document1
Purpose of the Business Requirement Document
This Business Requirements Document (BRD) is intended to [describe intention].
The BRD is the basis for all subsequent project planning, design and coding. It describes what should happen in the system under various conditions, as
completely as known at this time. The BRD does NOT contain design information or anything related to how the system will provide the functionality.
This document expresses the functions and capabilities that a system must provide for the [enter project name] to be successful. All known constraints,
assumptions and dependencies are also defined.
All attempts have been made to use business terminology and language in describing the business requirements. Only common technical terminology is used in
this document.
Intended Audience
[Indicate who will benefit from reading this document]
e.g. This document is intended mainly for the business owners and end users of the Banner Student system to verify that their business requirements have been
documented here completely, accurately and unambiguously.
Technical staff will benefit when considering how to design a system to meet the business requirements.
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 4 of 16
Document1
Project Overview
[Provide an introduction to the Project (copy from Project Charter). 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 functional business areas.]
Background
[Provide a brief background on the history of the requirements, the problem that must be addressed, the issues, concerns, challenges, etc.
Business Need
Define the business need that this project will address
[Describe why the project needs to be done at this point in time (copy from Project Charter).]
Objectives
[List the high level business needs that must be met by the defined solution.]
1. [Objective 1]
2.
3.
4.
5.
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 5 of 16
Document1
Stakeholders
[Identify the stakeholders for the project – departments, their clients, etc.]
Name
Title
Department
Describe involvement
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 6 of 16
Document1
Requirements Guidelines
These guidelines are for the document author. This section may be deleted.
Description
Requirements describe WHAT the system, process or product/service must do in order to fulfill the business need(s).
Template Guidelines
In each of the following tables, use the following guidelines:
 Req # – Use to uniquely identify each requirement. The number should be a sequential number starting at one and should not be prefixed or reset when
starting a new requirement.

Source – Enter the name of the person who identified the requirement.

Organization – Enter the organization for the source of the requirement.

Requirement Description –Define the requirement ensuring each accurately describes the functionality to be delivered.

Requirement Owner – Enter the name of the owner of the requirement (person or group)

Priority – Indicate if the requirement is High, Medium or Low.
o
High - Requirements identified as High are deemed critical to the operation of the proposed system. They represent features that the client cannot
function without
o
Medium - Requirements identified as Medium are those that are not mission critical to the client’s business but could provide significant benefit to
the organization.
o
Low - Requirements identified as Low are not critical to the operations of the proposed system, but would represent helpful or convenient features
that would be beneficial to the client.
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 7 of 16
Document1
Regulatory/Policy Requirements
If this section of the document is not required indicate with N/A and delete all content for the section below.
[In the table below, list any policies, standards or legal constraints that apply to this process. These are existing policies that MUN has identified or have been
defined by external parties that the system must respond to. Paste here and list the source and date of the documentation.]
Req #
1.
Source
Organization
Graduate School of Graduate Studies
Student
Support
Payroll
Form (Nov
2011)
Requirement Description
Req. Owner
For International Students, Graduate Assistantship Stop Date CANNOT exceed School of
expiry date on graduate’s Social Insurance Number
Graduate Studies
Priority
H
2.
3.
Functional Requirements
[List the functional requirements that are necessary to meet the business needs. Where requirements are particular to a location or subset of the employee
population (e.g. exempt vs. non-exempt, note this as an aspect of the requirement. These statements should be measurable and finite enough to generate a
technical design. Decompose broad processes and procedure statement into system parameters.]
Req #
1.
Source
Jane Doe
Organization
School of Graduate Studies
Requirement Description
Users completing payroll requests shall be able to enter more than one
payment source on a graduate payroll request.
Req. Owner
Priority
School of
Graduate Studies
H
2.
3.
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 8 of 16
Document1
Approval Requirements
If this section of the document is not required indicate with N/A and delete all content for the section below.
[In the table below, list approval requirements for this process (if any). In the description, list whether an approval, formal review, or simply a notification is
required.]
Req #
1.
Source
Jane Doe
Organization
School of Graduate Studies
Requirement Description
User shall be able to approve Payroll requests.
Req. Owner
Priority
School of
Graduate Studies
H
2.
3.
Report Requirements
If this section of the document is not required indicate with N/A and delete all content for the section below.
[In the table below, list report requirements necessary for this process. When defining a report requirement, be sure to describe how the report is used in the
process, the source of the report, frequency (daily, weekly, ad hoc), and who uses the report.
Req #
1.
Source
Jane Doe
Organization
School of Graduate Studies
Requirement Description
User shall be able to report on unapproved payroll requests.
Req. Owner
Priority
School of
Graduate Studies
H
2.
3.
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 9 of 16
Document1
Data Requirements
If this section of the document is not required indicate with N/A and delete all content for the section below.
[In the table below, list data requirements (conversion, cleansing, retention, etc.). For data retention requirements, detail the source of data, how often the data
must be accessed, whether or not this is a regulatory requirement and how many years the data must be retained]
Req #
1.
Source
Jane Doe
Organization
School of Graduate Studies
Requirement Description
User shall be able to approve Payroll requests.
Req. Owner
Priority
School of
Graduate Studies
H
2.
3.
Interfaces/Batch Process Requirements
If this section of the document is not required indicate with N/A and delete all content for the section below.
[In the table below, list interfaces that are necessary for this process (information that must be provided to other entities)].
Req #
1.
Source
John Smith
Organization
Registrar’s Office
Requirement Description
Req. Owner
The system must pass class schedule information to the room booking system. Registrar’s
Office
Priority
H
2.
3.
4.
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 10 of 16
Document1
Performance Requirements
If this section of the document is not required indicate with N/A and delete all content for the section below.
[In this section, describe the requirements for speed, reliability, capacity, scalability, etc.]
Req #
1.
Source
Jane Doe
Organization
School of Graduate Studies
Requirement Description
Req. Owner
The application shall clearly acknowledge all user requests within 0.5 seconds. School of
Graduate Studies
Priority
H
2.
3.
4.
Operational Requirements
If this section of the document is not required indicate with N/A and delete all content for the section below.
[In this section, describe the environments (hardware/software), availability, supportability, and recovery requirements.]
Req #
1.
Source
Jane Doe
Organization
School of Graduate Studies
Requirement Description
The Payroll system shall not have more than 5 hours of scheduled downtime
per month and not more than an average of 1 hour of unscheduled downtime
per month.
Req. Owner
Priority
School of
Graduate Studies
H
2.
3.
4.
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 11 of 16
Document1
Usability Requirements
If this section of the document is not required indicate with N/A and delete all content for the section below.
[Usability requirements identify what users’ abilities and expectations of usage experiences the product must conform to. Meant to address user friendliness and
how the user interfaces (screens) are designed with consideration for the different types or users and their skill sets.]
Req #
1.
Source
Jane Doe
Organization
School of Graduate Studies
Requirement Description
The system will populate any effective date field with the current date when
adding or updating a record.
Req. Owner
Priority
School of
Graduate Studies
H
2.
3.
4.
Security Requirements
If this section of the document is not required indicate with N/A and delete all content for the section below.
[Security requirements identify the security, confidentiality, integrity and privacy issues affecting access to the product, use of the product, and protection of the
data the product uses or creates.
Req #
1.
Source
Jane Doe
Organization
School of Graduate Studies
Requirement Description
Req. Owner
The system shall not require users to identify themselves multiple times during School of
a single session (i.e., single sign on).
Graduate Studies
Priority
H
2.
3.
4.
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 12 of 16
Document1
Training Requirements
If this section of the document is not required indicate with N/A and delete all content for the section below.
[Training requirements identify all user, help desk and support training required, e.g. required materials, level of training, number of participants, duration of
training, etc.]
Req #
1.
Source
Jane Doe
Organization
School of Graduate Studies
Requirement Description
Req. Owner
All users must attend basic system training before being granted access to the School of
system.
Graduate Studies
Priority
H
2.
3.
4.
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 13 of 16
Document1
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.]
#
Description
1.
2.
3.
4.
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.]
#
Description
1.
2.
3.
4.
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 14 of 16
Document1
Constraints
[Identify any factors that limit or place constraints on the development of the solution. These may include but are not limited to time and budget constraints,
regulatory, technological or business realities.]
#
Description
1.
2.
3.
4.
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 15 of 16
Document1
Appendix A: References
If this section of the document is not required indicate with N/A and delete all content for the section below.
[List external documents to which this document refers and their location e.g., URL, folder, etc.]
References
Location
[Project Name]
7/26/2016
Classified: Internal Use Only
Page 16 of 16