Business requirement template

1. Tech Comm Templates
BusinessRequirements Document(BRD)
Template
Project/Initiative
Month 20YY
Version X.XX
Company Information

2. Tech Comm Template BRD
Template provided at no chargeby TechWhirl.com
You arefree to use and customize as needed 1
1 Document Revisions
2 Approvals
Role Name Title Signature Date
ProjectSponsor
BusinessOwner
ProjectManager
SystemArchitect
DevelopmentLead
User Experience Lead
QualityLead
ContentLead
Date Version Number Document Changes
05/02/20xx 0.1 Initial Draft

3. Tech Comm Template BRD
Template provided at no chargeby TechWhirl.com
You arefree to use and customize as needed
3 Introduction
3.1 ProjectSummary
3.1.1 Objectives
[These should describetheoverallgoalin developing theproduct, high leveldescriptionsofwhat
theproductwill do, howthey arealigned to businessobjectives, and therequirementsfor
interaction with othersystems.]
 DeliveraWidgetInteractive NamingSystem(WINS) thatsynchronizesnamingandlinkingof all
widgetsinall systemsacrossthe enterprise.
 Avoidduplicationof widgetnames andreduce time toproductionforexistingprojects.
 Supporttextsearchingonwidgetnamesorbusinessdescriptions.
 Sync widgetnamesandchangestoWindowsandLinux platformadministrationtools.
 Tracks changesto widgetsincludingnew widgets,modifiedwidgets,andwidgets tobe archived.
3.1.2 Background
[Providea brief history of howthe projectcameto be proposed and initiated, including the
businessissues/problemsidentified, and expected benefitofimplementing theproject/developing
theproduct.]
Timelyandaccurate synchronizationof widgetnameswill reduce developmentlevelsof effortsacrossthe
enterprise byeliminatingduplicatenamesof widgetsindevelopmentanddeployed.Acme uncoveredseriously
highlevelsof errorsacrosstestingenvironments,productionerror messages,andincreasedreworkdue tolack
of knowledge aboutwidgetsalreadyinproduction.
3.1.2.1 Business Drivers
[List thebusinessdriversthatmakedevelopmentofthisproductimportant. Thesecan befinancial,
operational, marketorenvironmental.]
 Customersare lookingforfasterupdatestoinformationonthe [product] website,andmayconsider
competitorsif needsare notmet.
 Developmentgrouprequiresascalable solutiontotrackthe widgetsbeingdeployedintoall
environmentstobettermanage resources.

4. Tech Comm Template BRD
Template provided at no chargeby TechWhirl.com
You arefree to use and customize as needed 1
3.2 Project Scope
[Describe whatwork is in scopefor theproject, and specifically whatwork is outof scope…beyond
thecurrentbudget, resourcesand timelineasapproved by theprojectstakeholders. Thisis
designed to prevent“scopecreep”of additionalfeaturesand functionsnotoriginally anticipated.]
3.2.1 In Scope Functionality
 Create name recordsfor widgetsbycategory
o SupplyChain
o ProductionLines
o Internal webapps
o External webapps
 Abilitytocreate/delete widgetnamesrestrictedbyrole
 Searchby name,team,date,lastmodified
 Synchronize widgetsacrossproduct/operationslines
 Provide audittrail
 Reportingonnew,modified,andarchivedwidgetsbytime periodandteam
3.2.2 Out of Scope Functionality
 Create widgetsforsubsidiarycompanyproductlines
 Searchby approver,or rationale
 Archivingof widgetobjects
3.3 SystemPerspective
[Providea completedescription ofthefactors thatcould preventsuccessfulimplementation or
acceleratethe projects, particularly factorsrelated to legaland regulatory compliance, existing
technicalor operationallimitationsin theenvironment, and budget/resourceconstraints.]
3.3.1 Assumptions
 Inventoryof existingwidgetscompletedbyQ1.
 Testingdatacomprisesscrubbedproductiondataasof December31.
3.3.2 Constraints
 Impendingchangestoprivacyregulationsmayimpactdatadictionarydesign.
 Timeline forenterpriseplatformupdateswill impactexecutionof testingplan.
3.3.3 Risks
 PreviouslyapprovedQ2/Q3developmentprojectsmaylimitavailabilityof developmentand QA
resources,necessitatingoutsourcingoradditional budgetrequisitionstomeetthe anticipated
timeline.
 .
3.3.4 Issues


