A computer software technology development debugging system

Abstract

The application discloses a computer software technology development debugging system, belongs to the technical field of computer software technology development debugging, and comprises a task management module, a debugging evaluation module and a feedback and control debugging module. The task management module is used for collecting real-time module progress and error quantity in a debugging process. An evaluation debugging task progress degree unit calculates a debugging completion rate TW according to the input of the module progress and the error quantity, calculates a debugging efficiency TX by using a debugging capability reflecting unit, calculates a debugging progress comprehensive evaluation value TJ by using a comprehensive evaluation debugging progress unit on the basis of introducing automatic debugging, and carries out feedback evaluation on the current debugging progress by using the feedback and control debugging module. According to the evaluation result, the strategy of the current development debugging project is maintained and adjusted. The application realizes accurate debugging progress evaluation, dynamic optimization of debugging efficiency, and the effect of flexible progress adjustment and optimization.

Description

TECHNICAL FIELD

[0001] The application relates to the technical field of computer software technology development debugging, and in particular to a computer software technology development debugging system. BACKGROUND

[0002] In modern computer software development, the debugging phase is usually one of the most time-consuming and complex links, and the purpose of software debugging is to identify and repair errors in the code to ensure the stability and function of the software. However, existing software development debugging methods mostly rely on manual debugging and manual intervention, often lacking systematicness and automation. Therefore, how to efficiently and accurately assess the debugging progress and optimize the debugging efficiency has become a problem to be solved.

[0003] In the prior art, simple time management, error tracking and team collaboration methods are mainly used in the debugging process. Although these methods can complete the basic debugging tasks, they cannot accurately reflect the debugging progress and efficiency in complex projects, and cannot automatically adjust the debugging strategy to optimize the progress, resulting in resource waste and long debugging time.

[0004] For the above and existing related technologies, the inventors believe that the following defects often exist: first, the existing method only evaluates the debugging progress according to the working time and module number in the debugging process, ignoring the working efficiency of the developers, the auxiliary role of the automated tools and the complexity of the debugging tasks, and the efficiency of the debugging usually depends on the experience of the developers, lacking a systematic debugging efficiency calculation method, and not fully considering the variable factors in complex projects. In addition, the existing method cannot optimize and adjust the debugging strategy in real time during the debugging process, which is not flexible and efficient when the project progress changes greatly. SUMMARY

[0005] The technical problem to be solved by the present application is that the prior art has the shortcomings of insufficient debugging progress evaluation, insufficient efficiency optimization and imperfect adjustment mechanism. Therefore, the present application provides a computer software technology development debugging system.

[0006] The technical solution is mainly as follows: a computer software technology development debugging system, comprising a task management module, a debugging evaluation module and a feedback and control debugging module, characterized in that the debugging evaluation module comprises an evaluation debugging task progress degree unit, a debugging capability reflecting unit and a comprehensive debugging progress evaluation unit.

[0007] The debugging is implemented as follows:

[0008] The task management module is used to collect the real-time module progress and error number in the debugging process.

[0009] The unit for evaluating the progress of the debugging task calculates and outputs the debugging completion rate TW based on the input of module progress and the number of errors.

[0010] Based on the debugging completion rate TW, the debugging efficiency TX is calculated and output using the unit reflecting debugging capability;

[0011] Based on the debugging efficiency TX, and using the comprehensive evaluation unit for debugging progress, the comprehensive evaluation value TJ of debugging progress is calculated and output on the basis of introducing automated debugging.

[0012] Based on the comprehensive evaluation value TJ of the debugging progress, and using the feedback and control debugging module, the current debugging progress is evaluated, and the strategy for maintaining and adjusting the current development and debugging project is maintained based on the evaluation results.

[0013] Preferably, the devices used in the task management module include real-time data monitoring tools and progress evaluation dashboards;

[0014] The equipment used in the debugging and evaluation module includes computer hardware and automation tools;

[0015] The equipment used in the feedback and control debugging module includes debugging software tools and a version control system.

[0016] Preferably, the calculation formula for the unit evaluating the progress of the debugging task is as follows:

[0017] ;

[0018] in:

[0019] TW represents the debugging completion rate;

[0020] WM represents the number of debugged modules, reflecting the number of modules that have completed debugging.

[0021] CM stands for Error Module Quantity. CM reflects the total number of modules that exist and have errors during the debugging process.

[0022] ZM represents the total number of modules;

[0023] YM represents the number of modules to be debugged. YM reflects the total number of modules remaining in the total number of modules ZM that are waiting to be debugged, and ZM-YM=WM;

[0024] ZT represents the total test time;

[0025] The unit for evaluating the progress of the debugging task measures the current progress using the number of debugged modules (WM), the number of faulty modules (CM), the total number of modules (ZM), the number of modules to be debugged (YM), and the total testing time (ZT). In this unit... The square root operation is used to balance the influence of errors.

[0026] Preferably, the calculation formula of the reflection debugging capability unit is as follows:

[0027] ;

[0028] ZDF=A×B×C;

[0029] ;

[0030] Wherein:

[0031] TX is the debugging efficiency;

[0032] GT is the average working time, which reflects the average degree of working time of all developers;

[0033] ZDF is the efficient processing factor coefficient;

[0034] The efficient processing factor coefficient ZDF is added to is to measure how much debugging time can be saved and how many errors can be reduced by using efficient tools and methods in the same time, so as to reflect the acceleration effect of the debugging process;

[0035] A is the automation tool coefficient, B is the pre-debugging script efficiency, and C is the code analysis tool usage rate;

[0036] F is the complexity coefficient;

[0037] O is the coupling degree between modules, and O is an index for measuring the dependency relationship between modules in a software system. High coupling degree means strong dependency between modules, and low coupling degree means weak dependency between modules;

[0038] The complexity coefficient F reflects the dependency relationship and functional complexity between the debugged module WM in the software. The higher the complexity, the more difficult the debugging process, so the larger the complexity coefficient F is, and the debugging efficiency TX will be more limited;

[0039] TW×GT indicates the relationship between the current debugging progress and the average time invested. The efficient processing factor coefficient ZDF represents the additional acceleration brought by efficient tools and methods in the debugging process. The complexity coefficient F represents the difficulty faced in the debugging process. Therefore, is used to calculate the amount of work invested and the acceleration effect, and the complexity coefficient F is used to adjust the complexity, so that the debugging efficiency TX can comprehensively reflect the task completion progress, personnel investment and software complexity.

[0040] Preferably, the calculation formulas of the automation tool coefficient A, the pre-debugging script efficiency B, and the code analysis tool usage rate C are as follows:

[0041] A = AW / ZZ;

[0042] B = BW / ZZ;

[0043] C = CW / CZ;

[0044] wherein:

[0045] AW is the number of tasks completed by the automation tool, ZZ is the total number of tasks;

[0046] The automation tool coefficient A measures the proportion of the automation tool in the entire debugging task, and the higher the proportion result value, the more the use of the automation tool can accelerate the debugging process;

[0047] BW is the number of tasks completed by the script;

[0048] The pre-debugging script efficiency B measures the amount of work that can be saved by the pre-debugging script in the entire debugging task, and the higher the proportion result value, the more obvious the role of the pre-debugging script in improving the debugging efficiency;

[0049] CW is the number of executions, CZ is the total number of debugging;

[0050] The code analysis tool usage rate C measures the frequency of use of the code analysis tool in the debugging process, and the higher the frequency, the higher the detection accuracy of the code quality and the debugging accuracy.

[0051] Preferably, the calculation formula of the comprehensive evaluation debugging progress unit is as follows:

[0052]

[0053] wherein:

[0054] TJ is the comprehensive evaluation value of the debugging progress;

[0055] Q is a weight coefficient, Q reflects the weight relationship of the current debugging project in the total project, and its value is {0.1-1.1}, close to 0.1 indicates that the current debugging project has low weight in the total project, and close to 1.1 indicates that the current debugging project has high weight in the total project;

[0056] D is the progress difference value;

[0057] K is a project adjustment coefficient;

