CN112668869A

CN112668869A - Method, device, terminal and storage medium for monitoring software development process

Info

Publication number: CN112668869A
Application number: CN202011560001.3A
Authority: CN
Inventors: 刘秋菊; 李向蔚
Original assignee: Ping An Technology Shenzhen Co Ltd
Current assignee: Ping An Technology Shenzhen Co Ltd
Priority date: 2020-12-25
Filing date: 2020-12-25
Publication date: 2021-04-16
Also published as: WO2022134348A1

Abstract

The application is applicable to the technical field of computers, and provides a method, a device, a terminal and a storage medium for monitoring a software development process, wherein the method comprises the following steps: acquiring a software quality monitoring model corresponding to each stage in the development process of target software, and performing quality monitoring on each stage according to the software quality monitoring model corresponding to each stage to obtain a quality score corresponding to each stage; and determining whether each stage needs to be adjusted according to the quality score corresponding to each stage. By the method, the comprehensive quality monitoring in the software development process is realized; and when quality monitoring is carried out on each stage based on the software quality monitoring model corresponding to each stage, the obtained quality score is more accurate, and then adaptive adjustment is carried out on each stage according to the quality score corresponding to each stage, so that the finally developed software is good in quality and strong in stability.

Description

Method, device, terminal and storage medium for monitoring software development process

Technical Field

The present application belongs to the field of computer technologies, and in particular, to a method, an apparatus, a terminal, and a storage medium for monitoring a software development process.

Background

The quality monitoring in the software development process determines the quality of software products to a great extent, so that quality monitoring at each flow stage in the software development process is very necessary. However, the existing software development process supervision software has simple functions, and cannot accurately and comprehensively monitor the quality of all process stages in the software development process, so that the quality of software products obtained by development is poor.

Disclosure of Invention

In view of this, embodiments of the present application provide a method, an apparatus, a terminal, and a storage medium for monitoring a software development process, so as to solve the problem that the quality of a developed software product is poor due to the fact that the existing software development process supervision software has a simple function and cannot accurately and comprehensively monitor the quality of all process stages in the software development process.

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

acquiring a software quality monitoring model corresponding to each stage in the development process of target software, wherein the software quality monitoring model corresponding to each stage is constructed and obtained on the basis of a preset score index and a preset score calculation method corresponding to each stage, and the development process of the target software comprises a demand analysis stage, a plan management stage, a development stage, a test stage and a release stage;

respectively monitoring the quality of each stage according to the software quality monitoring model respectively corresponding to each stage to obtain the quality score respectively corresponding to each stage;

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

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

the system comprises an acquisition unit, a storage unit and a processing unit, wherein the acquisition unit is used for acquiring a software quality monitoring model corresponding to each stage in the development process of target software, the software quality monitoring model corresponding to each stage is constructed and obtained based on a preset scoring index and a preset scoring calculation method corresponding to each stage, and the development process of the target software comprises a demand analysis stage, a plan management stage, a development stage, a test stage and a release stage;

the quality monitoring unit is used for respectively monitoring the quality of each stage according to the software quality monitoring model respectively corresponding to each stage to obtain the quality score respectively corresponding to each stage;

and the determining unit is used for determining whether each stage needs to be adjusted according to the quality score corresponding to each stage.

A third aspect of the embodiments 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 executable on the processor, wherein the processor implements the steps of the method for monitoring a software development process according to the first aspect when executing the computer program.

A fourth aspect of embodiments of the present application provides a computer storage medium storing a computer program which, when executed by a processor, implements the steps of the method of monitoring a software development process as described in the first aspect above.

A fifth aspect of the embodiments of the present application provides a computer program product, which, when running on a terminal for monitoring a software development process, causes the terminal for monitoring the software development process to execute the steps of the method for monitoring a software development process according to the first aspect.

The method for monitoring the software development process, the device for monitoring the software development process, the terminal for monitoring the software development process and the storage medium provided by the embodiment of the application have the following beneficial effects:

according to the embodiment of the application, a software quality monitoring model corresponding to each stage is constructed according to different preset scoring indexes and preset scoring calculation methods corresponding to each stage in the development process of target software; performing quality monitoring on each stage based on the software quality monitoring model corresponding to each stage respectively to obtain quality scores corresponding to each stage respectively; and determining whether each stage needs to be adjusted according to the quality score corresponding to each stage. The development process of the target software comprises a requirement analysis stage, a plan management stage, a development stage, a test stage and a release stage. Based on the method, quality monitoring is carried out on all flow stages in the software development process, and comprehensive quality monitoring in the software development process is realized; and because the software quality monitoring model corresponding to each stage is constructed according to different preset grading indexes and preset grading calculation methods corresponding to each stage, when quality monitoring is carried out on each stage based on the software quality monitoring models, the obtained quality grading is more accurate, and then adaptive adjustment is carried out on each stage according to the quality grading corresponding to each stage, so that the finally developed target software is good in quality and strong in stability.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

FIG. 1 is a schematic flow chart diagram of a method for monitoring a software development process according to an embodiment of the present application;

FIG. 2 is a schematic flow chart diagram of a method for monitoring a software development process according to another embodiment of the present invention;

FIG. 3 is a schematic flow chart diagram of a method for monitoring a software development process according to yet another embodiment of the present invention;

FIG. 4 is a schematic flow chart diagram of a method for monitoring a software development process according to yet another embodiment of the present invention;

FIG. 5 is a schematic diagram of an apparatus for monitoring a software development process according to an embodiment of the present application;

fig. 6 is a schematic diagram of a terminal for monitoring a software development process according to another embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The quality monitoring in the software development process determines the quality of software products to a great extent, so that quality monitoring at each flow stage in the software development process is very necessary. The inventor realizes that the existing software development process supervision software has simple functions and cannot accurately and comprehensively realize quality monitoring on all process stages in the software development process. For example, in the prior art, quality monitoring is usually performed only in a development stage and a test stage in a software development process; and the evaluation mode is single, for example, the evaluation is carried out according to whether the defects are encountered or not and the number of the defects in the software development process, so that the software product obtained by development is poor in quality and weak in stability.

In view of this, the present application provides a method for monitoring a software development process, in which a software quality monitoring model corresponding to each stage is constructed according to different preset score indexes and preset score calculation methods corresponding to each stage in the development process of target software; performing quality monitoring on each stage based on the software quality monitoring model corresponding to each stage respectively to obtain quality scores corresponding to each stage respectively; and determining whether each stage needs to be adjusted according to the quality score corresponding to each stage. The development process of the target software comprises a requirement analysis stage, a plan management stage, a development stage, a test stage and a release stage. Based on the method, quality monitoring is carried out on all flow stages in the software development process, and comprehensive quality monitoring in the software development process is realized; and because the software quality monitoring model corresponding to each stage is constructed according to different preset grading indexes and preset grading calculation methods corresponding to each stage, when quality monitoring is carried out on each stage based on the software quality monitoring models, the obtained quality grading is more accurate, and then adaptive adjustment is carried out on each stage according to the quality grading corresponding to each stage, so that the finally developed target software is good in quality and strong in stability.

Referring to fig. 1, fig. 1 is a schematic flowchart of a method for monitoring a software development process according to an embodiment of the present application. In this embodiment, the main execution body of the method for monitoring the software development process is a terminal, a server, and the like, where the terminal includes, but is not limited to, a mobile terminal such as a smart phone, a tablet computer, a Personal Digital Assistant (PDA), and the like, and may also include a terminal such as a desktop computer. In this embodiment, an execution subject is taken as an example for explanation, and the method for monitoring the software development process shown in fig. 1 may include S101 to S104, which are specifically as follows:

s101: the method comprises the steps of obtaining a software quality monitoring model corresponding to each stage in the development process of target software, wherein the software quality monitoring model corresponding to each stage is constructed and obtained on the basis of a preset scoring index and a preset scoring calculation method corresponding to each stage, and the development process of the target software comprises a demand analysis stage, a plan management stage, a development stage, a test stage and a release stage.

The development process of the target software may be divided into a demand analysis phase, a plan management phase, a development phase, a test phase, and a release phase in advance. The target software is the software to be developed, and can be understood as the software which is finally wanted by the user and needs to be developed. The software development process is a whole process for developing the software based on software design ideas and methods, and may include requirement analysis preset for target software, functions to be realized by the target software, a general structure and each module corresponding to the target software, work allocation of developers, how to interface the modules, an algorithm for realizing the target software, a coding mode corresponding to each module, tests of different dimensions, test cases, release time, conditions to be met during release, and the like. The development process of the target software is divided into a requirement analysis phase, a plan management phase, a development phase, a test phase and a release phase according to the included information. It should be noted that different software has different corresponding development processes, and the specific corresponding contents of the finally divided stages, namely, the requirement analysis stage, the plan management stage, the development stage, the test stage and the release stage, may also be different. The description is given for illustrative purposes only and is not intended to be limiting.

Optionally, in a possible implementation manner, the development process of the target software may be divided according to experience of the developer, or the developer uploads documents of each stage corresponding to the development process of the target software to the terminal, and the terminal identifies the documents of each stage, that is, identifies the documents corresponding to each of the requirement analysis stage, the plan management stage, the development stage, the test stage, and the release stage, to implement the division of the development process of the target software. The description is given for illustrative purposes only and is not intended to be limiting.

The specific development modes of each stage are different, and correspondingly, the software quality monitoring models corresponding to each stage are also different. The 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. And the preset scoring index corresponding to each stage is different from the preset scoring calculation method.

Illustratively, a first software quality monitoring model corresponding to the demand analysis stage is constructed according to a first preset score index and a first preset score calculation method corresponding to the demand analysis stage. The first preset scoring index includes: requirement confirmation, requirement documentation and requirement review. Wherein the requirement validation comprises: whether the requirement confirmation of more than 50% is completed before the development and whether the requirement confirmation of more than 50% is completed before the development is half of the whole development period. The requirements document includes: whether there is an explicit requirement document. The requirement review comprises the following steps: whether to carry out requirement evaluation or not and whether to test participation in the requirement evaluation or not. The total quality score corresponding to the requirement analysis stage can be adjusted according to actual conditions, in this embodiment, the total quality score corresponding to the requirement analysis stage is 20 points, wherein the requirement confirmation corresponds to 10 points, the requirement document corresponds to 5 points, and the requirement review corresponds to 5 points. The description is given for illustrative purposes only and is not intended to be limiting.

The first preset score calculating method includes: more than 50% of the demand validation is completed before development, and the corresponding score is the full score of the item, for example 5 points; 20% -50% of the requirement confirmation is completed before the development, and the corresponding score is half of the score of the item, such as 2.5 points; less than 20% of the demand validation is done before development, with a corresponding score of zero, e.g., 0; more than 50% of the demand validation is completed before half of the whole development cycle, and the corresponding score is the full score of the score, such as 5 scores; the requirement confirmation of 20-50% is completed before the development is carried out to half of the whole development period, and the corresponding score is half of the score of the item, such as 2.5 points; less than 20% of the demand validation is done until half of the entire development cycle, with a corresponding score of zero, e.g., 0.

The first preset score calculating method further includes: there is a clear requirement document, the corresponding score is the full score of the item, e.g. 5; without an explicit requirement document, the corresponding score is zero, e.g., 0.

The first preset score calculating method further includes: carrying out requirement evaluation, wherein the corresponding score is 2 points; no requirement evaluation is carried out, and the corresponding score is 0; the test participates in the requirement evaluation, and the corresponding score is 3; the test did not participate in the requirement review and the corresponding score was 3.

And constructing a first software quality monitoring model corresponding to the demand analysis stage according to the listed first preset scoring index and the first preset scoring calculation method. And quality monitoring can be carried out on the requirement analysis stage of the target software according to the first software quality monitoring model. The description is given for illustrative purposes only and is not intended to be limiting.

Illustratively, a second software quality monitoring model corresponding to the plan management stage is constructed according to a second preset score index corresponding to the plan management stage and a second preset score calculation method. The second preset scoring index includes: version plan rationality, story (story) split rationality, story hand-over rationality of target software development. The rationality of the version plan of the target software development comprises the following steps: whether a version plan is made in advance, whether a staging handover plan of a store exists, whether the version plan participates in the staging handover plan making or not and whether the staging handover plan is reasonable or not are tested. The storage split rationality comprises: whether the store is consistent with the offline split, whether the split of the store is assigned according to business logic rather than according to (head of person) tasks, and whether the store is sufficiently thin. The storage handover rationality includes: whether the Story is in time for transfer or not and whether sufficient test time exists after the complex function is transferred or not. The total quality score corresponding to the plan management stage can be adjusted according to actual conditions, in the embodiment, the total quality score corresponding to the plan management stage is 20, wherein the version plan rationality of target software development corresponds to 10, the storage split rationality corresponds to 5, and the storage handover rationality corresponds to 5. The description is given for illustrative purposes only and is not intended to be limiting.

The second preset score calculating method includes: the version plan is made in advance, the corresponding score is 2 points, the version plan is not made in advance, and the corresponding score is 0 point; the corresponding score of the staging handover plan with the store is 3, the corresponding score of the staging handover plan without the store is 0; the test participates in the stage-by-stage handover plan formulation, the corresponding score is 2, the test does not participate in the stage-by-stage handover plan formulation, and the corresponding score is 0; the staging transfer plan is reasonable, the corresponding score is 3, the staging transfer plan is unreasonable, and the corresponding score is 0.

The second preset score calculating method further includes: the stock is consistent with the offline split, and the corresponding score is 2; the store and the offline split are inconsistent, and the corresponding score is 0; the split of the store is allocated according to the business logic instead of the (head) task, and the corresponding score is 2; the resolution of the store is assigned according to (head of person) tasks, and the corresponding score is 0; whether the storage is divided or not is calculated according to the number proportion, and the corresponding score is the product of a preset constant and the proportion (for example, the ratio of the storage which does not exceed 3 days is 40% by statistics, and the corresponding score is 6 x 0.4-2.4 points).

The second preset score calculating method further includes: all storeys are handed over on time, and the corresponding score is 2; the Story part is handed over according to time, and the corresponding score is the product of a handover proportion and 2(2 is the corresponding score when the Story is all handed over according to time); sufficient testing time exists after the complex function is handed over, and the corresponding score is 3 points; there is not enough test time after the complex function is handed over, and the corresponding score is 0. Wherein, when the time which is more than or equal to 30% of the whole development cycle is still left after the complex function is handed over as the test time, the sufficient test time is judged after the complex function is handed over; when less than 30% of the whole development period of time remains as the test time after the complex function is handed over, it is judged that there is not enough test time after the complex function is handed over.

And constructing a second software quality monitoring model corresponding to the plan management stage according to the enumerated second preset score index and the second preset score calculation method. And monitoring the quality of the planning management stage of the target software according to the second software quality monitoring model. The description is given for illustrative purposes only and is not intended to be limiting.

Illustratively, a third software quality monitoring model corresponding to the development stage is constructed according to a third preset score index corresponding to the development stage and a third preset score calculation method. The third preset scoring index includes: development design and development compliance. Wherein, the development design comprises: whether to carry out design evaluation and whether to deliver detailed test design documents; developing compliance includes: whether there is a modification of entrainment, whether there is an artificial control of the number of defects. The total quality score corresponding to the development stage can be adjusted according to actual conditions, in this embodiment, the total quality score corresponding to the development stage is 20 points, wherein the development design corresponds to 10 points, and the development compliance corresponds to 5 points. The description is given for illustrative purposes only and is not intended to be limiting.

The third preset score calculation method includes: carrying out design evaluation, wherein the corresponding score is 5; design evaluation is not carried out, and the corresponding score is 0; delivering a detailed test design document, wherein the corresponding score is 5; no detailed test design documents are delivered, with a corresponding score of 0.

The third preset score calculating method further includes: with entrainment modification, the corresponding score is 5 points; no entrainment modification, the corresponding score is 0; artificially controlling the number of defects, wherein the corresponding score is 5; the number of defects is controlled artificially, and the corresponding score is 0.

And constructing and obtaining a third software quality monitoring model corresponding to the development stage according to the enumerated third preset score index and the third preset score calculation method. And quality monitoring can be carried out on the development stage of the target software according to the third software quality monitoring model. The description is given for illustrative purposes only and is not intended to be limiting.

Illustratively, a fourth software quality monitoring model corresponding to the test stage is constructed according to a fourth preset score index corresponding to the test stage and a fourth preset score calculation method. The fourth preset scoring index includes: whether a Test case evaluation link exists or not, whether a Test progress report exists or not, whether a User Acceptance Test (UAT) enters a notice or not, whether a UAT Acceptance result exists or not, whether a system Test is completed on time or not, and whether a software plate is closed on time or not. The total quality score corresponding to the testing stage can be adjusted according to the actual situation, and in this embodiment, the total quality score corresponding to the testing stage is 20. The description is given for illustrative purposes only and is not intended to be limiting.

The fourth preset score calculation method includes: a test case evaluation link exists, and the corresponding score is 2; no test case evaluation link exists, and the corresponding score is 0; a test progress report is provided, and the corresponding score is 2; no test progress report exists, and the corresponding score is 0; a user acceptance test UAT enters the notice, and the corresponding score is 1; no user acceptance test UAT enters into the notice, and the corresponding score is 0; the UAT acceptance result is obtained, and the corresponding score is 1; no UAT acceptance result exists, and the corresponding score is 0; completing the system test on time, wherein the corresponding score is 7; the system test can not be completed on time, and the corresponding score is 0; performing software sealing plate on time, wherein the corresponding score is 7; software sealing can not be performed on time, and the corresponding score is 0.

And constructing a fourth software quality monitoring model corresponding to the testing stage according to the enumerated fourth preset score index and a fourth preset score calculation method. And monitoring the quality of the target software in the testing stage according to the fourth software quality monitoring model. The description is given for illustrative purposes only and is not intended to be limiting.

Illustratively, a fifth software quality monitoring model corresponding to the release stage is constructed according to a fifth preset score index corresponding to the release stage and a fifth preset score calculation method. The fifth preset scoring index includes: the defect density corresponding to the target software, the defect proportion corresponding to the target software, whether smoke is generated and the defect repair number are counted. The total quality score corresponding to the release stage can be adjusted according to the actual situation, and in this embodiment, the total quality score corresponding to the release stage is 20. The description is given for illustrative purposes only and is not intended to be limiting.

