Data asset management method and device based on functional business perspective, and medium

Abstract

The invention provides a data asset management method and device based on a functional service perspective, and a medium. The method comprises the following steps: determining an item list of a functional service; performing data resource planning from the perspective of functional business to obtain a data resource planning result; stock data exploration is carried out from the bottom database side, and a data exploration result is obtained; and comparing and associating the data resource planning result with the data investigation result to form a data account book for data asset management. The invention provides a data asset management method based on a functional business perspective, and the method can be used for the governance management of local data assets, the exploration, the sorting of possible or generated data assets according to the actual business of each department, and the association matching with the actual data in a database. And a data architecture and a data asset atlas corresponding to the business are explored and established, so that subsequent management application is facilitated.

Description

Technical Field

[0001] The present application relates to the technical field of data resource management, and in particular to a data asset management method, device and medium based on a functional business perspective. Background Art

[0002] Digital transformation often requires the efficient governance of data first, and more importantly, the asset management of data.

[0003] As a new production factor, data should be well managed, whether it is needed for business production guidance of enterprises and institutions or as an asset for subsequent factorized transactions. Data resource management is a management activity that uses information system technologies such as database management, data warehouses, and other data management tools to complete organizational data resource management tasks and meet the information needs of corporate shareholders.

[0004] The domestic data governance framework is mainly based on the DCMM (Data Management Capability Maturity Model), which includes eight core areas: data strategy, data governance, data architecture, data standards, data quality, data security, data application, and data life cycle. It focuses on the data management process and methods, and is a reference standard for domestic enterprises to manage data. The existing data asset management method points out that data assets should be managed comprehensively, scientifically, and effectively, including data asset registration, classification management, quality management, security management, application management, auditing and evaluation. However, the existing data governance theory or data asset management method mainly focuses on the management process and methods, and often underestimates the first step of data source. Some data management governance platforms have been built, but it is difficult to integrate into the original business system. Even some small enterprises have no concept of data asset management. Summary of the invention

[0005] The technical problem to be solved by this application is to provide a data asset management method, device and medium based on a functional business perspective in order to solve the problems existing in the prior art in view of the above-mentioned deficiencies in the prior art.

[0006] In a first aspect, the present application provides a data asset management method based on a functional business perspective, the method comprising:

[0007] S1. Determine the list of functional business matters;

[0008] S2. Carry out data resource planning from the functional business perspective and obtain data resource planning results;

[0009] S3. Conduct a data survey on the underlying database to obtain the data survey results.

[0010] S4. Compare and associate the data resource planning results with the data investigation results to form a data ledger for data asset management.

[0011] In some embodiments, S1 includes:

[0012] According to the metadata framework of business matters, the stock documents related to functions are processed and model training on function data is carried out;

[0013] Fine-tune the model instructions and perform word prediction on the trained model, convert the job function text and fill it into the function data framework;

[0014] Proofread and complete based on the functional data framework to obtain a list of items for the functional business.

[0015] In some embodiments, S2 includes:

[0016] Obtain at least one of the existing metadata, data items, source systems, system-owned departments, and data owners from the internal data management system, and save it to the database;

[0017] Match the data metadata and corresponding information items in the database to each department and specific functions according to department affiliation, data domain affiliation, and data owner;

[0018] Verify the functions that have not generated data or cannot match data, and supplement system information and metadata information of expected data.

[0019] In some embodiments, S3 includes:

[0020] Obtain system information, library table field information, library table comments, and field comments for the entire system;

[0021] For the functional data that has been successfully associated with the metadata related to the internal system, import the relevant metadata information;

[0022] For the resource planning data generated by the verification, the table and column information crawled from the database are summarized and matched with the corresponding functional business;

[0023] Automatically score the successfully matched functional data to generate a matching degree;

[0024] For the remaining system library table data that does not correspond to specific functions, they are manually classified or placed in separate columns according to the data source or annotations.

[0025] In some embodiments, S4 includes:

[0026] Preliminary matching of functional business: by comparing core information items, matching the core data fields of the database table with the business items of the resource planning results, and establishing the relationship between data and functional business;

[0027] According to the relationship between data and functional business, the data catalog and various element information are supplemented and improved to form a data ledger catalog;

[0028] For each data resource included in the data ledger directory, supplement the responsibility attribute information.

[0029] In some embodiments, it also includes:

[0030] S5. Based on the data ledger, determine the data update and maintenance mechanism and various management responsibilities, and establish a data asset management system.

[0031] In some embodiments, S5 includes:

[0032] Determine the main processes for data updating, maintenance, development and utilization, as well as the evaluation factors for data resource quality;

[0033] According to the needs of data management, establish a division of labor and cooperation mechanism among departments, and determine the dynamic update and maintenance system of data and catalogs;

[0034] A data asset management system for dynamically managing data asset ledgers should be developed simultaneously according to scale requirements.

[0035] In a second aspect, the present application provides a data asset management device based on a functional business perspective, the device comprising:

[0036] A task list determination module, which is configured to determine the task list of functional business;

[0037] A data resource planning module is configured to perform data resource planning from a functional business perspective and obtain data resource planning results;

[0038] The stock data survey module is configured to conduct a stock data survey from the underlying database side to obtain data survey results;

[0039] A comparison and association module is configured to compare and associate the data resource planning results with the data survey results to form a data ledger for data asset management.

[0040] In a third aspect, the present application provides a data asset management device based on a functional business perspective, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to implement the data asset management method based on a functional business perspective described in the first aspect above.

[0041] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the data asset management method based on a functional business perspective as described in the first aspect above is implemented.

[0042] The data asset management method, device and medium based on the functional business perspective provided in this application include: determining a list of functional business matters; performing data resource planning from the functional business perspective to obtain data resource planning results; conducting a stock data survey from the bottom database side to obtain data survey results; comparing and associating the data resource planning results with the data survey results to form a data account book for data asset management. This application provides a data asset management method based on the functional business perspective, which establishes a global data resource planning and management framework based on the idea of ​​functional business management, combs the stock data according to the business data framework, adopts a combination of top-down and bottom-up methods, and uses a large training model to comb and match text information to build a data asset maintenance management system. This application can be used for the governance and management of local data assets, explores the data assets that may be generated or have been generated according to the actual business of each department, and associates and matches them with the actual data in the database, explores the establishment of a data architecture and data asset map corresponding to the business, and facilitates subsequent management applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0044] Figure 1 A flowchart of a data asset management method based on a functional business perspective provided in an embodiment of the present application;

[0045] Figure 2 A schematic diagram of a list of items for determining functional business provided in an embodiment of the present application;

[0046] Figure 3 A schematic diagram of data resource planning provided in an embodiment of the present application;

[0047] Figure 4 A schematic diagram of conducting a stock data survey provided in an embodiment of the present application;

[0048] Figure 5 A flowchart of another data asset management method based on a functional business perspective provided in an embodiment of the present application;

[0049] Figure 6 A schematic diagram of the structure of a data asset management device based on a functional business perspective provided in an embodiment of the present application;

[0050] Figure 7 A schematic diagram of the structure of another data asset management device based on a functional business perspective provided in an embodiment of the present application.

[0051] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0052] In order to enable those skilled in the art to better understand the technical solution of the present application, the implementation mode of the present application will be further described in detail below with reference to the accompanying drawings.

[0053] It should be understood that the specific embodiments and drawings described herein are only used to explain the present application, rather than to limit the present application.

[0054] It can be understood that, in the absence of conflict, the various embodiments in the present application and the various features in the embodiments can be combined with each other.

[0055] It can be understood that, for the convenience of description, the drawings of the present application only show the parts related to the present application, while the parts unrelated to the present application are not shown in the drawings.

[0056] It can be understood that each unit and module involved in the embodiments of the present application may correspond to only one physical structure, or may be composed of multiple physical structures, or multiple units and modules may be integrated into one physical structure.

[0057] It can be understood that the terms "first", "second", etc. in the embodiments of the present application are used to distinguish different objects, or to distinguish different processing of the same object, rather than to describe a specific order of objects.

[0058] It is understandable that, in the absence of conflict, the functions and steps marked in the flowcharts and block diagrams of the present application may occur in an order different from that marked in the drawings.

[0059] It is understood that the flowcharts and block diagrams of the present application illustrate the possible architectures, functions, and operations of the systems, devices, equipment, and methods according to the various embodiments of the present application. Among them, each box in the flowchart or block diagram may represent a unit, module, program segment, code, which contains executable instructions for implementing the specified functions. Moreover, each box or combination of boxes in the block diagram and flowchart may be implemented by a hardware-based system that implements the specified functions, or by a combination of hardware and computer instructions.