[0058] The result of TXxQ reflects the progress of the debugging progress relative to the total target of the project, and the progress difference value D measures the deviation of the project progress. If the progress difference value D is positive, it means that the actual progress is ahead of schedule, and if the progress difference value D is negative, it means that it is lagging behind. The project adjustment coefficient K is used to adjust external factors to more truly reflect the progress evaluation result, therefore,​ The deviation between the calculated debugging progress and the target progress is adjusted by the project adjustment coefficient K to adjust the influence of external factors, and the finally obtained debugging progress comprehensive evaluation value TJ represents the matching degree of the debugging progress and the target.

[0059] Preferably, the calculation formulae of the progress difference D and the project adjustment coefficient K are as follows respectively:

[0060]

[0061]

[0062] Wherein, MJ is the target progress, which is the expected workload calculated according to the target set in the early stage of the project;

[0063] XMT is the project adjustment times, and YCS is the delayed time after adjustment.

[0064] Preferably, the debugging analysis based on the debugging progress comprehensive evaluation value TJ is as follows:

[0065] TJ>0: indicates that the debugging progress exceeds the predetermined target, the progress is good, and the development debugging project is carried out according to the plan;

[0066] TJ=0: indicates that the debugging progress is consistent with the target progress, and the development debugging project is carried out according to the plan;

[0067] TJ<0: indicates that the debugging progress lags behind the target, the project exists lag, and the debugging adjustment strategy of the development debugging project needs to be adjusted.

[0068] Technical effects and advantages of the present application:

[0069] In the present application, the evaluation debugging task progress degree unit can accurately calculate the debugging completion rate TW by comprehensively considering the factors of the already debugged module quantity WM, the error module quantity CM, the total module quantity ZM, the to-be-debugged module quantity YM and the total test time ZT, and the calculation method effectively considers the influence of the error quantity on the debugging progress and balances through the root operation, thereby avoiding the excessive influence of the error on the progress evaluation.

[0070] In the present application, the reflection debugging capability unit comprehensively considers and calculates the debugging completion rate TW, the average working time GT, the efficient processing factor coefficient ZDF and the complexity coefficient F, thereby dynamically calculating the debugging efficiency TX, and the calculation method can adjust the debugging strategy in real time according to the changes of the debugging progress, the personnel working time, the tool usage and the software complexity, and through optimizing the debugging efficiency TX, the system can accelerate the development progress and improve the resource use efficiency.

[0071] ​​In the present application, the comprehensive evaluation debugging progress unit calculates the comprehensive evaluation value TJ of the debugging progress by combining the debugging efficiency TX, the weight coefficient Q and the progress difference D, and the evaluation not only considers the influence of internal and external factors, but also can real-time feedback the difference between the actual progress and the target progress of the project, based on the result of the comprehensive evaluation value TJ of the debugging progress, the system can adjust the task priority, allocate more resources and extend the time to ensure that the development and debugging project is promoted according to the plan. BRIEF DESCRIPTION OF DRAWINGS

[0072] Fig. 1 The method flow chart for developing and debugging the system of the present computer software technology;

[0073] Fig. 2 The structural schematic diagram of the debugging evaluation module in the present application;

[0074] Fig. 3 The debugging evaluation result schematic diagram of the comprehensive evaluation value TJ of the debugging progress in the present application. DETAILED DESCRIPTION

[0075] The present application will be further described in detail in combination with the drawings and preferred embodiments.

[0076] Referring to Figs. 1-3 The present application provides a technical solution: a computer software technology development and debugging system, comprising a task management module, a debugging evaluation module and a feedback and control debugging module, characterized in that: the debugging evaluation module comprises an evaluation debugging task progress degree unit, a debugging ability reflecting unit and a comprehensive evaluation debugging progress unit.

[0077] The debugging is specifically implemented as follows:

[0078] The task management module is used for collecting the real-time module progress and the number of errors in the debugging process;

[0079] The evaluation debugging task progress degree unit calculates the debugging completion rate TW according to the input of the module progress and the number of errors;

[0080] Based on the debugging completion rate TW, the debugging efficiency TX is calculated by using the debugging ability reflecting unit;

