A data hierarchical management system and method based on a bank customer information model

Abstract

The application provides a data hierarchical management system and method based on a bank customer information model, which comprises a back management service module, a core service interface module, a database mapping service module, an image file storage service module, a back management database and a core service database, the back management service module is used for managing users, data dictionaries, data, departments, logs and timing tasks, the core service interface module is connected with the back management service module and is used for providing a functional interface to the back management service module, the back management database and the core service database are respectively used for storing background management data and test data, the database mapping service module is used for operating the database in an API mode, and the image file storage service module is used for storing image files generated in data construction on a server. The application guarantees that test personnel and test automation scripts can quickly find test data meeting test requirements, and reduces the time and difficulty of test data construction.

Description

Technical Field

[0001] This invention relates to the field of software system development technology, and more specifically, to a data hierarchical management system and method based on a bank customer information model. Background Technology

[0002] With the continuous growth of banking business, system requirements are constantly increasing and version iterations are frequent. Taking Jiangsu Suning Bank as an example, there is a minor version every week and a major version every three weeks. With the delivery cycle becoming shorter and faster, the delivery quality still needs to be guaranteed.

[0003] Currently, during version testing at most banks, test data is primarily constructed manually. Manually constructing test data requires preparing account opening elements such as customer name, mobile phone number, customer ID number, and images. This process is time-consuming, has a long preparation cycle, and involves high repetition, severely impacting testing efficiency. Most non-essential elements are left blank, resulting in incomplete test data and potential quality risks. Furthermore, the test data generated over a significant period lacks full lifecycle management, quickly becoming obsolete and difficult for others to reuse.

[0004] Furthermore, due to differences in communication protocols, test construction methods, and banking business data models, there is currently no universally applicable and mature solution of its kind on the market. Moreover, integration and customization require a long development cycle and significant additional learning costs, failing to meet the management requirements of business test data. Other banks of similar types have similar solutions, but these solutions are deeply coupled with the business logic of the bank's transaction system and cannot be adjusted according to actual circumstances. As business grows and system complexity increases, maintainability deteriorates, bringing significant risks and costs to overall test data management. Summary of the Invention

[0005] In view of the above problems, the present invention provides a data layered management system and method based on a bank customer information model, which ensures that testers and test automation scripts can quickly find test data that meets testing requirements, and reduces the time and difficulty of test data construction.

[0006] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is: a data hierarchical management system based on a bank customer information model, including a back-end management service module, a core service interface module, a database mapping service module, an image file storage service module, a back-end management database, and a core service database. The back-end management service module is used to manage users, data dictionaries, data, departments, logs, and scheduled tasks. The core service interface module is connected to the back-end management service module and is used to provide functional interfaces for various system services within the bank to the back-end management service module. The back-end management database and the core service database are used to store back-end management data and test data, respectively. The database mapping service module is connected to the back-end management database and the core service database and is used to operate the database using API. The image file storage service module is connected to the core service interface module and is used to store image files generated during data construction on the server.

[0007] As a preferred embodiment, the test data includes a customer data layer, an account data layer, a product data layer, and a customization data layer constructed sequentially from bottom to top, with each layer of data relying on the data of the previous layer to complete its construction.

[0008] This invention also provides a data layering management method based on a bank customer information model, running on the data layering management system based on the bank customer information model as described above, including the following steps: acquiring user data and dividing the user data into multiple data layers, including a customer data layer, an account data layer, a product data layer, and a customized data layer; sorting out the interfaces to be called for each data layer and the element information required by the interfaces; establishing the configuration information of the test environment and the corresponding data pool threshold; periodically comparing the remaining data in the data pool with the threshold, and if it is lower than the threshold, supplementing the data pool with test data based on the data layer; after each end-of-day batch task accounting day switch, the status of the test data is periodically reverse-synchronized from the test environment daily.

[0009] As a preferred embodiment, the construction of the customer data layer includes: automatically generating customer names and ID card information using a Fake toolset, then using code to recognize the ID card to complete other customer information, and automatically generating image files; the construction of the account data layer includes: randomly obtaining customer information from the customer data layer to open accounts; the construction of the product data layer includes: obtaining data from the customer data layer and / or the account data layer to construct product data; the construction of the customized data layer includes: calling the customer data layer, account data layer, or product data layer for the creation and deployment of business dashboards, and constructing specific test data files.

[0010] As a preferred option, the configuration information for establishing the test environment and the corresponding data pool thresholds include: based on the Java HashMap built-in cache Encache technology, the addresses, parameters and running thresholds of different test environments are pre-configured in the form of a page list, and then converted into key-value pairs by code and written to the cache for real-time invocation.