[0060] It can be understood that the units and modules involved in the embodiments of the present application can be implemented by software or hardware, for example, the units and modules can be located in a processor.

[0061] Existing data governance theories or data asset management methods mainly focus on the management process and methods, and often neglect the data source in the first step. Relying on existing theoretical methods, many units often find it difficult to get started due to poor information technology foundation, high governance costs, and insufficient data awareness. Some units have built data management and governance platforms, but they are difficult to integrate into the original business system, aggravating data fragmentation, or focusing on data movement and quality management, ignoring the linkage with business production, resulting in management and business ends not even knowing that there is a "gold mine" of data, or not knowing its "gold content", making it difficult to jointly analyze data to support the digital transformation of the enterprise. Even some small enterprises have no concept of data asset management.

[0062] The idea of ​​this application is mainly to start from the global functional business, to associate and match with the enterprise data resources, without relying on or binding to the information system, to build an internal data asset management system at a relatively low cost, covering the business and technical departments, and forming a dynamically updated data asset "one account", which is convenient for the company's subsequent data governance and joint analysis applications.

[0063] This application proposes a data asset management method based on a functional business perspective, mainly exploring solutions to the problems of unclear internal data accounts and chaotic management in enterprises and institutions (especially cross-domain and multi-business enterprises) under the background of digital transformation, and providing enterprises and institutions with a data management approach that includes business, data, and service objects. In this process, relevant management and maintenance responsibilities are clarified to facilitate the implementation of data management work.

[0064] This application specifically includes the following steps: sorting out and establishing a functional business list, planning a data resource framework, surveying existing data, building a data map through correlation matching, and improving a data management and maintenance mechanism based on business functions.

[0065] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0066] The present application provides a data asset management method based on a functional business perspective. The work processing flow of the method can be implemented through electronic devices, such as computers, handheld smart terminals, etc. For the convenience of explanation, the embodiments of the present application are described with the method execution subject being a computer.

[0067] Figure 1 A schematic diagram of a data asset management method based on a functional business perspective provided in an embodiment of the present application, such as Figure 1 As shown, the present application provides a data asset management method based on a functional business perspective, the method includes S1-S4, which are as follows:

[0068] S1. Determine the list of functional business matters;

[0069] In some embodiments, S1 includes:

[0070] According to the metadata framework of business matters, the stock documents related to functions are processed and model training on function data is carried out;

[0071] Fine-tune the model instructions and perform word prediction on the trained model, convert the job function text and fill it into the function data framework;

[0072] Proofread and complete based on the functional data framework to obtain a list of items for the functional business.

[0073] Specifically, Figure 2 A schematic diagram of a list of items for determining functional business provided in an embodiment of the present application, such as Figure 2 As shown, this step is mainly for the business department to sort out functional business matters.

[0074] In this step, the business matters of the performance of duties are sorted out. According to the authority, exercising subject, operation process, corresponding responsibilities, etc. of each department, a "function-business-matters" framework system is systematically constructed as the basis for the overall situation of data resources generated, collected and managed for the subsequent development of various businesses and execution of various matters. The sorting content includes the name of the function, the name of the business, the name of the matter, the field to which it belongs, the description of the business matter, the type of business matter, the management service object, the responsible department, etc.

[0075] The steps of combing are as follows:

[0076] 1. Based on the specified business metadata framework, relying on the industry's pre-trained NLP algorithms and LLM models, process the stock documents related to the functions, split the text, convert word vectors (Word2Vec), and strengthen the model training in terms of function data;

[0077] 2. Fine-tune the model instructions, use Transformer to predict words, and convert the job function text into the set function data framework;

[0078] 3. Proofread and complete on this basis to form a functional business data list;

[0079] 4. Solidify the enhanced model, automatically generate and update the functional business data framework based on the subsequent continuous input documents, and then equip it with relevant workflows for review and confirmation. At the same time, establish a log table in the database to record update and maintenance records.

[0080] S2. Carry out data resource planning from the functional business perspective and obtain data resource planning results;

[0081] In some embodiments, S2 includes:

[0082] Obtain at least one of the existing metadata, data items, source systems, system-owned departments, and data owners from the internal data management system, and save it to the database;

[0083] Match the data metadata and corresponding information items in the database to each department and specific functions according to department affiliation, data domain affiliation, and data owner;

