BRD Document
BRD Document
BRD Document
<Logo of manni or mansoft> Business Requirement Specification <Client Logo> Project Name ocument Name <Name of the Project> Business Requirement Specification Re"ie#er
Signature
!uthor
Signature
!ppro"er
Signature
ocument
istri-ution
< Specific the name of individual from customer side as well as form mania or man soft side, who will be receiving this document. Also specify their role as PM, VH, ! etc " his document will be directly distributed to the following individuals. Sr. No. <client #ame / 0 Mania $orporation% mania System / 0 Name of the in.i"i.ual Role
'aster files are store. electronically an. are a"aila-le to all associates Printe. copies of the master files are for reference only
)a-le of contents
/. *ntro.uction................................................. ............1
&.& Purpose...........................................................' &.( Scope...............................................................' &.) *efinitions, acronyms and abbreviations.........' &.' +eference.........................................................' &., *ocument Structure.........................................'
1. !nne4ure5s6................................................. ...............7
/. *N)R% &C)*%N
/./ P4+P5S6
<7n this sub.section specify the purpose of the document and the intended audience"
/.0 S$5P6
<7n this sub section, describe the domain to be covered and brief description of the domain also specify e8clusions, if any"
<7n this sub.section provide all the terms used in this document. Also list in the same subsection acronyms and abbreviation re2uired to properly interpreting the document "
Abbreviation
*escription
&.' +6/6+6#$6S sr .no *ocume *ocume Versio nt itle nt #o. n & ( ) Author +eleas ed date
0. !SS&'P)*%NS !N
(P(N (NC*(S
<Provide the appropriate diagram to describe current business process and describe the e8isting functionality of the same."
2.0 PR%P%S(
B&S*N(SS PR%C(SS
<Provide the activity diagram to describe propose business process and describe the e8isting functionality of the same."
<Provide the business process flow diagram to describe proposed business sub. process and describe the e8isting functionality of the same." #5 6; +epeat these sections to describe each current -usiness sub.process
Post conditions
*ependencies < *escribe the assumptions 0if any1specific to this customer re2uirement, for e.g. dependency on some other re2uests%action%transactions%e8ternal interfaces%result of some other transactions etc" $onstraints << *escribe the constraints 0if any1specific to this customer re2uirement, for e.g. $onstraints related to operating. implementing. $ustomer testing, environment etc" #on <*escribe #on /unctional +e2uirement" /unctional +e2uirement #on functional <Specify the uni2ue no. for #on functional re2uirement re2uirement" #o.
&
<!ist of performance characteristics includes following . +esponse time per Performance transaction0average, ma8imum1 . hroughput 0transactions per second1 . $apacity 0number of customers or transactions the system can accommodate1" ( 4sability < his section includes all of those re2uirements that affect the usability" ) +eliability <*escribe the reliability related re2uirements" ' Security <*escribe the following . +e2uirements for access to the system . +e2uirements for the protection of information0privacy" Proposed Screen !ayout%user 7nterface its details;
<Paste the re2uirement screen layout%user interface and describe the re2uirement and describe the re2uirement in detail in terms of what is e8pected. How it is e8pected, loo< =feel of Screen%4ser interface validation chec<s for ob>ects places on screen%4ser interface etc."
#ote; +epeat this table to describe various customer