The fifth preset score calculating method includes: the defect density is less than or equal to 0.1, and the corresponding fraction is 5 points; the defect density is more than 0.1 and less than or equal to 0.2, and the corresponding fraction is 2.5; the defect density was greater than 0.2, with a corresponding score of 0. The defect proportion is less than or equal to 5 percent, and the corresponding fraction is 5 points; the defect proportion is more than 5 percent and less than or equal to 20 percent, and the corresponding fraction is 2.5 points; the defect ratio is more than 20%, and the corresponding fraction is 0. And whether the smoke passes or not is judged, and the corresponding fraction is the product of the ratio of the number of normal handoffs and the fraction of 5. The defect repair number is 0, and the corresponding score is 5; the defect repair number is less than or equal to 5, and the corresponding score is 2.5; the defect repair number is more than 5, and the corresponding score is 0.

And constructing and obtaining a fifth software quality monitoring model corresponding to the release stage according to the enumerated fifth preset score index and a fifth preset score calculation method. And quality monitoring can be carried out on the issuing stage of the target software according to the fifth software quality monitoring model. The description is given for illustrative purposes only and is not intended to be limiting.

And the terminal acquires the software quality monitoring model corresponding to each stage respectively. Namely, the terminal acquires a first software quality monitoring model corresponding to a demand analysis stage, a second software quality monitoring model corresponding to a plan management stage, a third software quality monitoring model corresponding to a development stage, a fourth software quality monitoring model corresponding to a test stage and a fifth software quality monitoring model corresponding to a release stage.

S102: and respectively monitoring the quality of each stage according to the software quality monitoring model respectively corresponding to each stage to obtain the quality score respectively corresponding to each stage.

And respectively monitoring the quality of each stage based on different software quality monitoring models corresponding to each stage. Illustratively, data generated when the target software is developed to each stage is collected, and the data generated by each stage is scored through a preset scoring index and a preset scoring calculation method in a software quality monitoring model corresponding to each stage, so that quality scores corresponding to each stage are obtained. The data generated when the target software is developed to each stage may be the data generated when the target software is developed to each stage uploaded by a developer, or the data generated when the target software is developed to each stage in the actual development process. The description is given for illustrative purposes only and is not intended to be limiting.

Referring to fig. 2, fig. 2 is a schematic flow chart of a method for monitoring a software development process according to another embodiment of the present invention. Optionally, in a possible implementation manner, as shown in fig. 2, the S102 may include S1021 to S1022, specifically as follows:

s1021: and acquiring target data generated when the target software is developed to a first stage, wherein the first stage is any one stage in each stage.

S1022: and scoring the target data based on a preset scoring index and a 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 a requirement analysis stage, a plan management stage, a development stage, a test stage and a release stage in the development process of target software. The first phase may be a demand analysis phase, a plan management phase, a development phase, a test phase, and a release phase in that order.

Version information corresponding to the target software can be obtained in advance, and the current stage of the target software is determined based on the version information. For example, the version information corresponding to the target software may be automatically obtained by calling an Application Programming Interface (API) and/or a preset defect management system, where the version information is used to indicate which stage the target software is at. The description is given for illustrative purposes only and is not intended to be limiting.

Illustratively, when the first phase is a requirement analysis phase, target data generated by the target software when developed into the requirement analysis phase is collected. For example, the target software uploads a requirement confirmation progress file, a requirement document and a requirement review request during the requirement analysis phase, and the collected target data may include: a requirement confirmation progress file, a requirement document and a requirement review request.

And scoring the target data according to a first preset scoring index and a first preset scoring calculation method in a first software quality monitoring model corresponding to the demand analysis stage. For example, the item is scored according to the actual completion of the demand confirmation in the demand confirmation progress file. If the progress file is confirmed according to the requirement, only the requirement confirmation of more than 50% is confirmed to be completed before the development, and the corresponding score is 5. As another example, it is detected that all the requirement documents are explicit requirements, and the corresponding score is 5. The target data comprises a requirement review request, and the corresponding score of the item is 5.

And after scoring the target data, adding the scores corresponding to each piece of data to obtain the quality score corresponding to the requirement analysis stage. For example, 5 points corresponding to the requirement confirmation progress file, 5 points corresponding to the requirement document and 5 points corresponding to the requirement review request are added to obtain 15 points, and then the quality score corresponding to the requirement analysis stage is 15 points. The description is given for illustrative purposes only and is not intended to be limiting.

Illustratively, when the first phase is a planning management phase, target data generated by the target software when developed into the planning management phase is collected. For example, the target software uploads a version plan rationality document, a store split rationality document, and a store handover rationality document during a plan management phase, and the target data collected at this time may include: version plan rationality documents, store split rationality documents, store hand-over rationality documents. The version plan rationality document comprises a version plan which is made in advance, a test participation stage transfer plan which is made and a stage transfer plan which is reasonable. The store split rationality document includes that the split of the store is 40% in terms of (head of person) task assignment, that the store and offline split are consistent, and that no more than 3 days are available. The storage handover rationality document comprises that the storage is completely handed over on time, and the time which is greater than or equal to 30% of the whole development period is used as the test time after the complex function is handed over.

And scoring the target data according to a second preset scoring index and a second preset scoring calculation method in a second software quality monitoring model corresponding to the plan management stage. For example, the version plan is previously rated as 2 points based on a second preset rating index and a second preset rating calculation method; detecting no staging handover plan of the store, wherein the corresponding score is 0; the test participates in the staged handover plan formulation, and the corresponding score is 2; the stock is consistent with the offline split, and the corresponding score is 2; the resolution of the store is assigned according to (head of person) tasks, and the corresponding score is 0; the storage rate was 40% without more than 3 days, corresponding to a score of 6 x 0.4-2.4; all storeys are handed over on time, and the corresponding score is 2; and after the complex function is handed over, the time which is more than or equal to 30% of the whole development period is used as the test time, the sufficient test time is judged after the complex function is handed over, and the corresponding score is 3.

And after scoring the target data, adding the scores corresponding to each piece of data to obtain the quality score corresponding to the plan management stage. For example, the scores of the target data corresponding to the plan management stage are added to obtain 13.4 scores, that is, the quality score corresponding to the plan management stage is 13.4 scores. The description is given for illustrative purposes only and is not intended to be limiting.