[0081] Based on the debugging efficiency TX, the comprehensive evaluation value TJ of the debugging progress is calculated by using the comprehensive evaluation debugging progress unit on the basis of introducing automatic debugging;

[0082] Based on the comprehensive evaluation value TJ of the debugging progress, the feedback and control debugging module is used to perform feedback evaluation on the current debugging progress, and the strategy of the current development and debugging project is maintained and adjusted according to the evaluation result;

[0083] The devices used by the task management module include real-time data monitoring tools and progress evaluation instrument panels.

[0084] The devices used by the debugging evaluation module include computer hardware devices and automated tools.

[0085] The devices used by the feedback and control debugging module include debugging software tools and version control systems.

[0086] The present embodiment forms a cyclic feedback mechanism through the above-mentioned method steps, modules, units and device configurations, continuously optimizes the efficiency and progress of debugging, and through the cooperation of the task management module, the debugging evaluation module and the feedback and control debugging module, the debugging progress can be accurately mastered, and the system performance and development quality can be continuously optimized. Through the calculation of the evaluation debugging task progress degree unit, the reflection debugging capability unit and the comprehensive evaluation debugging progress unit, the progress and efficiency of debugging can be continuously evaluated and adjusted. According to the feedback result of the comprehensive evaluation debugging progress value TJ, the priority and working time of the task can be adjusted to ensure that the debugging progress is not delayed. Through the introduction of automated tools, the debugging efficiency TX can be continuously improved, and the debugging process can be accelerated. In addition, according to the actual progress of the project and the changes of external factors, the debugging strategy can be adjusted in time to ensure that the debugging progress meets the expectations.

[0087] Referring to Figs. 1-3 In the present embodiment, the calculation formula of the evaluation debugging task progress degree unit is as follows:

[0088] ;

[0089] Among them:

[0090] TW is the debugging completion rate;

[0091] WM is the quantity of modules that have been debugged, which reflects the number of modules that have been completed debugging;

[0092] CM is the quantity of error modules, which reflects the total number of modules that exist and have errors in the debugging process;

[0093] ZM is the total number of modules;

[0094] YM is the quantity of modules to be debugged, which reflects the total number of modules remaining and waiting to be debugged in the total number of modules ZM, and ZM-YM=WM;

[0095] ZT is the total test time;

[0096] The evaluation debugging task progress degree unit measures the current progress through the quantity of modules that have been debugged WM, the quantity of error modules CM, the total number of modules ZM, the quantity of modules to be debugged YM and the total test time ZT. In this unit, The square root operation is used to balance the effects of errors.

[0097] In this algorithm unit The calculation section measures the quality of debugged modules by combining the number of currently debugged modules (WM) with the number of faulty modules (CM). The addition of the square root operation indicates that the impact of the number of errors on the progress is not linearly increasing, but rather has a certain mitigating effect. More errors will gradually affect the debugging progress, but this impact will become more gradual as the number of errors increases. Therefore, the square root operation is used to make the impact of the number of errors on the completion rate gradually decrease, avoiding excessive penalties. In other words, more errors do not mean that the debugging progress will decrease exponentially, but rather that the impact will increase gradually.

[0098] In this embodiment, the debugging completion rate TW considers multiple factors that affect the debugging progress, including the number of debugged modules WM, the number of faulty modules CM, the total number of modules ZM, the number of modules to be debugged YM, and the total test time ZT. Through this comprehensive evaluation, the actual progress of the debugging task can be reflected more comprehensively.

[0099] Among them, the square root operation prevents the number of errors during the debugging process from having an excessively large impact on the debugging progress, and avoids inaccurate evaluation of the debugging progress due to the accumulation of a few errors. In this way, the completion rate of the debugging task is more realistic and balanced.

[0100] Furthermore, incorporating the total testing time ZT into the formula helps assess the impact of time on the progress of debugging tasks. In this way, the system can reasonably evaluate the effectiveness of developers completing tasks within a given timeframe.

[0101] Reference Figs. 1-3 As shown in this implementation scheme, the calculation formula for the unit reflecting debugging capability is as follows:

[0102] ;

[0103] ZDF = A × B × C;

[0104] ;

[0105] in:

[0106] TX stands for debugging efficiency;

