WO2022134348A1

WO2022134348A1 - Method and apparatus for monitoring software development process, terminal, and storage medium

Info

Publication number: WO2022134348A1
Application number: PCT/CN2021/083312
Authority: WO
Inventors: 刘秋菊; 李向蔚
Original assignee: 平安科技（深圳）有限公司
Priority date: 2020-12-25
Filing date: 2021-03-26
Publication date: 2022-06-30
Also published as: CN112668869A

Abstract

A method and apparatus for monitoring a software development process, a terminal, and a storage medium, applicable to the field of artificial intelligence. The method comprises: obtaining a software quality monitoring model separately corresponding to each stage in a development process of target software (S101); according to the software quality monitoring model corresponding to each stage, performing quality monitoring on each stage to obtain a quality score corresponding to the stage (S102); and determining, according to the quality score corresponding to each stage, whether the stage needs to be adjusted (S103). According to the above method, comprehensive quality monitoring in a software development process is implemented; moreover, quality monitoring is performed on each stage on the basis of the software quality monitoring model corresponding to the stage, so that the obtained quality score is more accurate, and then each stage is adaptively adjusted according to the quality score separately corresponding to the stage; thus, the finally developed software has good quality and high stability.

Description

A method, device, terminal and storage medium for monitoring software development process

This application is filed in the Patent Office of the State Intellectual Property Office of the People's Republic of China on December 25, 2020, the application number is 202011560001.3, and the invention name is "a method, device, terminal and storage medium for monitoring software development process" in China Priority to the patent application, the entire contents of which are incorporated herein by reference.

technical field

The present application belongs to the field of artificial intelligence, and in particular relates to a method, device, terminal and storage medium for monitoring a software development process.

Background technique

The quality control in the software development process largely determines the quality of the software product. Therefore, it is very necessary to monitor the quality of each process stage in the software development process. The inventor realizes that the existing software development process supervision software has simple functions, and cannot accurately and comprehensively implement quality monitoring in all process stages in the software development process, resulting in poor quality of the developed software products.

technical problem

One of the purposes of the embodiments of the present application is to provide a method, device, terminal and storage medium for monitoring the software development process, so as to solve the problem that the existing software development process monitoring software has simple functions and cannot accurately and comprehensively monitor the software development process. Quality control is achieved in all process stages, resulting in technical problems of poor quality of developed software products.

technical solutions

In a first aspect, an embodiment of the present application provides a method for monitoring a software development process, the method comprising:

Obtain the software quality monitoring model corresponding to each stage in the development process of the target software, wherein the software quality monitoring model corresponding to each stage is constructed based on the preset scoring index corresponding to each stage and the preset scoring calculation method. , the development process of the target software includes a requirements analysis stage, a plan management stage, a development stage, a testing stage and a release stage;

According to the software quality monitoring model corresponding to each stage, the quality monitoring of each stage is carried out respectively, and the corresponding quality score of each stage is obtained;

Determine whether each stage needs to be adjusted according to the quality score corresponding to each stage.

In a second aspect, an embodiment of the present application provides a device for monitoring a software development process, including:

The acquiring unit is used to acquire the software quality monitoring model corresponding to each stage in the development process of the target software, wherein the software quality monitoring model corresponding to each stage is based on the preset scoring index and preset corresponding to each stage The scoring calculation method is constructed and obtained, and the development process of the target software includes a requirement analysis stage, a plan management stage, a development stage, a testing stage and a release stage;

The quality monitoring unit is used to monitor the quality of each stage according to the software quality monitoring model corresponding to each stage, and obtain the quality score corresponding to each stage;

The determination unit is used to determine whether each stage needs to be adjusted according to the quality score corresponding to each stage.

In a third aspect, an embodiment of the present application provides a terminal for monitoring a software development process, including a memory, a processor, and a computer program stored in the memory and running on the processor, where the processor implements when executing the computer program:

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium may be non-volatile or volatile, and the computer-readable storage medium stores a computer program, the computer program Implemented when executed by the processor:

beneficial effect

Compared with the prior art, the embodiment of the present application has the following beneficial effects: the embodiment of the present application constructs each stage according to different preset score indicators and preset score calculation methods corresponding to each stage in the development process of the target software. Corresponding software quality monitoring model; based on the corresponding software quality monitoring model for each stage, perform quality monitoring on each stage, and obtain the corresponding quality score for each stage; determine each stage according to the corresponding quality score for each stage. Whether the stage needs to be adjusted. Among them, the development process of the target software includes the requirements analysis stage, the planning management stage, the development stage, the testing stage and the release stage. Based on this method, quality monitoring is carried out for all process stages in the software development process, realizing comprehensive quality monitoring in the software development process; and because the software quality monitoring model corresponding to each stage is based on the corresponding software quality of each stage It is constructed from different preset scoring indicators and preset scoring calculation methods based on these software quality monitoring models. When the quality monitoring of each stage is performed based on these software quality monitoring models, the quality score obtained is more accurate, and then the quality scores corresponding to each stage are obtained. , to make adaptive adjustments to each stage, so that the final developed target software has good quality and strong stability.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only for the present application. In some embodiments, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without any creative effort.

1 is a schematic flowchart of a method for monitoring a software development process provided by an embodiment of the present application;

2 is a schematic flowchart of a method for monitoring a software development process provided by another embodiment of the present application;

3 is a schematic flowchart of a method for monitoring a software development process provided by another embodiment of the present application;

4 is a schematic flowchart of a method for monitoring a software development process provided by still another embodiment of the present application;

5 is a schematic diagram of a device for monitoring a software development process provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of a terminal for monitoring a software development process provided by another embodiment of the present application.

Embodiments of the present invention

In order to make the purpose, technical solutions and advantages of the present application more clearly understood, the present application will be described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, but not to limit the present application.

The quality control in the software development process largely determines the quality of the software product. Therefore, it is very necessary to monitor the quality of each process stage in the software development process. The inventor realizes that the existing software development process monitoring software has simple functions, and cannot accurately and comprehensively implement quality monitoring for all process stages in the software development process. For example, in the prior art, only the development phase and the testing phase of the software development process are usually only monitored for quality; and the evaluation method is relatively simple, such as evaluating whether defects are encountered in the software development process and the number of defects, resulting in the development of The software products are of poor quality and weak stability.

In view of this, the present application provides a method for monitoring a software development process. In the method, according to different preset score indicators and preset score calculation methods corresponding to each stage in the development process of the target software, each The software quality monitoring model corresponding to each stage; based on the software quality monitoring model corresponding to each stage, the quality monitoring of each stage is carried out, and the corresponding quality score of each stage is obtained; according to the corresponding quality score of each stage, each stage is determined. Whether this stage needs to be adjusted. Among them, the development process of the target software includes the requirements analysis stage, the planning management stage, the development stage, the testing stage and the release stage. Based on this method, quality monitoring is carried out for all process stages in the software development process, realizing comprehensive quality monitoring in the software development process; and because the software quality monitoring model corresponding to each stage is based on the corresponding software quality of each stage It is constructed from different preset scoring indicators and preset scoring calculation methods based on these software quality monitoring models. When the quality monitoring of each stage is performed based on these software quality monitoring models, the quality score obtained is more accurate, and then the quality scores corresponding to each stage are obtained. , to make adaptive adjustments to each stage, so that the final developed target software has good quality and strong stability.

Please refer to FIG. 1. FIG. 1 is a schematic flowchart of a method for monitoring a software development process provided by an embodiment of the present application. The execution subject of the method for monitoring a software development process in this embodiment is a terminal, a server, etc., wherein the terminal includes but is not limited to mobile terminals such as smart phones, tablet computers, computers, personal digital assistants (Personal Digital Assistant, PDA), etc. Including desktop computers and other terminals. In this embodiment, the execution subject is taken as an example for description. The method for monitoring the software development process shown in FIG. 1 may include S101 to S104, and the details are as follows:

S101: Obtain a software quality monitoring model corresponding to each stage in the development process of the target software, wherein the software quality monitoring model corresponding to each stage is based on a preset scoring index and a preset scoring calculation method corresponding to each stage After construction, the development process of the target software includes a requirement analysis phase, a plan management phase, a development phase, a testing phase and a release phase.

The development process of target software can be divided into requirements analysis stage, plan management stage, development stage, testing stage and release stage in advance. The target software is the software to be developed, which can be understood as the software we ultimately want that needs to be developed. The software development process, in layman's terms, is the entire process of developing the software based on software design ideas and methods, which can include the analysis of the preset requirements of the target software, the functions that the target software needs to achieve, and the overall corresponding to the target software. The structure and each module, the work assignment of developers, how to connect each module, the algorithm to realize the target software, the coding method corresponding to each module, the tests of different dimensions, the test case, the release time, and the conditions to be satisfied when releasing Wait. According to the included information, the development process of target software is divided into requirements analysis stage, planning management stage, development stage, testing stage and release stage. It is worth noting that the corresponding development processes of different software are different, and the specific content corresponding to the requirements analysis stage, plan management stage, development stage, testing stage, and release stage obtained by the final division may also be different. This is only an exemplary description, and it is not limited.

Optionally, in a possible implementation manner, the development process of the target software may be divided according to the developer's experience, or the developer may upload the documents corresponding to each stage of the development process of the target software to the terminal, and the terminal Identify the documents of each stage, that is, identify the corresponding documents of the requirements analysis stage, the planning management stage, the development stage, the testing stage and the release stage, so as to realize the division of the development process of the target software. This is only an exemplary description, and it is not limited.

The specific development methods of each stage are different, and correspondingly, the software quality monitoring model corresponding to each stage is also different. A software quality monitoring model corresponding to each stage can be constructed and obtained in advance according to the preset scoring index and the preset scoring calculation method corresponding to each stage. The preset scoring indicators and preset scoring calculation methods corresponding to each stage are different.

Exemplarily, a first software quality monitoring model corresponding to the demand analysis stage is constructed according to the first preset scoring index and the first preset scoring calculation method corresponding to the demand analysis stage. The first preset scoring indicators include: requirement confirmation, requirement document, and requirement review. Among them, the requirements confirmation includes: whether more than 50% of the requirements are confirmed before development, and whether more than 50% of the requirements are confirmed before the development reaches half of the entire development cycle. Requirements documents include: whether there is a clear requirements document. Requirements review includes: whether to conduct requirements review and whether to test participation in requirements review. The total quality score corresponding to the demand analysis stage can be adjusted according to the actual situation. In this embodiment, the total quality score corresponding to the demand analysis stage is 20 points, of which, the demand confirmation corresponds to 10 points, and the demand document corresponds to 5 points. The needs assessment corresponds to 5 points. This is only an exemplary description, and it is not limited.

The first preset score calculation method includes: completing more than 50% of the requirements confirmation before development, and the corresponding score is the full score of the score, for example, 5 points; completing 20% to 50% of the requirements confirmation before development, the corresponding score is the Half of the item's score, such as 2.5 points; less than 20% of the requirements confirmation before development, the corresponding score is zero, such as 0 points; more than 50% of the requirements confirmation completed before half of the development cycle, the corresponding score is The full score of this score, such as 5 points; 20% to 50% of the requirements confirmation is completed before half of the entire development cycle, and the corresponding score is half of the score, such as 2.5 points; before half of the entire development cycle is developed Completion of less than 20% of the demand confirmation, the corresponding score is zero, for example, 0 points.

The first preset score calculation method further includes: if there is a clear requirement document, the corresponding score is the full score of the score, such as 5 points; if there is no clear requirement document, the corresponding score is zero, such as 0 point.

The first preset score calculation method further includes: performing a requirement review, the corresponding score is 2 points; not performing the requirement review, the corresponding score is 0 points; the test participates in the requirements review, and the corresponding score is 3 points; the test does not participate in the requirements review , the corresponding score is 3 points.

According to the first preset scoring index and the first preset scoring calculation method listed above, a first software quality monitoring model corresponding to the requirement analysis stage is constructed and obtained. According to the first software quality monitoring model, quality monitoring can be performed on the requirement analysis stage of the target software. This is only an exemplary description, and it is not limited.

Exemplarily, according to the second preset scoring index corresponding to the planning management stage and the second preset scoring calculation method, a second software quality monitoring model corresponding to the planning management stage is constructed. The second preset scoring indicators include: the rationality of the version plan developed by the target software, the rationality of story splitting, and the rationality of story handover. Among them, the rationality of the version plan for target software development includes: whether the version plan is formulated in advance, whether there is a stage handover plan for the story, whether the test participates in the stage handover plan formulation, and whether the stage handover plan is reasonable. The rationality of story splitting includes: whether the story is consistent with the offline split, whether the story is split according to business logic rather than (head) task assignment, and whether the story is split sufficiently finely. The rationality of story handover includes: whether the story is handed over on time, and whether there is sufficient testing time after the handover of complex functions. The total quality score corresponding to the plan management stage can be adjusted according to the actual situation. In this embodiment, the total quality score corresponding to the plan management stage is 20 points, of which the rationality of the version plan for target software development corresponds to 10 points. The rationality of story splitting corresponds to 5 points, and the rationality of story handover corresponds to 5 points. This is only an exemplary description, and it is not limited.

The second preset score calculation method includes: if the version plan is formulated in advance, the corresponding score is 2 points; if the version plan is not formulated in advance, the corresponding score is 0; if there is a stage handover plan with a story, the corresponding score is 3 points, and there is no story. The corresponding score is 0 points if the test is involved in the staged handover plan formulation; if the test participates in the staged handover plan formulation, the corresponding score is 2 points; if the test does not participate in the staged handover plan formulation, the corresponding score is 0; if the staged handover plan is reasonable, the corresponding score is 3 points, the phased handover plan is unreasonable, and the corresponding score is 0 points.

The second preset score calculation method further includes: the story and offline split are consistent, and the corresponding score is 2 points; the story and offline split are inconsistent, and the corresponding score is 0 points; the story is split according to business logic, not according to (Human head) task assignment, the corresponding score is 2 points; stories are divided according to (human head) task assignment, the corresponding score is 0 points; whether the story is split is calculated in proportion to the number, and the corresponding score is a preset constant and ratio (for example, the ratio of stories that do not exceed 3 days is 40%, and the corresponding score is 6*0.4=2.4 points).

The second preset score calculation method also includes: all the stories are handed over on time, and the corresponding score is 2 points; part of the stories is handed over on time, and the corresponding score is the product of the handover ratio and 2 (2 is the score corresponding to when all the stories are handed over on time); If there is sufficient test time after the handover of complex functions, the corresponding score is 3 points; if there is insufficient test time after the handover of complex functions, the corresponding score is 0 points. Among them, when the complex function is handed over, there is still more than or equal to 30% of the entire development cycle as the test time, and it is determined that there is sufficient test time after the complex function is handed over; when the complex function is handed over, there is still less than 30% of the entire development cycle. Testing time, it is determined that there is insufficient testing time after the handover of complex functions.

According to the second preset score index and the second preset score calculation method listed above, a second software quality monitoring model corresponding to the plan management stage is constructed and obtained. According to the second software quality monitoring model, quality monitoring can be performed on the planning management stage of the target software. This is only an exemplary description, and it is not limited.

