Project risk data determination method and device, electronic equipment and storage medium

Abstract

The invention relates to the field of data management, and discloses a project risk data determination method and device, electronic equipment and a storage medium, and the method comprises the steps: determining a back-end problem in an open state in a project as risk data, and determining a risk level corresponding to the back-end problem in the open state according to a preset risk level division strategy; if a first failure node in the project process is associated with the back-end problem in the open state, determining respective corresponding priority values according to respective risk degree parameters of subordinate target type child nodes of the first failure node; if the priority numerical value of the at least one target type child node is obtained, determining the first failure node as risk data, and determining a risk level corresponding to the first failure node according to the obtained at least one priority numerical value; wherein the risk levels of the failure nodes are in one-to-one correspondence with the risk levels of the back-end problems. The risk level of the back-end risk data can be quickly determined, and omission of the risk data can be avoided.

Description

Technical Field

[0001] The present application relates to the field of data management, and particularly to a method, apparatus, electronic device, and storage medium for determining project risk data. Background Art

[0002] For the risk control of a project, relatively independent analysis means are usually adopted, resulting in relative independence between R & D and after-sales. The R & D process generally focuses on analyzing various risk issues at the front end of project development, ignoring the risk analysis of issues at the back end of the project, leading to the inability to plan prevention and detection measures in advance. In the after-sales stage, only the handling results of issues such as customer complaints and after-sales repairs are generally simply recorded, lacking integration with front-end data, resulting in the lack of risk data analysis for the entire project.

[0003] Meanwhile, when determining the risk data in the project process, due to the lack of combination with the back-end issues of the project, some risk data are not discovered, and it is even impossible to know the risk levels of the missing risk data, thus causing the lack of project risk data. Summary of the Invention

[0004] In view of the above problems, the present application provides a method, apparatus, electronic device, and storage medium for determining project risk data, which are used to accurately determine the risk data at the front end and back end of the project and avoid the omission of risk data.

[0005] According to one aspect of the present application, a method for determining project risk data is provided. The determination method includes: determining the back-end issues in the project that are in the open state as risk data, and determining the risk levels corresponding to the back-end issues in the open state according to a preset risk level classification strategy; if the first failure node in the project process is associated with the back-end issues in the open state, then determining the respective priority values according to the risk degree parameters of the target type sub-nodes subordinate to the first failure node; if the priority values of at least one target type sub-node are obtained, then determining the first failure node as the risk data, and determining the risk level corresponding to the first failure node according to the obtained at least one priority value; wherein, the risk levels of the failure nodes and the risk levels of the back-end issues correspond one by one.

[0006] In an optional manner, the determination method further includes: if the second failure node in the project process is associated with the back-end issues in the closed state, and the missing nodes of the chain to which the second failure node belongs, then determining the second failure node as the risk data, and determining the risk level of the second failure node as a preset risk level.

[0007] In an alternative manner, the method for determining the missing node of the chain to which the second failed node belongs includes: detecting whether the second failed node has a parent node, and whether the level of the top node in the chain to which the second failed node belongs is a preset level; if either is no, determining the missing node of the chain to which the second failed node belongs.

[0008] In an alternative manner, the determining, according to the risk degree parameters of the target type sub-nodes under the first failed node, of the respective corresponding priority values includes: traversing each target type sub-node under the first failed node, and taking the traversed target type sub-node as the focus sub-node; matching the risk degree parameter of the focus sub-node with a preset risk degree parameter; if the matching fails, determining that the priority value corresponding to the focus sub-node is empty; if the matching succeeds, taking the priority value corresponding to the preset risk degree parameter that succeeds in matching as the priority value of the focus sub-node, so as to obtain the priority values of each target type sub-node.

[0009] In an alternative manner, the risk degree parameter includes different types of risk degree parameters; the number of the preset risk degree parameters is multiple, and each preset risk degree parameter includes sub-preset risk degree parameters of different types; the matching of the risk degree parameter of the focus sub-node with the preset risk degree parameter includes: respectively matching the risk degree parameters of each type of the focus sub-node with the sub-preset risk degree parameters of the same type in the target preset risk degree parameter; wherein, the target preset risk degree parameter is any one of the preset risk degree parameters; if the risk degree parameters of all types succeed in matching, it indicates that the risk degree parameter of the focus sub-node and the preset risk degree parameter succeed in matching.

[0010] In an alternative manner, the determining method further includes: substituting each risk data based on its occurrence time and the item to which it belongs into the corresponding display block in the display diagram; wherein, the display block is a block divided in the display diagram according to a preset threshold point interval and different preset items, and the preset threshold point interval is an interval divided according to the corresponding time of the preset item stage node; determining the color of each display block according to the number of risk data and the corresponding risk level in each display block, so that each display block displays the corresponding color and the number of risk data it contains; wherein, the depth of the color is proportional to the number of the risk data and the risk level.

[0011] In an alternative manner, the determination method further includes: in response to a trigger instruction of a user for a target display tile, generating a quantity bar chart representing the risk data at different times in the target display tile according to the risk data at each time in the target display tile and the risk levels corresponding to the risk data at each time; wherein different colored bars in the quantity bar chart represent the risk data at different times, and the color of each colored bar is determined according to the risk level of the risk data represented by each colored bar.

[0012] According to another aspect of the present application, there is provided a device for determining project risk data, the determination device including: a first determination module, configured to determine the backend problems in the project that are in an open state as risk data, and determine the risk levels corresponding to the backend problems in the open state according to a preset risk level classification strategy; a second determination module, configured to, if a first failure node in the project process is associated with the backend problems in the open state, determine the respective corresponding priority values according to the respective risk degree parameters of the target type sub-nodes subordinate to the first failure node; a third determination module, configured to, if the priority values of at least one target type sub-node are obtained, determine the first failure node as the risk data, and determine the risk level corresponding to the first failure node according to the obtained at least one priority value; wherein the risk levels of the failure nodes and the risk levels of the backend problems correspond one by one.

[0013] According to one aspect of the present application, there is provided an electronic device, including: a controller; a memory, configured to store one or more programs, and when the one or more programs are executed by the controller, to execute the above determination method.

[0014] According to one aspect of the present application, there is also provided a computer-readable storage medium, on which computer-readable instructions are stored, and when the computer-readable instructions are executed by a processor of a computer, the computer is caused to execute the above determination method.

[0015] According to one aspect of the present application, there is also provided a computer program product or a computer program, the computer program product or the computer program including computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the above determination method.

[0016] This application determines the backend problems in the project that are in the open state as risk data, and quickly determines the risk levels of the backend risk data according to the preset risk level classification strategy. At the same time, for the risk judgment of the first failure node in the project process, not only the relevance between the first failure node and the backend problems in the open state is considered, but also the priority values of the target type sub-nodes under the first failure node are combined to accurately judge the risk of the first failure node, and the risk level of the first failure node is determined according to the priority values, so as to avoid missing risk data.

[0017] The above description is only an overview of the technical solution of this application. In order to be able to understand the technical means of this application more clearly, it can be implemented according to the content of the specification. And in order to make the above and other purposes, features and advantages of this application more obvious and understandable, the following specifically illustrates the specific implementation manners of this application. Brief Description of the Drawings

[0018] The drawings here are incorporated into the specification and form a part of this specification, showing the embodiments consistent with this application, and are used together with the specification to explain the principles of this application. Obviously, the drawings in the following description are only some embodiments of this application. For those of ordinary skill in the art, other drawings can be obtained according to these drawings without creative efforts.

[0019] Figure 1 It is a schematic flowchart of a method for determining project risk data shown in an exemplary embodiment of this application.

[0020] Figure 2 Based on Figure 1 Another schematic flowchart of a method for determining project risk data shown in the exemplary embodiment.

[0021] Figure 3 It is a schematic diagram showing the complete situation of the subordinate chain of the second failure node shown in an exemplary embodiment of this application.

[0022] Figure 4 It is a schematic diagram showing the missing situation of the subordinate chain of the second failure node shown in an exemplary embodiment of this application.

[0023] Figure 5 Based on Figure 1 Another schematic flowchart of a method for determining project risk data shown in the exemplary embodiment.

[0024] Figure 6 Based on Figure 1 , Figure 2 , Figure 5 Another schematic flowchart of a method for determining project risk data shown in any one of the exemplary embodiments.

[0025] Figure 7 It is a schematic diagram showing the substitution of risk data into a preset valve point interval shown in an exemplary embodiment of the present application.

[0026] Figure 8 It is a display diagram of risk data shown in an exemplary embodiment of the present application.

[0027] Figure 9 It is a schematic diagram showing the detailed information display of a target display tile shown in an exemplary embodiment of the present application.

[0028] Figure 10 It is a schematic diagram of an application scenario of a method for determining project risk data of the present application.

[0029] Figure 11 It is a schematic structural diagram of a device for determining project risk data shown in an exemplary embodiment of the present application.

[0030] Figure 12 It is a schematic structural diagram of a computer system of an electronic device shown in an exemplary embodiment of the present application. Detailed implementation manners

[0031] Here, an exemplary embodiment will be described in detail, and its examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0032] The block diagrams shown in the drawings are only functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0033] The flowcharts shown in the drawings are only exemplary descriptions and do not necessarily include all contents and operations / steps, nor do they necessarily need to be executed in the described order. For example, some operations / steps can be decomposed, while some operations / steps can be combined or partially combined. Therefore, the actual execution order may change according to the actual situation.

[0034] In the present application, "a plurality of" means two or more. "And / or" describes the association relationship of associated objects and indicates that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0035] The R & D department generally focuses on analyzing various risk issues at the front end of project development and ignores the risk analysis of backend issues. However, certain backend issues can, to a certain extent, reflect front-end risks. If the integration of these backend issues is missing, front-end risk data will be omitted, resulting in the inability to comprehensively identify potential front-end risk issues and, even more, the inability to know the risk levels of the missing risk data. As a result, hierarchical overall management of risk data at all stages of the project cannot be carried out.

[0036] For this reason, one aspect of this application provides a method for determining project risk data. Specifically, please refer to Figure 1 , Figure 1 which is a flowchart showing a method for determining project risk data illustrated in an exemplary embodiment of this application. This determination method at least includes S110 to S130, which are introduced in detail as follows:

[0037] S110: Determine the backend issues in the project that are in the open state as risk data, and determine the risk levels corresponding to the backend issues in the open state according to the preset risk level classification strategy.

[0038] Backend issues are different types of issues that are characterized by feedback after the project runs or is launched into the market, including but not limited to customer complaints, after-sales repairs, etc. This application can determine the status of backend issues according to the status field in the problem record; if the backend issue is in the open state, it means that the backend issue has not been resolved and is still in an active state, and may continue to trigger risk incidents; if the backend issue is in the closed state, it means that the backend issue has been properly resolved, and the possibility of it triggering risks again is relatively low, and it is determined as non-risk data. As shown in Table 1, it is possible to quickly determine whether it is in the open state or the closed state according to the problem status value of 0 or 1, and it is also possible to quickly lock the associated failure nodes in the project process according to the associated failure node ID therein.

[0039] Table 1: Exemplary Backend Issue Table

[0040]

[0041]

[0042] The preset risk level classification strategy is a preset strategy for classifying the risk levels of project backend risk data. By combining it with the relevant parameters of the risk data for analysis, the risk levels corresponding to the risk data can be quickly determined.

[0043] Exemplarily, the preset risk level classification strategy indicates that the risk level of risk data is determined based on the recording time of risk data (i.e., the duration of the backend problem determined as risk data being in an open state) and the type of risk data. For example, if a backend problem of type A is in an open state at 8:00 and lasts until the current time 10:00, then according to the instructions of the preset risk level classification strategy, the duration of the backend problem is calculated to be 120 minutes, which is then multiplied by the first weight coefficient to calculate the first weight score; and the preset score corresponding to type A is multiplied by the second weight coefficient to calculate the second weight score; and the risk level corresponding to the risk data is determined based on the sum of the first weight score and the second weight score.

[0044] S120: If the first failure node in the project process is associated with an open backend problem, then the priority values ​​corresponding to the respective target type sub-nodes under the first failure node are determined according to the risk degree parameters of the respective target type sub-nodes.

[0045] Failed nodes are nodes in the project process where invalid or failed conditions occur. They can cover the operation nodes in the operation process of different components and systems in the project. For example, if a failure mode occurs in a certain operation node system, then the operation node is a failed node. The first failed node is a node associated with an open backend problem in the project to which it belongs. If a failed node is not associated with any backend problem, it indicates that the failed node currently has no substantial impact on the backend operation of the project, that is, there is no risk for the time being, and it is regarded as non-risk data.

[0046] Exemplarily, the backend issues in the open state in project A include backend issue a, backend issue b, and backend issue c. A failed node in project A is associated with backend issue b. Then, the risk level parameters of the subordinate target type sub-nodes of the failed node are obtained to determine their corresponding priority values.

[0047] The risk level parameter is a numerical value that characterizes the degree of corresponding risk of a node, which may include sub-level parameters of different types or dimensions. For example, the risk level parameter includes type A sub-level parameter, type B sub-level parameter, and type C sub-level parameter.

[0048] The priority value is a value used to represent the execution order of the node. The larger the priority value, the higher the execution order of the node.

[0049] There are multiple target type child nodes under the first failure node, and the target type refers to a collective concept of at least one risk type. For example, the target type refers to Q risk type, W risk type, and E risk type. Therefore, there may be multiple types of child nodes of the first failure node, and this embodiment does not specifically limit them.

[0050] Exemplarily, the sub - nodes of the target type under the failure node of DFMEA (Design Failure Mode and Effects Analysis) include preventive control sub - nodes, detective control sub - nodes, preventive measure sub - nodes, and detective measure sub - nodes; taking their respective risk degree parameters: severity (severity), occurrence (occurrence frequency), detection (detection difficulty) as input conditions, query in the exemplary AP (action Priority) rule table shown in Table 2 to obtain the priority values of each target type sub - node.

[0051] Table 2: Exemplary AP Rule Table

[0052]

[0053] In this embodiment, operations such as calculating the priority value will be performed for each target type sub - node to determine the corresponding priority value of each target type sub - node. However, the priority values of each target type sub - node cannot be obtained. If the priority values of the sub - nodes of the target type under the first failure node are all empty, that is, no priority value of any target type sub - node is determined, it indicates that the sub - nodes with corresponding risks under the first failure node will not be executed, and there are no risk hazards for the first failure node, and it is regarded as non - risk data.

[0054] S130: If the priority values of at least one target type sub - node are obtained, the first failure node is determined as risk data, and the risk level corresponding to the first failure node is determined according to the obtained at least one priority value; where the risk level of the failure node corresponds one - to - one with the risk level of the backend problem.

[0055] If the priority value of any target type sub - node is determined, it indicates that there are risk hazards for the first failure node, and it is regarded as risk data, and the obtained priority value is subjected to corresponding calculations or operations to determine the risk level corresponding to the first failure node.

[0056] Exemplarily, if three priority values are obtained, that is, the priority values corresponding to three target type sub - nodes respectively, the preset risk level corresponding to the average value of the three priority values is used as the risk level of the first failure node.

[0057] Another exemplarily, if three priority values are obtained, the preset risk level corresponding to the maximum value among the three priority values is used as the risk level of the first failure node.

[0058] In another example, if three priority values are obtained, the three priority values are respectively multiplied by their corresponding preset weight coefficients (determined according to the type of the child node corresponding to the priority value), and the preset risk level corresponding to the sum of the three products is used as the risk level of the first failure node. Among them, each target type corresponds to a corresponding preset weight coefficient.

[0059] By unifying the risk levels of the failure nodes and the risk levels of the back-end problems in this application, the number of risk levels of the two is made the same, thus facilitating the overall management of two different types of risk data. For example, both risk levels are divided into high, medium, and low according to the level of risk, so that the high risk level of the failure node type corresponds to the high risk level of the back-end problem type, the medium risk level of the failure node type corresponds to the medium risk level of the back-end problem type, and the low risk level of the failure node type corresponds to the low risk level of the back-end problem type, so that the risk levels of the two correspond one by one.

[0060] This application determines the back-end problems in the project that are in the open state as risk data, and quickly determines the risk levels of the back-end risk data according to the preset risk level division strategy. At the same time, for the risk judgment of the first failure node in the project process, not only the relevance between the first failure node and the back-end problems in the open state is considered, but also the priority values of the sub-nodes of the target type under the first failure node are combined to accurately judge the risk of the first failure node, and the risk level of the first failure node is determined according to the priority values, avoiding missing risk data. At the same time, this application realizes the purpose of overall management of two different types of risk data by making the risk levels of the failure nodes and the risk levels of the back-end problems correspond one by one, thus facilitating the analysis of the risk levels of all risk data.

[0061] The related technology does not combine and analyze the failure nodes and the back-end problems in the project process, nor does it analyze the status risk of the back-end problems. The status of the back-end problems includes not only the open state, but also the closed state, that is, the back-end problems of the solved problems. If the back-end problems in this state are not paid attention to, there may be missing risk points.

[0062] In another exemplary embodiment of this application, a method for determining the risk of another type of failure node in the project process is introduced in detail. For details, please refer to Figure 2 , Figure 2 is a schematic flowchart of another method for determining project risk data shown based on the exemplary embodiment shown in Figure 1 This determination method, on the basis of S110 to S130 shown in Figure 1 also includes at least S210, which is introduced in detail as follows:

[0063] S210: If the second failure node in the project process is associated with a backend problem in the closed state and there is a missing node in the chain to which the second failure node belongs, then determine the second failure node as risk data and determine the risk level of the second failure node as the preset risk level.

[0064] Figure 2 Only an example of the possible execution order of S210 is shown. Obviously, it can also be placed after S110. As is known, the present application does not limit its specific execution order.

[0065] The backend problem in the closed state is a resolved backend problem, that is, a backend problem that no longer poses a risk. If a failure node in the project process is associated with it, there may be a risk hidden danger in this failure node. To accurately determine whether this failure node is risk data, it is necessary to analyze the integrity of the chain to which it belongs; if it is complete, determine it as non-risk data; if it is missing, determine it as risk data. In this embodiment, for the judgment of chain integrity, it focuses on whether there are missing nodes in the chain, for example, whether there are missing target type nodes, whether the number of nodes meets the preset number, and similar such judgment conditions, to quickly determine whether the second failure node is risk data.

[0066] There are risk hidden dangers in the relevant failure nodes in the project process. The present application combines and analyzes the backend problems in the closed state to determine the failure nodes with risk hidden dangers, and based on whether there are missing nodes in the chain to which they belong, accurately determines whether they are risk data. Compared with the method of single determination for the failure node itself in the related art, the present application breaks through the barriers between the front end and the backend of the project, combines the data at both ends for risk analysis, and discovers the failure nodes with hidden risks in the project process.

[0067] Further, in another exemplary embodiment, it illustrates how to determine whether there is a missing node in the chain to which the second failure node belongs, and the details are introduced as follows: Detect whether the second failure node has a parent node, and whether the level of the top node in the chain to which the second failure node belongs is the preset level; if either is no, then determine that there is a missing node in the chain to which the second failure node belongs.

[0068] Please refer to Figure 3 , Figure 3 is a schematic diagram showing the situation where the chain to which the second failure node belongs is complete in an exemplary embodiment of the present application. From Figure 3 The two complete situations shown, it can be seen that the number of nodes in the chain to which the second failure node belongs is at least two, and the level of the top node in the chain must be the preset level level = 0. In some embodiments, the specific meaning of this preset level can be adaptively adjusted according to the actual situation.

[0069] Please refer to Figure 4 ,Figure 4 It is a schematic diagram showing the situation of the absence of the subordination chain of the second failure node shown in an exemplary embodiment of the present application. From Figure 4 the two absence situations shown, it can be seen that if the second failure node has no parent node, its subordination chain has only one node, that is, the second failure node itself, then it is determined that the node of the chain to which the second failure node belongs is missing. If the second failure node has a parent node, that is, the number of nodes in the subordination chain of the second failure node is two, but the level of the top node in its subordination chain is not the preset level level = 0, then it is determined that the node of the chain to which the second failure node belongs is missing.

[0070] In another exemplary embodiment of the present application, how to determine the respective corresponding priority values according to the risk degree parameters of the target type sub-nodes under the first failure node is introduced in detail. For details, please refer to Figure 5 , Figure 5 is based on Figure 1 a schematic flowchart of another method for determining project risk data shown in the exemplary embodiment shown. In S120 shown in Figure 1 this method at least further includes S510 to S540, which are introduced in detail as follows:

[0071] S510: Traverse each target type sub-node under the first failure node, and use the traversed target type sub-node as the focus sub-node.

[0072] The priority value of each target type sub-node is determined by traversing to ensure no omission.

[0073] S520: Match the risk degree parameter of the focus sub-node with the preset risk degree parameter.

[0074] The number of risk degree parameters and preset risk degree parameters can both be multiple. The matching process is to match the parameters of the same type one by one to determine the matching result.

[0075] S530: If the match fails, it is determined that the priority value corresponding to the focus sub-node is empty.

[0076] If the match fails, it means that there is no preset risk degree parameter that matches successfully, so the priority value corresponding to the relevant preset risk degree parameter cannot be obtained, that is, it is determined that the priority value corresponding to the focus sub-node is empty.

[0077] S540: If the match is successful, use the priority value corresponding to the preset risk degree parameter that matches successfully as the priority value of the focus sub-node to obtain the priority values of each target type sub-node.

[0078] It should be known that Figure 5Only the execution order between S530 and S540 is exemplified, and their execution order is not limited according to the label order. Specifically, corresponding steps are selectively executed according to the matching situation.

[0079] This application can determine the priority values of each target type of child nodes under the first failed node without omission by traversing them, and determine whether the priority value of the corresponding target type of child node is empty through a simple parameter matching method, without complex calculation processing, thus improving the efficiency of the priority value determination process.

[0080] Furthermore, in another exemplary embodiment, it is introduced that S520 at least further includes S5201 to S5202; among them, the risk degree parameters include different types of risk degree parameters; the number of preset risk degree parameters is multiple, and each preset risk degree parameter includes different types of sub-preset risk degree parameters, which are introduced in detail as follows:

[0081] S5201: Match the risk degree parameters of each type of the focus child node with the sub-preset risk degree parameters of the same type in the target preset risk degree parameter; among them, the target preset risk degree parameter is any one of the preset risk degree parameters.

[0082] Exemplarily, the nodes in the project process are the exemplary DFMEA (Design Failure Mode and Effects Analysis) nodes shown in Table 3, and the failed nodes in the project process can be quickly determined according to the node type.

[0083] Table 3: Exemplary DFMEA Node Information Table

[0084]

[0085]

[0086] Traverse the preventive control child node, detection control child node, preventive measure child node, and detection measure child node under the failed node of DFMEA; when traversing to the detection control child node (focus child node), match its risk degree parameters: severity (severity), occurrence (occurrence frequency), detection (detection difficulty) with the sub-preset risk degree parameters of the same type in the first preset risk degree parameter in turn; if the match fails, then match it with the sub-preset risk degree parameters of the same type in the second preset risk degree parameter, and so on. If it fails to match with all preset risk degree parameters, it means that the risk degree parameters of the detection control child node (focus child node) fail to match the preset risk degree parameters.

[0087] S5202: If the risk level parameters of all types are successfully matched, it indicates that the risk level parameters of the focal sub-node are successfully matched with the preset risk level parameters.

[0088] For the risk level parameters of all types in the focal sub-node to indicate that the risk level parameters of the focal sub-node are successfully matched with the preset risk level parameters, that is, to indicate that the risk level parameters of the focal sub-node are successfully matched with the preset risk level parameters, the risk level parameters of all types in the focal sub-node need to be successfully matched with the corresponding sub-preset risk level parameters in a preset risk level parameter.

[0089] In this application, a detailed classification and matching of the risk level parameters of the focal sub-node is performed. Each risk level parameter in the focal sub-node is separately matched with the corresponding sub-preset risk level parameter in each preset risk level parameter one by one, so as to determine the matching result of the focal sub-node according to each sub-matching result, making the matching result more reliable and improving the accuracy of the matching result.

[0090] In related technologies, project risk data is generally only recorded and stored. If analysts want to perform risk analysis on it, they need to manually check one by one and cannot quickly know the distribution of project risk data.

[0091] Therefore, in another exemplary embodiment of this application, a method for intuitively displaying project risk data is introduced in detail. For details, please refer to Figure 6 , Figure 6 is based on Figure 1 , Figure 2 , Figure 5 A schematic flowchart of another method for determining project risk data shown in any of the exemplary embodiments shown. Based on the above example steps, this determination method further includes at least S610 to S620, which are introduced in detail as follows:

[0092] S610: Substitute each risk data into the corresponding display block in the display diagram based on its occurrence time and the project to which it belongs; wherein, the display block is a block divided in the display diagram according to a preset threshold interval and different preset projects, and the preset threshold interval is an interval divided according to the corresponding time of the preset project stage node.

[0093] Projects of the same type follow a specific R & D process, and this R & D process can be divided into multiple project stage nodes. Each project stage node can be regarded as a preset threshold, and these preset thresholds can be recorded in the exemplary project information table shown in Table 4. Based on the times corresponding to these preset thresholds, the project can be divided into multiple preset threshold intervals in the time dimension, and the preset threshold intervals can be adaptively adjusted according to the project type.

[0094] Table 4: Exemplary project information table

[0095]

[0096] Here, the risk data refers to all risk data, that is, the risk data including the failure node type and the backend problem type. Each risk data records its own occurrence time. During the risk judgment process of some embodiments, the potential risks of some failure nodes in the project process are not discovered in time, resulting in the failure to record their occurrence times. In order to better integrate the risk data of the failure node type and the risk data of the backend problem type, the occurrence time of the backend problem associated with the risk data of the failure node type is used as the occurrence time of the risk data of the failure node type. The following combines Figure 7 , and gives an exemplary description of the division of the preset threshold point interval to which the risk data belongs; among them, Figure 7 is a schematic diagram showing the substitution of risk data into the preset threshold point interval shown in an exemplary embodiment of the present application.

[0097] Match the occurrence time of each risk data with the time in the preset threshold point interval to determine the preset threshold point interval corresponding to each risk data, so as to substitute each risk data into the corresponding preset threshold point interval.

[0098] S620: Determine the color of each display tile according to the number of risk data and the corresponding risk level in each display tile, so that each display tile displays the corresponding color and the number of risk data it contains; among them, the depth of the color is directly proportional to the number of risk data and the risk level.

