Banking Management System SRS

A Banking Management system is an application that gives functionality like sending money, bill payment, taking a loan, check balance, see all transaction history and many more.

1. BankingManagementSystem
SoftwareRequirementSpecification
GuidedBy: SubmittedBy:
Dr.G.L.Prajapati LOKESHNARGESH(19I8029)
MADHURJATIYA(19I8030)
RANIAHIRE(20C8084)
DepartmentofComputerEngineering/InformationTechnology
InstituteofEngineering&Technology
DeviAhilyaVishwavidyalaya,Indore(M.P.)
(www.iet.dauniv.ac.in)
March2023

2. SoftwareRequirementsSpecificationfor<BankingManagementSystem> Pageii
TableofContents
TableofContents..........................................................................................................................ii
1.Introduction.............................................................................................................................1
1.1Purpose.............................................................................................................................................1
1.2DocumentConventions....................................................................................................................1
1.3IntendedAudienceandReadingSuggestions..................................................................................1
1.4ProductScope...................................................................................................................................1
1.5References........................................................................................................................................2
2.OverallDescription.................................................................................................................3
2.1ProductPerspective..........................................................................................................................3
2.2ProductFunctions.............................................................................................................................4
2.3UserClassesandCharacteristics......................................................................................................5
2.4OperatingEnvironment....................................................................................................................6
2.5DesignandImplementationConstraints..........................................................................................6
2.6UserDocumentation.........................................................................................................................7
2.7AssumptionsandDependencies.......................................................................................................8
3.ExternalInterfaceRequirements.........................................................................................10
3.1UserInterfaces................................................................................................................................10
3.2HardwareInterfaces........................................................................................................................10
3.3SoftwareInterfaces.........................................................................................................................10
3.4CommunicationsInterfaces............................................................................................................11
4.SystemFeatures.....................................................................................................................12
4.1SystemFeature1............................................................................................................................12
4.2SystemFeature2(andsoon).........................................................................................................12
5.OtherNonfunctionalRequirements....................................................................................13
5.1PerformanceRequirements............................................................................................................13
5.2SafetyRequirements.......................................................................................................................13
5.3SecurityRequirements....................................................................................................................14
5.4SoftwareQualityAttributes............................................................................................................14
5.5BusinessRules................................................................................................................................15
6.OtherRequirements..............................................................................................................16
AppendixA:Glossary...................................................................Error!Bookmarknotdefined.
AppendixB:AnalysisModels....................................................................................................16
AppendixC:ToBeDeterminedList............................................Error!Bookmarknotdefined.

3. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
1.Introduction
1.1Purpose
The“BankingManagementSystem”projectisamodelInternetBankingSite.Thissiteenablesthe
customerstoperformthebasicbankingtransactionsbysittingattheirofficeorathomesthrough
PCorlaptop.Thesystemprovidestheaccesstothecustomertocreateanaccount,deposit/withdraw
thecashfromhisaccount,alsotoviewreportsofallaccountspresent.Thecustomerscanaccessthe
bankswebsiteforviewingtheirAccountdetailsandperformthetransactionsonaccountaspertheir
requirements.WithInternetBanking,thebrickandmortarstructureofthetraditionalbankinggets
convertedintoaclickandportalmodel,therebygivingaconceptofvirtualbankingarealshape.
Thus,today'sbankingisnolongerconfinedtobranches.E-bankingfacilitatesbankingtransactions
bycustomersroundtheclockglobally.
1.2DocumentConventions
ThefontweareworkingwithTimeNewRomansize(20)forHeadingsandsize(16)forusual
details.ThetextformatwearefollowingisTimeNewRomansize(14)forheadinganddescription.
Thisapplicationdoesnotrequiresanyspecialtoolforperforminganyoperation,thisapplication
canbeeasilyruninanysmartphone.
1.3IntendedAudienceandReadingSuggestions
Thisdocumentswillcaptureallstackholderspreferences,differentconflictandtheirresolution.
Also,itcouldbeusedbypotentialdevelopers,designengineer,tester,projectmanagerse.t.c.This
projecthasbeenimplementedundertheguidanceofcollegeprofessor.Thisprojectisusefulforthe
parkingmanagementteamandalsoforstudentsandfaculties.
1.4ProductScope
TheBankingManagementSystemisasoftwareapplicationdesignedtofacilitatethemanagement
ofbankingtransactionsandcustomerinformation.Theprimaryobjectiveofthissystemisto
simplifybankingprocesses,reduceerrors,andprovideasecureplatformforfinancialtransactions.
TheproductscopefortheBankingManagementSystemincludesthefollowingfunctionalities:
AccountManagement:Thesystemallowsthecreationandmanagementofcustomeraccounts.
Customerscanopennewaccounts,viewaccountdetails,andperformtransactionssuchasdeposits,
withdrawals,andfundtransfers.
CustomerManagement:Thesystemmaintainscustomerinformation,includingpersonaldetails,
accountdetails,andtransactionhistory.Customerscanupdatetheirpersonalinformationandview
theirtransactionhistory.

4. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
TransactionManagement:Thesystemprovidesasecureplatformforprocessingtransactionssuch
asdeposits,withdrawals,andfundtransfers.Thesystemmaintainstransactionrecordsand
generatesreportsforaccountholders.
UserManagement:Thesystemsupportsthecreationandmanagementofuseraccounts,including
administratorsandtellers.Thesystemmaintainsuserinformation,accessrights,andactivitylogs.
Reporting:Thesystemgeneratesreportsoncustomeraccounts,transactionhistory,anduser
activity.ReportscanbeexportedinvariousformatssuchasPDF,Excel,orCSV.
Security:Thesystemprovidesasecureplatformforfinancialtransactionsandprotectssensitive
datasuchascustomerinformation,accountdetails,andtransactionrecords.Thesystemincludes
authenticationandauthorizationmechanismstoensurethatonlyauthorizeduserscanaccessthe
system.
TheBankingManagementSystemisdesignedtoprovideacomprehensivesolutionformanaging
bankingtransactionsandcustomerinformation.Thesystemaimstoimprovetheefficiencyof
bankingprocesses,reduceerrors,andenhancecustomersatisfaction.
1.5References
1.CreatingaGUIWithSwing
https://docs.oracle.com/javase/tutorial/uiswing/index.html
2.HowtoCreateBankingSystemusingJSwings&MYSQLDBMSonNetbeansIDE
https://www.javatpoint.com/banking-application-in-java
3.BankApplicationinJava:
https://www.youtube.com/watch?v=z1O0pnd07GA
4.MySQLvideotutorials
https://www.youtube.com/watch?v=DxoRUmW44JE

5. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
2.OverallDescription
Theprimaryaimofthis“BankingManagementSystem”istoprovideanimproveddesign
methodology,whichenvisagesthefutureexpansion,andmodification,whichisnecessaryforacore
sectorlikebanking.Thisnecessitatesthedesigntobeexpandableandmodifiableandsoamodular
approachisusedindevelopingtheapplicationsoftware.
AnybodywhoisanAccountholderinthisbankcanbecomeamemberofBankAccount
ManagementSystem.HehastofillaformwithhispersonaldetailsandAccountNumber.
Bankistheplacewherecustomersfeelthesenseofsafetyfortheirproperty.Inthebank,customers
depositandwithdrawtheirmoney.Transactionofmoneyalsoisapartwherecustomertakesshelter
ofthebank.Nowtokeepthebeliefandtrustofcustomers,thereisthepositiveneedfor
managementofthebank,whichcanhandleallthiswithcomfortandease.
Smoothandefficientmanagementaffectsthesatisfactionofthecustomersandstaffmembers,
indirectly.Andofcourse,itencouragesmanagementcommitteeintakingsomeneededdecisionfor
futureenhancementofthebank.
Nowaday’s,managingabankistediousjobuptocertainlimit.Sosoftwarethatreducesthework
isessential.Also,today’sworldisagenuinecomputerworldandisgettingfasterandfasterday-by-
day.Thus,consideringabovenecessities,thesoftwareforbankmanagementhasbecomenecessary
whichwouldbeusefulinmanagingthebankmoreefficiently.
AlltransactionsarecarriedoutonlinebytransferringfromaccountsinthesameBankor
internationalbank.Thesoftwareismeanttoovercomethedrawbacksofthemanualsystem.
2.1ProductPerspective
Functionalrequirements:Identifythecorefunctionsthatthebankingmanagementsystemneedsto
perform,suchasmanagingcustomeraccounts,facilitatingtransactions,generatingreports,andso
on.
Userrolesandpermissions:Determinethedifferenttypesofuserswhowillinteractwiththe
system,suchascustomers,bankemployees,andadministrators,anddefinethepermissionsand
privilegesassociatedwitheachrole.
Securityandprivacy:Ensurethatthesystemisdesignedtohandlesensitiveinformationsecurely,
includinguserdata,transactiondetails,andfinancialinformation.
Scalabilityandperformance:Considerhowthesystemwillhandleagrowingnumberofusersand
transactions,andensurethatitcandeliverfastandreliableperformanceunderdifferentconditions.
Integrationwithexternalsystems:Evaluateanyexternalsystemsthatthebankingmanagement
systemneedstointegratewith,suchaspaymentgateways,regulatoryagencies,andotherfinancial
institutions.
Usabilityandaccessibility:Designthesystemtobeuser-friendlyandaccessibleforusersof
differentskilllevelsandabilities,withclearnavigation,intuitiveinterfaces,andaccessibledesign.

6. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
Compliancewithindustrystandards:Ensurethatthesystemmeetsallrelevantregulatoryand
industrystandardsforfinancialsystems,suchasPCIDSS,GDPR,andotherrelevantregulations.
Flexibilityandcustomization:Considertheneedforcustomizationandflexibilityinthesystem,
suchasallowinguserstocustomizetheiraccountsorpersonalpreferences,orgivingbank
employeestheabilitytotailorthesystemtotheirspecificneeds.
Maintenanceandsupport:Definetheongoingmaintenanceandsupportrequirementsforthesystem,
includinghowupdatesandpatcheswillbehandled,howusersupportwillbeprovided,andhowto
troubleshootissues.
Reportingandanalytics:Determinethereportingandanalyticsrequirementsforthesystem,
includinghowdatawillbestoredandanalyzed,whatmetricswillbetracked,andhowreportswill
begeneratedanddistributed.
2.2ProductFunctions
Accountcreation:Customersshouldbeabletoopennewaccounts,suchaschecking,savingsor
creditcardaccounts,onlineorinperson.Theyshouldbeabletoprovidepersonalandfinancial
informationrequiredtoopentheaccount,suchasname,address,dateofbirth,socialsecurity
number,andinitialdeposit.
Accountmanagement:Customersshouldbeabletoviewtheiraccountbalance,transactionhistory,
andotherrelevantdetails.Theyshouldbeabletotransferfundsbetweenaccounts,paybills,andset
upautomaticpaymentsordeposits.
Accountadministration:Bankadministratorsshouldbeabletoviewallaccounts,searchfor
specificaccountsbycustomernameoraccountnumber,andperformadministrativetaskssuchas
freezingorclosingaccounts,modifyingaccountsettings,orupdatingaccountinformation.
Securityandprivacy:Thebankingmanagementsystemshouldcomplywithindustrystandards
andregulationsfordatasecurityandprivacy.Customersshouldberequiredtoauthenticate
themselveswithausernameandpassword,andsensitivedatasuchasaccountnumbersandpersonal
informationshouldbeencryptedandprotected.
Notificationsandalerts:Thesystemshouldbeabletogeneratenotificationsandalertsto
customersandadministratorsforvariousevents,suchasaccountbalancechanges,suspicious
activities,oraccountupdates.
Reportsandanalytics:Thesystemshouldbeabletogeneratereportsandanalyticsonvarious
aspectsofaccountmanagement,suchasaccountbalances,transactionvolumes,orcustomer
demographics.

7. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
Integrationwithothersystems:Thebankingmanagementsystemshouldbeabletointegratewith
othersystemssuchaspaymentgateways,corebankingsystems,orcustomerrelationship
management(CRM)systemstostreamlineprocessesandimprovecustomerexperience.
2.3UserClassesandCharacteristics
UserModule:
Asimpleusercanaccesstheiraccountandcandeposit/withdrawmoneyfromtheiraccount.
Usercanalsotransfermoneyfromtheiraccounttoanyotherbankaccount.Usercanseetheir
transactionreportandbalanceenquirytoo.
1-Userlogin,usePINsystem
2-Creating/opennewaccountregistration
3-Fundstransfer(local/international/domestic)
4-Viewstatementstransaction
5-Useraccountdetails
6-ChangePasswordandPin
AdminModule
Admincanaccessthisprojectthereisanauthorizationprocess.IfyouloginasanAdminthenyou
willberedirectedtotheAdminHomePageandifyouareasimpleuseryouwillberedirectedto
yourAccountHomePage.Thisperformsthefollowingfunctions:Create
IndividualAccounts,manageexistingaccounts,Viewalltransactions,Balanceenquiry,
Delete/closeaccountetc.
1-Adminlogin
2-Add/delete/updateaccount
3-Withdrawal/deposit/statementstransaction
4-AccountInformation
5-Userdetailslist
6-Active/Inactiveaccount
7-Viewtransactionhistories

8. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
2.4OperatingEnvironment
2.4.1ServerSide:
Processor:Intel®Xeon®processor3500series
HDD:Minimum500GBDiskSpace
RAM:Minimum16GB
OS:Windows8.1,Linux
Database:SQLServer2014(SQL14)
2.4.2Clientside(minimumrequirements):
Processor:IntelDualCore
HDD:Minimum80GBDiskSpace
RAM:Minimum1GB
OS:Windows8,Linux.
2.5DesignandImplementationConstraints
SecurityandCompliance:Thebankingindustryishighlyregulated,andthesystemmustcomply
withvarioussecuritystandardsandregulations,suchasPCIDSS,HIPAA,andGDPR.This
requiresimplementingsecurityfeaturessuchasencryption,accesscontrols,andauditing.
Scalability:Thesystemshouldbedesignedtohandleahighvolumeoftransactionsandcustomers,
andmustbescalabletosupportfuturegrowth.
Availability:Thesystemmustbehighlyavailableandreliabletoensurethatcustomerscanaccess
theiraccountsandperformtransactionsatalltimes.Thisrequiresimplementingredundancy,fail
overmechanisms,anddisasterrecoveryprocedures.
Integration:Thesystemmayneedtointegratewithotherbankingsystems,suchascorebanking
systems,paymentgateways,orthird-partyservices.Thisrequiresimplementinginterfaces,APIs,
anddatamapping.
Usability:Thesystemmustbeuser-friendlyandintuitivetouse,toensurethatcustomerscan
performtransactionseasilyandefficiently.Thisrequiresimplementingauser-centereddesign
approach,usabilitytesting,andusertraining.
Performance:Thesystemmustbedesignedtoperformwellandrespondquicklytouserrequests,
toensurethatcustomerscancompletetransactionswithoutdelay.Thisrequiresoptimizingdatabase
queries,implementingcaching,andloadtesting.

9. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
Technologyconstraints:Thesystemmustbedevelopedusingappropriatetechnologies,suchas
programminglanguages,frameworks,andlibraries.Itshouldalsobecompatiblewithvarious
operatingsystemsandbrowsers.
Cost:Thesystemdevelopmentandmaintenancecostsmustbeconsidered,includinghardware,
software,licensing,andpersonnelcosts.Thisrequiresperformingcost-benefitanalysis,budgeting,
andresourceplanning.
2.6UserDocumentation
TheBankingManagementSystemisdesignedtohelpyoumanageyouraccountsandperform
bankingtransactionsonline.Thisuserguidewillprovideyouwithanoverviewofthesystem's
featuresandhowtousethem.
GettingStarted:
ToaccesstheBankingManagementSystem,pleasevisitourwebsiteandloginusingyour
usernameandpassword.Ifyoudonothaveanaccountyet,pleasecontactyourbanktocreateone.
AccountDashboard:
Onceyoulogin,youwillseeyouraccountdashboard.Thispagewillshowyouanoverviewof
youraccount,includingyourbalanceandrecenttransactions.Fromthispage,youcanaccessthe
followingfeatures:
ViewAccounts:Thispagewillallowyoutoseeallofyouraccounts,includingchecking,savings,
andcreditcardaccounts.Youcanviewyourbalancesandtransactionhistoryforeachaccount.
TransferFunds:Thispagewillallowyoutotransferfundsbetweenyouraccountsortoanother
person'saccount.Youcanselecttheaccountsyouwanttotransferfromandto,specifytheamount,
andaddamemoifnecessary.
PayBills:Thispagewillallowyoutopaybillsonline.Youcanselectthebilleryouwanttopay,
specifytheamount,andschedulethepaymentdate.
ManageAccountSettings:Thispagewillallowyoutomanageyouraccountsettings,suchas
changingyourpasswordorupdatingyourpersonalinformation.
ContactCustomerService:Thispagewillallowyoutocontactcustomerserviceifyouhaveany
questionsorissues.
SecurityandPrivacy:
TheBankingManagementSystemtakesyoursecurityandprivacyseriously.Weuseindustry-
standardencryptiontoprotectyourpersonalandfinancialinformation,andwerequireyoutousea

10. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
securepasswordwhenloggingin.Pleaseensurethatyoukeepyourlogininformationsafeanddo
notshareitwithanyone.
Ifyounoticeanysuspiciousactivityorunauthorizedtransactionsonyouraccount,pleasecontact
customerserviceimmediately.
Conclusion:
WehopethisuserguidehashelpedyouunderstandthefeaturesandbenefitsoftheBanking
ManagementSystem.Ifyouhaveanyquestionsorfeedback,pleasecontactcustomerservice.
Thankyouforchoosingourbankandusingoursystemtomanageyourfinances.
2.7AssumptionsandDependencies
Assumptions:
1.Customerswillhaveaccesstotheinternetandwilluseweb-basedinterfacestointeractwith
thesystem.
2.Customerswillhaveaccesstomobiledevicesandwillusemobileapplicationstointeract
withthesystem.
3.Customerswillhavevarioustypesofaccounts,suchaschecking,savings,andcreditcard
accounts.
4.Customerswillbeabletoperformvarioustypesoftransactions,suchasdepositingand
withdrawingfunds,transferringfundsbetweenaccounts,andpayingbills.
5.Thesystemwillbedevelopedusinganobject-orientedprogramminglanguage,suchasJava
andwilluseadatabasemanagementsystem(DBMS)suchasMySQLorOracle.
6.Thesystemwillhavealayeredarchitecture,withseparatelayersforpresentation,
applicationlogic,anddatastorage.
7.Thesystemwillintegratewithotherbankingsystems,suchascorebankingsystems,
paymentgateways,andthird-partyservices,usingstandardizedinterfacesandprotocols.
Dependencies:
1.Hardwareandinfrastructure:Thesystemwilldependonhardwareinfrastructure,suchas
servers,storage,andnetworkequipment.Thehardwaremustbecompatiblewiththe
softwareandmeetthesystemrequirements.
2.Softwaredependencies:Thesystemmaydependonothersoftwarepackages,libraries,or
frameworks.Forexample,thesystemmayuseanopen-sourcedatabasemanagementsystem
orathird-partypaymentgatewayservice.
3.Datasources:Thesystemwilldependonvariousdatasources,suchascustomer
information,transactiondata,andregulatorydata.Thedatamustbeaccurate,consistent,and
up-to-date.
4.Regulatorycompliance:Thesystemmustcomplywithvariousregulatoryrequirements,
suchasthoserelatedtodataprivacy,security,andfinancialreporting.Thesystemmayalso
dependonregulatorybodiesorthird-partyauditorstoverifycompliance.

11. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
5.Usertrainingandsupport:Thesystemwilldependonusers'abilitytousethesystem
correctlyandefficiently.Usertrainingandsupportmayberequiredtoensurethatuserscan
performtaskseffectivelyandthatusererrorsareminimized.
6.Third-partyintegration:Thesystemmaydependonintegratingwiththird-partyservices,
suchaspaymentprocessors,creditbureaus,orfrauddetectionservices.Theintegrationmay
requireAPIsordatamapping.
7.Projectmanagementandteamdependencies:Thesuccessfuldeliveryofthesystemmay
dependoneffectiveprojectmanagement,includingtaskplanning,scheduling,andresource
allocation.Theprojectmayalsodependonteammemberswithspecificskillsorexpertise,
suchasdatabaseadministratorsorsecurityspecialists.

12. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
3.ExternalInterfaceRequirements
3.1UserInterfaces
Thesystemmustprovideuserinterfacesforcustomerstomanagetheiraccounts,andfor
administratorstomanagethesystem.Theuserinterfacesshouldbeintuitive,user-friendly,and
accessiblefrommultipledevices,includingdesktops,laptops,tablets,andmobiledevices.The
systemmusthaveauserinterfacethatiseasytouseandintuitive.Theuserinterfaceshouldallow
customerstomanagetheiraccounts,viewtransactionhistories,maketransfers,andperformother
bankingfunctions.Itshouldalsoallowbankadministratorstomanageaccounts,viewreports,and
performotheradministrativetasks.
3.2HardwareInterfaces
Laptopwith8GBRAMand320GBStorage:
LaptoporaPCisrequiredwithminimum4GBofRAMand320GBofstoragewithOperating
Systemwindows8orhigher,AndRAM4GBtousethesoftwareefficiently.
3.3SoftwareInterfaces
TheBankingManagementSystemisasoftwareapplicationthatinterfaceswithvariouscomponents
toprovidebankingservicestoitsusers.ThesoftwareinterfacesfortheBankingManagement
Systemareasfollows:
UserInterface(UI):Theuserinterfaceprovidesaninteractiveinterfaceforuserstoperform
bankingtransactions.TheUIisdevelopedusingJavaSwing,whichprovidesarichsetofGUI
componentssuchasbuttons,textboxes,andtablesforuserinteraction.
DatabaseInterface:Thesysteminterfaceswithadatabasemanagementsystemtostoreand
retrievedata.ThesystemusesJavaDatabaseConnectivity(JDBC)APItointeractwiththedatabase.
NetworkInterface:Thesysteminterfaceswiththenetworktoprovideaccesstobankingservices
fromremotelocations.ThesystemusesJavaNetworkProgrammingAPItoenablenetwork
communication.
SecurityInterface:Thesysteminterfaceswithvarioussecuritycomponentstoensurethesecurity
ofbankingtransactions.ThesystemusesJavaCryptographyArchitecture(MD5)APItoenable
encryptionanddecryptionofsensitivedata.
OperatingSystemInterface:Thesysteminterfaceswiththeunderlyingoperatingsystemto
performvarioustaskssuchasfileinput/outputandsystemconfiguration.ThesystemusesJava
NativeInterface(JNI)APItointerfacewiththeoperatingsystem.
ThesoftwareinterfacesoftheBankingManagementSystemprovideaseamlessintegrationof
variouscomponentstoprovideacompletebankingsolutiontoitsusers.TheuseofstandardAPIs
suchasJDBCenableseasyintegrationwithvarioussoftwareandhardwarecomponents.

13. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
3.4CommunicationsInterfaces
1.Webinterface:Awebinterfaceallowscustomerstoaccessthesystemthroughaweb
browserfromanydevicewithaninternetconnection.Theinterfaceshouldbeuser-friendly,
intuitive,andresponsive.
2.Mobileinterface:Amobileinterfaceallowscustomerstoaccessthesystemthrougha
mobileappontheirsmartphonesortablets.Theinterfaceshouldbeoptimizedforsmaller
screensandtouchinput.
3.Messaginginterface:Amessaginginterfaceallowsthesystemtosendnotificationsor
alertstocustomersoradministratorsthroughvariouschannels,suchasemail,SMS,orpush
notifications.

14. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
4.SystemFeatures
4.1SystemFeature1
TheBankingManagementSystemisasoftwareapplicationdesignedtoprovideefficientand
reliablebankingservicestoitsusers.ThesystemfeaturesoftheBankingManagementSystemare
asfollows:
AccountManagement:Thesystemprovidestheabilitytoopen,close,andmanagebankaccounts.
Customerscanviewtheiraccountbalance,transactionhistory,andperformtransactionssuchas
deposits,withdrawals,andfundtransfers.
CustomerManagement:Thesystemmaintainscustomerinformationsuchaspersonaldetails,
accountdetails,andtransactionhistory.Customerscanupdatetheirpersonalinformationandview
theirtransactionhistory.
TransactionManagement:Thesystemprovidesasecureplatformforprocessingtransactionssuch
asdeposits,withdrawals,andfundtransfers.Thesystemmaintainstransactionrecordsand
generatesreportsforaccountholders.
UserManagement:Thesystemsupportsthecreationandmanagementofuseraccounts,including
administratorsandtellers.Thesystemmaintainsuserinformation,accessrights,andactivitylogs.
Reporting:Thesystemgeneratesreportsoncustomeraccounts,transactionhistory,anduser
activity.ReportscanbeexportedinvariousformatssuchasPDF,Excel,orCSV.
4.2SystemFeature2
Security:Thesystemprovidesahighlevelofsecuritytopreventunauthorizedaccesstouserdata
andtransactions.Thesystemusesencryption,authentication,andauthorizationmechanismsto
ensuredatasecurity.
BackupandRecovery:Thesystemprovidesbackupandrecoverymechanismstopreventdataloss
duringsystemfailuresordisasters.
AuditTrail:Thesystemmaintainsanaudittrailofalltransactionsanduseractivities.Theaudit
trailcanbeusedforregulatorycomplianceandforensicanalysis.
NotificationSystem:Thesystemprovidesanotificationsystemtoalertusersofimportantevents
suchasaccountbalanceupdates,transactionconfirmations,andsystemmaintenancewindows.
HelpandSupport:Thesystemprovidesahelpandsupportsystemtoassistuserswithcommon
issuesandquestions.Thehelpandsupportsystemcanincludeusermanuals,FAQs,andahelpdesk.
ThesystemfeaturesoftheBankingManagementSystemprovideacomprehensivesolutionfor
managingbankingtransactionsandcustomerinformation.Thefeaturesaredesignedtoimprovethe
efficiencyofbankingprocesses,reduceerrors,andenhancecustomersatisfaction.

15. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
5.OtherNonfunctionalRequirements
5.1PerformanceRequirements
TheBankingManagementSystemisasoftwareapplicationdesignedtoprovideefficientand
reliablebankingservicestoitsusers.TheperformancerequirementsfortheBankingManagement
Systemareasfollows:
ResponseTime:Thesystemshouldrespondtouserrequestswithinareasonabletimeframeto
ensureasmoothuserexperience.Theresponsetimeshouldbelessthan2secondsformost
transactions.
Throughput:Thesystemshouldbeabletohandlealargenumberofsimultaneoustransactions
withoutperformancedegradation.Thesystemshouldbeabletohandleatleast500concurrentusers.
Availability:Thesystemshouldbeavailableforuseatalltimes,exceptduringscheduled
maintenancewindows.Thesystemshouldhaveanavailabilityofatleast99.9%.
Reliability:Thesystemshouldbereliableandnotloseanydataduringnormaloperation.The
systemshouldbeabletorecoverfromhardwareandsoftwarefailureswithoutdataloss.
Scalability:Thesystemshouldbescalabletoaccommodateanincreasingnumberofusersand
transactionswithoutcompromisingperformance.Thesystemshouldbeabletoscaleupordownas
perdemand.
Security:Thesystemshouldprovideahighlevelofsecuritytopreventunauthorizedaccesstouser
dataandtransactions.Thesystemshoulduseencryption,authentication,andauthorization
mechanismstoensuredatasecurity.
ErrorHandling:Thesystemshouldhaverobusterrorhandlingmechanismstohandleexceptions
anderrorsgracefully.Thesystemshouldlogerrorsandprovideappropriatefeedbacktousers.
TheperformancerequirementsoftheBankingManagementSystemensurethatthesystemprovides
asmoothandreliablebankingexperiencetoitsusers.Theuseofefficientalgorithms,database
optimization,andcachingmechanismscanhelpachievethedesiredperformancerequirements.
5.2SafetyRequirements
1.Datasecurity:Thesystemmustensurethatcustomerdataissecureandprotectedfrom
unauthorizedaccessortheft.Thisrequiresimplementingdataencryption,accesscontrols,
andauditing.
2.Frauddetectionandprevention:Thesystemshouldincludemeasurestodetectand
preventfraudulenttransactions,suchasanomalydetection,transactionmonitoring,anduser
authentication.

16. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
3.Disasterrecovery:Thesystemmustbedesignedtorecoverquicklyandreliablyfrom
disastersordisruptions,suchashardwarefailures,poweroutages,ornaturaldisasters.This
requiresimplementingbackupandrecoveryprocedures,redundancy,andfailover
mechanisms.
4.Regulatorycompliance:Thesystemmustcomplywithvariousregulatoryrequirements
relatedtodataprivacy,security,andfinancialreporting.Thesystemmaybesubjecttoaudits
byregulatorybodiesorthird-partyauditorstoverifycompliance.
5.3SecurityRequirements
1.Userauthentication:Thesystemmustverifytheidentityofusersaccessingthesystem,to
ensurethatonlyauthorizeduserscanperformtransactionsoraccesssensitivedata.This
requiresimplementingsecureloginprocedures,passwordpolicies,andmulti-factor
authentication.
2.Accesscontrols:Thesystemmustensurethatuserscanonlyaccessthedataand
functionalitythattheyareauthorizedtouse.Thisrequiresimplementingrole-basedaccess
controls,permissionlevels,andaudittrails.
3.Systemmonitoring:Thesystemshouldincludemonitoringcapabilitiestodetectsuspicious
activities,errors,orperformanceissues.Thisrequiresimplementinglogging,alerting,and
performancemetrics.
5.4SoftwareQualityAttributes
Availability:
Thisattributeisindicativeastowhetheranapplicationwillexecutethetasksitisassignedto
perform.Availabilityalsoincludescertainconceptsthatrelatetosoftwaresecurity,performance,
integrity,reliability,dependability,andconfidentiality.Inaddition,top-notchavailabilityindicates
thatasoftware-drivensystemwillrepairanyoperatingfaultssothatserviceoutageperiodswould
notexceedaspecifictimevalue.
Performance:
Thisattributepertainstotheabilityofasoftware-drivensystemtoconformtotimingrequirements.
Fromatestingpointofview,itimpliesthatSoftwareTestingengineersmustcheckwhetherthe
systemrespondstovariouseventswithindefinedtimelimits.Theseeventsmayoccurintheformof
clockevents,processinterruptions,messages,andrequestsfromdifferentusers,andothers.
Testability:
Softwaretestabilityindicateshowwellasoftware-drivensystemallowsSoftwareTesting
professionalstoconducttestsinlinewithpredefinedcriteria.Thisattributealsoassessestheease
withwhichSoftwareQualityAssuranceengineerscandeveloptestcriteriaforasaidsystemandits

17. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
variouscomponents.Engineerscanassessthetestabilityofasystembyusingvarioustechniques
suchasencapsulation,interfaces,patterns,lowcoupling,andmore.
Usability:
Everysoftware-drivensystemisdesignedforeaseofusetoaccomplishcertaintasks.Theattribute
ofusabilitydenotestheeasewithwhichusersareabletoexecutetasksonthesystem;italso
indicatesthekindofusersupportprovidedbythesystem.Themostwellknownprincipleforthis
propertyisKISS(KeepItSimpleStupid).Inaddition,SoftwareQualityAssuranceengineersmust
testsoftwaretocheckwhetheritsupportsdifferentaccessibilitytypesofcontrolforpeoplewith
disabilities.Usabilityhasacriticalandlongstandingbearingonthecommercialfortunesofa
softwareapplicationorpackage.
Functionality:
Thisattributedeterminestheconformityofasoftware-drivensystemwithactualrequirementsand
specifications.MostSoftwareTestingprofessionalsviewthisattributeascrucialandaforemost
requirementofamodernapplication,andwouldthereforeadvocatetheperformanceofteststhat
assessthedesiredfunctionalityofasystemintheinitialstagesofSoftwareTestinginitiatives.
5.5BusinessRules
BusinessRulesAbusinessruleisanythingthatcapturesandimplementsbusinesspoliciesand
practices.Arulecanenforcebusinesspolicy,makeadecision,orinfernewdatafromexisting
data.ThisincludestherulesandregulationsthattheSystemusersshouldabideby.Thisincludesthe
costoftheprojectandthediscountoffersprovided.Theusersshouldavoidillegalrulesand
protocols.Neitheradminnormembershouldcrosstherulesandregulations.

18. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
6.OtherRequirements
TherearedifferentcategoriesofusersnamelyAdmin,Usersetc.Dependinguponthecategoryof
usertheaccessrightsaredecided.Itmeansiftheuserisanadministratorthenhecanbeableto
modifythedata,delete,appendetc.AllotherusersexcepttheAdminonlyhavetherightstoretrieve
theinformationaboutdatabase.
AppendixA:AnalysisModels
TheBankingManagementSystemisasoftwareapplicationdesignedtoprovideefficientand
reliablebankingservicestoitsusers.TheanalysismodelsusedinthedevelopmentoftheBanking
ManagementSystemareasfollows:
UseCaseModel:Theusecasemodeldefinesthevarioususecasesofthesystemandtheir
interactionswithactorssuchascustomers,administrators,andtellers.Theusecasemodelhelpsin
identifyingsystemrequirementsandvalidatingsystemfunctionality.

19. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
ClassModel:Theclassmodeldefinesthevariousclassesandtheirrelationshipsinthesystem.The
classmodelhelpsinunderstandingsystemarchitectureandidentifyingdataobjects.
ActivityModel:Theactivitymodeldefinestheflowofactivitiesinaparticularusecase.The
activitymodelhelpsinidentifyingsystembehaviorandvalidatingsystemfunctionality.
DataFlowModel:Thedataflowmodeldefinestheflowofdatainthesystem.Thedataflow
modelhelpsinidentifyingsystemarchitectureandvalidatingsystemfunctionality.

20. SoftwareRequirementsSpecificationfor<BankingManagementSystem>
StateModel:Thestatemodeldefinesthevariousstatesofanobjectandtheirtransitions.Thestate
modelhelpsinidentifyingsystembehaviorandvalidatingsystemfunctionality.
TheanalysismodelsusedinthedevelopmentoftheBankingManagementSystemprovidea
comprehensiveunderstandingofsystemrequirements,architecture,andbehavior.Theuseofthese
modelshelpsinidentifyingpotentialissuesandimprovingsystemfunctionality.Themodelscan
alsobeusedforsystemdocumentation,testing,andmaintenance.