CN113094095B - Agile development progress determining method and device - Google Patents
Agile development progress determining method and device Download PDFInfo
- Publication number
- CN113094095B CN113094095B CN202110325179.8A CN202110325179A CN113094095B CN 113094095 B CN113094095 B CN 113094095B CN 202110325179 A CN202110325179 A CN 202110325179A CN 113094095 B CN113094095 B CN 113094095B
- Authority
- CN
- China
- Prior art keywords
- target
- development
- identification information
- duration
- progress
- 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.)
- Active
Links
- 238000011161 development Methods 0.000 title claims abstract description 265
- 238000000034 method Methods 0.000 title claims abstract description 56
- 230000007547 defect Effects 0.000 claims description 195
- 238000012360 testing method Methods 0.000 claims description 140
- 238000010586 diagram Methods 0.000 claims description 41
- 238000012545 processing Methods 0.000 claims description 14
- 238000004590 computer program Methods 0.000 description 12
- 238000004891 communication Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 8
- 230000006870 function Effects 0.000 description 7
- 230000036541 health Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/77—Software metrics
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
- G06Q10/063114—Status monitoring or status determination for a person or group
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Theoretical Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
According to the method and the device, the predicted first total time length for completing target iteration and the first time length for executing the target iteration are obtained, the development progress of the target iteration is determined according to the first total time length and the first time length, the predicted second total time length for completing target demand corresponding to the target iteration and the second time length for executing the target demand are obtained, the sub-development progress of the target demand is determined according to the second total time length and the second time length, the target iteration, the development progress, the target demand and the sub-development progress are displayed, the development progress of the agile development is displayed, supervision on the development progress of the agile development is well achieved, and the use feeling of a user is improved.
Description
Technical Field
The application relates to the technical field of data processing, in particular to a method and a device for determining agile development progress.
Background
Along with the development of technology, a plurality of kinds of open source software which can be used for agile development exist, when agile development is carried out, a plurality of open source software are needed to support the agile development process, such as JIRA, confluecne, testlink, sonarQube, gitlab, and the open source software has different functions in the agile development process, and the open source software has some statistical functions and can record the corresponding working conditions. For example, JIRA can be used for managing project development tasks and acquiring task states and progress; confluence is taken as a knowledge base and an organization material management tool, and can be taken as a agile development requirement document to manage; testlink manages project use cases; the SonarQube performs static scanning on the code; gitlab management code, etc.
However, these open source software can only record the respective working conditions, and cannot reflect the development progress of agile development, so that the development progress of agile development cannot be well supervised.
Disclosure of Invention
The application provides a method, a device, equipment and a medium for determining agile development progress, which are used for solving the problems that the development progress of agile development cannot be reflected, the agile development progress cannot be supervised, and user experience is affected in the prior art.
In a first aspect, the present application provides a method for determining agile development progress, the method including:
receiving progress information of agile development sent by JIRA, wherein the progress information comprises target iteration where current agile development is located, predicted first total duration for completing the target iteration, first duration for executing the target iteration, target requirement corresponding to the target iteration, predicted second total duration for completing the target requirement and second duration for executing the target requirement;
determining the development progress of the target iteration according to the first total duration and the first duration, and determining the sub-development progress of the target requirement according to the second total duration and the second duration;
And displaying the target iteration, the development progress, the target requirement and the sub development progress.
In a second aspect, the present application further provides an agile development progress determining device, the device including:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving progress information of agile development sent by JIRA, wherein the progress information comprises target iteration where current agile development is located, predicted first total duration for completing the target iteration, first duration for executing the target iteration, target requirement corresponding to the target iteration, predicted second total duration for completing the target requirement and second duration for executing the target requirement;
the determining module is used for determining the development progress of the target iteration according to the first total duration and the first duration, and determining the sub-development progress of the target requirement according to the second total duration and the second duration;
and the display module is used for displaying the target iteration, the development progress, the target requirement and the sub development progress.
In a third aspect, the present application further provides an electronic device, where the electronic device includes at least a processor and a memory, where the processor is configured to implement the steps of determining the agile development progress described in any of the above when executing a computer program stored in the memory.
In a fourth aspect, the present application also provides a computer readable storage medium storing a computer program which when executed by a processor performs the steps of agile development progress determination of any of the above.
Receiving the progress information of the agile development sent by the JIRA, wherein the progress information comprises a target iteration where the current agile development is located, a predicted first total duration for completing the target iteration, a first duration for executing the target iteration, a target requirement corresponding to the target iteration, a predicted second total duration for completing the target requirement and a second duration for executing the target requirement; determining the development progress of the target iteration according to the first total duration and the first duration, and determining the sub-development progress of the target requirement according to the second total duration and the second duration; displaying the target iteration, the development progress, the target requirement and the sub-development progress. In the method, the development progress of the target iteration is determined by acquiring the predicted first total time length for completing the target iteration and the first time length for executing the target iteration, according to the first total time length and the first time length, the development progress of the target iteration is determined by acquiring the predicted second total time length for completing the target demand corresponding to the target iteration and the second time length for executing the target demand, and the sub development progress of the target demand is determined according to the second total time length and the second time length, and the target iteration, the development progress, the target demand and the sub development progress are displayed, so that the development progress of agile development is displayed, supervision of the development progress of agile development can be well realized, and the use experience of a user is improved.
Drawings
In order to more clearly illustrate the technical solutions of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a process for determining agile development progress provided in the present application;
FIG. 2 is a schematic diagram showing development progress of agile development provided in the present application;
FIG. 3 is a schematic diagram showing the development progress of a target requirement provided in the present application;
FIG. 4 is a diagram showing the correspondence between target requirements, target sub-requirements, target test cases, and target defects provided in the present application;
FIG. 5a is a schematic illustration of a display of the burnout map for the target iteration provided herein;
FIG. 5b is a schematic illustration of a speed map of agile development provided herein;
FIG. 6 is a schematic diagram of a project development quality report provided in the present application;
FIG. 7 is a schematic diagram of a test management report provided in the present application;
FIG. 8 is a schematic diagram of a pipeline health report provided in the present application;
Fig. 9 is a schematic structural diagram of an agile development progress determining device provided in the present application;
fig. 10 is a schematic structural diagram of an electronic device provided in the present application.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the present application more apparent, the present application will be described in further detail below with reference to the accompanying drawings, wherein it is apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
In order to display development progress of agile development, facilitate subsequent supervision of development progress of agile development, improve user experience, in the application, a predicted first total duration of completing target iteration and a predicted first duration of executing the target iteration are obtained, the development progress of the target iteration is determined according to the first total duration and the first duration, a predicted second total duration of completing target requirement corresponding to the target iteration and a predicted second duration of executing the target requirement are obtained, a sub-development progress of the target requirement is determined according to the second total duration and the second duration, and the target iteration, the development progress, the target requirement and the sub-development progress are displayed.
In order to facilitate understanding of development progress of agile development and improve use experience of users, the application provides a method, a device, equipment and a medium for determining agile development progress.
Fig. 1 is a schematic diagram of a process for determining agile development progress, where the process includes:
s101: and receiving the progress information of the agile development sent by the JIRA, wherein the progress information comprises a target iteration where the current agile development is located, a first total predicted time length for completing the target iteration, a first time length for executing the target iteration, a target requirement corresponding to the target iteration, a second total predicted time length for completing the target requirement and a second time length for executing the target requirement.
The method for determining the agile development progress is applied to electronic equipment, and the electronic equipment can be a mobile phone, a PC (personal computer) and the like. The software for agile development, such as JIRA, testlink, runs in other electronic devices, and may also run in the electronic device for determining the agile development progress.
In the application, the electronic device may receive the progress information of the agile development sent by the JIRA, where the JIRA may communicate with the electronic device in real time, and send the progress information of the agile development to the electronic device in real time, where the progress information includes a target iteration where the current agile development is located, a predicted first total duration required to complete the target iteration, a first duration that has been currently executed for the target iteration, a target requirement corresponding to the target iteration, a predicted second total duration required to complete the target requirement, and a second duration that has been currently executed for the target requirement.
In addition, in the application, the progress information can also include iterations of completed development and iterations waiting for development in the agile development. Specifically, for agile development, multiple iterations are needed to be performed to thoroughly develop a product, the target iteration is the iteration currently performed by the agile development, the completed iteration is the iteration after the development is completed, and the iteration to be developed is the iteration to be developed in the future.
In the present application, if there is a target sub-requirement in the target requirement, the progress information further carries a target sub-requirement corresponding to the target requirement, and the predicted third total duration for completing the target sub-requirement is specific to the third duration currently executed by the target sub-requirement.
S102: and determining the development progress of the target iteration according to the first total duration and the first duration, and determining the sub-development progress of the target requirement according to the second total duration and the second duration.
In the application, after receiving progress information of agile development, determining the development progress of the target iteration according to a first total duration and a first duration carried in the progress information. Specifically, the ratio of the first duration to the first total duration may be determined as the development progress of the target iteration by determining the ratio of the first duration to the first total duration. In the present application, the development progress may be expressed in the form of a percentage, a fraction, or a fraction, etc., and the numerical size of the development progress does not exceed 1.
In the application, after receiving the progress information of agile development, determining the sub-development progress of the target requirement according to the second total duration and the first duration carried in the progress information. Specifically, the ratio of the second duration to the second total duration may be determined as the sub-development progress of the target requirement by determining the ratio of the second duration to the second total duration. In the present application, the expression form of the sub development progress may be a percentage, a fraction, or a fraction, etc., and the numerical size of the sub development progress does not exceed 1.
S103: and displaying the target iteration, the development progress, the target requirement and the sub development progress.
In the application, after the development progress of the target iteration and the sub-development progress of the target requirement are obtained, the target iteration, the development progress, the target requirement and the sub-development progress are displayed. Specifically, in the present application, the target iteration, development progress, target demand, and sub-development progress are displayed on the same page when displayed. Specifically, the target iteration and the development progress may be displayed at adjacent positions to identify that the development progress is the target iteration, and the target demand and the sub development progress may be displayed at adjacent positions to identify that the sub development progress is the target demand.
For example, in the present application, when development progress and sub development progress are displayed, development progress is displayed with a progress bar, a specific value of the development progress is displayed above the progress bar, sub development progress is displayed with another progress bar, and a specific value of the sub development progress is displayed above the progress bar.
In the method, the development progress of the target iteration is determined by acquiring the predicted first total time length for completing the target iteration and the first time length for executing the target iteration, according to the first total time length and the first time length, the development progress of the target iteration is determined by acquiring the second total time length of the target requirement corresponding to the target iteration and the second time length for executing the target requirement, and according to the second total time length and the second time length, the sub development progress of the target requirement is determined, the target iteration, the development progress, the target requirement and the sub development progress are displayed, the development progress of agile development is displayed, the supervision of the development progress of agile development can be well realized, and the use experience of a user is improved.
In order to achieve display of development progress of agile development and improve user experience, in the present application, on the basis of the foregoing embodiment, determining the development progress of the target iteration according to the first total duration and the first duration includes:
And determining a first ratio of the first duration to the first total duration as the development progress of the target iteration.
In the present application, when determining the development progress of the target iteration according to the first total duration and the first duration, the ratio of the first duration to the first total duration may be determined as the development progress of the target iteration by determining the ratio of the first duration to the first total duration.
Specifically, in the present application, the first total duration is a predicted total duration for completing a target iteration, the first duration is a duration that has been executed for the target iteration, and a development progress of the target iteration is determined, that is, a proportion of the first duration that has executed the target iteration in the first total duration is determined. Thus, in determining the development progress, the ratio may be determined as the development progress of the target iteration by determining a first ratio of the first duration to a first total duration. In the present application, the development progress may be expressed in the form of a percentage, a fraction, or a fraction, etc., and the numerical size of the development progress does not exceed 1.
For example, if the first total duration of the target iteration is 100 hours and the first duration of the target iteration that has been performed is 25 hours, then the development progress of the target iteration is 25%.
In order to achieve display of development progress of agile development and improve use experience of a user, on the basis of the foregoing embodiments, in this application, determining the sub-development progress of the target requirement according to the second total duration and the second duration includes:
and determining a second ratio of the second time length to the second total time length as a sub-development task of the target requirement.
In the present application, in determining the sub-development progress of the target requirement according to the second total duration and the first duration carried in the progress information, the ratio of the second duration to the second total duration may be determined as the sub-development progress of the target requirement by determining the ratio of the second duration to the second total duration.
Specifically, in the present application, the second total duration is a predicted total duration for completing the target demand, where the second duration is a duration that has been executed for the target demand, and the development progress of the target demand is determined, that is, a proportion of the second duration that has executed the target demand in the second total duration is determined. Thus, in determining the sub-development progress, the second ratio may be determined as the sub-development progress of the target demand by determining a second ratio of the second time period to a second total time period. The sub development progress may be expressed in the form of a percentage, a fraction, or a score, etc., and the numerical size of the sub development progress does not exceed 1.
For example, if the second total duration of the target demand is 50 hours and the second duration of the target demand has been executed is 5 hours, the sub-development progress of the target demand is 10%.
Fig. 2 is a schematic display diagram of development progress of agile development provided in the present application, and as shown in fig. 2, when the development progress of agile development is displayed, all iteration processes of a product including completed iterations, currently located target iterations, and iterations to be completed are displayed, and the development progress of each iteration is displayed. For the completed iteration, the development progress is 100%, the development progress of the current target iteration is 42%, and the development progress of the iteration to be completed is 0.
In the application, when receiving the target requirement sent by the JIRA, the type of the target requirement is also received, the type of the target requirement is obtained by the JIRA from the run-tce configuration file, all the received target requirements are counted according to the type, and the number of the target requirements of each type is displayed. In fig. 2, when the target requirement of the target iteration is displayed, if the target iteration has a poetry story (Epic), the Epic is displayed, and the type of the target requirement under the Epic is not displayed; if there is no Epic, the type of target demand is displayed. In the present application, the Epic is a poetry story and is used to record the functions to be implemented in the whole agile development, i.e. the Epic includes all target requirements.
Fig. 3 is a schematic diagram of displaying a sub-development progress of a target requirement provided in the present application, in fig. 3, for each target requirement, the sub-development progress of the target requirement is displayed, and the type of the target requirement belongs to.
In order to achieve display of development progress of agile development and improve use experience of a user, on the basis of the above embodiments, in the present application, the method further includes:
receiving information of a test case and information of a tested defect sent by open source software Testlink, wherein the information of the test case carries second identification information of the test case and first identification information of a requirement corresponding to the test case, and the information of the defect carries third identification information of the test case with the tested defect;
identifying target first identification information which is consistent with target identification information corresponding to the target requirement in the first identification information, and determining that the test case corresponding to the target first identification information is the target test case corresponding to the target requirement;
identifying target third identification information consistent with the second identification information in the third identification information, and determining that the defect corresponding to the target third identification information is the target defect corresponding to the target test case;
And displaying the corresponding relation among the target requirement, the target test case and the target defect.
In this application, each target requirement has one or more test cases corresponding to the target requirement, where the test cases are specifically configured to detect the target requirement after the corresponding target requirement is developed, and when the test cases detect an error, consider that the developed target requirement has an error, and generate a defect to identify that the development of the target requirement has an error. In the application, the process of detecting the target requirement of development by using the test case is performed in open source software Testlink.
In the application, the electronic device also receives information of the test case and information of the tested defect, which are sent by the open source software Testlink installed in other electronic devices, wherein the information of the test case carries second identification information of the test case and first identification information of a requirement corresponding to the test case, and the information of the defect carries third identification information of the test case tested to the defect.
Specifically, after the information of the test case is received, the information of the test case carries second identification information of the test case, and in the application, the second identification information is used for identifying the test case, and each test case corresponds to different second identification information. The information of the test case also carries first identification information of the requirement corresponding to the test case, and in the application, the first identification information is used for identifying the requirement corresponding to the test case, and because a condition that one requirement corresponds to a plurality of test cases possibly exists, the first identification information carried in the information of at least two test cases possibly exists to be the same. After receiving the information of the tested defect, the information of the defect carries third identification information of the test case for testing the defect.
After receiving the information of the test case and the information of the defect, identifying the content in the information of the test case and the information of the defect, and realizing statistics of the agile development flow. In the application, first, a target test case corresponding to a target requirement is identified, namely, target first identification information, which is consistent with target identification information corresponding to the target requirement, in first identification information is identified, and the test case corresponding to the target first identification information is determined to be the target test case corresponding to the target requirement. Specifically, in the application, each requirement corresponds to one piece of identification information, and the identification information corresponding to each requirement is different, and when the target identification information corresponding to the target requirement is consistent with the first identification information of the requirement corresponding to the test case carried in the information of the test case, the requirement corresponding to the test case is determined to be the target requirement, and the test case is the target test case.
After the target test case is determined, identifying target third identification information consistent with the second identification information in the third identification information, and determining the defect corresponding to the target third identification information as the target defect corresponding to the target test case. Specifically, in the application, the identification information corresponding to each test case is unique, and when the second identification information corresponding to the target test case is consistent with the third identification information of the test case corresponding to the defect carried in the defect information, the defect is determined to be the target defect corresponding to the target test case.
In the application, after the target requirement, the target test case and the target defect are determined, the corresponding relation among the target requirement, the target test case and the target defect is displayed on the display interface.
Fig. 4 is a corresponding relationship between a target requirement, a target sub-requirement, a target test case and a target defect provided in the present application, where in fig. 4, the target requirement is "global analysis", and includes three target sub-requirements, namely, a target sub-requirement 1, a target sub-requirement 2 and a target sub-requirement 3, where the target sub-requirement 1 corresponds to one test case.
In order to achieve display of development progress of agile development and improve user experience, based on the above embodiments, in the present application, after receiving information of a test case and information of a tested defect sent by open source software Testlink, the method further includes:
counting the number of unresolved defects in the target iteration, and constructing a burnout diagram of the target iteration according to the number and the time for receiving the information of the defects.
In the application, after the information of the tested defects sent by open source software Testlink is received, determining the number of defects which are not solved in the target iteration according to the information of the defects, and constructing the burnout diagram of the target iteration according to the number and the time for receiving the information of the defects.
Specifically, after the information of the defects is received, determining the number of defects which are not solved in the target iteration, taking the number as an ordinate, determining the time for receiving the information of the defects as an abscissa, determining the coordinates corresponding to the information of the defects, identifying the coordinates with the number of the defects as a y axis and the time as an x axis, and connecting points corresponding to other coordinates recorded before by using broken lines to construct a burnout diagram.
For example, if the number of unresolved defects in the target iteration is 10 and the time is 2021, 3, and 10 days, the coordinates corresponding to the information of the defects are (10, 2021, 3, and 10 days), a point corresponding to the coordinates is found in the coordinate system, and the point is connected with the determined previous point.
In addition, in the present application, open source software Testlink will send defect information in real time.
In order to achieve the display of the development progress of the agile development and improve the use feeling of the user, on the basis of the above embodiments, after receiving the progress information of the agile development sent by the JIRA, in the present application, the method includes:
and constructing the agile development speed diagram according to the first duration and the first total duration carried in the progress information.
In this application, the development speed of the target iteration is also shown for the target iteration, specifically, after receiving the predicted first total duration of completing the target iteration and the first duration of having executed the target iteration, a speed map is constructed. The velocity map may be a histogram, wherein the abscissa of the histogram is an iteration in agile development, and a column with a first total length of time and a column with a first length of time are constructed at positions corresponding to the target iteration.
Furthermore, in this application, other already developed iterations of the agile development may also be shown in the velocity graph.
In the application, after the burnout diagram and the speed diagram are constructed, the burnout diagram and the speed diagram are displayed on the same display page.
Fig. 5a is a schematic diagram showing an burnout diagram of a target iteration provided in the present application, where, as shown in fig. 5a, the ordinate of the burnout diagram is the number of unprocessed problems, that is, the number of unresolved defects in the target iteration, and the abscissa is the working time.
Fig. 5b is a schematic diagram showing a speed chart of agile development provided in the present application, where, as shown in fig. 5b, the ordinate of the speed chart is the working time length, and the abscissa is the iteration.
In order to achieve display of development progress of agile development and improve use experience of a user, in the application, if target third identification information consistent with the second identification information is not identified in the third identification information, the method further includes:
determining that the target test case has no corresponding target defect;
and displaying the corresponding relation between the target requirement and the target test case.
In the application, the defect is recorded when the agile development of the requirement corresponding to the test case is detected and an error is detected by adopting the test case, and when the agile development of the requirement does not have the error, the defect is not marked, so that the target test case may not have the defect tested, that is, in the third identification information, the target third identification information consistent with the second identification information corresponding to the target test case may not be identified.
In the application, if the target third identification information consistent with the second identification information corresponding to the target test case is not identified in the third identification information, determining that the target test case has no corresponding target defect, and displaying the corresponding relation between the target requirement and the target test case on a display interface.
In order to achieve display of development progress of agile development and improve use experience of a user, on the basis of the above embodiments, in the present application, the method further includes:
and receiving and displaying code submission line number information corresponding to each employee sent by the Gitlab.
In the present application, the number of code submission lines per employee, that is, the number of lines per employee's submitted code, is recorded in the Gitlab. In order to display the working condition of each employee, in the application, the electronic device also receives the code submission number information corresponding to each employee sent by the Gitlab, and displays the code submission number information corresponding to each employee on a display interface.
In order to achieve display of development progress of agile development and improve use experience of a user, on the basis of the above embodiments, in the present application, the method further includes:
receiving the number of working days of the month, the number of development tasks completed, the number of defects repaired, the number of repaired defects reopened and the number of defects newly added in the month of the target staff sent by the JIRA;
determining the defect through rate of the target staff according to the repaired defect number and the reopened number;
Determining the number of the day defects of the target staff according to the number of the defects newly increased in the current month and the number of the working days in the current month;
displaying the number of the completed development tasks, the number of the repaired defects which are reopened, the number of the defects which are newly increased in the month, the defect through rate and the number of the day defects.
In this application, the electronic device also receives the number of days of the month, the number of development tasks completed, the number of defects repaired that have been reopened, and the number of defects newly added in the month for the target employee sent by the JIRA.
Before the work of the month begins, the target staff is allocated with a preset number of development tasks, and the number of the completed development tasks is the number of the development tasks completed by the target staff; meanwhile, in the application, the target staff can repair the generated defect and record the repaired defect number of the target staff, when the target staff repair the defect, the test case corresponding to the defect is retested, if the defect is not successfully repaired, the defect is reopened, and at the moment, the repaired defect reopened number is recorded.
In the application, after the number of repaired defects and the number of repaired defects to be reopened are received, the defect through rate of the target staff is determined according to the number of repaired defects and the number of repaired defects to be reopened. Specifically, the number of defects that are not reopened in the repaired defects of the target employee, that is, the number of non-reopened defects, is calculated, wherein the number of non-reopened defects is the difference between the number of repaired defects and the number of reopened defects, the ratio of the number of non-reopened defects to the number of repaired defects is calculated, and the ratio is determined as the defect through rate of the target employee, and generally the defect through rate is a percentage. For example, if the number of repaired defects of the target employee is 10, the number of reopened defects is 4, the number of unreturned defects is 6, the ratio of the number of unreturned defects to the number of repaired defects is 0.6, and the defect through rate of the target employee is 60%.
In the application, after the number of defects newly increased in the month and the working days of the month are received, the number of the day defects of the target staff is determined according to the number of defects newly increased in the month and the working days of the month. Specifically, the ratio of the number of defects newly increased in the month to the working days of the month is calculated, and the ratio is determined as the number of the day defects of the target staff. If the target employee is not configured with the working days of the month, the number of the day defects of the target employee is not calculated. For example, if the number of defects added to the target employee in the month is 5 and the number of days of work in the month is 20, the number of defects in the target employee is 0.25.
In the present application, the number of completed development tasks, the number of repaired defects that are reopened, the number of defects that have been newly added in the present month, the defect through rate, and the number of day defects are also displayed.
Fig. 6 is a schematic display diagram of a project development quality report provided in the present application, where, as shown in fig. 6, the project quality development report includes code statistics, defect statistics and sonarqub, where the code statistics includes code submission line number information corresponding to each employee sent by a Gitlab, and the defect statistics includes the number of completed development tasks, the number of repaired defects reopened, the number of defects newly added in the present month, the defect through rate and the number of day defects of each employee, and the sonarqub is the number of code defects counted by sonarqub.
Fig. 7 is a schematic display diagram of a test management report provided in the present application, where, as shown in fig. 7, the test progress of each target demand is displayed in the test management report, and the test result of the target demand or the target sub-demand is displayed, if the test is successful, a "pass" word is displayed behind the target demand or the target sub-demand, and if the test is failed, a "fail" word is displayed behind the target demand or the target sub-demand, and a bug button is displayed. Further, in the present application, the bug button may be clicked to jump to the JIRA page.
Fig. 8 is a schematic display diagram of a pipeline health report provided in the present application, where, as shown in fig. 8, the pipeline health report includes a pipeline execution state statistics, a resource number, a pending pipeline, an execution failure rate, and an execution record, where the data is directly obtained from confence.
Fig. 9 is a schematic structural diagram of an agile development progress determining device provided in the present application, where the device includes:
a receiving module 901, configured to receive progress information of agile development sent by JIRA, where the progress information includes a target iteration in which a current agile development is located, a predicted first total duration for completing the target iteration, a first duration for having executed the target iteration, a target requirement corresponding to the target iteration, a predicted second total duration for completing the target requirement, and a second duration for having executed the target requirement;
a determining module 902, configured to determine a development progress of the target iteration according to the first total duration and the first duration, and determine a sub-development progress of the target requirement according to the second total duration and the second duration;
the display module 903 is configured to display the target iteration, the development progress, the target requirement, and the sub development progress.
In a possible implementation manner, the determining module 902 is specifically configured to determine a first ratio of the first duration to the first total duration as the development progress of the target iteration.
In a possible implementation manner, the determining module 902 is specifically configured to determine a second ratio of the second duration to the second total duration as the sub-development task of the target requirement.
In a possible implementation manner, the receiving module 901 is further configured to receive information of a test case and information of a tested defect sent by an open source software Testlink, where the information of the test case carries second identification information of the test case and first identification information of a requirement corresponding to the test case, and the information of the defect carries third identification information of the test case that tests the defect;
the determining module 902 is further configured to identify target first identification information, which is consistent with target identification information corresponding to the target requirement, in the first identification information, and determine that a test case corresponding to the target first identification information is a target test case corresponding to the target requirement; identifying target third identification information consistent with the second identification information in the third identification information, and determining that the defect corresponding to the target third identification information is the target defect corresponding to the target test case;
The display module 903 is further configured to display a correspondence among the target requirement, the target test case, and the target defect.
In a possible implementation manner, if no target third identification information consistent with the second identification information is identified in the third identification information, the determining module 902 is further configured to determine that the target test case has no corresponding target defect;
the display module 903 is further configured to display a correspondence between the target requirement and the target test case.
In a possible implementation manner, the receiving module 901 is further configured to receive and display code submission number information corresponding to each employee sent by the Gitlab.
In a possible implementation manner, the receiving module 901 is further configured to receive a number of days of the month of work, a number of completed development tasks, a number of repaired defects that are reopened, and a number of defects that are newly added in the month, which are sent by the JIRA;
the determining module 902 is further configured to determine a defect through rate of the target employee according to the number of repaired defects and the number of reopened defects; determining the number of the day defects of the target staff according to the number of the defects newly increased in the current month and the number of the working days in the current month;
The display module 903 is further configured to display the number of completed development tasks, the number of repaired defects that are reopened, the number of defects that are newly added in the month, the defect through rate, and the number of day defects.
In a possible implementation manner, the determining module 902 is further configured to count the number of unresolved defects in the target iteration, and construct a burnout map of the target iteration according to the number and the time for receiving the information of the defects.
In a possible implementation manner, the determining module 902 is further configured to construct the speed map of agile development according to the first duration and the first total duration carried in the progress information.
Fig. 10 is a schematic structural diagram of an electronic device provided in the present application, and on the basis of the foregoing embodiments, the present application further provides an electronic device, as shown in fig. 10, including: processor 1001, communication interface 1002, memory 1003 and communication bus 1004, wherein processor 1001, communication interface 1002, memory 1003 accomplish the mutual communication through communication bus 1004;
the memory 1003 stores a computer program which, when executed by the processor 1001, causes the processor 1001 to perform the steps of:
Receiving progress information of agile development sent by JIRA, wherein the progress information comprises target iteration where current agile development is located, predicted first total duration for completing the target iteration, first duration for executing the target iteration, target requirement corresponding to the target iteration, predicted second total duration for completing the target requirement and second duration for executing the target requirement;
determining the development progress of the target iteration according to the first total duration and the first duration, and determining the sub-development progress of the target requirement according to the second total duration and the second duration;
and displaying the target iteration, the development progress, the target requirement and the sub development progress.
In one possible implementation manner, the determining the development progress of the target iteration according to the first total duration and the first duration includes:
and determining a first ratio of the first duration to the first total duration as the development progress of the target iteration.
In one possible implementation manner, the determining the sub-development progress of the target requirement according to the second total duration and the second duration includes:
And determining a second ratio of the second time length to the second total time length as a sub-development task of the target requirement.
In one possible embodiment, the method further comprises:
receiving information of a test case and information of a tested defect sent by open source software Testlink, wherein the information of the test case carries second identification information of the test case and first identification information of a requirement corresponding to the test case, and the information of the defect carries third identification information of the test case with the tested defect;
identifying target first identification information which is consistent with target identification information corresponding to the target requirement in the first identification information, and determining that the test case corresponding to the target first identification information is the target test case corresponding to the target requirement;
identifying target third identification information consistent with the second identification information in the third identification information, and determining that the defect corresponding to the target third identification information is the target defect corresponding to the target test case;
and displaying the corresponding relation among the target requirement, the target test case and the target defect.
In one possible embodiment, if no target third identification information consistent with the second identification information is identified in the third identification information, the method further includes:
Determining that the target test case has no corresponding target defect;
and displaying the corresponding relation between the target requirement and the target test case.
In one possible embodiment, the method further comprises:
and receiving and displaying code submission line number information corresponding to each employee sent by the Gitlab.
In one possible embodiment, the method further comprises:
receiving the number of working days of the month, the number of development tasks completed, the number of defects repaired, the number of repaired defects reopened and the number of defects newly added in the month of the target staff sent by the JIRA;
determining the defect through rate of the target staff according to the repaired defect number and the reopened number;
determining the number of the day defects of the target staff according to the number of the defects newly increased in the current month and the number of the working days in the current month;
displaying the number of the completed development tasks, the number of the repaired defects which are reopened, the number of the defects which are newly increased in the month, the defect through rate and the number of the day defects.
In one possible implementation manner, after the receiving the information of the test case and the information of the tested defect sent by the open source software Testlink, the method further includes:
Counting the number of unresolved defects in the target iteration, and constructing a burnout diagram of the target iteration according to the number and the time for receiving the information of the defects.
In one possible implementation, after the receiving the progress information of agile development sent by JIRA, the method further includes:
and constructing the agile development speed diagram according to the first duration and the first total duration carried in the progress information.
Because the principle of solving the problem of the electronic device is similar to that of the agile development progress determining method, implementation of the electronic device can refer to implementation of the method, and repeated parts are omitted.
The communication bus mentioned above for the electronic devices may be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, etc. The communication bus may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus.
The communication interface 1002 is used for communication between the above-described electronic device and other devices.
The Memory may include random access Memory (Random Access Memory, RAM) or may include Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.
The processor may be a general-purpose processor, including a central processing unit, a network processor (Network Processor, NP), etc.; but also digital instruction processors (Digital Signal Processing, DSP), application specific integrated circuits, field programmable gate arrays or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
On the basis of the above embodiments, the present application further provides a computer readable storage medium having stored therein a computer program executable by a processor, which when run on the processor, causes the processor to perform the steps of:
receiving progress information of agile development sent by JIRA, wherein the progress information comprises target iteration where current agile development is located, predicted first total duration for completing the target iteration, first duration for executing the target iteration, target requirement corresponding to the target iteration, predicted second total duration for completing the target requirement and second duration for executing the target requirement;
Determining the development progress of the target iteration according to the first total duration and the first duration, and determining the sub-development progress of the target requirement according to the second total duration and the second duration;
and displaying the target iteration, the development progress, the target requirement and the sub development progress.
In one possible implementation manner, the determining the development progress of the target iteration according to the first total duration and the first duration includes:
and determining a first ratio of the first duration to the first total duration as the development progress of the target iteration.
In one possible implementation manner, the determining the sub-development progress of the target requirement according to the second total duration and the second duration includes:
and determining a second ratio of the second time length to the second total time length as a sub-development task of the target requirement.
In one possible embodiment, the method further comprises:
receiving information of a test case and information of a tested defect sent by open source software Testlink, wherein the information of the test case carries second identification information of the test case and first identification information of a requirement corresponding to the test case, and the information of the defect carries third identification information of the test case with the tested defect;
Identifying target first identification information which is consistent with target identification information corresponding to the target requirement in the first identification information, and determining that the test case corresponding to the target first identification information is the target test case corresponding to the target requirement;
identifying target third identification information consistent with the second identification information in the third identification information, and determining that the defect corresponding to the target third identification information is the target defect corresponding to the target test case;
and displaying the corresponding relation among the target requirement, the target test case and the target defect.
In one possible embodiment, if no target third identification information consistent with the second identification information is identified in the third identification information, the method further includes:
determining that the target test case has no corresponding target defect;
and displaying the corresponding relation between the target requirement and the target test case.
In one possible embodiment, the method further comprises:
and receiving and displaying code submission line number information corresponding to each employee sent by the Gitlab.
In one possible embodiment, the method further comprises:
receiving the number of working days of the month, the number of development tasks completed, the number of defects repaired, the number of repaired defects reopened and the number of defects newly added in the month of the target staff sent by the JIRA;
Determining the defect through rate of the target staff according to the repaired defect number and the reopened number;
determining the number of the day defects of the target staff according to the number of the defects newly increased in the current month and the number of the working days in the current month;
displaying the number of the completed development tasks, the number of the repaired defects which are reopened, the number of the defects which are newly increased in the month, the defect through rate and the number of the day defects.
In one possible implementation manner, after the receiving the information of the test case and the information of the tested defect sent by the open source software Testlink, the method further includes:
counting the number of unresolved defects in the target iteration, and constructing a burnout diagram of the target iteration according to the number and the time for receiving the information of the defects.
In one possible implementation, after the receiving the progress information of agile development sent by JIRA, the method further includes:
and constructing the agile development speed diagram according to the first duration and the first total duration carried in the progress information.
Since the principle of solving the problem with the computer readable medium provided above is similar to that of the agile development progress determination method, the steps implemented after the processor executes the computer program in the computer readable medium may be referred to the other embodiments, and the repetition is omitted.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.
Claims (9)
1. A method for determining agile development progress, the method comprising:
receiving progress information of agile development sent by JIRA, wherein the progress information comprises target iteration where current agile development is located, first total duration of predicted completion of the target iteration, first duration of executed target iteration, target demand corresponding to the target iteration, second total duration of predicted completion of the target demand, second duration of executed target demand, target sub-demand existing in the target demand, third total duration of predicted completion of the target sub-demand, and third duration of currently executed target sub-demand;
determining the development progress of the target iteration according to the first total duration and the first duration, and determining the sub-development progress of the target requirement according to the second total duration and the second duration;
displaying the target iteration, the development progress, the target demand and the sub development progress so as to realize supervision of the development progress of agile development;
receiving the target demand sent by the JIRA, and receiving the type of the target demand, wherein the type of the target demand is obtained by JIRA from a run-tce configuration file; counting all received target demands according to types, and displaying the number of target demands of each type;
Receiving information of a test case and information of a tested defect, wherein the information is sent by open source software Testlink installed in other electronic equipment, the information of the test case carries second identification information of the test case and first identification information of a requirement corresponding to the test case, and the information of the defect carries third identification information of the test case for testing the defect;
identifying target first identification information which is consistent with target identification information corresponding to the target requirement in the first identification information, and determining that the test case corresponding to the target first identification information is the target test case corresponding to the target requirement;
identifying target third identification information consistent with the second identification information in the third identification information, and determining that the defect corresponding to the target third identification information is the target defect corresponding to the target test case;
displaying the corresponding relation among the target requirements, the target test cases and the target defects;
generating a test management report, displaying the test progress of each target requirement in the test management report, displaying the test result of the target requirement, if the test is successful, displaying a pass word after the target requirement, and if the test is failed, displaying a fail word after the target requirement and displaying a bug button, so that the page of the JIRA is jumped to by the bug button.
2. The method of claim 1, wherein determining the development progress of the target iteration based on the first total duration and the first duration comprises:
and determining a first ratio of the first duration to the first total duration as the development progress of the target iteration.
3. The method of claim 1, wherein determining the sub-development schedule of the target demand based on the second total duration and the second duration comprises:
and determining a second ratio of the second time length to the second total time length as a sub-development task of the target requirement.
4. The method of claim 1, wherein if no target third identification information consistent with the second identification information is identified in the third identification information, the method further comprises:
determining that the target test case has no corresponding target defect;
and displaying the corresponding relation between the target requirement and the target test case.
5. The method according to claim 1, wherein the method further comprises:
and receiving and displaying code submission line number information corresponding to each employee sent by the Gitlab.
6. The method according to claim 1, wherein the method further comprises:
Receiving the number of working days of the month, the number of development tasks completed, the number of defects repaired, the number of repaired defects reopened and the number of defects newly added in the month of the target staff sent by the JIRA;
determining the defect through rate of the target staff according to the repaired defect number and the reopened number;
determining the number of the day defects of the target staff according to the number of the defects newly increased in the current month and the number of the working days in the current month;
displaying the number of the completed development tasks, the number of the repaired defects which are reopened, the number of the defects which are newly increased in the month, the defect through rate and the number of the day defects.
7. The method of claim 1, wherein after receiving the information of the test case and the information of the tested defect sent by the open source software Testlink, the method further comprises:
counting the number of unresolved defects in the target iteration, and constructing a burnout diagram of the target iteration according to the number and the time for receiving the information of the defects.
8. The method of claim 1, wherein after receiving the JIRA sent progress information for agile development, the method further comprises:
And constructing the agile development speed diagram according to the first duration and the first total duration carried in the progress information.
9. An agile development progress determination device, the device comprising:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving progress information of agile development sent by JIRA, wherein the progress information comprises target iteration where current agile development is located, predicted first total duration for completing the target iteration, first duration for executing the target iteration, target demand corresponding to the target iteration, predicted second total duration for completing the target demand, second duration for executing the target demand, target sub-demand existing in the target demand, predicted third total duration for completing the target sub-demand and current executed third duration of the target sub-demand;
the processing module is used for determining the development progress of the target iteration according to the first total duration and the first duration, and determining the sub-development progress of the target requirement according to the second total duration and the second duration;
the display module is used for displaying the target iteration, the development progress, the target requirement and the sub development progress so as to realize supervision of the development progress of agile development;
The receiving module is further configured to receive a type of the target demand when receiving the target demand sent by the JIRA, where the type of the target demand is obtained by the JIRA from a run-tce configuration file;
the display module is also used for counting all received target demands according to types and displaying the number of the target demands of each type;
the receiving module is further configured to receive information of a test case and information of a tested defect, where the information of the test case carries second identification information of the test case and first identification information of a requirement corresponding to the test case, and the information of the defect carries third identification information of the test case that tests the defect;
the processing module is further used for identifying target first identification information which is consistent with target identification information corresponding to the target requirement in the first identification information, and determining that the test case corresponding to the target first identification information is the target test case corresponding to the target requirement; identifying target third identification information consistent with the second identification information in the third identification information, and determining that the defect corresponding to the target third identification information is the target defect corresponding to the target test case;
The display module is further used for displaying the corresponding relation among the target requirement, the target test case and the target defect;
the processing module is also used for generating a test management report;
the display module is further configured to display a test progress of each target requirement in the test management report, and display a test result of the target requirement, if the test is successful, display a "pass" word after the target requirement, and if the test is failed, display a "fail" word after the target requirement and display a fault bug button, so that the user jumps to the JIRA page through the bug button.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110325179.8A CN113094095B (en) | 2021-03-26 | 2021-03-26 | Agile development progress determining method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110325179.8A CN113094095B (en) | 2021-03-26 | 2021-03-26 | Agile development progress determining method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113094095A CN113094095A (en) | 2021-07-09 |
| CN113094095B true CN113094095B (en) | 2024-03-22 |
Family
ID=76668197
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110325179.8A Active CN113094095B (en) | 2021-03-26 | 2021-03-26 | Agile development progress determining method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113094095B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8407078B1 (en) * | 2009-01-20 | 2013-03-26 | Perot Systems Corporation | Method of and system for managing projects, programs and portfolios throughout the project lifecycle |
| US9672481B1 (en) * | 2009-10-30 | 2017-06-06 | Parasoft Corporation | System and method for automatically monitoring the overall health of a software project |
| CN107957929A (en) * | 2017-11-20 | 2018-04-24 | 南京大学 | A kind of software deficiency report based on topic model repairs personnel assignment method |
| CN108184159A (en) * | 2016-12-08 | 2018-06-19 | 武汉斗鱼网络科技有限公司 | The implementation method and device of a kind of progress bar |
| CN108694039A (en) * | 2018-05-14 | 2018-10-23 | 链家网（北京）科技有限公司 | A kind of efficiency of research and development promotion optimization method and device of agility flow |
| CN108956850A (en) * | 2017-05-17 | 2018-12-07 | 北大先行科技产业有限公司 | A kind of detection method of Fast Evaluation tertiary cathode material surface residual alkali relative amount |
| CN109377195A (en) * | 2018-12-05 | 2019-02-22 | 江苏风云网络服务有限公司 | Project development management method and device |
| CN111047272A (en) * | 2019-11-07 | 2020-04-21 | 苏宁云计算有限公司 | Project scheduling method and device for multi-language collaborative development |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170061360A1 (en) * | 2015-09-01 | 2017-03-02 | SmartSheet.com, Inc. | Interactive charts with dynamic progress monitoring, notification, and resource allocation |
-
2021
- 2021-03-26 CN CN202110325179.8A patent/CN113094095B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8407078B1 (en) * | 2009-01-20 | 2013-03-26 | Perot Systems Corporation | Method of and system for managing projects, programs and portfolios throughout the project lifecycle |
| US9672481B1 (en) * | 2009-10-30 | 2017-06-06 | Parasoft Corporation | System and method for automatically monitoring the overall health of a software project |
| CN108184159A (en) * | 2016-12-08 | 2018-06-19 | 武汉斗鱼网络科技有限公司 | The implementation method and device of a kind of progress bar |
| CN108956850A (en) * | 2017-05-17 | 2018-12-07 | 北大先行科技产业有限公司 | A kind of detection method of Fast Evaluation tertiary cathode material surface residual alkali relative amount |
| CN107957929A (en) * | 2017-11-20 | 2018-04-24 | 南京大学 | A kind of software deficiency report based on topic model repairs personnel assignment method |
| CN108694039A (en) * | 2018-05-14 | 2018-10-23 | 链家网（北京）科技有限公司 | A kind of efficiency of research and development promotion optimization method and device of agility flow |
| CN109377195A (en) * | 2018-12-05 | 2019-02-22 | 江苏风云网络服务有限公司 | Project development management method and device |
| CN111047272A (en) * | 2019-11-07 | 2020-04-21 | 苏宁云计算有限公司 | Project scheduling method and device for multi-language collaborative development |
Non-Patent Citations (2)
| Title |
|---|
| 军用软件过程质量度量实施方法研究;解群等;微型机与应用;第33卷(第17期);第1-4页 * |
| 基于敏捷模式的自动化测试管理系统设计;徐晨;《中国优秀硕士学位论文全文数据库信息科技辑》(第第03期期);第I138-2642页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113094095A (en) | 2021-07-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Sharma | Quantitative analysis of automation and manual testing | |
| US20090070734A1 (en) | Systems and methods for monitoring software application quality | |
| CN105427695B (en) | Program class examination paper automatic assessment method and system | |
| CN110674047B (en) | Software testing method and device and electronic equipment | |
| WO2019056720A1 (en) | Automated test case management method and apparatus, device, and storage medium | |
| US20170097812A1 (en) | Automated and heuristically managed solution to quantify cpu and path length cost of instructions added, changed or removed by a service team | |
| CN111198811A (en) | Page automatic test method and device, electronic equipment and storage medium | |
| CN112380255A (en) | Service processing method, device, equipment and storage medium | |
| Jain et al. | A Comparison of RANOREX and QTP Automated Testing Tools and their impact on Software Testing | |
| CN111752833B (en) | Software quality system approval method, device, server and storage medium | |
| CN110688173B (en) | Positioning method and device of components in cross-platform interface framework and electronic equipment | |
| CN113094095B (en) | Agile development progress determining method and device | |
| Ali et al. | A Comprehensive Study on Automated Testing with The Software Lifecycle | |
| US20230059609A1 (en) | Assistance information generation device, assistance information generation method, and program recording medium | |
| CN110866492B (en) | Baseline branch identification method and device and computer system | |
| CN113986753A (en) | Interface test method, device, equipment and storage medium | |
| CN115812195A (en) | Calculating developer time in a development process | |
| CN112597041A (en) | Cross-branch merging method, system, equipment and storage medium for code coverage rate | |
| JP2020061073A (en) | Simulation device and simulation method | |
| Lavrenova et al. | Testing System for Corporation Productivity Improvement Department | |
| CN114116468A (en) | Application testing method and device, electronic equipment and storage medium | |
| CN114201410A (en) | Method, device, equipment and medium for monitoring executed degree of test case | |
| Miori | The Necessity of Teaching Computer Simulation within Data Analytics Programs | |
| Zai et al. | A survey of software quality metrics for software measurement process | |
| CN114936148A (en) | Page testing method and device, electronic equipment and readable 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |