RFP Response for
Deepraj Pathak | 14th march, 2024
CLIENT DETAILS
• Unique Bank, a leading financial services group, operates across 28 markets. Unique Bank is APAC and EMEA
centered commercial bank focused on harnessing the region’s long-term potential as the center of economic
gravity shifts eastwards to Asia and Middle East
• A frontrunner in digital transformation, Unique Bank seek to deliver a new kind of banking that is so simple,
seamless and invisible, that customers have more time to spend on the people or things they care about.
• At Unique Bank is a strong advocate of building a sustainable future. Working with partners, empower people
to live larger than themselves. Unique Bank create avenues that encourage our customers to live socially
conscious; establish platforms to help social entrepreneurs bring their ideas to life; and provide the next
generation with opportunities to develop innovative solutions that address sustainability issues.
• Unique Bank is distinct from local or global players. As a leader in digital transformation, Unique Bank has the
reach and sophistication to outcompete local lenders, and deep Asian and Middle East insights that distinguish
us from global competitors. Unique Bank seek to intermediate trade and investment flows between Asia’s
three key axes of growth – Southeast Asia, South Asia and Middle East – as well as participate in Asia’s and
Middle East regions’ growing affluence.
PROJECT DETAILS
• Client is seeking to rewrite the internet banking platform with latest technologies and to update the product
and provide compatibility to use the application in mobile devices.
• Looking to replace the existing commercially off the shelf product with custom software
• Build an appealing User Experience
• Take sufficient assumptions on the existing system to provide an Unique Bank, at the same time a pragmatic
solution in this portal platform modernization.
• Client would like to see MVP version and then add features and enhancements once they get a customer
experience feedback?
• Migrating the existing users and data for last 3 years.
• Speed/Performance issues and response time.
• Centralised authentication mechanism has to be implemented.
CLIENT’S NEEDS
Current System Proposed System
 Live and Successful internet Banking platform
 Application using English as only Business Language
 Outdated UI(Fit for Web only)
 Built using legacy tools & technologies(Monolithic
Architecture)
 Adoption & Integration of COTS products
 Slow Time-to-Market
 Slow Performance
 Modern Banking platform
 Multi-Lingual Application
 Responsive UI experience for all kind of Touchpoints
like Web, Desktop, Mobile, Tablet, Foldable Display
 Simple & Seamless consumer like experience using
Microservices Architecture
 End to End Proprietary Solution(Zero COTS product)
 Very fast Time-to-Market
 Best in class performance using Geographically
Distributed System
 Centralized Authentication Mechanism
 Role-Based Authorization
 Migration of last 3 years data
 Regional Data Protection Rules & Policies
