Process failure state analysis method, system, and computer equipment

Abstract

The present invention provides a method for analyzing the failure state of a process, and the method for analyzing the failure state of a process includes: setting an end embedded point at the end node of the process, wherein the process includes several process steps; running the process; when the process runs to the end node, judging whether the state of the process is a failure state; when the process is a failure state, collecting the end embedded point; parsing the end embedded point to obtain the process steps experienced when running the process as running steps; backtracking the inferred steps based on the previous running steps of the end node; and analyzing the missing scenarios that cause the state of the process to be a failure state based on the running steps and the inferred steps. In addition, the present invention also provides a system and computer device for analyzing the failure state of a process. The technical solution of the present invention effectively solves the problem that the program cannot know the cause based on the failure state of the process and make up for the missing scenarios.

Description

Technical Field

[0001] The present invention relates to the field of financial technology, and in particular to a method for analyzing process failure status, a system thereof, and computer equipment. Background Art

[0002] Currently, in the development of software systems for various industries, various states are set for various scenarios, especially in the financial credit card industry, such as account status, cancellation status, card process status, application, activation, various card control code status, and even batch operation status, but they all include invalid status such as invalid, canceled, expired, failed, etc.

[0003] A good and complete state process can greatly promote business development, but it is often not fully considered during the product development and design stages. Sometimes the state is not fully customized before it is launched, and it has not undergone various complex production verifications, which may lead to production accidents. In addition, many intermediate states are often adjusted or added due to business changes, resulting in constant discussions between developers and business about product requirements and code adjustments, and even delays in feature launches. Summary of the Invention

[0004] In view of this, it is necessary to provide a process failure status analysis method and its system, computer equipment, to analyze the failure status of the process in order to improve the process.

[0005] In a first aspect, an embodiment of the present invention provides a method for analyzing a process failure state, the method comprising:

[0006] Setting the end embedding point at the end node of the process, wherein the process includes several process steps;

[0007] running the process;

[0008] When the process runs to the end node, determining whether the state of the process is an invalid state;

[0009] When the state of the process is an invalid state, collecting the end buried point;

[0010] Parsing the end embedded point to obtain the process steps experienced when running the process as running steps;

[0011] Backtracking the inference step based on the previous running step of the end node; and

[0012] The missing scenarios that cause the state of the process to be a failure state are analyzed based on the running steps and the inference steps.

[0013] Preferably, before running the process, the method for analyzing the process failure status further includes:

[0014] Set up several front-end embedding points in the process steps.

[0015] Preferably, the missing scenarios that lead to the failure state of the process according to the analysis of the running steps and the inference steps specifically include:

[0016] Acquire the process step with the front-end tracking point in the running step as the tracking point step;

[0017] Determining whether the inference step includes the point embedding step;

[0018] When the inference step does not include the point burying step, obtaining the preceding point burying step of the point burying step; and

[0019] The missing scenario in which the state of the process is in a failed state due to the preceding tracking analysis of the tracking step.

[0020] Preferably, setting several front-end embedding points in the process steps specifically includes:

[0021] Obtaining tracking rules, wherein the tracking rules include the process steps of the core of the process; and

[0022] According to the tracking rule, the front-end tracking is set at the process step of the core of the process.

[0023] Preferably, after analyzing the missing scenario that causes the process to be in a failure state according to the running step and the inference step, the process failure state analysis method further includes:

[0024] The result generated by performing the inference step is analyzed according to the missing scene.

[0025] Preferably, after analyzing the result of executing the inference step according to the missing scenario, the process failure status analysis method further includes:

[0026] The results are input into a pre-set analysis model to obtain the failure cause.

[0027] In a second aspect, an embodiment of the present invention provides a computer device, comprising:

[0028] a memory for storing program instructions; and

[0029] A processor is used for executing the program instructions to implement the above-mentioned method for analyzing the process failure state.

[0030] In a third aspect, an embodiment of the present invention provides a process failure status analysis system, the process failure status analysis system comprising:

[0031] A first setting module is used to set the end embedding point at the end node of the process, wherein the process includes a plurality of process steps;

[0032] A simulation operation module, used to run the process;

[0033] A first judgment module is used to judge whether the state of the process is an invalid state when the process runs to the end node;

[0034] A first collection module is used to collect the end buried point when the process is in an invalid state;

[0035] A first parsing module is used to parse the end embedded point to obtain the process steps experienced when running the process as running steps;

[0036] A backtracking module, configured to backtrack the inferred step according to the previous running step of the end node; and

[0037] The first analysis module is used to analyze the missing scenarios that cause the state of the process to be a failure state according to the operating steps and the inference steps.

[0038] Preferably, the process failure status analysis system further includes:

[0039] The second setting module is used to set a number of front-end embedded points in the process steps.

[0040] Preferably, the first analysis module specifically includes:

[0041] A first acquisition module is used to acquire a process step with a front-end tracking point in the running step as a tracking point step;

[0042] A second judgment module is used to judge whether the inference step includes the tracking step;

[0043] A second acquisition module is configured to acquire the preceding buried points of the buried point step when the inference step does not include the buried point step; and

[0044] The second analysis module is used to analyze the missing scenarios that cause the process status to be an invalid state based on the previous tracking point analysis of the tracking point step.

[0045] The above-mentioned process failure status analysis method and its system and computer equipment set tracking points in the program to be tested, run the program, check the tracking points of the failure status, analyze the experienced process steps, backtrack the inferred steps, compare the experienced process steps with the inferred steps, and analyze the missing scenarios that lead to the failure status. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the embodiments of the present invention 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 invention. For ordinary technicians in this field, other drawings can be obtained based on the structures shown in these drawings without paying any creative work.

[0047] Figure 1 This is a flow chart of a method for analyzing process failure status provided by an embodiment of the present invention.

[0048] Figure 2 This is a first sub-flowchart of the method for analyzing process failure status provided by an embodiment of the present invention.

[0049] Figure 3 This is a second sub-flowchart of the method for analyzing process failure status provided by an embodiment of the present invention.

[0050] Figure 4 This is the third sub-flowchart of the method for analyzing process failure status provided by an embodiment of the present invention.

[0051] Figure 5 This is a fourth sub-flowchart of the method for analyzing process failure status provided by an embodiment of the present invention.

[0052] Figure 6 This is a fifth sub-flowchart of the method for analyzing process failure status provided by an embodiment of the present invention.

[0053] Figure 7 This is a schematic diagram of the first internal structure of the dynamic interactive system for asset configuration provided by an embodiment of the present invention.

[0054] Figure 8 This is a schematic diagram of the second internal structure of the dynamic interactive system for asset configuration provided by an embodiment of the present invention.

[0055] Figure 9 for Figure 7 Schematic diagram of the internal structure of the first analysis module.

[0056] Figure 10 A schematic diagram of the internal structure of a computer device provided in an embodiment of the present invention.

[0057] The purpose, features and advantages of the present invention will be further described with reference to the accompanying drawings and in conjunction with the embodiments. DETAILED DESCRIPTION

[0058] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0059] The terms "first," "second," "third," "fourth," and the like (if any) in the specification and claims of this application and in the accompanying drawings are used to distinguish similar program objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate. In other words, the described embodiments are implemented according to an order other than that illustrated or described herein. In addition, the terms "including" and "having," and any variations thereof, may also encompass other content. For example, a process, method, system, product, or apparatus comprising a series of steps or units need not be limited to only those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to these processes, methods, products, or apparatus.

[0060] It should be noted that the descriptions of "first", "second", etc. in the present invention are for descriptive purposes only and should not be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" or "second" may explicitly or implicitly include one or more of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but this must be based on the fact that they can be implemented by ordinary technicians in this field. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0061] Please refer to Figure 1 , which is a flow chart of a method for analyzing a process failure state provided by an embodiment of the present invention. The method for analyzing a process failure state specifically includes the following steps.

[0062] Step S101, setting the end embedding point at the end node of the process, wherein the process includes several process steps.

[0063] Specifically, in software development and design, the product code development process includes several steps, some of which follow a certain sequence, and the last step of each sequence has an end node. For example, a simple update operation process, from the initial initiation to the final end node, involves a query process, an if-else branch judgment process, a data conversion process, and finally the result process. The end point is set at the end node of the result process.

[0064] Step S102, run the process.

[0065] Specifically, the program flow to be analyzed is simulated in the development and testing environment. For example, a simple update operation process is simulated and run, and the update operation process program includes the query process, branch judgment process, data conversion process, and result process.

[0066] Step S103: When the process reaches the end node, it is determined whether the state of the process is an invalid state.

[0067] Specifically, a process status includes a failed state and a successful state. A failed state means that the process has entered the result process but has not executed the required action. For example, in an update operation process, the successful state means the update is completed, while the failed state means the update failed.

[0068] When the status of the process is an invalid state, step S104 is executed.

[0069] Step S104: collecting the final buried points.

[0070] Specifically, through AI technology, the end point can be collected, that is, the end point can be collected at the end node of the result process.

[0071] Step S105: parse the end embedded point to obtain the process steps experienced when running the process as the running steps.

[0072] Specifically, it analyzes and intelligently identifies the rule scenarios for the final embedded points, and decomposes and traces back the previous step-by-step process steps based on the final failure state.

[0073] For example, a process includes process steps A, B, C, D, E, F, and G. Parsing the end tracking data reveals that the process steps involved in running the process include C, E, F, and G. Therefore, C, E, F, and G are running steps.

[0074] Step S106, backtracking the inference step according to the previous running step of the end node.

[0075] Specifically, the previous process steps are decomposed and traced back according to the final failure state.

[0076] For example, the previous running step of the end node is process step G, and the backtracking speculation steps include process step F and process step A.

[0077] Step S107 , analyzing the missing scenarios that cause the process state to be a failure state based on the running steps and the inferred steps.

[0078] For example, if the backtracking speculation steps include process steps F and A, that is, process step A can trigger process step G, and process step F can also trigger process step G at the same time, different failure states can be generated, and process step A is the missing scenario of the failure state. It is understandable that in some possible situations, the combination of process steps A and C may also trigger process step G.

[0079] Specifically, the run step is the simulated run step, and the inference step is the decomposition and backtracking step based on the final failure state. The run step includes all steps from the start of the process execution, while the inference step is the reverse step. For example, if the process being run is an update operation, based on the process steps obtained from the run step, the system can intelligently detect the update operation interface, detect each program step in the system process one by one, and finally perform a process comparison to see if the reversed steps cover the run step. If any steps are interrupted or encounter an exception, they will not match the tracking rule steps, thus detecting all potential missing scenarios in the product or code that can lead to failure states.

[0080] The specific process of how to analyze the missing scenarios that cause the process status to be a failure state based on the running steps and the inferred steps will be described in detail below.

[0081] In the above embodiment, the system sets an end tracking point for the development program flow, simulates the program flow, and when the program flow fails, collects the end tracking point, analyzes the end tracking point to infer the inferred steps, and analyzes the missing scenarios that may lead to the failure state.

[0082] Please refer to Figure 2 and Figure 4 , Figure 2 The first sub-flowchart of the method for analyzing process failure status provided by an embodiment of the present invention is as follows: Figure 4 This is a third sub-flowchart of the process failure status analysis method provided by the embodiment of the present invention. Before executing step S102, the process failure status analysis method further includes the following steps.

[0083] Step S201, set several front-end embedded points in the process steps.

[0084] Specifically, a front-end tracking point is set in the code of the process step. The front-end tracking point is used by designers to track the functions required by the process step according to development needs for subsequent detection.

[0085] Setting several front-end tracking points in the process steps specifically includes the following steps.

[0086] Step S401: Obtain tracking rules, where the tracking rules include the core process steps.

[0087] Step S402: Set the process steps of the front-end tracking point at the core of the process according to the tracking point rules.

[0088] Specifically, tracking rules are tracking points for the core steps of a development process. For example, when monitoring a user watching a video, you can set a tracking point at the beginning of the video and another in the middle. The first tracking point is used to monitor the video's click volume, and the two tracking points are combined to monitor the video's views. Developers can set tracking rules based on development needs and set tracking points at core steps.

[0089] In the above embodiment, the system sets tracking points in the process steps according to the tracking point rules input by the developer.

[0090] Please refer to Figure 3 , which is the second sub-flowchart of the process failure state analysis method provided by the embodiment of the present invention. Step S107 specifically includes the following steps.

[0091] Step S301, obtaining a process step with a front-end tracking point in the running step as a tracking point step.

[0092] For example, according to the tracking rules, set the front-end tracking at process steps B, C, and F. The tracking steps then include process steps B, C, and F.

[0093] Step S302, determine whether the inference step includes a point embedding step.

[0094] Specifically, when the inference step is set with a tracking step, that is, the inference step may have the same tracking point as the running step. When the inference step and the running step have the same tracking point, that is, the scenario that can lead to the failure state may be the same scenario, and further judgment is required.

[0095] When the inference step does not include the point embedding step, step S303 is executed.

[0096] Step S303, obtaining the preceding tracking points of the tracking step.

[0097] Step S304: Analyze the missing scenarios that result in the process status being in an invalid state based on the previous tracking step.

[0098] Specifically, when the inference step is set with a tracking step, the inference step can lead to a missing scenario based on the tracking step analysis. For example, in a login operation, when the failure state is that the account and password are inconsistent, if the operation process is to receive the account - receive the password - retrieve the secret of the account in the database - compare whether the two passwords are consistent, in this process, there is no check to see if the receiving account is the account in the database. The result may be that the user has to repeatedly enter the correct password when the username is incorrect and cannot get the correct guidance. Developers may not necessarily discover the occurrence of such scenarios.

[0099] In the above embodiment, the system detects the preceding buried points of the inferred steps through the inferred steps, and finds out the missing scenarios that will lead to the failure state except for the last process in the inferred steps.

[0100] Please refer to Figure 5 , which is the fourth sub-flowchart of the process failure status analysis method provided by the embodiment of the present invention. After executing step S107, the process failure status analysis method further includes the following steps.

[0101] Step S502: Analyze the result of the inference step according to the missing scene.

[0102] Specifically, based on the detected failure scenarios that can lead to failure, the system calculates and analyzes the possible consequences, allowing it to take necessary measures in advance to improve product quality and reliability. For example, in the case of account activation failure or credit card application failure, it can detect the specific scenarios or reasons that lead to failure.

[0103] Please refer to Figure 6 , which is the fifth sub-flowchart of the process failure status analysis method provided by the embodiment of the present invention. After executing step S502, the process failure status analysis method further includes the following steps.

[0104] Step S501: Input the result into a preset analysis model to obtain the failure cause.

[0105] Specifically, the analysis method for process failure states can also be used for machine learning. Based on the collected tracking points and the detected failure results, intelligent analysis of the failure causes can be performed. For example, whether the design is too redundant, whether there are too many external dependencies, whether parameter validation is too strict, whether the design has too many features, and whether downgrade is necessary. Based on the resulting failure state, it can be inferred whether the system interface is well-designed, whether the fields are complete, and the severity of the system failure and the probability of bugs can be determined. Designers and developers can use this function to make corresponding modifications to the development software.

[0106] Please refer to Figure 10, which is a schematic diagram of the internal structure of a computer device provided in an embodiment of the present invention. The computer device 300 specifically includes a memory 310 and a processor 320. The memory 310 is used to store program instructions, and the processor 320 is used to execute the program instructions to implement the above-mentioned process failure state analysis method.

[0107] In some embodiments, the processor 320 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip, configured to execute program instructions stored in the memory 210 .

[0108] The memory 310 includes at least one type of readable storage medium, which includes a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the memory 310 can be an internal storage unit of a computer device, such as a hard disk of the computer device. In other embodiments, the memory 310 can also be an external storage device of the computer device, such as a plug-in hard disk, a smart memory card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the computer device. Furthermore, the memory 310 can also include both an internal storage unit of the computer device and an external storage device. The memory 310 can not only be used to store application software and various types of data installed on the computer device, such as the code for implementing the analysis method of the process failure state, but can also be used to temporarily store data that has been output or is about to be output.

[0109] Please refer to Figure 7 , which is a schematic diagram of the first internal structure of a process failure status analysis system 50 provided in an embodiment of the present invention. The process failure status analysis system 50 includes a first setting module 51, a simulation operation module 52, a first judgment module 53, a first acquisition module 54, a first analysis module 55, a backtracking module 56, and a first analysis module 57.

[0110] The first setting module 51 is used to set the end embedding point at the end node of the process, wherein the process includes several process steps.