5. Tech Comm Template BRD
Template provided at no chargeby TechWhirl.com
You arefree to use and customize as needed 2
4 Business Process Overview
[Describe howthe currentprocess(es)work, including theinteractionsbetween systemsand
variousbusiness units. Includevisualprocessflowdiagramsto furtherillustratetheprocessesthe
new productwill replaceor enhance.
Usecase documentationand accompanying activity orprocessflowdiagramscan beused to
createthe description(s)of theproposed or“To-Be”processes.]
4.1 Current BusinessProcess(As-Is)
At anypointduringor afterdeploymentof webappsorwebsites(internalorexternal)tosupportbusiness
activities,development/supportteamsmaycreate and deploywidgets.
1. CMS / database administratorsforthe employee portal use the CMStool to create widgets.Theycan
testwidgetsinthe designatedstagingenvironment,thenregisterthemanddeploytoproduction.
2. Developmentteamsmaydeploywidgetstodevelopmentandtestingenvironmentssetupfortheir
developmentprojects.Theymustcheckwidgetcode intoandoutof the source code repository
accordingto theirprojects’developmentschedule.
4.2 Proposed Business Process (To-Be)
1. Technical Leadsearchesrepository
2. If widgetisnot found,usercreatesanew widgetname record.
3. WINSvalidatesthatall fieldshave beencompleted.
4. WINSconfirmsthat nosimilarwidgetsexist
5. User confirmsrecordto be created.

6. Tech Comm Template BRD
Template provided at no chargeby TechWhirl.com
You arefree to use and customize as needed 3
1. User searchesrepositorytolocate existingwidgetdescription.
2. WINSdisplaysrecord
3. User selectsEdittoopenand modifyrecord
4. WINSvalidatesall fieldscompletedcorrectly
5. User confirmschanges.
6. WINSconfirmschangesandupdatesAudittable.

7. Tech Comm Template BRD
Template provided at no chargeby TechWhirl.com
You arefree to use and customize as needed 0
5 Business Requirements
[The specific businessrequirementselicited fromstakeholdersshould belisted, categorized by bothpriority and area offunctionality to
smooth theprocessofreading and tracking them. Includelinksto usecasedocumentation, and otherkey referencematerialasneeded to
maketherequirementsascompleteand understandableaspossible. You may wish to incorporatethefunctionaland non-functional
requirementsinto a traceability matrixthatcan befollowed throughouttheproject.]
The requirementsinthisdocumentare prioritizedasfollows:
Value Rating Description
1 Critical Thisrequirementiscritical tothe successof the project.The projectwill notbe possible withoutthisrequirement.
2 High Thisrequirementishighpriority,butthe project canbe implementedata bare minimumwithoutthisrequirement.
3 Medium Thisrequirementissomewhatimportant,asitprovidessome value butthe projectcanproceedwithoutit.
4 Low Thisis a lowpriorityrequirement,ora“nice to have”feature,if time andcostallowit.
5 Future Thisrequirementisoutof scope forthisproject,andhas beenincludedhere forapossible futurerelease.
5.1 Functional Requirements
Req# Priority Description Rationale
Use Case
Reference
Impacted
Stakeholders
General / Base Functionality
FR-G-001 1
A newMaster Widgetrepositoryshallbe
createdto house the name recordsand
linkstothe widgetobjects.
Single repositorysimplifies
management of widget
developmentacross30+
global developmentteams
Development
teams
Infrastructure
engineers
FR-G-002 1 A widgetshall be definedinthe ID+Name eliminatesduplicate

8. Tech Comm Template BRD
Template provided at no chargeby TechWhirl.com
You arefree to use and customize as needed 1
Req# Priority Description Rationale
Use Case
Reference
Impacted
Stakeholders
repository viaaunique identifierand
name combination.
widgetname records
FR-G-003
FR-G-004
FR-G-005
Security Requirements
FR-S-001 1
Widgetcreationinthe repositoryshall be
limitedtouserswithTeamLeador
SystemAdministrator,
ReportingRequirements
FR-R-001 2
The systemshall generate aweekly
Reportof WidgetName StatusChanges
UsabilityRequirements
FR-U-001 1
User interface forthe WINSrepository
shall be responsive,allowingforproper
displayontablet,laptop,anddesktop
devices.
Audit Requirements
FR-A-001 1 Anychange to a widgetname record

9. Tech Comm Template BRD
Template provided at no chargeby TechWhirl.com
You arefree to use and customize as needed 2
Req# Priority Description Rationale
Use Case
Reference
Impacted
Stakeholders
shall be appendedwithuserIDand
date/time stamp.
5.2 Non-FunctionalRequirements
[Includetechnicaland operationalrequirementsthatarenotspecificto a function. Thistypically includesrequirements such asprocessing
time, concurrentusers, availability, etc.]
ID Requirement
NFR-001 The WINS repositoryshall accommodate upto100 usersconcurrently.
NFR-002 The WINS repositoryshall be designatedatLevel 2for availabilityandSLA purposes.
NFR-003
NFR-004
NFR-005

10. Tech Comm Template BRD
Template provided at no chargeby TechWhirl.com
You arefree to use and customize as needed 0
6 Appendices
6.1 List of Acronyms
[If needed, createa list of acronymsused throughouttheBRDdocumentto aid in comprehension.]
6.2 Glossary of Terms
[If needed, identify and defineany termsthatmay beunfamiliarto readers, includingtermsthat
are uniqueto theorganization, thetechnologyto beemployed, orthestandardsin use.]
6.3 Related Documents
[Providea list of documentsorweb pages, includinglinks, which are referenced in theBRD.]