IDEATION TO PRODUCTION
DESIGN APPROACH(MICROSERVICES)
Why we chose
Microservices over
Monolithic?
1. Resiliency or Max. Availability
2. Loosely-Coupled Architecture
3. Very Smooth Add/update/Removal of new
Banking Features
4. Language Independent
5. Granularity
6. Easy to Maintain/Operate
LIST OF SERVICES IN INTERNET BANKING
• Authentication Service
• User Registration
• User Login
• Account Service
• Open/Close AC(Savings/Current/Demat/Trading)
• Check Account Summary
• Check Account Balance
• Download Statement / Automate E-Statement
• Update Details(Mobile No., Email ID, Home Branch, PIN No., Aadhaar
No.)
• Cheque Book Request
• New Debit Card Request
• Credit Card Limit Enhancement Request
• Redeem Reward Points
• NOC for Repaid Loans
• Transaction Service
• Add/Manage Payee
• Online Fund Transfer
• Auto-Debit
• Inward Remittances
• Online Recharge/Bill Payment(Mobile, D2H, Gas, Electricity, Fasttag)
• New LOB Service
• Open FD/RD/PPF/ULIP/Mutual Fund/Term Plan/Health
Insurance/Demat AC
• Request for Locker
• Apply for Bank AC/Credit Card/Debit Card/Loan
• Logging & Monitoring Service
• Fraud Detection Service
• Security Service
PROPOSED COMPONENT ARCHITECTURE
DB Replication
Failover
Rest API
PROPOSED DEPLOYMENT ARCHITECTURE
PROPOSED CI/CD PIPELINE AUTOMATION
PROPOSED TECH STACK & TOOLS
PROPOSED SAMPLE USE-CASE DIAGRAM
PROPOSED SAMPLE DATAFLOW DIAGRAM
DEVELOPMENT METHODOLOGY(AGILE)
Why we chose Agile over
Waterfall?
1. Less prone to Error
2. More Flexible & Adaptive to change
3. More Predictable End Product
4. Less Impact Analysis
5. Quick Time-to-Market
6. More Customer Involvement
QUALITY STRATEGY
Steps to Ensure Quality of
Microservices
1. Unit Testing: Performed by Developers
2. Integration Testing: Performed by QA
3. Component Testing: Performed by QA
4. Contract Testing: Performed by QA
5. End-to-End Testing: Performed by QA
QUALITY STRATEGY CONTD.(UTITCTCNTE2ET)
ESTIMATION & COST
STAFFING PLAN & RESOURCE LOADING
ENGAGEMENT TYPE
AGILE PROJECT GOVERNANCE FRAMEWORK
DATA GOVERNANCE FRAMEWORK
DATA PROTECTION(AS PER CURRENT MARKET SCOPE)
SECURITY IMPLEMENTATION
RISKS | CONSTRAINTS | DEPENDENCIES
Risks Constraints Dependencies
 Quality Risk
 Schedule Risk
 Budget Risk
 Scope Creep Risk
 Knowledge Risk
 Productivity Risk
 Security Risk
 External Risk
 Customer Acquisition
Risk
 Data Protection
Compliance Risk
 Scoping & Schedule would drive success of this
transformation. Clients handshaking is required at
the optimum level to know clear prioritization of
business objectives that result in product backlog.
So every product must have a clear business
owner identified and aligned.
 We propose modern development stack like Java,
Springboot, opensource tools for automation and
low code. In the event of any stack preferences
we would like to know upfront from the client.
 80% of the product development is carried at
offshore, so access, data clearance and other
logistics must be cleared off prior to the
engagement kick off.
 SME availability from client
side for user interviews,
knowledge transfers and
proposed architecture
review/consulting.
 Hardware/Software/Cloud
License Dependencies.
 Dependency on Client’s
Stakeholder Availability for
Periodic meetings.
QUESTIONS?
We are Listening……..
Thank you 

