CN111291375B - Application program evaluation method and device, computer equipment and storage medium - Google Patents

Abstract

The application relates to an application program evaluation method, an application program evaluation device, computer equipment and a storage medium. The method comprises the following steps: determining a first research and development guarantee level of each top-level function module of the application program according to the danger level of the application program, and then establishing a dependency relationship tree corresponding to each top-level function module, wherein the dependency relationship tree comprises the dependency relationship between the top-level function module and each sub-function module corresponding to the top-level function module; and finally, for each top-level function module, determining a second research and development guarantee level of each sub-function module corresponding to the top-level function module according to the first research and development guarantee level and the dependency relationship tree. By adopting the method, the research and development guarantee level of the application program can be accurately evaluated.

Description

Application evaluation method, apparatus, computer equipment and storage medium

technical field

The present application relates to the field of computer technology, and in particular, to an application evaluation method, apparatus, computer device and storage medium.

Background technique

With the development of computer technology, the development of application programs has become common. When developing an application program, it is necessary to evaluate the security level of the application program to determine the research and development assurance level of the application program. Among them, the security level of the application program is It is used to characterize the degree to which the failure of the application has an impact on the safety of system operation or the completion of tasks. Generally, the higher the security level of the application, the higher the R&D assurance level of the application, and the higher the R&D assurance level means the application The higher the human and material resources for program development, on the contrary, the lower the security level of the application, the lower the application development assurance level.

Commonly, a security level can be artificially determined for the application program according to the degree of impact on the entire system and personnel when the application program fails, and then the R&D assurance level of the application program can be obtained according to the security level of the application program.

However, the related technology considers relatively simple factors when determining the security level of an application program, so the obtained security level is imprecise, which in turn leads to the problem of inaccuracy in the research and development assurance level of the finally obtained application program.

SUMMARY OF THE INVENTION

Based on this, it is necessary to provide an accurate application evaluation method, apparatus, computer equipment and storage medium for the above technical problems.

In a first aspect, an application evaluation method is provided, the method comprising:

The first R&D assurance level of each top-level functional module of the application is determined according to the danger level of the application, where the danger level includes the severity level of the dangerous consequences caused by the failure of the application, the frequency of the application being exposed to external dangerous events At least one of the degree level and the probability level of the occurrence of the external dangerous event, in the application program, each of the top-level function modules corresponds to at least one sub-function module, and each of the top-level function modules depends on the top-level function module. each of the sub-function modules;

For each of the top-level functional modules, a dependency tree corresponding to the top-level functional module is established, and the dependency tree includes the dependencies between the top-level functional module and each of the sub-functional modules corresponding to the top-level functional module;

For each top-level functional module, according to the first R&D assurance level and the dependency tree, a second R&D assurance level of each sub-function module corresponding to the top-level functional module is determined.

In one embodiment, the first R&D assurance level of each top-level functional module of the application is determined according to the risk level of the application, including:

Get the risk level matrix table;

Determine the hazard level of the application by querying the hazard level matrix table;

The first R&D assurance level of each top-level functional module of the application is determined according to the danger level of the application.

In one of the embodiments, the dependency relationship includes a serial dependency relationship, and the serial dependency relationship is used to represent that the premise of ensuring the normal operation of the top-level functional module is that all sub-function modules corresponding to the top-level functional module work normally. According to the first The R&D assurance level and the dependency tree determine the second R&D assurance level of each sub-function module corresponding to the top-level functional module, including:

The first R&D guarantee level is used as the second R&D guarantee level of each sub-function module corresponding to the top-level functional module.

In one of the embodiments, the dependency relationship includes a parallel dependency relationship, and the parallel dependency relationship is used to represent that the premise of ensuring the normal operation of the top-level functional module is to ensure that any sub-function module corresponding to the top-level functional module is normal. The first R&D assurance level and the dependency tree determine the second R&D assurance level of each sub-function module corresponding to the top-level functional module, including:

Use the first R&D guarantee level as the second R&D guarantee level of at least one sub-function module in each of the sub-function modules corresponding to the top-level functional module; or,

A third R&D guarantee level is used as the second R&D guarantee level of at least two sub-function modules in each of the sub-function modules corresponding to the top-level functional module, and the third R&D guarantee level is lower than the first R&D guarantee level.

In one of the embodiments, the dependency includes a series-parallel dependency and a parallel-series dependency, and the series-parallel dependency and the parallel-series dependency are used to represent the premise of ensuring that the top-level functional module works normally. All the sub-function modules in the series relationship in the corresponding sub-function modules work normally, and any sub-function module in the parallel relationship works normally, the top level is determined according to the first R&D guarantee level and the dependency tree. The second R&D assurance level of each sub-function module corresponding to the functional module includes:

The first R&D guarantee level of the top-level functional module is taken as the second R&D guarantee level of at least one sub-function module in the sub-function modules in the parallel relationship among the sub-function modules corresponding to the top-level functional module, or the third R&D guarantee level The R&D guarantee level is used as the second R&D guarantee level of at least two sub-function modules in the sub-function modules in parallel relationship among the sub-function modules corresponding to the top-level functional module, and the third R&D guarantee level is lower than the first R&D guarantee level ;

Use the first R&D guarantee level as the second R&D guarantee level of the sub-function modules in the series relationship among the sub-function modules corresponding to the top-level functional module, or use the fourth R&D guarantee level as the sub-function corresponding to the top-level functional module. The second R&D guarantee level of at least one sub-function module in the series relationship in the parallel relationship among the functional modules, and the fourth R&D guarantee level is the highest among the sub-function modules in the parallel relationship among the sub-function modules corresponding to the top-level functional module. R&D Assurance Level.

In one embodiment, the dependency relationship includes a voting relationship, and the voting relationship is used to represent that the premise of ensuring that the top-level functional module is normal is to ensure that a preset number of sub-functional modules in the sub-functional modules corresponding to the top-level functional module are normal. , the second R&D guarantee level of each sub-function module corresponding to the top-level functional module is determined according to the first R&D guarantee level and the dependency tree, including:

Taking the first R&D guarantee level of the top-level functional module as the second R&D guarantee level of the sub-function module at the voter position in each of the sub-function modules corresponding to the top-level functional module;