[0107] GT stands for Average Working Hours, which reflects the average working hours of all developers.

[0108] ZDF is a high-efficiency factor coefficient;

[0109] The efficient processing factor coefficient ZDF is added to The middle is to measure how much debugging time can be saved and how many errors can be reduced in the same time by using efficient tools and methods, so as to reflect the acceleration effect of the debugging process;

[0110] A is the automation tool coefficient, B is the pre-debugging script efficiency, and C is the code analysis tool usage rate;

[0111] F is the complexity coefficient;

[0112] O is the inter-module coupling degree, and O is an index for measuring the dependency between modules in a software system. High coupling degree means strong dependency between modules, and low coupling degree means weak dependency between modules;

[0113] The complexity coefficient F reflects the dependency and functional complexity between the debugged module quantity WM in the software. The higher the complexity, the more difficult the debugging process, so the larger the complexity coefficient F, and the debugging efficiency TX will be more limited;

[0114] TWxGT indicates the relationship between the current debugging progress and the average time invested. The efficient processing factor coefficient ZDF represents the additional acceleration brought by efficient tools and methods in the debugging process. The complexity coefficient F represents the difficulty faced in the debugging process. Therefore, The complexity coefficient F is used to adjust the complexity, so that the debugging efficiency TX can comprehensively reflect the task completion progress, personnel investment, and software complexity;

[0115] The automation tool coefficient A, the pre-debugging script efficiency B, and the code analysis tool usage rate C are calculated as follows:

[0116] A = AW / ZZ;

[0117] B = BW / ZZ;

[0118] C = CW / CZ;

[0119] Wherein:

[0120] AW is the number of tasks completed by the automation tool, and ZZ is the total number of debugging tasks;

[0121] The automation tool coefficient A measures the proportion of the automation tool completed in the entire debugging task, and the higher the proportion result value, the more the use of automation tools can accelerate the debugging process;

[0122] BW is the number of tasks completed by the script;

[0123] The pre-debugging script efficiency B measures the amount of work that can be saved by the pre-debugging script in the entire debugging task, and the higher the proportion result value, the more obvious the improvement of the debugging efficiency by the pre-debugging script;

[0124] CW is the number of executions, and CZ is the total number of debugging;

[0125] The code analysis tool usage rate C measures the frequency of the use of the code analysis tool in the debugging process. The higher the frequency, the higher the accuracy of the detection of the code quality and the debugging.

[0126] In this algorithm unit Reflects the actual work efficiency in unit time, which adjusts the debugging completion rate TW through the average working time GT, improves the reflection of the debugging efficiency TX on the time input, and the increase of the average working time GT will improve the efficiency, so as to better reflect the relationship between the actual developer's debugging working time and the debugging progress, Join Reflects the positive influence of the automatic tool, the script pre-debugging efficient processing technology on the debugging efficiency, plus the efficient processing factor coefficient ZDF, which can effectively improve the debugging efficiency XT, especially the use of efficient tools in the debugging process can greatly reduce manual operation, thereby improving the overall efficiency;

[0127] In this embodiment, the efficient processing factor coefficient ZDF is introduced into the calculation of the debugging capability unit, which can reflect the improvement of the debugging efficiency by the automatic tool and other auxiliary tools. In this way, the debugging efficiency can be optimized with the improvement of the tool and the method, and the overall debugging speed is improved;

[0128] The complexity coefficient F is introduced into the debugging capability unit, which reflects the influence of software complexity on the debugging efficiency XT. The debugging of high complexity software is difficult, and more time and effort are needed. Therefore, the introduction of the complexity coefficient F can help the system to identify and adapt to the debugging needs of different projects;

[0129] In addition, by multiplying the debugging completion rate TW by the average working time GT, plus the efficient processing factor coefficient ZDF, and dividing by the complexity coefficient F, the debugging capability unit comprehensively considers the influence of task completion, time input and auxiliary tools, so as to form a more accurate debugging efficiency measurement method.

[0130] Referring to Figs. 1-3 , in the present embodiment, the calculation formula of the comprehensive evaluation debugging progress unit is as follows:

[0131] ;

