Flow chart automatic verification method and device, computer equipment and storage medium

Abstract

The invention relates to an automatic checking method and device for a flow chart, computer equipment and a storage medium. The automatic checking method comprises the steps that global information of the flow chart in a flow engine is recognized and checked; identifying each node path of the flow chart, and starting from a head node of the flow chart, carrying out reachability analysis verification on all nodes of the flow chart based on each node path; according to each node path, carrying out logical verification on a dependency relationship of front and back configurations of each node of the flow chart; and performing logical verification on the node content of each node of the flow chart. According to the method, the flow chart in the flow engine can be automatically checked, manual rechecking and checking are not needed, and the checking accuracy and efficiency of the flow chart can be improved.

Description

Technical Field

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

[0002] At present, process engine design is widely used in various companies. However, it also brings some problems during use: the flowchart is drawn manually, and the review is also based on personal experience to conduct a superficial verification of the entire flowchart. This method has extremely high requirements for individuals and has the following problems:

[0003] 1. Subjective bias: Personal understanding may be biased, resulting in the interpretation and verification of the business process diagram being affected by subjective judgment.

[0004] 2. Inefficiency: Manual inspection often takes a long time, especially for complex business processes, which may take a lot of time to understand and analyze.

[0005] 3. Error-prone: Manual inspection is easily affected by factors such as fatigue and distraction, and may miss some details or misinterpret the information in the flowchart.

[0006] 4. Lack of consistency: Different inspectors may have different understandings and judgments of the same flowchart, resulting in a lack of consistency in the verification results.

[0007] 5. Difficulty in handling complex logic: For business process diagrams that contain complex logical judgments and branches, manual inspection may find it difficult to fully cover all possible paths and scenarios.

[0008] 6. Difficulty in updating and maintenance: When business processes change, manual checks need to be repeated, which may lead to increased maintenance costs.

[0009] 7. Lack of systematicity: Manual inspection may lack systematic methodological support, resulting in incomplete inspection or duplication of work.

[0010] 8. Difficult to quantify: The results of manual inspection are often difficult to quantify, which may affect subsequent process improvements and decision-making.

[0011] 9. Limitations in professional capabilities: The professional knowledge and experience of inspectors may limit the discovery and resolution of deep-seated problems in business process diagrams.

[0012] 10. Reliance on personal experience: Manual inspection relies heavily on the inspector’s personal experience, which may lead to neglect of new or uncommon issues. Summary of the invention

[0013] Based on this, it is necessary to provide a flowchart automatic verification method, device, computer equipment and storage medium to address the above technical problems, which can automatically verify the flowchart in the process engine without manual review and verification, and can improve the accuracy and efficiency of flowchart verification.

[0014] A flowchart automatic verification method includes: identifying and verifying the global information of the flowchart in a process engine; identifying each node path of the flowchart, starting from the head node of the flowchart, and performing reachability analysis and verification on all nodes of the flowchart based on each node path; performing logical verification on the dependency relationship of the front and back configurations of each node of the flowchart according to each node path; and performing logical verification on the node content of each node of the flowchart.

[0015] In one embodiment, the global information of the flowchart in the process engine is identified and verified, including: identifying the global information configuration component in the configuration interface of the process engine; reading the global information from the global information configuration component and verifying the global information.

[0016] In one of the embodiments, the global information configuration component includes a process name component, a validity period component and a business scenario component. Global information is read from the global information configuration component and global information verification is performed, including: reading the process name from the process name component, verifying the validity of the process name and verifying whether the process name complies with the naming specification; reading the validity period from the validity period component, verifying the validity of the input validity period value and verifying whether the validity period complies with the rules; reading business scenario information from the business scenario component, verifying the validity of the business scenario information and verifying whether the business scenario information complies with the rules.

[0017] In one of the embodiments, a reachability analysis check is performed on all nodes of the flowchart based on each node path, including: checking the connection lines between each node based on each node path; if there are extra connection lines or unconnected lines, then determining that the reachability analysis results of the previous and next nodes corresponding to the extra connection lines or unconnected lines are infeasible.

[0018] In one of the embodiments, the dependency relationship includes the causal relationship before and after the nodes and the constraints between the nodes, and a logical check is performed on the dependency relationship of the before and after configurations of each node of the flowchart according to each node path, including: a logical check is performed on the causal relationship before and after the nodes of each node of the flowchart and the constraints between the nodes according to each node path.

[0019] In one embodiment, the node-by-node causal relationship includes a random probability relationship between the nodes, and the constraints between the nodes include node flow conditions. The node-by-node causal relationship and the constraints between the nodes of the flowchart are logically checked according to the paths of each node, including: identifying the random nodes of the flowchart and all the first flow nodes of the random nodes, and the random nodes flow to any first flow node according to the random probability; obtaining the probability value of the random nodes flowing to each first flow node, accumulating the probability values ​​of all the first flow nodes, and logically checking the random nodes and all the first flow nodes based on the accumulated value; identifying the conditional nodes of the flowchart and all the second flow nodes of the conditional nodes, and the conditional nodes refer to the nodes that flow to the corresponding second flow nodes according to predetermined conditions; identifying all the node flow conditions of the conditional nodes, and logically checking the conditional nodes and all the second flow nodes according to whether there is a corresponding relationship between the flow conditions of each node and each second flow node.

[0020] In one of the embodiments, a flowchart automatic verification method further includes: collecting variables configured for each path according to each node path; and identifying whether the format of the configured variables meets the format requirements.

[0021] A flow chart automatic verification device comprises: a global information verification module for identifying and verifying the global information of the flow chart in the process engine; a node verification module for identifying each node path of the flow chart, starting from the head node of the flow chart, and performing reachability analysis verification on all nodes of the flow chart based on each node path; a node dependency verification module for performing logical verification on the dependency relationship of the front and back configurations of each node of the flow chart according to each node path; and a node content verification module for performing logical verification on the node content of each node of the flow chart.

[0022] A computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of any of the above-mentioned embodiments are implemented.

[0023] A computer-readable storage medium stores a computer program, which implements the steps of any of the above-mentioned method embodiments when the computer program is executed by a processor.

[0024] The above-mentioned flowchart automatic verification method, device, computer equipment and storage medium identify and verify the global information of the flowchart in the process engine; identify each node path of the flowchart, start from the head node of the flowchart, and perform reachability analysis and verification on all nodes of the flowchart based on each node path; perform logical verification on the dependency relationship of the front and back configurations of each node of the flowchart according to each node path; and perform logical verification on the node content of each node of the flowchart. Therefore, the flowchart can be automatically verified without manual review and verification, which can improve the accuracy and efficiency of flowchart verification. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 An application environment diagram of a flowchart automation verification method in an embodiment;

[0026] Figure 2 A schematic diagram of a flowchart automation verification method in one embodiment;

[0027] Figure 3 A schematic diagram of an interface of a flow chart configuration interface of a process engine in one embodiment;

[0028] Figure 4 A flowchart diagram of a specific example of a flowchart automation verification method in an embodiment;

[0029] Figure 5 It is a structural block diagram of a flow chart automatic verification device in one embodiment;

[0030] Figure 6 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0032] The present application provides a flowchart automatic verification method, which is applied to Figure 1 In the application environment shown. Figure 1 As shown, the terminal 100 is used to implement a flowchart automatic verification method of the present application. Figure 1As shown, a process engine is installed in the terminal 100. After the user starts the process engine in the terminal 100, the terminal 100 displays a flowchart drawing interface, and the user can draw a flowchart in the flowchart drawing interface. Furthermore, the terminal 100 executes a flowchart automatic verification method of the present application to automatically verify the flowchart drawn by the user. Specifically, the terminal 100 identifies and verifies the global information of the flowchart in the process engine; identifies each node path of the flowchart, starting from the head node of the flowchart, and performs reachability analysis and verification on all nodes of the flowchart based on each node path; performs a logical verification on the dependency relationship of the front and back configurations of each node of the flowchart according to each node path; and performs a logical verification on the node content of each node of the flowchart. Among them, the terminal 100 can be a mobile device such as a laptop computer, a desktop computer, a mobile phone, etc.