The first R&D guarantee level of the top-level functional module is taken as the second R&D guarantee level of at least one sub-function module that is not in the position of the voter in each of the sub-function modules corresponding to the top-level functional module, or the third R&D guarantee level As the second R&D guarantee level of at least two sub-function modules that are not in the voter position among the sub-function modules corresponding to the top-level functional module, the third R&D guarantee level is lower than the first R&D guarantee level.

In one embodiment, after determining the second R&D assurance level of each of the sub-function modules corresponding to the top-level functional module according to the first R&D assurance level and the dependency tree, the method further includes:

Determine the probability level that the application fails to avoid hazardous events;

The second R&D assurance level is adjusted according to the probability level that the application fails to avoid the hazardous event.

In one embodiment, the second R&D assurance level is adjusted according to the probability level that the application program fails to avoid the dangerous event, including:

When the probability level of the application program failing to avoid the dangerous event falls within the preset level range, the level of the second R&D guarantee level is increased.

In a second aspect, an application evaluation device is provided, the device comprising:

The first determination module is used to determine the first R&D assurance level of each top-level functional module of the application program according to the risk level of the application program, where the risk level includes the severity level of the dangerous consequences caused by the failure of the application program, the application program At least one of the frequency level of exposure of the program to an external dangerous event and the probability level of the occurrence of the external dangerous event, in the application program, each of the top-level functional modules corresponds to at least one sub-functional module, and each of the top-level functional modules Depends on each of the sub-function modules corresponding to the top-level function module;

A building module is used to establish, for each of the top-level functional modules, a dependency tree corresponding to the top-level functional module, where the dependency tree includes the dependencies between the top-level functional module and each of the sub-function modules corresponding to the top-level functional module ;

The second determining module is configured to, for each top-level functional module, determine the second R&D assurance level of each sub-function module corresponding to the top-level functional module according to the first R&D assurance level and the dependency tree.

In one of the embodiments, the first determining module is specifically configured to obtain a risk level matrix table; determine the risk level of the application program by querying the risk level matrix table; determine the risk level of the application program according to the risk level of the application program The first R&D assurance level of a top-level functional module.

In one of the embodiments, the dependency relationship includes a serial dependency relationship, and the serial dependency relationship is used to represent that the premise of ensuring that the top-level functional module works normally is that all sub-functional modules corresponding to the top-level functional module work normally, and the second determining module Specifically, the first R&D guarantee level is used as the second R&D guarantee level of each sub-function module corresponding to the top-level functional module.

In one of the embodiments, the dependency relationship includes a parallel dependency relationship, and the parallel dependency relationship is used to represent that the premise of ensuring the normal operation of the top-level functional module is to ensure that any sub-function module corresponding to the top-level functional module is normal, and the second The determining module is specifically used to take the first R&D guarantee level as the second R&D guarantee level of at least one sub-function module in each of the sub-function modules corresponding to the top-level functional module; or, take the third R&D guarantee level as the top-level function The second R&D guarantee level of at least two sub-function modules in each of the sub-function modules corresponding to the module, and the third R&D guarantee level is lower than the first R&D guarantee level.

In one of the embodiments, the dependency includes a series-parallel dependency and a parallel-series dependency, and the series-parallel dependency and the parallel-series dependency are used to represent the premise of ensuring that the top-level functional module works normally. All the sub-function modules in the series relationship in the corresponding sub-function modules work normally, and any sub-function module in the parallel relationship is in normal operation. A research and development assurance level is used as the second research and development assurance level of at least one sub-function module in the sub-function modules in the parallel relationship among the sub-function modules corresponding to the top-level functional module, or a third research and development assurance level is used as the top-level functional module. Corresponding to the second R&D guarantee level of at least two sub-function modules in the sub-function modules in a parallel relationship among the sub-function modules, the third R&D guarantee level is lower than the first R&D guarantee level; the first R&D guarantee level As the second research and development assurance level of the sub-function modules in the series relationship among the sub-function modules corresponding to the top-level functional module The second R&D guarantee level of at least one sub-functional module in the series relationship of the top-level functional modules, and the fourth R&D guarantee level is the highest R&D guarantee level among the sub-functional modules in the parallel relationship among the sub-functional modules corresponding to the top-level functional module.

In one embodiment, the dependency relationship includes a voting relationship, and the voting relationship is used to represent that the premise of ensuring that the top-level functional module is normal is to ensure that a preset number of sub-functional modules in the sub-functional modules corresponding to the top-level functional module are normal. , the second determination module is specifically used to take the first R&D guarantee level of the top-level functional module as the second R&D guarantee level of the sub-function module located at the voter position in each of the sub-function modules corresponding to the top-level functional module; The first R&D guarantee level of the top-level functional module is taken as the second R&D guarantee level of at least one sub-function module that is not in the position of the voter among the sub-function modules corresponding to the top-level functional module, or the third R&D guarantee level is taken as The second R&D guarantee level of at least two sub-function modules that are not in the voter position among the sub-function modules corresponding to the top-level functional module, and the third R&D guarantee level is lower than the first R&D guarantee level.

In one embodiment, the device further includes an adjustment module, the adjustment module is used to determine the probability level that the application program fails to avoid the dangerous event; adjust the first probability level according to the probability level that the application program fails to avoid the dangerous event 2. R&D guarantee level.

In one embodiment, the adjustment module is specifically configured to increase the level of the second R&D guarantee level when the probability level of the application program failing to avoid the dangerous event falls within a preset level range.

In a third aspect, a computer device is provided, including a memory and a processor, where the memory stores a computer program, and when the processor executes the computer program, the application program evaluation method described in any one of the above-mentioned first aspect is implemented.

In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, implements the application program evaluation method described in any one of the above-mentioned first aspect.

