Академический Документы
Профессиональный Документы
Культура Документы
Prepared By:
XX Person
emailaddress@email.com
Version: 1.0
Version Date:
May 25, 2008
Proprietary i
XX Site (SoBR)
Version: 1.0, May 25, 2008
TABLE OF CONTENTS
Page
2. ADMINISTRATION ................................................................................10
2.1. Contact List............................................................................................................10
2.2. Glossary.................................................................................................................10
2.3. Appendices............................................................................................................10
2.4. Exhibits..................................................................................................................10
Proprietary ii
XX Site (SoBR)
Version: 1.0, May 25, 2008
INTRODUCTION
The Statement of Business Requirements (SoBR) template is intended for use by the business/project
sponsor and internal IT business analyst. It is intended to capture relevant business objectives and
requirements salient to the project or program to be developed. Large, complex, or integrated projects
and programs may require additional information or sections which can be added to the SoBR as
needed. Specifically, this document is intended to:
Proprietary 1
XX Site (SoBR)
Version: 1.0, May 25, 2008
Priority
OBJ-ID Business Objective Description BREQ IDs
Number
OPRI-n OBJ-n BREQ-n, BREQ-n
OPRI-n
1.3.1. Constraints – This section identifies constraints that apply to the Customer Request (CR). It
includes restrictions or limitations, either internal or external to the project or company
organizations (i.e. sales, provisioning, field operations, financial, order entry, etc.) that will affect
the performance of the project or program. Constraints inhibit or hinder action; restrict the
freedom in designing and delivering a solution. Requirements are not included in this section as
they are covered in section 1.4.
Constraint ID Constraint Description
CONS-1 Completion of US + Int’l Your Toolkit (HR Toolbox and Manage Your Workforce) wireframes
based on date (TBD) agreed upon by IT and HR
1.3.2. Assumptions – This section identifies the critical assumptions that apply to the Customer
Request (CR). Assumptions are the conditions and factors of the project, environment, or
personnel that are considered true, real, or certain without proof or demonstration. These may
include best-guess decisions. Requirements are not included in this section as they are
covered in section 1.4.
Assumption
Assumption Description
ID
ASUM-1
ASUM-2
Proprietary 2
XX Site (SoBR)
Version: 1.0, May 25, 2008
ASUM-3
1.3.3. Dependencies – This section identifies the dependencies that apply to the Customer Request
(CR). Requirements are not included in this section as they are covered in section 1.4.
Dependency
Dependency Description
ID
DEP-n
1.3.4. Risks – This section identifies the outcome of the risk assessment that applies to the Customer
Request (CR) from a business perspective as opposed to delivery related risks that are captured
later in the Project Tracking Tool (PTT). A risk is an uncertain circumstance or event that, should
it occur, would have an adverse effect on the program/project’s objectives.
Requirements are not included in this section as they are covered in the
next section.
Risk Description Risk Ranking
Risk ID
(Low/Medium/High)
Risk-n
Proprietary 3
XX Site (SoBR)
Version: 1.0, May 25, 2008
Proprietary 4
XX Site (SoBR)
Version: 1.0, May 25, 2008
Proprietary 5
XX Site (SoBR)
Version: 1.0, May 25, 2008
Proprietary 6
XX Site (SoBR)
Version: 1.0, May 25, 2008
Business
New Business Rule Description Use Case IDs Requirement Source
Rule ID
BRULE-1 UCASE-n, Functional Area:
UCASE-n
POC:
Data Integrity
Requirement Data Integrity Requirement Description Requirement Source
ID
DIREQ-n Functional Area:
POC:
Proprietary 7
XX Site (SoBR)
Version: 1.0, May 25, 2008
Non-
Functional
Non-Functional Requirement Description Requirement Source
Requirement
ID
NFREQ-n Functional Area:
POC:
1.9.1. Potential Project Revenues/Expenses – This section identifies the potential annual revenue
and/or potential expense reduction associated to the project being requested by the
sponsor/client. List the possible benefits in the form of cost efficiencies/cost avoidance. Also list
what the impact will be if this request is not implemented. This information should be available
from the Original Project Request.
1.9.2. Number of customers impacted (if applicable) – This section identifies the number of
customers impacted by the project. This information should be available from the Original Project
Request.
1.9.3. End to End Testing – Identify if the business will participate and require end to end testing. This
information should be available from the Original Project Request.
Proprietary 8
XX Site (SoBR)
Version: 1.0, May 25, 2008
Functional Requirements
1.10. Functional Requirements (Provided by Development)
A functional requirements specification describes what is required to meet the users'
business needs. Functional requirements specify which actions the design must provide in
order to benefit the system's users. Functional requirements capture the intended use and
behavior of the system and are based upon the needs, user, and task analysis of the current
system. The functional requirements tie directly back to the detailed business requirements
stated in section 1.4 of this document. For traceability, the business requirements ID (BREQ-
ID) and the functional requirements ID (FREQ-ID) must be included in the matrix below to
demonstrate a clear linkage(s) between the functional requirement(s) and the business
requirement(s).
Row BREQ- FREQ- FREQ-ID Functional Requirement Obj-ID
ID ID Priority Description
(High, Priority
Medium,
Low)
1 BREQ-n FREQ-n OBJ-n OPRI-n
.
2
.
3
.
4
.
5
.
Proprietary 9
XX Site (SoBR)
Version: 1.0, May 25, 2008
2. Administration
2.1. Contact List
The Project Contributors/Contacts section lists all of the participants that assisted in the
production of the document.
2.2. Glossary
The Glossary contains an alphabetical list of key terms, acronyms, definitions, used in this
document which are not commonly used in the MCI business environment or would help the
reader understand the contents of this document.
2.3. Appendices
The Appendices section records optional, text-based documentation, which may be included
for clarity.
2.4. Exhibits
Proprietary 10
XX Site (SoBR)
Version: 1.0, May 25, 2008
The Exhibits section contains tangible items, such as diagrams, with the name of the author,
exhibit date, and location.
Proprietary 11
XX Site (SoBR)
Version: 1.0, May 25, 2008
Proprietary 12