A project problem determination method and device, electronic equipment and storage medium

Abstract

The application provides a project problem determination method and device, electronic equipment and storage medium. The method comprises the following steps: designing a test case based on the requirement of a target project, and determining the total number of problems of the target project; determining the problem omission rate of the target project up to the current release number of the target project based on the total number of problems; determining the problem omission number of the target project based on the problem omission rate of the target project and the total number of discovered problems of the target project; detecting whether the problem omission number of the target project meets a preset problem omission number threshold value; if yes, allowing the target project in the current release number to be used; and if no, continuously determining the problem omission number of the target project in the next release. The problem omission number of the project is dynamically predicted according to the effectiveness of the project problem solution. The predicted problem omission number can be used to evaluate the project quality, thereby improving the maturity of the project.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of software, in particular to a project problem determination method and device, electronic equipment and storage medium. BACKGROUND

[0002] For long-period test projects, the completion of the test project is generally measured by test problems, such as problem discovery, problem repair, and problem inheritance. The number of test problems can reflect the completion of the test project to assist managers in determining test decisions for the test project. Existing project development, especially software development, is becoming more and more complex, and the number of problems discovered in the project is also increasing. The discovery of problems is often delayed until the later stage of the project, so that the problem solving time is short, the problem is not fully verified, and the project quality is difficult to guarantee. The current problem management uses the experience method to predict the problem growth trend with the project progress, without considering the effectiveness of the specific personnel in solving the problem, and the problem growth trend cannot truly reflect the overall completion quality of the project. Therefore, how to predict the number of missing problems in the project has become a technical problem that cannot be underestimated. SUMMARY

[0003] Therefore, the purpose of the present application is to provide a project problem determination method and device, electronic equipment and storage medium, which dynamically predict the number of missing problems in the project according to the effectiveness of problem solving in the project, and use the predicted number of missing problems to evaluate the project quality, thereby improving the maturity of the project.

[0004] The present application provides a project problem determination method, which comprises:

[0005] Obtaining the requirements of a target project, designing test cases based on the requirements of the target project, and determining the total number of problems of the target project;

[0006] Based on the total number of problems, determining the problem omission rate of the target project up to the current release number, and based on the problem omission rate of the target project and the total number of discovered problems of the target project, determining the number of missing problems of the target project;

[0007] Detecting whether the number of missing problems of the target project meets a preset problem omission number threshold, if yes, allowing the target project at the current release number to be used, and if not, continuing to determine the number of missing problems of the target project at the next release.

[0008] In one possible implementation, the test case design based on the requirements of the target project and the determination of the total number of problems of the target project comprise:

[0009] determining a number of test points of the target project based on the requirement of the target project;

[0010] determining a number of test cases of the test points based on the test points;

[0011] determining a total number of problems of the target project based on a product of the number of test cases and the number of test points.

[0012] In a possible implementation, the problem omission rate of the target project up to the current release number is determined by the following steps:

[0013] determining a first value based on the total number of problems of the target project minus a total number of discovered problems of the target project up to the current release number;

[0014] determining the problem omission rate of the target project based on the first value divided by the total number of problems of the target project.

[0015] In a possible implementation, the determining of the problem omission number of the target project based on the problem omission rate of the target project and the total number of discovered problems of the target project comprises:

[0016] determining a second value based on the target value minus the problem omission rate of the target project;

[0017] determining a third value based on the problem omission rate of the target project divided by the second value;

[0018] determining a total number of problems to be solved when the target project reaches zero problems up to the current release number based on the total number of discovered problems of the target project multiplied by the third value;

[0019] determining the problem omission number of the target project based on a sum of the total number of problems to be solved and the total number of discovered problems of the target project.

[0020] In a possible implementation, after the determining of the problem omission rate of the target project up to the current release number based on the total number of problems and the determining of the problem omission number of the target project based on the problem omission rate of the target project and the total number of discovered problems of the target project, the determining method further comprises:

[0021] determining a fourth value based on the total number of discovered problems of the target project divided by the total number of problems of the target project;

[0022] determining a maturity value based on the target value minus the fourth value;

[0023] evaluate the target project based on the maturity value and the current release number.