Exemplarily, a third software quality monitoring model corresponding to the development stage is constructed according to the third preset score index and the third preset score calculation method corresponding to the development stage. The third preset scoring indicators include: development design and development compliance. Among them, the development design includes: whether to conduct a design review and whether to deliver detailed test design documents; development compliance includes: whether there are entrained modifications, and whether the number of defects is artificially controlled. The total quality score corresponding to the development stage can be adjusted according to the actual situation. In this embodiment, the total quality score corresponding to the development stage is 20 points, of which the development design corresponds to 10 points, and the development compliance corresponds to 5 points. This is only an exemplary description, and it is not limited.

The third preset score calculation method includes: design review, the corresponding score is 5 points; no design review, the corresponding score is 0 points; detailed test design documents are delivered, the corresponding score is 5 points; no detailed test design documents are delivered, the corresponding score is 5 points; Test design documents, the corresponding score is 0 points.

The third preset score calculation method further includes: if there is an entrainment modification, the corresponding score is 5 points; if there is no entrainment modification, the corresponding score is 0 points; the number of defects is artificially controlled, and the corresponding score is 5 points; The corresponding score is 0.

According to the third preset score index and the third preset score calculation method listed above, a third software quality monitoring model corresponding to the development stage is constructed and obtained. The quality monitoring of the development stage of the target software can be performed according to the third software quality monitoring model. This is only an exemplary description, and it is not limited.

Exemplarily, according to the fourth preset scoring index corresponding to the testing stage and the fourth preset scoring calculation method, a fourth software quality monitoring model corresponding to the testing stage is constructed. The fourth preset scoring indicator includes: whether there is a test case review link, whether there is a test progress report, whether there is a User Acceptance Test (UAT) entry notification, whether there is a UAT acceptance result, whether the system test is completed on time, whether it is on time Perform software sealing. The total quality score corresponding to the testing stage can be adjusted according to the actual situation. In this embodiment, the total quality score corresponding to the testing stage is 20 points. This is only an exemplary description, and it is not limited.

The fourth preset score calculation method includes: if there is a test case review process, the corresponding score is 2 points; if there is no test case review process, the corresponding score is 0 points; if there is a test progress report, the corresponding score is 2 points; if there is no test progress report, the corresponding score is 2 points. Report, the corresponding score is 0; there is a user acceptance test UAT entry notification, the corresponding score is 1; there is no user acceptance test UAT entry notification, the corresponding score is 0; there is a UAT acceptance result, the corresponding score is 1 point If there is no UAT acceptance result, the corresponding score is 0; if the system test is completed on time, the corresponding score is 7; if the system test cannot be completed on time, the corresponding score is 0; if the software sealing board is completed on time, the corresponding score is 7 ; If the software cannot be sealed on time, the corresponding score is 0.

According to the fourth preset scoring index and the fourth preset scoring calculation method listed above, a fourth software quality monitoring model corresponding to the testing stage is constructed and obtained. The quality monitoring of the test phase of the target software can be performed according to the fourth software quality monitoring model. This is only an exemplary description, and it is not limited.

Exemplarily, a fifth software quality monitoring model corresponding to the release phase is constructed according to the fifth preset score index and the fifth preset score calculation method corresponding to the release phase. The fifth preset scoring index includes: the defect density corresponding to the target software, the defect ratio corresponding to the target software, whether it passes through with smoke, and the number of defects to be repaired. The total quality score corresponding to the release stage can be adjusted according to the actual situation. In this embodiment, the total quality score corresponding to the release stage is 20 points. This is only an exemplary description, and it is not limited.

The fifth preset score calculation method includes: if the defect density is less than or equal to 0.1, the corresponding score is 5 points; if the defect density is greater than 0.1 and less than or equal to 0.2, the corresponding score is 2.5 points; if the defect density is greater than 0.2, the corresponding score is 0 marks. If the proportion of defects is less than or equal to 5%, the corresponding score is 5 points; if the proportion of defects is greater than 5% and less than or equal to 20%, the corresponding score is 2.5 points; if the proportion of defects is greater than 20%, the corresponding score is 0 points. Whether the smoke passes through, the corresponding score is the product of the ratio of the number of normal handovers and the score 5. If the number of defect repairs is 0, the corresponding score is 5 points; if the number of defect repairs is less than or equal to 5, the corresponding score is 2.5 points; if the number of defect repairs is greater than 5, the corresponding score is 0 points.

According to the fifth preset score index and the fifth preset score calculation method listed above, a fifth software quality monitoring model corresponding to the release stage is constructed and obtained. According to the fifth software quality monitoring model, quality monitoring can be performed on the release stage of the target software. This is only an exemplary description, and it is not limited.

The terminal obtains the software quality monitoring model corresponding to each stage. That is, the terminal obtains the first software quality monitoring model corresponding to the demand analysis phase, the second software quality monitoring model corresponding to the planning management phase, the third software quality monitoring model corresponding to the development phase, the fourth software quality monitoring model corresponding to the testing phase, and the release The fifth software quality monitoring model corresponding to the stage.

S102: According to the software quality monitoring model corresponding to each stage, perform quality monitoring on each stage respectively, and obtain a quality score corresponding to each stage.

Based on the different software quality monitoring models corresponding to each stage, the quality of each stage is monitored separately. Exemplarily, collect the data generated when the target software is developed to each stage, and perform the data generated in each stage through the preset scoring index and preset scoring calculation method in the software quality monitoring model corresponding to each stage. Score to get the quality score corresponding to each stage. Among them, the data collected when the target software is developed to each stage can be the data generated by the target software uploaded by the developer when the target software is developed to each stage, or it can be in the actual development process. Data generated at each stage of development. This is only an exemplary description, and it is not limited.

Please refer to FIG. 2, which is a schematic flowchart of a method for monitoring a software development process provided by another embodiment of the present application. Optionally, in a possible implementation manner, as shown in FIG. 2 , the foregoing S102 may include S1021 to S1022, and the details are as follows:

S1021: Collect target data generated when the target software is developed to a first stage, where the first stage is any stage in each of the stages.

S1022: Score the target data based on the preset scoring index and the preset scoring calculation method in the software quality monitoring model corresponding to the first stage, to obtain a quality score corresponding to the first stage.

Each stage refers to the requirements analysis stage, plan management stage, development stage, testing stage and release stage in the development process of the target software. The first stage can be followed by requirements analysis stage, plan management stage, development stage, testing stage and release stage.

The version information corresponding to the target software may be acquired in advance, and based on the version information, the current stage of the target software may be determined. For example, the version information corresponding to the target software can be automatically obtained by calling an application programming interface (Application Programming Interface, API) and/or a preset defect management system, and the version information is used to indicate which stage the target software is currently in. This is only an exemplary description, and it is not limited.

Exemplarily, when the first stage is the requirements analysis stage, target data generated when the target software is developed to the requirements analysis stage is collected. For example, in the requirement analysis stage, the developer of the target software uploads a requirement confirmation progress file, a requirement document, and a requirement review request. The target data collected at this time may include: a requirement confirmation progress document, a requirement document, and a requirement review request.

The target data is scored according to the first preset scoring index and the first preset scoring calculation method in the first software quality monitoring model corresponding to the requirement analysis stage. For example, the item is scored according to the actual completion of the requirement confirmation in the requirement confirmation progress document. If the progress document is confirmed according to the requirement, only the requirement confirmation of more than 50% has been completed before the development, and the corresponding score is 5 points. For another example, it is detected that all requirements in the requirements document are clear requirements, and the corresponding score is 5 points. The target data contains a requirement review request, and the corresponding score for this item is 5 points.

After scoring the target data, add the scores corresponding to each piece of data to obtain the quality score corresponding to the demand analysis stage. For example, adding 5 points corresponding to the requirements confirmation progress document, 5 points corresponding to the requirements document, and 5 points corresponding to the requirements review request, to obtain 15 points, the quality score corresponding to the requirements analysis stage is 15 points. This is only an exemplary description, and it is not limited.