[0084] Verify the functions that have not generated data or cannot match data, and supplement system information and metadata information of expected data.

[0085] Specifically, Figure 3 A schematic diagram of data resource planning provided in an embodiment of the present application is shown in FIG. Figure 3 As shown, this step is mainly carried out by the business department to carry out system data resource planning.

[0086] In this step, data resource planning is to sort out the data resources that should be generated, collected and managed from the perspective of functional business, and clarify the overall layout of data resources. For each item sorted out in the previous step, a summary description of the data resources generated, collected and managed is given, and combined with the actual situation of the business work, the supporting system platform used and the key information items involved that can characterize the important performance process and results of the business items are sorted out, and the key information items of the business items are clarified as the main basis for the subsequent selection of appropriate information items from the database table to associate with the business and data resources. New sorting content based on step S1 includes system name, data name, and information item.

[0087] Specific sorting steps:

[0088] 1. Obtain existing metadata, data items, source systems, system departments, data owners, and other information from internal data management systems (such as Data Cube, Data Sharing, Data Lake Hive, and Waterdrop), and establish database tables for storage;

[0089] 2. Write scripts to match the data metadata and corresponding information items recorded in the system dictionary to various departments and specific functions according to department ownership, data domain ownership, data owner and other information;

[0090] 3. Verify the functions that have not generated data or cannot match data, and supplement the system information and metadata information of expected data;

[0091] S3. Conduct a data survey on the underlying database to obtain the data survey results.

[0092] In some embodiments, S3 includes:

[0093] Obtain system information, library table field information, library table comments, and field comments for the entire system;

[0094] For the functional data that has been successfully associated with the metadata related to the internal system, import the relevant metadata information;

[0095] For the resource planning data generated by the verification, the table and column information crawled from the database are summarized and matched with the corresponding functional business;

[0096] Automatically score the successfully matched functional data to generate a matching degree;

[0097] For the remaining system library table data that does not correspond to specific functions, they are manually classified or placed in separate columns according to the data source or annotations.

[0098] Specifically, Figure 4 A schematic diagram of conducting a stock data survey provided in an embodiment of the present application, such as Figure 4 As shown, this step is mainly carried out by the data technology department to trace the existing data.

[0099] In this step, the data technology department sorts out the information system platforms and database table contents that support business work, completely constructs the actual correspondence between "system-library table-information items", and clarifies the basic situation of the data resources accumulated by each system platform. The main steps are: collect the previous system platform lists and data resource sorting results, and grasp the basic status of data resource construction. Comprehensively collect normative documents generated during the development of relevant application systems of the department to support the data resource survey. Sort out the database tables of each system one by one, and according to the business items carried by the system and its work content for management service objects, extract the important data fields in the library table that can represent the execution process and results of each business item, and construct a data list with organic connections between "system-library table-core information items". According to the actual situation of data resources, standardize and completely collect the contents of elements such as information resource name, information resource summary, data level, data area range, data time range, etc. The specific sorting steps are as follows:

[0100] 1. Capture the system information, library table field information, library table comments, and field comments of the entire system;

[0101] 2. For the functional data that has been successfully associated with the internal system-related metadata in the previous step, further import relevant metadata information, such as data resource summary, level, data area range, time range and other elements.

[0102] 3. For the resource planning data generated by the verification, the table and column information crawled from the database are summarized with the help of language models to match the corresponding functional business;

[0103] 4. Automatically score the successfully matched functional data in step 3 to generate a matching degree for verification reference;

[0104] 5. For the remaining system library table data that do not correspond to specific functions, they should be manually classified or placed in separate columns according to their sources, comments, etc.

[0105] S4. Compare and associate the data resource planning results with the data investigation results to form a data ledger for data asset management.

[0106] In some embodiments, S4 includes:

[0107] Preliminary matching of functional business: by comparing core information items, matching the core data fields of the database table with the business items of the resource planning results, and establishing the relationship between data and functional business;

[0108] According to the relationship between data and functional business, the data catalog and various element information are supplemented and improved to form a data ledger catalog;

[0109] For each data resource included in the data ledger directory, supplement the responsibility attribute information.

