XYZ company

Business Requirements Document (BRD)

Project/Initi ati ve
Month 20YY
Version X.XX

Company Information

Certain company is in electronic industry since past such years. Very energetic and vision having company.
 Tech Comm Template BRD

1 Document Revisions
Version
Date Document Changes
Number
05/02/20xx 0.1 Initial Draft

2 Approvals
Role Name Title Signature Date
Project Sponsor

Business Owner

Project Manager

System Architect

Development Lead

User Experience Lead

Quality Lead

Content Lead

Template provided at no charge by TechWhirl.com

You are free to use and customize as needed 2
copyright INKtopia Limited | All Rights Reserved
 Tech Comm Template BRD

3 Introduction
3.1 Project Summary
3.1.1 Objectives
Certain project is all about the simple calculator.

3.1.2 Background
No background

3.1.2.1 Business Drivers

No certain drivers

Template provided at no charge by TechWhirl.com

You are free to use and customize as needed
 Tech Comm Template BRD
3.2 Project Scope
It also includes GAP analysis

3.2.1 In Scope Functionality

 Create name records for widgets by category
o Supply Chain
o Production Lines
o Internal web apps
o External web apps
 Ability to create/delete widget names restricted by role
 Search by name, team, date, last modified
 Synchronize widgets across product/operations lines
 Provide audit trail
 Reporting on new, modified, and archived widgets by time period and team

3.2.2 Out of Scope Functionality

 Create widgets for subsidiary company product lines
 Search by approver, or rationale
 Archiving of widget objects

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
No assumption

3.3.2 Constraints
 Impending changes to privacy regulations may impact data dictionary design.
 Timeline for enterprise platform updates will impact execution of testing plan.

Template provided at no charge by TechWhirl.com

You are free to use and customize as needed 1
copyright INKtopia Limited | All Rights Reserved
 Tech Comm Template BRD

4 Business Process Overview

[Describe how the current 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.]

Demonstrations in UML

Template provided at no charge by TechWhirl.com

You are free to use and customize as needed 2
copyright INKtopia Limited | All Rights Reserved
 Tech Comm Template BRD

5 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 non-functional
requirements into a traceability matrix that can be followed throughout the project.]
The requirements in this document are prioritized as follows:

Value Rating Description

1 Critical This requirement is critical to the success of the project. The project will not be possible without this requirement.
2 High This requirement is high priority, but the project can be implemented at a bare minimum without this requirement.
3 Medium This requirement is somewhat important, as it provides some value but the project can proceed without it.
4 Low This is a low priority requirement, or a “nice to have” feature, if time and cost allow it.
5 Future This requirement is out of scope for this project, and has been included here for a possible future release.

5.1 Functional Requirements

Use Case Impacted
Req# Priority Description Rationale
Reference Stakeholders

General / Base Functionality

Single repository simplifies Development

A new Master Widget repository shall be management of widget teams
FR-G-001 1 created to house the name records and development across 30+
links to the widget objects. Infrastructure
global development teams
engineers

FR-G-002 1 A widget shall be defined in the ID+Name eliminates duplicate

Template provided at no charge by TechWhirl.com

You are free to use and customize as needed 0
 Tech Comm Template BRD
Use Case Impacted
Req# Priority Description Rationale
Reference Stakeholders

repository via a unique identifier and widget name records

name combination.

FR-G-003

FR-G-004

FR-G-005

Security Requirements

Widget creation in the repository shall be

FR-S-001 1 limited to users with Team Lead or
System Administrator,

Reporting Requirements

The system shall generate a weekly

FR-R-001 2
Report of Widget Name Status Changes

Usability Requirements

User interface for the WINS repository

shall be responsive, allowing for proper
FR-U-001 1
display on tablet, laptop, and desktop
devices.

Audit Requirements

Template provided at no charge by TechWhirl.com

You are free to use and customize as needed 1
 Tech Comm Template BRD
Use Case Impacted
Req# Priority Description Rationale
Reference Stakeholders

Any change to a widget name record

FR-A-001 1 shall be appended with user ID and
date/time stamp.

5.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 The WINS repository shall accommodate up to 100 users concurrently.

NFR-002 The WINS repository shall be designated at Level 2 for availability and SLA purposes.

NFR-003

NFR-004

NFR-005

Template provided at no charge by TechWhirl.com

You are free to use and customize as needed 2
 Tech Comm Template BRD

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

6.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.]

6.3 Related Documents

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

Template provided at no charge by TechWhirl.com

You are free to use and customize as needed 0