[0024] In a possible implementation, after determining the problem omission rate of the target project based on the total number of problems and the current release number of the target project, and determining the problem omission number of the target project based on the problem omission rate of the target project and the total number of discovered problems of the target project, the determining method further includes:

[0025] drawing a problem burn-down curve of the target project based on the release numbers of the target project, the problem omission rate of the target project corresponding to each release time, and the problem omission number of the target project corresponding to each release time.

[0026] The embodiments of the present application further provide a project problem determining apparatus, which includes:

[0027] an acquisition module, configured to acquire a requirement of a target project, design a test case based on the requirement of the target project, and determine a total number of problems of the target project;

[0028] a problem prediction module, configured to determine a problem omission rate of the target project based on the total number of problems and the current release number of the target project, and determine a problem omission number of the target project based on the problem omission rate of the target project and a total number of discovered problems of the target project;

[0029] a detection module, configured to detect whether the problem omission number of the target project meets a preset problem omission number threshold, and if yes, allow the target project in the current release number to be used, and if not, continue to determine a problem omission number of the target project in the next release.

[0030] In a possible implementation, when the acquisition module is used for designing a test case based on the requirement of the target project and determining the total number of problems of the target project, the acquisition module is specifically configured to:

[0031] determine a number of test points of the target project based on the requirement of the target project;

[0032] determine a number of test cases of the test points based on the test points;

[0033] determine the total number of problems of the target project based on a product of the number of test cases and the number of test points.

[0034] The embodiment of the present application further provides an electronic device, comprising a processor, a memory and a bus, the memory stores machine readable instructions executable by the processor, when the electronic device is running, the processor and the memory communicate through the bus, and the machine readable instructions are executed by the processor to perform the steps of the project problem determination method.

[0035] The embodiment of the present application further provides a computer readable storage medium, the computer readable storage medium stores a computer program, and the computer program is executed by the processor to perform the steps of the project problem determination method.

[0036] The embodiment of the present application provides a project problem determination method and device, an electronic device and a storage medium, the determination method comprises the following steps: obtaining the requirement of a target project, designing a test case based on the requirement of the target project, and determining the total number of problems of the target project; for the current release number of the target project, determining the problem omission rate of the target project up to the current release number based on the total number of problems, determining the problem omission number of the target project based on the problem omission rate of the target project and the total number of discovered problems of the target project; detecting whether the problem omission number of the target project meets a preset problem omission number threshold, if yes, allowing the target project at the current release number to be used, and if not, continuing to determine the problem omission number of the target project at the next release. The problem omission number of the project is dynamically predicted according to the effectiveness of project problem solving, and the predicted problem omission number can be used to evaluate the quality of the project, thereby improving the maturity of the project.

[0037] In order to make the above objectives, characteristics and advantages of the present application more apparent, clear and easy to understand, the following will describe the preferred embodiments in detail, and the accompanying drawings will be described as follows. BRIEF DESCRIPTION OF DRAWINGS

[0038] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments, and it should be understood that the following drawings only show some embodiments of the present application, and therefore should not be regarded as a limitation to the scope, and for those skilled in the art, other related drawings can also be obtained without creative labor.

[0039] Figure 1 The flow chart of the project problem determination method provided by the embodiment of the present application;

[0040] Figure 2 The problem burn-down curve of the target project provided by the embodiment of the present application;

[0041] Figure 3A structure schematic view of a project problem determination device provided in an embodiment of the present application;

[0042] Figure 4 A structure schematic view of a project problem determination device provided in an embodiment of the present application;

[0043] Figure 5 A structure schematic view of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0044] To make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of description and illustration, and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn according to the actual proportions. The flowcharts show the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowcharts can not be implemented in sequence, and the steps without logical context relationship can be reversed in sequence or implemented simultaneously. In addition, one or more other operations can be added to the flowcharts or one or more operations can be removed from the flowcharts under the guidance of the content of the present application.

[0045] In addition, the described embodiments are only some of the embodiments of the present application, not all the embodiments. The components of the embodiments of the present application described and shown in the drawings herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the claimed present application, but only represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0046] In order to enable those skilled in the art to use the content of the present application, the following implementation is given in combination with a specific application scenario "determining a problem of a project", and those skilled in the art can apply the general principles defined herein to other embodiments and application scenarios without departing from the spirit and scope of the present application.