Exemplarily, when the first stage is the planning management stage, the target data generated when the target software is developed to the planning management stage is collected. For example, in the planning management stage of the target software, the developer uploads the version plan rationality document, the story split rationality document, and the story handover rationality document. The target data collected at this time may include: version plan rationality document, story split rationality document It is divided into rationality documents and story handover rationality documents. Among them, the version plan rationality document includes the preparation of the version plan in advance, the test participation in the staged handover plan formulation, and the reasonable staged handover plan. The rationality of story splitting document includes that the splitting of stories is based on (human head) task assignment, the splitting of stories and offline is consistent, and the ratio of stories that do not exceed 3 days is 40%. The rationality document of story handover includes that all stories are handed over on time, and after the handover of complex functions, there is more than or equal to 30% of the whole development cycle time as testing time.

The target data is scored according to the second preset scoring index and the second preset scoring calculation method in the second software quality monitoring model corresponding to the plan management stage. For example, based on the second preset scoring index and the second preset scoring calculation method, a score of 2 points is given to the version plan in advance; if the stage handover plan of the story is not detected, the corresponding score is 0 point; the test participates in the stage handover plan formulation , the corresponding score is 2 points; the story and offline splits are the same, the corresponding score is 2 points; the split of the story is assigned according to the task (head), and the corresponding score is 0 points; the story ratio of no more than 3 days is 40 %, the corresponding score is 6*0.4=2.4 points; all stories are handed over on time, and the corresponding score is 2 points; after the handover of complex functions, there is still more than or equal to 30% of the whole development cycle time as testing time, it is determined that after the handover of complex functions There is sufficient test time, and the corresponding score is 3 points.

After scoring the target data, add the scores corresponding to each data to obtain the quality score corresponding to the planning management stage. For example, the scores of each data in the target data corresponding to the above-mentioned plan management stage are added up to obtain 13.4 points, that is, the quality score corresponding to the plan management stage is 13.4 points. This is only an exemplary description, and it is not limited.

Exemplarily, when the first stage is the development stage, target data generated when the target software is developed to the development stage is collected. For example, the collected target data corresponding to this development stage include: design review information, detailed test design documents, entrained modifications, and non-human control of the number of defects.

The target data is scored according to the third preset scoring index and the third preset scoring calculation method in the third software quality monitoring model corresponding to the development stage. For example, based on the third preset scoring index and the third preset scoring calculation method, the design review information is scored as 5 points; the detailed test design document is detected, the corresponding score is 5 points; the entrainment modification is detected, the corresponding score is 5 points. The score is 5 points; the number of non-artificial control defects is detected, and the corresponding score is 0 points.

After scoring the target data, add the scores corresponding to each data to obtain the quality score corresponding to the development stage. For example, the scores of each data in the target data corresponding to the above-mentioned development stage are added up to obtain 15 points, that is, the quality score corresponding to the development is 15 points. This is only an exemplary description, and it is not limited.

Exemplarily, when the first stage is the testing stage, target data generated when the target software is developed to the testing stage is collected. For example, the collected target data corresponding to this test stage include: test case review link information, test progress report, UAT acceptance result, time to complete the system test, and time to seal the software.

The target data is scored according to the fourth preset scoring index and the fourth preset scoring calculation method in the fourth software quality monitoring model corresponding to the testing stage. For example, based on the fourth preset scoring index and the fourth preset scoring calculation method, the detected test case review link information is scored as 2 points; the test progress report is detected, the corresponding score is 2 points; the user acceptance is not detected When testing the UAT entry notification, the corresponding score is 0; if the UAT acceptance result is detected, the corresponding score is 1; when the system test is completed within the preset completion time, the corresponding score is 7; If the time of the plate is not within the preset sealing time, the corresponding score is 0.

After scoring the target data, add the scores corresponding to each data to obtain the quality score corresponding to the testing stage. For example, the scores of each data in the target data corresponding to the above-mentioned testing stage are added up to obtain 12 points, that is, the quality score corresponding to the development is 12 points. This is only an exemplary description, and it is not limited.

Exemplarily, when the first stage is the release stage, target data generated when the target software is developed to the release stage is collected. For example, the collected target data corresponding to this release stage include: defect density of 0.15, defect ratio corresponding to target software 10%, normal handover ratio of 0.6, and defect repaired number of 3.

The target data is scored according to the fifth preset scoring index and the fifth preset scoring calculation method in the fifth software quality monitoring model corresponding to the release stage. For example, based on the fifth preset scoring index and the fifth preset scoring calculation method, the defect density of 0.15 is scored as 2.5 points; the defect ratio corresponding to the target software is 10%, the corresponding score is 2.5 points; the ratio of the number of normal handovers is 0.6 , the corresponding score is 5*0.6=3 points; the number of defect repairs is 3, and the corresponding score is 2.5 points.

After scoring the target data, add the scores corresponding to each piece of data to obtain the quality score corresponding to the release stage. For example, the scores of each data in the target data corresponding to the above-mentioned release stage are added up to obtain 10.5 points, that is, the quality score corresponding to the development is 10.5 points. This is only an exemplary description, and it is not limited.

S103: Determine whether each stage needs to be adjusted according to the quality score corresponding to each stage.

Different preset thresholds corresponding to each stage can be preset, and the preset thresholds corresponding to each stage are used to judge whether the quality score corresponding to each stage meets the standard, and then judge whether each stage needs to be adjusted.

When a stage needs to be adjusted, the stage is adjusted based on the scores corresponding to each data in the target data of the stage. For example, if the corresponding score of a certain data is low, which affects the overall quality score of this stage, the items corresponding to the data should be adjusted accordingly. This is only an exemplary description, and it is not limited.

Please refer to FIG. 3 , which is a schematic flowchart of a method for monitoring a software development process provided by another embodiment of the present application. Optionally, in a possible implementation manner, as shown in FIG. 3 , the above S103 may include S1031 to S1033. It is worth noting that S1032 is parallel to S1033, and S1031 is determined according to the comparison result between the quality score and the preset threshold. Whether to execute S1032 or S1033 after S1032, instead of executing S1033 after S1032, is as follows:

S1031: Obtain the quality score corresponding to the first stage.

S1032: When it is detected that the quality score is less than a preset threshold, determine that the first stage needs to be adjusted. Or, S1033: When it is detected that the quality score is greater than or equal to the preset threshold, determine that the first stage does not need to be adjusted.

Exemplarily, when the first stage is the demand analysis stage, a first preset threshold value corresponding to the demand analysis stage is obtained, and the first preset threshold value is used to judge whether the quality score corresponding to the demand analysis stage meets the standard, and then judge the demand analysis stage. Whether the stage needs to be adjusted. The first preset threshold may be adjusted according to different target software. For example, the first preset threshold may be 12 points, and the quality score corresponding to the requirement analysis stage is obtained as 15 points.

Comparing the quality score of 15 points corresponding to the demand analysis stage and the first preset threshold of 12 points, obviously, the quality score corresponding to the demand analysis stage is greater than the first preset threshold, and it is determined that the demand analysis stage does not need to be adjusted. This is only an exemplary description, and it is not limited.

Exemplarily, when the first stage is the plan management stage, a second preset threshold value corresponding to the plan management stage is obtained, and the second preset threshold value is used to judge whether the quality score corresponding to the plan management stage meets the standard, and then judge the plan management stage. Whether the stage needs to be adjusted. The second preset threshold may be adjusted according to different target software. For example, the second preset threshold may be 15 points, and the quality score corresponding to the acquisition of the plan management stage is 13.4 points.

Comparing the quality score of 13.4 points corresponding to the plan management stage and the second preset threshold of 15 points, it is obvious that the quality score corresponding to the plan management stage is less than the second preset threshold, and it is determined that the plan management stage needs to be adjusted. This is only an exemplary description, and it is not limited.

Exemplarily, when the first stage is the development stage, a third preset threshold value corresponding to the development stage is obtained, and the third preset threshold value is used to judge whether the quality score corresponding to the development stage meets the standard, and then judge whether the development stage needs to be adjusted. . The third preset threshold may be adjusted according to different target software. For example, the third preset threshold may be 14 points, and the quality score corresponding to the development stage is obtained as 15 points.

Comparing the quality score of 15 points corresponding to the development stage and the third preset threshold of 14 points, it is obvious that the quality score corresponding to the development stage is greater than the third preset threshold, and it is determined that the development stage does not need to be adjusted. This is only an exemplary description, and it is not limited.

Exemplarily, when the first stage is a testing stage, a fourth preset threshold value corresponding to the testing stage is obtained, and the fourth preset threshold value is used to judge whether the quality score corresponding to the testing stage reaches the standard, and then judge whether the testing stage needs to be adjusted. . The fourth preset threshold may be adjusted according to different target software. For example, the fourth preset threshold may be 15 points, and the quality score corresponding to the development stage is obtained as 12 points.

Comparing the quality score of 12 points corresponding to the testing stage and the fourth preset threshold of 15 points, it is obvious that the quality score corresponding to the development stage is less than the fourth preset threshold, and it is determined that the testing stage needs to be adjusted. This is only an exemplary description, and it is not limited.

Exemplarily, when the first stage is the release stage, a fifth preset threshold corresponding to the release stage is obtained, and the fifth preset threshold is used to judge whether the quality score corresponding to the release stage meets the standard, and then to determine whether the release stage needs to be adjusted. . The fifth preset threshold may be adjusted according to different target software. For example, the fifth preset threshold may be 10 points, and the quality score corresponding to the development stage is obtained as 10.5 points.

Comparing the quality score of 10.5 points corresponding to the release stage and the fifth preset threshold of 10 points, obviously, the quality score corresponding to the release stage is greater than the fifth preset threshold, and it is determined that the release stage does not need to be adjusted. This is only an exemplary description, and it is not limited.

Optionally, in a possible implementation manner, when it is determined that the first stage needs to be adjusted, the method may further include: adjusting the first stage based on a preset rule; based on the software quality monitoring model corresponding to the first stage, The quality of the adjusted first stage is monitored, and a quality score corresponding to the adjusted first stage is obtained.

The preset rule may be to detect the main data that affects the quality score corresponding to the first stage, that is, data that has a greater impact on the quality score corresponding to the first stage, and adjust the data accordingly. For example, if the score corresponding to a certain data in the first stage is 0, the data is the main data that affects the quality score corresponding to the first stage. Then analyze the reasons for the score of 0 in detail, and adopt different adjustment methods according to different reasons. If the data is missing, the data will be supplemented; if the data setting is unreasonable, the data will be reset. This is only an exemplary description, and it is not limited.

Following the example in S103, according to the description in S103, it can be known that adjustment is required when the first stage is the planning management stage, and adjustment is required when the first stage is the testing stage.

Exemplarily, taking the first stage as the plan management stage as an example, adjustment is required during the plan management stage, and the quality score corresponding to the plan management stage is 13.4 points. From the description in S1022, it can be seen that the phase handover plan of the story is not detected in the plan management stage, and the score corresponding to this data is 0; the split of the story is assigned according to the (head) task, and the score corresponding to this data is 0. It is mainly these two items that affect the quality score corresponding to the management phase of the program. Therefore, when making adjustments to the program management phase, these two aspects can be taken into account. For example, submit the staged handover plan of the story, and the split of the story is allocated according to the business logic. This is only an exemplary description, and it is not limited.

Based on the second software quality monitoring model corresponding to the plan management stage, quality monitoring is performed again on the adjusted plan management stage, and a quality score corresponding to the adjusted plan management stage is obtained. For example, the target data corresponding to the adjusted plan management stage is obtained, and the adjusted plan management stage is evaluated according to the second preset score index and the second preset score calculation method in the second software quality monitoring model corresponding to the plan management stage. The corresponding target data is scored, and the quality score corresponding to the adjusted plan management stage is obtained. Exemplarily, the target data corresponding to the adjusted plan management stage includes the staged handover plan of the story, and the score corresponding to this data is 3 points; the split of the story is allocated according to business logic, and the score corresponding to this data is 2 points; For the scoring process corresponding to each data, reference may be made to the relevant description in S1032, which will not be repeated here.

It can be seen from the above that the quality score corresponding to the planning management stage before adjustment is 13.4 points, and the quality score corresponding to the planning management stage after adjustment is 18.4 points. Optionally, in a possible implementation manner, the size of the quality score corresponding to the adjusted plan management stage of 18.4 points and the second preset threshold of 15 points can be compared again. Obviously, the quality score corresponding to the plan management stage is greater than the second preset threshold. 2. Preset thresholds to determine that the adjusted plan management stage meets the standard and does not need to be adjusted again. If the result obtained from the re-comparison is that adjustment is required in the planning management stage, the adjusted planning management stage is re-adjusted again until the planning management stage reaches the standard and no adjustment is required. This is only an exemplary description, and it is not limited.

Exemplarily, taking the first stage as a testing stage as an example, the testing stage needs to be adjusted, and the quality score corresponding to the testing stage is 12 points. According to the description in S1022, it can be known that the time for software sealing the board in this test stage is not within the preset board sealing time, and the corresponding score is 0 points. Mainly this affects the quality score corresponding to this testing phase. Therefore, this is the place to start when making adjustments to the testing phase. For example, the time for software sealing is advanced so that the time for software sealing is within the preset sealing time.

Based on the fourth software quality monitoring model corresponding to the testing phase, the quality monitoring of the adjusted testing phase is performed again to obtain a quality score corresponding to the adjusted testing phase. For example, the target data corresponding to the adjusted testing stage is obtained, and according to the fourth preset scoring index and the fourth preset scoring calculation method in the fourth software quality monitoring model corresponding to the testing stage, the target corresponding to the adjusted testing stage is The data is scored to obtain a quality score corresponding to the adjusted test phase. Exemplarily, in the target data corresponding to the adjusted test phase, the time for software sealing is advanced, so that the time for software sealing is within the preset sealing time, that is, the time for software sealing is within the preset sealing time. In time, the score corresponding to this data is 7 points. For the scoring process corresponding to the remaining data, reference may be made to the relevant description in S1022, which will not be repeated here.

It can be seen from the above that the quality score corresponding to the unadjusted test stage is 12 points, and the quality score corresponding to the adjusted test stage is 19 points. Optionally, in a possible implementation manner, the quality score corresponding to the adjusted test stage of 19 points and the fourth preset threshold of 15 points can be compared again. Obviously, the quality score corresponding to the adjusted test stage is greater than The fourth preset threshold determines that the adjusted test stage meets the standard and does not need to be adjusted again. If the result obtained from the re-comparison still needs to be adjusted in the test phase, the adjusted test phase is re-adjusted again until the test phase reaches the standard and no adjustment is required. This is only an exemplary description, and it is not limited.

Optionally, in a possible implementation manner, the method for monitoring the software development process may further include: determining the final quality score corresponding to each stage, and when the first stage needs to be adjusted, the final quality score is the adjusted first quality score. The quality score corresponding to the stage, when the first stage does not need to be adjusted, the final quality score is the quality score corresponding to the unadjusted first stage; based on the final quality score corresponding to each stage, the overall quality score corresponding to the target software is calculated; when When it is detected that the overall quality score is greater than or equal to the preset quality threshold, a qualified report corresponding to the target software is generated. When it is detected that the overall quality score is less than the preset quality threshold, an email message is generated, and the email message is used to remind the developer that the development process of the target software is unqualified.

