Framework-Driven Development of Risk Management Products: Enhancing Customization, Compliance, and Feature Reuse

DOI

https://www.doi.org/10.59256/indjcst.20260501073

Published In

Volume 5, Issue 1 (2026)

Published Online

January-April 2026

Pages

616-623

Article Type

Original Article

Check for updates

To address the operational, credit and regulatory risks, banks resort to Risk Management and Consumer Loan Processing products. These products are Basel compliant II to Basel compliant III but can be tailored according to the country-based requirements and bank-specific processes. The time delays in implementation were however large as the banks would make frequent requests to include additional workflows and function. These custom-made features could also not be adopted into the core products to become a common use due to the existence of various technologies and various development teams. In order to resolve these problems, we have devised a common architecture, an unrestricted and generic approach to normalize development, reduce redundancy and increase the delivery of features. It provides a central repository of user, product and functionality where Role-Based Access Control (RBAC) and Single Sign-On (SSO) can be integrated, workflow can be manipulated, reporting services can be provided and notification services can be provided- in an abstract form so as to provide product specific customization. The technology stack on which the framework is based is Java, JSF, spring and Hibernate. RBAC modules had externalized hooks that were used to delegate user principles at the product-level. Mapping of feature requests of a number of banking products, absolute implementation of a feature request, was done in one central place and it could be reused by other products. During the integration of product specific features into the core systems, implementation of the framework using five products in the banks provided 40 percent reduction in the mean feature development time, 60 percent faster-integration of customized workflows and 50 percent reduction in deployment conflicts. The results of these clearly indicate that the structure does not only make the product development easier, but also makes them much more maintainable and faster to deliver standardized yet customizable banking solutions.