[0132] Wherein:

[0133] TJ is the comprehensive evaluation value of the debugging progress;

[0134] Q is a weight coefficient, Q reflects the weight relationship of the project currently being debugged in the total project, and its value is {0.1-1.1}, close to 0.1 indicates that the weight of the project currently being debugged in the total project is low, close to 1.1 indicates that the weight of the project currently being debugged in the total project is high;

[0135] D is a progress difference value;

[0136] K is a project adjustment coefficient;

[0137] The result of TX×Q reflects the progress of the debugging progress relative to the total target of the project, the progress difference value D measures the deviation of the project progress, if the progress difference value D is positive, it means that the actual progress is ahead, if the progress difference value D is negative, it means that it lags behind, the project adjustment coefficient K is used to adjust the external factors, so as to more truly reflect the progress evaluation result, therefore, The deviation between the calculated debugging progress and the target progress is adjusted by the project adjustment coefficient K to adjust the influence of external factors, and the final debugging progress comprehensive evaluation value TJ represents the matching degree of the debugging progress and the target;

[0138] The calculation formulas of the progress difference value D and the project adjustment coefficient K are as follows:

[0139]

[0140]

[0141] Wherein, MJ is the target progress, MJ is the expected workload calculated according to the target set at the beginning of the project;

[0142] XMT is the number of project adjustment times, YCS is the adjusted delay time.

[0143] In this algorithm unit The multiplication of the calculation part reflects the relationship between the debugging progress and the target achievement degree, Q is a weight coefficient, by multiplying the weight coefficient Q, the debugging efficiency is adjusted according to the importance of the project target, if the target is very important, the debugging efficiency has greater influence on the progress evaluation, this calculation part adjusts the progress evaluation, so that the debugging progress of different project targets has different weights, then subtract the progress difference value D, which is used to reflect the deviation of the debugging progress relative to the target progress, and subtracting this difference value can reflect whether the project progress is ahead or lags behind, and by correcting the difference value, it ensures that the progress evaluation can reflect the difference between the actual and the expected, and ensures more accurate progress control;

[0144] ​​In this embodiment, the comprehensive evaluation unit for debugging progress introduces a project adjustment coefficient K, which can dynamically adjust the debugging progress based on the impact of external factors such as team adjustments and task changes. This makes the debugging progress evaluation more flexible and adaptable to uncertainties and changes in the project. The design of the comprehensive evaluation unit for debugging progress can adjust the debugging progress in real time based on the progress difference D. If the progress is lagging, the system can provide feedback and adjust the debugging strategy to ensure that the project progresses on time.

[0145] By introducing a weighting coefficient Q, the comprehensive evaluation unit for commissioning progress can better highlight the core objectives of the project, ensuring that the importance of the project objectives is fully considered when evaluating the commissioning progress, thereby making reasonable schedule adjustments.

[0146] Reference Figs. 1-3 As shown in the figure, the debugging analysis based on the comprehensive evaluation value TJ of the debugging progress in this implementation plan is as follows:

[0147] TJ>0: This indicates that the debugging progress has exceeded the predetermined target, the progress is good, and the development and debugging project is proceeding as planned.

[0148] TJ=0: This indicates that the debugging progress is in line with the target progress, and the development and debugging project is proceeding as planned.

[0149] TJ<0: This indicates that the debugging progress is lagging behind the target, the project is behind schedule, and the debugging strategy for the development and debugging project needs to be adjusted.

[0150] In this algorithm unit, the comprehensive evaluation value TJ of the debugging progress unit can provide the actual performance of the debugging progress, which will affect the calculation of the debugging completion rate TW. If the progress is found to be lagging, the system will adjust the task priority, resource allocation, and time arrangement to speed up the progress and optimize the result of the debugging completion rate TW. Moreover, based on the evaluation of DPE, the system can adjust the work tasks and debugging plans of the developers. This feedback mechanism helps to identify bottlenecks in the project in a timely manner and make corrections, ensuring that the entire debugging process always moves in the optimal direction. In addition, the comprehensive evaluation unit of debugging progress can also change the evaluation of debugging efficiency by affecting the calculation of debugging efficiency TX.

