brd example

8/11/2019 BRD Example

1/15

[Insert Project Name]Business Requirements Document (BRD)

Version i


2/15

VERSIONANDAPPROVALSUTORS

VERSIONHISTORY

Version # Date Revised B Reason !or c"ane

This document has been approved as the official Business Requirements Document for ,

and accuratel reflects the current understandin! of business requirements" #ollo$in! approval of thisdocument, requirement chan!es $ill be !overned b the project%s chan!e mana!ement process, includin!impact analsis, appropriate revie$s and approvals"

DOCUMENTAPPROVALS

A$$rover Name Project Ro%e Sinat&re'E%ectronic A$$rova% Date


3/15

TABLEO()ONTENTS

&R'*TDT+-.""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""/

'VRV0"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""/

D'*123TR.'1R*.""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""/

4-'..+R5'#TR2.""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""/

&R'*T'VRV0""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""/

4.1 Project Overview and Background....................................................................................................1

4.2 Project Dependencies....................................................................................................................... 2

4.3 Stakeholders..................................................................................................................................... 2

65+..12&T'3.+3D*'3.TR+3T."""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""7

5.1 e! "ssu#ptions and $onstraints.......................................................................................... .......... 2

1.*+..""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""7

%se $ase Diagra#..................................................................................................................................2

%se $ase &arrative.................................................................................................................................3

B1.3..R81R23T."""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""9

+&&3D:."""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""";

"ppendi' " ( Business Process )lows................................................................................................ ...*

"ppendi' B ( Business +ules $atalog..................................................................................................1,

"ppendi' $- odels..............................................................................................................................1,

/racea0ilit! atri'................................................................................................................................. 1,

%se $ase &arrative nstructions........................................................................................................ ...1,


4/15

PRO*E)TDETAILS

Project Name nter &roject 3ame

Project T$e (e.g. New Initiative or Phase II)

Project Start Date

Project End DateProject S$onsor

Primar Driver (e.g. Mandatory or Efficiency)

Secondar Driver

Division

Project +anaer'De$t

OVERVIE,

This document defines the hi!h level requirements insert project name=" t $ill be used as the basisfor the follo$in! activities

*reatin! solution desi!ns

Developin! test plans, test scripts, and test cases

Determinin! project completion

+ssessin! project success

DO)U+ENTRESOUR)ES

Name B&siness Unit Ro%e

-LOSSAR.O(TER+S

Term'Acronm De!inition

PRO*E)TOVERVIE,

/01 Project Overvie2 and Bac3ro&nd


5/15

/05 Project De$endencies

"

Use )ase Diaram


6/15

Use )ase Narrative


7/15

A" nteract $ith the campus map usin! available functionalit

+lternative *ourses 3one

@ceptions 3one

ncludes

&riorit Hi!h

#requenc of 1se 'nce per visit"

Business Rules TBDI.pecial Requirements 7C; access

Response times comparable to common $eb mappin! solutions

(e"!" 4oo!le 2aps)

1 of 2 accessibilit requirements

1 of 2 e*ommunications requirements

+ssumptions

3otes and ssues

1se *ase 4raphic


8/15

BUSINESSRE9UIRE+ENTS

The follo$in! sections document the various business requirements of this project"

Requirement

Tpe ,

D

G&

refi@JJ

,D

G3umber

#unction G #eature Requirement1se*

ase

Reference

Required

::

::

::

*omments

Business 1ser Requirements# FFF/

# FFF7

# FFFA

# FFFC

# FFF9

# FFF;

# FFF;

# FFFK

Reportin! Requirements# FFF/

# FFF7

# FFFA

# FFFC

# FFF9

# FFF;

# FFF;

# FFFK

1ser +ccess.ecurit Requirements# FFF/

# FFF7

# FFFA

# FFFC

# FFF9

# FFF;

# FFF;

# FFFK

.ervice -evel&erformance Requirements# FFF/

# FFF7

# FFFA

# FFFC

# FFF9