[0033] In one embodiment, Figure 2 As shown, a flowchart automatic verification method is provided, which is applied to Figure 1 The terminal 100 in FIG. 1 is taken as an example to illustrate the method, which includes the following steps:

[0034] S202, identifying and verifying the global information of the flowchart in the process engine.

[0035] In this embodiment, the process engine is used to provide basic functional components for flowchart drawing to generate a flowchart. Global information is the overall architecture information of the flowchart configured by the user. For example, the global information includes the name of the configured flowchart, the validity period of the flowchart, and the business scenario applicable to the flowchart.

[0036] In one embodiment, the global information of the flowchart in the process engine is identified and verified, including: identifying the global information configuration component in the configuration interface of the process engine; reading the global information from the global information configuration component and verifying the global information.

[0037] In an example of the present implementation, the global information configuration component includes a process name component, a validity period component, and a business scenario component. Global information is read from the global information configuration component and global information verification is performed, including: reading the process name from the process name component, verifying the validity of the process name, and verifying whether the process name complies with the naming specifications; reading the validity period from the validity period component, verifying the validity of the input validity period value, and verifying whether the validity period complies with the rules; reading business scenario information from the business scenario component, verifying the validity of the business scenario information, and verifying whether the business scenario information complies with the rules.

[0038] In this embodiment, Figure 3As shown, the module A part of the interface provides the basic information of the flow chart plan / global information configuration component, and the user can configure the global information independently in the module A part. Figure 3 As shown, the global information configuration component includes a process name component, an effective period component, and a business scenario component. For example, the process name component is the name of the business plan, in which the user can select or enter the name of the self-configured flowchart. In the business scenario component, the user can select or enter the business scenario information corresponding to the flowchart.

[0039] For the process name of the flowchart, pre-set its validity and naming rules. After reading the process name from the process name component, check its validity and whether it complies with the naming conventions. Similarly, check the validity of the validity period and whether it complies with the validity period setting rules. Check the validity of the business scenario information and check whether the business scenario information complies with the rules. Specifically, the global basic information check includes checking the name of the process, validity period and other mandatory items. For example, check whether it is input, whether the input value is valid, whether it complies with the rules, etc.

[0040] It can automatically identify and verify the global information of the flowchart in the process engine, without manual verification, to avoid the flowchart configuration being non-compliant due to the global information not meeting the requirements.

[0041] S204, identifying each node path of the flowchart, starting from the head node of the flowchart, and performing reachability analysis and verification on all nodes of the flowchart based on each node path.

[0042] In this embodiment, each node in the flowchart is connected in order through a node path. Starting from the head node, all nodes of the flowchart are identified according to each node path, and reachability analysis and verification are performed on all nodes based on each node path. Specifically, the flowchart is analyzed according to each node path, starting from the head node, and reachability analysis is performed on all nodes on the entire flowchart to ensure that each node has a connecting line that can be reached.

[0043] In one embodiment, a reachability analysis check is performed on all nodes of the flowchart based on each node path, including: checking the connection lines between each node based on each node path; if there are redundant connection lines or unconnected lines, then determining that the reachability analysis results of the previous and next nodes corresponding to the redundant connection lines or unconnected lines are infeasible.

[0044] Specifically, we analyze the flow chart according to the path of each node, starting from the head node, and perform reachability analysis on all nodes on the entire flow chart to ensure that each node has a connection that can be reached. Figure 3As shown, the module B displayed in the interface provides an example of a connection line between node paths. That is, if the connection line between two nodes is not connected, the corresponding previous and next nodes are unreachable. In addition, if there are redundant connection lines between two nodes, this also means that the two nodes are unreachable.

[0045] It can automatically perform reachability analysis and verification on all nodes of the flowchart based on the paths of each node, avoiding unreachable situations between nodes without manual verification, so that the configured flowchart can realize process flow.

[0046] S206: Perform a logic check on the dependency relationship of the previous and next configurations of each node in the flowchart according to each node path.

[0047] In this embodiment, dependency analysis is performed on each node of the flowchart. Specifically, a logic check is performed on the front and back configurations of each node of the flowchart to ensure the rationality of the configuration of the entire flowchart.

