You are on page 1of 6

Business Requirement Document

Template
Project/Initiative
Month 2016

Version X.XX

L&T Shared Services

Document Revisions
Version
Number

Date
05/04/20xx

0.1

Document Changes
Initial Draft

2 Approvals
Role

Name

Title

Signature

Date

Sponsor
Business Owner
(Customer SPOC)
Transition Manager
System Architect
Technical Team
Lead
Quality Lead
Business Analyst

3 Introduction
3.1

Project Summary

3.1.1

Objectives

[These should describe the overall goal in developing the product, high level
descriptions of what the product will do, how they are aligned to business
objectives, and the requirements for interaction with other systems.]
3.1.2

Background

[Provide a brief history of how the transition came to be proposed and initiated,
including the business issues/problems identified, and expected benefit of
implementing the transition.]
3.1.2.1 Business Drivers
[List the business drivers that make development of this product important. These can be financial,
operational, market or environmental.]

3.2 Project Scope


[Describe what work is in scope for the transition, and specifically what work is out
of scope beyond the current budget, resources and timeline as approved by all the
stakeholders. This is designed to prevent scope creep of additional features and
functions not originally anticipated.]
3.2.1

In Scope Functionality

3.2.2

Out of Scope Functionality

3.3 System Perspective


[Provide a complete description of the factors that could prevent successful
implementation or accelerate the projects, particularly factors related to legal and
regulatory compliance, existing technical or operational limitations in the
environment, and budget/resource constraints.]
3.3.1

Assumptions

3.3.2

Constraints

3.3.3

Risks

3.3.4

Issues

4 Business Process Overview


[Describe how the current or As-Is process (es) work, including the interactions
between systems and various business units. Include visual process flow diagrams
to further illustrate the processes the new product will replace or enhance.
Use case documentation and accompanying activity or process flow diagrams can
be used to create the description(s) of the proposed or To-Be processes.]

4.1 Current Business Process (As-Is)


[Provide the process flow diagram, current technical capabilities and a high level
process analysis of the use of technology in implementing the process]

4.2 Proposed Business Process (To-Be)


[Provide the process flow diagram, future technical capabilities and a high level
process analysis of the use of technology in implementing the process]

5 User Scenarios/Use Cases


[Provide a summary of the major functions that the product will perform.
Organize the functions to be understandable to the customer or a first time reader.
Include use cases and business scenarios, or provide a link to a separate document
(or documents). A business scenario describes a significant business need,
identifies, documents, and ranks the problem that is driving the scenario, describes
the business and technical environment that will resolve the problem, states the
desired objectives, and shows the Actors and where they fit in the business
model.]
Use Case: <Enter Use Case name here>
<Enter a short name for the Use Case using an active verb phrase.
e.g. Process Invoice, Trigger Documents>
Id: UC- <Enter value of Id here>
<Enter a unique numeric identifier for the Use Case. e.g. UC-113>
Description
<Enter description here>
<Briefly describe this use case.>
Level: <Enter Use Case Goal Level here>
<Enter the goal level of this Use Case. Specify whether the Use Case level is - High
Level Summary, Summary, User Goal, Sub-Function, Low Level>
Primary Actor
<List the Primary actor here>
<List the Actor whos goal is being satisfied by this Use Case and has the primary
interest in the outcome of this Use Case.>
Pre-Conditions
<List Pre-Conditions here>
Post Conditions
Success end condition
<List success end condition here>
<Enter the successful end condition of the Use Case where the Primary Actors goal
is satisfied.
Failure end condition:
<List failure end condition here>
< Enter the failure end condition of the Use Case if the Primary Actors goal has not
been achieved.
Minimal Guarantee
<List minimal guarantee here

6 Business Requirements
[The specific business requirements elicited from stakeholders should be listed,
categorized by both priority and area of functionality to smooth the process of
reading and tracking them. Include links to use case documentation, and other key
reference material as needed to make the requirements as complete and
understandable as possible. You may wish to incorporate the functional and nonfunctional requirements into a traceability matrix that can be followed
throughout the project.]
The requirements in this document are prioritized as follows:
Value

Rating

Description

Critical

This requirement is critical to the success of the transition. The transition will not be
possible without this requirement.

High

This requirement is high priority, but the transition can be implemented at a bare
minimum without this requirement.

Medium

This requirement is somewhat important, as it provides some value but the


transition can proceed without it.

Low

This is a low priority requirement or a nice to have feature, if time and cost allow
it.

Future

This requirement is out of scope for this project, and has been included here for a
possible future release.

6.1 Functional Requirements


Requirement# Priority Description
General / Base Functionality
FR-G-001

Security Requirements
FR-S-001

Reporting Requirements
FR-R-001

Usability Requirements
FR-U-001

Audit Requirements
FR-A-001

Comments

Use Case Reference

Impacted
Stakeholders

6.2 Non-Functional Requirements


[Include technical and operational requirements that are not specific to a function.
This typically includes requirements such as processing time, concurrent users,
availability, etc.]

ID

Requirement

NFR-001
NFR-002

7 Appendices
7.1 List of Acronyms
[If needed, create a list of acronyms used throughout the BRD document to aid in
comprehension.]

7.2 Glossary of Terms


[If needed, identify and define any terms that may be unfamiliar to readers,
including terms that are unique to the organization, the technology to be
employed, or the standards in use.]

7.3 Related Documents


[Provide a list of documents or web pages, including links, which are referenced in
the BRD.]

You might also like