The above-mentioned application evaluation method, device, computer equipment and storage medium, by determining the first R&D assurance level of each top-level functional module of the application according to the danger level of the application, where the danger level includes the danger caused by the failure of the application At least one of a severity level of consequences, a frequency level of exposure of the application to an external dangerous event, and a probability level of the occurrence of the external dangerous event, in the application, each of the top-level functional modules is associated with at least one sub-functional module. Correspondingly, each of the top-level functional modules depends on each of the sub-function modules corresponding to the top-level functional module; then for each of the top-level functional modules, a dependency tree corresponding to the top-level functional module is established, and the dependency tree includes the top-level function. The dependencies between the modules and the sub-functional modules corresponding to the top-level functional modules; finally, for each of the top-level functional modules, according to the first R&D assurance level and the dependency tree, determine the corresponding top-level functional modules. The second R&D assurance level for sub-function modules. Because of the application evaluation method provided in this application, when evaluating the R&D assurance level of an application, various influencing factors that affect the risk level of the application are fully considered, and each application is determined according to the dependencies between the functional modules in the application. The R&D assurance level of functional modules makes the final evaluation of the application development assurance level more accurate.

Description of drawings

1 is an application environment diagram of an application evaluation method in one embodiment;

2 is a schematic flowchart of an application evaluation method in one embodiment;

3 is a schematic flowchart of a method for determining a first R&D assurance level of each top-level functional module of an application in an application evaluation method according to an embodiment;

FIG. 4 is a dependency tree diagram of concatenated dependencies in one embodiment;

5 is a dependency tree diagram of parallel dependencies in one embodiment;

6 is a dependency tree diagram of a series-parallel dependency in one embodiment;

FIG. 7 is a dependency tree diagram of parallel and concatenated dependencies in one embodiment;

8 is a dependency tree diagram of a voting relationship in one embodiment;

9 is a schematic flowchart of a method for adjusting a second R&D assurance level in an application evaluation method according to an embodiment;

10 is a structural block diagram of an apparatus for evaluating an application program in one embodiment;

11 is a structural block diagram of an apparatus for evaluating an application program in another embodiment;

Figure 12 is a diagram of the internal structure of a computer device in one embodiment.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application more clearly understood, the present application will be described in further 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 application, but not to limit the present application.

With the development of computer technology, application development has become common. For example, in the development of airborne systems, a new generation of airborne systems has become a typical application-intensive system. Airborne applications undertake core functions such as flight control, power control, avionics integration, mission planning, and safety alerts. It has a significant impact on flight safety and mission completion. At the same time, the system security problems caused by the failure of the airborne application system are increasing day by day. According to statistics, in the modern airborne equipment, the failure caused by the software has accounted for more than 70% of the total number of failures. Once a critical application fails or fails, it can lead to mission failure, equipment damage and even casualties. Therefore, in the development process of my country's airborne applications, the application security level has been the focus of attention.

When developing an application, it is necessary to evaluate the security level of the application to determine the R&D assurance level of the application. Among them, the security level of the application is used to represent the degree to which the failure of the application affects the system operation safety or task completion. Generally, the higher the security level of the application, the higher the research and development assurance level of the application. The higher the level, the higher the human and material resources invested in the research and development of the application. Conversely, the lower the security level of the application, the lower the level of guarantee for the research and development of the application.

Commonly, a security level can be artificially determined for the application program according to the degree of impact on the entire system and personnel when the application program fails, and then the R&D assurance level of the application program can be obtained according to the security level of the application program.

However, the related technology considers relatively simple factors when determining the security level of an application program, so the obtained security level is imprecise, which in turn leads to the problem of inaccuracy in the research and development assurance level of the finally obtained application program.

The application evaluation method provided in this application can be applied to the application environment shown in FIG. 1 . Wherein, the terminal 101 can be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers and portable wearable devices.

In one embodiment, as shown in FIG. 2 , a method for evaluating an application program is provided, and the method is applied to the terminal 101 in FIG. 1 as an example for description, including the following steps:

Step 201, the terminal determines the first R&D assurance level of each top-level functional module of the application program according to the risk level of the application program, the risk level includes the severity level of the dangerous consequences caused by the failure of the application program, the exposure of the application program to the outside At least one of the frequency level of the dangerous event and the probability level of the occurrence of the external dangerous event, in this application, each of the top-level functional modules corresponds to at least one sub-functional module, and each of the top-level functional modules depends on the Each sub-function module corresponding to the top-level function module.

In this step, in order to accurately assess the risk level of the application, it is necessary to comprehensively consider three factors. They are the severity level of the dangerous consequences (denoted by C in this application), the frequency level of the application program's exposure to external dangerous events (denoted by F in this application), and the probability level of the occurrence of external dangerous events (denoted by F in this application), respectively. Denoted by W in this application). The above three levels will now be described in detail.

1. The severity level C of the dangerous consequences caused by the failure of the application

1) The functional hazard assessment (English: FHA) method can be used to analyze the system hazard events (English: FC) caused by the failure of the application program. According to the system function and the task stage, analyze the consequences of FC on the system;

2) According to the impact of the consequences of dangerous events, combined with Table 1, quantitatively evaluate the severity level C of the consequences of dangerous events caused by the application (divided into five levels of A, B, C, D and E).

2. The frequency level of application exposure to external dangerous events is F

1) Use probabilistic risk assessment method (English: PRA) and regional safety analysis (English: ZSA) to analyze the categories of external dangerous events that the application may come into contact with. Combined with the running characteristics and architecture of the application, determine the possibility that the application will interact with the external dangerous events, that is, the frequency value;

2) According to the frequency value of the interaction between the application program and the external danger source when the application program is running, combined with Table 2, quantitatively evaluate the frequency level F (divided into H, M, O and L four levels) of the application program contacting external hazardous events.

3. Probability level W of external dangerous events

1) Obtain the approximate evaluation value W of the occurrence probability of external dangerous events through statistical analysis of empirical data, expert experience or simulation of abnormal excitation conditions;

2) According to the approximate evaluation value W of the probability of occurrence of external dangerous events, combined with Table 3, determine the "probability of occurrence of dangerous events W" (divided into five levels of 1, 2, 3, 4 and 5).

Table 1

Table 2

table 3

After obtaining the severity level C of the dangerous consequences caused by the failure of the application program, the frequency level F of the application program's exposure to external dangerous events, and the probability level W of the occurrence of external dangerous events. The first R&D assurance level of each top-level functional module of the application may be determined according to at least one of the levels. Generally speaking, the higher the risk level, the higher the corresponding R&D guarantee level.

Step 202: For each top-level functional module, the terminal establishes a dependency tree corresponding to the top-level functional module, where the dependency tree includes the dependency between the top-level functional module and each sub-function module corresponding to the top-level functional module.