[0048] In one embodiment, the dependency relationship includes the node before and after causal relationships and the constraints between nodes. The dependency relationship of the before and after configurations of each node in the flowchart is logically checked according to each node path, including: performing a logical check on the node before and after causal relationships and the constraints between nodes of each node in the flowchart according to each node path.

[0049] In an example of the present embodiment, the node-by-node causal relationship includes a random probability relationship between the nodes, and the constraints between the nodes include node flow conditions. The node-by-node causal relationship and the constraints between the nodes of the flowchart are logically checked according to the paths of each node, including: identifying the random nodes of the flowchart and all the first flow nodes of the random nodes, and the random nodes flow to any first flow node according to the random probability; obtaining the probability value of the random nodes flowing to each first flow node, accumulating the probability values ​​of all the first flow nodes, and logically checking the random nodes and all the first flow nodes based on the accumulated value; identifying the conditional nodes of the flowchart and all the second flow nodes of the conditional nodes, and the conditional nodes refer to the nodes that flow to the corresponding second flow nodes according to predetermined conditions; identifying all the node flow conditions of the conditional nodes, and logically checking the conditional nodes and all the second flow nodes according to whether there is a corresponding relationship between the flow conditions of each node and each second flow node.

[0050] In this embodiment, the dependency relationship includes the causal relationship before and after the nodes and the constraints between the nodes. The causal relationship before and after the nodes refers to the previous node being the triggering cause of the next node, and the next node being the result of the flow after the previous node is triggered. Among them, the causal relationship before and after the nodes includes the random probability relationship before and after the nodes. That is, when the previous node is triggered, it flows to the next node according to a certain random probability. The constraints between the nodes refer to that after the previous node is triggered according to the conditions, it must flow to the next node.

[0051] Specifically, identify the random nodes of the flowchart and all the first flow nodes of the random nodes. Calculate the cumulative value of the probability values ​​of the random nodes flowing to each first flow node. If the cumulative value is 100%, the logic check of the random nodes and all the first flow nodes passes. Identify the conditional nodes of the flowchart and all the second flow nodes of the conditional nodes. Trigger all the node flow conditions of the conditional nodes, and check whether they can flow to the corresponding second flow node when any node flow condition is triggered. If so, the conditional nodes and all the second flow nodes pass the logic check, otherwise the logic check fails. That is: the sum of the probabilities of all branches after the random node must be 100%; the conditional nodes cannot have scenarios where there is no executable path, etc. For example, if Figure 3 As shown in Figure 1, the mutual constraints between nodes are given in module C. When any condition is triggered, it flows to the intermediate event through the event gateway. If it cannot flow to the intermediate event, that is, the condition of the intermediate event cannot be met, it flows to the waiting node. Therefore, it is ensured that there is no scenario where there is no executable path in the condition node.

[0052] It can automatically perform logical verification on the dependencies of the front and back configurations of each node in the flowchart according to the paths of each node, without manual verification, to avoid non-compliant configuration of the flowchart caused by the dependencies of the front and back configurations of each node not meeting the requirements.

[0053] S208, performing a logic check on the node content of each node in the flow chart.

[0054] In this embodiment, the node content configured in the node of the flowchart is checked to ensure that the internal logic of the node is executed correctly. For example, for the model node in the flowchart, the validity of the model configured in the model node is checked.

[0055] like Figure 3As shown, module D gives an example of performing a logical check on the node content. Specifically, the node is an event-triggered node, and its configured node content includes derived events, feature tags, and full links. Based on the node characteristic of event triggering, a logical check is performed on its configured derived events, feature tags, and full links. For example, it is determined whether the derived event meets the triggering conditions. If so, the logical check passes. For example, it is determined whether the feature tag can identify the derived event and whether it has the system identification function. If so, the logical check passes. For example, it is determined whether the link attributes of the full link meet the system configuration requirements. If so, the logical check passes.

[0056] It can automatically perform logical verification on the node content of each node of the flowchart, avoiding non-compliant configuration of the flowchart due to node content not meeting requirements without manual verification.

[0057] In one embodiment, after the step of identifying each node path of the flowchart, the step further includes: collecting variables configured for each path according to each node path; and identifying whether the format of the configured variables meets the format requirements.

