TWM606888U - Enterprise data gaze system capable of conducting data lineage analysis, data importance analysis, or data change tracking - Google Patents

Abstract

This new model proposes an enterprise data guide system, which includes: a data change tracking subsystem, which can receive data from multiple databases in different information management systems, and store multiple database outlines and data in multiple databases. The recorded multiple label outlines and the field names of multiple label entity tables; the label data subsystem is configured to visually present label data corresponding to the multiple label outlines and the field names of multiple label entity tables; and The data pedigree subsystem is set to perform data pedigree analysis based on multiple database outlines to establish the relationship between individual tables in multiple databases and other tables in the same database, and the relationship between individual tables and different databases The correlation between other tables, and the results of the data genealogy analysis are presented in a visual way.

Description

Enterprise data guidance system that can perform data genealogy analysis, data importance analysis, or data change tracking

The new model relates to database technology, especially an enterprise data guide system that can perform data genealogy analysis, data importance analysis, or data change tracking.

Many enterprise groups or consortiums have become larger and larger due to business expansion, diversified operations, or mergers and acquisitions. As a result, the number of databases used by their subsidiaries continues to increase. Over the years, it often leads to the simultaneous use of a large number of databases of various types with different brands/versions within the same enterprise group or consortium. Due to the complex data connection between different databases, or the restrictions on the use of each other’s databases between different units, it is often difficult for the information management department, product development department, and even high-level decision-making to clearly grasp the group or organization’s The data volume and data types in all databases are also difficult to efficiently aggregate and analyze the data in different databases. This type of situation is very common, especially for corporate groups or large consortia, where many of its databases are managed and used by different units or companies.

For example, many financial institutions or companies adjust various internal operating procedures in order to develop new products or businesses, or to comply with various domestic and foreign regulatory requirements (for example, personal information laws or EU GDPR regulations), and often need to develop Multiple programs in different databases. However, the aforementioned multiple databases are often managed by different departments or different subsidiaries. Therefore, when developing such cross-database programs, people from many different departments (for example, program developers, product managers, management Personnel, even legal compliance department personnel) must spend a very large amount of pre-work time and manpower to discuss and check, in order to clarify whether the changes in the contents of each database will affect the normal operation of other databases, otherwise it may affect the entire organization Business operations brought unforeseen catastrophic impact.

In view of this, how to reduce or eliminate the above-mentioned difficulties in developing cross-database programs is a technical problem to be solved.

This specification provides an example of an enterprise data guide system, which includes: a data change tracking subsystem, which is configured to receive data from multiple databases in different information management systems, and store the corresponding data from the multiple databases The multiple database outlines and the multiple label outlines and the field names of the multiple label entity tables recorded in the multiple databases; a label data subsystem, coupled to the data change tracking subsystem, is set to Visually present the label data corresponding to the plurality of label outlines and the field names of the plurality of label entity tables; and a data genealogy subsystem, coupled to the data change tracking subsystem, and set to be based on the plurality of The database outline performs data genealogical analysis to establish the relationship between individual tables in the multiple databases and other tables in the same database, as well as the relationship between individual tables and other tables in different databases. Visualize the results of data pedigree analysis.

This specification also provides an example of an enterprise data guide system, which includes: a data change tracking subsystem configured to receive data from multiple databases in different information management systems, and store the multiple database locations Corresponding multiple database outlines, multiple label outlines and multiple label entity table field names recorded in the multiple databases; a label data subsystem, coupled to the data change tracking subsystem, set The label data corresponding to the plurality of label outlines and the column names of the plurality of label entity tables are presented in a visual manner; a data genealogy subsystem is coupled to the data change tracking subsystem and is configured to be based on the plurality of The database outline performs data genealogical analysis to establish the relationship between individual tables in the multiple databases and other tables in the same database, as well as the relationship between individual tables and other tables in different databases. Visualize the results of data genealogy analysis; a model management subsystem, coupled to the data change tracking subsystem, is configured to store the identification data of multiple data models, and create individual data models and one or more parameters they refer to The mapping relationship between the source table and multiple parameter source fields; a data importance judging subsystem, coupled to the data pedigree subsystem, is set based on the association between a target table and other tables in the same database Of the target table, the relevance between the target table and other tables in different databases, and one or more user browsing indicators corresponding to the target table to calculate a data importance index value corresponding to the target table, where , The one or more user browsing indicators include the total number of the target form being queried by the user, the frequency of the target form being queried by the user, or the total number of the target form being subscribed and tracked by the user; wherein the data change tracking The subsystem is also set to intermittently check whether there is any change in the field names of the multiple database outlines, the multiple label outlines, and the multiple label entity tables; wherein, in the multiple database outlines, the multiple label When the outline or the field names of the multiple label entity tables are changed, the data importance judgment subsystem will update the data importance index values of the individual tables; among them, one or more parameter sources referred to in the individual data model When a table or one or more parameter source fields are changed, the model management subsystem will generate a corresponding data model parameter update warning notification.

One of the advantages of the above embodiment is that the enterprise data guide system can automatically analyze the relationship between multiple data tables in multiple databases in different information management systems, and the importance of individual data tables, and can visualize It presents the relevant data genealogy analysis results and data importance analysis results in a way, so that even if the user lacks the management or access authority of the relevant database, he can compare the relevant database and other databases based on the analysis results generated by the enterprise data guide system. The data relevance and importance of the data get complete and detailed reference information.

Another advantage of the above embodiment is that with the help of the enterprise data guide system, users can greatly improve their understanding and control of multiple databases and related data modules across systems, and effectively improve the project development process. Discuss and check efficiency. In this way, when developing programs that span multiple systems and multiple databases, relevant personnel can easily determine whether changes in the contents of each database will affect the normal operation of other databases, thereby saving a lot of pre-work Time and manpower, and can effectively avoid the unforeseen catastrophic impact on the business operations of the entire organization due to the development of cross-database programs.

The other advantages of the present invention will be explained in more detail with the following description and drawings.

The embodiments of the present invention will be described below in conjunction with related drawings. In the drawings, the same reference numerals indicate the same or similar elements or method flows.

FIG. 1 is a simplified functional block diagram of an enterprise information guide system 100 according to an embodiment of the new type. The enterprise data guide system 100 can communicate with multiple information management systems (for example, the exemplary information management systems 160, 170, and 180 in FIG. 1) through a suitable dedicated network or the Internet to obtain such information. Manage the relevant data of different databases in the system, and can automatically analyze the correlation between multiple data tables in different databases, analyze the importance of individual data tables, and visually present relevant analysis results.

As shown in Figure 1, the enterprise data guide system 100 in this embodiment includes a data change tracking subsystem 110, a tag data subsystem 120, a data genealogy subsystem 130, a model management subsystem 140, and a data important性 Judgment Subsystem 150.

The data change tracking subsystem 110 is configured to communicate with the aforementioned multiple information management systems 160~180 through a suitable dedicated network or the Internet to receive multiple databases in different information management systems 160~180 Incoming data, and store multiple database outlines corresponding to multiple databases, as well as multiple label outlines and multiple label entity table field names recorded in multiple databases.

The tag data subsystem 120 is coupled to the data change tracking subsystem 110, and is configured to visually present tag data corresponding to the field names of multiple tag outlines and multiple tag entity tables.

The data pedigree subsystem 130 is coupled to the data change tracking subsystem 110, and is configured to perform data pedigree analysis based on multiple database outlines to establish the relationship between individual tables in multiple databases and other tables in the same database , And the relationship between individual tables and other tables in different databases, and visually present the results of data genealogy analysis.

The model management subsystem 140 is coupled to the data change tracking subsystem 110, and is configured to store the identification data of multiple data models, and create a relationship between an individual data model and one or more parameter source tables and multiple parameter source fields to which it refers The mapping relationship between.

The data importance judging subsystem 150 is coupled to the data genealogy subsystem 130, and is configured to be based on the association between a target table and other tables in the same database, the association between the target table and other tables in different databases, And one or more user browsing indicators corresponding to the target table to calculate a data importance indicator value corresponding to the target table.

In practice, the individual subsystems in the enterprise data guide system 100 can be implemented by one or more arithmetic circuits with appropriate computing capabilities, or they can be implemented by a computer program composed of one or more functional modules. .

In the embodiment of Figure 1, all information management systems have similar main circuit architectures, but different additional circuit components can be set in different information management systems, without limiting the hardware architecture of all information management systems to complete the same. For example, the information management system 160 includes multiple databases (for example, the exemplary databases 161 to 163 in FIG. 1), a storage device 165, a communication circuit 167, a processing circuit 169, and data recorded in the storage device 165 One or more data models 192. Similarly, the information management system 170 includes multiple databases (for example, the exemplary databases 171 and 173 in FIG. 1), a storage device 175, a communication circuit 177, a processing circuit 179, and records in the storage device 175 One or more data models of 194.

In the information management system 160, the databases 161 to 163 are used to store various types of data. The storage device 165 is used to store various data models 192 (for example, various financial models, financial models, AI big data analysis models, engineering data analysis models, medical data analysis models, traffic data analysis models, etc.). The communication circuit 167 is used for data communication with the enterprise data guide system 100 through a suitable dedicated network or the Internet. The processing circuit 169 is coupled to the databases 161 to 163, the storage device 165, and the communication circuit 167 to control the operation of the aforementioned devices.

In the information management system 170, the databases 171 to 173 are used to store various types of data. The storage device 175 is used to store various data models 194 (for example, various financial models, financial models, AI big data analysis models, engineering data analysis models, medical data analysis models, traffic data analysis models, etc.). The communication circuit 177 is used for data communication with the enterprise data guide system 100 through a suitable dedicated network or the Internet. The processing circuit 179 is coupled to the databases 171 to 173, the storage device 175, and the communication circuit 177 to control the operation of the aforementioned devices.

The main circuit structure and operation mode of the information management system 180 are also similar to the aforementioned information management system 160 or 170, but for the sake of brevity, the internal circuit structure of the information management system 180 is not shown in FIG. 1.

In practice, the databases 161 to 163 and 171 to 173 can be implemented with various types of databases, and can also be implemented with a combination of multiple databases located in the same geographic area or in different geographic areas. The storage devices 165 and 175 can be implemented by various suitable volatile storage circuits or non-volatile storage circuits. The communication circuits 167 and 177 can be implemented by various appropriate circuits that comply with relevant network communication, wireless communication, or mobile communication specifications, such as network cards, wireless transmission circuits, or mobile communication circuits. Both the processing circuits 169 and 179 can be implemented by one or more processor modules with appropriate computing capabilities. In addition, the brands, models, and data types stored in different databases in the same information management system can be different. The number of databases in different information management systems can also vary.

In some embodiments, the aforementioned one or more data models 192 can also be stored in the databases 161 to 163, and the aforementioned one or more data models 194 can be stored in the databases 171-173. In this case, the aforementioned storage devices 165 and 175 may be omitted.

Please note that the aforementioned enterprise data guide system 100 and information management system 160~180 can be implemented with human-machine interface devices (for example, display, keyboard, mouse, touch screen, etc.) required for users to control. ), but in order to simplify the content of the drawing, these man-machine interface devices are not shown in Figure 1.

In practical applications, different information management systems 160, 170, and 180 may be managed and used by the same department or company, or they may be managed and used by different departments or companies. Therefore, the system administrators of the information management system 160, 170, or 180 in FIG. 1 may be different from each other and do not have the management authority of other information management systems.

For example, the information management systems 160, 170, and 180 may be managed and used by different companies under the same financial holding group. In general, the information management personnel of individual companies will not have management and access rights to other companies' internal information management systems. In some environments regulated by laws and regulations, it may not be allowed for anyone in the same group to have the management and access rights of all communication management systems at the same time.

The managers, users, or other related product developers and managers of different information management systems 160, 170, 180 can use appropriate devices (such as various computers, smart phones, tablets, etc.) and individual The account logs into the enterprise information guide system 100 to query the data in the enterprise information guide system 100, obtain various analysis results of the enterprise information guide system 100, and leave messages, notes, or mutual discussions. In this way, managers, users, or other related product developers and managers of information management systems 160, 170, and 180 can use the enterprise data guide system without the authority to access the relevant data inventory. The analysis results of 100 learn about the data association between multiple data tables in different databases, and even the importance of individual data items, which can effectively clarify whether changes in the contents of each database will affect The normal operation of other databases to avoid the unforeseen catastrophic impact of the development of new products on the business operations of the entire organization.

Hereinafter, the operation mode of the enterprise information guide system 100 will be further described in conjunction with FIGS. 2 to 6. FIG. 2 is a simplified schematic diagram of the data flow logic when the enterprise data guide system 100 is operating. FIG. 3 is a simplified flowchart of an embodiment of a method for data genealogy analysis and importance judgment performed by the enterprise data guide system 100. 4 is a simplified schematic diagram of an embodiment of the data genealogical analysis result screen 400 generated by the enterprise data guide system 100. FIG. 5 is a simplified schematic diagram of an embodiment of a data importance analysis result screen 500 generated by the enterprise data guide system 100. 6 is a simplified flowchart of an embodiment of a method for tracking data changes performed by the enterprise data guide system 100.

In the flowcharts of FIGS. 3 and 6, the process in the column of a specific device represents the process performed by the specific device. For example, the part marked in the "Data Change Tracking Subsystem" field is the process carried out by the data change tracking subsystem 110; the part marked in the "Tag Data Subsystem" field is made by the label data subsystem The process performed by 120; the part marked in the "Data Genealogy Subsystem" field is the process performed by the Data Genealogy Subsystem 130; the rest can be deduced by analogy.

In order to obtain the data required for various analyses, the data change tracking subsystem 110 of the enterprise data guide system 100 can perform the process 302 in FIG. 3 to communicate with multiple information management systems 160 to 180 to obtain and store the corresponding data. Multiple database schemas for databases 161~173.

In the process 304, the data change tracking subsystem 110 can also communicate with multiple information management systems 160 to 180 to obtain and store multiple tag schemas recorded in different databases 161 to 173, and The column names of multiple label entity tables.

In the process 306, the tag data subsystem 120 can obtain the plurality of tag outlines and the field names of the plurality of tag entity tables according to the instructions of the data change tracking subsystem 110. In practice, the data change tracking subsystem 110 can directly transmit the multiple tag outlines and the field names of the multiple tag entity tables to the tag data subsystem 120, or the multiple tag outlines and the multiple tag entity tables The storage location of the field name of is notified to the tag data subsystem 120, so that the tag data subsystem 120 can read the multiple tag outlines and the field names of the multiple tag entity tables.

In the process 308, the tag data subsystem 120 can present tag data in various suitable visual ways. For example, the tag data subsystem 120 can list various tag data set by the managers or users of the databases 161~173. The list or various statistical graphs are presented to the users of the enterprise information guide system 100.

In the process 310, the data genealogy subsystem 130 may obtain the multiple database outlines according to the instructions of the data change tracking subsystem 110. In practice, the data change tracking subsystem 110 can directly transmit the multiple database outlines to the data genealogy subsystem 130, or notify the data genealogy subsystem 130 of the storage location of the multiple database outlines, so that the data genealogy subsystem 130 Read the outlines of the multiple databases by yourself.

In the process 312, the data genealogy subsystem 130 can obtain the multiple tag outlines according to the instructions of the data change tracking subsystem 110 or the tag data subsystem 120. In practice, the data change tracking subsystem 110 or the tag data subsystem 120 can directly send the multiple tag outlines to the data genealogy subsystem 130, or notify the data genealogy subsystem 130 of the storage location of the multiple tag outlines, so that the data The pedigree subsystem 130 reads the multiple tag outlines by itself.

In the process 314, the data pedigree subsystem 130 can perform various appropriate data pedigree analyses according to the aforementioned multiple tag outlines to establish the relationship between the individual tables in the aforementioned databases 161 to 173 and other tables in the same database. , And establish the relationship between individual tables and other tables in different databases. In some embodiments, the data pedigree subsystem 130 may further refer to the aforementioned multiple tag outlines to perform data pedigree analysis of individual data tables.

In the process 316, the data pedigree subsystem 130 may present the data pedigree analysis result in various suitable visual ways, for example, the data pedigree analysis result screen 400 shown in FIG. 4. In the data pedigree analysis result screen 400, the data pedigree subsystem 130 can arrange the pedigree analysis results of some of the data tables 402-418 in the aforementioned databases 161-173 in the form of an association graph, and express them as a connecting line with arrows. Blood relationship between different data sheets. In the embodiment of FIG. 4, at least part of the content in the data table 408 is derived from the content of the data tables 402, 404, and 406; at least part of the content in the data tables 414 and 416 is derived from the data table 410 The content of data table 418 is derived from the content of data table 412; the rest can be deduced by analogy.

In the process 318, the data importance judgment subsystem 150 can obtain the data pedigree analysis result according to the instruction of the data pedigree subsystem 130. In practice, the data pedigree subsystem 130 can send the data pedigree analysis result to the data importance determination subsystem 150, or notify the data importance determination subsystem 150 of the storage location of the data pedigree analysis result, so that the data importance determination subsystem 150 self-read data pedigree analysis results.

In this embodiment, the data importance judging subsystem 150 can also perform a process 320 to collect and count user browsing indicators of individual tables. The aforementioned user browsing index may include the total number of individual forms inquired by users, the frequency with which individual forms are inquired by users, and/or the total number of individual forms subscribed and tracked by users.

In the process 322, the data importance judging subsystem 150 can analyze the data importance of individual tables based on the data pedigree analysis result of the data pedigree subsystem 130 to generate corresponding data importance index values.

For example, for a certain target table, the data importance judgment subsystem 150 can be based on the association between the target table and other tables in the same database, and the association between the target table and other tables in different databases In order to calculate the data importance index value of the target table, various appropriate weighting operations are performed. For another example, the data importance judgment subsystem 150 can be based on the relationship between the target table and other tables in the same database, the relationship between the target table and other tables in different databases, and the correspondence of the target table. The user browses the index and performs various appropriate weighting operations to calculate the data importance index value of the target table.

For other tables, the data importance judgment subsystem 150 can calculate a corresponding data importance index value in accordance with the method of the aforementioned target table.

In practical applications, the data importance judging subsystem 150 can present the data importance analysis result in various suitable visual ways, for example, the data importance analysis result screen 500 shown in FIG. 5. In the data importance analysis result screen 500, the data importance judgment subsystem 150 can sort the relative importance of multiple data tables in the databases 161 to 173 and their pedigree associations into corresponding data table associations Figure 510, at the same time presents the more important data tables with a larger graphic area, and connects the data tables with genealogical relevance with lines.

In addition, as shown in FIG. 5, the data importance judgment subsystem 150 can also assign multiple data tables to the system (system), to the database (database, DB), table name (table name), and table creator (Table Owner), Table Maintainer, Lineage Score, Impact Score, Importance Score, Change Frequency, Ownership Related information such as group, group centrality, etc., is compiled into a corresponding data importance summary table 520 for users to refer to.

In this embodiment, the model management subsystem 140 also performs the process 602 in FIG. 6 to store the identification data of multiple data models (for example, the aforementioned data models 192, 194) in the databases 161 to 173, and Establish the mapping relationship between the individual data model and the referenced parameter source table and parameter source field. In practice, the identification data of individual data models, the parameter source table and parameter source fields that the data model refers to, can be input by the user of the enterprise data guide system 100 to the model management subsystem 140, or can be from the aforementioned The information management systems 160~180 of the data are automatically transmitted to the data change tracking subsystem 110 through a predetermined method, and the data change tracking subsystem 110 provides the model management subsystem 140.

In practical applications, the model management subsystem 140 can, according to the user’s request or query, map the mapping relationship between the individual data model and the referenced parameter source table and parameter source field as appropriate form, chart, text description, etc. The visualized way is provided for user reference.

As time passes, the database outlines corresponding to the aforementioned different databases 161~173, the recorded label outlines, and the field names of the recorded label entity tables may all be used by individual database managers and Or product developers make changes or adjustments, but these changes or adjustments are usually not provided in detail to managers, users, or product developers of other information management systems’ databases.

Therefore, the enterprise data guide system 100 will also intermittently execute other processes in FIG. 6 to track related changes in individual databases.

As shown in Figure 6, the data change tracking subsystem 110 can perform a process 604 to intermittently communicate with multiple information management systems 160 to 180, and obtain multiple database outlines corresponding to different databases 161 to 173, respectively. Multiple label outlines and field names of multiple label entity tables recorded in different databases 161 to 173.

Then, the data change tracking subsystem 110 can perform the process 606 to compare the newly received database outline, tag outline, and tag entity table field names with the previously received database outline, tag outline, and tag entity table. Compare the field names of, to check whether the field names of the database outline, label outline, or label entity table corresponding to the aforementioned databases 161~173 have changed.

If there is no change in the database outline, label outline, and field names of the label entity table corresponding to the databases 161 to 173, the data change tracking subsystem 110 can perform the aforementioned processes 604 and 606 again after a suitable time has elapsed. .

If certain database outlines, certain label outlines, or certain label entity table field names corresponding to databases 161 to 173 are changed, the data change tracking subsystem 110 can perform process 608 to generate corresponding Information update notification.

In the process 610, the tag data subsystem 120, the data genealogy subsystem 130, the model management subsystem 140, or the data importance judgment subsystem 150 will receive the data update notification generated by the data change tracking subsystem 110.

As shown in Figure 6, if some database outlines and/or certain tag outlines are changed, the data genealogy subsystem 130 can perform process 612 to perform data genealogical analysis again to update the individual databases 161 to 173. The relationship between a table and other tables in the same database, and the relationship between an individual table and other tables in a different database.

In the process 614, the data pedigree subsystem 130 may present the updated data pedigree analysis results in various suitable visual ways. For example, the data pedigree subsystem 130 can generate a data pedigree analysis result screen similar to the data pedigree analysis result screen 400 in FIG. 4 but with different content.

In the process 616, the data importance judgment subsystem 150 can obtain the updated data pedigree analysis result according to the instruction of the data pedigree subsystem 130. For example, the data pedigree subsystem 130 can send the updated data pedigree analysis result to the data importance judging subsystem 150, or notify the data importance judging subsystem 150 of the storage location of the updated data pedigree analysis result to make the data important The sex judgment subsystem 150 reads the updated data pedigree analysis result by itself.

Similar to the embodiment in FIG. 3, the data importance judging subsystem 150 can continue to perform the process 618 to continuously collect and count user browsing indicators of individual tables.

In the process 620, the data importance judging subsystem 150 can analyze the data importance of the individual tables again based on the updated data genealogical analysis results to update the data importance index values corresponding to the individual tables.

For example, for a certain target table, the data importance judgment subsystem 150 can be based on the association between the target table and other tables in the same database, and the association between the target table and other tables in different databases To recalculate and update the data importance index value of the target table, perform various appropriate weighting operations. For another example, the data importance judgment subsystem 150 can be based on the relationship between the target table and other tables in the same database, the relationship between the target table and other tables in different databases, and the correspondence of the target table. Users browse the indicators and perform various appropriate weighting operations to recalculate and update the data importance indicator value of the target table.

For other tables, the data importance judgment subsystem 150 can update the data importance index value corresponding to the individual table in the same manner as the aforementioned target table.

If there is a change in the parameter source table and/or parameter source field referenced by an individual data model, the model management subsystem 140 can perform process 622 to update the relationship between the individual data model and the referenced parameter source table and parameter source field Antipodal relationship.

In this case, the model management subsystem 140 may also perform the process 624 to generate a corresponding data model parameter update warning notice and provide it to the relevant user. In this way, the relevant user can check or query the change process of the parameter source table and/or parameter source field referenced by the relevant data model according to the warning notice of the model management subsystem 140 to clarify the relevant Is the transaction a legal transaction or a wrong transaction accidentally caused by someone else.

From the foregoing description, it can be seen that the enterprise data guide system 100 can automatically analyze the relationship between multiple data tables in multiple databases in different information management systems 160 to 180, and the importance of individual data tables, and can visualize Ways to present relevant data pedigree analysis results and data importance analysis results. Therefore, even if the user of the enterprise data guide system 100 lacks the management or access authority of the relevant database, he can still analyze the data relevance between the relevant database and other databases based on the analysis results generated by the enterprise data guide system 100. The importance of data to obtain complete and detailed reference information, which can provide very substantial information to relevant personnel involved in cross-database program development (for example, program developers, product managers, management personnel, and even legal compliance department personnel) help.

In addition, the enterprise data guide system 100 can also automatically determine and track whether the database outlines of multiple databases 161 to 173 have changed, the label outlines and/or the field names of the label entity tables recorded in different databases 161 to 173. Whether there is a change, and whether the parameter source table and/or parameter source field referenced by the individual data model is changed, and when the aforementioned data items are changed, the relevant data genealogical analysis results, data importance analysis results, And the mapping relationship between the individual data model and the referenced parameter source table and parameter source field.

Therefore, with the assistance of the enterprise data guide system 100, users can greatly improve their understanding and control of multiple databases and related data modules in the cross-system, and effectively improve the efficiency of discussion and verification of the project development process.

In this way, when developing programs that span multiple systems and multiple databases, relevant personnel can easily determine whether changes in the contents of each database will affect the normal operation of other databases, thereby saving a lot of pre-work Time and manpower, and can effectively avoid the unforeseen catastrophic impact on the business operations of the entire organization due to the development of cross-database programs.