Illustratively, when the first phase is a development phase, target data generated by the target software when developed to the development phase is collected. For example, acquiring target data corresponding to the development stage includes: design review information, detailed test design documents, entrained modification and non-artificial control of defect number are carried out.

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

And after scoring the target data, adding the scores corresponding to each piece of data to obtain the quality score corresponding to the development stage. For example, the scores of the target data corresponding to the development stage are added to obtain 15 scores, that is, the quality score corresponding to the development stage is 15 scores. The description is given for illustrative purposes only and is not intended to be limiting.

Illustratively, when the first phase is a testing phase, target data generated by the target software when developed to the testing phase is collected. For example, acquiring target data corresponding to the test stage includes: the test case reviews link information, a test progress report, a UAT acceptance result, time for completing system test and time for performing software plate sealing.

And scoring the target data according to a fourth preset scoring index and a fourth preset scoring calculation method in a fourth software quality monitoring model corresponding to the testing stage. For example, the detected test case review link information is scored as 2 on the basis of a fourth preset scoring index and a fourth preset scoring calculation method; detecting a test progress report, wherein the corresponding score is 2; if no user acceptance test UAT entrance notification is detected, the corresponding score is 0; detecting a UAT acceptance result, wherein the corresponding score is 1; detecting that the time for completing the system test is within the preset completion time, wherein the corresponding score is 7; and detecting that the time for carrying out software plate closing is not within the preset plate closing time, wherein the corresponding score is 0.

And after scoring the target data, adding the scores corresponding to each piece of data to obtain the quality score corresponding to the test stage. For example, the scores of the target data corresponding to the test period are added to obtain 12 scores, that is, the corresponding quality score is developed to be 12 scores. The description is given for illustrative purposes only and is not intended to be limiting.

Illustratively, when the first phase is the release phase, target data generated by the target software during development to the release phase is collected. For example, acquiring the target data corresponding to the publishing stage includes: the defect density is 0.15, the defect proportion corresponding to the target software is 10%, the proportion of the normal handover number is 0.6, and the defect repair number is 3.

And scoring the target data according to a fifth preset scoring index and a fifth preset scoring calculation method in a fifth software quality monitoring model corresponding to the release stage. For example, a defect density of 0.15 is scored as 2.5 points based on a fifth preset scoring index and a fifth preset scoring calculation method; the defect proportion corresponding to the target software is 10%, and the corresponding fraction is 2.5 points; the ratio of the number of normal handoffs is 0.6, corresponding to a score of 5 x 0.6 to 3; the number of defect repairations is 3, and the corresponding score is 2.5.

And after scoring the target data, adding the scores corresponding to each piece of data to obtain the quality score corresponding to the release stage. For example, the scores of the target data corresponding to the release stage are added to obtain 10.5 points, that is, the quality score corresponding to the development is 10.5 points. The description is given for illustrative purposes only and is not intended to be limiting.

S103: and determining 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 threshold corresponding to each stage is used for judging whether the quality score corresponding to each stage reaches the standard or not, and further judging whether each stage needs to be adjusted or not.

When a certain stage needs to be adjusted, the stage is adjusted according to the corresponding scores of all the data in the target data of the stage. For example, if the score corresponding to a certain data is low and affects the overall quality score at that stage, the corresponding items of the data are adjusted accordingly. The description is given for illustrative purposes only and is not intended to be limiting.

Referring to fig. 3, fig. 3 is a schematic flow chart of a method for monitoring a software development process according to another embodiment of the present invention. Optionally, as shown in fig. 3, the foregoing S103 may include S1031 to S1033, and it is worth to be noted that S1032 and S1033 are juxtaposed, and according to a comparison result between the quality score and the preset threshold, it is determined whether to execute S1032 or S1033 after S1031, instead of executing S1033 after S1032, which is specifically as follows:

s1031: and acquiring the quality score corresponding to the first stage.

S1032: and when the quality score is detected to be smaller than a preset threshold value, determining that the first stage needs to be adjusted. Or, S1033: determining that no adjustment is required for the first stage when it is detected that the quality score is greater than or equal to the preset threshold.

Exemplarily, when the first stage is a demand analysis stage, a first preset threshold corresponding to the demand analysis stage is obtained, and the first preset threshold is used for judging whether a quality score corresponding to the demand analysis stage reaches the standard, and further judging whether the demand analysis 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 15 corresponding to the demand analysis stage with the first preset threshold 12, 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. The description is given for illustrative purposes only and is not intended to be limiting.

Illustratively, when the first stage is a plan management stage, a second preset threshold corresponding to the plan management stage is obtained, and the second preset threshold is used for judging whether the quality score corresponding to the plan management stage reaches the standard, and further judging whether the plan management 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 plan management stage is obtained as 13.4 points.

And comparing the quality score 13.4 corresponding to the plan management stage with the second preset threshold value 15, obviously, the quality score corresponding to the plan management stage is smaller than the second preset threshold value, and determining that the plan management stage needs to be adjusted. The description is given for illustrative purposes only and is not intended to be limiting.

Illustratively, when the first stage is a development stage, a third preset threshold corresponding to the development stage is obtained, and the third preset threshold is used for judging whether the quality score corresponding to the development stage reaches the standard, and further judging 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.

And comparing the quality score 15 corresponding to the development stage with the third preset threshold value 14, wherein obviously, the quality score corresponding to the development stage is greater than the third preset threshold value, and the development stage is determined not to need to be adjusted. The description is given for illustrative purposes only and is not intended to be limiting.

Exemplarily, when the first stage is a test stage, a fourth preset threshold corresponding to the test stage is obtained, and the fourth preset threshold is used for judging whether the quality score corresponding to the test stage reaches the standard, and further judging whether the test 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.

And comparing the quality score 12 corresponding to the testing stage with a fourth preset threshold 15, wherein obviously, the quality score corresponding to the development stage is smaller than the fourth preset threshold, and the testing stage is determined to need to be adjusted. The description is given for illustrative purposes only and is not intended to be limiting.

Illustratively, when the first stage is an issuing stage, a fifth preset threshold corresponding to the issuing stage is obtained, and the fifth preset threshold is used for judging whether the quality score corresponding to the issuing stage reaches the standard, and further judging whether the issuing 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.

