Functional Specifications Document

7/23/2019 Functional Specifications Document

1/11

RBL SBL

Functional Specifcations

Document

April 2015


2/11

Functional Specifcations Document

Functional Name

ro!ect Name" RBL SBL

ro!ect Re#erence $" Functional Re#. $"

So#t %op& Name"

Version No." Date" 2'(Apr(15

Version %ontrol

Version

)so#tcop&*

u+lis,e-

Date

Aut,or)s* Sections

%,ane-

Description o# %,anes

1.0 Aman Garg New Document

Information contained herein is for internal use and may be used only for business purposes authorized by Max Life Insurance Co. Ltd.

/(FSD(01 Ver. .0 Business Private (when filled), Business Confidential (when not filled) ae 2 o#

11


3/11


Approals

Approving Authority Name Signature Date

Author Aman Garg

Sr. Business SystemsAnalyst

Business Unit Head

User

Information Security Head


/(FSD(01 Ver. .0 Business Private (when filled), Business Confidential (when not filled) ae o#

11


4/11


/a+le o# %ontents

Version Control________________________________________________________________________________2

Approvals____________________________________________________________________________________3

Table of Contents______________________________________________________________________________3

1. Background_______________________________________________________________________________3

1.1. Business Requirement and Objectives_____________________________________________________3

2. Syste!"odule #vervie$____________________________________________________________________3

2.1. Features In-scope______________________________________________________________________3

2.2. Out of Scope__________________________________________________________________________3

2.3. ssumptions__________________________________________________________________________3

2.!. "ard#are and Soft#are $%atform________________________________________________________3

2.&. $roposed 'or(f%o#____________________________________________________________________3

3. S%&C'('C ()*CT'#* +&SC,'%T'#*S______________________________________________________3

3.1. )Function *ame+______________________________________________________________________3

3.1.1. Description________________________________________________________________________33.1.2. Inputs____________________________________________________________________________3

3.1.3. Processing________________________________________________________________________3

3.1.4. Outputs___________________________________________________________________________3

3.1.5. Technical Change___________________________________________________________________33.1.6. Cross Functional Impact_____________________________________________________________3

3.1.. Inter!ace Consi"erations_____________________________________________________________3

-. "igration ,euireents_____________________________________________________________________3

/. %erforance ,euireents__________________________________________________________________3

0. S'C Considerations_________________________________________________________________________3

. Syste ,euireents_______________________________________________________________________3

. Security ,euireents______________________________________________________________________3

#.1. Pass$or" Polic% &e'uirement__________________________________________________________3#.2. (ni'ue user ID_____________________________________________________________________3

#.3. (ser )anagement *u"it Trails_________________________________________________________3

#.4. (ser Transactional *u"it Trails_________________________________________________________3

#.5. &ole +ase" *uthori,ation_____________________________________________________________3#.6. Principal o! -east priileges___________________________________________________________3

#.. /ession )anagement_________________________________________________________________3#.#. Input0Output ali"ations______________________________________________________________3

#.. +u!!er oer!lo$ ali"ations___________________________________________________________3#.1. Disaling Director% ro$sing__________________________________________________________3

#.11. /eparate usiness logic "ataase an" $e la%ers ph%sicall% an" logicall%_____________________3

#.12. rror han"ling mechanism to preent s%stem !rom thro$ing "e!ault error messages_______________3

#.13. 7D* contract an" *)C signe" $ith the usiness partner___________________________________3#.14. +aseline Installation an" &ecoer% "ocumentation________________________________________3

#.15. /eparate Testing Deelopment an" Pro"uction nironment________________________________3


/(FSD(01 Ver. .0 Business Private (when filled), Business Confidential (when not filled) ae ' o#

11


5/11


#.16. Operating /%stem 8ar"ening__________________________________________________________3

. Testing Considerations______________________________________________________________________3

,.1. Sstem estin/ Scope___________________________________________________________________3

,.2. estin/ Scenarios______________________________________________________________________314. Traceability atri5_______________________________________________________________________3

11. ,eference +ocuents_____________________________________________________________________3

12. #pen 'tes_____________________________________________________________________________3

13. 6lossary________________________________________________________________________________3

1-. Appendi5_______________________________________________________________________________3



11


6/11


1. Bac3roun-

1.1. Business Re4uirement an- +!ecties

Descries rie!y why the system"module is eing de#elo$ed% and lists the most im$ortantfeatures and ca$ailities. &his should e directly im$orted from the usiness re'uirementdocument and e($anded u$on if necessary. )lease re#ise the o*ecti#e if the originalre'uirement was unclear or has een altered y the a$$roach ta+en.



11


7/11


2. S&stem7o-ule erie8

2.1. Features 9n(scope

)ro#ide list of the functions that the system"module will e re'uired to $erform. ,here afeature com$rises se#eral functional ca$ailities% a tale may e de#elo$ed to illustratethese relationshi$s.

2.2. ut o# Scope

&his section descries the e(clusions from the sco$e of this functionality

2.. Assumptions

-ists any assum$tions that were made in s$ecifying the functional re'uirements

2.'. :ar-8are an- So#t8are lat#orm

-ist the hardware and software $latform $ro$osed for the system./

2.5. ropose- ;or3o8

Show a helico$ter #iew of the $ro$osed system"module/


/(FSD(01 Ver. .0 Business Private (when filled), Business Confidential (when not filled) ae = o#

11


8/11


. S%9F9% F?N%/9N DS%R9/9NS

a+e a laundry list of all the functions with rief descri$tion not more than a sentence ortwo. &his will hel$ ensure that all the functions ha#e een ca$tured in the document and

considered for the ne(t stage System Design. Some e(am$les of functions are2calculations% sorting or se'uencing% other o$erations relating in$uts to out$uts% #aliditychec+s on in$uts% error handling and reco#ery/

SNo.

Function Name Brie# Description

3.1.

3.4.

3.3.

3.5.

3.6.

3.7.

3.8.

&he following section should e re$eated for each function of the system"module. &hat is%create a susection for each function name

.1.

.1.1. Description

Descries the function and its role in the system"module. &he detail information for each ofthe changes will e included in the A$$endi( in su documents% ut each com$onent shouldalso e descried here in general with a descri$tion of how they 9t together to meet theusiness re'uirements. Su:sections can also e created to se$arate changes into clientchanges and ser#er changes if that ma+es it more understandale. ;or ease of reading"!ow%include any screen designs in the A$$endi(.

.1.2. 9nputs

Descrie the in$uts to the function.


9/11



10/11


'. iration Re4uirements

Descries migration re'uirements data 9(es/ re'uired for the function.

5. er#ormance Re4uirements

Discuss items such as res$onse times% through$ut re'uirements% data #olume re'uirements%ma(imum data 9le siEe or $rolem com$le(ity% ma(imum numer of concurrent uses% and$ea+ load re'uirements for we:ased a$$lications/. Include e($ected res$onse times for

entering information% 'uerying data 9les and dataases% $erforming calculations of #ariouscom$le(ities% and im$orting"e($orting data.

6. S9% %onsi-erations

Descries SIC considerations re'uired for the function.

=. S&stem Re4uirements

&his section should contain details aout system access and ca$acity% including2

desired hours of o$eration : Descrie re'uirements items such as days or wee+s of

continuous o$eration% security re'uirements : Descrie any $assword:$rotected access le#els such as data

center o$erator% de#elo$er% con9guration manager% dataase administrator and whichfunctionality will e accessile to each access le#el and to whom.

ac+u$ fre'uency

disaster reco#ery

@. /estin %onsi-erations

-ist the functional acce$tance criteria or attach the functional test $lan

.1. S&stem /estin Scope

De9ne the system testing sco$e for this functionality



11


11/11


.2. /estin Scenarios

Descrie uni'ue testing constraints or situations% e.g.% the functionality is only tested as $artof the $eriod atch cycle testing $rocess or ensure that the $remium calculations are

tested.

Documents

Functional Specifications Document