BUSINESS

REQUIREMENTS DOCUMENT
[Project Name]
[Version #]
[Date]
REVISION HISTORY
DATE VERSION AUTHOR UPDATE DESCRIPTION
January 1,
1900
0.1 Swift Kick Communications Initial Draft
TABLE OF CONTENTS
ALL ABOUT THIS BRD 1
WHATS THE PURPOSE OF THIS DOCUMENT? 1
WHO IS THE TARGET AUDIENCE FOR THIS DOCUMENT? 1
WHAT IS THE COMPANYS VISION FOR THIS PROJECT? 2
EXECUTIVE SUMMARY 2
WHATS THE PROBLEM BEING SOLVED? 2
WHAT ARE THE BUSINESS GOALS? 2
THE PROJECT 101 3
WHAT ARE THE PROJECT GOALS? 3
WHATS IN AND OUT OF SCOPE? 3
IN SCOPE
O!" O# SCOPE
WHO ARE THE STAEHOLDERS? 3
TEAMWOR !
WHOS ON THE PROJECT TEAM AND WHOS DOING WHAT? !
WHAT ARE OUR TEAM STRENGTHS? !
WHAT ARE OUR TEAM LIMITATIONS? !
RISS AND CONSTRAINTS "
WHAT ASSUMPTIONS HAVE WE CONSIDERED? "
WHAT CONSTRAINTS DO WE NEED TO CONSIDER? "
WHATS THE BIG PICTURE? #
WHATS THE CONTEXT FOR THIS PROJECT? #
REQUIREMENTS $
FUNCTION $
$!SINESS %C"I&I"' (&E)$*NO!N P+)%SE, -
)E.!I)E/EN"S 0IS" 1
DOCUMENT SIGN%OFF 10
APPENDIX 11
APPENDIX A& GLOSSARY OF TERMS 11
APPENDIX B& OUTSTANDING QUESTIONS'ISSUES 11
[PROJECT NAME: Business Requirements Document]
ALL ABOUT THIS BRD
WHATS THE PURPOSE OF THIS DOCUMENT?
[State the purpose o the !usiness requirements "ocument an" the !ac#$roun" o
the process comp%ete" to o!tain an" &na%i'e the inormation (ithin the "ocument)
*o( (as the "ocument !ui%t+ *o( (i%% !e use" mo,in$ or(ar"+ -h. is it important
to the !usiness to participate in the re,ie( an" si$n/o0 o it+ ]
WHO IS THE TARGET AUDIENCE FOR THIS DOCUMENT?
[Descri!e (ho the primar. tar$et au"ience is or this "ocument: !usiness area1
"epartment1 ro%es1 etc]
1
[PROJECT NAME: Business Requirements Document]
WHAT IS THE COMPANYS VISION FOR THIS
PROJECT?
EXECUTIVE SUMMARY
[2se the e3ecuti,e summar. to hi$h%i$ht (h. the pro4ect is ta#in$ p%ace1 the
!usiness o!4ecti,es1 an" (hat the !ene&ts (i%% !e to the "ocument au"ience)
Remem!er to sta. hi$h/%e,e%1 as this is 4ust an o,er,ie( 1 (ith more "etai%s !ein$
pro,i"e" throu$hout the "ocument) Emphasi'e the !ene&ts ]
WHATS THE PROBLEM BEING SOLVED?
[Descri!e (hat pro!%em5s6 the pro4ect is reso%,in$) Su$$este" structure is 789:T*EN;
to state pro!%em) Can !e more than one pro!%em1 i so%ution is attemptin$ to so%,e
more than one)]
WHAT ARE THE BUSINESS GOALS?
[Descri!e (hat the !usiness o!4ecti,es:aspirations o the pro4ect are) -hen
"escri!in$ aspirations1 !e sure to inc%u"e: a !eha,iour1 an achie,ement1 an" a
speci&c %e,e% o perormance) Or sse the 7SMART; o!4ecti,es princip%e as a $ui"e%ine <
#eep .our aspirations speci&c1 measura!%e1 attaina!%e1 re%e,ant an" time%.)]
2
[PROJECT NAME: Business Requirements Document]
WHAT IS THIS PROJECT ABOUT?
WHAT ARE THE PROJECT GOALS?
[Separate rom the !usiness o!4ecti,es1 "escri!e (hat the o!4ecti,es are or the
pro4ect < (hat (i%% ma#e it successu%+ Ta%# a!out important "ates the !usiness (i%%
care a!out1 qua%it. o "e%i,er.1 trainin$ o!4ecti,es1 an" e,en the %e,e% o team(or#
an" in"i,i"ua% proessiona% "e,e%opment)
WHATS IN AND OUT OF SCOPE?
[This shou%" a%rea". !e "e&ne" in the pro4ect scope "ocument1 !ut it;s a%(a.s a $oo"
i"ea to put it in the BRD as a remin"er o the %ines the requirements nee" to p%a.
(ithin) Scope creep is a s%ipper. s%ope to step oot upon < "o .our !est to a,oi" it)
An" remem!er1 items i"enti&e" as !ein$ out o scope shou%" a%(a.s !e #ept in min"
as (e%%)]
IN SCOPE
[8n Scope Description]
OUT OF SCOPE
[Out o Scope Description]
WHO ARE THE STAEHOLDERS?
[=ist out .our sta#eho%"ers < users1 s.stems1 etc]

[PROJECT NAME: Business Requirements Document]

TEAMWOR
WHOS ON THE PROJECT TEAM AND WHOS DOING
WHAT?
[8"enti. the pro4ect team !. name1 ro%e1 an" responsi!i%it. (ith respect to the
acti,ities reerre" to (ithin this "ocument) 9or a more "etai%e" approach1 use a RAC8
chart to !rea# "o(n responsi!i%ities !. person an" ro%e) This is a $oo" (a. to p%an
ahea" (ho (i%% !e accounta!%e or (hat1 an" can sa,e a %ot o time "o(n the roa"
(hen somethin$ "oesn;t $et "one an" .ou nee" someone to !%ame1 (hoops 8 mean1
ta%# to)]
RAC8 C*ART
Project Activity Expected Due
Date
Role/Person A Role/Person B Role/Person C
Requirements
E%icitation
R A 8
-rite:2p"ate BRD R A 8
Re,ie( BRD A C R
Si$n/O0 BRD A C R
R >
Responsi!%e
A>Accounta!
%e
C >
Consu%te"
8>8norme"
WHAT ARE OUR TEAM STRENGTHS?
[Thin#in$ a!out the stren$ths an" %imitations o a team !eore the start o the
!usiness requirements phase can he%p .ou put measures in p%ace to curtai% an.
possi!%e issues) 9or e3amp%e1 i the su!4ect matter e3perts on the team are air%. ne(
to the compan.1 .ou ma. (ant to i"enti. that as a possi!%e %imitation as it ma.
a0ect time%ine an" the nee" or an a""itiona% temporar. resource) On the other
han"1 it is a%(a.s $oo" to #no( the stren$ths .ou #no( on .our team < i"enti.in$
speci&c areas1 s#i%%s1 a particu%ar person:ro%e has on the team can he%p .ou $et a
!etter sense ho( each resource can contri!ute)
Thin# a!out the o%%o(in$ questions or stren$ths:
?-hat stren$ths o this team an" or$ani'ation can !e %e,era$e" to successu%%.
comp%ete this "ocument+@
3
[PROJECT NAME: Business Requirements Document]
WHAT ARE OUR TEAM LIMITATIONS?
Thin# a!out the o%%o(in$ questions or %imitations:
?-hat are some %imitations o the team or pro4ect1 (hich nee" to !e consi"ere"
"urin$ the "e,e%opment o this "ocument+@ ]
RISS AND CONSTRAINTS
WHAT ASSUMPTIONS HAVE WE CONSIDERED?
[8"enti.in$1 an" more important%. con&rmin$1 assumptions throu$hout the
"e,e%opment o the pro4ect can he%p .ou to squash an. i%% consequences o ma#in$
them) 8n this section1 i"enti. the assumptions .ou ha,e ma"e a!out a%% aspects o
the !r"1 an" o%%o(/up to assure the. are in"ee" correct) ]
Assumption Aa%i"ate" B. Date
Aa%i"ate"
WHAT CONSTRAINTS DO WE NEED TO CONSIDER?
[8n a""ition to assumptions1 it;s a%so important to consi"er (hat constraints .ou are
(or#in$ (ithin) Thin# outsi"e o the o!,ious time an" mone. an" thin# in terms o
s#i%%s1 #no(%e"$e an" e3perience on the pro4ect team) A%so consi"er prerequisite
con"itions that nee" to !e in p%ace or processes to ta#e p%ace1 or particu%ar
"ea"%ines 5.ear en" or e3amp%e6) =istin$ the constraints #eeps them ,isi!%e
throu$hout the pro4ect)]
4
[PROJECT NAME: Business Requirements Document]
WHATS THE BIG PICTURE?
WHATS THE CONTEXT FOR THIS PROJECT?
[Beore 4umpin$ into the natura%%. nitt. $ritt. "etai%s o requirements1 $i,e the
au"ience some conte3t !. pro,i"in$ a hi$h/%e,e% o,er,ie( o the acti,ities an"
!usiness processes that (i%% !e "etai%e" in the rest o the "ocument) Peop%e %i#e to
start thin#in$ hi$h/%e,e%1 !eore $ettin$ microscopic) Ease them into it !. settin$ the
scene < an" e,en !etter1 "ra( them a picture o it) Most peop%e are ,isua%1 $i,in$
them a picture to $o o,er (i%% not he%p them to un"erstan" the "etai%s %ater on1 !ut it
(i%% sa,e them time in tr.in$ to "o so < an" .ou time in tr.in$ to $et the "ocument
si$ne"/o0B 8 there is more than one !usiness process co,ere" in the "ocument1 then
$i,e them a e( "ia$rams < 4ust !e sure to use su!tit%es to he%p them o%%o( a%on$) A
sma%% "escription or each is he%pu% as (e%%)
Cou cou%" use "i0erent t.pes o "ia$rams here "epen"in$ on .our preerence an"
(hat .our au"ience %i#es !est) M. persona% a,ourite is the process s(im%ane
"ia$ram1 !ecause it;s !usiness ocuse" an" !rea#s it "o(n !. each ma4or ro%e or
"epartment1 (hich he%ps peop%e $et conte3t rom their o(n perspecti,e)]
[S-8M=ANE PROCESS D8ADRAM]
T8P: *.per%in# !et(een .our s(im%ane "ia$ram acti,ities an" the requirements or
it1 so .our rea"ers can easi%. na,i$ate their (a. !ac# an" orth)
5
[PROJECT NAME: Business Requirements Document]
REQUIREMENTS
[The section (e;,e a%% !een (aitin$ or < the requirements section) This is the meat o
the "ocument1 an" (i%% !e (here the !u%# o the (or# is "one in "eterminin$ it;s
contents)
8n %istin$ the requirements1 8 "o so !. the unctiona% areas on the s(im%ane "ia$ram1
an" then !. the !usiness acti,ities (ithin those unctiona% areas) 8 the scope o the
"ocument on%. co,ers one process then1 4ust the acti,ities (ou%" !e %iste" here) The
reason 8 %ist !. !usiness process an" acti,it. is !ecause it ma#es it easier or the
"ocument to !e re,ie(e"1 an" thereore si$ne"/o0 quic#er1 (hen peop%e on%. ha,e a
speci&c section the. nee" to ocus on an" their min" is not 4umpin$ !ac# an" orth)
-hi%e i"ea%%. (e (ant e,er.one to rea" the entire "ocument1 t.pica%%. resources (i%%
sta%% on si$nin$/o0 on the "ocument !ecause the. "on;t ha,e the time to rea" it)
Brea#in$ the requirements section up so that the. can tar$et (hat the. rea"1 ma#es
the process $o a (ho%e %ot easier or them1 an" a (ho%e %ot quic#er or .ou) 8t;s a (in/
(in))
-hat "o 8 mean !. !usiness process an" !usiness acti,it.+ 9or e3amp%e1 the scope
o the entire "ocument ma. co,er the requirements or a ne( &nance s.stem)
Thereore the unctiona% ro%es mi$ht !e somethin$ %i#e accounts pa.a!%e1 accounts
recei,a!%e1 an" the acti,ities un"er them thin$s such as 78ssue an 8n,oice;1 7Reun" a
Customer;1 7Co%%ect Mone. O(e";)
FUNCTION
[Map to s(im%ane "ia$ram unctiona% %anes]
BUSINESS ACTIVITY (VERB'NOUN PHRASE)
[Map to s(im%ane "ia$ram acti,ities]
OVERVIEW
[A simp%e o,er,ie( o the !usiness acti,it.1 (ith an. re%e,ant !ac#$roun"
inormation inc%u"e") Eeep the %an$ua$e 7%a.man; terms1 an" remem!er (ho .our
au"ience is < !e sure to spea# to themB 8 .ou ha,e "one SME inter,ie(s1 inc%u"e a
e( quotes rom those con,ersations or cite peop%e < #eep the (or"in$ %i,e%.1 an"
.ou #eep the au"ience en$a$e") ]
WHOS INVOLVED?
[ 8"enti. the sta#eho%"ers in,o%,e" in this acti,it. < an" (hen .ou "istri!ute the
"ocument1 ma#e it eas. or sta#eho%"er to &n" their o(n ro%es (ithin the "ocument
to re,ie() 8nc%u"in$ the actors (ithin the ta!%e o contents1 is one i"ea to "o that) ]
-
&i6w Sco76
&i6w Sco76
&i6w $i8
Pictur6
&i6w $i8
Pictur6
"i79 +y76rlink t:6 s:a76s ;ack to
t:6 $i8 Pictur6 s6ction an< Sco76
s6ction
[PROJECT NAME: Business Requirements Document]
IF YOU USE USE CASES *&
USE CASE
[8 .ou ha,e use" use cases to e%icit the requirements1 this is (here .ou can %ist a%%
the use case "etai%s or this acti,it. 5pre/con"itions1 tri$$ers1 outcomes1 steps1
a%ternate use cases etc6))]
REQUIREMENTS LIST
[8n this section1 %ist out the requirements or the i"enti&e" acti,it.) 8 usua%%. !rea#
requirements out !. t.pe1 !ut o course each compan. has their o(n (a. o "oin$ it1
an" .ou shou%" or$ani'e this section as .ou see &t) -here 8 am a!%e to1 8 %i#e to trace
requirements !oth !ac#(ar" to the use case step F1 an" or(ar" to the test case1
(hen it is e,entua%%. constructe") The 7teste"; co%umn is a he%pu% co%umn or not
on%. the GA;s1 !ut a%so the !usiness users (ho use the BRD as a reerence "urin$
their o(n 2AT < this (a. the. can ensure that each requirement has !een teste"1
an" ha,e that "ocumente") ]
WHAT ARE THE BUSINESS REQUIREMENTS?
Requirement
ID
Requirement Priori
ty
Use
Case
Step
est
Case !
ested
BRD)HH)9HHHI
BRD)HH)9HHHJ
BRD)HH)9HHHK
BRD)HH)9HHHL
EtcM
WHAT ARE THE PERFORMANCE REQUIREMENTS?
Requirement
ID
Requirement Priori
ty
Use
Case
Step
est
Case !
ested
BRD)HH)PHHHI
BRD)HH)PHHHJ
BRD)HH)PHHHK
BRD)HH)PHHHL
1
[PROJECT NAME: Business Requirements Document]
EtcM
WHAT ARE THE SECURITY REQUIREMENTS?
Requirement
ID
Requirement Priori
ty
Use
Case
Step
est
Case !
ested
BRD)HH)SHHHI
BRD)HH)SHHHJ
BRD)HH)SHHHK
BRD)HH)SHHHL
EtcM
WHAT ARE THE REPORTING REQUIREMENTS?
Requirement
ID
Report
"ame
Description #requen
cy
Criteria $utpu
t
BRD)HH)RHHHI
BRD)HH)RHHHJ
BRD)HH)RHHHK
BRD)HH)RHHHL
EtcM
+OTHER REQUIREMENT TYPES*,
[REPEAT REG28REMENT OAERA8E-1 ACTORS1 2SE CASE1 AND REG28REMENTS
=8ST8NDS 9OR EAC* ACT8A8TC 2NDER T*E 92NCT8ONA= AREA1 T*EN MOAE ONTO T*E
NENT 92NCT8ONA= AREA AND =8ST O2T REG28REMENTS 9OR EAC* ACT8A8TC T*ERE)
A== S*O2=D T8E BACE TO T*E D8ADRAM PROA8DED 8N T*E B8D P8CT2RE]
9
[PROJECT NAME: Business Requirements Document]
DOCUMENT SIGN%OFF
[Si$n/o0 is important so as to a,oi" uture "e%a.s an" conOicts: !e%o( is su$$este"
(or"in$1 chan$e as .ou (ish)]
8 ha,e re,ie(e" an" appro,e o the inormation an" requirements out%ine" (ithin this
!usiness requirements "ocument or the [PROJECT NAME] pro4ect1 (ith the o%%o(in$
con"itions1 to !e met !. the [require" "ate < testin$1 imp%ementation1 etc]
C$"DII$" SE B% DAE
C$&P'EED
8 un"erstan" that an. urther requeste" chan$es1 outsi"e o the con"itions state"1 to
the o!4ecti,es1 requirements or content %iste" (ithin this "ocument (i%% ris# a "e%a. in
the &na% "e%i,er. "ate an" cost o the pro4ect)
PPPPPPPPPPPPPPPPPPPPPPPPPP PPPPPPPPPPPPP
[si$nature] [Ro%e] ["ate]
PPPPPPPPPPPPPPPPPPPPPPPPPP PPPPPPPPPPPPP
[si$nature] [Ro%e] ["ate]
PPPPPPPPPPPPPPPPPPPPPPPPPP PPPPPPPPPPPPP
[si$nature] [Ro%e] ["ate]
10
[PROJECT NAME: Business Requirements Document]
APPENDIX
APPENDIX A& GLOSSARY OF TERMS
[A $%ossar. o terms an" acron.ms can !e useu% or %ar$er pro4ects < !etter to
e3p%ain in the "ocument (hen .ou can)]
APPENDIX B& OUTSTANDING QUESTIONS'ISSUES
[Eeep trac# o pro4ect questions an" issues that nee" to !e a""resse" < an" once
the. are a""resse"1 put the ans(er in here) This section can turn into a han". 9AG1
(hich can !e he%pu% or the au"ience)]
11