And comparing the quality score 10.5 corresponding to the release stage with the fifth preset threshold value of 10, wherein obviously, the quality score corresponding to the release stage is greater than the fifth preset threshold value, and the release stage is determined not to need to be adjusted. The description is given for illustrative purposes only and is not intended to be limiting.

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; and monitoring the quality of the adjusted first stage based on the software quality monitoring model corresponding to the first stage to obtain a quality score corresponding to the adjusted first stage.

The preset rule may be used to detect the main data affecting the quality score corresponding to the first stage, that is, the data having a large effect on the quality score corresponding to the first stage, and adjust the data accordingly. For example, a data in the first stage corresponds to a score of 0, and the data is the main data affecting the quality score corresponding to the first stage. And analyzing the reasons with the score of 0 specifically, and adopting different adjustment modes according to different reasons. If the data is lack, the data is complemented; if the data setting is not reasonable, the data is reset. The description is given for illustrative purposes only and is not intended to be limiting.

Following the example in S103, it can be known from the description in S103 that the first phase is the schedule management phase and needs to be adjusted, and the first phase is the test phase.

For example, the first stage is taken as a plan management stage for explanation, adjustment is required in the plan management stage, and the quality score corresponding to the plan management stage is 13.4. As can be seen from the description in S1022, the plan management stage does not detect the staged handover plan of the store, and the score corresponding to this data is 0; the split of the store is assigned according to the (head of person) task, and the score corresponding to the data is 0. These two terms mainly affect the quality score corresponding to the management stage of the plan. Therefore, when the plan management stage is adjusted, the two aspects can be started. For example, an installment handover plan of the store is submitted, and the split of the store is assigned according to the business logic. The description is given for illustrative purposes only and is not intended to be limiting.

And based on a second software quality monitoring model corresponding to the plan management stage, performing quality monitoring again on the adjusted plan management stage to obtain a quality score corresponding to the adjusted plan management stage. For example, the target data corresponding to the adjusted plan management stage is acquired, and the target data corresponding to the adjusted plan management stage is scored according to a second preset scoring index and a second preset scoring calculation method in a second software quality monitoring model corresponding to the plan management stage, so as to obtain a quality score corresponding to the adjusted plan management stage. Exemplarily, target data corresponding to the adjusted plan management stage includes a staged handover plan of a store, and a score corresponding to the data is 3 points; the splitting of the store is distributed according to business logic, and the score corresponding to the data is 2; the scoring process corresponding to the remaining data may refer to the related description in S1032, and is not described herein again.

As can be seen from the above, the quality score for the plan management stage before adjustment was 13.4 points, and the quality score for the plan management stage after adjustment was 18.4 points. Optionally, in a possible implementation manner, the quality score 18.4 corresponding to the adjusted plan management phase may be compared with the second preset threshold 15, obviously, the quality score corresponding to the plan management phase is greater than the second preset threshold, and it is determined that the adjusted plan management phase reaches the standard, and the adjustment is not needed again. And if the obtained result is compared again and the plan management stage is required to be adjusted, performing secondary adjustment on the adjusted plan management stage again until the plan management stage reaches the standard and does not need to be adjusted. The description is given for illustrative purposes only and is not intended to be limiting.

Illustratively, the first stage is taken as a test stage, which needs to be adjusted, and the corresponding quality score of the test stage is 12. As can be seen from the description in S1022, the time for performing software sealing in the test phase is not within the preset sealing time, and the corresponding score is 0. It is mainly this term that affects the corresponding quality score at this stage of the test. Therefore, when the test phase is adjusted, it is possible to start from this aspect. For example, the time for software sealing plate is advanced, so that the time for software sealing plate is within the preset time for sealing plate.

And monitoring the quality of the adjusted test stage again based on a fourth software quality monitoring model corresponding to the test stage to obtain a quality score corresponding to the adjusted test stage. For example, the target data corresponding to the adjusted test stage is obtained, and the target data corresponding to the adjusted test stage is scored according to a fourth preset scoring index and a fourth preset scoring calculation method in a fourth software quality monitoring model corresponding to the test stage, so as to obtain a quality score corresponding to the adjusted test stage. Illustratively, the time for software sealing is advanced in the target data corresponding to the adjusted test phase, 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, and the score corresponding to the data is 7 points. The scoring process corresponding to the rest of each data may refer to the related description in S1022, and is not described herein again.

As can be seen from the above, the quality score for the test period before adjustment was 12 points, and the quality score for the test period after adjustment was 19 points. Optionally, in a possible implementation manner, the quality score 19 corresponding to the adjusted test phase may be compared with the fourth preset threshold 15, obviously, the quality score corresponding to the adjusted test phase is greater than the fourth preset threshold, and it is determined that the adjusted test phase reaches the standard without being adjusted again. If the result obtained by the comparison again still needs to be adjusted in the testing stage, the adjusted testing stage is adjusted again for the second time until the testing stage reaches the standard and does not need to be adjusted. The description is given for illustrative purposes only and is not intended to be limiting.

Optionally, in a possible implementation manner, the method for monitoring the software development process may further include: determining a final quality score corresponding to each stage, wherein 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 final quality score is the quality score corresponding to the unadjusted first stage; calculating the total quality score corresponding to the target software based on the final quality score corresponding to each stage; and when the total quality score is detected to be greater than or equal to the preset quality threshold, generating a qualified report corresponding to the target software. And when the total quality score is smaller than the preset quality threshold value, generating mail information, wherein the mail information is used for reminding developers that the development process of the target software is unqualified.

Illustratively, the final quality score for each stage is different, as each stage may or may not require adjustment. Or a first stage, which is any one of a requirement analysis stage, a plan management stage, a development stage, a test stage, and a release stage. When the first stage needs to be adjusted, the final quality score corresponding to the first stage is the adjusted quality score corresponding to the first stage, and since the adjustment may be performed multiple times, the adjustment refers to the last adjustment, and it can also be understood that the quality score corresponding to the first stage meets the standard, and the quality score corresponding to the first stage 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, namely the quality score corresponding to the first stage is obtained when the software quality monitoring model corresponding to the first stage is adopted to perform quality monitoring on the first stage for the first time.

