CN115543261A - Software development data statistical method, device, computer equipment and medium - Google Patents
Software development data statistical method, device, computer equipment and medium Download PDFInfo
- Publication number
- CN115543261A CN115543261A CN202211244880.8A CN202211244880A CN115543261A CN 115543261 A CN115543261 A CN 115543261A CN 202211244880 A CN202211244880 A CN 202211244880A CN 115543261 A CN115543261 A CN 115543261A
- Authority
- CN
- China
- Prior art keywords
- development
- requirement
- software development
- software
- stage
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a software development data statistical method, a device, computer equipment and a medium, wherein the method comprises the following steps: in a software development requirement stage, acquiring a software development requirement, and counting the requirement quantity of the software development requirement; in the development stage of software development, generating a development result according to each software development requirement, and counting the development amount of the development result; in the testing stage of software development, testing each research and development result and determining the demand defect amount caused by the software development demand; in the delivery stage of software development, acquiring the online defect amount of the target software after online; if the online defect amount does not meet a third requirement, informing the software development test stage; and if the online defect amount meets a third requirement, completing the development of the target software. According to the method and the device, the improvement and optimization process of the project can be accelerated, so that the development efficiency of software is improved.
Description
Technical Field
The application relates to the technical field of software development, in particular to a software development data statistical method, a software development data statistical device, computer equipment and a medium.
Background
In the software development process, the statistical analysis and measurement of the whole development period of the project by adopting digitization is a scientific and objective management mode for the project. Software development is generally divided into four phases: in the actual software development process, a manual statistics mode is adopted, missing statistics or error statistics is easily caused, the optimization of the project is influenced, different responsibility main bodies exist in different project stages, data splitting of each stage of the project is caused, the statistical calibers are inconsistent, the responsibility main bodies in each project stage lack global cognition on the project, and the improvement of the development efficiency of the project and the improvement and optimization of the project are not facilitated.
Disclosure of Invention
In view of this, embodiments of the present application provide a method, an apparatus, a computer device, and a medium for statistical data of software development, which can record and correct statistical data of each stage of software development in time, and are beneficial to accelerating an optimization process for improving a project, thereby improving software development efficiency.
In a first aspect, an embodiment of the present application provides a statistical method for software development data, including:
in a software development requirement stage, acquiring a software development requirement, and counting the requirement quantity of the software development requirement;
in a development stage of software development, generating a development result according to each software development requirement, and counting the development amount of the development results; if the comparison result of the research and development amount and the demand amount does not meet the first requirement, restarting the research and development stage of the software development; if the comparison result of the research and development amount and the demand amount meets a first requirement, entering a testing stage of the software development;
in the testing stage of software development, testing each research and development result and determining the demand defect amount caused by the software development demand; if the demand defect quantity does not meet the second requirement, restarting the demand phase of the software development; if the demand defect quantity meets a second requirement, forming target software by each research and development result, and entering a delivery stage of software development;
in the delivery stage of software development, acquiring the online defect amount of the target software after online; if the online defect amount does not meet a third requirement, informing the software development test stage; and if the online defect amount meets a third requirement, completing the development of the target software.
In a possible implementation manner, each research and development result is tested, and the requirement defect amount caused by the software development requirement is determined; if the demand defect quantity does not meet the second requirement, restarting the demand phase of the software development; if the demand defect amount meets a second requirement, forming target software by each research and development result, and entering a delivery stage of software development, wherein the delivery stage comprises the following steps:
testing each research and development result to obtain a test result of each research and development result;
determining the test result with the defects from the test results, and counting the total defect amount of the test result with the defects;
screening out requirement defects caused by the software development requirement from the test results with the defects, and counting the requirement defect quantity of the requirement defects caused by the software development requirement;
calculating a ratio of the required defect amount to the total defect amount;
restarting the requirement stage of the software development if the ratio of the requirement defect amount to the total defect amount does not meet a second requirement; and if the ratio of the required defect amount to the total defect amount meets a second requirement, entering a development stage of the software development to generate a new development result, forming target software by the new development result, and entering a delivery stage of the software development.
In a possible implementation manner, the on-line defect amount after the target software is on-line is obtained; if the online defect amount does not meet the third requirement, informing the software development testing stage, including:
acquiring the online defect amount of the target software after online, and calculating the ratio of the online defect amount to the total defect amount based on the total defect amount;
and if the ratio of the on-line defect amount to the total defect amount does not meet a third requirement, notifying a test stage of the software development to prompt a worker in the test stage to improve a test case in the test stage of the next software development.
In one possible implementation, the total number of defects is the sum of the number of defects caused by demand defects, code defects, interface defects, and unprocessed exceptions.
In one possible embodiment, the demand defect amount is a sum of the number of defects due to the demand alteration and the number of defects due to the demand description being unclear.
In a second aspect, an embodiment of the present application provides a software development data statistics apparatus, including:
the requirement module is used for acquiring software development requirements at a requirement stage of software development and counting the demand quantity of the software development requirements;
the development module is used for generating development results according to each software development requirement in the development stage of software development and counting the development amount of the development results; if the comparison result of the research and development amount and the demand amount does not meet the first requirement, restarting the research and development stage of the software development; if the comparison result of the research and development amount and the demand amount meets a first requirement, entering a testing stage of the software development;
the testing module is used for testing each research and development result in the testing stage of software development and determining the required defect amount caused by the software development requirement; if the demand defect quantity does not meet the second requirement, restarting the demand phase of the software development; if the required defect amount meets a second requirement, forming target software by each research and development result, and entering a delivery stage of software development;
the delivery module is used for acquiring the online defect amount of the target software after the target software is online in the delivery stage of software development; if the online defect amount does not meet a third requirement, informing the software development test stage; and if the online defect amount meets a third requirement, completing the development of the target software.
In one possible embodiment, the test module includes:
the test unit is used for testing each research and development result to obtain the test result of each research and development result;
the first statistical unit is used for determining the test result with the defects from the test results and counting the total defect quantity of the test result with the defects;
the second statistical unit screens out the requirement defects caused by the software development requirements from the test results with the defects, and counts the requirement defect amount of the requirement defects caused by the software development requirements;
a first calculation unit configured to calculate a ratio of the required defect amount to the total defect amount;
a first determining unit, configured to restart a demand phase of the software development if a ratio of the demand defect amount to the total defect amount does not meet a second requirement; and if the ratio of the required defect amount to the total defect amount meets a second requirement, entering a development stage of the software development to generate a new development result, forming target software by the new development result, and entering a delivery stage of the software development.
In one possible embodiment, the delivery module includes:
a second calculating unit, configured to obtain an online defect amount after the target software is online, and calculate a ratio between the online defect amount and the total defect amount based on the total defect amount;
and the second determining unit is used for notifying the testing stage of the software development if the ratio of the on-line defect quantity to the total defect quantity does not meet a third requirement so as to prompt the testing stage staff to improve the test case at the testing stage of the next software development.
In a third aspect, an embodiment of the present application provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the steps of the software development data statistical method according to any one of the first aspect when executing the computer program.
In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to perform the steps of the software development data statistical method according to any one of the first aspect.
According to the software development data statistical method provided by the embodiment of the application, the demand of the software development requirement is counted according to the software development requirement, a research and development result is generated according to the software development requirement, the research and development amount of the research and development result is counted, the research and development amount is compared with the demand in order to measure the completion rate of the software development requirement in the research and development stage, if the comparison result does not meet the first requirement, the research and development stage of the software development is restarted, if the comparison result meets the first requirement, the test stage is started, each research and development result is tested in the test stage, the demand defect amount caused by the software development requirement is determined, in order to measure the accuracy of the proposed software development requirement, the proportion of the demand defect amount to the total defect amount is judged, if the demand defect amount does not meet the second requirement, the demand stage is restarted, target software is formed by each research and development result and is started in the delivery stage of the software development, in the delivery stage, the online defect amount after the target software is obtained in order to measure the working effectiveness of the test stage, the on-line defect amount is judged, and the ratio of the on the software development line is notified in the third test stage, if the on-line defect amount does not meet the requirement; and if the online defect amount meets a third requirement, completing the development of the target software.
According to the data statistical method for software development, relevant responsible persons can acquire data of each stage in time, and when the data do not meet requirements, the data return to the target stage in time so that workers can correct the data in time, improvement and optimization processes of projects can be accelerated, and accordingly software development efficiency is improved.
In order to make the aforementioned objects, features and advantages of the present application comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic flowchart of a statistical method for software development data according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart of a method for restarting a software development in a demand phase according to an embodiment of the present disclosure;
fig. 3 is a schematic flowchart of a method for restarting a test phase of software development according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a software development data statistics apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.
In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict.
The embodiment of the application provides a software development data statistical method, as shown in fig. 1, comprising the following steps:
s101, acquiring a software development requirement at a software development requirement stage, and counting the requirement quantity of the software development requirement;
s102, in a development stage of software development, generating a development result according to each software development requirement, and counting the development amount of the development results; if the comparison result of the research and development amount and the demand amount does not meet the first requirement, restarting the research and development stage of the software development; if the comparison result of the research and development amount and the demand amount meets a first requirement, entering a testing stage of the software development;
s103, testing each research and development result in a testing stage of software development, and determining the quantity of required defects caused by the software development requirement; if the demand defect quantity does not meet a second requirement, restarting the demand phase of the software development; if the required defect amount meets a second requirement, forming target software by each research and development result, and entering a delivery stage of software development;
s104, acquiring the online defect amount of the target software after online in the delivery stage of software development; if the online defect amount does not meet the third requirement, informing the software development test stage; and if the online defect amount meets a third requirement, completing the development of the target software.
The above exemplary steps of the embodiments of the present application will be described below.
In step S101, in a requirement phase of software development, a software development requirement is obtained, and a demand amount of the software development requirement is counted.
In some embodiments, the software development requirement may be a set of requirements to be developed, and the requirement amount is the number of requirements to be developed.
In step S102, in a development stage of software development, generating a development result according to each software development requirement, and counting a development amount of the development result; if the comparison result of the research and development amount and the demand amount does not meet the first requirement, restarting the research and development stage of the software development; and if the comparison result of the research and development amount and the demand amount meets a first requirement, entering a testing stage of the software development.
In some embodiments, the comparison result of the development amount and the demand amount is an important index for measuring whether the software development requirement is completed in time.
As an example, if the comparison result between the research and development amount and the demand amount does not meet the first requirement, for example, the research and development amount accounts for less than 90% of the demand amount, the research and development stage of software development is restarted, and research and development personnel are required to perform research and development again to make the research and development amount meet the requirement.
In step S103, in a test stage of software development, each research and development result is tested, and a demand defect amount caused by the software development demand is determined; if the demand defect quantity does not meet the second requirement, restarting the demand phase of the software development; and if the required defect amount meets a second requirement, forming target software by each research and development result, and entering a delivery stage of software development.
In some embodiments, the required defect amount is an index for determining whether the requirement proposed in the requirement stage is clear and complete, and whether the required defect amount meets the second requirement is determined on the basis of the total defect amount, that is, the ratio of the required defect amount to the total defect amount is determined.
For example, if the required defect amount accounts for more than 10% of the total defect amount, the required defect amount is considered to be not in accordance with the second requirement, the required stage is restarted to correct the requirement, and the subsequent development is performed.
In some embodiments, the total defect amount is obtained by a smoking test, the total defect amount and the test throughput are counted in the test stage, and a smoking passing rate index is obtained by a ratio of the test throughput and the total defect amount, and the smoking passing rate index is used for measuring whether research and development are required to complete development with high quality.
In some embodiments, the number of developers is counted in the testing stage, and a development defect density index is obtained by a ratio of the total defect amount to the number of developers, so as to measure the development capability of the developers, and the index needs to be reduced by improving the code capability and quality awareness of the developers.
In some embodiments, the number of cases is counted during the testing stage, that is, the number of test cases used during the testing process, and the hit rate index of the defect cases is obtained by the ratio of the total defect amount to the number of cases, so as to measure whether the test cases compiled during the testing work are efficient.
For example, if 100 test cases are written, the number of defects is not found, which indicates that the code development result is high in quality, or the quality of the test cases is poor, and defects cannot be detected.
In some embodiments, in the testing stage, the severity levels of the software are counted into a first level and a second level, and a level defect index is obtained by the ratio of the defects of the first level and the second level to the total defect amount, and is an index for measuring the severity of the software development quality problem.
In step S104, in the delivery stage of software development, acquiring the online defect amount of the target software after online; if the online defect amount does not meet a third requirement, informing the software development test stage; and if the online defect amount meets a third requirement, completing the development of the target software.
In some embodiments, the on-line defect amount is an index for measuring the effectiveness of the test work in the test stage, and the determination of whether the on-line defect amount meets the third requirement is based on the total required defect amount, and the ratio of the on-line defect amount to the total defect amount is determined.
As an example, if the on-line defect amount accounts for more than 5% of the total defect amount, the on-line defect amount is considered to be not in accordance with the third requirement, and the test phase needs to be restarted for testing.
In some embodiments, the capital loss caused by the online accident, namely the online accident capital loss index, is counted in the delivery stage, and the index is used for measuring and judging the online accident severity level.
In some embodiments, as shown in fig. 2, step S103 includes the following steps:
s201, testing each research and development result to obtain the test result of each research and development result.
S202, determining the test result with the defects from the test results, and counting the total defect amount of the test result with the defects.
In some embodiments, the total defect count is the sum of the number of demand defects, code defects, interface defects, and defects caused by unprocessed exceptions; the total defect amount may be derived from a smoking test.
S203, screening out requirement defects caused by the software development requirement from the test results with the defects, and counting the requirement defect quantity of the requirement defects caused by the software development requirement.
In some embodiments, the demand defect amount is a sum of a defect amount due to the demand alteration and a defect amount due to the demand unclear.
For example, if only WeChat login is required to be supported originally, and WeChat and Paibao login are required to be supported during acceptance check, the requirement is changed.
And S204, calculating the ratio of the required defect amount to the total defect amount.
S205, if the ratio of the required defect amount to the total defect amount does not meet a second requirement, restarting the required stage of the software development; and if the ratio of the required defect amount to the total defect amount meets a second requirement, entering a development stage of the software development to generate a new development result, forming target software by the new development result, and entering a delivery stage of the software development.
In some embodiments, when the ratio of the required defect amount to the total defect amount meets a second requirement, entering a development stage of software development, generating a new development result according to the total defect amount, forming target software from the new development result, and entering a delivery stage of the software development; and testing the new research and development results again in the testing stage according to the new research and development results until the total defect amount meets the requirement to obtain the final research and development results, forming the target software by the final research and development results, and entering the delivery stage of software development.
In some embodiments, as shown in fig. 3, step S104 includes the following steps:
s301, acquiring the online defect amount of the target software after online, and calculating the ratio of the online defect amount to the total defect amount based on the total defect amount.
In some embodiments, if the ratio of the on-line defect amount to the total defect amount is greater than 0.05, the on-line defect amount is considered to be not in compliance with the third requirement.
And S302, if the ratio of the on-line defect amount to the total defect amount does not meet a third requirement, informing a testing stage of the software development to prompt a worker in the testing stage to improve a test case in the testing stage of the next software development.
In some embodiments, a defect escape rate index is obtained by a ratio of the on-line defect amount to the total defect amount, if the defect escape rate index does not meet a third requirement, if the defect escape rate is greater than 5%, it indicates that the defect of the on-line defect amount is not tested in the test work, a test stage of software development is notified, a worker in the test stage is prompted to improve a test case in the test stage of the next software development, and the defect escape rate index is an index for measuring the effectiveness of the test work.
In summary, the embodiments of the present application have the following beneficial effects:
the software development data statistical method comprises the steps of counting the demand of software development requirements according to the software development requirements, generating research and development results according to the software development requirements, counting the research and development amounts of research and development results, comparing the research and development amounts with the demand in order to measure the completion rate of the software development requirements in the research and development stages, restarting the research and development stages of the software development if the comparison results do not meet the first requirements, entering a test stage of the software development if the comparison results meet the first requirements, testing each research and development result in the test stage to determine the demand defect amount caused by the software development requirements, judging the proportion of the demand defect amount to the total defect amount in order to measure the accuracy of the proposed software development requirements, restarting the demand stage if the demand defect amount does not meet the second requirements, forming target software by each research and development result, entering a delivery stage of the software development, acquiring the online defect amount of the target software after the online in the delivery stage of the software development, judging the proportion of the online defect amount to the total defect amount in order to measure the effectiveness of the work in the test stage, and notifying the third test result that the online defect amount does not meet the test requirements; and if the online defect amount meets the third requirement, the target software development is completed, and the software development process enables related responsible persons to obtain the data of each stage in time and returns to the target stage in time to correct the data in time when the data does not meet the requirement, so that the improvement and optimization process of the project is accelerated, and the development efficiency of the software is improved.
Based on the same inventive concept, the embodiment of the present application further provides a software development data statistics apparatus corresponding to the software development data statistics method in the first embodiment, and since the principle of the apparatus in the embodiment of the present application for solving the problem is similar to the software development data statistics method, the implementation of the apparatus can refer to the implementation of the method, and repeated details are not repeated.
As shown in fig. 4, fig. 4 is a schematic structural diagram of a software development data statistics apparatus provided in the present application. The software development data statistic device comprises:
the requirement module 401 is used for acquiring a software development requirement at a requirement stage of software development and counting the requirement amount of the software development requirement;
the development module 402 is configured to generate a development result according to each software development requirement in a development stage of software development, and count a development amount of the development result; if the comparison result of the research and development amount and the demand amount does not meet the first requirement, restarting the research and development stage of the software development; if the comparison result of the research and development amount and the demand amount meets a first requirement, entering a testing stage of the software development;
the test module 403 is configured to test each research and development result in a test stage of software development, and determine a demand defect amount caused by the software development demand; if the demand defect quantity does not meet the second requirement, restarting the demand phase of the software development; if the demand defect quantity meets a second requirement, forming target software by each research and development result, and entering a delivery stage of software development;
a delivery module 404, configured to obtain, at a delivery stage of software development, an online defect amount after the target software is online; if the online defect amount does not meet the third requirement, informing the software development test stage; and if the online defect amount meets a third requirement, completing the development of the target software.
It should be understood by those skilled in the art that the implementation functions of the modules in the software development data statistics apparatus shown in fig. 4 can be understood by referring to the related description of the software development data statistics method. The functions of the units in the software development data statistics apparatus shown in fig. 4 may be implemented by a program running on a processor, or may be implemented by specific logic circuits.
In one possible implementation, the test module 403 includes:
the test unit is used for testing each research and development result to obtain the test result of each research and development result;
the first statistical unit is used for determining the test result with the defects from the test results and counting the total defect amount of the test result with the defects;
the second statistical unit is used for screening out the requirement defects caused by the software development requirement from the test results with the defects and counting the requirement defect quantity of the requirement defects caused by the software development requirement;
a first calculation unit configured to calculate a ratio of the required defect amount to the total defect amount;
a first determining unit, configured to restart a demand phase of the software development if a ratio of the demand defect amount to the total defect amount does not meet a second requirement; and if the ratio of the required defect amount to the total defect amount meets a second requirement, entering a development stage of the software development to generate a new development result, forming target software by the new development result, and entering a delivery stage of the software development.
In one possible implementation, the delivery module 404 includes:
the second calculating unit is used for acquiring the online defect amount after the target software is online and calculating the ratio of the online defect amount to the total defect amount based on the total defect amount;
and the second determining unit is used for notifying the testing stage of the software development if the ratio of the on-line defect quantity to the total defect quantity does not meet a third requirement so as to prompt the testing stage staff to improve the test case at the testing stage of the next software development.
In one possible implementation, the total number of defects is the sum of the number of defects caused by demand defects, code defects, interface defects, and unprocessed exceptions.
In one possible embodiment, the demand defect amount is a sum of a number of defects due to the demand alteration and a number of defects due to the demand description being unclear.
The software development data statistical device is used for counting the quantity of demand of software development requirements according to the software development requirements, generating a research and development result according to the software development requirements, counting the quantity of research and development results, comparing the quantity of research and development with the quantity of demand in order to measure the completion rate of the software development requirements in the research and development stage, restarting the research and development stage of the software development if the comparison result does not meet the first requirement, entering a test stage of the software development, testing each research and development result in the test stage to determine the quantity of demand defects caused by the software development requirements, judging the proportion of the quantity of demand defects to the total quantity of defects in order to measure the accuracy of the proposed software development requirements, restarting the demand stage if the quantity of demand defects does not meet the second requirement, forming target software by each research and development result and entering a delivery stage of the software development, acquiring the quantity of on-line defects of the target software after the on-line in the delivery stage of the software development, judging the proportion of the quantity of on-line defects to the total quantity of defects in order to measure the working effectiveness of the test stage, and notifying the quantity of the on-line if the third stage does not meet the test requirement; and if the online defect amount meets the third requirement, the target software development is completed, and the software development process enables related responsible persons to obtain the data of each stage in time and returns to the target stage in time to correct the data in time when the data does not meet the requirement, so that the improvement and optimization process of the project is accelerated, and the development efficiency of the software is improved.
Corresponding to the statistical method for software development data in fig. 1, an embodiment of the present application further provides a computer device 500, as shown in fig. 5, the device includes a memory 501, a processor 502, and a computer program stored on the memory 501 and capable of running on the processor 502, where the processor 502 implements the statistical method for software development data when executing the computer program.
Specifically, the memory 501 and the processor 502 can be general memories and processors, which are not specifically limited herein, and when the processor 502 runs a computer program stored in the memory 501, the software development data statistical method can be executed, thereby solving the problems that in the prior art, data in each stage is split, and cannot be timely fed back to a target stage for correction and optimization according to data which does not meet requirements, which is not favorable for software development efficiency.
Corresponding to the software development data statistical method in fig. 1, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the computer program performs the steps of the software development data statistical method.
Specifically, the storage medium can be a general storage medium, such as a mobile disk, a hard disk and the like, when a computer program on the storage medium is operated, the software development data statistical method can be executed, the problems that data in each stage is split, data which do not meet requirements cannot be timely fed back to a target stage for correction and optimization and software development efficiency is not good in the prior art are solved, relevant responsible persons can timely acquire the data in each stage, and when the data do not meet the requirements, the data can timely return to the target stage to enable workers to timely correct the data, improvement and optimization processes of projects can be accelerated, and therefore software development efficiency is improved.
In the embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other ways. The above-described apparatus embodiments are merely illustrative, and for example, the division of the units into only one type of logical function may be implemented in other ways, and for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments provided in the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions may be stored in a computer-readable storage medium if they are implemented in the form of software functional units and sold or used as separate products. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, and various media capable of storing program codes.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined or explained in subsequent figures, and moreover, the terms "first," "second," "third," etc. are used merely to distinguish one description from another, and are not to be construed as indicating or implying relative importance.
It should be noted that the term "comprising" as used in the embodiments of the present application is intended to indicate the presence of the features as stated hereinafter, but does not exclude the addition of further features.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the application and is not intended to be limiting of the application.
Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present application, and are used for illustrating the technical solutions of the present application, but not limiting the same, and the scope of the present application is not limited thereto, and although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: those skilled in the art can still make modifications or changes to the embodiments described in the foregoing embodiments, or make equivalent substitutions for some features, within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present application. Are intended to be covered by the scope of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A software development data statistical method is characterized by comprising the following steps:
in a software development requirement stage, acquiring a software development requirement, and counting the demand of the software development requirement;
in a development stage of software development, generating a development result according to each software development requirement, and counting the development amount of the development results; if the comparison result of the research and development amount and the demand amount does not meet the first requirement, restarting the research and development stage of the software development; if the comparison result of the research and development amount and the demand amount meets a first requirement, entering a testing stage of the software development;
in the testing stage of software development, testing each research and development result, and determining the quantity of demand defects caused by the software development demand; if the demand defect quantity does not meet the second requirement, restarting the demand phase of the software development; if the required defect amount meets a second requirement, forming target software by each research and development result, and entering a delivery stage of software development;
in the delivery stage of software development, acquiring the online defect amount of the target software after online; if the online defect amount does not meet a third requirement, informing the software development test stage; and if the online defect amount meets a third requirement, completing the development of the target software.
2. The statistical method of software development data according to claim 1, wherein the testing is performed on each development result and a demand defect amount caused by the software development demand is determined; if the demand defect quantity does not meet a second requirement, restarting the demand phase of the software development; if the demand defect amount meets a second requirement, forming target software by each research and development result, and entering a delivery stage of software development, wherein the delivery stage comprises the following steps:
testing each research and development result to obtain a test result of each research and development result;
determining the test result with the defects from the test results, and counting the total defect amount of the test result with the defects;
screening out requirement defects caused by the software development requirement from the test results with the defects, and counting the requirement defect quantity of the requirement defects caused by the software development requirement;
calculating a ratio of the required defect amount to the total defect amount;
restarting the requirement stage of the software development if the ratio of the requirement defect amount to the total defect amount does not meet a second requirement; and if the ratio of the required defect amount to the total defect amount meets a second requirement, entering a development stage of the software development to generate a new development result, forming target software by the new development result, and entering a delivery stage of the software development.
3. The software development data statistical method according to claim 2, wherein the on-line defect amount after the target software is on-line is obtained; if the online defect amount does not meet the third requirement, notifying the testing stage of the software development, wherein the testing stage comprises the following steps:
acquiring the online defect amount of the target software after online, and calculating the ratio of the online defect amount to the total defect amount based on the total defect amount;
and if the ratio of the on-line defect amount to the total defect amount does not meet a third requirement, notifying a test stage of the software development to prompt a worker in the test stage to improve a test case in the test stage of the next software development.
4. The software development data statistical method of claim 2, wherein the total defect amount is a sum of a number of defects caused by a demand defect, a code defect, an interface defect, and an unprocessed exception.
5. The software development data statistical method according to claim 1, wherein the demand defect amount is a sum of a defect amount due to the demand alteration and a defect amount due to the demand description being unclear.
6. A software development data statistics apparatus, comprising:
the requirement module is used for acquiring software development requirements at a requirement stage of software development and counting the demand quantity of the software development requirements;
the development module is used for generating development results according to each software development requirement in the development stage of software development and counting the development amount of the development results; if the comparison result of the research and development amount and the demand amount does not meet the first requirement, restarting the research and development stage of the software development; if the comparison result of the research and development amount and the demand amount meets a first requirement, entering a testing stage of the software development;
the testing module is used for testing each research and development result in the testing stage of software development and determining the required defect amount caused by the software development requirement; if the demand defect quantity does not meet a second requirement, restarting the demand phase of the software development; if the demand defect quantity meets a second requirement, forming target software by each research and development result, and entering a delivery stage of software development;
the delivery module is used for acquiring the online defect amount of the target software after the target software is online in the delivery stage of software development; if the online defect amount does not meet the third requirement, informing the software development test stage; and if the online defect amount meets a third requirement, completing the development of the target software.
7. The software development data statistics apparatus of claim 6, wherein the test module comprises:
the test unit is used for testing each research and development result to obtain the test result of each research and development result;
the first statistical unit is used for determining the test result with the defects from the test results and counting the total defect quantity of the test result with the defects;
the second statistical unit screens out the requirement defects caused by the software development requirements from the test results with the defects, and counts the requirement defect amount of the requirement defects caused by the software development requirements;
a first calculation unit configured to calculate a ratio of the required defect amount to the total defect amount;
a first determining unit, configured to restart a demand phase of the software development if a ratio of the demand defect amount to the total defect amount does not meet a second requirement; and if the ratio of the required defect amount to the total defect amount meets a second requirement, entering a development stage of the software development to generate a new development result, forming target software by the new development result, and entering a delivery stage of the software development.
8. The software development data statistics apparatus of claim 7, wherein the delivery module comprises:
the second calculating unit is used for acquiring the online defect amount after the target software is online and calculating the ratio of the online defect amount to the total defect amount based on the total defect amount;
and the second determining unit is used for notifying the testing stage of the software development if the ratio of the on-line defect quantity to the total defect quantity does not meet a third requirement so as to prompt the testing stage staff to improve the test case at the testing stage of the next software development.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of the preceding claims 1-5 are implemented when the computer program is executed by the processor.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method according to any one of the claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211244880.8A CN115543261A (en) | 2022-10-12 | 2022-10-12 | Software development data statistical method, device, computer equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211244880.8A CN115543261A (en) | 2022-10-12 | 2022-10-12 | Software development data statistical method, device, computer equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115543261A true CN115543261A (en) | 2022-12-30 |
Family
ID=84733864
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211244880.8A Pending CN115543261A (en) | 2022-10-12 | 2022-10-12 | Software development data statistical method, device, computer equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115543261A (en) |
-
2022
- 2022-10-12 CN CN202211244880.8A patent/CN115543261A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107885656B (en) | Automatic product algorithm testing method and application server | |
| US20140033174A1 (en) | Software bug predicting | |
| CN110096430B (en) | Third party SDK access test method, device, terminal and storage medium | |
| CN110046086B (en) | Expected data generation method and device for test and electronic equipment | |
| US10382292B2 (en) | Quality assessment and decision recommendation for continuous deployment of cloud infrastructure components | |
| CN110888813A (en) | Project scheduling management method, device, equipment and storage medium | |
| CN112363911A (en) | Software test defect analysis method and device | |
| JP2019175273A (en) | Quality evaluation method and quality evaluation | |
| CN111506455A (en) | Checking method and device for service release result | |
| CN115543261A (en) | Software development data statistical method, device, computer equipment and medium | |
| CN110765005A (en) | Software reliability evaluation method and device | |
| CN113704871B (en) | Method and device for determining wheel bending fatigue, terminal equipment and medium | |
| CN107423140B (en) | Return code identification method and device | |
| CN115203025A (en) | Test defect analysis method and device | |
| CN115408292A (en) | Method, device, equipment and medium for evaluating software testing process | |
| CN115185833A (en) | Abnormal code processing method and device, computer equipment and storage medium | |
| CN111124918B (en) | Test data prediction method and device and processing equipment | |
| CN110008098B (en) | Method and device for evaluating operation condition of nodes in business process | |
| CN113821443A (en) | Application program function detection method, device, equipment and storage medium | |
| CN113342676A (en) | Software test evaluation method and device, computing equipment and storage medium | |
| CN109815109B (en) | Data mode change detection method, device, equipment and readable storage medium | |
| CN111310989A (en) | Method and device for predicting part machining success rate and readable storage medium | |
| CN113157583A (en) | Test method, device and equipment | |
| CN112148621A (en) | Test method and device and electronic equipment | |
| CN116561018B (en) | Service system counting method, device, terminal equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |