Data processing method, device, data processing equipment and storage medium

Abstract

The present application discloses a data processing method, apparatus, device, and storage medium, wherein the method includes: displaying a metadata management page including multiple metadata management entries, triggering the update of target management item data of a target subcategory under a target management item to target data through a target metadata management entry, determining a target system use case corresponding to the target subcategory from a system use case, and updating the data associated with the target system use case and the target management item through the target data. In this manner, the relevant data of all target system use cases corresponding to the target subcategory can be updated through a single update operation on the target management item data of the target subcategory under the target management item, thereby improving the efficiency and accuracy of data updates for system use cases.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data processing method, a data processing apparatus, a data processing device, and a computer storage medium. Background Art

[0002] Traditional document editing uses full-text replacement to update identical words and phrases. For example, if you want to replace a person's name in an article, you first need to perform a global match to find the name, then use the replace function to modify the name. However, this traditional text replacement method only works for plain text files and is not suitable for structured data such as those used in system use cases.

[0003] In system use cases, data is highly structured, and the same word may appear in multiple different system use cases. Traditional global replacement methods can only meet the needs of a single use case. For multiple system use cases, the replacement operation must be repeated one by one, which is inefficient and prone to errors. Furthermore, even within a single system use case, global search can hardly clearly display the target content because the information display format is different from that of ordinary text files, which affects the replacement process.

[0004] It can be seen that the existing data update method for system use cases has obvious shortcomings. How to improve the efficiency and accuracy of data updates for system use cases has become an urgent problem to be solved. Summary of the Invention

[0005] The embodiments of the present application provide a data processing method, apparatus, device and storage medium, which can complete the update of relevant data of all target system use cases corresponding to the target subcategory through a single update operation of the target management item data under the target management item of the target subcategory, which is conducive to improving the data update efficiency and accuracy for the system use case.

[0006] In one aspect, an embodiment of the present application provides a data processing method, the method comprising:

[0007] Displays the metadata management page, which includes multiple metadata management entries. Each metadata management entry is used to trigger the management of a category of metadata. Metadata is used to describe data associated with system use cases.

[0008] When a trigger operation is detected for a target metadata management entry, at least one subcategory of the target category, at least one management item related to the at least one subcategory, management item data of each subcategory under each management item, and an update entry corresponding to each subcategory are displayed; wherein the target category is the category of metadata whose management is triggered by the target metadata management entry;

[0009] The target management item data of the target subcategory under the target management item is updated to the target data through the update entry corresponding to the target subcategory;

[0010] A target system use case corresponding to a target subcategory is determined from the system use cases, and data associated with the target system use case and the target management item is updated using target data.

[0011] On the other hand, an embodiment of the present application provides a data processing device, the data processing device comprising:

[0012] A display unit is used to display a metadata management page, which includes multiple metadata management entries, each of which is used to trigger the management of a category of metadata; metadata refers to data associated with a system use case;

[0013] The display unit is further configured to, when a trigger operation for a target metadata management entry is detected, display at least one subcategory of the target category, at least one management item related to the at least one subcategory, management item data for each subcategory under each management item, and an update entry corresponding to each subcategory; wherein the target category is the category of metadata whose management is triggered by the target metadata management entry;

[0014] A processing unit, configured to trigger, through an update entry corresponding to the target subcategory, updating the target management item data of the target subcategory under the target management item to target data;

[0015] The processing unit is further used to determine the target system use case corresponding to the target subcategory from the system use case, and update the data associated with the target system use case and the target management item through the target data.

[0016] In one embodiment, the data processing apparatus further comprises a communication unit, wherein:

[0017] A display unit, specifically configured to display a metadata update window when a trigger operation for an update entry corresponding to a target subcategory is detected, the metadata update window including target management items;

[0018] The processing unit is specifically configured to input update data including target data in the metadata update window, where the target data is used to update target management item data of the target subcategory under the target management item;

[0019] The processing unit is further specifically configured to trigger the communication unit to send an audit request carrying the updated data to the audit device, so that the audit device can audit the updated data and return the audit result;

[0020] The communication unit is used to receive the audit result returned by the audit device. If the audit result is passed, the target management item data of the target subcategory under the target management item is updated to the target data.

[0021] In one embodiment, the target categories include domain, use case classification, use case identification, use case stakeholder, use case actor, or use case field;

[0022] When the target category is the above-mentioned domain, the target subcategory is the target domain, and the target system use case is the system use case whose domain is the target domain among the system use cases;

[0023] When the target category is a use case classification, the target subcategory is the target use case classification, and the target system use case is the system use case whose use case classification in the system use case is the target use case classification;

[0024] When the target category is use case stakeholders, the target subcategory is target use case stakeholders, and the target system use case is the system use case whose use case stakeholders are target use case stakeholders.

[0025] When the target category is use case executor, the target subcategory is target use case executor, and the target system use case is the system use case whose use case executor is the target use case executor in the system use case;

[0026] When the target category is a use case field, the target subcategory is the target use case field, and the target system use case is the system use case that uses the target use case field in the system use case.

[0027] In one embodiment, the system use case includes multiple, the target category is the use case classification, the target subcategory is the target use case classification, the metadata update window also includes a business sequence diagram input item, the business sequence diagram input item is used to trigger the input execution of the business sequence diagram corresponding to the system use case, the update data includes the business sequence diagram, the processing unit is also specifically used to obtain and identify the business sequence diagram from the update data to determine the use case classification to which each system use case belongs; the system use case classified as the target use case classification from each system use case is determined as the target system use case.

[0028] In one embodiment, the display unit is further specifically used to detect the management status of each management item data corresponding to each subcategory through the processing unit; if it is detected that the management status of any management item data corresponding to any subcategory is a modification status, then the update entry corresponding to any subcategory is displayed in a first display mode, and the first display mode includes displaying in a first specified color and / or displaying in a first specified font.

[0029] In one embodiment, the processing unit is also used to add a display deletion entry for the target subcategory if it is detected that no system use case in the system use case is associated with the target subcategory in the target category. The deletion entry is used to trigger the deletion of the management item data of the target subcategory under each management item.

[0030] In one embodiment, the processing unit is further used to detect the association relationship between each subcategory and the system use case when a trigger operation for the target metadata management entry is detected; if it is detected that there is no system use case in the system use case associated with the target subcategory in each subcategory, the deletion entry corresponding to the target subcategory is displayed in a second display mode through the display unit, and the second display mode includes displaying in a second specified color and / or displaying in a second specified font.

[0031] In one embodiment, the display unit is further configured to display an add entry when a trigger operation for a target metadata management entry is detected, where the add entry is configured to trigger the addition of management item data of one or more new subcategories under each management item.

[0032] In one embodiment, the processing unit is further configured to trigger the communication unit to execute the step of sending an audit request carrying the updated data to the audit device if the data format of the target data obtained by verification satisfies the corresponding format condition.

[0033] Accordingly, an embodiment of the present application also provides a data processing device, which includes an output device, a processor and a storage device; the storage device is used to store program instructions; and the processor is used to call the program instructions and execute the above-mentioned data processing method.

[0034] Correspondingly, an embodiment of the present application further provides a computer storage medium, in which program instructions are stored. When the program instructions are executed, they are used to implement the above-mentioned data processing method.

[0035] Accordingly, according to one aspect of the present application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the data processing method provided above.

[0036] In an embodiment of the present application, a metadata management page including multiple metadata management entries can be displayed. When a trigger operation for a target metadata management entry is detected, at least one subcategory of the target category, at least one management item involved in at least one subcategory, management item data of each subcategory under each management item, and an update entry corresponding to each subcategory are displayed. Furthermore, the target management item data of the target subcategory under the target management item is updated to the target data through the update entry corresponding to the target subcategory, and the target system use case corresponding to the target subcategory is determined from the system use case, and the data associated with the target system use case and the target management item is updated through the target data. In this way, the relevant data of all target system use cases corresponding to the target subcategory can be updated through a single update operation for the target management item data of the target subcategory under the target management item, which is beneficial to improving the efficiency and accuracy of data updates for system use cases. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0038] Figure 1 A schematic diagram of a data processing system provided in an embodiment of the present application;

[0039] Figure 2 This is a schematic flow chart of a data processing solution provided in an embodiment of the present application;

[0040] Figure 3 is a schematic flow chart of a data processing method provided in an embodiment of the present application;

[0041] Figure 4a to Figure 4f This is a page diagram provided by an embodiment of the present application;

[0042] Figure 5 is a schematic flow chart of another data processing method provided in an embodiment of the present application;

[0043] Figure 6a to Figure 6c This is a page diagram provided by an embodiment of the present application;

[0044] Figure 6d This is a schematic diagram of a service sequence diagram provided by an embodiment of the present application;

[0045] Figure 7a This is a schematic flowchart of a metadata deletion process provided by an embodiment of the present application;

[0046] Figure 7b This is a schematic flow chart of a metadata adding process provided by an embodiment of the present application;

[0047] Figure 7c This is a schematic flow chart of a metadata update process provided by an embodiment of the present application;

[0048] Figure 7d This is a schematic diagram of a scenario for deleting a use case classification provided by an embodiment of the present application;

[0049] Figure 7e This is a schematic diagram of a scenario for increasing use case classification provided by an embodiment of the present application;

[0050] Figure 8 is a structural diagram of a data processing device provided in an embodiment of the present application;

[0051] Figure 9 It is a structural diagram of a data processing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0052] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0053] In order to improve the data update efficiency and accuracy for system use cases, this application proposes a data processing system and a data processing solution based on the data processing system. Figure 1 The data processing system proposed in the embodiment of the present application may include: a data processing device 10 and an audit device 11. In one embodiment, the data processing device 10 and the audit device 11 may both be pre-installed with the same data processing platform and perform corresponding data processing through the data processing platform. The data processing device 10 and the audit device 11 may both be smartphones (such as Android phones, iOS phones, etc.), tablet computers, laptop computers, desktop computers, smart speakers, smart watches, etc., but are not limited to these.

[0054] In one embodiment, the data processing scheme proposed in the embodiment of the present application can be Figure 1 The data processing equipment and auditing equipment shown are executed. Figure 2 , the implementation process of the data processing solution is as follows:

[0055] At S20, the data processing device displays a metadata management page. This page includes multiple metadata management entries, each of which triggers the management of metadata for a specific category. Metadata is used to describe data associated with system use cases. Specifically, metadata refers to raw data, which is specially defined information containing different business meanings. Metadata can be understood as basic components that can be used to describe data associated with system use cases (e.g., the domain corresponding to the system use case, use case classification, use case identifier (e.g., use case name), use case stakeholders, use case performers, or use case fields).

[0056] In software engineering or systems engineering, a system use case can be understood as a description of how a system responds to external requests. It's a technique for capturing requirements through user scenarios. Each system use case provides one or more scenarios that illustrate how the system interacts with end users or other systems—in other words, who can use the system and what—to achieve a clear business goal. For example, if the business goal is repayment, the corresponding system use case might be a use case for the repayment process; if the business goal is collection, the corresponding system use case might be a use case for defining the collection process.

[0057] S21, when the data processing device detects a trigger operation for the target metadata management entry, it displays at least one subcategory of the target category, at least one management item involved in the at least one subcategory, the management item data of each subcategory under each management item, and the update entry corresponding to each subcategory.

[0058] Among them, the target metadata management entry is any one of multiple metadata management entry, and different target categories of content can be triggered to be displayed through different metadata management entry. The target category is the category of metadata triggered and managed by the target metadata management entry. Exemplarily, the target category can include domain, use case classification, use case identification, use case stakeholder, use case executor or use case field, etc.

[0059] In an embodiment of the present application, each metadata management entry is used to trigger the management of metadata of a category. For example, the first metadata management entry is used to trigger the management of metadata of the domain category; the second metadata management entry is used to trigger the management of metadata of the use case classification category. Furthermore, for a category, it can be divided into multiple subcategories. For example: if the target category is domain, at least one subcategory of the target category may include XX payment system, change, marketing, payment, etc.; for another example: if the target category is use case classification, at least one subcategory of the target category may include release testing, XX collection, XX payment, etc.

[0060] S22: When the data processing device detects a triggering operation for an update entry corresponding to a target subcategory, a metadata update window is displayed, where the metadata update window includes the target management item.

[0061] S23, the data processing device inputs update data including target data in the metadata update window, where the target data is used to update the target management item data of the target subcategory under the above target management item.

[0062] S24: The data processing device triggers to send an audit request carrying updated data to the audit device.

[0063] S25, the audit device audits the updated data and returns the audit result.

[0064] S26, the data processing device receives the audit result returned by the audit device. If the audit result is passed, the target management item data of the target subcategory under the target management item is updated to the target data.

[0065] S27, the data processing device determines the target system use case corresponding to the target subcategory from the system use case, and updates the data associated with the target system use case and the target management item through the target data.

[0066] In the embodiment of the present application, the target category includes a domain, a use case classification, a use case identifier, a use case stakeholder, a use case executor, or a use case field, etc. For example, when the target category is a domain, the target subcategory is the target domain (such as XX payment system, change, marketing, payment, etc.), and the target system use case is a system use case whose domain is the target domain in the system use case. Alternatively, when the target category is a use case classification, the target subcategory is the target use case classification (such as release test, XX collection, XX payment, etc.), and the target system use case is a system use case whose use case classification is the target use case classification in the system use case.

[0067] Alternatively, when the target category is use case stakeholder, the target subcategory is target use case stakeholder (e.g., XX user, XX merchant, XX bank, etc.), and the target system use case is the system use case whose use case stakeholder is the target use case stakeholder. When the target category is use case executor, the target subcategory is target use case executor (e.g., XX merchant, XX user, etc.), and the target system use case is the system use case whose use case executor is the target use case executor. When the target category is use case field, the target subcategory is target use case field, and the target system use case is the system use case that uses the target use case field in the system use case.

[0068] From the above content, it can be seen that the implementation of the embodiment of the present application can complete the update of the relevant data of all target system use cases corresponding to the target subcategory through a single update operation of the target management item data under the target management item for the target subcategory, which is conducive to improving the data update efficiency and accuracy for the system use cases.

[0069] Based on the description of the above data processing solution, the embodiment of the present application proposes a data processing method, which can be executed by the above-mentioned data processing device, see Figure 3 , the data processing method may include the following steps S301-S303:

[0070] S301: Displaying a metadata management page. This metadata management page includes multiple metadata management portals. Each metadata management portal is used to trigger the management of metadata for a specific category. In this embodiment of the present application, metadata categories may include any one or more of the following: domain, use case classification, use case identifier, use case stakeholder, use case actor, and use case field. The use case identifier may be a use case name, use case code, or the like.

[0071] For example, the metadata management page can be as follows Figure 4a As shown, the metadata management entrances include: "Domain", "Use Case Classification", "Use Case Name", "Stakeholder", "Executor", and "Field". The metadata management entrance "Domain" is used to trigger the management of metadata of the domain class, the metadata management entrance "Domain" is used to trigger the management of metadata of the domain category, the metadata management entrance "Use Case Classification" is used to trigger the management of metadata of the use case classification category, the metadata management entrance "Use Case Name" is used to trigger the management of metadata of the use case name category, the metadata management entrance "Stakeholder" is used to trigger the management of metadata of the use case stakeholder category, the metadata management entrance "Executor" is used to trigger the management of metadata of the use case executor category, and the metadata management entrance "Field" is used to trigger the management of metadata of the use case field category.

[0072] S302: When a trigger operation is detected for a target metadata management entry, at least one subcategory of the target category, at least one management item associated with the at least one subcategory, the management item data for each subcategory under each management item, and the update entry corresponding to each subcategory are displayed. The target category is the category of metadata that is triggered for management by the target metadata management entry, and the target metadata management entry is any one of the multiple metadata management entries. The trigger operation can be a click, press, or voice input operation on the target metadata management entry on the page.

[0073] For example, continue to refer to the above Figure 4aThe metadata management page shown includes metadata management entries: "Domain", "Use Case Classification", "Use Case Name", "Stakeholders", "Actors", and "Fields". When the user clicks on the metadata management entry: "Domain", the data processing device can display at least one subcategory of the "Domain" category (i.e., the target category) (including: commercial cash register APP payment domain, XX payment system 1 domain, and XX payment system 2 domain), at least one management item involved in at least one subcategory (including: importance, domain Chinese name, domain English name, domain person in charge, domain type, creator, last modifier, operation, etc.), management item data of each subcategory under each management item, and the update entry corresponding to each subcategory (i.e. Figure 4a The display effect can be referred to Figure 4a shown.

[0074] Alternatively, when the user clicks on the metadata management portal: "Use Case Classification", the content displayed by the data processing device can be as follows: Figure 4b As shown, specifically, at least one subcategory of the "Use Case Classification" category (i.e., target category) (including: direct merchant collection, XX payment, and XX collection), at least one management item involved in at least one subcategory (including: category name, parent node (the parent node is used to represent the field to which the corresponding use case classification belongs), business sequence diagram, creator, last modifier, operation, etc.), management item data of each subcategory under each management item, and the update entry corresponding to each subcategory (i.e. Figure 4b ).

[0075] When the user clicks the metadata management entry: "Use Case Name", the content displayed by the data processing device can be as follows Figure 4c Specifically, the metadata management page can display at least one subcategory (including: collection, payment, etc.) of the "use case name" category (i.e., target category), at least one management item involved in at least one subcategory (including: importance, executor, use case name, involved scenarios, use case person in charge, last modifier, operation, etc.), the management item data of each subcategory under each management item, and the update entry corresponding to each subcategory (i.e. Figure 4c ).

[0076] When the user clicks on the metadata management portal: "Stakeholders", the content displayed by the data processing device can be as follows Figure 4dSpecifically, the metadata management page can display at least one subcategory (including: merchant A, bank B, etc.) of the "stakeholder" category (i.e., target category), at least one management item involved in at least one subcategory (including: stakeholder name, creator, last modifier, operation, etc.), management item data of each subcategory under each management item, and the update entry corresponding to each subcategory (i.e., Figure 4d ).

[0077] When the user clicks the metadata management entry: "Executor", the content displayed by the data processing device can be as follows Figure 4e Specifically, the metadata management page can display at least one subcategory (including: XX payment system, XX marketing system, etc.) of the "executor" category (i.e., target category), at least one management item involved in at least one subcategory (including: executor name, category, creator, last modifier, operation, etc.), management item data of each subcategory under each management item, and the update entry corresponding to each subcategory (i.e., Figure 4e ).

[0078] When the user clicks on the metadata management entry: "Field", the content displayed by the data processing device can be as follows Figure 4f Specifically, the metadata management page can display at least one subcategory (including: first field, second field, etc.) of the "field" category (i.e., target category), at least one management item (including: field name, variable name, composition, length, creator, last modifier, operation, etc.) involved in at least one subcategory, the management item data of each subcategory under each management item, and the update entry corresponding to each subcategory (i.e., Figure 4f ).

[0079] S303: triggering the target management item data of the target subcategory under the target management item to be updated to the target data through the update entry corresponding to the target subcategory.

[0080] In one embodiment, the data processing device may trigger the display of a metadata update window through an update entry corresponding to the target subcategory, and the user may update the target management item data under the target management item of the target subcategory to the target data in the metadata update window.

[0081] S304: Determine the target system use case corresponding to the target subcategory from the system use case, and update the data associated with the target system use case and the target management item through the target data.

[0082] Among them, the above-mentioned target categories include domains, use case classifications, use case identifiers, use case stakeholders, use case executors or use case fields, etc. In one embodiment, when the target category is a domain, the target subcategory is the target domain (such as XX payment system, change, marketing, payment, etc.), the target management item can include the Chinese name of the domain, the English name of the domain, etc., and the target system use case is the system use case whose domain in the system use case is the target domain. Assuming that the target management item is the Chinese name of the domain, the content of this update is: update the Chinese name of the domain from "A payment system" (target management item data under the target management item) to "XA payment system" (i.e. target data), then the data processing device can update the Chinese name of the domain corresponding to the target system use case (i.e. the data associated with the target system use case and the target management item) from "A payment system" to "XA payment system".

[0083] In another embodiment, when the target category is a use case classification, the target subcategory is a target use case classification (e.g., direct merchant collection, XX payment, XX collection, etc.), the target management item may include a classification name, a parent node, etc., and the target system use case is a system use case whose use case classification in the system use case is the target use case classification. Assuming the target management item is a classification name, the content of this update is: updating the classification name from "direct merchant collection" (target management item data under the target management item) to "XX merchant collection" (i.e., target data). Then, the data processing device can update the classification name corresponding to the target system use case (i.e., the data associated with the target system use case and the target management item) from "direct merchant collection" to "XX merchant collection."

[0084] In another embodiment, when the target category is a use case name, the target subcategory is the target use case name (e.g., collection, payment, etc.), the target management item can include the use case name, etc., and the target system use case is all system use cases whose use case name is the target use case name. Assuming the target management item is a use case name, the content of this update is: updating the use case name from "collection" (the target management item data under the target management item) to "XX collection" (i.e., the target data). Then, the data processing device can update the use case names corresponding to all target system use cases (i.e., the data associated with the target system use case and the target management item) from "collection" to "XX collection."

[0085] In another embodiment, when the target category is use case stakeholder, the target subcategory is target use case stakeholder (e.g., XX user, XX merchant, XX bank, etc.), and the target system use case is a system use case whose use case stakeholder is the target use case stakeholder. Assuming the target management item is a stakeholder name, and the content of this update is to update the stakeholder name from "Merchant A" (target management item data under the target management item) to "Merchant B" (i.e., target data), the data processing device can update the stakeholder names corresponding to all target system use cases (i.e., the data associated with the target system use case and the target management item) from "Merchant A" to "Merchant B."

[0086] In another embodiment, when the target category is use case executor, the target subcategory is target use case executor (e.g., XX merchant, XX user, etc.), and the target system use case is a system use case whose use case executor is the target use case executor. Assuming the target management item is the executor name, the content of this update is: updating the executor name from "XX payment system" (target management item data under the target management item) to "A payment system" (i.e., target data). Then, the data processing device can update the executor names corresponding to all target system use cases (i.e., the data associated with the target system use case and the target management item) from "XX payment system" to "A payment system."

[0087] In another embodiment, when the target category is a use case field, the target subcategory is a target use case field, and the target system use case is a system use case that uses the target use case field within the system use case. Assuming the target management item is a variable name, the content of this update is: updating the variable name from "1****" (target management item data under the target management item) to "2****" (i.e., target data). Then, the data processing device can update the variable names of the target use case fields corresponding to all target system use cases (i.e., the data associated with the target system use case and the target management item) from "1****" to "2****."

[0088] In an embodiment of the present application, a metadata management page including multiple metadata management entries can be displayed. When a trigger operation for a target metadata management entry is detected, at least one subcategory of the target category, at least one management item involved in at least one subcategory, management item data of each subcategory under each management item, and an update entry corresponding to each subcategory are displayed. Furthermore, the target management item data of the target subcategory under the target management item is updated to the target data through the update entry corresponding to the target subcategory, and the target system use case corresponding to the target subcategory is determined from the system use case, and the data associated with the target system use case and the target management item is updated through the target data. In this way, the relevant data of all target system use cases corresponding to the target subcategory can be updated through a single update operation for the target management item data of the target subcategory under the target management item, which is beneficial to improving the efficiency and accuracy of data updates for system use cases.

[0089] See Figure 5 , is a flow chart of another data processing method provided by an embodiment of the present application. The data processing method can be executed by the data processing device mentioned above, see Figure 5 , the data processing method may include the following steps S501-S504:

[0090] S501: Displaying a metadata management page, which includes multiple metadata management entries.

[0091] S502: When a trigger operation is detected for the target metadata management entry, at least one subcategory of the target category, at least one management item associated with the at least one subcategory, the management item data for each subcategory under each management item, and the update entry corresponding to each subcategory are displayed. The specific implementation of steps S501 and S502 can be found in the description of steps S301 and S302 in the above embodiment and will not be repeated here.

[0092] S503: When a trigger operation for an update entry corresponding to a target subcategory is detected, a metadata update window is displayed, which includes target management items. The trigger operation for the update entry includes a click, press, voice input, etc. on the update entry.

[0093] S504: inputting update data including target data in the metadata update window, where the target data is used to update the target management item data under the target management item of the target subcategory.

[0094] S505: If the data format of the target data meets the corresponding format condition, a review request carrying the updated data is triggered to be sent to the review device, so that the review device reviews the updated data and returns the review result.

[0095] In one embodiment, before the data processing device triggers sending an audit request carrying updated data to the audit device, it can also verify whether the data format of the target data meets the corresponding format conditions. If so, it triggers the execution of the step of sending an audit request carrying updated data to the audit device.

[0096] It is understandable that for different target data, the corresponding designated data formats are different. For example, in the embodiment of the present application, the correspondence between each target data and the designated data format can be as shown in Table 1.

[0097] Table 1

[0098] Target data Format conditions Field Chinese name Globally unique Field English name Globally unique and does not contain Chinese characters Use case category name The use case category name is unique in the same field Use Case Name The use case name is unique within the same use case category Executor Name Globally unique Field Name Globally unique Field length A pure number or a range of values

[0099] S506: receiving the audit result returned by the audit device. If the audit result is passed, updating the target management item data of the target subcategory under the target management item to the target data.

[0100] In the embodiment of the present application, the metadata update window triggered by different update entrances displays different contents. For example, see Figure 6a As shown, assuming the target category is domain, the target subcategory is the commercial cashier APP payment domain, the target management items include the domain Chinese name and the domain English name, and the update entry corresponding to the target subcategory is Figure 6a Update entry 1 in the update, through the update entry 1 can trigger the display Figure 6a In Metadata Update Window 1, users can enter the new domain Chinese name and domain English name (i.e., target data) through Metadata Update Window 1. Furthermore, by clicking the "Confirm and Submit for Review" button, a review request carrying the updated data is sent to the review device, allowing the review device to review the updated data and return the review result. If the review result is approved, the original domain Chinese name "Commercial Cashier APP Payment" and domain English name "xx-pay" are updated with the new domain Chinese name and domain English name.

[0101] For example, see Figure 6b As shown, assuming the target category is use case classification, the target subcategory is direct merchant payment collection, the target management item includes the use case category name, and the update entry corresponding to the target subcategory is Figure 6b Update entry 2 in the update, through the update entry 2 can trigger the display Figure 6bIn Metadata Update Window 2, users can enter a new use case category name (i.e., target data). Furthermore, by clicking the "Confirm and Submit for Review" button, a review request containing the updated data is sent to the review device, which then reviews the updated data and returns the review result. If the review result is "approved," the original use case category name, "Direct Merchant Payment Collection," is updated with the new use case category name.

[0102] In one embodiment, the update data may include target data and the reason for this update. Figure 6b It can be seen intuitively that the data entered in the metadata update window can include not only the target data (such as the new use case category name) used to update the target management item data of the target subcategory under the target management item, but also the reason for this update (i.e., the reason for modification). In this case, the audit request triggered to be sent to the audit device can not only carry the target data, but also the reason for this update, so as to facilitate the review by the auditor corresponding to the audit device.

[0103] In one embodiment, the above review request may also carry the user information of the user who operated the update and the update time, so that the reviewer can understand who submitted the update and the specific time of the update. For example, the review page displayed by the review device may be as follows: Figure 6c As shown, the auditor can view the audit tasks to be audited through the audit device, conduct the audit, and submit the audit results (pass or reject).

[0104] S507: Determine the target system use case corresponding to the target subcategory from the system use case, and update the data associated with the target system use case and the target management item using the target data. The specific implementation of step S507 can be found in the description of step S304 in the above embodiment, and will not be repeated here.

[0105] In one embodiment, the system use case includes multiple use cases, the target category is the use case classification, the target subcategory is the target use case classification, the metadata update window also includes a business sequence diagram input item, the business sequence diagram input item is used to trigger the input of the business sequence diagram corresponding to the execution system use case, the update data includes the business sequence diagram, and the target system use case corresponding to the target subcategory is determined from the system use case, including: identifying the business sequence diagram to determine the use case classification to which each system use case belongs; further, classifying the use case into the system use case of the target use case classification from each system use case as the target system use case.

[0106] Among them, the business sequence diagram is used to describe the implementation process of the system use case, that is, the business process. For example, the business sequence diagram can be as follows Figure 6d As shown. Each arrow in the business sequence diagram corresponds to a system use case. Figure 6d The system use cases include: repayment, obtaining payment order receipt, payment collection, querying authorized bank cards, and displaying the payment collection interface. The data processing device can intuitively determine the use case category to which each system use case belongs through this business sequence diagram.

[0107] In one embodiment, when the data processing device executes the above step S502 and detects a trigger operation for the target metadata management entry, it can also detect the management status of each management item data corresponding to the above subcategories. If it is detected that the management status of any management item data corresponding to any subcategory is a modification status, the update entry corresponding to any subcategory is displayed in a first display mode, and the first display mode includes displaying in a first specified color and / or displaying in a first specified font to distinguish it from the update entries corresponding to other subcategories that are not in a modification status. In one embodiment, the update entry displayed in the first display mode is in an inoperable state, that is, when the user touches the update entry in an inoperable state, the data processing device will not respond. Alternatively, when the user touches the update entry in an inoperable state, the data processing device can output a prompt message to prompt that the management status of the corresponding management item data is a modification status.

[0108] For example, assuming that the first designated color is gray, the metadata management page is as follows: Figure 6a As shown in the figure above, the target category is the field, and any subcategory corresponding to the target category is: the commercial cashier APP payment field. When the data processing device detects that any management item data corresponding to the commercial cashier APP payment (such as the Chinese name of the field) is in a modified but not yet approved state, it can be determined that the management state of any management item data is the modified state. Further, in Figure 6a The page shown shows the updated entry 1 corresponding to the commercial cashier APP payment in grayscale.

[0109] In one embodiment, the data processing device can also traverse all system use cases, detect the association between each system use case in the system use case and the target subcategory in the target category, and if it is detected that no system use case in the system use case is associated with the target subcategory in the target category, then a deletion entry is added for the target subcategory, and the deletion entry is used to trigger the deletion of the management item data of the target subcategory under each management item. For example, see Figure 6a , assuming that the target category is domain and the target subcategory is the commercial cashier APP payment domain, when the data processing device detects that there is no system use case belonging to the commercial cashier APP payment domain, then it can be determined that there is no system use case in the system use case associated with the commercial cashier APP payment domain. Accordingly, a display deletion entry can be added for the commercial cashier APP payment domain (such as Figure 6aDelete entry 1).

[0110] Alternatively, in another embodiment, when a trigger operation is detected for a target metadata management entry, the association relationship between each subcategory and a system use case may also be detected. If it is detected that no system use case in the system use case is associated with the target subcategory in each subcategory, a deletion entry corresponding to the target subcategory is displayed in a second display mode. The second display mode includes displaying in a second specified color and / or in a second specified font, and the second display mode is different from the display mode of deletion entries corresponding to other subcategories that are associated with any system use case.

[0111] For example, assuming that the second display mode is displayed in black bold, continue to refer to Figure 6a , assuming that the target category is a domain and the target subcategory is a commercial cashier APP payment domain, when the data processing device detects that no system use case belongs to a domain that is a commercial cashier APP payment domain, then it can be determined that no system use case in the system use case is associated with the commercial cashier APP payment domain. Accordingly, the deletion entry corresponding to the XX payment system 1 can be displayed in a black bold display mode (such as Figure 6a For other subcategories that are associated with any system use case (e.g. Figure 6a The deletion entries corresponding to XX Payment System 1 and XX Payment System 2) are displayed in grayscale.

[0112] In one embodiment, when a trigger operation for a target metadata management entry is detected, an add entry may be displayed, which is used to trigger the addition of one or more new subcategories of management item data under each management item. Figure 4a to Figure 4f , the added entry can be, for example, "new field", "new category", "new stakeholder", "new executor", "new field" and so on.

[0113] In this embodiment of the present application, a data processing platform can be pre-deployed on the data processing device. The front-end code of the data processing platform is implemented based on the Vue open-source framework and the elementUI open-source components. It provides metadata management and approval-related pages, encapsulating various components to support metadata addition, deletion, modification, and query capabilities, as well as the status flow of corresponding approval forms. The back-end implementation of the data processing platform is based on the NodeJS Express framework, primarily providing interfaces for addition, deletion, and query, supporting metadata reading and writing capabilities, and the status change and cycle management of approval forms.

[0114] This data processing platform enables the full lifecycle management of metadata, enabling metadata to serve as a unified data source and enable linkage across system use cases and cross-use cases. This fundamentally reduces the impact of inconsistent and fragmented data sources, reducing duplication of effort and improving use case update efficiency. Specifically, the full lifecycle business process for metadata includes deleting, adding, and updating metadata. The overall process for deleting, adding, and updating can be found in the . Figure 7a to Figure 7c shown.

[0115] For example, see Figure 7d , assuming the target category is use case classification, users can Figure 7d Metadata management page (i.e. Figure 7d The delete entry shown in the figure above deletes one or more use case classification subcategories and triggers the review process. For another example, see Figure 7e , users can Figure 7e Metadata management page (i.e. Figure 7e Add one or more use case classification subcategories and trigger the review process.

[0116] In an embodiment of the present application, a data processing device displays a metadata management page including multiple metadata management entries. When a trigger operation is detected for a target metadata management entry, the device displays at least one subcategory of the target category, at least one management item associated with the at least one subcategory, management item data for each subcategory under each management item, and an update entry corresponding to each subcategory. Furthermore, when a trigger operation is detected for an update entry corresponding to a target subcategory, a metadata update window is displayed. Update data including the target data is entered in the metadata update window. If the data format of the target data meets the corresponding format conditions, a review request carrying the update data is sent to the review device, so that the review device reviews the update data and returns the review result. Upon receiving the review result returned by the review device, if the review result indicates approval, the target management item data for the target subcategory under the target management item is updated to the target data. Furthermore, the update entry corresponding to the target subcategory triggers the update of the target management item data for the target subcategory under the target management item to the target data, and a target system use case corresponding to the target subcategory is determined from the system use case. The target data is used to update the data associated with the target system use case and the target management item. In this way, the audit link for target data can be added. After the audit is passed, the data associated with the target system use case and the target management item can be updated through the target data, which is conducive to further improving the effectiveness of the system use case data update.

[0117] An embodiment of the present application further provides a computer storage medium, in which program instructions are stored. When the program instructions are executed, they are used to implement the corresponding methods described in the above embodiments.

[0118] See also Figure 8 , is a structural diagram of a data processing device in an embodiment of the present application. The data processing device in an embodiment of the present application can be set in the above-mentioned data processing device, or it can be a computer program (including program code) running in the data processing device.

[0119] In one implementation of the device of the embodiment of the present application, the device includes the following structure.

[0120] Display unit 80, for displaying a metadata management page, the metadata management page includes multiple metadata management entries, each metadata management entry is used to trigger the management of a category of metadata; metadata refers to data associated with a system use case;

[0121] The display unit 80 is further configured to, when a trigger operation is detected for a target metadata management entry, display at least one subcategory of the target category, at least one management item associated with the at least one subcategory, management item data for each subcategory under each management item, and an update entry corresponding to each subcategory; wherein the target category is the category of metadata that is triggered for management by the target metadata management entry;

[0122] The processing unit 81 is configured to trigger, through the update entry corresponding to the target subcategory, updating the target management item data of the target subcategory under the target management item to the target data;

[0123] The processing unit 81 is further configured to determine a target system use case corresponding to a target subcategory from the system use cases, and update data associated with the target system use case and the target management item using the target data.

[0124] In one embodiment, the data processing device further includes a communication unit 82 and a processing unit 81, which are specifically used to: when a trigger operation for an update entry corresponding to a target subcategory is detected, display a metadata update window through the display unit 80, and the metadata update window includes a target management item; input update data including target data in the metadata update window, and the target data is used to update the target management item data of the target subcategory under the target management item; trigger the communication unit 82 to send an audit request carrying the update data to the audit device, so that the audit device can audit the update data and return the audit result; receive the audit result returned by the audit device through the communication unit 82, and if the audit result is passed, update the target management item data of the target subcategory under the target management item to the target data.

[0125] In one embodiment, the target categories include domain, use case classification, use case identification, use case stakeholder, use case actor, or use case field;

[0126] When the target category is the field, the target subcategory is the target field, and the target system use case is a system use case in the system use case whose field is the target field;

[0127] When the target category is the use case classification, the target subcategory is the target use case classification, and the target system use case is a system use case in the system use case whose use case classification is the target use case classification;

[0128] When the target category is the use case stakeholder, the target subcategory is the target use case stakeholder, and the target system use case is the system use case whose use case stakeholder is the target use case stakeholder in the system use case;

[0129] When the target category is the use case executor, the target subcategory is the target use case executor, and the target system use case is a system use case in the system use case whose use case executor is the target use case executor;

[0130] When the target category is the use case field, the target subcategory is the target use case field, and the target system use case is a system use case that uses the target use case field in the system use case.

[0131] In one embodiment, the system use case includes multiple use cases, the target category is a use case classification, the target subcategory is a target use case classification, the metadata update window further includes a business sequence diagram input item, the business sequence diagram input item is used to trigger input execution of the business sequence diagram corresponding to the system use case, the update data includes the business sequence diagram, and the processing unit 81 is further specifically used to:

[0132] Obtaining and identifying the business sequence diagram from the updated data to determine the use case classification to which each system use case belongs;

[0133] The use cases are classified into a system use case classified as a target use case from among the system use cases and determined as a target system use case.

[0134] In one embodiment, the display unit 80 is specifically configured to:

[0135] Detecting the management status of each management item data corresponding to each subcategory;

[0136] If it is detected that the management status of any management item data corresponding to any subcategory is a modification status, the update entry corresponding to any subcategory is displayed in a first display mode, and the first display mode includes displaying in a first specified color and / or displaying in a first specified font.

[0137] In one embodiment, the processing unit 81 is also used to add a display deletion entry for the target subcategory through the display unit 80 if it is detected that there is no system use case in the system use case associated with the target subcategory in the target category. The deletion entry is used to trigger the deletion of the management item data of the target subcategory under each management item.

[0138] In one embodiment, the processing unit 81 is also used to detect the association relationship between each subcategory and the system use case when a trigger operation for the target metadata management entry is detected; if it is detected that there is no system use case in the system use case associated with the target subcategory in each subcategory, the deletion entry corresponding to the target subcategory is displayed in a second display mode through the display unit 80, and the second display mode includes displaying in a second specified color and / or displaying in a second specified font.

[0139] In one embodiment, the processing unit 81 is also used to display an add entry through the display unit 80 when a trigger operation for the target metadata management entry is detected, and the add entry is used to trigger the addition of one or more new subcategories of management item data under each management item.

[0140] In one embodiment, the processing unit 81 is further configured to trigger the communication unit 82 to execute the step of sending the audit request carrying the updated data to the audit device if the data format of the target data is verified to meet the corresponding format condition.

[0141] In the embodiments of the present application, the specific implementation of each of the above-mentioned units can refer to the description of the relevant contents in the embodiments corresponding to the aforementioned figures.

[0142] The data processing device in the embodiment of the present application can display a metadata management page including multiple metadata management entries. When a trigger operation for a target metadata management entry is detected, at least one subcategory of the target category, at least one management item involved in at least one subcategory, management item data of each subcategory under each management item, and an update entry corresponding to each subcategory are displayed. Furthermore, the target management item data of the target subcategory under the target management item is updated to the target data through the update entry corresponding to the target subcategory, and the target system use case corresponding to the target subcategory is determined from the system use case, and the data associated with the target system use case and the target management item is updated through the target data. In this way, the relevant data of all target system use cases corresponding to the target subcategory can be updated through a single update operation for the target management item data of the target subcategory under the target management item, which is beneficial to improving the data update efficiency and accuracy for the system use case.

[0143] See also Figure 9 , is a schematic diagram of the structure of a data processing device according to an embodiment of the present application. The data processing device herein includes, but is not limited to, tablet computers, laptop computers, notebook computers, and desktop computers, among others. The data processing device according to the present application includes a power supply module and other structures, and includes a processor 90, a storage device 91, an input device 92, an output device 93, and a communication interface 94. The processor 90, storage device 91, input device 92, output device 93, and communication interface 94 can exchange data with each other, and the processor 90 implements the corresponding data processing functions.

[0144] The storage device 91 may include a volatile memory, such as a random-access memory (RAM); the storage device 91 may also include a non-volatile memory, such as a flash memory, a solid-state drive (SSD), etc.; the storage device 91 may also include a combination of the above types of memory.

[0145] The processor 90 may be a central processing unit (CPU). In one embodiment, the processor 90 may also be a graphics processing unit (GPU). The processor 90 may also be a combination of a CPU and a GPU. In a data processing device, multiple CPUs and GPUs may be included as needed to perform corresponding data processing.

[0146] The input device 92 may refer to a display screen, a fingerprint collector, etc., which may be used to detect user input-related operations (such as the target metadata management entry, the trigger operation of the update entry input corresponding to the target subcategory, etc.), and the output device 93 may include a display (LCD, etc.), a speaker, etc.

[0147] In one embodiment, the storage device 91 is used to store program instructions. The processor 90 can call the program instructions to implement the various methods mentioned above in the embodiments of the present application.

[0148] In a first possible implementation, the processor 90 of the data processing device calls the program instructions stored in the storage device 91 to:

[0149] The metadata management page is displayed through the output device 93, and the metadata management page includes multiple metadata management entries, one metadata management entry is used to trigger the management of a category of metadata; metadata is used to describe data associated with system use cases; when a trigger operation for the target metadata management entry is detected, at least one subcategory of the target category, at least one management item involved in at least one subcategory, management item data of each subcategory under each management item, and an update entry corresponding to each subcategory are displayed through the output device 93; wherein, the target category is the category of metadata triggered by the target metadata management entry; the update entry corresponding to the target subcategory triggers the target management item data of the target subcategory under the target management item to be updated to the target data; the target system use case corresponding to the target subcategory is determined from the system use case, and the data associated with the target system use case and the target management item is updated through the target data.

[0150] In one embodiment, the processor 90 is specifically used to: when a trigger operation for an update entry corresponding to a target subcategory is detected, display a metadata update window through an output device 93, wherein the metadata update window includes a target management item; input update data including target data in the metadata update window, wherein the target data is used to update the target management item data of the target subcategory under the target management item; trigger the communication interface 94 to send an audit request carrying the update data to the audit device, so that the audit device can audit the update data and return the audit result; receive the audit result returned by the audit device through the communication interface 94, and if the audit result is passed, update the target management item data of the target subcategory under the target management item to the target data.

[0151] In one embodiment, the target categories include domain, use case classification, use case identification, use case stakeholder, use case actor, or use case field;

[0152] When the target category is the field, the target subcategory is the target field, and the target system use case is a system use case in the system use case whose field is the target field;

[0153] When the target category is the use case classification, the target subcategory is the target use case classification, and the target system use case is a system use case in the system use case whose use case classification is the target use case classification;

[0154] When the target category is the use case stakeholder, the target subcategory is the target use case stakeholder, and the target system use case is the system use case whose use case stakeholder is the target use case stakeholder in the system use case;

[0155] When the target category is the use case executor, the target subcategory is the target use case executor, and the target system use case is a system use case in the system use case whose use case executor is the target use case executor;

[0156] When the target category is the use case field, the target subcategory is the target use case field, and the target system use case is a system use case that uses the target use case field in the system use case.

[0157] In one embodiment, the system use case includes multiple use cases, the target category is a use case classification, the target subcategory is a target use case classification, the metadata update window further includes a business sequence diagram input item, the business sequence diagram input item is used to trigger input execution of the business sequence diagram corresponding to the system use case, the update data includes the business sequence diagram, and the processor 90 is further specifically configured to:

[0158] Obtaining and identifying the business sequence diagram from the updated data to determine the use case classification to which each system use case belongs;

[0159] The use cases are classified into a system use case classified as a target use case from among the system use cases and determined as a target system use case.

[0160] In one embodiment, the output device 93 is specifically configured to:

[0161] Detecting the management status of each management item data corresponding to each subcategory;

[0162] If it is detected that the management status of any management item data corresponding to any subcategory is a modification status, the update entry corresponding to any subcategory is displayed in a first display mode, and the first display mode includes displaying in a first specified color and / or displaying in a first specified font.

[0163] In one embodiment, the processor 90 is also used to add a display deletion entry for the target subcategory through the output device 93 if it is detected that there is no system use case in the system use case associated with the target subcategory in the target category, and the deletion entry is used to trigger the deletion of the management item data of the target subcategory under each management item.

[0164] In one embodiment, the processor 90 is further used to detect the association relationship between each subcategory and the system use case when a trigger operation for the target metadata management entry is detected; if it is detected that there is no system use case in the system use case associated with the target subcategory in each subcategory, the deletion entry corresponding to the target subcategory is displayed in a second display mode through the output device 93, and the second display mode includes displaying in a second specified color and / or displaying in a second specified font.

[0165] In one embodiment, the processor 90 is further configured to display an add entry through the output device 93 when a trigger operation for the target metadata management entry is detected, wherein the add entry is configured to trigger the addition of one or more new subcategories of management item data under each management item.

[0166] In one embodiment, the processor 90 is further configured to trigger the communication interface 94 to execute the step of sending the audit request carrying the updated data to the audit device if the data format of the target data is verified to meet the corresponding format condition.

[0167] In the embodiment of the present application, the specific implementation of the above-mentioned processor 90 can refer to the description of the relevant content in the embodiments corresponding to the aforementioned figures.

[0168] The data processing device in the embodiment of the present application can display a metadata management page including multiple metadata management entries. When a trigger operation for a target metadata management entry is detected, at least one subcategory of the target category, at least one management item involved in at least one subcategory, management item data of each subcategory under each management item, and an update entry corresponding to each subcategory are displayed. Furthermore, the target management item data of the target subcategory under the target management item is updated to the target data through the update entry corresponding to the target subcategory, and the target system use case corresponding to the target subcategory is determined from the system use case, and the data associated with the target system use case and the target management item is updated through the target data. In this way, the relevant data of all target system use cases corresponding to the target subcategory can be updated through a single update operation for the target management item data of the target subcategory under the target management item, which is conducive to improving the efficiency and accuracy of data updates for system use cases.

[0169] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing the relevant hardware through a computer program. The described program can be stored in a computer-readable storage medium. When executed, the program can include the processes in the above-described method embodiments. The storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0170] The above disclosure is only part of the embodiments of the present application, and it is certainly not intended to limit the scope of the rights of the present application. A person skilled in the art can understand that all or part of the processes of the above embodiments and equivalent changes made in accordance with the claims of the present application are still within the scope of the invention.

Claims

1. A data processing method, characterized in that: include: Displaying a metadata management page, wherein the metadata management page includes a plurality of metadata management entries, and each metadata management entry is used to trigger management of metadata of a category; The metadata is used to describe data associated with the system use case; When a trigger operation for a target metadata management entry is detected, at least one subcategory of the target category, at least one management item related to the at least one subcategory, management item data of each subcategory under each management item, and an update entry corresponding to each subcategory are displayed; wherein the target category is the category of metadata whose management is triggered by the target metadata management entry; triggering, through an update entry corresponding to the target subcategory, to update the target management item data of the target subcategory under the target management item to the target data; wherein, triggering, through the update entry corresponding to the target subcategory, to display a metadata update window, wherein the metadata update window is used to input update data, wherein the update data includes the target data; A target system use case corresponding to the target subcategory is determined from the system use cases, and data associated with the target system use case and the target management item is updated using the target data.

2. The method according to claim 1, wherein The updating of the target management item data of the target subcategory under the target management item to the target data is triggered by the update entry corresponding to the target subcategory, including: When a trigger operation for an update entry corresponding to the target subcategory is detected, a metadata update window is displayed, wherein the metadata update window includes a target management item; Inputting update data including target data in the metadata update window, wherein the target data is used to update target management item data of the target subcategory under the target management item; Triggering the sending of an audit request carrying the updated data to the audit device, so that the audit device can audit the updated data and return the audit result; An audit result returned by the audit device is received. If the audit result is passed, the target management item data of the target subcategory under the target management item is updated to the target data.

3. The method according to claim 1 or 2, wherein: The target categories include domain, use case classification, use case identification, use case stakeholders, use case performers or use case fields; When the target category is the field, the target subcategory is the target field, and the target system use case is a system use case in the system use case whose field is the target field; When the target category is the use case classification, the target subcategory is the target use case classification, and the target system use case is a system use case in the system use case whose use case classification is the target use case classification; When the target category is the use case stakeholder, the target subcategory is the target use case stakeholder, and the target system use case is the system use case whose use case stakeholder is the target use case stakeholder in the system use case; When the target category is the use case executor, the target subcategory is the target use case executor, and the target system use case is a system use case in the system use case whose use case executor is the target use case executor; When the target category is the use case field, the target subcategory is the target use case field, and the target system use case is a system use case that uses the target use case field in the system use case.

4. The method according to claim 2, wherein The system use case includes a plurality of use cases, the target category is a use case classification, the target subcategory is a target use case classification, the metadata update window further includes a business sequence diagram input item, the business sequence diagram input item is used to trigger input and execute the business sequence diagram corresponding to the system use case, the update data includes the business sequence diagram, and determining the target system use case corresponding to the target subcategory from the system use case includes: Obtaining and identifying the business sequence diagram from the updated data to determine the use case classification to which each system use case belongs; The use cases are classified into a system use case classified as a target use case from among the system use cases and determined as a target system use case.

5. The method according to claim 1, wherein The update entry corresponding to each subcategory is displayed, including: Detecting the management status of each management item data corresponding to each subcategory; If it is detected that the management status of any management item data corresponding to any subcategory is a modification status, the update entry corresponding to any subcategory is displayed in a first display mode, and the first display mode includes displaying in a first specified color and / or displaying in a first specified font.

6. The method according to claim 1, wherein The method further comprises: If it is detected that no system use case in the system use case is associated with the target subcategory in the target category, a deletion entry is added for the target subcategory, and the deletion entry is used to trigger the deletion of the management item data of the target subcategory under each management item.

7. The method according to claim 1, wherein The method further comprises: When a trigger operation for a target metadata management portal is detected, detecting associations between the subcategories and the system use cases; If it is detected that no system use case in the system use case is associated with the target subcategory in each subcategory, the deletion entry corresponding to the target subcategory is displayed in a second display mode, and the second display mode includes displaying in a second specified color and / or displaying in a second specified font.

8. The method according to claim 1, wherein The method further comprises: When a trigger operation for the target metadata management entry is detected, an add entry is displayed, and the add entry is used to trigger the addition of one or more new subcategories of management item data under each management item.

9. The method according to claim 2, wherein Before triggering the sending of the audit request carrying the updated data to the audit device, the method further includes: If it is verified that the data format of the target data meets the corresponding format condition, the step of sending the audit request carrying the updated data to the audit device is triggered.

10. A data processing device, characterized in that: include: A display unit, configured to display a metadata management page, wherein the metadata management page includes a plurality of metadata management entries, each metadata management entry being configured to trigger management of a category of metadata; the metadata being data associated with a system use case; The display unit is further configured to, when a trigger operation for a target metadata management entry is detected, display at least one subcategory of the target category, at least one management item related to the at least one subcategory, management item data of each subcategory under each management item, and an update entry corresponding to each subcategory; wherein the target category is the category of metadata whose management is triggered by the target metadata management entry; a processing unit, configured to trigger, through an update entry corresponding to the target subcategory, updating the target management item data of the target subcategory under the target management item to target data; wherein, the update entry corresponding to the target subcategory triggers display of a metadata update window, wherein the metadata update window is used to input update data, wherein the update data includes the target data; The processing unit is further configured to determine a target system use case corresponding to the target subcategory from system use cases, and update data associated with the target system use case and the target management item using the target data.

11. A data processing device, characterized in that: The data processing device includes a processor and a storage device, which are connected to each other, wherein the storage device is used to store a computer program, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method according to any one of claims 1 to 9.

12. A computer storage medium, characterized in that The computer storage medium stores program instructions, which, when executed, are used to implement the method according to any one of claims 1 to 9.

13. A computer program product comprising computer instructions, characterized in that When the computer instructions are executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images