[0058] Specifically, according to each node path, the variables configured on all paths are collected, and the variables in the process are checked to ensure that the format of all configured variables is correct. For example, the configured variable format should be in time format, but the variable configured by the user on the path is in numeric format, then it is identified that the format of the configured variable does not meet the format requirements. Therefore, the variable format can be automatically checked, and manual verification can be avoided to avoid non-compliant configuration of the flowchart due to non-compliance of the variables configured on the path.

[0059] In one embodiment, any of the above steps S202-S208 further includes: if the verification fails, an error message is displayed on the configuration interface of the flow chart of the process engine to remind the user to modify the configuration content.

[0060] Specifically, if any verification logic fails, an error is reported to remind the user to modify the configuration again, and the erroneous nodes, lines, node attribute content and the cause of the problem obtained by the verification are displayed to facilitate the user to make modifications.

[0061] The above-mentioned flowchart automatic verification method identifies and verifies the global information of the flowchart in the process engine; identifies each node path of the flowchart, starts from the head node of the flowchart, and performs reachability analysis and verification on all nodes of the flowchart based on each node path; performs logical verification on the dependency relationship of the front and back configurations of each node of the flowchart according to each node path; and performs logical verification on the node content of each node of the flowchart. Therefore, the flowchart can be automatically verified without manual review and verification, which can improve the accuracy and efficiency of flowchart verification.

[0062] For a flowchart automatic verification method of each of the above embodiments, a specific application scenario is provided below. Figure 4 As shown:

[0063] First, check the overall basic properties of the flowchart process, including: naming standards, validity period check, and business scenario check.

[0064] Secondly, check the process connections in the flowchart, including: unconnected line check and redundant line check.

[0065] Then, the dependencies between nodes in the flowchart are checked, including the cause and effect before and after the nodes and the constraints between the nodes.

[0066] Finally, the contents configured in the nodes in the flowchart are checked, including: checking whether the required items of the nodes are missing, checking whether the node configuration contents are reasonable, and checking whether the status of the node configuration contents is normal.

[0067] Therefore, the above-mentioned flowchart automatic verification method has the following advantages:

[0068] 1. Prevent errors and defects: Pre-verification can detect potential errors and defects in the design stage, prevent them from flowing into the subsequent development and implementation stages, and reduce rework and repair costs.

[0069] 2. Ensure process correctness: Verify that the business process diagram correctly reflects business requirements and logic, and that each step and decision point in the process meets business goals.

[0070] 3. Improve efficiency: By verifying and solving bottlenecks and redundant steps in the process, you can optimize the process and improve the efficiency of overall business execution.

[0071] 4. Support compliance: For business processes that need to comply with specific regulations and standards, pre-verification ensures that the flowchart meets all relevant legal and regulatory requirements.

[0072] 5. Risk Management: Preliminary verification helps identify possible risk points and allows the project team to plan risk mitigation strategies in advance.

[0073] 6. Support continuous improvement: Verification not only helps ensure the correctness of current processes, but also provides a basis for continuous improvement, enabling organizations to continuously learn and optimize their business processes.

[0074] 7. Easy to automate and integrate: Accurate business process diagrams provide clear guidance for automation tools and system integration, helping to achieve automation and digital transformation of business processes.

[0075] 8. Save time and cost: Rework avoided through pre-verification can significantly save project time and cost and improve the efficiency of resource utilization.

[0076] It should be understood that, although the steps in the flowchart are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0077] The present application also provides a flow chart automatic verification device. Figure 5 As shown, a flowchart automatic verification device includes a global information verification module 502, a node verification module 504, a node dependency verification module 506, and a node content verification module 508. The global information verification module 502 is used to identify and verify the global information of the flowchart in the process engine; the node verification module 504 is used to identify each node path of the flowchart, starting from the head node of the flowchart, and perform reachability analysis verification on all nodes of the flowchart based on each node path; the node dependency verification module 506 is used to perform logical verification on the dependency relationship of the front and back configurations of each node of the flowchart according to each node path; the node content verification module 508 is used to perform logical verification on the node content of each node of the flowchart.

[0078] In one embodiment, the global information of the flowchart in the process engine is identified and verified, including: identifying the global information configuration component in the configuration interface of the process engine; reading the global information from the global information configuration component and verifying the global information.

