Thus core banking components include:

Interest calculations
Processing of cash deposits and withdrawals
Processing of incoming and outgoing remittances, cheques, etc.
Customer management
Customer account management
Definition of the banks products (product management) including such things as minimum
balances, interest rates, number of withdrawals, etc.
Interest rate definition
Customers standing instructions
Maintaining records of all financial transactions
Challenges for testing in Banking Domain:
There are 3 characteristics that pose specific challenges to testing for banks:
1. Frequently changing market and regulatory requirements
2. High data confidentiality requirements
3. Complex system landscapes including legacy systems
Resulting the Challenges:
challenge 1:Ensure cost-effective regression testing over the application life-cycle
challenge2: Ensure test data usage is compliant with data confidentiality requirements
challenge3: Ensure testing covers system integration and ensure integrity of test data

Testing Approaches:
ForChallenge1: RiskbasedTesting,Automate testcases,off-shore testactivites
It is always a good approach to think about risk-based testing before starting to automate test cases or
starting to off-shore test activities. The aim should be to reduce the number of tests to be executed for
each release (or upgrade) while keeping the risk within an acceptable range
Forchallenge2:
There are two basic approaches that can be taken to achieve compliance
with data confidentiality requirements: Data masking ,Synthetic test data
Data masking tools and techniques can be used to change production
data in a way that it is not sensitive anymore and can be used for testing purposes. The main advantages
of this approach are a good coverage regarding diversity and volume of data and the option to
reproduce production scenarios
synthetic test data is excellent under the aspects of compliance, sustainability and
integrity assuming that the synthetic data is produced the same way as real data in production.
However, the disadvantage is that some gaps regarding coverage always remain, because it is not
possible to synthetically produce all kinds and varieties of data (incl. historical data constellations) with
all systems
Challenge3:system integration test environment (incl. all systems and batch processing).
system integration test environment needs to fulfill the following requirements:
system coverage and operational coverage,Data coverage&Integrity and Environment Management.
he characteristics of a Banking application are as follows:
Multi tier functionality to support thousands of concurrent user sessions
Large scale Integration , typically a banking application integrates with numerous
other applications such as Bill Pay utility and Trading accounts
Complex Business workflows
Real Time and Batch processing
High rate of Transactions per seconds
Secure Transactions
Robust Reporting section to keep track of day to day transactions
Strong Auditing to troubleshoot customer issues
Massive storage system
Disaster Management.
banking application may have:
1. Web Server to interact with end users via Browser
2. Middle Tier to validate the input and output for web server
3. Data Base to store data and procedures
4. Transaction Processor which could be a large capacity Mainframe or any other Legacy
system to carry out Trillions of transactions per second.


http://www.gcreddy.com/2012/11/banking-domain.html#.UUCr8hx_Mmk
http://www.indiumsoft.com/banking_focus.php
books.google.co.in/books?isbn=812033535X