[0110] In this step, the coordination department is mainly responsible for the correlation and optimization of the data catalog. This step is to correlate and optimize the results of data resource planning and data investigation to form a data "one account" (data account book) with a complete description of data resource characteristics, which is convenient for searching, locating and acquiring data resources, and better supporting data joint analysis and development and utilization. This link is mainly carried out by manual comparison and sorting. The main process of this step includes:

[0111] 1. Preliminary comparison and matching of functional business, compare the core information items of the above two links, match the core data fields of the database table with the business items of the resource planning results, and accurately establish the relationship between "data-functional business".

[0112] 2. The coordinating department takes the lead, and the data technology department and the business department jointly confirm and improve the results of the data resource sorting, and study and confirm the cases where the resource planning and data survey results fail to be successfully associated and matched. For the successful matching of data resource planning and actual data resources, the data technology department and the business department need to jointly confirm the accuracy of the "data-business matters" matching results and the correctness of the content of each element, and further optimize and improve the sorting results of the overall business framework and the overall data framework.

[0113] 3. Based on the results of correlation comparison and sorting and confirmation, supplement and improve the data directory and various element information to form a "one-book" directory of data.

[0114] 4. Supplement and improve the responsibility attribute information of data resources. For each data resource included in the data catalog, supplement and improve various types of responsibility attribute information, including data sharing authority control, update and maintenance responsibilities, quality and safety management responsibilities, etc.

[0115] Figure 5 Another schematic diagram of the data asset management method based on the functional business perspective provided in the embodiment of the present application is as follows: Figure 5 As shown, the present application provides a data asset management method based on a functional business perspective, the method also includes:

[0116] S5. Based on the data ledger, determine the data update and maintenance mechanism and various management responsibilities, and establish a data asset management system.

[0117] In some embodiments, S5 includes:

[0118] Determine the main processes for data updating, maintenance, development and utilization, as well as the evaluation factors for data resource quality;

[0119] According to the needs of data management, establish a division of labor and cooperation mechanism among departments, and determine the dynamic update and maintenance system of data and catalogs;

[0120] A data asset management system for dynamically managing data asset ledgers should be developed simultaneously according to scale requirements.

[0121] In this step, the coordinating department is mainly responsible for improving the data asset management mechanism. This step focuses on the data "one account" directory, clarifies the data update and maintenance mechanism and various management responsibilities, and improves the relevant management system of data assets. The main processes of this step include:

[0122] 1. Establish standards to clarify the main processes for data updating, maintenance, development and utilization, and the evaluation factors for data resource quality.

[0123] 2. Improve the system rules, improve the data responsibility management system, establish a division of labor and cooperation mechanism among departments according to data management needs, and clarify the dynamic update and maintenance system of data and catalogs.

[0124] 3. Based on the scale requirements, a data asset management system can be developed simultaneously to dynamically manage the data asset "one account" directory.

[0125] This application provides a data asset management method based on the functional business perspective, relying on the idea of ​​functional business management to establish a global data resource planning and management framework, sorting out the stock data according to the business data framework, using a combination of top-down and bottom-up methods, and using the training of large models to sort out and match text information, and build a data asset maintenance management system. This application can be used for the governance and management of local data assets, exploring the sorting of data assets that may be generated or have been generated according to the actual business of each department, and associating and matching them with the actual data in the database, exploring the establishment of a data architecture and data asset map corresponding to the business, to facilitate subsequent management applications.

[0126] It should be understood that, although the various steps in the flowcharts in the above-described embodiments are sequentially displayed according to the indications of the arrows, these steps are not necessarily executed sequentially in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and they can be executed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily to be carried out sequentially, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0127] Figure 6 A schematic diagram of a data asset management device based on a functional business perspective provided in an embodiment of the present application, such as Figure 6 As shown, the present application provides a data asset management device based on a functional business perspective, the device comprising:

[0128] A task list determination module 11, which is configured to determine a task list of functional business;

[0129] A data resource planning module 12, which is configured to perform data resource planning from a functional business perspective and obtain a data resource planning result;

[0130] The stock data survey module 13 is configured to conduct a stock data survey from the bottom database side to obtain a data survey result;

[0131] The comparison and association module 14 is configured to compare and associate the data resource planning results with the data investigation results to form a data ledger for data asset management.

[0132] Regarding the limitation of the data asset management device based on the functional business perspective, reference may be made to the limitation of the data asset management method based on the functional business perspective in the above-mentioned embodiments of the present application, which will not be elaborated in this embodiment.