[0099] Please refer to Figure 8 , Figure 8 is a display diagram of risk data shown in an exemplary embodiment of the present application. Among them, the first coordinate represents the preset threshold point interval, and the second coordinate represents the project; each display tile displays the number of risk data of the project in the corresponding preset threshold point interval, and the depth of the color of the display tile is positively correlated with the number of risk data and the risk level.

[0100] The present application associates risk data with time, and visually presents the risk situation within the preset threshold point interval corresponding to each project clearly, facilitating analysts to quickly obtain the distribution of risk data of any project.

[0101] Furthermore, in another exemplary embodiment, it is introduced how to respond to the user's trigger instruction to display the data details represented by the target display tile, and the specific introduction is as follows:

[0102] In response to a trigger instruction from a user for a target display tile, a quantity bar chart representing the risk data at different times in the target display tile is generated according to the risk data at each time in the target display tile and the risk levels corresponding to the risk data at each time; wherein, different colored bars in the quantity bar chart represent the risk data at different times, and the colors of the respective bars are determined according to the risk levels of the risk data represented by them.

[0103] The trigger instruction may be an instruction generated by the user through voice or touching the target display tile and sent to the execution entity of this application. It carries the identifier of the trigger object, enabling the execution entity of this application to quickly determine the target display tile from multiple display tiles, and quickly generate the corresponding quantity bar chart of the target display tile according to the risk data at each time represented by the target display tile and the risk levels corresponding to the risk data at each time. As Figure 9 shown, Figure 9 is a schematic diagram showing the detailed information display of the target display tile shown in an exemplary embodiment of this application. Among them, different colored bars in the quantity bar chart represent the risk data at different times, and the colors of the respective bars are determined according to the risk levels of the risk data represented by them. This quantity bar chart is displayed on the upper layer of the target display tile, facilitating the user to quickly know the details of the risk data represented by the target display tile and enabling the user to quickly focus on the risk data in any project and any valve point interval.

[0104] In another exemplary embodiment of this application, the application scenarios of the above-mentioned multiple determination methods are illustrated by examples. For details, please refer to Figure 10 , Figure 10 is a schematic diagram of the application scenario of the method for determining the project risk data of this application. Among them, it includes a user terminal 100, a display page 200, and a server 300. The three terminals can be connected by wireless communication. This application does not limit the connection method between them.

[0105] The user can input project information, trigger corresponding instructions, etc. through the user terminal 100. The display page 200 can display information on relevant risk data and a risk data display chart, so that the user can intuitively and clearly obtain the relevant risk data through the display page 200. The server 300, as the execution entity, executes the determination method shown in any of the above exemplary embodiments. The examples are as follows:

[0106] The server 300 determines the backend problems in the project that are in the enabled state as risk data, and determines the risk levels corresponding to the backend problems in the enabled state according to a preset risk level classification strategy; if the first failure node in the project process is associated with the backend problems in the enabled state, the server 300 determines the respective priority values according to the risk degree parameters of the target type child nodes subordinate to the first failure node; if the priority values of at least one target type child node are obtained, the server 300 determines the first failure node as risk data and determines the risk level corresponding to the first failure node according to the at least one obtained priority value; wherein, the risk levels of the failure nodes and the risk levels of the backend problems correspond one by one.

[0107] The server 300 can be understood as an independent physical server in the background of the display page 200, or a server cluster or distributed system composed of multiple physical servers. Among them, multiple servers can form a blockchain, and the server is a node on the blockchain. The server 300 can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. This is not limited here either.

[0108] Another aspect of the present application also provides a device for determining project risk data, as Figure 11 shown, Figure 11 is a schematic structural diagram of a device for determining project risk data shown in an exemplary embodiment of the present application. The determining device 1100 includes:

[0109] A first determining module 1110, configured to determine the backend problems in the project that are in the enabled state as risk data, and determine the risk levels corresponding to the backend problems in the enabled state according to a preset risk level classification strategy;

[0110] A second determining module 1130, configured to, if the first failure node in the project process is associated with the backend problems in the enabled state, determine the respective priority values according to the risk degree parameters of the target type child nodes subordinate to the first failure node;

[0111] A third determining module 1150, configured to, if the priority values of at least one target type child node are obtained, determine the first failure node as risk data and determine the risk level corresponding to the first failure node according to the at least one obtained priority value; wherein, the risk levels of the failure nodes and the risk levels of the backend problems correspond one by one.

[0112] In another exemplary embodiment, the determining device 1100 further includes:

[0113] A fourth determination module, configured to, if a second failure node in a project process is associated with a backend problem in a closed state and a node in the chain to which the second failure node belongs is missing, determine the second failure node as risk data and determine the risk level of the second failure node as a preset risk level.

[0114] In another exemplary embodiment, the method for determining that a node in the chain to which the second failure node belongs is missing includes:

[0115] Detecting whether the second failure node has a parent node and whether the level of the top node in the chain to which the second failure node belongs is a preset level;

[0116] If either is false, it is determined that a node in the chain to which the second failure node belongs is missing.

[0117] In another exemplary embodiment, the second determination module 1130 includes:

[0118] A traversal unit, configured to traverse each target type sub-node under the first failure node and use the traversed target type sub-node as a focus sub-node;

[0119] A matching unit, configured to match the risk degree parameter of the focus sub-node with a preset risk degree parameter;

[0120] A matching failure unit, configured to, if the matching fails, determine that the priority value corresponding to the focus sub-node is empty;

[0121] A matching success unit, configured to, if the matching succeeds, use the priority value corresponding to the preset risk degree parameter that matches successfully as the priority value of the focus sub-node, so as to obtain the priority values of each target type sub-node.

[0122] In another exemplary embodiment, the risk degree parameter includes different types of risk degree parameters; the number of preset risk degree parameters is multiple, and each preset risk degree parameter includes different types of sub-preset risk degree parameters; the matching unit includes:

[0123] A first matching section, configured to respectively match each type of risk degree parameter of the focus sub-node with the sub-preset risk degree parameter of the same type in a target preset risk degree parameter; wherein, the target preset risk degree parameter is any one of the preset risk degree parameters;

[0124] A matching success section, configured to, if all types of risk degree parameters are successfully matched, indicate that the risk degree parameter of the focus sub-node is successfully matched with the preset risk degree parameter.

[0125] In another exemplary embodiment, the determination device 1100 further includes:

[0126] A data substitution module for substituting each risk data into corresponding display blocks in a display graph based on their respective occurrence times and respective affiliated items; wherein, the display blocks are blocks obtained by dividing the display graph according to a preset threshold point interval and different preset items, and the preset threshold point interval is an interval obtained by dividing according to the corresponding times of preset project stage nodes;

[0127] A block determination module for determining the colors of each display block according to the quantity of risk data and the corresponding risk level in each display block, so that each display block displays the corresponding color and the quantity of risk data it contains; wherein, the depth of the color is directly proportional to the quantity of risk data and the risk level.

[0128] In another exemplary embodiment, the determination device 1100 further includes:

[0129] A response module for generating a quantity bar graph representing the risk data at different times in a target display block in response to a trigger instruction of a user for the target display block, according to the risk data at each time in the target display block and the risk level corresponding to the risk data at each time; wherein, different colored bars in the quantity bar graph represent the risk data at different times, and the color of each colored bar is determined according to the risk level of the risk data it represents.

[0130] The determination device of the present application determines the backend problems in the project that are in the open state as risk data, and quickly determines the risk levels of the backend risk data according to a preset risk level division strategy. At the same time, for the risk judgment of the first failure node in the project process, not only the relevance between the first failure node and the backend problems in the open state is considered, but also the priority value of the target type sub-nodes subordinate to the first failure node is combined to accurately judge the risk of the first failure node, and the risk level of the first failure node is determined according to the priority value, so as to avoid missing risk data. At the same time, the determination device of the present application realizes the purpose of overall management of two different types of risk data by corresponding the risk levels of the failure nodes and the risk levels of the backend problems one by one, so as to facilitate the risk degree analysis of all risk data.

[0131] It should be noted that the determination device provided in the above embodiment and the determination method provided in the foregoing embodiment belong to the same concept. The specific manners in which each module and unit perform operations have been described in detail in the method embodiment and will not be elaborated here.

[0132] On the other hand, the present application also provides an electronic device, including: a controller; a memory for storing one or more programs, which when executed by the controller, are used to execute the above determination method.

[0133] Please refer to Figure 12 , Figure 12 which is a schematic structural diagram of a computer system of an electronic device shown in an exemplary embodiment of the present application, and shows a schematic structural diagram of a computer system of an electronic device suitable for implementing the embodiments of the present application.

[0134] It should be noted that Figure 12 the computer system 1200 of the electronic device shown is only an example, and should not impose any limitations on the functions and usage scope of the embodiments of the present application.

[0135] As Figure 12 shown, the computer system 1200 includes a central processing unit (CPU) 1201, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1202 or the program loaded from the storage section 1208 into the random access memory (RAM) 1203, such as executing the methods in the above embodiments. In the RAM 1203, various programs and data required for system operation are also stored. The CPU 1201, ROM 1202, and RAM 1203 are connected to each other via a bus 1204. The input / output (I / O) interface 1205 is also connected to the bus 1204.

[0136] The following components are connected to the I / O interface 1205: an input section 1206 including a keyboard, a mouse, etc.; an output section 1207 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; a storage section 1208 including a hard disk, etc.; and a communication section 1209 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the I / O interface 1205 as required. A removable medium 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1210 as required, so that the computer program read from it can be installed into the storage section 1208 as required.

[0137] In particular, according to an embodiment of the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, an embodiment of the present application includes a computer program product that includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication section 1209, and / or installed from the removable medium 1211. When the computer program is executed by the central processing unit (CPU) 1201, various functions defined in the system of the present application are executed.

[0138] It should be noted that the computer-readable medium shown in the embodiments of the present application can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, the computer-readable storage medium can be any tangible medium that contains or stores a program, and the program can be used by or in combination with an instruction execution system, apparatus, or device. In the present application, the computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable computer program is carried. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, and the computer-readable medium can send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The computer program included on the computer-readable medium can be transmitted by any suitable medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0139] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. Among them, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code, and the above-mentioned module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, as well as the combination of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0140] The units involved in the embodiments described in the present application can be implemented in software or in hardware, and the described units can also be provided in a processor. Among them, the names of these units do not constitute a limitation to the unit itself in some cases.

[0141] Another aspect of the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the above-mentioned determination method is implemented. The computer-readable storage medium can be included in the electronic device described in the above embodiments, or can exist separately and not be assembled into the electronic device.

[0142] Another aspect of the present application also provides a computer program product or a computer program. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the determination method provided in the above various embodiments.

[0143] According to one aspect of the embodiments of the present application, a computer system is further provided, including a Central Processing Unit (CPU), which can perform various appropriate actions and processes according to the program stored in the Read-Only Memory (ROM) or the program loaded from the storage part into the Random Access Memory (RAM), such as executing the methods in the above embodiments. In the RAM, various programs and data required for system operation are also stored. The CPU, ROM, and RAM are connected to each other via a bus. The Input / Output (I / O) interface is also connected to the bus.

