Вы находитесь на странице: 1из 8

This template represents the minimum number of

sections necessary to complete this deliverable.

Project Title
Business Requirements
Document
Template ID: 2.2.T.01

Project ID:
Version:
Date: ddmmmyy

Document Sign-off
Approved by:
Name, Title

Date:

Signature:
Name, Title

Date:

Signature:
Name, Title

Date:

Signature:

Reviewed by:
Name, Title

Date:

Signature:
Name, Title

Date:

Signature:
Name, Title

Date:

Signature:

Version Project Name 2.2.T.01

Page 2 of 8

TABLE OF CONTENTS
1

INTRODUCTION ................................................................................................................................................... 4
1.1
1.2
1.3

PURPOSE AND SCOPE ........................................................................................................................................... 4


RELATED DOCUMENTS .......................................................................................................................................... 4
REVISION HISTORY............................................................................................................................................... 4

OVERVIEW .............................................................................................................................................................. 5
2.1
2.2
2.3
2.4
2.5

BUSINESS REQUIREMENTS OVERVIEW ............................................................................................................... 5


BUSINESS SCOPE.................................................................................................................................................. 5
BENEFITS ............................................................................................................................................................... 5
IMPACTED FUNCTIONAL AREAS............................................................................................................................ 5
IMPACTED APPLICATIONS/PLATFORMS ............................................................................................................... 5

BUSINESS REQUIREMENTS DETAIL ......................................................................................................... 6

ASSUMPTIONS, RISKS AND CONSTRAINTS ........................................................................................ 8


4.1
4.2
4.3

ASSUMPTIONS ....................................................................................................................................................... 8
RISKS ..................................................................................................................................................................... 8
CONSTRAINTS ....................................................................................................................................................... 8

Version Project Name 2.2.T.01

Page 3 of 8

1 Introduction
1.1 Purpose and Scope
The purpose of the Business Requirements document is to capture and define the necessary
requirements for each business unit to successfully support an initiative or project.
Business Requirements specifically do not include references to specific systems or technical
processes these will be defined in the Technical Requirements and other design documents.
The Business PM and Business SMEs are accountable and responsible for developing all aspects of
the Business Requirements. The Business Requirements will be reviewed with the appropriate
cross-functional working team for input and approval, moving it to baseline status.
Refer to the Document Business Requirement process narrative for guidelines to develop
Business Requirements and to the Rationalize Business Requirements process narrative for the
quality assurance / quality control associated to Business Requirements.

1.2 Related Documents


Title and version of documents used to generate this Business Requirements document.
Document Title

Version

1.3 Revision History


Version

Date

Version Project Name 2.2.T.01

Author(s)

Description

Page 4 of 8

2 Overview
2.1 Business Requirements Overview
A brief overview summarizing the business goals and objectives of this project.

2.2 Business Scope


In-scope Business Processes, Functions and Events
Business processes, functions and events that are specifically included in this implementation.
Out of scope Business Processes, Functions and Events
Business processes, functions and events that are specifically excluded in this implementation.

2.3 Benefits
Describe the benefits realized by implementing this project.

2.4 Impacted Functional Areas


Identify the functional areas that are impacted by this initiative.
Functional Area

Impact

Sales and
Marketing
Products and
Services
Customer
Operations
Finance
Customer
Experience
Human Resources
Network
Operations

2.5 Impacted Applications/Platforms


Applications and/or platforms that are impacted by this initiative, including but not limited to
interfaces.
Applications/Platforms

Team

Details

BSCS iX
LHS
OFS

Version Project Name 2.2.T.01

Page 5 of 8

3 Business Requirements Detail


The table below identifies the eTOM level 1 processes that must be assigned to each business
requirement.
ID

Process Level 1

Sub-processes

BIL

Billing, Invoicing & Settlement

Prepaid, Payment Services, Product/Pricing/Plan Definition,


Detailed Event Collection, Mediation/Interconnection, Rating
Discounts & Promotions, Taxes & Surcharges, Bill Calculation,
Invoice Production & Distribution, Electronic Presentment,
Payment Processing, Collections, Fraud Detections, Settlement

DBI

Business Intelligence

Profitability, Data Mining, Data Warehousing

ENT

Enterprise Tools

Utility Service Management, Application Testing Management,


Release Management, Communication Service Management,
Help Desk Management, Incident Management, Project
Management, Security Management, Availability Management,
Configuration Management, Capacity Management, Change
Management, Middleware

ERP

ERP Administration

Finance, Knowledge Management, Financial Reporting,


HR/Payroll, Logistics, Procurement

LEG

Legal / Regulatory

Legal/Regulatory

PMS

Product Development, Marketing & Sales

Product & Service Development, Product Lifecycle Management,


Multi-party Solution Development, Marketing Intelligence,
Channel Management, Products & Services Catalog, 3rd party
Services, Opportunity Management, Campaign Management,
Sales Force Management, Point of Sale, Commissions

CRM

Relationship Management

Self Care, Call Center, IVR, Contract Management, Customer


Notifications, Call Center Management, Churn Management,
Personalization Engine, Application & Service Helpdesk, Account
Management, Performance Management, 3rd Party
Management

RRA

Revenue Assurance

Network Operations, Billing Operations, System Controls

SSA

Service Assurance

Performance Management, Customer Trouble Management,


Network Management and Monitoring

SPF

Service Provisioning / Fulfillment

Credit Screening, Order Entry, Order Management, Provisioning


Identity Management, Mobile Device Management, Number
Administration, Provisioning Gateways,
Activation/Configuration, Inventory Management, Repairs
Management

Instructions

These requirements define the requests of the business.

Requirements shall be numbered using the following standards:


o PR#.LLL.BR.##

PR# (project code, i.e. PR1)

LLL (eTOM process level 1 code, i.e. CRM)

BR.## (requirement number, i.e. BR.01)

Subsequent additions/deletions will not disturb the original numeration. For example, if a project has
4 requirements and one is later removed, the remaining requirements shall not be renumbered. This
also applies to adding requirements, the new requirement shall have the next available number,
regardless of the section in which it has been placed.

Version Project Name 2.2.T.01

Page 6 of 8

Sample
Project

eTOM Level 1 Process

Req ID

Business Requirement Description

PR1

PMS

PR1.PMS.BR.01

The capability for business users to both own and


manage web content with minimal IT involvement

PR1

PMS

PR1.PMS.BR.02

The capability to support content management


approval processes (e.g. workflow)

PR1

PMS

PR1.PMS.BR.02

The capability to receive interactive agent support


particularly during online transactions

Version Project Name 2.2.T.01

Page 7 of 8

4 Assumptions, Risks and Constraints


4.1 Assumptions
Provide the assumptions associated with achieving the objectives of these business requirements.

4.2 Risks
Identify the risks associated with achieving the objectives of these business requirements.

4.3 Constraints
Identify the constraints associated with achieving the objectives of these business requirements.

Version Project Name 2.2.T.01

Page 8 of 8