[0111] Specifically, in software development and design, the product code development process includes several process steps, some of which have a certain order, and the last process step of the several sequential process steps is set with an end node. For example, a simple update operation process, from the initial initiation to the final end node, goes through a query process, an if-else branch judgment process, a data conversion process, and finally a result process. The first setting module 51 sets the end point at the end node of the result process.

[0112] The simulation operation module 52 is used to operate the process.

[0113] Specifically, the simulation operation module 52 simulates and runs the program flow to be analyzed in the development and testing environment. For example, a simple update operation flow is simulated and runs the update operation flow program, and the update operation flow includes a query flow, a branch judgment flow, a data conversion flow, and a result flow.

[0114] The first judgment module 53 is used to judge whether the state of the process is an invalid state when the process runs to the end node.

[0115] Specifically, the status of a process includes a failure state and a success state. The failure state means that the process has entered the result process but has not executed the required action. For example, in an update operation process, the success state is update completed, and the failure state is update failed. The first judgment module 53 determines whether the update operation is update completed or update failed.

[0116] The first collection module 54 is used to collect the end buried points when the process is in an invalid state.

[0117] Specifically, the first acquisition module 54 can collect the end buried point through AI technology, that is, collect the end buried point at the end node of the result process.

[0118] The first parsing module 55 is used to parse the end embedded point to obtain the process steps experienced when the process is running as the running steps.

[0119] Specifically, the first parsing module 55 parses and intelligently identifies the rule scenario of the end embedding point, and decomposes and traces back the previous step-by-step process steps according to the final failure state.

[0120] For example, a process includes process steps A, B, C, D, E, F, and G. Parsing the end tracking data reveals that the process steps involved in running the process include C, E, F, and G. Therefore, C, E, F, and G are running steps.

[0121] The backtracking module 56 is used to backtrack the inferred step according to the previous running step of the end node.

[0122] Specifically, the backtracking module 56 decomposes and backtracks the preceding process steps according to the final failure state.

[0123] For example, the previous running step of the end node is process step G, and the backtracking speculation steps include process step F and process step A.

[0124] The first analysis module 57 is configured to analyze, based on the running steps and the inferred steps, missing scenarios that cause the process to be in a failed state.

[0125] For example, if the backtracking speculation steps include process steps F and A, that is, process step A can trigger process step G, and process step F can also trigger process step G at the same time, different failure states can be generated, and process step A is the missing scenario of the failure state. It is understandable that in some possible situations, the combination of process steps A and C may also trigger process step G.

[0126] Specifically, the run step is the simulated run step, and the inference step is the decomposition and backtracking step based on the final failure state. The run step includes all steps from the start of the process execution, while the inference step is the reverse step. For example, if the process being run is an update operation, based on the process steps obtained from the run step, the system can intelligently detect the update operation interface, detect each program step in the system process one by one, and finally perform a process comparison to see if the reversed steps cover the run step. If any steps are interrupted or encounter an exception, they will not match the tracking rule steps, thus detecting all potential missing scenarios in the product or code that can lead to failure states.

[0127] Please refer to Figure 8 , which is a second internal structure diagram of the process failure status analysis system provided by an embodiment of the present invention. The process failure status analysis system 50 further includes a second setting module 61.

[0128] The second setting module 61 is used to set a number of front-end embedded points in the process steps.

[0129] Specifically, a front-end tracking point is set in the code of the process step. The front-end tracking point is used by designers to track the functions required by the process step according to development needs for subsequent detection.

[0130] Please refer to Figure 9 , which is a schematic diagram of the internal structure of the first analysis module provided by an embodiment of the present invention. The first analysis module 57 includes a first acquisition module 71, a second judgment module 72, a second acquisition module 73 and a second analysis module 74.

[0131] The first acquisition module 71 is used to acquire a process step with a front-end tracking point in the running steps as a tracking point step.

[0132] The second judgment module 72 is used to judge whether the inference step includes a point embedding step.

[0133] The second acquisition module 73 is used to acquire the preceding buried points of the buried point step when the inference step does not include the buried point step.

[0134] The second analysis module 74 is used to analyze the missing scenarios that cause the process status to be in a failed state based on the previous tracking step.

