ImpactU Versión 3.11.2 Última actualización: Interfaz de Usuario: 16/10/2025 Base de Datos: 29/08/2025 Hecho en Colombia
Diseñar un sistema de escalamiento de clientes en un sistema bancario, basado en la aplicación de la norma ISO/IEC 20000:2011, y Scrum en la ciudad de Bogotá
This project was carried out through a work plan and a diagnosis, which provides us with the information for its development.By means of business area requirements, it tells us the business rules of how the customer, product and balance count should be performed. The main dimension of the system in all cases is the person table where the customer is identified by the document type and the identification number (TIP_DOC_ID, NUM_DOC_ID), so each customer will have a single record in the final table. As the different sources are read to each of the products it is concatenated cod_product and cod_subprodu to assign a code that identifies the product. It is important to note that for each of them the following are defined: Measures the number of products (contract or accounts) in which the customer is listed as the contract holder. Stores the balance with which I close the end of the day or month. In the case of Savings account whatever has the closure. Indicates whether or not the customer owns the product as the contract holder (independent of the number of contracts or accounts). for the IVC count,the following will be taken into account for the savings product and credit card. The savings product will be divided into three products: savings, destination savings and nomina, for counting will be counted as a single product. The credit card product is divided into visa, master and private, the count for the count will be counted as a single product. For tenure, the proceeds of funds will not be counted.