For example, when the first stage is a demand analysis stage, which does not need to be adjusted, the final quality score corresponding to the demand analysis stage is 15 points of the initial quality score. When the first stage is a 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 of the quality score corresponding to the adjusted plan management stage. When the first stage is a development stage, the development stage does not need to be adjusted, and the final quality score corresponding to the development stage is 15 points of the initial quality score. When the first stage is a testing stage, the testing stage needs to be adjusted, and the final quality score corresponding to the testing stage is 19 scores corresponding to the adjusted testing stage. When the first stage is a publishing stage, the publishing stage does not need to be adjusted, and the final quality score corresponding to the publishing stage is 10.5 points of the initial quality score. The description is given for illustrative purposes only and is not intended to be limiting.

And adding the final quality scores corresponding to each stage, wherein the obtained score is the total quality score corresponding to the target software. For example, 15 points of final quality scores corresponding to the requirement analysis stage, 18.4 points of final quality scores corresponding to the plan management stage, 15 points of final quality scores corresponding to the development stage, 19 points of final quality scores corresponding to the test stage, and 10.5 points of final quality scores corresponding to the release stage are added to obtain 77.9 points of total quality scores corresponding to the target software. The description is given for illustrative purposes only and is not intended to be limiting.

The preset quality threshold is used for judging whether the total quality score corresponding to the target software reaches the standard, namely judging whether the development process of the target software is qualified. The preset quality threshold may be adjusted according to different target software, for example, the preset quality threshold may be 75 minutes, 85 minutes, 90 minutes, etc., which is only an exemplary illustration and is not limited thereto.

Illustratively, the overall quality score corresponding to the target software is compared with the magnitude of the preset quality threshold. When the preset quality threshold is 75 minutes, obviously, 77.9 minutes of the total quality score corresponding to the target software is greater than 75 minutes of the preset quality threshold, and at this time, a qualified report corresponding to the target software is generated. 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 finally obtained target software is qualified. The qualification report may include target data for each stage of the target software, a quality score for each stage, a quality score for each data individually, an overall quality score for the target software, and the like. The description is given for illustrative purposes only and is not intended to be limiting.

When the preset quality threshold is 85 minutes, obviously, 77.9 minutes of the total quality score corresponding to the target software is smaller than 85 minutes of the preset quality threshold, and at this time, mail information is generated and used for reminding developers 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 finally obtained target software is unqualified. When receiving the mail information, the developer may check the whole development process of the target software, and perform individual adjustment on each stage and/or adjust a preset threshold corresponding to each stage, which is only an exemplary illustration here, and is not limited to this.

After each stage is independently adjusted and/or the preset threshold corresponding to each stage is adjusted, quality monitoring can be performed on the development process of the new round of target software again by the method for monitoring the software development process provided by the application, and the specific monitoring process is not repeated.

Optionally, in a possible implementation manner, after quality monitoring is performed on each stage, a mail corresponding to each stage may be generated and sent to a developer, so that the developer can be timely reminded of the development progress of the current target software and the development quality of each stage, and the developer can conveniently adjust the development progress in time, thereby ensuring that the target software finally developed is good in quality and strong in stability, and early warning in the software development process is achieved.

Optionally, in a possible implementation manner, before the target software is developed, the email reminds the developer to upload information such as a requirement confirmation progress file, a requirement document, and a requirement review request, which are required to be used in a requirement analysis stage. And in the development stage corresponding to the target software, the mail reminds the developer to send a test progress report, a UAT acceptance result and the like, and after the terminal detects the data, the data can be scored through a fourth software quality monitoring model.

Optionally, in a possible implementation manner, a comparison graph, a trend graph, and the like may be generated according to the quality score corresponding to each stage before the adjustment, the overall quality score corresponding to the target software, the individual score corresponding to each data, the quality score corresponding to each stage after the adjustment, and the like. The information is uploaded to a preset mapping table system, and the mapping table system can generate a general comparison chart, a general radar chart and a general trend chart corresponding to the target software according to the information, and generate a radar chart, a trend chart and a comparison chart corresponding to each phase according to each phase. The description is given for illustrative purposes only and is not intended to be limiting.

In the embodiment of the application, a software quality monitoring model corresponding to each stage is constructed according to different preset scoring indexes and preset scoring calculation methods corresponding to each stage in the development process of target software; performing quality monitoring on each stage based on the software quality monitoring model corresponding to each stage respectively to obtain quality scores corresponding to each stage respectively; and determining whether each stage needs to be adjusted according to the quality score corresponding to each stage. The development process of the target software comprises a requirement analysis stage, a plan management stage, a development stage, a test stage and a release stage. Based on the method, quality monitoring is carried out on all flow stages in the software development process, and comprehensive quality monitoring in the software development process is realized; and because the software quality monitoring model corresponding to each stage is constructed according to different preset grading indexes and preset grading calculation methods corresponding to each stage, when quality monitoring is carried out on each stage based on the software quality monitoring models, the obtained quality grading is more accurate, and then adaptive adjustment is carried out on each stage according to the quality grading corresponding to each stage, so that the finally developed target software is good in quality and strong in stability. And the method automatically monitors the quality of each stage through the software quality monitoring model corresponding to each stage, so that developers do not need to stare at the software quality monitoring model all the time, the developers can do more other works, the two hands of the developers are liberated, the cost of developing the software is saved on the side, and the efficiency and the quality of developing the software are improved.

Referring to fig. 4, fig. 4 is a schematic flowchart of a method for monitoring a software development process according to still another embodiment of the present invention. The method may include S201-S204. Steps S201 to S203 shown in fig. 4 may refer to the description of steps S101 to S103 in the embodiment corresponding to fig. 1, and are not repeated here for brevity. Step S204 will be specifically explained below.

S204: and uploading the software quality monitoring models respectively corresponding to each stage to a block chain.

Uploading the software quality monitoring models corresponding to each stage respectively to a block chain, namely uploading a first software quality monitoring model corresponding to a demand analysis stage, a second software quality monitoring model corresponding to a plan management stage, a third software quality monitoring model corresponding to a development stage, a fourth software quality monitoring model corresponding to a test stage and a fifth software quality monitoring model corresponding to a release stage respectively to the block chain.

In this embodiment, the software quality monitoring models corresponding to each stage are uploaded to the block chain, so that the security and the fair transparency to the user can be ensured. And uploading the software quality monitoring models respectively corresponding to each stage to the blockchain, so that the software quality monitoring models respectively corresponding to each stage can be prevented from being maliciously tampered by means of the characteristic that files on the blockchain cannot be tampered randomly, a subsequent user can directly and accurately obtain the software quality monitoring models respectively corresponding to each stage, and the subsequent user can conveniently use the software quality monitoring models respectively corresponding to each stage to perform quality monitoring on the development process of target software.

