Software requirements specification for banking sector ,SRS is crucial documents that outlines the functional and non functional requirements of a software system.
• In the banking industry SRS documents are vital for ensuring that software systems are developed to meet the unique needs and requirements of financials institutions.In scope • Managing account of single user,which would include maintaining of bookkeeping information about balance,credit,debit transactions etc.
• Computing account balance at the end of the day and interest rate of depositor
Giving ATM,debit,credit card • Updating the balance • User authentication
Main Scenario – User fills the form for a new bank account. User submits the form with personal documents such as Aadhar card, pan card, etc. Bank staff create new accounts for
customer, including personal and account details. User’s bank account created
Alternate Scenario –
User fill wrong information in account opening form. User doesn’t submit the necessary documents.
Main Scenario – User visits the website. User prompted for login &
password. User gives the login & password. User receives OTP on the registered mobile number because of two factor authentication. System does authentication. Main screen is displayed.
Alternate Scenario – Authentication fails. Prompt the user that he typed the wrong password or OTP. Allow him to re-enter the password or OTP. Give him 3 chances.
Main Scenario –
User logs into their online banking account and selects the option to apply for a loan. The system prompts the user to fill out the necessary information, such as loan amount, repayment period, and interest rate. The system validates the information and approves or rejects the loan application.
Alternate Scenario –
If the user does not meet the eligibility criteria for the loan, the system rejects the application and displays a reason for rejection.
Main Scenario –
User log in to online banking. User adds the beneficiary details. User enter the amount to be transferred. User verifies the transaction details. User receives OTP on the registered mobile number because of two factor authentication. Fund has been transfer by the user.
Alternate Scenario – Authentication fails. Prompt the user that he typed the
wrong password. Beneficiary details incorrect such as IFSC code & Account No not matching.
2. Purpose
• SRS is crucial documents that outlines the functional and non
functional requirements of a software system.
• In the banking industry SRS documents are vital for ensuring that
software systems are developed to meet the unique needs and
requirements of financials institutions.
3. scope
• In scope
• Managing account of single user,which would include maintaining of
bookkeeping information about balance,credit,debit transactions etc.
• Computing account balance at the end of the day and interest rate of
depositor
• Giving ATM,debit,credit card
• Updating the balance
• User authentication
4. Out of scope
• Deposit and withdrawal of money
• Tax computations for income
• Any predications
5. Use Case 1 : Account Management
Main Scenario –
User fills the form for a new bank account. User submits
the form with personal documents such as Aadhar card,
pan card, etc. Bank staff create new accounts for
customer, including personal and account details. User’s
bank account created.
Alternate Scenario –
User fill wrong information in account opening form.
User doesn’t submit the necessary documents.
6. Use Case 2 : Online Banking Login
Main Scenario –
User visits the website. User prompted for login &
password. User gives the login & password. User receives
OTP on the registered mobile number because of two
factor authentication. System does authentication. Main
screen is displayed.
Alternate Scenario –
Authentication fails. Prompt the user that he typed the
wrong password or OTP. Allow him to re-enter the
password or OTP. Give him 3 chances.
7. Use Case 3 : Loan Management
Main Scenario –
User logs into their online banking account and selects
the option to apply for a loan. The system prompts the
user to fill out the necessary information, such as loan
amount, repayment period, and interest rate. The system
validates the information and approves or rejects the
loan application.
Alternate Scenario –
If the user does not meet the eligibility criteria for the
loan, the system rejects the application and displays a
reason for rejection.
8. Use Case 4 : Fund Transfer
Management
Main Scenario –
User log in to online banking. User adds the beneficiary
details. User enter the amount to be transferred. User
verifies the transaction details. User receives OTP on the
registered mobile number because of two factor
authentication. Fund has been transfer by the user.
Alternate Scenario –
Authentication fails. Prompt the user that he typed the
wrong password. Beneficiary details incorrect such as
IFSC code & Account No not matching.
9. Use Case 5 : Cash Withdraw
Main Scenario –
User inserts their debit card into an ATM machine. User
enter his Pin and selects the option to withdraw cash.
The system prompts the user to enter the amount they
wish to withdraw. The system validates the information
and dispenses the cash.
Alternate Scenario –
User entered wrong Pin. If the ATM does not have
sufficient funds to dispense the requested amount, the
system displays an error message and prompts the user
to enter a different amount.