In an application, there are generally multiple functional modules, some of which are top-level functional modules, and the functions implemented by the top-level functional modules need to rely on sub-functional modules. It can be understood that the realization of some basic functions of the application requires the realization of other functions as a prerequisite. Therefore, a dependency tree between each functional module can be established according to the functional division of the application.

Step 203: For each top-level functional module, the terminal determines a second R&D assurance level of each sub-function module corresponding to the top-level functional module according to the first R&D assurance level and the dependency tree.

In this step, after the research and development assurance level of the top-level functional module is determined, a corresponding research and development assurance level is assigned to each sub-function module corresponding to the top-level functional module according to the pre-determined dependency tree. Generally speaking, in a dependency tree, the R&D assurance level of the top-level functional module is the highest, and the R&D assurance level of its corresponding sub-function module should be equal to or appropriately lower than the first R&D assurance level of the top-level functional module.

In the above application evaluation method, the first R&D assurance level of each top-level functional module of the application is determined according to the danger level of the application, where the danger level includes the severity level of the dangerous consequences caused by the failure of the application, the At least one of a frequency level of exposure of an application to an external dangerous event and a probability level of the occurrence of the external dangerous event, in the application, each top-level function module corresponds to at least one sub-function module, and each top-level function module corresponds to at least one sub-function module. The module depends on each of the sub-function modules corresponding to the top-level function module; then for each of the top-level function modules, a dependency tree corresponding to the top-level function module is established, and the dependency tree includes the top-level function module corresponding to the top-level function module. The dependencies between the sub-functional modules; finally, for each of the top-level functional modules, according to the first R&D assurance level and the dependency tree, determine the second R&D of each of the sub-functional modules corresponding to the top-level functional module Guaranteed level. Because of the application evaluation method provided in this application, when evaluating the R&D assurance level of an application, various influencing factors that affect the risk level of the application are fully considered, and each application is determined according to the dependencies between the functional modules in the application. The R&D assurance level of functional modules makes the final evaluation of the application development assurance level more accurate.

In the embodiment of the present application, referring to FIG. 3, a method for determining the first R&D assurance level of each top-level functional module of the application program in an application program evaluation method is provided, and the method includes:

Step 301, the terminal obtains the risk level matrix table.

In this step, a risk level matrix table (as shown in Table 4) may be established according to the three tables provided in the foregoing step 201 . In Table 4, the danger level is divided into five levels, which are represented by lowercase a, b, c, d, and e respectively. The smaller the letter, the higher the hazard risk level; the core factor in determining the hazard level is "the severity level C of the dangerous consequences caused by the failure of the application"; in addition, "the frequency level of the application exposure to external dangerous events" and "Probability level W of external hazardous events" plays a role in adjusting the risk level.

Table 4

Step 302, the terminal determines the risk level of the application by querying the risk level matrix table.

Step 303, the terminal determines the first R&D assurance level of each top-level functional module of the application program according to the risk level of the application program.

In this step, each top-level function can be matched to the corresponding first R&D assurance level with reference to the corresponding relationship between the hazard level and the R&D assurance level given in Table 5.

table 5

Levels of danger Corresponding R&D Assurance Level catastrophic a A dangerous b B major c C slight d D No security impacte E

In this embodiment of the present application, five kinds of dependencies between top-level functional modules and sub-functional modules are provided. Specifically, it includes: series dependency, parallel dependency, series-parallel dependency, parallel-series dependency, and voting relationship. These five dependencies are described in detail below.

1. Serial dependencies (Figure 4 provides a dependency tree diagram of serial dependencies, and only three sub-function modules are exemplarily given in Figure 4)

The serial dependency is used to represent that the premise of ensuring the normal operation of the top-level functional module is that all sub-function modules corresponding to the top-level functional module work normally. Simply put, the failure of any sub-functional module under the top-level functional module will cause the top-level functional module to fail, and the dependency tree corresponding to the concatenated dependency is the "OR" gate. When the tandem dependency relationship is satisfied between the top-level functional module and the sub-functional module of the application, the specific method for determining the second R&D assurance level of each sub-functional module corresponding to the top-level functional module is as follows:

The terminal uses the first R&D guarantee level as the second R&D guarantee level of each sub-function module corresponding to the top-level functional module.

2. Parallel dependency relationship (Figure 5 provides a dependency tree diagram of parallel dependency relationship, and only three sub-function modules are exemplarily given in Figure 5)

The parallel dependency is used to characterize the premise of ensuring the normal operation of the top-level functional module is to ensure that any sub-functional module corresponding to the top-level functional module is normal. The top-level functional module fails, and the dependency tree corresponding to the parallel dependency is an "AND" gate. When a parallel dependency relationship is satisfied between the top-level functional module and the sub-functional module of the application, the specific method for determining the second R&D assurance level of each sub-functional module corresponding to the top-level functional module is as follows:

The terminal uses the first R&D guarantee level as the second R&D guarantee level of at least one sub-function module in each of the sub-function modules corresponding to the top-level functional module; or,

The terminal uses a third R&D guarantee level as the second R&D guarantee level of at least two sub-function modules in each of the sub-function modules corresponding to the top-level functional module, and the third R&D guarantee level is lower than the first R&D guarantee level.

3. The series-parallel dependency and the parallel-series dependency (Figure 6 provides a dependency tree diagram of the series-parallel dependency, only five sub-function modules are exemplarily given in Figure 6; Figure 7 provides the parallel-series dependency dependency Tree diagram, only four sub-function modules are exemplarily given in Figure 7)

The series-parallel dependency and the parallel-series dependency are used to represent the premise of ensuring the normal operation of the top-level functional module is to ensure that all sub-function modules in the series relationship among the sub-function modules corresponding to the top-level functional module work normally and are in Any of the sub-function modules in the parallel relationship work normally. To put it simply, the series-parallel relationship represents that the sub-functions under the top-level functional module appear in a series relationship as a whole, but at a certain series node, multiple sub-function modules form a parallel relationship. Obviously, the failure of the sub-functional modules participating in parallel contributes less to the failure of the top-level functional module than the sub-functional modules participating in series, and the dependency tree corresponding to the series-parallel dependency is an "OR" gate; Under the function module, the sub-function modules appear in a parallel relationship as a whole, but at a certain series node, a series relationship is formed by multiple sub-function modules. Obviously, the contribution of the failure of the sub-function modules participating in parallel to the failure of the top-level functional module is the same as that of the sub-function modules participating in the series, and the dependency tree corresponding to the series relationship is an "AND-OR" gate. When a series-parallel dependency or a parallel-series dependency is satisfied between the top-level functional module and the sub-functional module of the application, the specific method for determining the second R&D assurance level of each sub-functional module corresponding to the top-level functional module is as follows:

The terminal takes the first R&D guarantee level of the top-level functional module as the second R&D guarantee level of at least one sub-function module in the sub-function modules that are in a parallel relationship among the sub-function modules corresponding to the top-level functional module, or takes the first R&D guarantee level. The third R&D guarantee level is the second R&D guarantee level of at least two sub-function modules in the sub-function modules in the parallel relationship among the sub-function modules corresponding to the top-level functional module, and the third R&D guarantee level is lower than the first R&D guarantee level grade;

The terminal takes the first R&D guarantee level as the second R&D guarantee level of the sub-function modules in the series relationship among the sub-function modules corresponding to the top-level functional module, or uses the fourth R&D guarantee level as the corresponding top-level functional module. The second R&D guarantee level of at least one sub-function module in the series relationship in the parallel relationship among the sub-function modules, and the fourth R&D guarantee level is the highest among the sub-function modules in the parallel relationship among the sub-function modules corresponding to the top-level functional module. R&D guarantee level.

4. Voting relationship (Figure 8 provides a dependency tree diagram of the voting relationship, and only three sub-function modules are exemplarily given in Figure 8)

The voting relationship is used to represent that the premise of ensuring that the top-level functional module is normal is to ensure that a preset number of sub-functional modules in each sub-functional module corresponding to the top-level functional module are normal. A voting system consisting of a functional module and a voter unit (a certain sub-functional module). When the voter unit is normal, the number of sub-function modules in normal operation is not less than r (1≤r≤n), the failure of the top-level function module will not occur, and the dependency tree corresponding to the voting relationship is the "voting" gate. When the voting relationship is satisfied between the top-level functional module and the sub-functional module of the application, the method for determining the second R&D assurance level of each sub-functional module corresponding to the top-level functional module is as follows:

The terminal uses the first R&D assurance level of the top-level functional module as the second R&D assurance level of the sub-function module at the voter position among the sub-function modules corresponding to the top-level functional module;

The terminal takes the first R&D guarantee level of the top-level functional module as the second R&D guarantee level of at least one sub-function module that is not in the position of the voter among the sub-function modules corresponding to the top-level functional module, or the terminal uses the third R&D guarantee level. The guarantee level is used as the second R&D guarantee level of at least two sub-function modules that are not in the voter position in the sub-function modules corresponding to the top-level functional module, and the third R&D level is lower than the first R&D guarantee level.

In the embodiment of the present application, after the dependency tree between the top-level functional module and its corresponding sub-functional modules in the application is determined, the relevant sub-functional modules can be assigned a level-by-level R&D assurance level from top to bottom. The above specific method of determining the second R&D assurance level of each sub-function module corresponding to the top-level functional module satisfies Principle 1 or Principle 2 in Table 6.

Table 6

In the embodiment of the present application, please refer to FIG. 9 , a method for adjusting the second R&D assurance level in the application evaluation method is provided, and the method further includes:

Step 401, the terminal determines the probability level that the application fails to avoid the dangerous event.

In this step, the sensitivity analysis method is used to determine the "probability level of failing to avoid dangerous events (represented by P in this application)", and to evaluate the sensitivity of the application failure probability to the probability of occurrence of dangerous events, that is, to evaluate the failure of the application program item. The degree to which a change in probability controls or affects the probability of a hazardous event. The main idea is: regard the probability of occurrence of dangerous events g(Q) as a function of the probability of failure of the application program Q _i , and take the partial derivatives of the probability of occurrence of dangerous events against the probability of failure of the application program at the state point O to obtain the state point O. The impact sensitivity value of the application failure probability. The larger the absolute value of the value is, it proves that the probability of occurrence of application failure Qi has a greater impact on the probability of occurrence of dangerous events g(Q), and the probability of occurrence of dangerous events g(Q _{) is more sensitive to the probability of occurrence of application failures Q i .}

Different thresholds can be set for the impact sensitivity, corresponding to four probability levels, namely "very high", "high", "normal" and "very low", corresponding to I, II, III, and IV. Then, the impact sensitivity of application failure to dangerous events is calculated, and experts evaluate which threshold range the impact sensitivity evaluation value falls in, and then obtain the evaluation value of "probability P of application failure to avoid dangerous events".

Step 402, the terminal adjusts the second R&D guarantee level according to the probability level that the application program fails to avoid the dangerous event.

In this step, the basic principle of adjusting the second R&D level is to increase the level of the second R&D guarantee level when the probability level of the application program failing to avoid dangerous events falls within the preset level range.

Now for the series dependency, parallel dependency, series-parallel dependency, parallel-series dependency and voting relationship, how to adjust the second R&D level according to the "probability P that the application fails to avoid dangerous events" will be explained in detail:

1. Serial dependencies

The second R&D level of each sub-function module is the same as the first R&D guarantee level of the top-level functional module, and is not affected by "the probability P that the application fails to avoid dangerous events".

2. Parallel dependencies

1) If the evaluation value of "probability P that the application fails to avoid dangerous events" is "high", the second R&D assurance level of the sub-function module should be the one that is consistent with the first R&D assurance level of the top-level functional module, Or the second R&D guarantee level of the sub-function module is the next level of the first R&D guarantee level of the top-level functional module;

2) If the evaluation value of "probability P that the application fails to avoid dangerous events" is "high", the second R&D assurance level of the sub-function module is the next level of the first R&D assurance level of the top-level functional module;

3) If the evaluation value of "Probability P of the application program failing to avoid dangerous events" is "general" or "very low", the second R&D assurance level of each sub-function module can be appropriately graded according to its most serious risk level , but must meet the allocation principles specified in Table 6.

Third, the series-parallel dependency