[0047] The methods, devices, electronic devices or computer readable storage media described in the embodiments of the present application can be applied to any scenario requiring determination of a problem of a project, and the embodiments of the present application do not limit the specific application scenario. Any solution using the project problem determination method, device, electronic device and storage medium provided in the embodiments of the present application is within the scope of protection of the present application.

[0048] Firstly, the application scenarios applicable to the present application are introduced. The present application can be applied to the field of software technology.

[0049] It is found through research that for long-period test projects, the completion of the test project is generally measured by test problems, such as discovered problems, repaired problems, and left problems, and the number of test problems can reflect the completion of the test project to assist managers in determining test decisions of the test project. Existing project development, especially software development, is becoming more and more complex, and the problems discovered by the project are also increasing, and the discovery of the problems has a lag, and the problems are often discovered until the later stage of the project, so that the problem solving time is short, the problem is not fully verified, and the project quality is difficult to guarantee. The current problem management adopts an empirical method to predict the problem growth trend with the project progress, without considering the effectiveness of the specific personnel in solving the problem, and the problem growth trend cannot truly reflect the overall completion quality of the project. Therefore, how to predict the number of problem omissions of the project has become a technical problem that cannot be underestimated.

[0050] Based on this, the embodiment of the present application provides a determination method of project problems, which dynamically predicts the number of problem omissions of the project according to the effectiveness of solving the project problems, and the predicted number of problem omissions can be used to evaluate the project quality, thereby improving the maturity of the project.

[0051] Please refer to Figure 1 , Figure 1 The flowchart of the determination method of project problems provided by the embodiment of the present application. As shown in Figure 1 The determination method provided by the embodiment of the present application comprises the following steps.

[0052] S101: Obtain the requirements of a target project, design test cases based on the requirements of the target project, and determine the total number of problems of the target project.

[0053] In this step, the requirements of the target project are obtained, test cases are designed according to the requirements of the target project, and the total number of problems of the target project is determined.

[0054] Here, the requirements of the target project can be to set a music playing display interface on the display interface of autonomous driving, and to update the display wallpaper on the music playing display interface according to weather changes.

[0055] Among them, the test case is a case to be designed according to the requirements of the target project.

[0056] Among them, the requirements of the target project are itemized, and each requirement generates a test case.

[0057] In a possible implementation, the test case design is performed based on the requirement of the target project, and the total number of problems of the target project is determined, including:

[0058] A: Based on the requirement of the target project, the number of test points of the target project is determined.

[0059] Here, the number of test points of the target project is determined according to the requirement of the target project.

[0060] In this embodiment, one requirement of the target project corresponds to two test points.

[0061] B: Based on the test points, the number of test cases of the test points is determined.

[0062] Here, the number of test cases of the test points is determined according to the test points.

[0063] In this embodiment, one test point corresponds to two test cases.

[0064] C: Based on the product of the number of test cases and the number of test points, the total number of problems of the target project is determined.

[0065] Here, the total number of problems of the target project is determined according to the product of the number of test cases and the number of test points.

[0066] For example, if the requirement of the target project has 10 requirements, one requirement corresponds to two test points, and one test point corresponds to two test cases, the total number of problems is: 10*2*2=40.

[0067] S102: Based on the total number of problems, the problem omission rate of the target project up to the current release number is determined, and based on the problem omission rate of the target project and the total number of discovered problems of the target project, the problem omission number of the target project is determined.

[0068] In this step, based on the total number of problems, the problem omission rate of the target project up to the current release number is determined, and based on the problem omission rate of the target project and the total number of discovered problems of the target project, the problem omission number of the target project is determined.

[0069] In this embodiment, the total number of discovered problems of the target project is the total number of problems of the target project discovered up to the current release number.

[0070] In this embodiment, the problem omission rate is the problem omission rate of the target project up to the current release number.

[0071] The problem omission quantity is the number of problems of the target project that have not been found by the current release number.

[0072] In a possible implementation, the problem omission rate of the target project by the current release number is determined by the following steps:

