[Insert Project Name]

Business Requirements Document (BRD)

Version i

VERSION AND APPROVALS
UTORS
VERSION HISTORY
Version # Date Revised B Reason !or c"an#e
This document has been approved as the official Business Requirements Document for <project name>,
and accuratel reflects the current understandin! of business requirements" #ollo$in! approval of this
document, requirement chan!es $ill be !overned b the project%s chan!e mana!ement process, includin!
impact analsis, appropriate revie$s and approvals"
DOCUMENT APPROVALS
A$$rover Name Project Ro%e Si#nat&re'E%ectronic A$$rova% Date
TABLE O( )ONTENTS
&R'()*T D)T+,-.""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""/
'V)RV,)0"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""/
D'*12)3T R).'1R*).""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""/
4-'..+R5 '# T)R2.""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""/
&R'()*T 'V)RV,)0""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""/
4.1 Project Overview and Background.................................................................................................... 1
4.2 Project Dependencies....................................................................................................................... 2
4.3 Stakeholders..................................................................................................................................... 2
6)5 +..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).. R)81,R)2)3T."""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""9
+&&)3D,:)."""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""";
"ppendi' " ( Business Process )lows................................................................................................... *
"ppendi' B ( Business +ules $atalog.................................................................................................. 1,
"ppendi' $- .odels.............................................................................................................................. 1,
/racea0ilit! .atri'................................................................................................................................. 1,
%se $ase &arrative 1nstructions........................................................................................................... 1,
PRO*E)T DETAILS
Project Name )nter &roject 3ame
Project T$e (e.g. New Initiative or Phase II)
Project Start Date
Project End Date
Project S$onsor
Primar Driver (e.g. Mandatory or Efficiency)
Secondar Driver
Division
Project +ana#er'De$t
OVERVIE,
This document defines the hi!h level requirements <insert project name=" ,t $ill be used as the basis
for the follo$in! activities>
*reatin! solution desi!ns
Developin! test plans, test scripts, and test cases
Determinin! project completion
+ssessin! project success
DO)U+ENT RESOUR)ES
Name B&siness Unit Ro%e
<,dentif all sta?eholders
and resources involved
in !atherin!
requirements>
-LOSSAR. O( TER+S
Term'Acronm De!inition
<,dentif an terms and acronms
used $ithin this document>
PRO*E)T OVERVIE,
/01 Project Overvie2 and Bac3#ro&nd
<T"is in!ormation can 4e ta3en !rom t"e Project )"arter" This is a brief description of $hat the
project is about" ,t includes the current situation, the problem and the objectives" This section serves
as the vision statement for the requirements" )ach requirement should brin! the project closer to the
vision">
/05 Project De$endencies
<-ist an related ?no$n projects that relate in $hole or in part, or has a dependenc on this project">
/06 Sta3e"o%ders
The follo$in! comprises the internal and e@ternal sta?eholders $hose requirements are represented
b this document>
Sta3e"o%ders
/"
7"
A"
7E. ASSU+PTIONS AND )ONSTRAINTS
801 7e Ass&m$tions and )onstraints
# Ass&m$tions
-ist an assumptions the requirements are based on
# )onstraints
-ist an constraints the requirements are based on
USE )ASES
< The primar purpose of the 1se *ase is to capture the required sstem behavior from the
perspective of the endBuser in achievin! one or more desired !oals" + 1se *ase contains a
description of the flo$ of events describin! the interaction bet$een actors and the sstem" The use
case ma also be represented visuall in 12- in order to sho$ relationships $ith other the use cases
and actors>"
Use )ase Dia#ram

Use )ase Narrative
<)ach 1se *ase should be documented usin! this template" Refer to the +ppendi@ for 1se *ase
3arrative instructions>
1se *ase ,D>
1se *ase
3ame>
*reated B> -ast 1pdated B>
Date *reated> Date -ast 1pdated>
+ctors>
Description>
&reconditions>
&ostconditions>
3ormal *ourse>
+lternative *ourses>
)@ceptions>
,ncludes>
&riorit>
#requenc of 1se>
Business Rules
.pecial Requirements>
+ssumptions>
3otes and ,ssues>
1se *ase 4raphic
Example of a completed use case:
1se *ase ,D> /
1se *ase
3ame>
Vie$ ,nteractive *ampus 2ap
*reated B> Dan .$ard -ast 1pdated B>
Date *reated> CD/EDFE Date -ast 1pdated>
+ctors> 1ser
Description> This use case describes the main $a this interactive campus map
$ill be used G as a $eb bro$ser accessed application" The user
accesses the appropriate 1R- and interacts $ith the functionalit
made available"
&reconditions> 0eb bro$ser opened, and interactive campus map 1R- accessed"
&ostconditions> 1ser navi!ates from interactive campus map $eb site"
3ormal *ourse> /" 'pen bro$ser
7" 3avi!ate to campus map 1R-
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> 7CD; 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

BUSINESS RE9UIRE+ENTS
The follo$in! sections document the various business requirements of this project"
R
e
q
u
i
r
e
m
e
n
t
T

p
e
,
D

G

&
r
e
f
i
@

J
J
,
D

G

3
u
m
b
e
r
#unction G #eature B Requirement
1
s
e

*
a
s
e
R
e
f
e
r
e
n
c
e
R
e
q
u
i
r
e
d
:
:
:
:
:
:
*omments
Business 1ser Requirements
# FFF/
# FFF7
# FFFA
# FFFC
# FFF9
# FFF;
# FFF;
# FFFK
Reportin! Requirements
# FFF/
# FFF7
# FFFA
# FFFC
# FFF9
# FFF;
# FFF;
# FFFK
1ser +ccessD.ecurit Requirements
# FFF/
# FFF7
# FFFA
# FFFC
# FFF9
# FFF;
# FFF;
# FFFK
.ervice -evelD&erformance Requirements
# FFF/
# FFF7
# FFFA
# FFFC
# FFF9
# FFF;
# FFF;
# FFFK
.calabilit Requirements
# FFF/
# FFF7
# FFFA
# FFFC
# FFF9
# FFF;
# FFF;
# FFFK
.upport and 2aintenance Requirements
# FFF/
# FFF7
# FFFA
# FFFC
# FFF9
# FFF;
# FFF;
( ;;;<
APPENDI=ES
A$$endi> A ? B&siness Process (%o2s
<Describe the current e@istin! process $or?flo$ usin! flo$ dia!rams (i"e" Visio #lo$charts) andDor a detailed narrative">
s Is !iagrams
<,nsert +s ,s Dia!rams here (if applicable)>
"o #e !iagrams
<,nsert To Be Dia!rams here (if applicable)>
A$$endi> B ? B&siness R&%es )ata%o#
<Instructions: Use the following template for each business rule. >
Business Rule 3ame> <The name should !ive ou a !ood idea about the topic
of the business rule">
,dentifier <Defines unique identifier"> 23".P425 B+1
Description <Defines the rule in detail"> 23".P425 6"ll e#plo!ee
la0or is tracked7 reported and 0illed in 15 #inute
incre#ents.8
)@ample <('ptional) +n e@ample of the rule>
.ource <.ource of the rule" )"!" sta?eholder>
Related Rules <-ist of related rules, to support traceabilit>
A$$endi> )@ +ode%s
<,nsert models here>
Tracea4i%it +atri>
<,nsert traceabilit matri@ here>
Use )ase Narrative Instr&ctions
<,nstructions for completin! the 1se *ase 3arrative are included here" Remove these
instructions from the completed Business Requirements Document>"
Use )ase (ie%d Name De!inition
1se *ase ,D 4ive each use case a unique numeric identifier, in
hierarchical form> :"5" Related use cases can be
!rouped in the hierarch" #unctional requirements
can be traced bac? to a labeled 1se *ase"
1se *ase 3ame .tate a concise, resultsBoriented name for the use
case" These reflect the tas?s the user needs to be
able to accomplish usin! the sstem" ,nclude an
action verb and a noun" .ome e@amples>
Vie$ part number information"
2anuall mar? hperte@t source and establish
lin? to tar!et"
&lace an order for a *D $ith the updated
soft$are version
*reated B ,nclude the name of the person $ho initiall
documented this 1se *ase"
Date *reated )nter the date on $hich the use case $as initiall
documented
Date -ast 1pdated )nter the date on $hich the use case $as most
recentl updated
-ast 1pdated B ,nclude the name of the person $ho performed the
most recent update to the use case description"
+ctor )nter the person or other entit e@ternal to the
soft$are sstem bein! specified $ho interacts $ith
the sstem and performs use cases to accomplish
Use )ase (ie%d Name De!inition
tas?s" Different actors often correspond to different
user classes, or roles, identified from the customer
communit that $ill use the product" 3ame the
actor(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!hBlevel
description of the sequence of actions and the
outcome of e@ecutin! the 1se *ase"
&reconditions -ist an activities that must ta?e place, or an
conditions that must be true, before the 1se *ase
can 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 conclusion
of the use case e@ecution" 3umber each post
condition" )@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 actions
and sstem responses that $ill ta?e place durin!
e@ecution of the use case under normal, e@pected
conditions" This dialo! sequence $ill ultimatel lead
to accomplishin! the !oal stated in the use case
name and description" This description ma be
$ritten as an ans$er to the hpothetical question,
LHo$ do , <accomplish the tas? stated in the use
case name>JM This is best done as a numbered list
of 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 in
this section" .tate the alternative course, and
describe an differences in the sequence of steps
that ta?e place" 3umber each alternative course
usin! the 1se *ase ,D as a prefi@, follo$ed b L+*M
to indicate L+lternative *ourseM" )@ample>
:"5"+*"/
)@ceptions Describe an anticipated error conditions that could
occur durin! e@ecution of the use case, and define
ho$ the sstem is to respond to those conditions"
+lso, describe ho$ the sstem is to respond if the
use case e@ecution fails for some unanticipated
reason" 3umber each e@ception usin! the 1se
*ase ,D as a prefi@, follo$ed b L):M to indicate
L)@ceptionM" )@ample> :"5"):"/
,ncludes -ist an other use cases that are included (LcalledM)
b this use case" *ommon functionalit that
appears in multiple use cases can be split out into a
separate use case that is included b the ones that
need that common functionalit"
&riorit ,ndicate the relative priorit of implementin! the
Use )ase (ie%d Name De!inition
functionalit required to allo$ this use case to be
e@ecuted" The priorit scheme used must be the
same as that used in the soft$are requirements
specification"
#requenc of 1se )stimate the number of times this 1se *ase $ill be
performed b the actors per some appropriate unit
of time"
Business Rules -ist an business rules that influence this 1se
*ase"
.pecial Requirements ,dentif an additional requirements, such as
nonfunctional requirements, for the use case that
ma need to be addressed durin! desi!n or
implementation" These ma include performance
requirements or other qualit attributes"
+ssumptions -ist an assumptions that $ere made in the
analsis that led to acceptin! this use case into the
product description and $ritin! the use case
description"
3otes and ,ssues -ist an additional comments about this use case
or an remainin! open issues or TBDs (To Be
Determined) that must be resolved" ,dentif $ho $ill
resolve each issue, the due date, and $hat the
resolution ultimatel is"