SRS For HDFC Banking System
SRS For HDFC Banking System
SRS For HDFC Banking System
INDEX
1.Introduction
1.1 Purpose
1.2 Scope
1.3 Overview
2. General Description
3. Functional specifications
3.1Login
3.2Validation
3.3Payment of money
3.4Transfer of money
3.5Transaction report
4. Interface Requirements
4.1 GUI
5. Performance Requirements
6. Constraints
7 Performance
7.1Security
7.2 Reliability
7.3 Availability
7.4 Maintainability
7.5 Reusability
8. References
Revision history
1. INTRODUCTION
HDFC Bank Limited (also known as HDFC) is an Indian banking and financial services company
headquartered in Mumbai. It is India's largest private sector bank by assets and the world's sixth-
largest bank by market capitalization as of August 2023, following its takeover of parent company
HDFC. The Reserve Bank of India (RBI) has identified the HDFC Bank, State Bank of India, and ICICI
Bank as Domestic Systemically Important Banks (D-SIBs), which are often referred to as banks that
are “too big to fail”. Source: Wikipedia
In this SRS DOCUMENT I will make detailed functional and nonfunctional requirements for the HDFC-
bank management system. This product will support online banking transaction. By this document a
programmer/developer will be able to completely understand customer requirement without
ambiguity
1.1 Purpose
This software of HDFC banking system is for internet banking for Balance Enquiry, Funds transfer
to another account in the same bank, Request for cheque book/change of address/stop
payment of cheques, complaints system for bank related fraud, wrong upi-payment reversal if
proved genuine also limit for reversal, Mini statements(can be sort by monthly ,yearly).
Earlier days, to maintain all details of a customer by entering details and record them manually,
Always user have to go to bank and fill cash withdrawal/ debit form offline by himself on receipt
that was not feasible, also they have to wait in queue for urgent cash that was again time
consuming, looking at complexity and problem faced by both customer and bank we will design
an internet banking system for the same to tackle the problem effectively.
HDFC online banking system will be safe, secure and easy user-interface compatible across all
devices.
1.2 Scope
This Product will automate of banking transaction process. This Project investigates the entry
threshold for providing a new transaction service channel via the real options approach, where
the entry threshold is established by using an Internet banking system designed for the use of
normal users(individuals), Industrialists, Entrepreneurs, Educational Institutions(Financial
sections), Organizations and Academicians under transaction rate uncertainty.
1.3 Overview
Overall Description: This section will describe major components of the system,
interconnections, and external interfaces.
Specific Requirements: This section will describe the functions of actors, their roles in the system
and the constraints faced by system.
2. General description
2.1 Product Perspective:
There will be client interface where he can interact with the banking system. It is a web
based interface which will be the webpage of the banking application. There will be a
homepage providing navigation to all the services like home loan, net banking, credit card
portal and more;
There will be dropdown for log in button containing personal login for normal user
After clicking login button on home page after clicking on it a pop window will appear asking
user credentials for log in and there will be 2 step verification otp through sms and email and
correct captcha need to be entered.
If login is verified the user will be redirected to home page with his user profile containing
His bank details transaction history. In case user Is new don’t know how to navigate through
Application there will be a guide video for each section for how to use the application
The administrator will have an administrative interface which is a GUI so that he can view
the entire system. He will also have a login page where he can enter the login particulars so
that he can perform all his actions. This administrative interface provides different
environment such that he can maintain data- base & provide backups for the information in
the database. He can register the users by providing them with username, password & by
creating account in the database. He can view the cheque book request & perform action to
issue the cheque books to the clients
Frontend client
Clients can use latest web browser like mozilla firefox , brave, Microsoft edge
Web server:
The web application will be hosted on any web server like F5 NGINX , LIGHTTPD , APACHE .
Back End:
3. functional specifications
This will be most important section,providing functional overview of product. We will be using PHP
as frontend and My SQL as backend for database.
1.Login
2.Validation
4.withdrawal of money
5.transfer money
6.customer info
3.1 Login:
Customer will login by entering user-id and password.
3.2 validation:
a customer enters the ATM card, its validity must be ensured. Then customer is allowed to
enter the valid PIN. The validation can be for following conditions:
When card is already reported as lost or stolen then the message “Lost/Stolen card!!!”.
If the card inserted by the customer has crossed the expiry date then the system will prompt
“Expired Card”.
database of every customer is maintained with bank. Hence the balance information of
every account is available in the database and can be displayed to the customer.
A customer is allowed to enter the amount which he/she wishes to withdraw. If the entered
amount is less than the available balance and if after withdraw if the minimum required
balance is maintained then allow the transaction.
The bank statement showing credit and debit information of corresponding account must be
printed by the machine.
A transaction should have all the properties of a data base transaction (Atomicity,
Consistency, Isolation, Durability).
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 Chrome, Microsoft Edge, Mozilla Firefox.
In this Customer can access all the services offered by the Bank by adding his details. As the
Customer avails any services as a transaction or a loan, then the required data flows to
Transaction Management System or the Loan Management System respectively. Any
Customer can print the activity status of the account which fetches information from all the
available databases using the Generate Customer Report System.
It helps the Customer to add/transfer money to another account. The Cashier may execute
or help execute the transaction process on behalf of the Bank where the Bank updates all
the corresponding details related to the Customer following a successful transaction.
It is used by the Customer to apply or request a Loan from the Bank. The Manager can
access the Loan_Details database to either accept or deny the request for the Loan. The
Bank has the access to modify the Loan Management System as the Bank can set or modify
any policies of the Loan offered by the Bank.
4. Interface Requirements
4.1 GUI(Graphical User Interface)
This is interface must be highly intuitive or interactive because there will not be an
assistance for the user who is operating the System. At most of the places help desk should
be provided for users convenience. The screens appearing should be designed in such a
manner that it can draw User attaraction towards the new plans for the customers.
Also the pin and password confidentiality should be maintained, This can be done by using
1. Touch screen/Monitor
2. Keypad
2. The PHP must be installed. For the database handling MYSQL must be installed.
These products are open source products.
3. The final application must be packaged in a set up program, so that the products can
be easily installed on machines. This application must be networked to corresponding banks.
5. Performance Requirements
The system should be compatible enough to hold the general traffic banking server should be fast .
It should not get hang or show some other problems arising out due to large no of concurrent users .
The system should be fast enough to meet the customer The high and low temperature should not
affect the performance of the device. An uninterrupted transaction must be performed.
6. Constraints
* The information of all the users must be stored in a database that is accessible by the
Online Banking System.
* The Online Banking System is connected to the computer and is running all 24hours a day.
* The users access the Online Banking System from any computer that has Internet
browsing capabilities and an Internet connection.
*The users must have their correct usernames and passwords to enter into the Online Banking
System.
Design Constraints:
The languages that shall be used for coding Online Banking System are c , c++ , java , and HTML. For
working on the coding phase of the Online job portal System Web Sphere Application
Server/WebSphere Application Server CE Server needs to be installed.
Database design
In our HDFC BANK database design, we give names to data flows, processes and data stores.
Although the names are descriptive of data, they do not give details .So following DFD, our interest is
to build some details of the contents of data flows, processes and data store. A data dictionary is a
structured repository of data about data .It is a set of rigorous definitions of all DFD data elements
and data structures .
7. Performance
7.1 Security
The banking system must be fully accessible to only authentic user. It should require pin for
entry to a new environment.
7.2 Reliability
The application should be highly reliable and it should generate all the updated information
in correct order.
7.3 Availability
Any information about the account should be quickly available from any computer to the
authorized user. The previously visited customer’s data must not be cleared.
7.4 Maintainability
The application should be maintainable in such a manner that if any new requirement occurs
then it should be easily incorporated in an individual module.
7.5 Portability
The application should be portable on any windows based system. It should not be machine
specific.
Definitions:
• Account
A single account in a bank against which transactions can be applied. Accounts may be of
various types with at least checking and savings. A customer can hold more than one
account.
• ATM
A station that allows customers to enter their own transactions using cash cards as
identification. The ATM interacts with the customer to gather transaction information, sends
the transaction information to the central computer for validation and processing, and
dispenses cash to the customer. We assume that an ATM need not operate independently of
the network.
• Bank
A financial institution that holds accounts for customers and that issues cash cards
authorizing access to accounts over the ATM network.
• Bank computer
The computer owned by a bank that interfaces with the ATM network and the bank’s own
cashier stations. A bank may actually have its own internal network of computers to process
accounts, but we are only concerned with the one that interacts with the network.
• Cash Card
A card assigned to a bank customer that authorizes access to accounts using an ATM
Machine. Each card contains a bank code and a card number, coded in accordance with
national standards on credit cards and cash cards. The bank code uniquely identifies the
bank within the consortium. The card number determines the accounts that the card can
access. A card does not necessarily access all of a customer’s accounts. Each cash card is
owned by a single customer, but multiple copies of it may exist, so the possibility of
simultaneous use of the same card from different machines must be considered.
• Customer
The holder of one or more accounts in a bank. A customer can consist of one or more
persons or corporations, the correspondence is not relevant to this problem. The same
person holding an account at a different bank is considered a different customer.
• Transaction
A single integral request for operations on the accounts of a single customer. We only
specified that ATMs must dispense cash, but we should not preclude the possibility of
printing checks or accepting cash or checks. We may also want to provide the flexibility to
operate on accounts of different customers, although it is not required yet. The different
operations must balance properly.
8 References:
www.w3schools.com
www.roseindia.net
www.dbforums.com
www.ibm.com
https://tomcat.apache.org/
Submitted by
Section K23EU
Roll no. 08
Design section
DFD
Levl 0
Level 1:
Account management
Level 2 transaction management
Dependencies:
User=
Navigate to login example@gmail User should be User is navigated Pass
1 page .com able to login to
Click on Login
4 button
Post-conditions:
User is validated with database and successfully login to account. The account session
details are logged in database.
Project Name: HDFC BANKING SYSTEM
Dependencies:
With message
“incorrect
Provided invalid username\
2 username Password: 1254 password”
Click on Login
4 button
Post-conditions:
User is not validated with database and not allowed to login to account. The account
session details are not logged in database. “Redirected to login page again”
Test cases :
Test case id 1
Test scenario Validate the login page enter invalid/wrong
user name and valid password
Test case Enter invalid user name and valid password
Expected result System should not allow the customer to login
the HDFC online banking login page and it
should display the message “please enter valid
user name and password”.
Actual result Customer is not able to login HDFC online
banking account.
Status Pass.
Test Data USER-ID: abcdf
Password:xyz123
Test case id 2
Test scenario Validate the login page enter invalid/wrong
user name and invalid password
Test case Enter invalid username and invalid password
Expected result System should not allow the customer to login
the HDFC online banking login page and it
should display the message “please enter valid
user name and password”.
Actual result Customer is not able to login HDFC online
banking account.
Status Pass.
Test Data USER-ID: abcd
Password:xyz12
Test case id 3
Test scenario Validate the login page enter valid user name
and invalid password
Expected result System should not allow the user to login the
HDFC banking system
Actual result Customer is not able to login HDFC online
banking account.
Status Pass.
Test Data USER-ID: abcdf
Password:xyz123
Test case id 4
Test case Enter valid user name and valid password
Expected result System should allow the user to login HDFC
banking system
Actual result Customer is able to login HDFC online banking
account.
Status Pass.
Test Data USER-ID: abcdf
Password:xyz123