Professional Documents
Culture Documents
SoftwareRequirementsSpecification
19/10/2015
SameerKhan
13CO37
TECO
SoftwareRequirementsSpecification
TableofContents
REVISIONHISTORY................................................................................................................................................II
DOCUMENTAPPROVAL........................................................................................................................................II
1.INTRODUCTION.....................................................................................................................................................1
1.1PURPOSE...............................................................................................................................................................1
1.2SCOPE....................................................................................................................................................................1
1.3DEFINITIONS,ACRONYMS,ANDABBREVIATIONS................................................................................................1
1.4REFERENCES.........................................................................................................................................................1
1.5OVERVIEW............................................................................................................................................................1
2.GENERALDESCRIPTION....................................................................................................................................2
2.1PRODUCTPERSPECTIVE........................................................................................................................................2
2.2PRODUCTFUNCTIONS...........................................................................................................................................2
2.3USERCHARACTERISTICS......................................................................................................................................2
2.4GENERALCONSTRAINTS.......................................................................................................................................2
2.5ASSUMPTIONSANDDEPENDENCIES......................................................................................................................2
3.SPECIFICREQUIREMENTS................................................................................................................................2
3.1EXTERNALINTERFACEREQUIREMENTS...............................................................................................................3
3.1.1UserInterfaces.............................................................................................................................................3
3.1.2HardwareInterfaces....................................................................................................................................3
3.1.3SoftwareInterfaces......................................................................................................................................3
3.1.4CommunicationsInterfaces..........................................................................................................................3
3.2FUNCTIONALREQUIREMENTS...............................................................................................................................3
3.2.1<FunctionalRequirementorFeature#1>..................................................................................................3
3.2.2<FunctionalRequirementorFeature#2>..................................................................................................3
3.3USECASES............................................................................................................................................................3
3.3.1UseCase#1.................................................................................................................................................3
3.3.2UseCase#2.................................................................................................................................................3
3.4CLASSES/OBJECTS..............................................................................................................................................3
3.4.1<Class/Object#1>.....................................................................................................................................3
3.4.2<Class/Object#2>.....................................................................................................................................3
3.5NONFUNCTIONALREQUIREMENTS......................................................................................................................4
3.5.1Performance.................................................................................................................................................4
3.5.2Reliability.....................................................................................................................................................4
3.5.3Availability...................................................................................................................................................4
3.5.4Security.........................................................................................................................................................4
3.5.5Maintainability.............................................................................................................................................4
3.5.6Portability....................................................................................................................................................4
3.6INVERSEREQUIREMENTS......................................................................................................................................4
3.7DESIGNCONSTRAINTS..........................................................................................................................................4
3.8LOGICALDATABASEREQUIREMENTS...................................................................................................................4
3.9OTHERREQUIREMENTS........................................................................................................................................4
4.ANALYSISMODELS..............................................................................................................................................4
4.1SEQUENCEDIAGRAMS..........................................................................................................................................5
4.3DATAFLOWDIAGRAMS(DFD)............................................................................................................................5
4.2STATETRANSITIONDIAGRAMS(STD)...................................................................................................................
SoftwareRequirementsSpecification
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
1.
1.Introduction
1.1Purpose
OnlinebankingsystemprovidesisspecificallydevelopedforinternetbankingforBalance
Enquiry,FundsTransfertoanotheraccountinthesamebank,Requestforcheque
book/changeofaddress/stoppaymentofcheques,Ministatements(ViewingMonthlyand
annualstatements).
TheTraditionalwayofmaintainingdetailsofauserinabankwastoenterthedetailsandrecord
them.Everytimetheuserneedtoperformsometransactionshehastogotobankandperform
thenecessaryactions,whichmaynotbesofeasibleallthetime.Itmaybeahardhittingtaskfor
theusersandthebankerstoo.TheprojectgivesreallifeunderstandingofInternetbankingand
activitiesperformedbyvariousrolesinthesupplychain.Here,weprovideanautomationfor
bankingsystemthroughInternet.Internetbankingsystemprojectcaptures
activitiesperformedbydifferentrolesinreallifebankingwhichprovidesenhancedtechniques
formaintainingtherequiredinformationuptodate,whichresultsinefficiency.Theproject
givesreallifeunderstandingofInternetbankingandactivitiesperformedbyvariousrolesinthe
supplychain.
1.2Scope
ThisProductwillautomateofbankingtransactionprocess.ThisProjectinvestigatesthe
entrythresholdforprovidinganewtransactionservicechannelviatherealoptions
approach,wheretheentrythresholdisestablishedbyusinganInternetbankingsystem
designedfortheuseofnormalusers(individuals),Industrialists,Entrepreneurs,
EducationalInstitutions(Financialsections),OrganizationsandAcademiciansunder
transactionrateuncertainty.
1.3Definitions,Acronyms,andAbbreviations
BMSBankManagementSystem
1.4References
www.w3schools.com
www.roseindia.net
www.dbforums.com
www.ibm.com
http://tomcat.apache.org/
SoftwareRequirementsSpecification
Page1
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
2.
2.GeneralDescription
2.1ProductPerspective
Theclientwillhaveclientinterfaceinwhichhecaninteractwiththebankingsystem.It
isawebbasedinterfacewhichwillbethewebpageofthebankingapplication.Startinga
pageisdisplayedaskingthetypeofcustomerheiswhetherordinaryoracorporate
customer.Thenthepageisredirectedtologinpagewheretheusercanenterthelogin
details.Iftheloginparticularsarevalidthentheuseristakentoahomepagewherehehas
theentiretransactionlistthathecanperformwiththebank.Alltheaboveactivitiescome
undertheclientinterface.
TheadministratorwillhaveanadministrativeinterfacewhichisaGUIsothathecan
viewtheentiresystem.Hewillalsohavealoginpagewherehecanenterthelogin
particularssothathecanperformallhisactions.Thisadministrativeinterfaceprovides
differentenvironmentsuchthathecanmaintaindatabase&providebackupsforthe
informationinthedatabase.Hecanregistertheusersbyprovidingthemwithusername,
password&bycreatingaccountinthedatabase.Hecanviewthechequebookrequest&
performactiontoissuethechequebookstotheclients.
2.2ProductFunctions
Thissectionprovidesthefunctionaloverviewoftheproduct.Theprojectwillrequirethe
PHPasafrontendandatthebackendthedatabaseMYSQLwillberunning.Various
functionalmodulesthatcanbeimplementedbytheproductwillbe
1.Login
2.Validation
3.Getbalanceinformation
4.Withdrawalofmoney
5.TransferMoney
6.Customerinfo.
2.2.1Login:
Customer logins by entering customer name & a login pin.
2.2.2Validation:
WhenacustomerenterstheATMcard,itsvaliditymustbeensured.Then
customerisallowedtoenterthevalidPIN.Thevalidationcanbeforfollowingconditions
Validationforlostorstolencard
Whencardisalreadyreportedaslostorstolen
thenthemessageLost/Stolencard!!!.
SoftwareRequirementsSpecification
Page2
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
Validationforcardsexpirydate
Ifthecardinsertedbythecustomerhascrossedtheexpirydatethenthesystemwillprompt
ExpiredCard.
ValidationforPIN
Aftervalidatingthecard,thevalidityofPINmustbeensured.Ifhe/shefailstoentervalidcode
forthreetimesthenthecardwillnotbereturnedtohim.Thatmeanstheaccountcanbelocked.
Thecounterfornumberofloginsmustbemaintained
Getbalanceinformation:
Thissystemmustbenetworkedtothebankscomputer.Theupdated
databaseofeverycustomerismaintainedwithbank.Hencethebalanceinformationofevery
accountisavailableinthedatabaseandcanbedisplayedtothecustomer.
2.2.3PaymentofMoney:
Acustomerisallowedtoentertheamountwhichhe/shewishestowithdraw.If
theenteredamountislessthantheavailablebalanceandifafterwithdrawiftheminimum
requiredbalanceismaintainedthenallowthetransaction.
2.2.4TransferofMoney:
Thecustomercandepositortransferthedesiredamountofmoney.
2.2.5Technical Issues
This product will work on client-server architecture. It will require an internet
server and which will be able to run PHP applications. The product should support some
commonly used browsers such as Internet Explorer, Mozilla Firefox.
2.2.6AircraftCheckin
Description:ThisprocessallowsapassengertoboardinAircraftandallowedtoproduce
ValidTicketsdetails.IftheDetailsareinvalid,Passengerisnotallowedtoboardin.
2.3UserCharacteristics
BankFrontendEmployees:TheBankEmployeeswouldbethemainusersoftheBankMan
Systems.TheymayperformbankingfunctionsusingEWS
ormayfacilitatecustomerinusingATM,asperbank'spolicy.
BankCustomers:ThecustomerswouldbeabletouseATMLogin,ifbankwantstoprovide
userwithdirectaccess,otherwisetheymayuseATMvia.Bank
Employee.
SoftwareRequirementsSpecification
Page3
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
2.4GeneralConstraints
1)TheinformationofalltheusersmustbestoredinadatabasethatisaccessiblebytheOnline
BankingSystem.
2)TheOnlineBankingSystemisconnectedtothecomputerandisrunningall24hoursaday.
3)TheusersaccesstheOnlineBankingSystemfromanycomputerthathasInternet
browsingcapabilitiesandanInternetconnection.
4)TheusersmusthavetheircorrectusernamesandpasswordstoenterintotheOnlineBanking
System.
2.5AssumptionsandDependencies
AllusersareassumedtobeequippedwithGUIterminals.
AllmasterdataentrywillbeundertakenjointlybyRMA.
AllCAMusershaveundergoneusertraining.
ReportswhicharenotfreezemustbefreezebeforethecompletionofHighleveldesign.
AllthedatarequirementsectiongiveninallprocesswillbegivenduringtheHighlevel
designstage
Inputparametersforreportneedsfurtherdiscussionwiththeendusers.
3.SpecificRequirements
3.1ExternalInterfaceRequirements
3.
3.1.1UserInterfaces
4.
3.1.2HardwareInterfaces
Variousinterfacesfortheproductcouldbe
1.Touchscreen/Monitor
2.Keypad
3.Continuousbatterybackup
4.Printerwhichcanproducethehardcopy.
5.Interfacethatconnectsthedevicetobankscomputer.
6.Aninterfacethatcancountcurrencynotes.
SoftwareRequirementsSpecification
Page4
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
5.
3.1.3SoftwareInterfaces
6. 1.Anywindowsoperatingsystem.
2.ThePHPmustbeinstalled.ForthedatabasehandlingMYSQLmustbeinstalled.These
productsareopensourceproducts.
3.Thefinalapplicationmustbepackagedinasetupprogram,sothattheproductscanbeeasily
installedonmachines.Thisapplicationmustbenetworkedtocorrespondingbanks.
7.
3.1.4CommunicationsInterfaces
CustomershouldaskclerktoconfirmtheacceptanceofAccountsignature.
Customershouldsubmitsliptotheclerkfortransaction.
3.2FunctionalRequirements
ThedetailsofthefunctionalitiesandmajorusecasecoveredintheCAMmoduleare:
MasterFileMaintenance
NgultrumAccounting
NormalVoucherPreparation
NormalVoucherAuthorization
ReverseVoucherPreparation
ReverseVoucherAuthorization
ProcessJournalReport
StaffSalarySaving
Withdrawalofsalary
Deposit
InterestCalculation
BankChequeMaintenance
Recordnewchequebook
ControlCancelCheque
BankReconciliation
BankStatementsEntry
BankStatementsAuthorization
Reconcileaccounts
ForeignCurrencyAccounting
NormalVoucherPreparation
NormalVoucherAuthorization
NormalReserveVoucherPreparation
NormalReverseVoucherAuthorization
BK01VoucherPreparation
BK01VoucherAuthorization
SoftwareRequirementsSpecification
Page5
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
BK02VoucherPreparation
BK02VoucherAuthorization
BK03VoucherPreparation
BK03VoucherAuthorization
BK04VoucherPreparation
BK04VoucherAuthorization
BK07VoucherPreparation
BK07VoucherAuthorization
BK08VoucherPreparation
BK08VoucherAuthorization
BK09VoucherPreparation
BK09VoucherAuthorization
BK10VoucherPreparation
BK10VoucherAuthorization
Revaluation
ForexHoldingRates
PrepareTableofconversion
GenerateRevaluationVouchers
RevaluationJournal
Linkagewithothermodules
IssueDivision
ForexDivision
PersonnelandAdministrationDivision
ResearchandStatisticalDivision
FinancialInstitutionSupervisionDivision
PaymentandSettlementSystem
GeneralReports
MIS/TimeSeriesReports
SoftwareRequirementsSpecification
Page6
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
3.3UseCases
8.
3.3.1UseCase#1
SoftwareRequirementsSpecification
Page7
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
3.3.2Usecase#2
3.3.3Usecase#3
SoftwareRequirementsSpecification
Page8
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
3.3.4Usecase#4
SoftwareRequirementsSpecification
Page9
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
3.4Classes/Objects
1.
3.4.1Customer
3.4.1.1.Attributes:
1.ID
2.Address
3.AccountNo.
SoftwareRequirementsSpecification
Page10
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
3.4.1.2.Functions:
1.OpenAccount
2.WithdrawCash
3.Applyforloan
4.Deposit
3.4.2Accountant
3.4.2.1.Attributes:
1.ID
2.Name
3.4.2.2.Functions:
1.Enquiry
2.LoanRequest
3.ProvideInfo.
4.Transaction
3.4.3Bank
3.4.3.1.Attributes:
1.BankID
2.Name
3.Loc
3.5NonFunctionalRequirements.
1.
3.5.1Performance
2.
3.5.2Reliability
3.
Thesystemshallupdateallaccountsinformationaftereverytransaction
Responsestoqueriesshalltakenolongerthan10secondstoloadontothescreenafter
theuserpaymentisinProcess.
TheUserVerificationprocessshouldaccessthedatabasefasterandConfirmation
messagemustbedisplay.
Nobreakdownofserverproblemsandaccountsstatusshouldnotbedelayed.
3.5.3Availability
AvailabilitytoseekhelpfromanystaffshouldbeProvided.
SoftwareRequirementsSpecification
Page11
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
4.
3.5.4Security:
Theuserdetailsinsidethedatabasemustbesafeandshouldbeproducewhenever
necessary.
Theconfirmationmessageafterpaymentmustbesafelysendtocustomeremails.
5.
3.5.5Maintainability
Thecustomerdetailsinsidethedatabasemustbesafelymaintained.
Thedetailsoftransactionmustbemaintained.
3.6InverseRequirements
NoInverseRequirements.
3.7DesignConstraints
NoDesignConstraints.
3.8LogicalDatabaseRequirements
3.9OtherRequirements
Catchallsectionforanyadditionalrequirements.
6.
4.AnalysisModels
4.1SequenceDiagrams
SoftwareRequirementsSpecification
Page12
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
SoftwareRequirementsSpecification
Page13
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
SoftwareRequirementsSpecification
Page14
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
4.3DataFlowDiagrams(DFD)
SoftwareRequirementsSpecification
Page15
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
SoftwareRequirementsSpecification
Page16
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
4.2StateTransitionDiagrams(STD)
SoftwareRequirementsSpecification
Page17
SYSTEMREQUIREMENTSPECIFICATIONFORLOANMANAGEMENTSYSTEM
1.
5.ChangeManagementProcess
IdentifyanddescribetheprocessthatwillbeusedtoupdatetheSRS,asneeded,whenproject
scopeorrequirementschange.Whocansubmitchangesandbywhatmeans,andhowwillthese
changesbeapproved.
SoftwareRequirementsSpecification
Page18