Exemplarily, since each stage may or may not require adjustment, the final quality score corresponding to each stage is different. It is still expressed in terms of the first stage, which is any stage in the requirements analysis stage, plan management stage, development stage, testing stage and release stage. When the first stage needs to be adjusted, the final quality score corresponding to the first stage is the quality score corresponding to the adjusted first stage. Since it may be adjusted multiple times, the adjusted here refers to the last adjustment. When it is understood that the quality score corresponding to the first stage reaches the standard, the quality score corresponding to the first stage at this time is the final quality score corresponding to the first stage.

When the first stage does not need to be adjusted, the final quality score corresponding to the first stage is the quality score corresponding to the unadjusted first stage, that is, the software quality monitoring model corresponding to the first stage is used for the first time. When performing quality monitoring, the quality score corresponding to the first stage is obtained.

For example, when the first stage is the requirements analysis stage, the requirements analysis stage does not need to be adjusted, and the final quality score corresponding to the requirements analysis stage is the initial quality score of 15 points. When the first stage is the plan management stage, and the plan management stage needs to be adjusted, the final quality score corresponding to the plan management stage is 18.4 points corresponding to the adjusted plan management stage. When the first stage is the development stage, the development stage does not need to be adjusted, and the final quality score corresponding to the development stage is the initial quality score of 15 points. When the first stage is a testing stage, and the testing stage needs to be adjusted, the final quality score corresponding to the testing stage is 19 points corresponding to the adjusted testing stage. When the first stage is the release stage, the release stage does not need to be adjusted, and the final quality score corresponding to the release stage is the initial quality score of 10.5 points. This is only an exemplary description, and it is not limited.

The final quality scores corresponding to each stage are added together, and the obtained score is the overall quality score corresponding to the target software. For example, the final quality score corresponding to the requirements analysis stage is 15 points, the final quality score corresponding to the planning management stage is 18.4 points, the final quality score corresponding to the development stage is 15 points, the final quality score corresponding to the testing stage is 19 points, and the final quality score corresponding to the release stage is 19 points. The quality score of 10.5 points is added up, and the overall quality score corresponding to the target software is 77.9 points. This is only an exemplary description, and it is not limited.

The preset quality threshold is used to judge whether the overall quality score corresponding to the target software meets the standard, that is, to judge whether the development process of the target software is qualified. The preset quality threshold can be adjusted according to different target software, for example, the preset quality threshold can be 75 points, 85 points, 90 points, etc., which are only exemplary descriptions, and are not limited.

Exemplarily, the overall quality score corresponding to the target software is compared with a preset quality threshold. When the preset quality threshold is 75 points, obviously, the overall quality score corresponding to the target software of 77.9 points is greater than the preset quality threshold of 75 points, and a qualified report corresponding to the target software is generated at this time. The qualification report is used to indicate that the development process of the target software is qualified, that is, the target software is developed according to each stage in the development process, and the final target software is qualified. The qualification report may include target data corresponding to each stage of the target software, a quality score corresponding to each stage, a quality score corresponding to each data individually, an overall quality score corresponding to the target software, and the like. This is only an exemplary description, and it is not limited.

When the preset quality threshold is 85 points, obviously, the overall quality score corresponding to the target software of 77.9 points is lower than the preset quality threshold of 85 points. At this time, an email message is generated, and the email message is used to remind the developer that the development process of the target software is unqualified. . That is, the target software is developed according to each stage in the development process, and the final target software is unqualified. When the developer receives the email message, he can review the entire development process of the target software, make individual adjustments to each stage and/or adjust the preset thresholds corresponding to each stage, etc. This is only an exemplary illustration. , which is not limited.

After each stage is individually adjusted and/or the preset threshold corresponding to each stage is adjusted, the quality monitoring of the development process of a new round of target software can be performed again through the method for monitoring the software development process provided in this application. , the specific monitoring process will not be repeated here.

Optionally, in a possible implementation manner, after quality monitoring of each stage, an email corresponding to each stage can be generated, and the email can be sent to the developer, which can timely remind the developer of the current target software. The development progress and the development quality of each stage are convenient for developers to make adjustments in time, thereby ensuring that the final developed target software has good quality and strong stability, and realizes early warning in the software development process.

Optionally, in a possible implementation manner, before the target software is developed, the developer is reminded by email to upload the requirements confirmation progress files, requirements documents, requirements review requests and other information that need to be used in the requirements analysis stage. In the development stage corresponding to the target software, the developer is reminded by email to send the test progress report, UAT acceptance result, etc. After the terminal detects these data, it can score the data through the fourth software quality monitoring model.

Optionally, in a possible implementation manner, the quality score corresponding to each stage before adjustment, the overall quality score corresponding to the target software, the individual score corresponding to each data, and the quality corresponding to each stage after adjustment can be used. Score, etc., generate comparison charts, trend charts, etc. Exemplarily, upload the information to a preset easy-to-draw chart system, and the easy-to-draw chart system can generate an overall comparison chart, an overall radar chart, and an overall trend chart corresponding to the target software according to the information, as well as each stage generated according to each stage. Radar chart, trend chart and comparison chart corresponding to each stage. This is only an exemplary description, and it is not limited.

In the embodiment of the present application, according to different preset scoring indicators and preset scoring calculation methods corresponding to each stage in the development process of the target software, a software quality monitoring model corresponding to each stage is constructed; The software quality monitoring model monitors the quality of each stage, and obtains the quality score corresponding to each stage; according to the quality score corresponding to each stage, it is determined whether each stage needs to be adjusted. Among them, the development process of the target software includes the requirements analysis stage, the planning management stage, the development stage, the testing stage and the release stage. Based on this method, all process stages in the software development process are monitored for quality, and comprehensive quality monitoring in the software development process is realized; and because the software quality monitoring model corresponding to each stage is based on the corresponding software quality of each stage It is constructed from different preset scoring indicators and preset scoring calculation methods based on these software quality monitoring models. When the quality monitoring of each stage is performed based on these software quality monitoring models, the quality score obtained is more accurate, and then the quality scores corresponding to each stage are obtained. , to make adaptive adjustments to each stage, so that the final developed target software has good quality and strong stability. Moreover, this method automatically monitors the quality of each stage through the software quality monitoring model corresponding to each stage, so that developers no longer have to stare at all times, so that developers can do more other work, freeing the hands of developers. , the cost of developing software is saved on the side, and the efficiency and quality of software development are improved.

Please refer to FIG. 4, which is a schematic flowchart of a method for monitoring a software development process provided by still another embodiment of the present application. The method may include S201˜S204. Wherein, for steps S201 to S203 shown in FIG. 4 , reference may be made to the relevant descriptions of S101 to S103 in the embodiment corresponding to FIG. 1 , which are not repeated here for brevity. Step S204 will be specifically described below.

S204: Upload the software quality monitoring model corresponding to each stage to the blockchain.

Upload the software quality monitoring model corresponding to each stage to the blockchain, namely the first software quality monitoring model corresponding to the requirement analysis stage, the second software quality monitoring model corresponding to the planning management stage, and the third software quality monitoring model corresponding to the development stage. The software quality monitoring model, the fourth software quality monitoring model corresponding to the testing phase, and the fifth software quality monitoring model corresponding to the release phase are uploaded to the blockchain respectively.

In this embodiment, the software quality monitoring model corresponding to each stage is uploaded to the blockchain to ensure its security and fairness and transparency to users. In addition, the software quality monitoring model corresponding to each stage is uploaded to the blockchain. With the feature that the files on the blockchain cannot be tampered with at will, the software quality monitoring model corresponding to each stage can be prevented from being maliciously tampered with, which is convenient for subsequent users. The software quality monitoring model corresponding to each stage can be directly and accurately obtained, and it is also convenient for subsequent users to use the software quality monitoring model corresponding to each stage to monitor the quality of the development process of the target software.