[0073] a: A first value is determined by subtracting the total number of discovered problems of the target project by the current release number from the total number of problems of the target project.

[0074] Here, the first value is determined by subtracting the total number of discovered problems of the target project by the current release number from the total number of problems of the target project.

[0075] b: The problem omission rate of the target project is determined by dividing the first value by the total number of problems of the target project.

[0076] Here, the total problem omission rate of the target project by the current release number is determined by dividing the first value by the total number of problems of the target project.

[0077] The problem omission rate is determined by the following formula:

[0078] Ri = (Ntotal - Ni) / Ntotal

[0079] Wherein, Ri is the problem omission rate of the target project by the i-th release number, Ntotal is the total number of problems of the target project, and Ni is the total number of discovered problems of the target project by the i-th release number.

[0080] Wherein, the problem omission rate must be less than 1, and the case of greater than or equal to 1 is invalid problem solving and submission failure.

[0081] In a possible implementation, the problem omission quantity of the target project is determined based on the problem omission rate of the target project and the total number of discovered problems of the target project, and includes:

[0082] (1) A second value is determined by subtracting the problem omission rate of the target project from a target value.

[0083] Here, the second value is determined by subtracting the problem omission rate of the target project from the target value.

[0084] Wherein, the target value is 1.

[0085] (2) A third value is determined by dividing the problem omission rate of the target project by the second value.

[0086] Here, the third value is determined by dividing the problem omission rate of the target project by the second value.

[0087] (3) multiplying the total number of discovered problems of the target project by the third value to determine the total number of problems to be solved when the target project reaches zero problems after the current release number.

[0088] Here, the total number of discovered problems of the target project is multiplied by the third value to determine the total number of problems to be solved when the target project reaches zero problems after the current release number.

[0089] Here, the total number of problems to be solved Pi is determined by the following formula:

[0090] Pi = Ni * Ri (1-Ri);

[0091] Wherein, Ri is the problem omission rate of the target project at the i-th release number, Ni is the total number of discovered problems of the target project at the i-th release number, and Pi is the total number of problems to be solved of the target project at the i-th release number.

[0092] (4) the sum of the total number of problems to be solved and the total number of discovered problems of the target project to determine the problem omission number of the target project.

[0093] Here, the sum of the total number of problems to be solved and the total number of discovered problems of the target project determines the problem omission number of the target project.

[0094] Here, the problem omission number Qi is determined by the following formula:

[0095] Qi = Ni + Pi;

[0096] Wherein, Pi is the total number of problems to be solved of the target project at the i-th release number, Ni is the total number of discovered problems of the target project at the i-th release number, and Qi is the problem omission number of the target project at the i-th release number.

[0097] In a possible implementation, after determining the problem omission rate of the target project based on the total number of problems at the current release number of the target project, and determining the problem omission number of the target project based on the problem omission rate of the target project and the total number of discovered problems of the target project, the determination method further comprises:

[0098] I: dividing the total number of discovered problems of the target project by the total number of problems of the target project to determine a fourth value.

[0099] Here, the total number of discovered problems of the target project is divided by the total number of problems of the target project to determine the fourth value.

[0100] II: subtracting the fourth value from the target value to determine the maturity value.

[0101] Here, the maturity value is determined by subtracting the fourth value from the target value.

[0102] Here, the maturity value is used to evaluate the target project, and the higher the maturity value, the better the target project.

[0103] III: Evaluate the target project based on the maturity value and the current release number.

[0104] Here, the target project is evaluated based on the maturity value and the current release number, and the higher the maturity value, the better the target project.

[0105] The maturity value is determined by the following formula:

[0106] Mi = 1 - Ni / Ntotal

[0107] Wherein, Ni is the total number of problems found in the target project at the ith release number, Ntotal is the total number of problems in the target project, and Mi is the maturity value of the target project at the ith release number.

[0108] In one possible implementation, after determining the problem omission rate of the target project up to the current release number based on the total number of problems, and determining the problem omission number of the target project based on the problem omission rate of the target project and the total number of problems found in the target project, the determining method further comprises:

[0109] Based on the multiple release numbers of the target project, the corresponding problem omission rate of the target project at each release time, and the problem omission number of the target project at each release time, draw the problem burn-down curve of the target project.