Please note that the execution sequence of the process in FIG. 3 is only an exemplary embodiment and does not limit the actual implementation of the present invention. For example, the sequence of the process 302 and the process 304 in FIG. 3 can be reversed or performed simultaneously. There is no restriction on the sequence of the processes 308 and 314. In addition, the sequence of the process 614, the process 616, and the process 622 in FIG. 6 is not limited in any way. In some applications, the process 312, the process 320, and/or the process 618 may also be omitted.

Please note that the number of the aforementioned information management system and database can be increased according to the needs of the actual application environment, and is not limited to the aspect depicted in the aforementioned embodiment.

Furthermore, in applications that do not need to use a data model or control the source of related parameters of the data model, the aforementioned model management subsystem 140 can be omitted to simplify the architectural complexity of the enterprise data guide system 100.

In the specification and the scope of the patent application, certain words are used to refer to specific elements, and those skilled in the art may use different terms to refer to the same elements. This specification and the scope of patent application do not use differences in names as a way to distinguish components, but use differences in functions of components as a basis for distinction. The "include" mentioned in the specification and the scope of the patent application is an open term and should be interpreted as "include but not limited to". In addition, the term "coupled" herein includes any direct and indirect connection means. Therefore, if it is described in the text that the first element is coupled to the second element, it means that the first element can be directly connected to the second element through electrical connection, wireless transmission, optical transmission, or other signal connection methods, or through other elements or connections. The means is indirectly connected to the second element electrically or signally.

The description method of "and/or" used in the description includes one of the listed items or any combination of multiple items. In addition, unless otherwise specified in the specification, any term in the singular case also includes the meaning of the plural case.

The above are only the preferred embodiments of the present invention, and all equivalent changes and modifications made in accordance with the claims of the present invention shall fall within the scope of the present invention.

100: Enterprise data gaze system (enterprise data gaze system)

110: data change tracking subsystem (data change tracking subsystem)

120: tag data subsystem (tag data subsystem)

130: data lineage subsystem (data lineage subsystem)

140: model management subsystem (model management subsystem)

150: data significance identification subsystem

160, 170, 180: information management system (management information system)

161, 163, 171, 173: database (database)

165, 175: storage device (storage device)

167, 177: communication circuit (communication circuit)

169, 179: processing circuit

192, 194: data model

302~322, 602~624: operation

400: data lineage analysis resulting screen

402~418: data table

500: data importance analysis resulting screen

510: table relationship diagram

520: data importance summary table (data importance summary table)

FIG. 1 is a simplified functional block diagram of the enterprise information guide system according to an embodiment of the new type.

Figure 2 is a simplified schematic diagram of the data flow logic when the enterprise data guide system in Figure 1 is operating.

3 is a simplified flowchart of an embodiment of a method for data genealogy analysis and importance judgment performed by the enterprise data guide system in FIG. 1.

4 is a simplified schematic diagram of an embodiment of a data genealogical analysis result screen generated by the enterprise data guide system in FIG. 1.

FIG. 5 is a simplified schematic diagram of an embodiment of a data importance analysis result screen generated by the enterprise data guide system in FIG. 1.

6 is a simplified flowchart of an embodiment of a method for tracking data changes performed by the enterprise data guide system in FIG. 1.

100: Enterprise Information Guide System

110: Data Change Tracking Subsystem

120: Tag data subsystem

130: Data Genealogy Subsystem

140: Model Management Subsystem

150: Data Importance Judgment Subsystem

160, 170, 180: Information Management System

161, 163, 171, 173: database

165, 175: storage device

167, 177: Communication circuit

169, 179: Processing circuit

192, 194: Data Model

Claims (10)