[0079] In one embodiment, the global information configuration component includes a process name component, a validity period component and a business scenario component. Global information is read from the global information configuration component and global information verification is performed, including: reading the process name from the process name component, verifying the validity of the process name and verifying whether the process name complies with the naming specification; reading the validity period from the validity period component, verifying the validity of the input validity period value and verifying whether the validity period complies with the rules; reading business scenario information from the business scenario component, verifying the validity of the business scenario information and verifying whether the business scenario information complies with the rules.

[0080] In one embodiment, a reachability analysis check is performed on all nodes of the flowchart based on each node path, including: checking the connection lines between each node based on each node path; if there are redundant connection lines or unconnected lines, then determining that the reachability analysis results of the previous and next nodes corresponding to the redundant connection lines or unconnected lines are infeasible.

[0081] In one embodiment, the dependency relationship includes the node before and after causal relationships and the constraints between nodes. The dependency relationship of the before and after configurations of each node in the flowchart is logically checked according to each node path, including: performing a logical check on the node before and after causal relationships and the constraints between nodes of each node in the flowchart according to each node path.

[0082] In one embodiment, the node-by-node causal relationship includes a random probability relationship between the nodes, and the constraints between the nodes include node flow conditions. The node-by-node causal relationship and the constraints between the nodes of the flowchart are logically checked according to the paths of each node, including: identifying the random nodes of the flowchart and all the first flow nodes of the random nodes, and the random nodes flow to any first flow node according to the random probability; obtaining the probability value of the random nodes flowing to each first flow node, accumulating the probability values ​​of all the first flow nodes, and logically checking the random nodes and all the first flow nodes based on the accumulated value; identifying the conditional nodes of the flowchart and all the second flow nodes of the conditional nodes, and the conditional nodes refer to the nodes that flow to the corresponding second flow nodes according to predetermined conditions; identifying all the node flow conditions of the conditional nodes, and logically checking the conditional nodes and all the second flow nodes according to whether there is a corresponding relationship between the flow conditions of each node and each second flow node.

[0083] In one embodiment, a flowchart automatic verification device further includes a variable verification module, which is used to collect variables configured in each path according to each node path; and identify whether the format of the configured variables meets the format requirements.

[0084] For the specific definition of a flowchart automation verification device, please refer to the definition of a flowchart automation verification method above, which will not be repeated here. Each module in the above-mentioned flowchart automation verification device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0085] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 6As shown. The computer device includes a processor, a memory, a network interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a flowchart automatic verification method is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a key, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.

[0086] Those skilled in the art will understand that Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0087] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the following steps are implemented: identifying and verifying the global information of a flowchart in a process engine; identifying each node path of the flowchart, starting from the head node of the flowchart, and performing reachability analysis and verification on all nodes of the flowchart based on each node path; performing a logical verification on the dependency relationship of the front and back configurations of each node of the flowchart according to each node path; and performing a logical verification on the node content of each node of the flowchart.

[0088] In one of the embodiments, when the processor executes a computer program to implement the above-mentioned steps of identifying and verifying the global information of the flowchart in the process engine, the following steps are specifically implemented: identifying the global information configuration component in the configuration interface of the process engine; reading the global information from the global information configuration component and performing global information verification.

[0089] In one of the embodiments, the global information configuration component includes a process name component, a validity period component and a business scenario component. When the processor executes a computer program to implement the above-mentioned steps of reading global information from the global information configuration component and verifying the global information, the following steps are specifically implemented: reading the process name from the process name component, verifying the validity of the process name and verifying whether the process name complies with the naming specifications; reading the validity period from the validity period component, verifying the validity of the input validity period value and verifying whether the validity period complies with the rules; reading the business scenario information from the business scenario component, verifying the validity of the business scenario information and verifying whether the business scenario information complies with the rules.

[0090] In one of the embodiments, when the processor executes a computer program to implement the above-mentioned step of performing reachability analysis and verification on all nodes of the flowchart based on each node path, the following steps are specifically implemented: checking the connection lines between each node based on each node path; if there are redundant connection lines or unconnected lines, determining that the reachability analysis results of the previous and next nodes corresponding to the redundant connection lines or unconnected lines are infeasible.

