<Project Name>

<AMP Reference Number>

Business Requirements Specification
<Section/Department>
<Date>

Version Control
Version
Number
Date Comments
1.0 15
th
March 2004 Initial draft for review
Approals
Date Name an! Position Si"nature

#able of Contents
1. INTRODUCTION............................................................................................1
2. Fnctional re!ire"ent#.................................................................................1
2.1 $Re!ire"ent 1%. .................................................................................1
2.1.1 De#cri&tion....................................................................................1
2.2 $Re!ire"ent 2%. .................................................................................1
2.2.1 De#cri&tion....................................................................................1
'. (erfor"ance Re!ire"ent#.............................................................................2
4. Data)a#e......................................................................................................2
5. De#i*n Con#traint#........................................................................................2
+. ,ecrit- and .dit.........................................................................................'
/. 0ardware and ,oftware..................................................................................'
1. Interface#.....................................................................................................'
2. Re&ortin*.....................................................................................................4
10. O&eration# and Maintenance.........................................................................4

$N.M3 OF (RO43CT%
$.M( IT R3F3R3NC3 NUM53R%
R36UIR3M3NT, ,(3CIFIC.TION
$% &N#R'D(C#&'N
. de#cri&tion of the intent and *oal# of the #-#te"7 what the *eneral crrent )#ine##
&roce## i#7 and ideall- a de#cri&tion or attach"ent of the new #-#te" re!ire"ent#
fro" the client8# &er#&ective. 9here a&&ro&riate7 attach"ent# in the for" of
flowchart# or &roce## flow dia*ra"# #howin* overall )#ine## &roce##in* flow# wold
)e #efl.
)% *unctional requirements
For each fnctional re!ire"ent the followin* detail# #hold )e inclded:
)%$ <Requirement $>%
;a)el or na"e of the re!ire"ent e*. Entering leave requests
)%$%$ Description
. de#cri&tion of the *eneral fnction to )e &erfor"ed and a clear nder#tandin* of
how the fnction wold )e te#ted ie. what identifie# that thi# &articlar fnction i#
wor<in* correctl- when in #e7 a# well a# an- other introdctor- or )ac<*rond
"aterial that "i*ht clarif- the &r&o#e and intent of the fnction.
,)#e!ent #)#ection# within thi# fnction re!ire"ent #ection "a- var- however
the- #hold detail all re!ired infor"ation a)ot thi# fnction incldin*:
9hen thi# fnction i# #ed and )- what=who"
9hat infor"ation i# re!ired to )e entered
>ol"e and fre!enc- of an- data in&t to the fnction
9here doe# the in&t data co"e fro" ?e*. (a&er for"7 interface@
.n- validation re!ire"ent# on the data e*. >alid ran*e# of data
.n- #ecrit- re!ire"ent# e*. fnction i# onl- athori#ed for certain #er#
9hat &roce##in* i# re!ired to )e carried ot within the fnction
9hat ot&t# there "a- )e ie. de#tination of data
.n- #&ecific error handlin* re!ired
.n- con#traint# on the fnction or the in&t# to the fnction
Reference to interface #&ecification# where a&&ro&riate
)%) <Requirement )>%
;a)el or na"e of the re!ire"ent e*. Approve Leave request
)%)%$ Description
. de#cri&tion of the *eneral fnction to )e &erfor"ed and a clear nder#tandin* of
how the fnction wold )e te#ted ie. what identifie# that thi# &articlar fnction i#
wor<in* correctl- when in #e7 a# well a# an- other introdctor- or )ac<*rond
"aterial that "i*ht clarif- the &r&o#e and intent of the fnction.
,)#e!ent #)#ection# within thi# fnction re!ire"ent #ection "a- var- however
the- #hold detail all re!ired infor"ation a)ot thi# fnction incldin*:
$In#ert doc"ent filena"e% (a*e 1
$N.M3 OF (RO43CT%
$.M( IT R3F3R3NC3 NUM53R%
R36UIR3M3NT, ,(3CIFIC.TION
9hen thi# fnction i# #ed and )- what=who"
9hat infor"ation i# re!ired to )e entered
>ol"e and fre!enc- of an- data in&t to the fnction
9here doe# the in&t data co"e fro" ?e*. (a&er for"7 interface@
.n- validation re!ire"ent# on the data e*. >alid ran*e# of data
.n- #ecrit- re!ire"ent# e*. fnction i# onl- athori#ed for certain #er#
9hat &roce##in* i# re!ired to )e carried ot within the fnction
9hat ot&t# there "a- )e ie. de#tination of data
.n- #&ecific error handlin* re!ired
.n- con#traint# on the fnction or the in&t# to the fnction
Reference to interface #&ecification# where a&&ro&riate
+% Performance Requirements
,&ecific infor"ation on how the #-#te" i# re!ired and=or eA&ected to &erfor". Thi#
cold inclde infor"ation on:
eA&ected n")er of #er#7
vol"e of tran#action#7
#&eed of &roce##in* re#&on#e#7
availa)ilit- and &Bti"e7
offBca"&# or onBca"&# availa)ilit- or &erfor"ance etc.
,% Database
Thi# #ection relate# to tho#e #-#te"# where a new central data)a#e7 or "odification to
an eAi#tin* data)a#e7 i# re!ired. It #hold identif- and #&ecif- an- #&ecific data)a#e
de#i*n i##e# incldin*:
eA&ected #iCe and *rowth of the data)a#e7
n")er of in#tance# ?ie. Different environ"ent# #ch a# develo&"ent7 te#t and
&rodction@ that are re!ired7
what ver#ion and relea#e of the data)a#e i# to )e #ed ?e*. Oracle v2@7
how the data)a#e will )e acce##ed e*. what other #-#te"#=a&&lication# are
li<el- to )e re!ired to have direct acce## to the data)a#e7
will #er# or #&&ort #taff &erfor" adhoc !erie# or re&ort# on the data.
-% Desi"n Constraints
Thi# #ection #hold identif- a# "an- &o##i)le technical and de#i*n con#traint# that can
)e identified &Bfront in the &roDect lifec-cle a# well a# how the- "a- )e re#olved. It
i# #i"ilar in #o"e wa-# to identif-in* &articlar ri#<# and "iti*ation #trate*ie#.
,&ecific con#traint# "a- relate to different o&tion# and reco""endation#. ,o"e
eAa"&le# inclde:
the a)ilit- ?or ina)ilit-@ to introdce a #&ecific technolo*- into 6UT7
$In#ert doc"ent filena"e% (a*e 2
$N.M3 OF (RO43CT%
$.M( IT R3F3R3NC3 NUM53R%
R36UIR3M3NT, ,(3CIFIC.TION
eAi#tin* )#ine## &roce##e# or &olicie# that i"&act on identif-in* an
a&&ro&riate de#i*n #oltion7
crrent hardware or o&eratin* #oftware re#triction#7 and
even #o"ethin* that "a- )e affected )- 6UT8# *eneral #er cltre.
.% Securit/ an! Au!it
. de#cri&tion of the #ecrit- and adit re!ire"ent# of the #-#te" detailin*:
9ho ha# acce## to what fnction# or &art# of the #-#te"
0ow the acce## #ecrit- i# i"&le"ented and controlled e*. If re#trictin* certain
fnction# to #er# then doe# thi# #e 6UT8# central athentication director- or
6UT >irtal &ortal acce## to control thi# and how.
If adhoc data acce## i# re!ired how will #er acce## )e ad"ini#tered or
contolled.
0ow i# thi# "onitored or lo**ed.
0% 1ar!2are an! Soft2are
. de#cri&tion of vario# hardware and #oftware &latfor" re!ire"ent# that need to )e
con#idered where a&&ro&riate #ch a#:
9hat #erver?#@ #&ecification
9hat o&eratin* #-#te"
0ow "ch "e"or-
De#<to& client re!ire"ent# or co"&ata)ilit-
Mo)ile device#
,&ecific networ< e!i&"ent or confi*ration
,tora*e re!ire"ent# #ch a# #tora*e #iCe and=or ,.N co"&ata)ilit-
3% &nterfaces
The "aDorit- of #-#te"# at 6UT re!ire #o"e for" of inte*ration or interfacin* with
other #-#te"#7 the networ< and=or e!i&"ent. Thi# #ection #hold define or
reference the nece##ar- &rotocol# or #&ecification# for the vario# interface# re!ired.
Data interface# "a- con#i#t of:
how one a&&lication i# e")edded in another7
data "ove"ent i##e# #ch a# where data co"e# fro" or *oe# to7
how and when the data need# to )e "oved7
what other #-#te" or ti"in* de&endencie# there are on the data in the new
#-#te" or data fro" other #-#te"#7 and
what #-#te" to #-#te" acce## accont# or &roce##e# "a- )e re!ired.
0ardware interface# "a- refer to #&ecific hardware &latfor"# or e!i&"ent )ein* &t
in &lace e*. Networ< hardware7 &orta)le device# etc.
$In#ert doc"ent filena"e% (a*e '
$N.M3 OF (RO43CT%
$.M( IT R3F3R3NC3 NUM53R%
R36UIR3M3NT, ,(3CIFIC.TION
Co""nication interface# will relate to an- #&ecific re!ire"ent# for co""nication
over the networ< e*. networ< &rotocol#7 a# well a# tho#e re!ired for co""nicatin*
with #&ecific hardware.
4% Reportin"
9hat re&ort# are re!ired fro" the #-#te". Inclde a "oc<B& of their *eneral la-ot
and de#i*n.
9hether or not adBhoc re&ortin* will )e re!ired and how thi# will )e carried ot7 for
eAa"&le7 a 5#ine## O)Dect# Univer#e.
$5% 'perations an! Maintenance
Thi# #ection wold detail how the #-#te" i# eA&ected to o&erate e*:
5#ine## ti"eta)le# and &ea<=low &eriod#
5ac<& and recover- re!ire"ent# and ti"in*
$In#ert doc"ent filena"e% (a*e 4