[0110] Here, the problem burn-down curve of the target project is drawn based on the multiple release numbers of the target project, the corresponding problem omission rate of the target project at each release time, and the problem omission number of the target project at each release time, which realizes the use of problem burn-down curve instead of problem growth trend chart.

[0111] Here, the problem burn-down curve is drawn by the following formula:

[0112] C i = Q i -N i (1+γ i +γ i 2 +…+γ i i-1), i = 1, 2, 3,...

[0113] wherein Qi is the number of missing problems of the target project at the ith release, Ni is the total number of discovered problems of the target project at the ith release, Ri is the missing problem rate of the target project at the ith release, and Ci is the problem curve of the target project at the ith release.

[0114] Further, please refer to Figure 2 , Figure 2 is the problem burn-down curve of the target project provided by the embodiments of the present application. As shown in Figure 2 , the number of problems of the target project is getting smaller and smaller as the release time goes on. The problem burn-down curve of the existing solution is a normal distribution curve.

[0115] S103: detecting whether the number of missing problems of the target project meets the preset threshold of the number of missing problems, if yes, allowing the target project at the current release to be used, if no, continuing to determine the number of missing problems of the target project at the next release.

[0116] In this step, it is detected whether the number of missing problems of the target project meets the preset threshold of the number of missing problems, if yes, allowing the target project at the current release to be used, if no, continuing to determine the number of missing problems of the target project at the next release according to step S102.

[0117] wherein the preset threshold of the number of missing problems is 0.

[0118] In specific embodiments, the requirements of the target project are itemized, each requirement generates a test case, the total number of problems of the target project is determined, the number of test cases is consistent with the total number of problems of the target project when the target project is not developed, with the development process of the target project, the number of missing problems of the target project at each release of the target project is determined, it is detected whether the number of missing problems of the target project meets the preset threshold of the number of missing problems, if yes, allowing the target project at the current release to be used, if no, continuing to determine the number of missing problems of the target project at the next release.

[0119] The embodiment of the present application provides a project problem determination method, which comprises the following steps: obtaining the demand of a target project, designing a test case based on the demand of the target project, and determining the total number of problems of the target project; determining the problem omission rate of the target project up to the current release number of the target project based on the total number of problems, determining the problem omission number of the target project based on the problem omission rate of the target project and the total number of discovered problems of the target project; detecting whether the problem omission number of the target project meets a preset problem omission number threshold value, if yes, allowing the target project in the current release number to be used, and if not, continuing to determine the problem omission number of the target project in the next release. According to the effectiveness of project problem solving, the problem omission number of the project is dynamically predicted, the predicted problem omission number is used to evaluate the project quality, and the maturity of the project is improved.

[0120] Please refer to Figure 3 、 Figure 4 , Figure 3 is a structure diagram of a project problem determination device provided by the embodiment of the present application. Figure 4 is a structure diagram of a project problem determination device provided by the embodiment of the present application. As shown in the figure, Figure 3 The project problem determination device 300 comprises:

[0121] The acquisition module 310 is configured to obtain the demand of a target project, design a test case based on the demand of the target project, and determine the total number of problems of the target project.

[0122] The problem prediction module 320 is configured to determine the problem omission rate of the target project up to the current release number of the target project based on the total number of problems, and determine the problem omission number of the target project based on the problem omission rate of the target project and the total number of discovered problems of the target project.

[0123] The detection module 330 is configured to detect whether the problem omission number of the target project meets a preset problem omission number threshold value, if yes, allowing the target project in the current release number to be used, and if not, continuing to determine the problem omission number of the target project in the next release.

[0124] In a possible implementation, when the acquisition module 310 is used for designing a test case based on the demand of the target project and determining the total number of problems of the target project, the acquisition module is specifically configured to:

[0125] Based on the requirements of the target project, the number of test points for the target project is determined;

[0126] Based on the test points, the number of test cases for each test point is determined;

[0127] The total number of problems in the target project is determined by multiplying the number of test cases by the number of test points.

[0128] In one possible implementation, the issue prediction module 320 determines the issue omission rate of the target project up to the current number of releases through the following steps:

[0129] The first value is determined by subtracting the total number of issues found in the target project up to the current number of releases from the total number of issues in the target project.

[0130] The first value is divided by the total number of problems in the target project to determine the problem omission rate of the target project.

[0131] In one possible implementation, when determining the number of missing problems in the target project based on the problem omission rate and the total number of problems found in the target project, the problem prediction module 320 is specifically used to:

[0132] The second value is determined by subtracting the problem omission rate of the target project from the target value.

[0133] Divide the problem omission rate of the target project by the second value to determine the third value;

[0134] The total number of issues discovered in the target project is multiplied by the third value to determine the total number of unresolved issues when the target project reaches zero issues after the current number of releases.

[0135] The sum of the total number of unresolved issues and the total number of issues discovered in the target project determines the number of issues missed in the target project.

[0136] Furthermore, such as Figure 4 As shown, the project problem determination device 300 further includes a maturity determination module 340, which is used for:

[0137] The fourth value is determined by dividing the total number of problems found in the target project by the total number of problems in the target project.

[0138] The maturity value is determined by subtracting the fourth value from the target value.

[0139] The target project with the current number of releases is evaluated based on the maturity value.

[0140] Furthermore, such as Figure 4 As shown, the problem-solving device 300 further includes a curve plotting module 350, which is used for:

[0141] Based on the number of releases of the target project, the issue omission rate of the target project at the release time corresponding to each release number, and the number of issues omitted in the target project at the release time corresponding to each release number, an issue burn-out curve of the target project is plotted.

[0142] This application provides a device for determining project issues. The device includes: an acquisition module, used to acquire the requirements of a target project, design test cases based on the requirements of the target project, and determine the total number of issues in the target project; an issue prediction module, used to determine the issue omission rate of the target project up to the current release number based on the total number of issues, and determine the number of missing issues in the target project based on the issue omission rate and the total number of issues found in the target project; and a detection module, used to detect whether the number of missing issues in the target project meets a preset threshold. If yes, the target project is allowed to be used at the current release number; otherwise, the number of missing issues in the target project at the next release is determined. By dynamically predicting the number of missing issues in a project based on the effectiveness of problem resolution, the predicted number of missing issues can be used to evaluate project quality, thereby improving project maturity.

[0143] Please see Figure 5 , Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 5 As shown, the electronic device 500 includes a processor 510, a memory 520, and a bus 530.

[0144] The memory 520 stores machine-readable instructions executable by the processor 510. When the electronic device 500 is running, the processor 510 and the memory 520 communicate via the bus 530. When the machine-readable instructions are executed by the processor 510, they can perform the operations described above. Figure 1 The steps of the method for determining the project problem in the method embodiment shown are described in detail in the method embodiment, and will not be repeated here.

[0145] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can perform the above-described actions. Figure 1The steps of the item problem determination method in the method embodiment are specifically implemented as described in the method embodiment, and will not be described here again.

[0146] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the system, device and unit described above can refer to the corresponding processes in the foregoing method embodiments, and will not be described here again.

[0147] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other manners. The described device embodiments are merely schematic, for example, the division of the units is merely a logical function division, and there can be another division manner in actual implementation, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections can be indirect couplings or communication connections through some communication interfaces, devices or units, and can be electrical, mechanical or other forms.

[0148] The units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, that is, can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0149] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit.

[0150] If the functions are realized in the form of software function units and sold or used as independent products, they can be stored in a nonvolatile computer readable storage medium executable by a processor. Based on this understanding, the technical solutions of the present application essentially or the parts of the prior art that make contributions or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and various storage medium that can store program codes.

