Oak Systems Banking UAT - A Case Study 1
A Case Study in Banking UAT
Oak Systems Banking UAT - A Case Study 2
About the Client
One of the Leading Banks in Oceanic
Region with large presence in Asia-
Pacific and Europe
Oak Systems Banking UAT - A Case Study 3
About the project
UAT of Customization done for the
Bank’s Asian Entities (Acquired by the
Bank in Retail, Institutional and Credit
card business)
Oak Systems Banking UAT - A Case Study 4
Functionalities involved
Asset: General Loans, Corporate
Loans, Syndicated Loans, Collaterals,
Limits
Liabilities: Current A/c, Savings A/c,
Term deposits
Others: EOD/BOD, SI, Inventory
Reconciliation, Payment Systems
Oak Systems Banking UAT - A Case Study 5
External Interfaces Tested
PSGL (General Ledger System) :
Outbound, and Inbound Txn interface
SPARROW / IST: ATM Switch
IVR: Interactive Voice Response
AML
Oak Systems Banking UAT - A Case Study 6
Different Testing Aspects covered
MAT : Minimum Acceptance Testing: – This
is a Sanity test done to ascertain the quality of
the Build and the environment being used for
testing.
Progression Testing (ST): The cycle wherein
the Enhancements / Patches are being tested in
depth and certified as per the business
requirement.
Oak Systems Banking UAT - A Case Study 7
Different Testing Aspects covered
System Integration Testing (SIT): – This is
done to ascertain if the System is in Sync with all
the required Interfaces and there is no
Downstream impact.
Regression Testing: The cycle wherein the
existing Functionalities are being tested and
ensured that it does not break.
Oak Systems Banking UAT - A Case Study 8
Different Testing Aspects covered
• End to End Testing (ETE): – This is done to
certify that the required data is in the defined
format which is being passed on to the
Downstream systems and are successfully
uploaded in all the required Interfaces.
• Back out Testing: The cycle wherein the new
Enhancements / Patches are reverted and ensured
that the system comes back to the original shape
in case of any unforeseen issues during
deployment.
Oak Systems Banking UAT - A Case Study 9
Major Roles of Team
SME's – Reviewing UAT detailed test plan and
Test scenarios, Supporting test execution,
Liaising with test team, Interacting with end
users
UAT Lead - Leading the respective test phase
from planning to completion
Test Analysts – Developing test cases,
Executing Test cases, Raising defects, Retest
Defect Fixed
Oak Systems Banking UAT - A Case Study 10
Major Responsibilities of Team
Involved in all the phases of testing right from
the requirement discussions to certifying the
enhancement / Patch. Testing Estimation and
resource allocation. Knowledge Transfer and
Hand holding to the new team members.
Preparation of HLTC’s, DLTC’s, Uploading the
same to QC, Test case execution, Raising
defects, follow up on the defect status,
Retesting of defects, publishing the various
Testing Matrix reports as per the clients
requirement.
Oak Systems Banking UAT - A Case Study 11
Major Highlights
A Team of 20 involved with Experience Range
of 3 – 12 years in various aspects of banking
domain including Testing
Average Finacle Experience of Team members 3-
4 years
Parallel work on Multiple tracks to meet
schedules
Team Involved in End-to-End Testing, System
Testing, System Integration Testing
Core Team involved in Critical Functional Testing
Oak Systems Banking UAT - A Case Study 12
Thank you
For further details, please contact us at –
OAK SYSTEMS PRIVATE LIMITED
#27, NGEF LANE, OFF 100 FEET ROAD,
INDIRANAGAR, BENGALURU – 560 038
Phone: +91-80-25216303; +919845091480
http://www.oaksys.net
pradeep@oaksys.net

Case study on Banking Software Testing - FINACLE : UAT

  • 1.
    Oak Systems BankingUAT - A Case Study 1 A Case Study in Banking UAT
  • 2.
    Oak Systems BankingUAT - A Case Study 2 About the Client One of the Leading Banks in Oceanic Region with large presence in Asia- Pacific and Europe
  • 3.
    Oak Systems BankingUAT - A Case Study 3 About the project UAT of Customization done for the Bank’s Asian Entities (Acquired by the Bank in Retail, Institutional and Credit card business)
  • 4.
    Oak Systems BankingUAT - A Case Study 4 Functionalities involved Asset: General Loans, Corporate Loans, Syndicated Loans, Collaterals, Limits Liabilities: Current A/c, Savings A/c, Term deposits Others: EOD/BOD, SI, Inventory Reconciliation, Payment Systems
  • 5.
    Oak Systems BankingUAT - A Case Study 5 External Interfaces Tested PSGL (General Ledger System) : Outbound, and Inbound Txn interface SPARROW / IST: ATM Switch IVR: Interactive Voice Response AML
  • 6.
    Oak Systems BankingUAT - A Case Study 6 Different Testing Aspects covered MAT : Minimum Acceptance Testing: – This is a Sanity test done to ascertain the quality of the Build and the environment being used for testing. Progression Testing (ST): The cycle wherein the Enhancements / Patches are being tested in depth and certified as per the business requirement.
  • 7.
    Oak Systems BankingUAT - A Case Study 7 Different Testing Aspects covered System Integration Testing (SIT): – This is done to ascertain if the System is in Sync with all the required Interfaces and there is no Downstream impact. Regression Testing: The cycle wherein the existing Functionalities are being tested and ensured that it does not break.
  • 8.
    Oak Systems BankingUAT - A Case Study 8 Different Testing Aspects covered • End to End Testing (ETE): – This is done to certify that the required data is in the defined format which is being passed on to the Downstream systems and are successfully uploaded in all the required Interfaces. • Back out Testing: The cycle wherein the new Enhancements / Patches are reverted and ensured that the system comes back to the original shape in case of any unforeseen issues during deployment.
  • 9.
    Oak Systems BankingUAT - A Case Study 9 Major Roles of Team SME's – Reviewing UAT detailed test plan and Test scenarios, Supporting test execution, Liaising with test team, Interacting with end users UAT Lead - Leading the respective test phase from planning to completion Test Analysts – Developing test cases, Executing Test cases, Raising defects, Retest Defect Fixed
  • 10.
    Oak Systems BankingUAT - A Case Study 10 Major Responsibilities of Team Involved in all the phases of testing right from the requirement discussions to certifying the enhancement / Patch. Testing Estimation and resource allocation. Knowledge Transfer and Hand holding to the new team members. Preparation of HLTC’s, DLTC’s, Uploading the same to QC, Test case execution, Raising defects, follow up on the defect status, Retesting of defects, publishing the various Testing Matrix reports as per the clients requirement.
  • 11.
    Oak Systems BankingUAT - A Case Study 11 Major Highlights A Team of 20 involved with Experience Range of 3 – 12 years in various aspects of banking domain including Testing Average Finacle Experience of Team members 3- 4 years Parallel work on Multiple tracks to meet schedules Team Involved in End-to-End Testing, System Testing, System Integration Testing Core Team involved in Critical Functional Testing
  • 12.
    Oak Systems BankingUAT - A Case Study 12 Thank you For further details, please contact us at – OAK SYSTEMS PRIVATE LIMITED #27, NGEF LANE, OFF 100 FEET ROAD, INDIRANAGAR, BENGALURU – 560 038 Phone: +91-80-25216303; +919845091480 http://www.oaksys.net pradeep@oaksys.net