[0091] In one of the embodiments, the dependency relationship includes the causal relationship before and after the nodes and the constraints between the nodes. When the processor executes the computer program to implement the above-mentioned step of logically checking the dependency relationship of the front and back configurations of each node of the flowchart according to each node path, the following steps are specifically implemented: logically checking the causal relationship before and after the nodes of each node of the flowchart and the constraints between the nodes according to each node path.

[0092] In one of the embodiments, the node-by-node causal relationship includes a random probability relationship between the nodes, and the constraints between the nodes include node flow conditions. When the processor executes a computer program to implement the above-mentioned step of performing a logical check on the node-by-node causal relationship and the constraints between the nodes of the flowchart according to the paths of each node, the following steps are specifically implemented: identifying the random nodes of the flowchart and all the first flow nodes of the random nodes, and the random nodes flow to any first flow node according to the random probability; obtaining the probability value of the random nodes flowing to each first flow node, accumulating the probability values ​​of all the first flow nodes, and performing a logical check on the random nodes and all the first flow nodes based on the accumulated value; identifying the conditional nodes of the flowchart and all the second flow nodes of the conditional nodes, and the conditional nodes refer to the nodes that flow to the corresponding second flow nodes according to predetermined conditions; identifying all the node flow conditions of the conditional nodes, and performing a logical check on the conditional nodes and all the second flow nodes according to whether there is a corresponding relationship between the flow conditions of each node and each second flow node.

[0093] In one of the embodiments, when the processor executes the computer program, the following steps are implemented: collecting variables configured for each path according to each node path; and identifying whether the format of the configured variables meets the format requirements.

[0094] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented: identifying and verifying the global information of the flowchart in the process engine; identifying each node path of the flowchart, starting from the head node of the flowchart, and performing reachability analysis and verification on all nodes of the flowchart based on each node path; performing a logical verification on the dependency relationship of the front and back configurations of each node of the flowchart according to each node path; and performing a logical verification on the node content of each node of the flowchart.

[0095] In one of the embodiments, when the computer program is executed by the processor to implement the above-mentioned steps of identifying and verifying the global information of the flowchart in the process engine, the following steps are specifically implemented: identifying the global information configuration component in the configuration interface of the process engine; reading the global information from the global information configuration component and performing global information verification.

[0096] In one of the embodiments, the global information configuration component includes a process name component, a validity period component and a business scenario component. When the computer program is executed by the processor to implement the above-mentioned steps of reading global information from the global information configuration component and verifying the global information, the following steps are specifically implemented: reading the process name from the process name component, verifying the validity of the process name and verifying whether the process name complies with the naming specifications; reading the validity period from the validity period component, verifying the validity of the input validity period value, and verifying whether the validity period complies with the rules; reading the business scenario information from the business scenario component, verifying the validity of the business scenario information and verifying whether the business scenario information complies with the rules.

[0097] In one of the embodiments, when the computer program is executed by the processor to implement the above-mentioned steps of performing reachability analysis and verification on all nodes of the flowchart based on each node path, the following steps are specifically implemented: checking the connection lines between each node based on each node path; if there are redundant connection lines or unconnected lines, determining that the reachability analysis results of the previous and next nodes corresponding to the redundant connection lines or unconnected lines are infeasible.

[0098] In one of the embodiments, the dependency relationship includes the causal relationship before and after the nodes and the constraints between the nodes. When the computer program is executed by the processor to implement the above-mentioned step of logically checking the dependency relationship of the before and after configuration of each node of the flowchart according to each node path, the following steps are specifically implemented: logically checking the causal relationship before and after the nodes of each node of the flowchart and the constraints between the nodes according to each node path.