[0144] The following components are connected to the I / O interface: an input part including a keyboard, a mouse, etc.; an output part including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), etc. and a speaker, etc.; a storage part including a hard disk, etc.; and a communication part including a network interface card such as a Local Area Network (LAN) card, a modem, etc. The communication part performs communication processing via a network such as the Internet. A drive is also connected to the I / O interface as needed. Removable media, such as magnetic disks, optical disks, magneto-optical disks, semiconductor memories, etc., are installed on the drive as needed so that the computer program read from them can be installed into the storage part as needed.

[0145] The above content is only a preferred exemplary embodiment of the present application and is not used to limit the implementation of the present application. Those of ordinary skill in the art can easily make corresponding adaptations or modifications according to the main concept and spirit of the present application. Therefore, the protection scope of the present application should be subject to the protection scope required by the claims.

Claims

1. A method for determining project risk data, characterized in that: The determination method comprises: Determine the backend issues in the project that are in an open state as risk data, and determine the risk level corresponding to the backend issues in the open state according to the preset risk level classification strategy; If the first failure node in the project process is associated with the backend problem in the open state, then determining the priority values ​​corresponding to the respective target type sub-nodes under the first failure node according to the risk degree parameters of the respective target type sub-nodes; If the priority value of at least one target type sub-node is obtained, the first failed node is determined as the risk data, and the risk level corresponding to the first failed node is determined based on the at least one priority value obtained; wherein the risk level of the failed node corresponds one-to-one to the risk level of the backend problem.

2. The determination method according to claim 1, characterized in that: The determination method further comprises: If the second failure node in the project process is associated with a backend problem in a closed state, and the chain to which the second failure node belongs is missing a node, the second failure node is determined as the risk data, and the risk level of the second failure node is determined as a preset risk level.

3. The determination method according to claim 2, characterized in that: The method for determining the missing node of the chain to which the second failed node belongs includes: Detecting whether the second failed node has a parent node, and whether the level to which the top node in the subordinate chain of the second failed node belongs is a preset level; If any one of them is no, then determine the missing node of the chain to which the second failed node belongs.

4. The determination method according to claim 1, characterized in that: The determining, according to the risk level parameters of the target type sub-nodes under the first failure node, the respective corresponding priority values ​​includes: Traversing each target type child node under the first invalid node, and taking the traversed target type child node as the focus child node; Matching the risk level parameter of the focus sub-node with a preset risk level parameter; If the match fails, it is determined that the priority value corresponding to the focus subnode is empty; If the match is successful, the priority value corresponding to the preset risk level parameter that is successfully matched is used as the priority value of the focus sub-node to obtain the priority values ​​of each target type sub-node.

5. The determination method according to claim 4, characterized in that: The risk level parameter includes different types of risk level parameters; the number of the preset risk level parameters is multiple, and each preset risk level parameter includes different types of sub-preset risk level parameters; The matching of the risk level parameter of the focus sub-node with a preset risk level parameter includes: Matching the risk degree parameters of each type of the focus sub-node with the sub-preset risk degree parameters of the same type in the target preset risk degree parameter; wherein the target preset risk degree parameter is any of the preset risk degree parameters; If all types of risk level parameters are matched successfully, then the risk level parameter representing the focus sub-node is matched successfully with the preset risk level parameter.

6. The determination method according to any one of claims 1 to 5, characterized in that: The determination method further comprises: Substitute each risk data into a corresponding display block in the display diagram based on the respective occurrence time and the respective subordinate project; wherein the display block is a block obtained by dividing the display diagram according to the preset valve point interval and different preset projects, and the preset valve point interval is an interval obtained by dividing according to the corresponding time of the preset project stage node; According to the amount of risk data in each display block and the corresponding risk level, the color of each display block is determined so that each display block displays the corresponding color and the amount of risk data contained in each display block; wherein the color depth is proportional to the amount of risk data and the risk level.

7. The determination method according to claim 6, characterized in that: The determination method further comprises: In response to a user's trigger instruction for a target display tile, a quantity bar graph representing the risk data at different moments in the target display tile is generated according to the risk data at each moment in the target display tile and the risk level corresponding to the risk data at each moment; wherein different color columns in the quantity bar graph represent the risk data at different moments, and the color of each color column is determined according to the risk level of the risk data represented by each column.

8. A device for determining project risk data, characterized in that: The determining device comprises: A first determination module is used to determine the backend problems in the project that are in an open state as risk data, and determine the risk level corresponding to the backend problems in the open state according to a preset risk level classification strategy; A second determination module is used to determine the priority values ​​corresponding to the target type sub-nodes under the first failure node according to the risk degree parameters of the target type sub-nodes under the first failure node if the first failure node in the project process is associated with the backend problem in the open state; The third determination module is used to determine the first failure node as the risk data if the priority value of at least one target type sub-node is obtained, and determine the risk level corresponding to the first failure node according to the at least one priority value obtained; wherein the risk level of the failure node corresponds one-to-one to the risk level of the backend problem.

9. An electronic device, characterized in that: include: Controller; A memory for storing one or more programs, which, when executed by a controller, enables the controller to implement the determination method described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: Computer-readable instructions are stored thereon, and when the computer-readable instructions are executed by a processor of a computer, the computer is caused to execute the determination method according to any one of claims 1 to 7.

Images