[0135] Specifically, tracking rules are tracking points for the core steps of a development process. For example, when monitoring a user watching a video, you can set a tracking point at the beginning of the video and another in the middle. The first tracking point is used to monitor the video's click volume, and the two tracking points are combined to monitor the video's views. Developers set tracking points at core steps and define corresponding tracking rules based on development needs.

[0136] In the above embodiment, the system and computer equipment use a method for analyzing process failure status, by setting tracking points in the program to be tested, running the program, checking the tracking points of the failure status, parsing the process steps experienced, backtracking the inferred steps, comparing the process steps experienced with the inferred steps, and analyzing the missing scenarios that lead to the failure status.

[0137] Obviously, those skilled in the art may make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if such changes and modifications fall within the scope of the claims and their equivalents, the present invention is intended to include such changes and modifications.

[0138] The above examples are merely preferred embodiments of the present invention and are not intended to limit the scope of the present invention. Therefore, equivalent changes made according to the claims of the present invention still fall within the scope of the present invention.

Claims

1. A method for analyzing process failure status, characterized in that: The analysis method of the process failure state includes: Setting the end embedding point at the end node of the process, wherein the process includes several process steps, the several process steps have a certain order, and the last process step is set with the end node; running the process; When the process runs to the end node, determining whether the state of the process is an invalid state; When the state of the process is an invalid state, collecting the end buried point; Parsing the end embedded point to obtain the process steps experienced when running the process as running steps; Backtracking the inference step based on the previous running step of the end node; and Analyze the missing scenarios that cause the state of the process to be a failure state according to the operating steps and the inference steps; Before running the process, the method for analyzing the failure status of the process further includes: Set up several front-end embedding points at the process steps; Analyzing the missing scenarios that cause the process to be in a failed state based on the running steps and the inference steps specifically includes: Acquire the process step with the front-end tracking point in the running step as the tracking point step; Determining whether the inference step includes the point embedding step; When the inference step does not include the point burying step, obtaining the preceding point burying step of the point burying step; and The missing scenario where the process status is in a failed state according to the preceding tracking analysis of the tracking step; Set up several front-end tracking points at the process steps, including: Obtaining tracking rules, wherein the tracking rules include the process steps of the core of the process; and According to the tracking rule, the front-end tracking is set at the process step of the core of the process.

2. The process failure state analysis method according to claim 1, characterized in that: After analyzing the missing scenario that causes the process to be in a failure state according to the running step and the inference step, the process failure state analysis method further includes: The result generated by performing the inference step is analyzed according to the missing scene.

3. The process failure state analysis method according to claim 2, characterized in that: After analyzing the result of executing the inference step according to the missing scenario, the process failure status analysis method further includes: The results are input into a pre-set analysis model to obtain the failure cause.

4. A computer device, characterized in that: The computer device comprises: a memory for storing program instructions; and A processor, configured to implement the program instructions to implement the process failure state analysis method according to any one of claims 1 to 3.

5. A process failure status analysis system, characterized in that: The process failure status analysis system includes: A first setting module is used to set the end embedding point at the end node of the process, wherein the process includes a plurality of process steps, the plurality of process steps have a certain order, and the last process step is set with the end node; A simulation operation module, used to run the process; A first judgment module is used to judge whether the state of the process is an invalid state when the process runs to the end node; A first collection module is used to collect the end buried point when the state of the process is an invalid state; A first parsing module is used to parse the end embedded point to obtain the process steps experienced when running the process as running steps; A backtracking module, configured to backtrack the inferred step according to the previous running step of the end node; and A first analysis module is configured to analyze, based on the operation steps and the inference steps, missing scenarios that cause the process to be in a failure state; The process failure status analysis system further includes a second setting module, which is used to set a number of front-end embedded points in the process steps; The first analysis module specifically includes: A first acquisition module is used to acquire a process step with a front-end tracking point in the running step as a tracking point step; A second judgment module is used to judge whether the inference step includes the tracking step; A second acquisition module is configured to acquire the preceding buried points of the buried point step when the inference step does not include the buried point step; and A second analysis module is configured to analyze missing scenarios that cause the process to be in a failed state based on the preceding tracking step; The second setting module is also used to obtain the tracking point rules, and set the process steps of the front-end tracking point in the core of the process according to the tracking point rules, wherein the tracking point rules include the process steps of the core of the process.

Images