1) If the sub-function module is an item in a series relationship, its corresponding second R&D guarantee level is consistent with the first R&D guarantee level of the top-level functional module;

2) For the item whose sub-function module is in a parallel relationship. If the evaluation value of "probability P that the application fails to avoid dangerous events" is "high", the second R&D assurance level of the sub-function module should be consistent with the first R&D assurance level of the top-level function module, or the top-level function The next level of the first R&D assurance level of the module; if the evaluation value of "the probability P of the application program failing to avoid dangerous events" is "higher", the second R&D assurance level of the sub-function module should be the top-level function module's second level. The next level of the first R&D assurance level;

3) If the evaluation value of "probability P that the application fails to avoid dangerous events" is "general" or "very low", the sub-function module can be appropriately graded according to its most serious risk level, but it must meet the requirements in Table 6. prescribed distribution principles.

Fourth, the series-parallel dependency

1) For sub-function modules, it is an item in a parallel relationship. If the evaluation value of "probability P that the application fails to avoid dangerous events" is "high", the second R&D assurance level of the sub-function module should be consistent with the first R&D assurance level of the top-level function module, or the top-level function The next level of the first R&D assurance level of the module; if the evaluation value of "the probability P of the application program failing to avoid dangerous events" is "higher", the second R&D assurance level of the sub-function module should be the top-level function module's second level. The next level of the first R&D assurance level; if the evaluation value of "Probability P of the application program failing to avoid dangerous events" is "normal" or "very low", the second R&D assurance level of the sub-function module can be based on its maximum value. Severe hazard levels are appropriately graded, subject to the assignment principles specified in Table 6;

2) For sub-function modules, it is an item in a series relationship. If the evaluation value of "probability P of the application program failing to avoid dangerous events" is "high", the second R&D assurance level of the sub-function module shall be consistent with the highest R&D assurance level of the sub-function modules in the parallel relationship;

3) If the evaluation value of "probability P that the application fails to avoid dangerous events" is "high", "general" or "very low", the sub-function module can be appropriately graded according to its most serious risk level, but The allocation principles specified in Table 6 must be met.

V. Voting relationship

1) If the sub-function module is in the position of the voter, its corresponding second R&D guarantee level is consistent with the first R&D guarantee level of the top-level functional module;

2) For the sub-function module, it is in the remaining position. If the evaluation value of "probability P that the application fails to avoid dangerous events" is "high", the second R&D assurance level of the sub-function module should be consistent with the first R&D assurance level of the top-level function module, or the top-level function The next level of the first R&D assurance level of the module; if the evaluation value of "the probability P of the application program failing to avoid dangerous events" is "higher", the second R&D assurance level of the sub-function module should be the top-level function module's second level. The next level of the first R&D assurance level; if the evaluation value of "Probability P of the application program failing to avoid dangerous events" is "normal" or "very low", the second R&D assurance level of the sub-function module can be based on its maximum value. Severe hazard classes are appropriately graded, but must meet the assignment principles specified in Table 6.

It should be understood that although the steps in the flowcharts of FIG. 2 to FIG. 9 are shown in sequence according to the arrows, these steps are not necessarily executed in the sequence shown by the arrows. Unless explicitly stated herein, the execution of these steps is not strictly limited to the order, and these steps may be performed in other orders. Moreover, at least a part of the steps in FIG. 2 to FIG. 9 may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed and completed at the same time, but may be executed at different times. These sub-steps or The order of execution of the stages is also not necessarily sequential, but may be performed alternately or alternately with other steps or sub-steps of other steps or at least a portion of a stage.

In this embodiment of the present application, as shown in FIG. 10 , an application evaluation apparatus 500 is provided, which includes: a first determination module 501 , a establishment module 502 and a second determination module 503 , wherein:

The first determination module 501 is configured to determine the first R&D assurance level of each top-level functional module of the application program according to the risk level of the application program, where the risk level includes the severity level of the dangerous consequences caused by the failure of the application program, the At least one of a frequency level of exposure of an application to an external dangerous event and a probability level of the occurrence of the external dangerous event, in the application, each top-level function module corresponds to at least one sub-function module, and each top-level function module corresponds to at least one sub-function module. The module depends on each sub-function module corresponding to the top-level function module;

The establishment module 502 is used to establish, for each of the top-level function modules, a dependency tree corresponding to the top-level function module, where the dependency tree includes the dependencies between the top-level function module and each sub-function module corresponding to the top-level function module relation;

The second determining module 503 is configured to, for each top-level functional module, determine the second R&D assurance level of each sub-function module corresponding to the top-level functional module according to the first R&D assurance level and the dependency tree.

In this embodiment of the present application, the first determining module 501 is specifically configured to obtain a risk level matrix table; determine the risk level of the application program by querying the risk level matrix table; determine the risk level of the application program according to the risk level of the application program This first R&D assurance level for each top-level functional module.

In the embodiment of the present application, the dependency relationship includes a series dependency relationship, and the series dependency relationship is used to represent that the premise of ensuring the normal operation of the top-level functional module is that all sub-function modules corresponding to the top-level functional module work normally, and the second determination module 503 is specifically configured to use the first R&D guarantee level as the second R&D guarantee level of each sub-function module corresponding to the top-level functional module.

In the embodiment of the present application, the dependency relationship includes a parallel dependency relationship, and the parallel dependency relationship is used to represent that the premise of ensuring the normal operation of the top-level functional module is to ensure that any sub-function module corresponding to the top-level functional module is normal, and the second The determining module 503 is specifically configured to take the first R&D guarantee level as the second R&D guarantee level of at least one sub-function module in each of the sub-function modules corresponding to the top-level functional module; or, take the third R&D guarantee level as the top-level function module The second R&D guarantee level of at least two sub-function modules in each of the sub-function modules corresponding to the functional module, and the third R&D guarantee level is lower than the first R&D guarantee level.

In this embodiment of the present application, the dependency includes a series-parallel dependency and a parallel-series dependency, and the series-parallel dependency and the parallel-series dependency are used to characterize the premise of ensuring the normal operation of the top-level functional module is to ensure the top-level functional module All the sub-function modules in the series relationship in the corresponding sub-function modules work normally, and any of the sub-function modules in the parallel relationship work normally, the second determination module 503 is specifically used for this top-level functional module The first R&D guarantee level is taken as the second R&D guarantee level of at least one sub-function module in the sub-function modules in a parallel relationship among the sub-function modules corresponding to the top-level functional module, or the third R&D guarantee level is taken as the top-level function The second R&D guarantee level of at least two sub-function modules in the sub-function modules in parallel relationship among the sub-function modules corresponding to the module, the third R&D guarantee level is lower than the first R&D guarantee level; the first R&D guarantee level The level is taken as the second R&D guarantee level of the sub-function modules in the series relationship among the sub-function modules corresponding to the top-level functional module, or the fourth R&D guarantee level is taken as the sub-function modules corresponding to the top-level functional module in the parallel relationship. The second R&D guarantee level of at least one sub-function module in the series relationship below is the highest R&D guarantee level among the sub-function modules in the parallel relationship among the sub-function modules corresponding to the top-level functional module.

In the embodiment of the present application, the dependency relationship includes a voting relationship, and the voting relationship is used to indicate that the premise of ensuring that the top-level functional module is normal is to ensure that a preset number of sub-functional modules in the sub-functional modules corresponding to the top-level functional module are normal. , the second determining module 503 is specifically configured to take the first R&D assurance level of the top-level functional module as the second R&D assurance level of the sub-function module at the voter position in each of the sub-function modules corresponding to the top-level functional module; The first R&D guarantee level of the top-level functional module is taken as the second R&D guarantee level of at least one sub-function module that is not in the position of the voter in each of the sub-function modules corresponding to the top-level functional module, or the third R&D guarantee level As the second R&D guarantee level of at least two sub-function modules that are not in the voter position among the sub-function modules corresponding to the top-level functional module, the third R&D guarantee level is lower than the first R&D guarantee level.

In this embodiment of the present application, referring to FIG. 11 , another application evaluation device 600 is provided. In addition to the modules included in the application evaluation device 500 , the application evaluation device 600 can optionally The evaluation device 600 also includes an adjustment module 504 .

The adjustment module 504 is configured to determine the probability level of the application program failing to avoid the dangerous event; adjust the second R&D guarantee level according to the probability level that the application program fails to avoid the dangerous event.

In the embodiment of the present application, the adjustment module 504 is specifically configured to increase the level of the second R&D guarantee level when the probability level of the application program failing to avoid the dangerous event falls within the preset level range.

For specific limitations on the application evaluation apparatus, reference may be made to the above limitations on the application evaluation method, which will not be repeated here. Each module in the above-mentioned application evaluation device may be implemented in whole or in part by software, hardware, or a combination thereof. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

In an embodiment of the present application, a computer device is provided, the computer device may be a terminal, and an internal structure diagram thereof may be as shown in FIG. 12 . The computer equipment includes a processor, memory, a network interface, a display screen, and an input device connected by a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium, an internal memory. The nonvolatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the execution of the operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. The computer program when executed by a processor implements an application evaluation method. The display screen of the computer equipment may be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment may be a touch layer covered on the display screen, or a button, a trackball or a touchpad set on the shell of the computer equipment , or an external keyboard, trackpad, or mouse.

Those skilled in the art can understand that the structure shown in FIG. 12 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied. Include more or fewer components than shown in the figures, or combine certain components, or have a different arrangement of components.

In the embodiment of the present application, a computer device is provided, including a memory and a processor, a computer program is stored in the memory, and the processor implements the following steps when executing the computer program:

The first R&D assurance level of each top-level functional module of the application is determined according to the danger level of the application, where the danger level includes the severity level of the dangerous consequences caused by the failure of the application, the frequency of the application being exposed to external dangerous events At least one of the degree level and the probability level of the occurrence of the external dangerous event, in the application program, each of the top-level function modules corresponds to at least one sub-function module, and each of the top-level function modules depends on the top-level function module. each of the sub-function modules;

For each of the top-level functional modules, a dependency tree corresponding to the top-level functional module is established, and the dependency tree includes the dependencies between the top-level functional module and each of the sub-functional modules corresponding to the top-level functional module;

For each top-level functional module, according to the first R&D assurance level and the dependency tree, a second R&D assurance level of each sub-function module corresponding to the top-level functional module is determined.

In the embodiment of the present application, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

The first R&D assurance level of each top-level functional module of the application is determined according to the danger level of the application, where the danger level includes the severity level of the dangerous consequences caused by the failure of the application, the frequency of the application being exposed to external dangerous events At least one of the degree level and the probability level of the occurrence of the external dangerous event, in the application program, each of the top-level function modules corresponds to at least one sub-function module, and each of the top-level function modules depends on the top-level function module. each of the sub-function modules;

For each of the top-level functional modules, a dependency tree corresponding to the top-level functional module is established, and the dependency tree includes the dependencies between the top-level functional module and each of the sub-functional modules corresponding to the top-level functional module;