[0099] In one embodiment, the node before and after causal relationship includes the random probability relationship before and after the nodes, and the constraints between the nodes include the node flow conditions. When the computer program is executed by the processor to implement the above-mentioned steps of logically checking the node before and after causal relationship and the constraints between the nodes of the flowchart according to each node path, the following steps are specifically implemented: identifying the random nodes of the flowchart and all the first flow nodes of the random nodes, and the random nodes flow to any first flow node according to the random probability; obtaining the probability value of the random nodes flowing to each first flow node, accumulating the probability values ​​of all the first flow nodes, and logically checking the random nodes and all the first flow nodes based on the accumulated value; identifying the conditional nodes of the flowchart and all the second flow nodes of the conditional nodes, the conditional nodes refer to the nodes that flow to the corresponding second flow nodes according to predetermined conditions; identifying all the node flow conditions of the conditional nodes, and logically checking the conditional nodes and all the second flow nodes according to whether there is a corresponding relationship between the flow conditions of each node and each second flow node.

[0100] In one of the embodiments, when the computer program is executed by a processor, the following steps are implemented: collecting variables configured for each path according to each node path; and identifying whether the format of the configured variables meets the format requirements.

[0101] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0102] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0103] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A flowchart automatic verification method, characterized in that: The method comprises: Identify and verify the global information of the flowchart in the process engine; Identify each node path of the flowchart, start from the head node of the flowchart, and perform reachability analysis and verification on all nodes of the flowchart based on each node path; Performing a logic check on the dependency relationship of the previous and next configurations of each node of the flowchart according to each node path; A logic check is performed on the node content of each node of the flow chart.

2. The method according to claim 1, characterized in that The identifying and verifying the global information of the flowchart in the process engine includes: Identify a global information configuration component in a configuration interface of the process engine; The global information is read from the global information configuration component and the global information is verified.

3. The method according to claim 2, characterized in that The global information configuration component includes a process name component, a validity period component, and a business scenario component. The reading of global information from the global information configuration component and performing global information verification include: Reading a process name from the process name component, performing validity verification on the process name, and verifying whether the process name complies with a naming specification; Reading the validity period from the validity period component, verifying the validity of the input value of the validity period, and verifying whether the validity period complies with the rules; The business scenario information is read from the business scenario component, the validity of the business scenario information is verified, and whether the business scenario information complies with the rules is verified.

4. The method according to claim 1, characterized in that: The performing reachability analysis and verification on all nodes of the flowchart based on the paths of each node includes: Checking the connection lines between the nodes based on the paths of the nodes; If there are extra connection lines or unconnected lines, the reachability analysis results of the front and rear nodes corresponding to the extra connection lines or unconnected lines are determined to be infeasible.

5. The method according to claim 1, characterized in that The dependency relationship includes the causal relationship between nodes and constraints between nodes. The logic check of the dependency relationship of the previous and next configurations of each node of the flowchart according to the node paths includes: A logical check is performed on the node before and after causal relationships of each node of the flow chart and the constraints between nodes according to the node paths.

6. The method according to claim 5, characterized in that The node before and after causal relationship includes the random probability relationship before and after the nodes, the constraint conditions between the nodes include the node flow conditions, and the logical verification of the node before and after causal relationship and the constraint conditions between the nodes of the flowchart according to the node paths includes: Identify a random node of the flowchart and all first flow nodes of the random node, and the random node flows to any first flow node according to a random probability; Obtaining probability values ​​of the random node flowing to each first flow node, accumulating the probability values ​​of all first flow nodes, and performing a logic check on the random node and all first flow nodes based on the accumulated values; Identify the conditional node of the flowchart and all second flow nodes of the conditional node, wherein the conditional node refers to a second flow node that flows to the corresponding node according to a predetermined condition; All node flow conditions of the conditional node are identified, and according to whether there is a corresponding relationship between each node flow condition and each second flow node, a logic check is performed on the conditional node and all second flow nodes.

7. The method according to claim 1, characterized in that The method further comprises: Collecting variables configured for each path according to each node path; Identify whether the format of the configured variable meets the format requirements.

8. A flow chart automatic verification device, characterized in that: The device comprises: The global information checking module is used to identify and check the global information of the flowchart in the process engine; A node checking module, used to identify each node path of the flowchart, starting from the head node of the flowchart, and performing reachability analysis and verification on all nodes of the flowchart based on each node path; A node dependency checking module, used for performing a logic check on the dependency relationship of the previous and next configurations of each node of the flowchart according to each node path; The node content checking module is used to perform logic verification on the node content of each node of the flow chart.

9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images