An enterprise information guide system (100), which includes: A data change tracking subsystem (110), which is configured to receive data from multiple databases (161, 163, 171, 173) in different information management systems (160, 170), and store the multiple databases (161, 163, 171, 173) corresponding multiple database outlines, and multiple label outlines and multiple label entity table fields recorded in the multiple databases (161, 163, 171, 173) name; A tag data subsystem (120), coupled to the data change tracking subsystem (110), is configured to visually present tag data corresponding to the plurality of tag outlines and the field names of the plurality of tag entity tables ;as well as A data pedigree subsystem (130), coupled to the data change tracking subsystem (110), is configured to perform data pedigree analysis based on the multiple database outlines to establish the multiple databases (161, 163, 171, 173) the relationship between individual tables and other tables in the same database, as well as the relationship between individual tables and other tables in different databases, and visually present the results of data genealogy analysis. The enterprise information guide system (100) as described in claim 1, which additionally includes: A data importance judging subsystem (150), coupled to the data pedigree subsystem (130), configured to calculate the data importance index value of individual tables based on the data pedigree analysis result of the data pedigree subsystem (130) . For example, the enterprise data guide system (100) according to claim 2, wherein the data importance judgment subsystem (150) is also set to be based on the relationship between a target table and other tables in the same database, and the target table For the correlation with other tables in different databases, a data importance index value corresponding to the target table is calculated. For example, the enterprise data guide system (100) according to claim 2, wherein the data importance judgment subsystem (150) is also set to be based on the relationship between a target table and other tables in the same database, and the target table The correlation with other tables in different databases and one or more user browsing indicators corresponding to the target table are calculated to calculate a data importance index value corresponding to the target table. The enterprise data guide system (100) according to claim 4, wherein the one or more user browsing indicators include the total number of the target form being queried by the user, the frequency of the target form being queried by the user, or the The total number of target tables subscribed and tracked by users. The enterprise data guide system (100) according to claim 1, wherein the data change tracking subsystem (110) is also configured to intermittently check the multiple database outlines, the multiple label outlines, and the multiple labels Whether the field name of the entity table has changed. The enterprise data guide system (100) according to claim 6, wherein the data importance judging subsystem (150) is further configured to be used in the plurality of database outlines, the plurality of label outlines, or the plurality of label entities When the field name of the table changes, update the data importance index value of the individual table. The enterprise information guide system (100) as described in claim 6, which additionally includes: A model management subsystem (140), coupled to the data change tracking subsystem (110), is configured to store the identification data of multiple data models, and create individual data models and one or more parameter source tables that they refer to and The mapping relationship between multiple parameter source fields. The enterprise data guide system (100) according to claim 8, wherein the model management subsystem (140) is further configured to list one or more parameter source tables or one or more parameter source columns referred to by individual data models When there is a bit change, update the mapping relationship between an individual data model and the referenced one or more parameter source tables and one or more parameter source fields, and generate corresponding data model parameter update warning notifications. An enterprise information guide system (100), which includes: A data change tracking subsystem (110), which is configured to receive data from multiple databases (161, 163, 171, 173) in different information management systems (160, 170), and store the multiple databases (161, 163, 171, 173) corresponding multiple database outlines, and multiple label outlines and multiple label entity table fields recorded in the multiple databases (161, 163, 171, 173) name; A tag data subsystem (120), coupled to the data change tracking subsystem (110), is configured to visually present tag data corresponding to the plurality of tag outlines and the field names of the plurality of tag entity tables ； A data pedigree subsystem (130), coupled to the data change tracking subsystem (110), is configured to perform data pedigree analysis based on the multiple database outlines to establish the multiple databases (161, 163, 171, 173) the relationship between individual tables in the same database and other tables in the same database, as well as the relationship between individual tables and other tables in different databases, and visually present the results of data genealogy analysis; A model management subsystem (140), coupled to the data change tracking subsystem (110), is configured to store the identification data of multiple data models, and create individual data models and one or more parameter source tables that they refer to and The mapping relationship between multiple parameter source fields; A data importance judging subsystem (150), coupled to the data pedigree subsystem (130), is set to be based on the relationship between a target table and other tables in the same database, the target table and different databases The correlation between other tables and one or more user browsing indicators corresponding to the target table are calculated to calculate a data importance index value corresponding to the target table, wherein the one or more user browsing indicators , Including the total number of the target form being queried by the user, the frequency of the target form being queried by the user, or the total number of the target form being subscribed and tracked by the user; Wherein, the data change tracking subsystem (110) is also set to intermittently check whether there is any change in the field names of the multiple database outlines, the multiple label outlines, and the multiple label entity tables; Among them, when the multiple database outlines, the multiple label outlines, or the field names of the multiple label entity tables are changed, the data importance judgment subsystem (150) will update the data importance indicators of individual tables value; Wherein, when one or more parameter source tables or one or more parameter source fields referred to by an individual data model are changed, the model management subsystem (140) will generate a corresponding data model parameter update warning notification.

Images