RFP Response for Unique Bank Technical Migration

  • 1.
    RFP Response for DeeprajPathak | 14th march, 2024
  • 2.
    CLIENT DETAILS • UniqueBank, a leading financial services group, operates across 28 markets. Unique Bank is APAC and EMEA centered commercial bank focused on harnessing the region’s long-term potential as the center of economic gravity shifts eastwards to Asia and Middle East • A frontrunner in digital transformation, Unique Bank seek to deliver a new kind of banking that is so simple, seamless and invisible, that customers have more time to spend on the people or things they care about. • At Unique Bank is a strong advocate of building a sustainable future. Working with partners, empower people to live larger than themselves. Unique Bank create avenues that encourage our customers to live socially conscious; establish platforms to help social entrepreneurs bring their ideas to life; and provide the next generation with opportunities to develop innovative solutions that address sustainability issues. • Unique Bank is distinct from local or global players. As a leader in digital transformation, Unique Bank has the reach and sophistication to outcompete local lenders, and deep Asian and Middle East insights that distinguish us from global competitors. Unique Bank seek to intermediate trade and investment flows between Asia’s three key axes of growth – Southeast Asia, South Asia and Middle East – as well as participate in Asia’s and Middle East regions’ growing affluence.
  • 3.
    PROJECT DETAILS • Clientis seeking to rewrite the internet banking platform with latest technologies and to update the product and provide compatibility to use the application in mobile devices. • Looking to replace the existing commercially off the shelf product with custom software • Build an appealing User Experience • Take sufficient assumptions on the existing system to provide an Unique Bank, at the same time a pragmatic solution in this portal platform modernization. • Client would like to see MVP version and then add features and enhancements once they get a customer experience feedback? • Migrating the existing users and data for last 3 years. • Speed/Performance issues and response time. • Centralised authentication mechanism has to be implemented.
  • 4.
    CLIENT’S NEEDS Current SystemProposed System  Live and Successful internet Banking platform  Application using English as only Business Language  Outdated UI(Fit for Web only)  Built using legacy tools & technologies(Monolithic Architecture)  Adoption & Integration of COTS products  Slow Time-to-Market  Slow Performance  Modern Banking platform  Multi-Lingual Application  Responsive UI experience for all kind of Touchpoints like Web, Desktop, Mobile, Tablet, Foldable Display  Simple & Seamless consumer like experience using Microservices Architecture  End to End Proprietary Solution(Zero COTS product)  Very fast Time-to-Market  Best in class performance using Geographically Distributed System  Centralized Authentication Mechanism  Role-Based Authorization  Migration of last 3 years data  Regional Data Protection Rules & Policies
  • 5.
  • 6.
    DESIGN APPROACH(MICROSERVICES) Why wechose Microservices over Monolithic? 1. Resiliency or Max. Availability 2. Loosely-Coupled Architecture 3. Very Smooth Add/update/Removal of new Banking Features 4. Language Independent 5. Granularity 6. Easy to Maintain/Operate
  • 7.
    LIST OF SERVICESIN INTERNET BANKING • Authentication Service • User Registration • User Login • Account Service • Open/Close AC(Savings/Current/Demat/Trading) • Check Account Summary • Check Account Balance • Download Statement / Automate E-Statement • Update Details(Mobile No., Email ID, Home Branch, PIN No., Aadhaar No.) • Cheque Book Request • New Debit Card Request • Credit Card Limit Enhancement Request • Redeem Reward Points • NOC for Repaid Loans • Transaction Service • Add/Manage Payee • Online Fund Transfer • Auto-Debit • Inward Remittances • Online Recharge/Bill Payment(Mobile, D2H, Gas, Electricity, Fasttag) • New LOB Service • Open FD/RD/PPF/ULIP/Mutual Fund/Term Plan/Health Insurance/Demat AC • Request for Locker • Apply for Bank AC/Credit Card/Debit Card/Loan • Logging & Monitoring Service • Fraud Detection Service • Security Service
  • 8.
    PROPOSED COMPONENT ARCHITECTURE DBReplication Failover Rest API
  • 9.
  • 10.
  • 11.
  • 12.
  • 13.
  • 14.
    DEVELOPMENT METHODOLOGY(AGILE) Why wechose Agile over Waterfall? 1. Less prone to Error 2. More Flexible & Adaptive to change 3. More Predictable End Product 4. Less Impact Analysis 5. Quick Time-to-Market 6. More Customer Involvement
  • 15.
    QUALITY STRATEGY Steps toEnsure Quality of Microservices 1. Unit Testing: Performed by Developers 2. Integration Testing: Performed by QA 3. Component Testing: Performed by QA 4. Contract Testing: Performed by QA 5. End-to-End Testing: Performed by QA
  • 16.
  • 17.
  • 18.
    STAFFING PLAN &RESOURCE LOADING
  • 19.
  • 20.
  • 21.
  • 22.
    DATA PROTECTION(AS PERCURRENT MARKET SCOPE)
  • 23.
  • 24.
    RISKS | CONSTRAINTS| DEPENDENCIES Risks Constraints Dependencies  Quality Risk  Schedule Risk  Budget Risk  Scope Creep Risk  Knowledge Risk  Productivity Risk  Security Risk  External Risk  Customer Acquisition Risk  Data Protection Compliance Risk  Scoping & Schedule would drive success of this transformation. Clients handshaking is required at the optimum level to know clear prioritization of business objectives that result in product backlog. So every product must have a clear business owner identified and aligned.  We propose modern development stack like Java, Springboot, opensource tools for automation and low code. In the event of any stack preferences we would like to know upfront from the client.  80% of the product development is carried at offshore, so access, data clearance and other logistics must be cleared off prior to the engagement kick off.  SME availability from client side for user interviews, knowledge transfers and proposed architecture review/consulting.  Hardware/Software/Cloud License Dependencies.  Dependency on Client’s Stakeholder Availability for Periodic meetings.
  • 25.
  • 26.