[0151] In this embodiment, when the debugging progress is ahead of schedule, i.e., TJ>0, it means that the team's work efficiency is much higher than expected. At this time, the development team can discover potential problems in advance and solve other unforeseen technical challenges, thereby ensuring quality. Debugging progress ahead of schedule is usually accompanied by more resource savings, which can be used to optimize other software technology development and debugging stages, further improving quality and stability. The early completion of the debugging progress also provides more time for feedback and iterative adjustments, which helps to improve and optimize the product.

[0152] When the debugging progress is consistent with the target, that is, TJ=0, it indicates that the debugging activities are proceeding normally according to the predetermined plan, and the project progress is effectively controlled, which means that the time management and resource allocation of the project are very reasonable, and all tasks are being completed in an orderly manner. This result shows that the initial development and debugging plan is reasonable and executable, and does not deviate from the target, which helps to avoid waste of resources and delay of time, and the progress is completed as expected, and each link of the project can be closely connected, reducing the risk and uncertainty caused by delay;

[0153] When the debugging progress lags behind the target, that is, TJ<0, it is essential to identify the problem immediately and take action. This result prompts the team to review the project progress and analyze the reasons for the lag. The lagging progress means that the project needs more resources or stronger support, and also needs to increase manpower, introduce more automation tools, and adjust the development strategy to make up for the progress gap.

[0154] It should be noted that any modification, equivalent replacement, improvement, etc. within the spirit and principles of the present application should also be within the scope of protection of the present application.

Claims

1. A computer software technology development and debugging system, comprising a task management module, a debugging evaluation module, and a feedback and control debugging module, characterized in that: The debugging evaluation module includes a unit for evaluating the progress of debugging tasks, a unit for reflecting debugging capabilities, and a unit for comprehensively evaluating debugging progress. The specific implementation and debugging are as follows: The task management module is used to collect real-time module progress and error count during the debugging process; The unit for evaluating the progress of the debugging task calculates and outputs the debugging completion rate TW based on the input of module progress and the number of errors. Based on the debugging completion rate TW, the debugging efficiency TX is calculated and output using the unit reflecting debugging capability; Based on the debugging efficiency TX, and using the comprehensive evaluation unit for debugging progress, the comprehensive evaluation value TJ of debugging progress is calculated and output on the basis of introducing automated debugging. Based on the comprehensive evaluation value TJ of the debugging progress, and using the feedback and control debugging module, the current debugging progress is evaluated, and the strategy for maintaining and adjusting the current development and debugging project is maintained based on the evaluation results.

2. The computer software technology development and debugging system according to claim 1, characterized in that: The equipment used by the task management module includes real-time data monitoring tools and progress evaluation dashboards; The equipment used in the debugging and evaluation module includes computer hardware and automation tools; The equipment used in the feedback and control debugging module includes debugging software tools and a version control system.

3. The computer software technology development and debugging system according to claim 2, characterized in that: The calculation formula for the unit that evaluates the progress of the debugging task is as follows: ； in: TW represents the debugging completion rate; WM represents the number of debugged modules, reflecting the number of modules that have completed debugging. CM stands for Error Module Quantity. CM reflects the total number of modules that exist and have errors during the debugging process. ZM represents the total number of modules; YM represents the number of modules to be debugged. YM reflects the total number of modules remaining in the total number of modules ZM that are waiting to be debugged, and ZM-YM=WM; ZT represents the total test time; The unit for evaluating the progress of the debugging task measures the current progress using the number of debugged modules (WM), the number of faulty modules (CM), the total number of modules (ZM), the number of modules to be debugged (YM), and the total testing time (ZT). In this unit... The square root operation is used to balance the effects of errors.

