Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
FunctionalRequirementsDocument
[ProjectName]
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
DocumentInformation:DocumentItem Description
CurrentVersion:
Owner:
DateLastUpdated:
LastUpdatedBy:
Author:
DateCreated:
ApprovedBy:
ApprovalDate:
RevisionHistory:VersionNumber
DateUpdated
RevisionAuthor
BriefDescriptionofChanges
DocumentApprovalsHistory:Role Name Signature Date
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
1.0Introduction:1.1Purpose:1.2DocumentConventions:1.3UserProblem/ProjectBackground:1.4Solution/SolutionScope:1.4.1IncludedinScope:1.4.2ExcludedinScope:2.0–References:113.0–Methodology:[SolutionApproach]11_Toc4284360314.0Solutionoveralldescription:4.1SolutionPerspective:4.2SolutionFeature:4.3UserClassesandCharacteristics:4.4Operatingenvironment:4.5DesignandImplementationConstraints:4.6UserDocumentation:[UserManual]5.0SolutionRequirement:5.1FUNCTIONALREQUIREMENT5.1.1FunctionalRequirements-UserRegistration5.1.2FunctionalRequirements-ChangePassword5.1.3FunctionalRequirements-ResetPassword5.1.4FunctionalRequirements–AccesstoStatementofTransaction 5.1.5FunctionalRequirements–FundsTransfer-inter-bank5.1.6FunctionalRequirements–FundsTransferintra-bank5.1.7FunctionalRequirements–RegistrationofBeneficiaryAccount5.1.8FunctionalRequirements–GenerationofFileforCB5.1.9FunctionalRequirements–UploadofresponsefilefromCB5.1.10FunctionalRequirements–Alertservicestocustomers5.2ContextDiagram5.3DataFlowDiagrams-FundsTransferProcess5.4LogicalDataModel5.5DataDictionary5.6–Non-FunctionalRequirements5.6.1-InterfaceRequirements5.6.2HardwareInterfaces5.6.3SoftwareInterfaces:5.6.4CommunicationsInterfaces:5.6.5DataConversionRequirements:5.7Security&SafetyRequirement5.7.1SecurityandPrivacy:5.7.2AuditTrail:5.7.3Reliability:
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
5.7.4Recoverability:5.7.5SystemAvailability:5.8GeneralPerformance5.9DataRetention:5.10ErrorHandling:5.11ValidationRules: 5.12Conventions/Standards: 5.13SoftwareQualityAttributes: 6.0AssumptionandConstraints(BusinessandTechnical):6.1AssumptionsandOtherRelevantFacts6.2RequirementConstraints&Dependencies7.0APPENDIXA-GLOSSARY
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
1.0Introduction:1.1Purpose:This document underlies the functional requirements for implementing Online BankingSolution(OBS)forGlobalBankLtd(GBL).TheoverallOBScoversawiderangeof features,which are proposed to be implemented on a phase-wise basis. This document covers thefunctionalrequirementsforPhase1deliverycomprisinglogin,transaction,andaccountviewrelatedfunctions.
1.2DocumentConventions:
This document covers the most critical and priority items for the implementation of theonlinebankingfacilitybytheGBL.TheBRDdocumentversion1.0isconsideredasthebasefor the preparation. Any changes in the BRD version 1.0 should be replicated in this FRDdocumentaccordingly.
1.3UserProblem/ProjectBackground:
The retail banking industry has undergone tremendous transformationwith the advent ofonline banking services. In 2014, almost 30% of the national banking transactionswithinbankswereexecutedusinganonlinebankingplatform.Theshareisexpectedtogrowattherateof5%everyyear for thenext fiveyears.Further,with themassiveadoptionofplasticmoney,thedigitalpaymentgrowthrateisexpectedtobeat40%in2014.
Thebank’sbusinesshasbeengrowingattherateofonly4%inthepastthreeyearsversustheaveragerateofgrowthofbusinessbanksprovidingmodernfacilities,includingInternetbanking,whichhasbeen10%.Customersprefertomaintainbankaccountswithbankswithmodernfacilities.Duetothispreference,thereisapotentiallossofnewcustomersaswellasshiftingofexistingcustomers.
With increasing real estate prices and cost of staffing, the operating costs of branches areincreasing, creating a constraint in opening of new branches as well as maintaining theexisting ones. In the past three years, the branch operations cost has escalated by 5%annually,creatingahugeimpactonprofits.Insuchascenario,itisimperativeforthebanktoupgradeitsqualityofserviceswiththechangingenvironment.
1.4Solution/SolutionScope:
At present, customers are using banking services through visiting the branches in person.The branches access core-banking solution (CBS) to update and carry out the customers’transactions. All customers’ data ismaintained in the CBS, enabling customers to operatethroughanyof thebranches.TheOnlineBankingSolution(OBS)wouldbe implementedasanadditionalinterfaceforthecustomerinconductingbankingoperations.TheOBSwouldbeconnected to the CBS for extracting customer (master) data and processing requests.ConnectivitywithCBisalreadyestablishedforchequetruncationandelectronictransfers.
ThereareahostoffeaturesthatcanbeprovidedthroughOBS.Thedevelopmentisexpectedtobe completedonaphase-wisebasis spanningacross twophases initially.The followingmodulesareproposedtobeimplementedacrossPhase1andPhase2.
These are the primary and must-have features. Additional features are proposed to beimplementedinsubsequentphases.
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
1.4.1Includedinthescope:
ThefollowingfunctionalitiesareincludedinthescopeforPhase1development:
a) Loginfacilitytoexistingaswellasnewcustomers.b) Facility to set and change the password, set the secret question, and password
policies.c) Onlinetransferoffundstoabeneficiarywithinthebank(intra-bank)d) OnlinetransferoffundstoabeneficiaryoutsidethebankusingRTGS,NEFTandIMPS
facility.e) Facilitytoviewaccountsummary.f) Facilitytoviewanddownloadstatementoftransaction.
1.4.2ExcludedinScope:
ThefollowingfunctionalitieswillbedevelopedinPhase2andhavebeenexcludedfromthescope:
• Requestforchequebook• Requestfordemanddraft• Stoppaymentofcheque• Emailregistration• Nomineeregistration
2.0–References:a MeetingwithMD,CTOandPMO,minutesofthemeetingdatedJuly01,2015.b WorkshopwithOperationsandSystemsteamdatedJuly20,2015.c PolicyNoteonFutureDevelopmentPlanbyBankCoreCommittee.d CB guidelines are circulars with respect to Online Banking, Electronic Payment
services.e BusinessRequirementDocument(Version1.0dated1.11.2015).
3.0–Methodology:[SolutionApproach]As the project involves integration with multiple development teams, a complexenvironment and agile methodology will be used for the overall implementation of theproject.
4.0SolutionOverview:
4.1SolutionPerspective:
At present, customers are using banking services by visiting the branches in person. Thebranches’ access core-banking solution (CBS) will update and carry out the customer’stransactions. All customers’ data ismaintained in the CBS, enabling customers to operatethroughanyof thebranches.TheOnlineBankingSolution(OBS)wouldbe implementedasanadditionalinterfaceforthecustomerinconductingbankingoperations.TheOBSwouldbeconnectedtotheCBSforextractingcustomerdataandprocessingtherequest.ConnectivitywithCBisalreadyestablishedforchequetruncationandelectronictransfers.
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
Aspertheproposedsolution,thecustomerscaninteractwiththebankeitherthroughbankbranch frontofficesor throughtheOnline InternetBanking facility. In theentirestructure,themajorcomponentsanditsbriefinteractionsareshowninpictorialdiagrambelow:
4.2SolutionFeature:
Theoverallsolutionconsistsofbelowmentionedmajorfunctionalgroups
Thefollowingdiagramliststhefunctionalitiesundereachofthesegroups
_________________________________________________________________________________________________________
_________________________________________________________________________________________________________
_________________________________________________________________________________________________________
_________________________________________________________________________________________________________
SolutionOverviewDiagram
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
SolutionModuleorphases(drawatable
SolutionUsers(sample)TypeofUser UserDetails Functions
Customer Customer has account and access tosolution
Login,Transact,AccountView,andRequests
Frontoffice FrontOfficeStaff Viewcustomers’ details.
HelpDesk Help Desk staff for resolving Customers’queries.
View customers’ onlineTransactions details.
Management SeniorStaffofmanagement ReportsAdministratorSystemsadministrator UserManagement, Reports
BackOffice Back office for generating Uploads andresponse feed from CB, printing ofInternetPINs.
UploadanddownloadofCBfiles,IPINprintingfiles,etc.
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
4.4Operatingenvironment:
Operatingenvironmentforcustomer:
_________________________________________________________________________________________________________
_________________________________________________________________________________________________________
_________________________________________________________________________________________________________
_________________________________________________________________________________________________________
Operatingenvironmentforbank:
_________________________________________________________________________________________________________
_________________________________________________________________________________________________________
_________________________________________________________________________________________________________
_________________________________________________________________________________________________________
DesignandImplementationConstraints:
_________________________________________________________________________________________________________
_________________________________________________________________________________________________________
_________________________________________________________________________________________________________
_________________________________________________________________________________________________________
4.6UserDocumentation:[UserManual]
Thefollowinguserdocumentswillbeprovided:• UserguideforcustomersTroubleShootingforcustomersUserguidefortheendusers
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
5.0SolutionRequirement:
5.1FUNCTIONALREQUIREMENT
5.1.1FunctionalRequirements-IRequirementID
Requirement
Description
Dependency
SuccessCriteria
Exceptions
InputData
OutputData
DataFormat
BusinessRule
Assumptions
Constraints
Comments
5.1.2FunctionalRequirements-IIRequirementID
Requirement
Description
Dependency
SuccessCriteria
Exceptions
InputData
OutputData
DataFormat
BusinessRule
Assumptions
Constraints
Comments
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
5.1.3FunctionalRequirements–IIIRequirementID
Requirement
Description
Dependency
SuccessCriteria
Exceptions
InputData
OutputData
DataFormat
BusinessRule
Assumptions
Constraints
Comments
5.1.4FunctionalRequirements–IVRequirementID
Requirement
Description
Dependency
SuccessCriteria
Exceptions
InputData
OutputData
DataFormat
BusinessRule
Assumptions
Constraints
Comments
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
5.2CONTEXTDIAGRAM
5.3DataFlowDiagrams-
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
5.4LOGICALDATAMODEL
5.5DATADICTONARY
TableName
BusinessName
ColumnAttributes
DataType
Size Description
5.6–NON-FUNCTIONALREQUIREMENTS
5.6.1-InterfaceRequirements:TheuserinterfacingtheOnlineBankingSystemmusthavefollowingbasicfeaturesavailableonhis/herdesktop
___________________________________________________________________________________________________________
___________________________________________________________________________________________________________
___________________________________________________________________________________________________________
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
SpecificInterfacerequirements:LoginFirsttimeusersshouldbedirectedtothehomepageofthesolutionwhereinthereshouldbean option to login. On selection of the login, a screen should be displayedwith option tocapture theuser ID andpassword. In the caseof a first-time login, after entering theuserdetails,thesystemshouldprompttheusertosetthenewpasswordandsecretquestionandanswertoresetthepassword.
ForgotIPIN?PasswordReset
Report
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
Upon login, themenuwillbedisplayed foraccountview, transactions,etc.Forreports, theuser will select the report menu. The following screen indicating the option of variousreportsshouldbedisplayedwithvariousoptions.Thecustomershouldbeabletoclicktheoptions/hewantstouse.
ReportsScreen–postexecutionBasedonselectionofthemenu,thescreenshouldbedisplayedtocapturethereportdetailsasbelow:
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
5.6.2HardwareInterfaces:__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
5.6.3SoftwareInterfaces:__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
5.6.4CommunicationsInterfaces:__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
5.6.5DataConversionRequirements:__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
5.7Security&SafetyRequirement
5.7.1SecurityandPrivacy:__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
5.7.2AuditTrail:__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
5.7.3Reliability:__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
5.7.4Recoverability:__________________________________________________________________________________________________________
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
5.7.5SystemAvailability:__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
5.8GeneralPerformance
5.8.1Capacity:Systemshouldabletohandlethefollowingvolumesonthedailybasis:• Maximumuserloginatsametime–2000.• MinimumrequestforIPINprinting-50,000perday.• Minimum0.5milliontransactionsperday.• Responsetimeshouldbenotmorethan2seconds100%ofthetime.
5.9DataRetention:
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
__________________________________________________________________________________________________________
5.10ErrorHandling:
Appropriateerrormessageshouldbedisplayed tousersonexceptionsanderrors.End-of-dayexceptionreportshouldbegeneratedforallexceptions.
Deployedapplicationsshouldgeneratenecessarylogsforeachactivityandfunctioncarriedoutinthesystem.Logsareapplicableforandnotlimitedtothirdpartysoftware,butalsototheapplicationdeveloped.
5.11ValidationRules:Thefollowingvalidationsshouldbeimplemented:
• BatchTotalsCheck• DigitsConsistencyChecks• ControlTotals• DataTypeChecks
5.12Conventions/Standards:
ProgrammingshouldfollowIEEEstandardforsoftware.
5.13SoftwareQualityAttributes:• Applicationsshouldhaveathroughputof1000transactionspersecond.
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
• 95%ofall requestsmustbeprocessed in less than4 seconds, andno requestsmusttakemorethan15seconds.
• Thesystemshouldbescalabletoaccommodateafutureincreaseinpeakloads.• Applicationshouldallowaminimumof2000concurrentusers.• AssumptionandConstraints(BusinessandTechnical):
6.1AssumptionsandOtherRelevantFacts
ID Assumption
6.2RequirementConstraints&Dependencies
DesignConstraintsID Constraint
7.0APPENDIXA–GLOSSARYTerminology Description
Functional Requirement Document (FRD) Template
__________________________________________
This functional requirement document is designed by Ms. Sandhya Jane for academic purposes only. For commercial use, please obtain commercial standard document by contacting her at www.sandhyajane.com
SolutionArchitecture(designdiagram):