[0011] As a preferred embodiment, the step of supplementing test data to the data pool based on the data layer includes: generating a scheduled task based on customer information, configuring the upper and lower limits of the pre-generated data and the test environment, and periodically supplementing test data after the scheduled task is triggered.

[0012] As a preferred embodiment, the test data status is reverse-synchronized from the test environment daily at regular intervals, including: obtaining the latest status of product data based on a scheduled task, querying the status of the core service database through the core service interface module, and reversing the synchronization to the back-end database.

[0013] As a preferred option, the following method is also provided: if a tester selects any test data and clicks "claim", all customer, account, and product data associated with that test data will be attributed to that tester.

[0014] As a preferred option, it also includes: using the Apache Echart open-source framework, the Bootstrap 3 adaptive front-end framework, and the database to display the total amount of data in the data pool, the amount of data used, and the amount of data remaining.

[0015] Compared with existing technologies, the beneficial effects of this invention include: by simulating bank customer information and adopting a data hierarchical management model, it can meet the test data needs of different levels; the test data status is updated in reverse on a regular basis, allowing selection of the required test data based on the latest status; the end-of-day batch planned execution management task solves the maintenance problem of different statuses of loan product data, meeting the needs of special data such as overdue, non-accrued, and write-off data; the isolation capability after test data is requisitioned ensures that test data is not damaged or interfered with; the test environment information is grouped and managed, allowing for quick access to new test environments through configuration, meeting the test data management capabilities of different test environments; the query management of existing test environment data, with the platform automatically generating data query and data query interface services, can meet the data usage needs of testers and test automation scripts for different functions, achieving maximum reuse of test data assets; test data threshold management monitors the generation, inventory, and usage of test data at different levels, automatically initiating data generation tasks at the relevant level once the threshold is reached; and test data statistical display management calculates and adjusts the generation of data at different levels based on data usage, avoiding the impact of excessive redundant test data on the test environment. This invention solves the problems of high complexity, poor completeness, and low timeliness of traditional manually constructed test data. It also addresses the issues of deep coupling between loan product test data and the business logic of bank transaction systems, lack of full lifecycle management, and difficulty in maintaining test data. Attached Figure Description

[0016] The disclosure of this invention is illustrated with reference to the accompanying drawings. It should be understood that the drawings are for illustrative purposes only and are not intended to limit the scope of protection of this invention. In the drawings, the same reference numerals are used to refer to the same parts. Wherein:

[0017] Figure 1 This is a schematic diagram of the data hierarchical management system according to an embodiment of the present invention;

[0018] Figure 2 This is a flowchart illustrating the data hierarchical management method according to an embodiment of the present invention. Detailed Implementation

[0019] It is readily understood that, based on the technical solution of this invention, those skilled in the art can propose various interchangeable structural methods and implementations without altering the essential spirit of the invention. Therefore, the following detailed embodiments and accompanying drawings are merely illustrative examples of the technical solution of this invention and should not be considered as the entirety of the invention or as limitations or restrictions on the technical solution of this invention.

[0020] According to one embodiment of the present invention, Figure 1As shown, a data hierarchical management system based on a bank customer information model includes a back-end service module, a core service interface module, a database mapping service module, an image file storage service module, a back-end database, and a core service database.

[0021] 1. Back-end management service module

[0022] This module primarily provides user management, data dictionary management, data management, department management, and scheduled task management functions through a page-based management interface.

[0023] 2. Core Service Interface Module

[0024] This module conforms to the RESTful specification and is based on the HTTP protocol to develop various functional interfaces for back-end management services to call, such as bank APP registration / real-name interface, bank counter operation interface, and public / private credit data construction interface.

[0025] 3. Database mapping service module

[0026] This module is based on the open-source framework Magic-API, which exposes database operations during development as APIs for use by developers, greatly improving development efficiency and reducing maintenance costs.

[0027] 4. Image file storage service

[0028] This module stores the image files generated during data construction as files on the server, isolating the image files from the test data construction platform. This aims to facilitate file management and improve the access efficiency of the test data construction platform.

[0029] In this embodiment of the invention, the back-end management service module is used to manage users, data dictionaries, data, departments, logs, and scheduled tasks. The core service interface module is connected to the back-end management service module and is used to provide the back-end management service module with functional interfaces for various system services within the bank. The back-end management database and the core service database are used to store back-end management data and test data, respectively. The database mapping service module is connected to the back-end management database and the core service database and is used to operate on the database using API. The image file storage service module is connected to the core service interface module and is used to store the image files generated during data construction on the server.

[0030] Specifically, the test data includes customer data layer, account data layer, product data layer and customized data layer constructed from bottom to top, and each layer of data depends on the data of the previous layer to complete the construction.

[0031] See Figure 2The present invention also provides a data hierarchical management method based on a bank customer information model, which runs on the above-mentioned data hierarchical management system based on a bank customer information model, and includes the following steps:

[0032] S101, acquire user data and divide the user data into multiple data layers, including customer data layer, account data layer, product data layer and customized data layer.

[0033] Specifically, the construction of the customer data layer includes: automatically generating customer names and ID card information through a Fake toolset, then using code to recognize the ID card to complete other customer information, and automatically generating image files (ID photos).

[0034] The construction of the account data layer includes: randomly retrieving customer information from the customer data layer to open accounts. This establishes a certain correlation between the data in this layer and the customer data layer, such as bank app registration / real-name account opening.

[0035] The construction of the product data layer includes: acquiring data from the customer data layer and / or account data layer based on product characteristics, and constructing product data. For example: obtaining customer information from the customer data layer, using the customer information as part of the parameters to call the corresponding product data construction interface, conducting loan-related credit business, thereby producing product data for the required credit type.

[0036] The construction of a customized data layer includes: calling the customer data layer, account data layer, or product data layer for the creation and deployment of business dashboards, and constructing specific test data files. For example: retrieving specified data from the customer data layer to create a blacklist dashboard; retrieving account information data from the account data layer to deploy a business credit / credit usage dashboard; and retrieving credit / credit usage data from the product data layer to generate accounting files for specific scenarios. A dashboard simulates a request to a third party and returns a response, primarily addressing testing needs in special scenarios.

[0037] S102, sort out the interfaces that need to be called for each data layer construction, as well as the element information required by the interfaces.

[0038] S103, Establish the configuration information for the test environment and the corresponding data pool threshold.

[0039] Specifically, the configuration information for the test environment and the corresponding data pool thresholds are established. This includes: based on JavaHashMap's built-in cache Encache technology, the addresses, parameters, and running thresholds of different test environments are pre-configured in the form of a page list, and then converted into key-value pairs by code and written to the cache for real-time invocation. Because it is directly stored in memory, it can be used immediately after configuration.

[0040] S104 periodically compares the remaining data in the data pool with a threshold. If the data falls below the threshold, test data is added to the data pool based on the data layer. Alternatively, testers can manually perform reverse synchronization of a specific data entry to ensure that the test data status in the management system is consistent with the test environment.

[0041] Specifically, test data is added to the data pool based on the data layer, including: generating scheduled tasks based on customer information, configuring the upper and lower limits of pre-generated data and the test environment, and periodically supplementing test data after the scheduled task is triggered.

[0042] For example: Scheduled task for generating customer information data.

[0043] The command `(genUserInfoTask.checkFakeUserCount(3L,'500','1000','Env1'))` configures the lower and upper limits of the pre-generated data and the test environment. The runtime CRON expression `(0 / 10****?)` represents triggering once every 10 seconds. Manually triggering data generation simply means manually triggering the scheduled task once.

[0044] S105: After each end-of-day batch task accounting day switch, the test data status is reverse-synchronized from the test environment on a daily schedule.

[0045] It should be understood that the term "end-of-day batch task accounting date" encompasses the meanings of "batch," "end-of-day batch," and "accounting date." Batch refers to daily or month-end processing for accounting tasks such as accruing deposit / loan interest, expense accruals, and report preparation. End-of-day batch essentially marks the end of a logical day. Accounting date is the monthly closing date designated by finance personnel. For example, if the closing date is the 5th of each month, the accounting date is the 5th of each month; accounts receivable after the 5th are carried over to the next month. Note that this differs from the common understanding of closing on the last day of the month.

[0046] Specifically, the test data status is reverse-synchronized from the test environment daily on a scheduled basis, including: obtaining the latest status of product data based on scheduled tasks, querying the status of the core service database through the core service interface module, and then reversing the synchronization to the back-end database.

[0047] In this embodiment of the invention, the method further includes: when a tester selects any piece of test data and clicks "claim," all customer, account, and product data associated with that test data will be attributed to that tester. The data management system periodically acquires existing data generated by non-management systems and provides it to all personnel for querying and use.

[0048] Once test data is claimed, it is isolated to ensure it is not corrupted or interfered with. Isolation means that the data owner's data is not visible to other users within a specified environment. This functionality is achieved through the Shiro permission framework and custom SQL statements. For example, when a tester clicks to claim user A in the ENV1 environment, the backend code synchronizes the owner field of all data tables involving user A to user A. Through Shiro permission filtering, other testers will then be unable to see any information related to user A (except for the super administrator).

[0049] In this embodiment of the invention, it also includes: using the Apache Echart open-source framework, the Bootstrap3 adaptive front-end framework, and the database, a test data dashboard is used to display the total amount of data, the amount of data used, and the amount of data remaining in the data pool.