4. The computer software technology development and debugging system according to claim 3, characterized in that: The calculation formula for the unit reflecting debugging capability is as follows: ； ZDF = A × B × C; ； in: TX stands for debugging efficiency; GT stands for Average Working Hours, which reflects the average working hours of all developers. ZDF is a high-efficiency factor coefficient; The efficient processing factor coefficient ZDF is added to The purpose of this measure is to assess how much debugging time can be saved and how many errors can be reduced by using efficient tools and methods within the same time frame, thereby reflecting the speed-up effect of the debugging process. A represents the automation tool coefficient, B represents the pre-debugging script efficiency, and C represents the code analysis tool usage rate. F is the complexity coefficient; O represents the coupling degree between modules, and it is an indicator that measures the dependency relationship between modules in a software system. High coupling degree means strong dependency between modules, while low coupling degree means weak dependency between modules. The complexity coefficient F reflects the dependencies and functional complexity between the number of debugged modules WM in the software. The higher the complexity, the more difficult the debugging process is. Therefore, the larger the complexity coefficient F is, the greater the limitation on the debugging efficiency TX will be. TW×GT indicates the relationship between current debugging progress and average time invested; the efficiency factor coefficient ZDF represents the additional speedup achieved through efficient tools and methods during debugging; and the complexity coefficient F represents the difficulty encountered during debugging. Therefore... The calculation of the workload and acceleration effect is used, while the complexity coefficient F is used to adjust the complexity so that the debugging efficiency TX can comprehensively reflect the task completion progress, personnel input and software complexity.

5. A computer software technology development and debugging system according to claim 4, characterized in that: The calculation formulas for the automation tool coefficient A, pre-debugging script efficiency B, and code analysis tool utilization rate C are as follows: A = AW / ZZ; B = BW / ZZ; C = CW / CZ; in: AW represents the number of tasks completed by the automation tool, and ZZ represents the total number of debugging tasks. The automation tool coefficient A measures the proportion of the entire debugging task completed by automation tools. The higher the proportion, the faster the debugging process can be accelerated by the use of automation tools. BW represents the number of tasks completed by the script. The pre-debug script efficiency (B) measures the amount of work that the pre-debug script can save in the entire debugging task. The higher the percentage result, the more significant the improvement in debugging efficiency of the pre-debug script. CW represents the number of executions, and CZ represents the total number of debugging attempts. The code analysis tool usage rate (C) measures the frequency of use of code analysis tools during the debugging process. The higher the frequency, the higher the accuracy of code quality detection and debugging.

6. The computer software technology development and debugging system according to claim 4, characterized in that: The calculation formula for the comprehensive evaluation and debugging progress unit is as follows: ； in: TJ represents the comprehensive evaluation value of the debugging progress; Q is the weighting coefficient, which reflects the weight of the project currently being debugged in the total project. Its value is {0.1-1.1}. A value close to 0.1 indicates that the project currently being debugged has a low weight in the total project, while a value close to 1.1 indicates that the project currently being debugged has a high weight in the total project. D represents the schedule difference; K is the project adjustment factor; The result of TX×Q reflects the progress of the commissioning schedule relative to the overall project goal. The schedule difference D measures the deviation from the project schedule; a positive schedule difference D indicates that the actual schedule is ahead of schedule, while a negative schedule difference D indicates that it is behind schedule. The project adjustment factor K is used to adjust for external factors in order to more accurately reflect the schedule assessment results. The deviation between the calculated commissioning progress and the target progress is adjusted by the project adjustment coefficient K to account for the influence of external factors. The final comprehensive evaluation value of commissioning progress, TJ, represents the degree of matching between the commissioning progress and the target.

7. A computer software technology development and debugging system according to claim 6, characterized in that: The formulas for calculating the schedule difference D and the project adjustment factor K are as follows: ； ； Where MJ is the target schedule, which is the expected workload calculated based on the goals set at the beginning of the project. XMT represents the number of project adjustments, and YCS represents the delay time after the adjustment.

8. A computer software technology development and debugging system according to claim 6, characterized in that: The debugging analysis based on the comprehensive evaluation value TJ of the debugging progress is as follows: TJ>0: This indicates that the debugging progress has exceeded the predetermined target, the progress is good, and the development and debugging project is proceeding as planned. TJ=0: This indicates that the debugging progress is in line with the target progress, and the development and debugging project is proceeding as planned. TJ<0: This indicates that the debugging progress is lagging behind the target, the project is behind schedule, and the debugging strategy for the development and debugging project needs to be adjusted.

Images