1. “Name of the project.”
Business Requirements Specification for “Name of Group”
Document Owner: Owner’s Name
Version Level: 1.0
Date of document

2. “Name of Initiative/System/Application” Business Requirements Specification
Table of Contents
INTRODUCTION.........................................................................................................................................................3
PURPOSE OF THIS DOCUMENT....................................................................................................................................3
DOCUMENT REVISION.................................................................................................................................................3
DOCUMENT CONTACTS...............................................................................................................................................3
STAKEHOLDER APPROVERS........................................................................................................................................3
REVIEWERS.................................................................................................................................................................3
PROCESS USED TO GATHERING THE BUSINESS REQUIREMENTS ...............................................................................4
REFERENCED DOCUMENTS OR NOTES .......................................................................................................................4
BUSINESS BACKGROUND: ....................................................................................................................................5
BUSINESS SCOPE AND OBJECTIVES:..................................................................................................................6
AS IS - TO BE BUSINESS PROCESS FLOWS........................................................................................................7
BUSINESS REQUIREMENTS ..................................................................................................................................8
BFR01: “NAME GIVEN TO DESCRIBE BUSINESS FUNCTIONAL REQUIREMENTS #1”.................................................8
BFR02: “NAME GIVEN TO DESCRIBE BUSINESS FUNCTIONAL REQUIREMENTS #2”.................................................8
BFR03: “NAME GIVEN TO DESCRIBE BUSINESS FUNCTIONAL REQUIREMENTS #3”.................................................8
BFR0N: “NAME GIVEN TO DESCRIBE BUSINESS FUNCTIONAL REQUIREMENTS #N”.................................................8
BUSINESS NON-FUNCTIONAL REQUIREMENTS (BNFR).............................................................................10
BNFR01: NON FUNCTIONAL REQUIREMENT #1......................................................................................................10
BNFR02: NON FUNCTIONAL REQUIREMENT #2......................................................................................................10
BNFR03: NON FUNCTIONAL REQUIREMENT #3......................................................................................................10
BNFR0N: NON FUNCTIONAL REQUIREMENT #N.....................................................................................................11
ASSUMPTIONS, DEPENDENCIES, AND CONSTRAINTS................................................................................12
APPENDIX..................................................................................................................................................................13
“?” DATA FIELDS:.....................................................................................................................................................13
”?” Data Fields:.................................................................................................................................................14
”Name of “ Project Page 2 of 15 Version - 1.0 Date: 04/24/15

3. “Name of Initiative/System/Application” Business Requirements Specification
Introduction
Purpose of this Document
This document provides the business requirements for enhancements to “Name of
Systems/Applications/Processes” driven by the ”Name of the initiative” process improvement efforts.
Document Revision
Revision
Number
Date of
Revision
Section Revised Nature of Revision
1.0 Initial version for wide distribution and review.
Document Contacts
All suggestions, comments, and requests for changes to this document should be directed to the document
owner.
Stakeholder Approvers
The following are the Stakeholder Approvers of this Business Requirement Specification (BRS).
Stakeholder Approvers Stakeholder Area Date Approved
Stakeholders Name Stakeholders Position/Title
Reviewers
The following are the reviewers of this Business Requirement Specification (BRS). In addition, the
document will be sent for comment to an extended list of stakeholders who have participated in
requirements sessions, and/or expressed interest in this project.
Reviewer Reviewer Area Date
Reviewed
”Name of “ Project Page 3 of 15 Version - 1.0 Date: 04/24/15

4. “Name of Initiative/System/Application” Business Requirements Specification
Review’s Name Reviewer’s Position/Title
Process Used to Gathering the Business Requirements
Business requirements were gathered from” Project Meeting’s Name” meetings, sponsored by”
Sponsor’s Name”, and lead by “Meeting Leaders’ Names”.
Referenced Documents or Notes
Document Number / Location / Links Reference Description/Name
”Name of “ Project Page 4 of 15 Version - 1.0 Date: 04/24/15

5. “Name of Initiative/System/Application” Business Requirements Specification
Business Background:
Reference ”Document’s Name” for description the business background.
”Name of “ Project Page 5 of 15 Version - 1.0 Date: 04/24/15

6. “Name of Initiative/System/Application” Business Requirements Specification
Business Scope and Objectives:
As defined in ”Document’s Name”, several enhancements are required for ”Name of Project”.
Describe, at a high level, the overall Business scope and the objectives of what is required.
”Name of “ Project Page 6 of 15 Version - 1.0 Date: 04/24/15

7. “Name of Initiative/System/Application” Business Requirements Specification
As Is - To Be Business Process Flows
Reference ”Document’s Name” for description of the As Is and To Be Business process flows.
Insert “As is” flow and “To be” flow diagrams here.
”Name of “ Project Page 7 of 15 Version - 1.0 Date: 04/24/15