[0133] Figure 7 Another schematic diagram of a data asset management device based on a functional business perspective provided in an embodiment of the present application is as follows: Figure 7 As shown, in some embodiments, the present application provides a data asset management device based on a functional business perspective, including a memory 22 and a processor 21, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the data asset management method based on a functional business perspective in the above-mentioned embodiments of the present application.

[0134] The memory is connected to the processor, the memory may be a flash memory or a read-only memory or other memory, and the processor may be a central processing unit or a single-chip microcomputer.

[0135] In some embodiments, the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the data asset management method based on the functional business perspective in the above-mentioned embodiments of the present application is implemented.

[0136] The computer-readable storage medium includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable read only memory), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer.

[0137] It is to be understood that the above embodiments are merely exemplary embodiments used to illustrate the principles of the present application, but the present application is not limited thereto. For those skilled in the art, various modifications and improvements can be made without departing from the spirit and substance of the present application, and these modifications and improvements are also considered to be within the scope of protection of the present application.

Claims

1. A data asset management method based on functional business perspective, characterized in that: The method comprises: S1. Determine the list of functional business matters; S2. Carry out data resource planning from the functional business perspective and obtain data resource planning results; S3. Conduct a data survey on the underlying database to obtain the data survey results. S4. Compare and associate the data resource planning results with the data investigation results to form a data ledger for data asset management.

2. The data asset management method based on functional business perspective according to claim 1 is characterized in that: S1, including: According to the metadata framework of business matters, the stock documents related to functions are processed and model training on function data is carried out; Fine-tune the model instructions and perform word prediction on the trained model, convert the job function text and fill it into the function data framework; Proofread and complete based on the functional data framework to obtain a list of items for the functional business.

3. The data asset management method based on functional business perspective according to claim 1 is characterized in that: S2, including: Obtain at least one of the existing metadata, data items, source systems, system-owned departments, and data owners from the internal data management system, and save it to the database; Match the data metadata and corresponding information items in the database to each department and specific functions according to department affiliation, data domain affiliation, and data owner; Verify the functions that have not generated data or cannot match data, and supplement system information and metadata information of expected data.

4. The data asset management method based on functional business perspective according to claim 1 is characterized in that: S3, including: Obtain system information, library table field information, library table comments, and field comments for the entire system; For the functional data that has been successfully associated with the metadata related to the internal system, import the relevant metadata information; For the resource planning data generated by the verification, the table and column information crawled from the database are summarized and matched with the corresponding functional business; Automatically score the successfully matched functional data to generate a matching degree; For the remaining system library table data that does not correspond to specific functions, they are manually classified or placed in separate columns according to the data source or annotations.

5. The data asset management method based on functional business perspective according to claim 1 is characterized in that: S4, including: Preliminary matching of functional business: by comparing core information items, matching the core data fields of the database table with the business items of the resource planning results, and establishing the relationship between data and functional business; According to the relationship between data and functional business, the data catalog and various element information are supplemented and improved to form a data ledger catalog; For each data resource included in the data ledger directory, supplement the responsibility attribute information.

6. The data asset management method based on functional business perspective according to any one of claims 1 to 5, characterized in that: Also includes: S5. Based on the data ledger, determine the data update and maintenance mechanism and various management responsibilities, and establish a data asset management system.

7. The data asset management method based on functional business perspective according to claim 6 is characterized in that: S5, including: Determine the main processes for data updating, maintenance, development and utilization, as well as the evaluation factors for data resource quality; According to the needs of data management, establish a division of labor and cooperation mechanism among departments, and determine the dynamic update and maintenance system of data and catalogs; A data asset management system for dynamically managing data asset ledgers should be developed simultaneously according to scale requirements.

8. A data asset management device based on functional business perspective, characterized in that: The device comprises: A task list determination module, which is configured to determine the task list of functional business; A data resource planning module is configured to perform data resource planning from a functional business perspective and obtain data resource planning results; The stock data survey module is configured to conduct a stock data survey from the underlying database side to obtain data survey results; A comparison and association module is configured to compare and associate the data resource planning results with the data survey results to form a data ledger for data asset management.

9. A data asset management device based on functional business perspective, characterized in that: It comprises a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to implement the data asset management method based on the functional business perspective as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the data asset management method based on a functional business perspective as described in any one of claims 1 to 7 is implemented.

Images