[0151] Finally, it should be noted that the above-described embodiments are merely specific embodiments of the present application, which are used to illustrate the technical solutions of the present application, but not to limit the same. The protection scope of the present application is not limited thereto. Although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those skilled in the art that any skilled person in the art can still modify or easily think of changes to the technical solutions recorded in the foregoing embodiments, or make equivalent replacements to some of the technical features, within the technical scope disclosed by the present application. The modifications, changes or replacements do not make the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for determining project problems, characterized in that, The determination method includes: Obtain the requirements of the target project, design test cases based on the requirements of the target project, and determine the total number of issues in the target project; For the current number of releases of the target project, the issue omission rate of the target project up to the current number of releases is determined based on the total number of issues. Based on the issue omission rate of the target project and the total number of issues found in the target project, the number of issues omitted in the target project is determined. If the number of missing issues in the target project meets the preset threshold for the number of missing issues, then the target project can be used for the current release. If not, then the number of missing issues in the target project for the next release will be determined. The determination of the number of missed issues in the target project based on the issue omission rate and the total number of issues found in the target project includes: The second value is determined by subtracting the problem omission rate of the target project from the target value; wherein, the target value is 1. Divide the problem omission rate of the target project by the second value to determine the third value; The total number of issues discovered in the target project is multiplied by the third value to determine the total number of unresolved issues when the target project reaches zero issues after the current number of releases. The sum of the total number of unresolved issues and the total number of issues discovered in the target project determines the number of issues missed in the target project.

2. The determination method according to claim 1, characterized in that, The process of designing test cases based on the requirements of the target project and determining the total number of issues in the target project includes: Based on the requirements of the target project, the number of test points for the target project is determined; Based on the test points, the number of test cases for each test point is determined; The total number of problems in the target project is determined by multiplying the number of test cases by the number of test points.

3. The determination method according to claim 1, characterized in that, The following steps were used to determine the issue omission rate of the target project up to the current number of releases: The first value is determined by subtracting the total number of issues found in the target project up to the current number of releases from the total number of issues in the target project. The first value is divided by the total number of problems in the target project to determine the problem omission rate of the target project.

4. The determination method according to claim 1, characterized in that, After determining the issue omission rate of the target project up to the current release count based on the total number of issues, and determining the issue omission count of the target project based on the issue omission rate and the total number of issues discovered in the target project, the determination method further includes: The fourth value is determined by dividing the total number of problems found in the target project by the total number of problems in the target project. The maturity value is determined by subtracting the fourth value from the target value. The target project with the current number of releases is evaluated based on the maturity value.

5. The determination method according to claim 1, characterized in that, After determining the issue omission rate of the target project up to the current release count based on the total number of issues, and determining the issue omission count of the target project based on the issue omission rate and the total number of issues discovered in the target project, the determination method further includes: Based on the number of releases of the target project, the issue omission rate of the target project at the release time corresponding to each release number, and the number of issues omitted in the target project at the release time corresponding to each release number, an issue burn-out curve of the target project is plotted.

6. A device for determining a project problem, characterized in that, The determining device includes: The acquisition module is used to acquire the requirements of the target project, design test cases based on the requirements of the target project, and determine the total number of issues in the target project. The issue prediction module is used to determine the issue omission rate of the target project up to the current number of releases based on the total number of issues, and to determine the number of issues missing in the target project based on the issue omission rate and the total number of issues found in the target project. The detection module is used to detect whether the number of missing issues in the target project meets the preset threshold for the number of missing issues. If yes, the target project can be used for the current release. If no, the number of missing issues in the target project will be determined for the next release. The problem prediction module is used to determine the number of missing problems in the target project based on the problem omission rate and the total number of problems found in the target project. The second value is determined by subtracting the problem omission rate of the target project from the target value; wherein, the target value is 1. Divide the problem omission rate of the target project by the second value to determine the third value; The total number of issues discovered in the target project is multiplied by the third value to determine the total number of unresolved issues when the target project reaches zero issues after the current number of releases. The sum of the total number of unresolved issues and the total number of issues discovered in the target project determines the number of issues missed in the target project.

7. The determining device according to claim 6, characterized in that, When the acquisition module is used to design test cases based on the requirements of the target project and determine the total number of issues in the target project, the acquisition module is specifically used for: Based on the requirements of the target project, the number of test points for the target project is determined; Based on the test points, the number of test cases for each test point is determined; The total number of problems in the target project is determined by multiplying the number of test cases by the number of test points.

8. An electronic device, characterized in that, include: The device includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus. The machine-readable instructions are executed by the processor to perform the steps of the method for determining the project problem as described in any one of claims 1 to 5.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the method for determining the project problem as described in any one of claims 1 to 5.

Images