Professional Documents
Culture Documents
_____________________________________________________________________________________________
Table of Contents
SECTION ZERO: POSITIONING OF THE BUSINESS REQUIREMENTS DOCUMENT..............................4
THE GOAL: COMMON UNDERSTANDING THROUGH STRUCTURED BUSINESS ANALYSIS ............................................4
A WORD OF CAUTION ABOUT REMOVING/ADDING SECTIONS....................................................................................4
DIFFERENT TYPES OF REQUIREMENTS.........................................................................................................................4
PRIORITIZING REQUIREMENTS......................................................................................................................................5
SECTION ONE: GLOSSARY......................................................................................................................................5
SECTION TWO: PROJECT SCOPE AND OBJECTIVES SUMMARY..............................................................5
SECTION THREE: TECHNOLOGY INFRASTRUCTURE AND INFORMATION ARCHITECTURE
COMPLIANCE..............................................................................................................................................................6
SECTION FOUR: INTENDED AUDIENCE............................................................................................................7
SECTION FIVE: DECISION MAKING AND APPROVAL PROCESS FOR THE BUSINESS
REQUIREMENTS DOCUMENT ...............................................................................................................................7
SECTION SIX: APPROACH......................................................................................................................................8
SECTION 6.1 OVERALL PROJECT MANAGEMENT APPROACH....................................................................................8
SECTION 6.2 BUSINESS ANALYSIS APPROACH..........................................................................................................8
SECTION SEVEN: BACKGROUND, HISTORICAL, AND PRIOR PROJECT INFORMATION..................9
SECTION EIGHT: BUSINESS-LEVEL REQUIREMENTS:
GOALS, VALUE PROPOSITION, AND BENEFITS...............................................................................................9
SECTION 8.1 REGULATORY REQUIREMENTS.............................................................................................................9
SECTION 8.2 REQUIREMENTS RELATING TO STRATEGIC GOALS (ORGANIZATION LEVEL).....................................10
SECTION 8.3 RELATED TACTICAL GOALS (DIVISION OR DEPARTMENT LEVEL)....................................................10
SECTION 8.4 RELATED OPERATIONAL GOALS (STAFF LEVEL)...............................................................................10
SECTION NINE: USER CLASS PROFILES AND KEY DELEGATIONS........................................................10
SECTION 9.1 SPONSORS AND STAKEHOLDERS.........................................................................................................10
SECTION 9.2 PRIMARY USERS.................................................................................................................................11
SECTION 9.3 SECONDARY USERS............................................................................................................................11
SECTION TEN: USER AND FUNCTIONAL LEVEL REQUIREMENTS........................................................11
SECTION ELEVEN: ADDITIONAL INFORMATION REGARDING FUNCTIONAL REQUIREMENTS
RELATED TO OUTPUT AND REPORTING.........................................................................................................12
SECTION TWELVE: CONCEPTUAL DATA MODEL.......................................................................................13
SECTION THIRTEEN: NONFUNCTIONAL REQUIREMENTS......................................................................13
SECTION 13.1 OPERATIONAL ENVIRONMENT..........................................................................................................13
SECTION 13.2 USER INTERFACE REQUIREMENTS....................................................................................................13
SECTION 13.3 USER ACCESS / SECURITY REQUIREMENTS......................................................................................13
_____________________________________________________________________________________________
Page 2 of 20
Revision History
Version
Date
Author(s)
Revision Notes
_____________________________________________________________________________________________
Page 3 of 20
User Requirements place the user at the center of focus, and describe, with Flowcharts, Use Case Diagrams,
Use Case Scenarios, Line of Vision and other process models, the to be user experience with the new system.
In some cases, especially where business processes are being modified, it may also be necessary to document the
as is state of user experience with the current system.
3.
Functional Requirements place the proposed system at the center of focus, and provide a prioritized list of
capabilities the system must demonstrate in order to satisfy business and user requirements.
_____________________________________________________________________________________________
Page 4 of 20
Prioritizing Requirements
Ensure that your users are aware of the following interpretations regarding the prioritization of requirements:
Must Have will be included in this release. These items represent core functionality and must be present.
Absence of any Must Have functionality represents project failure.
Should Have will be included in this release provided all Must Have requirements have been met and
sufficient project resources and time remain.
Nice to Have will be included in this release provided all Must Have and Should Have requirements have been
met and sufficient project resources and time remain.
Definition
Project Objectives:
_____________________________________________________________________________________________
Page 5 of 20
Compliance
_____________________________________________________________________________________________
Page 6 of 20
Compliance
Position
Telephone
_____________________________________________________________________________________________
Page 7 of 20
Approval Process
Is there any reason this project would get resistance? If so, from who?
Projects are managed in accordance with industry best practices, following the disciple of the PMI model of proper
project management.
Each project has a well defined project plan which is managed from initiation to closure.
Outside resources, vendors and subcontractors are managed as an additional resource to the project plan.
The BA will serve as the liaison among stakeholders to elicit, analyze, communicate and validate requirements.
The BA helps understand business problems and opportunities and recommends solutions that enable the business to
achieve its goals and objectives.
The BA will utilize the most appropriate means of gathering business requirements and assimilating those into
_____________________________________________________________________________________________
Page 8 of 20
History
Prior Projects
Are there any other projects that are related to this work?
Description
Description
Description
Position
Position
10.1
Requirement
10.2
10.3
10.4
Rank
D
Requirement
11.1
11.2
11.3
11.4
Rank
D
_____________________________________________________________________________________________
Page 12 of 20
Requirement
Rank
D
F
Rank
D
F
Rank
D
F
Requirement
Requirement
_____________________________________________________________________________________________
Page 13 of 20
Requirement
13.4.2
13.4.3
Rank
D
F
Requirement
13.5.2
13.5.3
Rank
D
Requirement
13.6.2
13.6.3
Rank
D
F
Rank
D
F
Requirement
13.7.2
13.7.3
Requirement
Rank
D
F
_____________________________________________________________________________________________
Page 14 of 20
13.8.2
13.8.3
ID
13.9.1
Requirement
13.9.2
13.9.3
Rank
D
F
Requirement
13.10.2
13.10.3
Rank
D
F
Requirement
13.11.2
13.11.3
Rank
D
Requirement
13.12.2
13.12.3
Rank
D
F
_____________________________________________________________________________________________
Page 15 of 20
Section Fourteen:
Assumptions, Dependencies, and Constraints
Assumptions: All projects operate in a less-than-perfect world. Not everything can be officially verified as existing
or available ahead of time. These unknowns are documented in project assumptions. An example might be The
project assumes the continued availability of funding following the upcoming merger.
Dependencies include, but are not limited to the availability of project resources, applications and systems that
interact with this one, hardware, facilities, equipment, business processes and regulatory approvals. Of particular
importance is the dependency on the availability of project stakeholders and users, and conformance to approval and
change management processes.
Constraints are those regulatory, technological or business realities that legitimately constrain solution development.
An example might be The new system must be built in Oracle . Although this example might sound, on the
surface, like a specification (and therefore not part of a Business Requirements Document) it becomes a constraining
requirement when stated up front. It is for this reason that users must be cautioned against careless statement of
constraints.
In essence, this section allows you to document that which cannot be ascertained in advance. These items may feed
the Risks and Risk Management section, which follows.
14.1.1
14.1.2
14.1.3
Assumptions
Uncertainty
M
Dependencies
Uncertainty
M
14.2.1
14.2.2
14.2.3
Assumptions
14.3.1
14.3.2
14.3.3
Uncertainty
M
_____________________________________________________________________________________________
Page 16 of 20
Assumptions
Uncertainty
M
Item
Likelihood
of
occurrence
(A)
Business
Impact
(B)
Score
A*B
15.1
15.2
15.3
Risk Matrix
10
9
8
Business Impact
7
6
5
4
3
2
1
0
0
10
Probablity
_____________________________________________________________________________________________
Page 17 of 20
Solution Options
Solution Options
Solution Options
Date
Change Description
Author
Initial Release
Requirement
Req.
Type
Req.
Priority
_____________________________________________________________________________________________
Page 19 of 20
Approvals
Role
Signature
Date
_____________________________________________________________________________________________
Page 20 of 20