Business Requirements Document (BRD)
Template
Project/Initiative
Month 20YY
Version X.XX
Company Information
Page 0|7
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
Page 1|7
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.]
• Deliver a Widget Interactive Naming System (WINS) that synchronizes naming and linking of all
widgets in all systems across the enterprise.
• Avoid duplication of widget names and reduce time to production for existing projects.
• Support text searching on widget names or business descriptions.
• Sync widget names and changes to Windows and Linux platform administration tools.
• Tracks changes to widgets including new widgets, modified widgets, and widgets to be archived.
3.1.2 Background
[Provide a brief history of how the project came to be proposed and initiated, including the
business issues/problems identified, and expected benefit of implementing the project/developing
the product.]
Timely and accurate synchronization of widget names will reduce development levels of efforts across the
enterprise by eliminating duplicate names of widgets in development and deployed. Acme uncovered seriously
high levels of errors across testing environments, production error messages, and increased rework due to lack
of knowledge about widgets already in production.
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.]
• Customers are looking for faster updates to information on the [product] website, and may consider
competitors if needs are not met.
• Development group requires a scalable solution to track the widgets being deployed into all
environments to better manage resources.
3.2 Project Scope
[Describe what work is in scope for the project, and specifically what work is out of scope… beyond
the current budget, resources and timeline as approved by the project stakeholders. This is
designed to prevent “scope creep” of additional features and functions not originally anticipated.]
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
Page 2|7
• 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
• Inventory of existing widgets completed by Q1.
• Testing data comprises scrubbed production data as of December 31.
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.
3.3.3 Risks
• Previously approved Q2/Q3 development projects may limit availability of development and QA
resources, necessitating outsourcing or additional budget requisitions to meet the anticipated
timeline.
• .
3.3.4 Issues
•
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.]
4.1 Current Business Process (As-Is)
At any point during or after deployment of web apps or web sites (internal or external) to support business
activities, development/support teams may create and deploy widgets.
1. CMS / database administrators for the employee portal use the CMS tool to create widgets. They can
test widgets in the designated staging environment, then register them and deploy to production.
Page 3|7
2. Development teams may deploy widgets to development and testing environments set up for their
development projects. They must check widget code into and out of the source code repository
according to their projects’ development schedule.
4.2 Proposed Business Process (To-Be)
1. Technical Lead searches repository
2. If widget is not found, user creates a new widget name record.
3. WINS validates that all fields have been completed.
4. WINS confirms that no similar widgets exist
5. User confirms record to be created.
1. User searches repository to locate existing widget description.
2. WINS displays record
3. User selects Edit to open and modify record
4. WINS validates all fields completed correctly
5. User confirms changes.
6. WINS confirms changes and updates Audit table.
Page 4|7
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 Business Requirements
Impacted
Req# Priority Description Rationale Comments
Stakeholders
General / Base Functionality
BR-G- Single repository Development
1 A new Master Widget
001 simplifies teams
repository shall be created to
management of
Page 5|7
Impacted
Req# Priority Description Rationale Comments
Stakeholders
house the name records and widget development Infrastructure
links to the widget objects. across 30+ global engineers
development teams
A widget shall be defined in ID+Name eliminates
BR-G- the repository via a unique duplicate widget
1
002 identifier and name name records
combination.
BR-G-
003
BR-G-
004
BR-G-
005
Security Requirements
Widget creation in the
repository shall be limited to
BR-S-001 1
users with Team Lead or
System Administrator,
Reporting Requirements
The system shall generate a
BR-R-
2 weekly Report of Widget
001
Name Status Changes
Usability Requirements
User interface for the WINS
repository shall be
BR-U-
1 responsive, allowing for
001
proper display on tablet,
laptop, and desktop devices.
Audit Requirements
Any change to a widget
BR-A- name record shall be
1
001 appended with user ID and
date/time stamp.
Page 6|7
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.]
Page 7|7