The blockchain referred to in this example is a new application mode of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. Blockchain, essentially a decentralized database, is a series of data blocks associated with cryptographic methods. Each data block contains a batch of network transaction information to verify its Validity of information (anti-counterfeiting) and generation of the next block. The blockchain can include the underlying platform of the blockchain, the platform product service layer, and the application service layer.

Please refer to FIG. 5 , which is a schematic diagram of an apparatus for monitoring a software development process provided by an embodiment of the present application. Each unit included in the apparatus is used to execute each step in the embodiment corresponding to FIG. 1 to FIG. 4 . For details, please refer to the relevant descriptions in the respective corresponding embodiments of FIG. 1 to FIG. 4 . For convenience of explanation, only the parts related to this embodiment are shown. See Figure 5, including:

The obtaining unit 310 is configured to obtain the software quality monitoring model corresponding to each stage in the development process of the target software, wherein the software quality monitoring model corresponding to each stage is based on the preset scoring index and the preset score corresponding to each stage. Suppose the scoring calculation method is constructed and obtained, and the development process of the target software includes a requirements analysis stage, a plan management stage, a development stage, a testing stage and a release stage;

The quality monitoring unit 320 is configured to monitor the quality of each stage respectively according to the software quality monitoring model corresponding to each stage, and obtain the quality score corresponding to each stage;

The determining unit 330 is configured to determine whether each stage needs to be adjusted according to the quality score corresponding to each stage.

Optionally, the quality monitoring unit 320 is specifically configured to:

collecting target data generated when the target software is developed to the first stage, where the first stage is any one of the each stage;

Based on the preset scoring index and the preset scoring calculation method in the software quality monitoring model corresponding to the first stage, the target data is scored to obtain the quality score corresponding to the first stage.

Optionally, the determining unit 330 is specifically configured to:

obtaining the quality score corresponding to the first stage;

When it is detected that the quality score is less than a preset threshold, it is determined that the first stage needs to be adjusted; or,

When it is detected that the quality score is greater than or equal to the preset threshold, it is determined that the first stage does not need to be adjusted.

Optionally, the device further includes:

an adjustment unit, configured to adjust the first stage based on a preset rule;

The scoring unit is configured to perform quality monitoring on the adjusted first stage based on the software quality monitoring model corresponding to the first stage, and obtain a quality score corresponding to the adjusted first stage.

Optionally, the device further includes:

The scoring determination unit is used to determine the final quality score corresponding to each stage. When the first stage needs to be adjusted, the final quality score is the quality score corresponding to the adjusted first stage. When adjustment is required, the final quality score is the quality score corresponding to the unadjusted first stage;

a computing unit, configured to calculate the overall quality score corresponding to the target software based on the final quality score corresponding to each stage;

A first generating unit, configured to generate a qualified report corresponding to the target software when it is detected that the overall quality score is greater than or equal to a preset quality threshold

Optionally, the device further includes:

The second generating unit is configured to generate email information when it is detected that the overall quality score is less than the preset quality threshold, where the email information is used to remind the developer that the development process of the target software is unqualified.

Optionally, the device further includes:

The uploading unit is used to upload the software quality monitoring model corresponding to each stage to the blockchain.

Please refer to FIG. 6, which is a schematic diagram of a terminal for monitoring a software development process provided by another embodiment of the present application. As shown in FIG. 6 , the terminal 4 for monitoring the software development process in this embodiment includes: a processor 40 , a memory 41 , and computer instructions 42 stored in the memory 41 and executable on the processor 40 . When the processor 40 executes the computer instructions 42 , the steps in each of the foregoing method embodiments for monitoring a software development process are implemented, for example, S101 to S103 shown in FIG. 1 . Alternatively, when the processor 40 executes the computer instructions 42, the functions of the units in the foregoing embodiments are implemented, for example, the functions of the units 310 to 330 shown in FIG. 5 .

Illustratively, the computer instructions 42 may be divided into one or more units, and the one or more units are stored in the memory 41 and executed by the processor 40 to complete the present application. The one or more units may be a series of computer instruction segments capable of accomplishing specific functions, and the instruction segments are used to describe the execution process of the computer instructions 42 in the terminal 4 that monitors the software development process. For example, the computer instructions 42 can be divided into an acquisition unit, a quality monitoring unit and a determination unit, and the specific functions of each unit are as described above.

The terminal for monitoring the software development process may include, but is not limited to, the processor 40 and the memory 41 . Those skilled in the art can understand that FIG. 6 is only an example of the terminal 4 monitoring the software development process, and does not constitute a limitation on the terminal monitoring the software development process, and may include more or less components than those shown in the figure, or a combination of certain Some components, or different components, for example, the terminal for monitoring the software development process may also include an input and output terminal, a network access terminal, a bus, and the like.

The so-called processor 40 may be a central processing unit (Central Processing Unit, CPU), or other general-purpose processors, digital signal processors (Digital Signal Processors, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), Off-the-shelf programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 41 may be an internal storage unit of the terminal that monitors the software development process, such as a hard disk or memory of the terminal that monitors the software development process. The memory 41 can also be an external storage terminal of the terminal for monitoring the software development process, such as a plug-in hard disk equipped on the terminal for monitoring the software development process, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, flash memory card (Flash Card), etc. Further, the memory 41 may also include both an internal storage unit of the terminal for monitoring the software development process and an external storage terminal. The memory 41 is used to store the computer instructions and other programs and data required by the terminal. The memory 41 can also be used to temporarily store data that has been output or will be output.

Exemplarily, an embodiment of the present application provides a terminal for monitoring a software development process, including a memory, a processor, and a computer program stored in the memory and running on the processor, and the processor implements each of the above when executing the computer program. Steps in a method embodiment of monitoring a software development process. For example, when the processor executes the computer program, it achieves: acquiring a software quality monitoring model corresponding to each stage in the development process of the target software, wherein the software quality monitoring model corresponding to each stage is based on a preset score corresponding to each stage The index and the preset score calculation method are constructed, and the development process of the target software includes the requirements analysis stage, the planning management stage, the development stage, the testing stage and the release stage; according to the software quality monitoring model corresponding to each stage, each Quality monitoring is carried out in each stage, and the corresponding quality score of each stage is obtained; according to the corresponding quality score of each stage, it is determined whether each stage needs to be adjusted.

Exemplarily, the embodiments of the present application further provide a computer-readable storage medium, the computer-readable storage medium may be non-volatile or volatile, and the computer-readable storage medium stores a computer program, the computer program When executed by the processor, the steps in each of the foregoing method embodiments for monitoring a software development process are implemented. For example, when the computer program is executed by the processor, it realizes: acquiring the software quality monitoring model corresponding to each stage in the development process of the target software, wherein the software quality monitoring model corresponding to each stage is based on the preset corresponding to each stage The scoring index and the preset scoring calculation method are constructed. The development process of the target software includes the requirements analysis stage, the plan management stage, the development stage, the test stage and the release stage; Quality monitoring is carried out in each stage, and the corresponding quality score of each stage is obtained; according to the corresponding quality score of each stage, it is determined whether each stage needs to be adjusted.

The above-mentioned embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the above-mentioned embodiments, those of ordinary skill in the art should understand that: it can still be used for the above-mentioned implementations. The technical solutions recorded in the examples are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit scope of the technical solutions in the embodiments of the application, and should be included in the present application. within the scope of protection of the application.

Claims

A method of monitoring a software development process, comprising:

Obtain the software quality monitoring model corresponding to each stage in the development process of the target software, wherein the software quality monitoring model corresponding to each stage is constructed based on the preset scoring index corresponding to each stage and the preset scoring calculation method. , the development process of the target software includes a requirements analysis stage, a plan management stage, a development stage, a testing stage and a release stage;