The blockchain referred to in this example is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.

Referring to fig. 5, fig. 5 is a schematic diagram of an apparatus for monitoring a software development process according to an embodiment of the present disclosure. The device comprises units for performing the steps in the embodiments corresponding to fig. 1-4. Please refer to the related description of the embodiments corresponding to fig. 1 to 4. For convenience of explanation, only the portions related to the present embodiment are shown. Referring to fig. 5, it includes:

the acquiring unit 310 is configured to acquire a software quality monitoring model corresponding to each stage in a development process of target software, where the software quality monitoring model corresponding to each stage is constructed based on a preset score index and a preset score calculation method corresponding to each stage, and the development process of the target software includes a demand analysis stage, a plan management stage, a development stage, a test stage, and a release stage;

the quality monitoring unit 320 is configured to perform quality monitoring on each stage according to the software quality monitoring model corresponding to each stage, respectively, to obtain a 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 a first stage, wherein the first stage is any one stage in each stage;

and scoring the target data based on a preset scoring index and a 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.

Optionally, the determining unit 330 is specifically configured to:

acquiring a quality score corresponding to the first stage;

when the quality score is detected to be smaller than a preset threshold value, determining that the first stage needs to be adjusted; or the like, or, alternatively,

determining that no adjustment is required for the first stage when it is detected that the quality score is greater than or equal to the preset threshold.

Optionally, the apparatus further comprises:

the adjusting unit is used for adjusting the first stage based on a preset rule;

and the scoring unit is used for monitoring the quality of the adjusted first stage based on the software quality monitoring model corresponding to the first stage to obtain the quality score corresponding to the adjusted first stage.

Optionally, the apparatus further comprises:

a score determining unit, configured to determine a final quality score corresponding to each stage, where when the first stage needs to be adjusted, the final quality score is a quality score corresponding to the adjusted first stage, and when the first stage does not need to be adjusted, the final quality score is a quality score corresponding to the unadjusted first stage;

the calculating unit is used for calculating the total 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 qualification 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 apparatus further comprises:

and the second generating unit is used for generating mail information when detecting that the total quality score is smaller than the preset quality threshold, wherein the mail information is used for reminding a developer that the development process of the target software is unqualified.

Optionally, the apparatus further comprises:

and the uploading unit is used for uploading the software quality monitoring models respectively corresponding to each stage to the block chain.

Referring to fig. 6, fig. 6 is a schematic diagram of a terminal for monitoring a software development process according to another embodiment of the present application. As shown in fig. 6, the terminal 4 for monitoring the software development process of this embodiment includes: a processor 40, a memory 41, and computer instructions 42 stored in the memory 41 and executable on the processor 40. The processor 40, when executing the computer instructions 42, implements the steps in the various method embodiments described above for monitoring software development processes, such as S101-S103 shown in fig. 1. Alternatively, the processor 40, when executing the computer instructions 42, implements the functions of the units in the embodiments described above, such as 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 that are stored in the memory 41 and executed by the processor 40 to accomplish the present application. The one or more units may be a series of computer instruction segments capable of performing specific functions, which are used to describe the execution of the computer instructions 42 in the terminal 4 for monitoring the software development process. For example, the computer instructions 42 may be divided into an acquisition unit, a quality monitoring unit, and a determination unit, each unit functioning specifically as described above.

The terminal for monitoring the software development process may include, but is not limited to, a processor 40 and a memory 41. It will be understood by those skilled in the art that fig. 6 is merely an example of a terminal 4 for monitoring a software development process and is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or different components, for example, the terminal for monitoring a software development process may also include input-output terminals, network access terminals, buses, etc.

The Processor 40 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, 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 for monitoring the software development process, such as a hard disk or a memory of the terminal for monitoring the software development process. The memory 41 may also be an external storage terminal of the terminal for monitoring the software development process, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are equipped on the terminal for monitoring the software development process. Further, the memory 41 may also include both an internal storage unit and an external storage terminal of the terminal that monitors the software development process. The memory 41 is used for storing the computer instructions and other programs and data required by the terminal. The memory 41 may also be used to temporarily store data that has been output or is to be output.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not cause the essential features of the corresponding technical solutions to depart from the spirit scope of the technical solutions of the embodiments of the present application, and are intended to be included within the scope of the present application.

Claims

1. A method of monitoring a software development process, comprising:

2. The method of claim 1, wherein the quality monitoring is performed on each stage according to the software quality monitoring model corresponding to each stage, and obtaining the quality score corresponding to each stage comprises:

3. The method of claim 2, wherein determining whether each stage requires adjustment based on the quality score corresponding to each stage comprises:

acquiring a quality score corresponding to the first stage;

4. The method of claim 3, wherein after determining that the first stage requires adjustment when the quality score is detected to be less than a predetermined threshold, the method further comprises:

adjusting the first stage based on a preset rule;

and monitoring the quality of the adjusted first stage based on the software quality monitoring model corresponding to the first stage to obtain a quality score corresponding to the adjusted first stage.

5. The method of any of claims 2 to 4, further comprising:

determining a final quality score corresponding to each stage, wherein 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 final quality score is the quality score corresponding to the unadjusted first stage;

calculating an overall quality score corresponding to the target software based on the final quality score corresponding to each stage;

and when the total quality score is detected to be greater than or equal to a preset quality threshold, generating a qualified report corresponding to the target software.

6. The method of claim 5, wherein after calculating the overall quality score for the target software based on the final quality score for each stage, the method further comprises:

and when the total quality score is smaller than the preset quality threshold value, generating mail information, wherein the mail information is used for reminding a developer that the development process of the target software is unqualified.

7. The method of claim 1, wherein the method further comprises:

and uploading the software quality monitoring models respectively corresponding to each stage to a block chain.

8. An apparatus for monitoring a software development process, comprising:

9. A terminal for monitoring a software development process, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 7 when executing the computer program.

10. A computer storage medium storing a computer program, characterized in that the computer program, when executed by a processor, implements the method according to any one of claims 1 to 7.