# FFF;

# FFF;

# FFFK

.calabilit Requirements# FFF/

# FFF7


9/15

# FFFA

# FFFC

# FFF9

# FFF;

# FFF;

# FFFK

.upport and 2aintenance Requirements# FFF/

# FFF7

# FFFA

# FFFC

# FFF9

# FFF;

# FFF;

( ;;;


10/15

APPENDI=ES

A$$endi> A ? B&siness Process (%o2s


11/15

s Is !iagrams


12/15

"o #e !iagrams


13/15

A$$endi> B ? B&siness R&%es )ata%o

Business Rule 3ame "P B+1Description

Related Rules

A$$endi> )@ +ode%s

Tracea4i%it +atri>

Use )ase Narrative Instr&ctions


14/15

Use )ase (ie%d Name De!inition

tas?s" Different actors often correspond to differentuser classes, or roles, identified from the customercommunit that $ill use the product" 3ame theactor(s) that $ill be performin! this 1se *ase"

Description &rovide a brief description of the reason for and

outcome of this use case, or a hi!hleveldescription of the sequence of actions and theoutcome of e@ecutin! the 1se *ase"

&reconditions -ist an activities that must ta?e place, or anconditions that must be true, before the 1se *asecan be started" 3umber each precondition"@amples

1ser%s identit has been authenticated"

1ser%s computer has sufficient free memor

available to launch tas?

&ost conditions Describe the state of the sstem at the conclusionof the use case e@ecution" 3umber each postcondition" @amples

Document contains onl valid .42- ta!s" &rice of item in database has been updated $ith

ne$ value

3ormal *ourse &rovide a detailed description of the user actionsand sstem responses that $ill ta?e place durin!e@ecution of the use case under normal, e@pectedconditions" This dialo! sequence $ill ultimatel leadto accomplishin! the !oal stated in the use casename and description" This description ma be$ritten as an ans$er to the hpothetical question,LHo$ do JM This is best done as a numbered listof actions performed b the actor, alternatin! $ith

responses provided b the sstem"+lternative *ourses Document other, le!itimate usa!e scenarios that

can ta?e place $ithin this use case separatel inthis section" .tate the alternative course, anddescribe an differences in the sequence of stepsthat ta?e place" 3umber each alternative courseusin! the 1se *ase D as a prefi@, follo$ed b L+*Mto indicate L+lternative *ourseM" @ample:"5"+*"/

@ceptions Describe an anticipated error conditions that couldoccur durin! e@ecution of the use case, and defineho$ the sstem is to respond to those conditions"

+lso, describe ho$ the sstem is to respond if theuse case e@ecution fails for some unanticipatedreason" 3umber each e@ception usin! the 1se*ase D as a prefi@, follo$ed b L:M to indicateL@ceptionM" @ample :"5":"/

ncludes -ist an other use cases that are included (LcalledM)b this use case" *ommon functionalit thatappears in multiple use cases can be split out into aseparate use case that is included b the ones thatneed that common functionalit"

&riorit ndicate the relative priorit of implementin! the


15/15

Use )ase (ie%d Name De!inition

functionalit required to allo$ this use case to bee@ecuted" The priorit scheme used must be thesame as that used in the soft$are requirementsspecification"

#requenc of 1se stimate the number of times this 1se *ase $ill be

performed b the actors per some appropriate unitof time"

Business Rules -ist an business rules that influence this 1se*ase"

.pecial Requirements dentif an additional requirements, such asnonfunctional requirements, for the use case thatma need to be addressed durin! desi!n orimplementation" These ma include performancerequirements or other qualit attributes"

+ssumptions -ist an assumptions that $ere made in theanalsis that led to acceptin! this use case into theproduct description and $ritin! the use casedescription"

3otes and ssues -ist an additional comments about this use caseor an remainin! open issues or TBDs (To BeDetermined) that must be resolved" dentif $ho $illresolve each issue, the due date, and $hat theresolution ultimatel is"

brd example

Documents