According to the software quality monitoring model corresponding to each stage, the quality monitoring of each stage is carried out respectively, and the corresponding quality score of each stage is obtained;

Determine whether each stage needs to be adjusted according to the quality score corresponding to each stage.
The method according to claim 1, wherein, according to the software quality monitoring model corresponding to each stage, the quality monitoring of each stage is carried out respectively, and the quality score corresponding to each stage is obtained, comprising:

collecting target data generated when the target software is developed to the first stage, where the first stage is any one of the each stage;

Based on the preset scoring index and the preset scoring calculation method in the software quality monitoring model corresponding to the first stage, the target data is scored to obtain the quality score corresponding to the first stage.
The method according to claim 2, wherein determining whether each stage needs to be adjusted according to the quality score corresponding to each stage, comprising:

obtaining the quality score corresponding to the first stage;

When it is detected that the quality score is less than a preset threshold, it is determined that the first stage needs to be adjusted; or,

When it is detected that the quality score is greater than or equal to the preset threshold, it is determined that the first stage does not need to be adjusted.
The method according to claim 3, wherein, after it is determined that the first stage needs to be adjusted when it is detected that the quality score is less than a preset threshold, the method further comprises:

adjusting the first stage based on preset rules;

Based on the software quality monitoring model corresponding to the first stage, the quality of the adjusted first stage is monitored to obtain a quality score corresponding to the adjusted first stage.
The method of any one of claims 2 to 4, wherein the method further comprises:

Determine the final quality score corresponding to each stage, when the first stage needs to be adjusted, the final quality score is the quality score corresponding to the adjusted first stage, and when the first stage does not need to be adjusted, the The final quality score is the quality score corresponding to the unadjusted first stage;

Based on the final quality score corresponding to each stage, calculate the overall quality score corresponding to the target software;

When it is detected that the overall quality score is greater than or equal to a preset quality threshold, a qualified report corresponding to the target software is generated.
The method according to claim 5, wherein after calculating the overall quality score corresponding to the target software based on the final quality score corresponding to each stage, the method further comprises:

When it is detected that the overall quality score is less than the preset quality threshold, email information is generated, and the email information is used to remind the developer that the development process of the target software is unqualified.
The method of claim 1, wherein the method further comprises:

Upload the software quality monitoring model corresponding to each stage to the blockchain.
A device for monitoring a software development process, comprising:

The acquiring unit is used to acquire the software quality monitoring model corresponding to each stage in the development process of the target software, wherein the software quality monitoring model corresponding to each stage is based on the preset scoring index and preset corresponding to each stage The scoring calculation method is constructed and obtained, and the development process of the target software includes a requirement analysis stage, a plan management stage, a development stage, a testing stage and a release stage;

The quality monitoring unit is used to monitor the quality of each stage according to the software quality monitoring model corresponding to each stage, and obtain the quality score corresponding to each stage;

The determination unit is used to determine whether each stage needs to be adjusted according to the quality score corresponding to each stage.
A terminal for monitoring a software development process, comprising a memory, a processor, and a computer program stored in the memory and running on the processor, and the processor implements when executing the computer program:

Obtain the software quality monitoring model corresponding to each stage in the development process of the target software, wherein the software quality monitoring model corresponding to each stage is constructed based on the preset scoring index corresponding to each stage and the preset scoring calculation method. , the development process of the target software includes a requirements analysis stage, a plan management stage, a development stage, a testing stage and a release stage;

According to the software quality monitoring model corresponding to each stage, the quality monitoring of each stage is carried out respectively, and the corresponding quality score of each stage is obtained;

Determine whether each stage needs to be adjusted according to the quality score corresponding to each stage.
The terminal according to claim 9, wherein, when the processor executes the computer program, it further implements:

collecting target data generated when the target software is developed to the first stage, where the first stage is any one of the each stage;

Based on the preset scoring index and the preset scoring calculation method in the software quality monitoring model corresponding to the first stage, the target data is scored to obtain the quality score corresponding to the first stage.
The terminal of claim 10, wherein, when the processor executes the computer program, it further implements:

obtaining the quality score corresponding to the first stage;

When it is detected that the quality score is less than a preset threshold, it is determined that the first stage needs to be adjusted; or,

When it is detected that the quality score is greater than or equal to the preset threshold, it is determined that the first stage does not need to be adjusted.
The terminal of claim 11, wherein the processor further implements when executing the computer program:

adjusting the first stage based on preset rules;

Based on the software quality monitoring model corresponding to the first stage, the quality of the adjusted first stage is monitored to obtain a quality score corresponding to the adjusted first stage.
The terminal according to any one of claims 10 to 12, wherein, when the processor executes the computer program, it further implements:

Determine the final quality score corresponding to each stage, when the first stage needs to be adjusted, the final quality score is the quality score corresponding to the adjusted first stage, and when the first stage does not need to be adjusted, the The final quality score is the quality score corresponding to the unadjusted first stage;

Based on the final quality score corresponding to each stage, calculate the overall quality score corresponding to the target software;

When it is detected that the overall quality score is greater than or equal to a preset quality threshold, a qualified report corresponding to the target software is generated.
The terminal of claim 13, wherein the processor further implements when executing the computer program:

When it is detected that the overall quality score is less than the preset quality threshold, email information is generated, and the email information is used to remind the developer that the development process of the target software is unqualified.
A computer-readable storage medium storing a computer program, wherein the computer program is executed by a processor to realize:

Obtain the software quality monitoring model corresponding to each stage in the development process of the target software, wherein the software quality monitoring model corresponding to each stage is constructed based on the preset scoring index corresponding to each stage and the preset scoring calculation method. , the development process of the target software includes a requirements analysis stage, a plan management stage, a development stage, a testing stage and a release stage;

According to the software quality monitoring model corresponding to each stage, the quality monitoring of each stage is carried out respectively, and the corresponding quality score of each stage is obtained;

Determine whether each stage needs to be adjusted according to the quality score corresponding to each stage.
The computer-readable storage medium of claim 15, wherein the computer program, when executed by the processor, further implements:

collecting target data generated when the target software is developed to the first stage, where the first stage is any one of the each stage;

Based on the preset scoring index and the preset scoring calculation method in the software quality monitoring model corresponding to the first stage, the target data is scored to obtain the quality score corresponding to the first stage.
The computer-readable storage medium of claim 16, wherein the computer program, when executed by the processor, further implements:

obtaining the quality score corresponding to the first stage;

When it is detected that the quality score is less than a preset threshold, it is determined that the first stage needs to be adjusted; or,

When it is detected that the quality score is greater than or equal to the preset threshold, it is determined that the first stage does not need to be adjusted.
The computer-readable storage medium of claim 17, wherein the computer program, when executed by the processor, further implements:

adjusting the first stage based on preset rules;

Based on the software quality monitoring model corresponding to the first stage, the quality of the adjusted first stage is monitored to obtain a quality score corresponding to the adjusted first stage.
The computer-readable storage medium of any one of claims 16 to 18, wherein the computer program, when executed by the processor, further implements:

Determine the final quality score corresponding to each stage, when the first stage needs to be adjusted, the final quality score is the quality score corresponding to the adjusted first stage, and when the first stage does not need to be adjusted, the The final quality score is the quality score corresponding to the unadjusted first stage;

Based on the final quality score corresponding to each stage, calculate the overall quality score corresponding to the target software;

When it is detected that the overall quality score is greater than or equal to a preset quality threshold, a qualified report corresponding to the target software is generated.
The computer-readable storage medium of claim 19, wherein the computer program, when executed by the processor, further implements:

When it is detected that the overall quality score is less than the preset quality threshold, email information is generated, and the email information is used to remind the developer that the development process of the target software is unqualified.