Public-safe case study
Turning banking requirements into working systems
How do risk and finance requirements become calculation logic, data architecture and deployable solutions?
At FPT IS, connected business requirements with Oracle-based and in-house CAR solutions, ICAAP implementation and Risk DataMart design.
Business Analyst — Banking Division
Requirements · calculation logic · POC · testing · deployment
CAR / ICAAP business-to-system delivery
FPT Information System · Nov 2018–Oct 2020
01
The implementation challenge
Banking risk and finance requirements need to be translated into definitions, calculation rules, data flows and system behavior. Business stakeholders and implementation teams must be able to work from the same interpretation.
02
My contribution
I worked on CAR and ICAAP solutions, translating requirements into calculation logic, data architecture and implementation designs. The work included Oracle solution configuration and the development of an in-house CAR solution, from requirements and proof of concept to testing and deployment.
I also contributed to Risk DataMart architecture and the development of ICAAP and ALM frameworks. This required working between banking risk and finance teams and the teams implementing the solution.
03
What the experience added
These assignments developed my ability to connect a business rule with its data requirements, system behavior and testable output. That discipline remains useful in product transformation: a strategic requirement becomes actionable when the delivery teams understand what must change and how it will be evaluated.
This case study focuses on transferable methods and leadership lessons. Customer data, proprietary model logic, exact commercial figures, and unpublished company decisions are not included.