For each top-level functional module, according to the first R&D assurance level and the dependency tree, a second R&D assurance level of each sub-function module corresponding to the top-level functional module is determined.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage In the medium, when the computer program is executed, it may include the processes of the above-mentioned method embodiments. Wherein, any reference to memory, storage, database or other medium used in the various embodiments provided in this application may include non-volatile and/or volatile memory. Nonvolatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Road (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

The technical features of the above embodiments can be combined arbitrarily. In order to make the description simple, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features It is considered to be the range described in this specification.

The above-mentioned embodiments only represent several embodiments of the present application, and the descriptions thereof are specific and detailed, but should not be construed as a limitation on the scope of the invention patent. It should be pointed out that for those skilled in the art, without departing from the concept of the present application, several modifications and improvements can be made, which all belong to the protection scope of the present application. Therefore, the scope of protection of the patent of the present application shall be subject to the appended claims.

Claims (11)

1. an application evaluation method, is characterized in that, described method comprises: The first R&D assurance level of each top-level functional module of the application program is determined according to the risk level of the application program, where the risk level includes the severity level of the dangerous consequences caused by the failure of the application program, the exposure of the application program to external at least one of the frequency level of the dangerous event and the probability level of the occurrence of the external dangerous event, in the application program, each of the top-level function modules corresponds to at least one sub-function module, and each of the top-level function modules corresponds to at least one sub-function module. The module depends on each of the sub-function modules corresponding to the top-level function module; For each of the top-level functional modules, a dependency tree corresponding to the top-level functional module is established, and the dependency tree includes dependencies between the top-level functional module and each of the sub-functional modules corresponding to the top-level functional module relation; For each of the top-level functional modules, a second R&D assurance level of each of the sub-function modules corresponding to the top-level functional module is determined according to the first R&D assurance level and the dependency tree. 2. The method according to claim 1, wherein the determining the first R&D assurance level of each top-level functional module of the application program according to the risk level of the application program comprises: Get the risk level matrix table; Determine the hazard level of the application by querying the hazard level matrix table; The first R&D assurance level of each top-level functional module of the application is determined according to the risk level of the application. 3 . The method according to claim 1 , wherein the dependency relationship comprises a serial dependency relationship, and the serial dependency relationship is used to represent that the premise of ensuring that the top-level functional module works normally is the corresponding top-level functional module. 4 . All sub-function modules work normally, and the second R&D assurance level of each of the sub-function modules corresponding to the top-level functional module is determined according to the first R&D assurance level and the dependency tree, including: The first R&D guarantee level is used as the second R&D guarantee level of each of the sub-function modules corresponding to the top-level functional modules. 4 . The method according to claim 1 , wherein the dependency relationship comprises a parallel dependency relationship, and the parallel dependency relationship is used to represent the premise of ensuring that the top-level functional module works normally is to ensure that the top-level functional module corresponds to 4. The method according to claim 1 . Any of the sub-function modules is normal, and the second R&D assurance level of each of the sub-function modules corresponding to the top-level functional module is determined according to the first R&D assurance level and the dependency tree, including: Taking the first R&D guarantee level as the second R&D guarantee level of at least one sub-function module in each of the sub-function modules corresponding to the top-level functional module; or, A third R&D guarantee level is used as the second R&D guarantee level of at least two sub-function modules in each of the sub-function modules corresponding to the top-level functional module, and the third R&D guarantee level is lower than the first R&D guarantee level. 5. The method according to claim 1, wherein the dependencies include a series-parallel dependency and a parallel-series dependency, and the series-parallel dependency and the parallel-series dependency are used to characterize the guarantee that the top layer The premise of the normal operation of the functional modules is to ensure that all sub-functional modules in a series relationship among the sub-functional modules corresponding to the top-level functional modules work normally, and any sub-functional modules in a parallel relationship work normally. According to the first R&D assurance level and the dependency relationship tree, determine the second R&D assurance level of each of the sub-function modules corresponding to the top-level functional module, including: Taking the first R&D assurance level of the top-level functional module as the second R&D assurance level of at least one sub-functional module in the sub-functional modules in a parallel relationship among the sub-functional modules corresponding to the top-level functional module, or , take the third R&D guarantee level as the second R&D guarantee level of at least two sub-function modules in the sub-function modules in the parallel relationship among the sub-function modules corresponding to the top-level functional modules, and the third R&D guarantee level is low at said first R&D assurance level; Taking the first R&D guarantee level as the second R&D guarantee level of the sub-function modules in a series relationship among the sub-function modules corresponding to the top-level functional module, or taking the fourth R&D guarantee level as the top-level function The second R&D guarantee level of at least one sub-function module in the series relationship in the parallel relationship among the sub-function modules corresponding to the module, and the fourth R&D guarantee level is the sub-function module in the parallel relationship in the sub-function module corresponding to the top-level functional module. The highest R&D assurance level among sub-function modules. 6 . The method according to claim 1 , wherein the dependency relationship comprises a voting relationship, and the voting relationship is used to represent that the premise of ensuring that the top-level functional module is normal is to ensure that each of the corresponding top-level functional modules is guaranteed. The preset number of sub-function modules in the sub-function modules are normal, and the second R&D guarantee of each of the sub-function modules corresponding to the top-level functional module is determined according to the first R&D guarantee level and the dependency tree. grades, including: Taking the first R&D guarantee level of the top-level functional module as the second R&D guarantee level of the sub-function module at the voter position in each of the sub-function modules corresponding to the top-level functional module; Taking the first R&D guarantee level of the top-level functional module as the second R&D guarantee level of at least one sub-function module that is not in the voter position in each of the sub-function modules corresponding to the top-level functional module, or, Taking the third R&D guarantee level as the second R&D guarantee level of at least two sub-function modules that are not located in the voter position in the sub-function modules corresponding to the top-level functional module, and the third R&D level is lower than the first R&D guarantee level R&D Assurance Level. 7 . The method according to claim 1 , wherein the second research and development of each of the sub-function modules corresponding to the top-level functional module is determined according to the first research and development assurance level and the dependency tree. 8 . After the assurance level, the method further includes: determine the probability level of the application's failure to avoid hazardous events; The second R&D assurance level is adjusted according to the probability level that the application program fails to avoid a hazardous event. 8. The method according to claim 7, wherein the adjusting the second R&D assurance level according to the probability level that the application program fails to avoid dangerous events, comprises: When the probability level of the application program failing to avoid the dangerous event falls within a preset level range, the level of the second R&D guarantee level is increased. 9. An application evaluation device, wherein the device comprises: A first determining module, configured to determine a first R&D assurance level of each top-level functional module of the application program according to the risk level of the application program, where the risk level includes the severity level of the dangerous consequences caused by the failure of the application program , at least one of the frequency level of exposure of the application program to external dangerous events and the probability level of the occurrence of the external dangerous event, in the application program, each of the top-level functional modules corresponds to at least one sub-functional module , each of the top-level functional modules depends on each of the sub-functional modules corresponding to the top-level functional modules; A building module, for establishing a dependency tree corresponding to the top-level functional module for each of the top-level functional modules, the dependency tree including the top-level functional module and each of the sub-functions corresponding to the top-level functional module dependencies between modules; A second determining module, configured to, for each of the top-level functional modules, determine a second R&D guarantee for each of the sub-function modules corresponding to the top-level functional module according to the first R&D guarantee level and the dependency tree grade. 10. A computer device, comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor implements the steps of the method according to any one of claims 1 to 8 when the processor executes the computer program . 11. A computer-readable storage medium on which a computer program is stored, wherein when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images