8. “Name of Initiative/System/Application” Business Requirements Specification
Business Requirements
3.1 Business Functional Requirements (BFR)
The purpose of this section is to document clear and unambiguous business requirements
(functional and non functional). Usually three tasks are performed to complete this section:
1. Identify and capture new business requirements
2. Modify and update any current business requirements
3. Eliminate any non-agreed upon business requirements
To ensure that the highest value requirements are satisfied first, it is important to prioritize
requirements. Prioritizing requirements additionally provides developers a mechanism for
prioritizing their work to ensure that high priority work is completed, even when some scope
must be sacrificed to meet delivery dates.
E: Essential - This implies that the software will not be acceptable unless these
requirements are provided in an agreed manner.
C: Conditional - This implies that these are requirements that would enhance the
software product, but would not make the product unacceptable if they are absent.
O: Optional - This implies a class of functions that may or may not be worthwhile.
BFR01: “Name given to describe Business Functional Requirements #1”
Priority:?
Insert the overview and details of Business Functional Requirement #1.
BFR02: “Name given to describe Business Functional Requirements #2”
Priority:?
Insert the overview and details of Business Functional Requirement #2.
BFR03: “Name given to describe Business Functional Requirements #3”
Priority:?
Insert the overview and details of Business Functional Requirement #3.
.
.
.
BFR0n: “Name given to describe Business Functional Requirements #n”
Priority:?
Insert the overview and details of Business Functional Requirement #n.
”Name of “ Project Page 8 of 15 Version - 1.0 Date: 04/24/15

9. “Name of Initiative/System/Application” Business Requirements Specification
”Name of “ Project Page 9 of 15 Version - 1.0 Date: 04/24/15

10. “Name of Initiative/System/Application” Business Requirements Specification
Business Non-Functional Requirements (BNFR)
In the next table, business non-functional requirements are documented. First column tracks a
requirement identifier. Second column states the business non-functional requirement. Third
column describes the priority for that that business non-functional requirement. Fourth column
documents the success criteria for each business non-functional requirement.
The purpose of this section is to identify the non-functional requirements which address those aspects of
the system that, while not directly affecting the functionality of the system as seen by the users, can have
a profound effect on how that business system is accepted by both the users and the people responsible
for supporting that system.
The non-functional aspects of a business system cover a broad range of themes. The major non-functional
themes identified by the Application Enabling Design (AED) Technical Council are listed below:
 Performance (including Capacity)
 Scalability
 Availability (including Recoverability and Reliability)
 Maintainability (including Flexibility and Portability)
 Security
 Manageability
 Environmental (including Safety)
 Data Integrity (including Currency, Locality of Updating, Data Retention)
BNFR01: Non Functional Requirement #1
Priority:?
Insert the overview and details of Non Functional #1. Example: Existing non-functional features
of “name of system” are not to be compromised with introduction of the requirements described
above.
BNFR02: Non Functional Requirement #2
Priority:?
Insert the overview and details of Non Functional #2.
BNFR03: Non Functional Requirement #3
Priority:?
Insert the overview and details of Non Functional #3.
.
”Name of “ Project Page 10 of 15 Version - 1.0 Date: 04/24/15

11. “Name of Initiative/System/Application” Business Requirements Specification
.
.
BNFR0n: Non Functional Requirement #n
Priority:?
Insert the overview and details of Non Functional #n.
”Name of “ Project Page 11 of 15 Version - 1.0 Date: 04/24/15

12. “Name of Initiative/System/Application” Business Requirements Specification
Assumptions, Dependencies, and Constraints
Please describe all known existing dependencies and constraints pertaining to this endeavor.
Please document all assumptions being accepted as part of project.
”Name of “ Project Page 12 of 15 Version - 1.0 Date: 04/24/15

13. “Name of Initiative/System/Application” Business Requirements Specification
Appendix
The appendix is where information not part of the main document that is added to help with the understanding of the
requirements. An example:
The data source for “?” data is in the “application/system name”,
“?” Data Fields:
Field Table/Field Attributes
End Date DB2 Table name, Field name
Detail Description of mapping, acquisitions, access required or
any thing that will be needed to know to be able to program.
Date
A (Alphanumeric) nn
DC (Decimal) nn,n
I (Integer)
SI (Short Integer)
TS (Timestamp)
Etc…
Key: Primary Key (Optional)
Note: “annotate”.
Calculated Fields:
M Example:
Calculation: Field1 + A
Use
Table1.Field 1
Join criteria
To get to
Table2.Field3
Join criteria, Conditions, etc…
Where Z = ’1’ and W = ‘01’
”Attribute”
”Annotate”
Key Fields
”Name of “ Project Page 13 of 15 Version - 1.0 Date: 04/24/15

14. “Name of Initiative/System/Application” Business Requirements Specification
”?” Data Fields:
Field Table/Field Attributes
Key Fields
”Name of “ Project Page 14 of 15 Version - 1.0 Date: 04/24/15

15. “Name of Initiative/System/Application” Business Requirements Specification
”Name of “ Project Page 15 of 15 Version - 1.0 Date: 04/24/15