[0050] In summary, the beneficial effects of this invention include: by simulating bank customer information and adopting a data hierarchical management model, it can meet the test data needs of different levels; the test data status is updated in reverse on a regular schedule, allowing selection of the required test data based on the latest status; the end-of-day batch planned execution management task solves the maintenance problem of different statuses of loan product data, meeting the needs of special data such as overdue, non-accrued, and write-off data; the isolation capability after test data is requisitioned ensures that test data is not damaged or interfered with; the test environment information group management allows for quick access to new test environments through configuration, meeting the test data management capabilities of different test environments; the query management of existing test environment data, with the platform automatically generating data query and data query interface services, can meet the data usage needs of testers of different functions and test automation scripts, achieving maximum reuse of test data assets; test data threshold management monitors the generation, inventory, and usage of test data at different levels, automatically initiating data generation tasks at the relevant level once the threshold is reached; and test data statistical display management calculates and adjusts the generation of data at different levels based on data usage, avoiding the impact of excessive redundant test data on the test environment.

[0051] This invention solves the problems of high complexity, poor completeness, and low timeliness of traditional manually constructed test data. It also addresses the issues of deep coupling between loan product test data and the business logic of bank transaction systems, lack of full lifecycle management, and difficulty in maintaining test data.

[0052] It should be understood that if the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0053] The technical scope of this invention is not limited to the content described above. Those skilled in the art can make various modifications and variations to the above embodiments without departing from the technical concept of this invention, and all such modifications and variations should fall within the protection scope of this invention.

Claims

1. A data hierarchical management method based on a bank customer information model, running on a data hierarchical management system based on a bank customer information model, characterized in that, Includes the following steps: Acquire user data and divide the user data into multiple data layers, including a customer data layer, an account data layer, a product data layer, and a customization data layer; Organize the interfaces that need to be called for each data layer construction, as well as the element information required by the interfaces; Establish the configuration information for the test environment, as well as the corresponding data pool thresholds; Periodically compare the remaining data in the data pool with the threshold. If the data is lower than the threshold, supplement the data pool with test data based on the data layer. After each end-of-day batch task accounting day switch, based on the test data status, reverse synchronization is performed daily from the test environment at regular intervals. The data hierarchical management system based on the bank customer information model includes a back-end management service module, a core service interface module, a database mapping service module, an image file storage service module, a back-end management database, and a core service database. The back-end management service module is used to manage users, data dictionaries, data, departments, logs, and scheduled tasks. The core service interface module is connected to the back-end management service module and is used to provide functional interfaces for various system services within the bank. The back-end management database and the core service database are used to store back-end management data and test data, respectively. The database mapping service module is connected to the back-end management database and the core service database and is used to operate on the database using APIs. The image file storage service module is connected to the core service interface module and is used to store image files generated during data construction on the server. The test data includes a customer data layer, an account data layer, a product data layer, and a customized data layer constructed from bottom to top, with each layer of data relying on the data of the previous layer to complete its construction; The construction of the customer data layer includes: automatically generating customer names and ID card information using a Fake toolset, then using code to recognize the ID card to complete other customer information and automatically generating image files; the construction of the account data layer includes: randomly obtaining customer information from the customer data layer to open accounts; the construction of the product data layer includes: obtaining data from the customer data layer and / or the account data layer to construct product data; the construction of the customized data layer includes: calling the customer data layer, account data layer, or product data layer for the creation and deployment of business dashboards and constructing specific test data files.

2. The data hierarchical management method based on a bank customer information model according to claim 1, characterized in that, The configuration information for establishing the test environment, and the corresponding data pool thresholds, include: Based on Java HashMap's built-in caching Encache technology, the addresses, parameters, and running thresholds for different test environments are pre-configured in the form of a page list, and then converted into key-value pairs by code and written to the cache for real-time invocation.

3. The data hierarchical management method based on a bank customer information model according to claim 1, characterized in that, The process of supplementing test data to the data pool based on the data layer includes: generating scheduled tasks based on customer information, configuring upper and lower limits of pre-generated data and the test environment, and periodically supplementing test data after the scheduled task is triggered.

4. The data hierarchical management method based on a bank customer information model according to claim 1, characterized in that, Based on the test data status, reverse synchronization is performed daily from the test environment, including: obtaining the latest status of product data based on a scheduled task, querying the status of the core service database through the core service interface module, and then reversing the synchronization to the back-end database.

5. The data hierarchical management method based on a bank customer information model according to claim 1, characterized in that, Also includes: When a tester selects any test data and clicks "claim," all customer, account, and product data associated with that test data will be attributed to that tester.

6. The data hierarchical management method based on a bank customer information model according to claim 1, characterized in that, Also includes: Using the Apache Echart open-source framework, the Bootstrap 3 adaptive front-end framework, and a database, this tool displays the total amount of data in the data pool, the amount of data used, and the amount of data remaining.

Images