CN113094095A - Agile development progress determination method and device - Google Patents
Agile development progress determination method and device Download PDFInfo
- Publication number
- CN113094095A CN113094095A CN202110325179.8A CN202110325179A CN113094095A CN 113094095 A CN113094095 A CN 113094095A CN 202110325179 A CN202110325179 A CN 202110325179A CN 113094095 A CN113094095 A CN 113094095A
- Authority
- CN
- China
- Prior art keywords
- target
- development
- progress
- requirement
- iteration
- 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.)
- Granted
Links
- 238000011161 development Methods 0.000 title claims abstract description 263
- 238000000034 method Methods 0.000 title claims abstract description 60
- 230000007547 defect Effects 0.000 claims description 184
- 238000012360 testing method Methods 0.000 claims description 114
- 238000010586 diagram Methods 0.000 claims description 31
- 238000012545 processing Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 description 12
- 238000004891 communication Methods 0.000 description 8
- 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
- 238000004458 analytical method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012804 iterative process 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
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000013102 re-test Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
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
The method comprises the steps of obtaining a first total time length for finishing target iteration and a first time length for executing the target iteration, determining the development progress of the target iteration according to the first total time length and the first time length, obtaining a second total time length for finishing a target requirement corresponding to the target iteration and a second time length for executing the target requirement, determining a sub-development progress of the target requirement according to the second total time length and the second time length, and displaying the target iteration, the development progress, the target requirement and the sub-development progress, so that the development progress of agile development is displayed, supervision on the development progress of agile development can be well achieved, and using experience 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
With the development of the technology, a plurality of open source software which can be used for agile development exist, when agile development is performed, a plurality of open source software are needed to support the agile development process, such as JIRA, Confluecne, Testlink, SonarQube, Gitlab, and the like, functions of the open source software in the agile development process are different, and the open source software has some statistical functions and can record respective corresponding working conditions. For example, JIRA may be used to manage project development tasks, obtain task status and progress; confluent is used as a knowledge base and organization material management tool and can be used as agile development requirement document management; testlink manages project use case; the SonarQube performs static scanning on the code; a Gitlab management code, etc.
However, these open source software can only record their 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 an 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 influenced in the prior art.
In a first aspect, the present application provides a method for determining an agile development progress, the method comprising:
receiving progress information of agile development sent by JIRA, wherein the progress information comprises a target iteration where the agile development is currently located, a predicted first total time length for completing the target iteration, a predicted first time length for completing the target iteration, a target requirement corresponding to the target iteration, a predicted second total time length for completing the target requirement, and a predicted second time length for completing 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 a second aspect, the present application also provides an agile development progress determination apparatus, 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, and the progress information comprises a target iteration where the agile development is currently located, a predicted first total time length for completing the target iteration, a predicted first time length for executing the target iteration, a target requirement corresponding to the target iteration, a predicted second total time length for completing the target requirement and a predicted second time length 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, which at least includes a processor and a memory, and the processor is configured to implement any one of the above steps of agile development progress determination when executing a computer program stored in the memory.
In a fourth aspect, the present application further provides a computer readable storage medium storing a computer program which, when executed by a processor, implements any of the aforementioned steps of agile development progress determination.
Receiving progress information of agile development sent by JIRA in the application, wherein the progress information comprises a target iteration where the agile development is currently located, a predicted first total time length for completing the target iteration, a predicted first time length for executing the target iteration, a target requirement corresponding to the target iteration, a predicted second total time length for completing the target requirement, and a predicted second time length 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 the method, the development progress of the target iteration is determined by obtaining the predicted first total time length for completing the target iteration and the predicted first time length for executing the target iteration, the predicted second total time length for completing the target iteration and the predicted second time length for executing the target requirement are obtained, the sub-development progress of the target requirement is determined according to the second total time length and the second time length, and the target iteration, the development progress, the target requirement and the sub-development progress are displayed, so that the development progress of the agile development is displayed, the development progress of the agile development can be well supervised, 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 needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
FIG. 1 is a schematic diagram illustrating a process for determining an agile development progress provided by the present application;
FIG. 2 is a schematic illustration of a display of development progress for agile development provided by the present application;
FIG. 3 is a schematic diagram of a sub-development progress of a display target requirement provided by the present application;
FIG. 4 is a corresponding relationship of target requirements, target sub-requirements, target test cases, and target defects provided by the present application;
FIG. 5a is a schematic illustration of a display of a burnout map for a target iteration as provided herein;
FIG. 5b is a schematic illustration of a display of a velocity map for agile development as provided herein;
FIG. 6 is a schematic diagram illustrating a display of a project development quality report provided herein;
FIG. 7 is a schematic diagram illustrating a display of a test management report according to the present application;
FIG. 8 is a schematic illustration of a display of a pipeline health report provided herein;
fig. 9 is a schematic structural diagram of an agile development progress determination apparatus provided in the present application;
fig. 10 is a schematic structural diagram of an electronic device provided in the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application clearer, the present application will be described in further detail with reference to the accompanying drawings, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In order to display the development progress of agile development, facilitate subsequent supervision on the development progress of agile development, and improve the use experience of a user, in the present application, a predicted first total duration for completing a target iteration and a predicted first duration for 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 for completing a target requirement corresponding to the target iteration and a predicted second duration for 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 the development progress of agile development and improve the use experience of a user, the application provides a method, a device, equipment and a medium for determining the agile development progress.
Fig. 1 is a schematic diagram of a process for determining an agile development progress provided by the present application, where the process includes:
s101: receiving progress information of agile development sent by JIRA, wherein the progress information comprises a target iteration where the agile development is located currently, a predicted first total time length for completing the target iteration, a predicted first time length for completing the target iteration, a target requirement corresponding to the target iteration, a predicted second total time length for completing the target requirement, and a predicted second time length for completing 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. Wherein, the software for agile development, such as JIRA, Testlink, etc. runs in other electronic devices, and can also run in the electronic device for determining agile development progress.
In the application, the electronic device may receive progress information of agile development sent by a JIRA, where the JIRA may communicate with the electronic device in real time and send the progress information of agile development to the electronic device in real time, where the progress information includes a target iteration where the agile development is currently located, a predicted first total time length required to complete the target iteration, a first time length currently executed for the target iteration, a target requirement corresponding to the target iteration, a predicted second total time length required to complete the target requirement, and a second time length currently executed for the target requirement.
In addition, in the present application, the progress information may further include an iteration of completed development and an iteration of waiting for development in the agile development. Specifically, the agile development needs to be iterated for multiple times to realize the complete development of the product, the target iteration is the iteration currently performed by the agile development, the iteration completed is the iteration of which the development is completed, and the iteration to be developed is the iteration to be developed in the future.
In the application, if a target sub-demand exists in the target demand, the progress information also carries the target sub-demand corresponding to the target demand, a predicted third total duration for completing the target sub-demand, and a third duration currently executed for the target sub-demand.
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 method and the device, after the progress information of agile development is received, the development progress of the target iteration is determined according to the first total time length and the first time length 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 expression of the development progress may be in the form of a percentage, decimal, fraction, or the like, and the numerical size of the development progress does not exceed 1.
In the method and the device, after the progress information of agile development is received, the sub-development progress required by the target is determined 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 sub-development progress may be expressed in the form of a percentage, a decimal, a fraction, or the like, and the numerical size of the sub-development progress does not exceed 1.
S103: displaying the target iteration, the development progress, the target requirement, and the sub-development progress.
In the method and the device, 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, the development progress, the target requirement, and the sub-development progress are displayed on the same page during display. Specifically, the target iteration and the development progress can be placed at adjacent positions to be displayed, the development progress is identified as the target iteration, the target requirement and the sub-development progress are placed at adjacent positions to be displayed, the sub-development progress is identified as the target requirement, and in addition, the development progress and the sub-development progress can be displayed in a progress bar mode when the development progress and the sub-development progress are displayed.
For example, in the present application, when displaying a development progress and a sub-development progress, the development progress is displayed by a progress bar, a specific numerical value of the development progress is displayed above the progress bar, the sub-development progress is displayed by another progress bar, and the specific numerical 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 obtaining the predicted first total time length for completing the target iteration and the predicted first time length for executing the target iteration and according to the first total time length and the first time length, the sub-development progress of the target requirement is determined by obtaining the second total time length of the target requirement corresponding to the target iteration and the executed second time length of the target requirement and according to the second total time length and the second time length, and the target iteration, the development progress, the target requirement and the sub-development progress are displayed, so that the development progress of the agile development is displayed, the development progress of the agile development can be well supervised, and the use experience of a user is improved.
In order to realize the display of the development progress of the agile development and improve the use experience of the user, on the basis of the above embodiment, in this application, 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 this application, when determining the development progress of the target iteration according to the first total duration and the first total 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 the target iteration, the first duration is a duration already executed for the target iteration, and the development progress of the target iteration is determined, that is, a proportion of the first duration already executed for the target iteration in the first total duration is determined. Therefore, when 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 the first total duration. In the present application, the expression of the development progress may be in the form of a percentage, decimal, fraction, or the like, and the numerical size of the development progress does not exceed 1.
For example, if the first total time duration of the target iteration is 100 hours and the first time duration for which the target iteration has been executed is 25 hours, the development progress of the target iteration is 25%.
In order to realize the display of the development progress of the agile development and improve the use experience of the user, on the basis of the foregoing embodiments, in this application, 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 this application, the sub-development progress of the target requirement is determined according to the second total duration and the first duration carried in the progress information, which may be that the ratio of the second duration to the second total duration is 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, the second duration is a duration executed for the target demand, and the development progress of the target demand is determined, that is, a ratio of the second duration for executing the target demand in the second total duration is determined. Therefore, when determining the sub-development progress, the second ratio may be determined as the sub-development progress of the target requirement by determining a second ratio of the second time duration to the second total time duration. The sub development progress may be expressed in a percentage, a decimal, a fraction, or the like, and the numerical size of the sub development progress does not exceed 1.
For example, if the second total time period of the target demand is 50 hours and the second time period in which the target demand has been executed is 5 hours, the sub-development progress of the target demand is 10%.
Fig. 2 is a schematic diagram illustrating the development progress of the agile development provided by the present application, and as shown in fig. 2, when the development progress of the agile development is displayed, all the iterative processes of a product, including the completed iteration, the current target iteration, and the iteration 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 to-be-completed iteration is 0.
In the present application, when receiving the target demand sent by the jitra, the type of the target demand is also received, the type of the target demand is obtained by the jitra from the run-tce configuration file, all the received target demands are counted according to the type, and the number of the target demands of each type is displayed. In fig. 2, when a target requirement of a target iteration is shown, if an verse story (Epic) exists in the target iteration, the Epic is shown, and the type of the target requirement in the Epic is not shown; if no Epic is present, the type of target demand is shown. In this application, the Epic is the stressful story for recording the functions to be implemented throughout the agile development, i.e., the Epic includes all the target requirements.
Fig. 3 is a schematic diagram for displaying the sub-development progress of the target requirement provided by the present application, and in fig. 3, for each target requirement, the sub-development progress of the target requirement is displayed, and the type to which the target requirement belongs.
In order to realize the display of the development progress of the agile development and improve the use experience of the 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 corresponding requirement of 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 a test case corresponding to the target first identification information as a target test case corresponding to the target requirement;
identifying target third identification information which is consistent with the second identification information in third identification information, and determining that the defect corresponding to the target third identification information is a 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 the application, each target requirement has one or more test cases corresponding to the target requirement, and the test cases are specifically used for detecting the developed target requirement by using the test case after the corresponding target requirement is developed, and when the test cases detect errors, the developed target requirement is considered to have errors, and then a defect is generated for identifying the development of the target requirement that has errors. In the application, the process of detecting the developed target requirement by using the test case is carried out in open source software Testlink.
In the application, the electronic device also receives information of a test case and information of a tested defect, which are sent by 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 corresponding requirement of the test case, and the information of the defect carries third identification information of the test case with the tested defect.
Specifically, after receiving the information of the test case, 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 after receiving the tested defect information, the defect information carries the third identification information of the test case with the tested 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 the statistics of the agile development process. In the application, a target test case corresponding to a target requirement is firstly identified, that is, first identification information of a target, which is consistent with target identification information corresponding to the target requirement, in the first identification information is identified, and the test case corresponding to the first identification information of the target is determined to be the target test case corresponding to the target requirement. Specifically, in the application, each requirement corresponds to one identification information, 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 which is consistent with the second identification information in the third identification information, and determining a defect corresponding to the target third identification information as a target defect corresponding to the target test case. Specifically, in the application, the identification information corresponding to each test case is also 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 of the target requirement, the target test case and the target defect is displayed on a 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 by 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 display the development progress of agile development and improve the use experience of a user, on the basis of the foregoing embodiments, in this application, after receiving information of a test case and information of a tested defect sent by open source software Testlink, the method further includes:
and counting the number of unsolved 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 method, after the information of the tested defects sent by the open source software Testlink is received, the number of the unsolved defects in the target iteration is determined according to the information of the defects, and the burnout diagram of the target iteration is constructed according to the number and the time for receiving the information of the defects.
Specifically, after receiving the information of the defect, determining the number of the unsolved defects in the target iteration, taking the number as a vertical coordinate, determining the time for receiving the information of the defect as a horizontal coordinate, determining a coordinate corresponding to the information of the defect, identifying the coordinate system 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 with a broken line to construct a burnout map.
For example, if the number of the unsolved defects in the target iteration is 10 and the time is 2021, 3, month and 10 days, the coordinates corresponding to the information of the defect are (10, 2021, 3, month and 10 days), the point corresponding to the coordinates is found in the coordinate system, and the point is connected with the determined last point.
In addition, in the present application, the open source software Testlink sends information of the defect in real time.
In order to realize the display of the development progress of the agile development and improve the use experience of the user, on the basis of the foregoing embodiments, in the present application, after receiving the JIRA-sent progress information of the agile development, the method includes:
and constructing the agile development speed chart according to the first duration and the first total duration carried in the progress information.
In the present application, the development speed of the target iteration is also shown for the target iteration, specifically, after receiving the predicted first total time length for completing the target iteration and the predicted first time length for executing the target iteration, a speed map is constructed. The velocity map may be a bar graph, wherein the abscissa of the bar graph is an iteration in agile development, and a bar graph with a first total duration as a height and a bar graph with a first duration as a height are constructed at a position corresponding to the target iteration.
In addition, in the present application, other iterations that have already been developed in the agile development can also be shown in the velocity map.
In the application, after the burnout map and the velocity map are constructed, the burnout map and the velocity map are displayed on the same display page.
Fig. 5a is a schematic diagram showing a burnout map of a target iteration provided by the present application, and as shown in fig. 5a, the ordinate of the burnout map is the number of unprocessed problems, i.e., the number of unsolved defects in the target iteration, and the abscissa is the operating time length.
Fig. 5b is a schematic diagram showing a velocity diagram of agile development provided by the present application, where the ordinate of the velocity diagram is the working time length and the abscissa is the iteration, as shown in fig. 5 b.
In order to realize the display of the development progress of the agile development and improve the use experience of the user, on the basis of the foregoing embodiments, in the present application, if the target third identification information that is 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 by using the test case and an error is detected, and when the agile development of the requirement has no error, the defect is not marked, so that the target test case may not have a 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, it is determined that the target test case has no corresponding target defect, and the corresponding relationship between the target requirement and the target test case is displayed on the display interface.
In order to realize the display of the development progress of the agile development and improve the use experience of the user, on the basis of the above embodiments, in the present application, the method further includes:
and receiving and displaying code submitting line number information corresponding to each employee, which is sent by the Gitlab.
In the present application, the code submission line number of each employee, that is, the line number of the code submitted by each employee, is recorded in the Gitlab. In order to display the working condition of each employee, in the application, the electronic device further receives code submitting line number information, corresponding to each employee, sent by the Gitlab, and displays each employee and the code submitting line number information corresponding to each employee on a display interface.
In order to realize the display of the development progress of the agile development and improve the use experience of the user, on the basis of the above embodiments, in the present application, the method further includes:
receiving the working days of the target employee in the month, the number of completed development tasks, the number of repaired defects reopened and the number of newly added defects in the month sent by the JIRA;
determining the defect first pass rate of the target employee according to the repaired defect number and the reopened number;
determining the number of day defects of the target employee according to the number of newly increased defects in the month and the number of working days in the month;
displaying the number of completed development tasks, the number of repaired defects reopened, the number of newly added defects in the month, the defect first pass rate, and the number of daily defects.
In the present application, the electronic device also receives the working days of the month, the number of completed development tasks, the number of repaired defects reopened, and the number of newly added defects in the month of the target employee, which are sent by the JIRA.
The target employee is allocated with a preset number of development tasks before the work of the target employee starts in the month, and the number of the completed development tasks is the number of the development tasks completed by the target employee; meanwhile, in the application, the target staff can also repair the generated defects and record the number of repaired defects of the target staff, the target staff can retest the test cases corresponding to the defects after repairing the defects, if the defects are not successfully repaired, the defects can be reopened, and the number of reopened repaired defects can be recorded.
In the method, after the number of repaired defects and the number of repaired defects reopened, the defect first pass rate of the target employee is determined according to the number of repaired defects and the number of reopened defects. Specifically, the number of unreopened defects in the repaired defects of the target employee, that is, the number of unreopened defects, needs to be calculated, where the number of unreopened defects is a difference between the number of repaired defects and the number of reopened defects, a ratio of the number of unreopened defects to the number of repaired defects is calculated, and the ratio is determined as the defect through-yield of the target employee, and generally, the defect through-yield 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 unreopened defects is 6, and the ratio of the number of reopened defects to the number of repaired defects is 0.6, the defect through rate of the target employee is 60%.
In the application, after the number of newly added defects in the month and the number of working days in the month are received, the number of day defects of the target employee is determined according to the number of newly added defects in the month and the number of working days in the month. Specifically, the ratio of the number of newly added defects in the month to the number of working days in the month is calculated, and the ratio is determined as the number of daily defects of the target employee. And if the target employee is not configured with the working days of the month, the number of day defects of the target employee is not calculated. For example, if the number of newly added defects of the target employee in this month is 5 and the number of working days in this month is 20 days, the number of daily defects of the target employee is 0.25.
In the present application, the number of completed development tasks, the number of repaired defects reopened, the number of newly added defects in the month, the defect first pass rate, and the number of daily defects are also displayed.
Fig. 6 is a schematic diagram illustrating a display of a project development quality report provided by the present application, where as shown in fig. 6, the project development quality report includes code statistics, defect statistics, and SonarQube, where the code statistics indicates the number of code submission lines corresponding to each employee sent by Gitlab, the defect statistics shows the number of completed development tasks, the number of repaired defects reopened, the number of newly added defects in this month, the defect through rate, and the number of day defects of each employee, and the SonarQube is the number of code defects counted by SonarQube.
Fig. 7 is a schematic display diagram of a test management report provided by the present application, where as shown in fig. 7, the test management report displays a test progress of each target requirement and a test result of the target requirement or the target sub-requirement, if the test is successful, a "pass" word is displayed behind the target requirement or the target sub-requirement, and if the test is failed, a "fail" word is displayed behind the target requirement or the target sub-requirement, 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 diagram illustrating a display of a pipeline health report provided in the present application, where as shown in fig. 8, the pipeline health report includes statistics of pipeline execution states, resource quantities, pending pipelines, an execution failure rate, and an execution record, where all the data are directly obtained from Confluence.
Fig. 9 is a schematic structural diagram of an agile development progress determining apparatus provided in the present application, where the apparatus includes:
a receiving module 901, configured to receive progress information of agile development sent by the JIRA, where the progress information includes a target iteration where the agile development is currently located, a predicted first total duration for completing the target iteration, a predicted 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 predicted 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;
a display module 903, 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 a 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 a 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, 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 where the defect is tested;
the determining module 902 is further configured to identify first target identification information in the first identification information, where the first target identification information is consistent with the target identification information corresponding to the target requirement, and determine that the test case corresponding to the first target identification information is a target test case corresponding to the target requirement; identifying target third identification information which is consistent with the second identification information in third identification information, and determining that the defect corresponding to the target third identification information is a target defect corresponding to the target test case;
the display module 903 is further configured to display a corresponding relationship between the target requirement, the target test case, and the target defect.
In a possible implementation manner, if the target third identification information consistent with the second identification information is not 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 corresponding relationship 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 line number information, which is sent by the Gitlab and corresponds to each employee.
In a possible implementation manner, the receiving module 901 is further configured to receive the working days of the target employee in the month, the number of completed development tasks, the number of repaired defects reopened, and the number of newly added defects in the month sent by the jitra;
the determining module 902 is further configured to determine a defect first pass rate of the target employee according to the repaired defect number and the reopened number; determining the number of day defects of the target employee according to the number of newly increased defects in the month and the number of working days in the month;
the display module 903 is further configured to display the number of completed development tasks, the number of repaired defects reopened, the number of new defects in the month, the defect first pass rate, and the number of daily defects.
In a possible implementation, the determining module 902 is further configured to count the number of unsolved 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 a speed map of the 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: the system comprises a processor 1001, a communication interface 1002, a memory 1003 and a communication bus 1004, wherein the processor 1001, the communication interface 1002 and the memory 1003 are communicated with each other through the communication bus 1004;
the memory 1003 has stored therein 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 a target iteration where the agile development is currently located, a predicted first total time length for completing the target iteration, a predicted first time length for completing the target iteration, a target requirement corresponding to the target iteration, a predicted second total time length for completing the target requirement, and a predicted second time length for completing 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 a possible implementation manner, the determining, according to the first total duration and the first duration, a development progress of the target iteration includes:
and determining 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 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 corresponding requirement of 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 a test case corresponding to the target first identification information as a target test case corresponding to the target requirement;
identifying target third identification information which is consistent with the second identification information in third identification information, and determining that the defect corresponding to the target third identification information is a 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 a possible implementation manner, if the target third identification information that is 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 one possible embodiment, the method further comprises:
and receiving and displaying code submitting line number information corresponding to each employee, which is sent by the Gitlab.
In one possible embodiment, the method further comprises:
receiving the working days of the target employee in the month, the number of completed development tasks, the number of repaired defects reopened and the number of newly added defects in the month sent by the JIRA;
determining the defect first pass rate of the target employee according to the repaired defect number and the reopened number;
determining the number of day defects of the target employee according to the number of newly increased defects in the month and the number of working days in the month;
displaying the number of completed development tasks, the number of repaired defects reopened, the number of newly added defects in the month, the defect first pass rate, and the number of daily defects.
In a possible implementation manner, 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 includes:
and counting the number of unsolved 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 embodiment, after receiving the JIRA-sent agile development progress information, the method further comprises:
and constructing the agile development speed chart according to the first duration and the first total duration carried in the progress information.
Because the principle of the electronic device for solving the problems is similar to the agile development progress determination method, the implementation of the electronic device can refer to the implementation of the method, and repeated details are not repeated.
The communication bus mentioned in the electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface 1002 is used for communication between the electronic apparatus and other apparatuses.
The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Alternatively, the memory may be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, including a central processing unit, a Network Processor (NP), and the like; but may also be a Digital instruction processor (DSP), an application specific integrated circuit, a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or the like.
On the basis of the foregoing embodiments, the present application further provides a computer-readable storage medium, in which a computer program executable by a processor is stored, and when the program is run on the processor, the processor is caused to execute the following steps:
receiving progress information of agile development sent by JIRA, wherein the progress information comprises a target iteration where the agile development is currently located, a predicted first total time length for completing the target iteration, a predicted first time length for completing the target iteration, a target requirement corresponding to the target iteration, a predicted second total time length for completing the target requirement, and a predicted second time length for completing 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 a possible implementation manner, the determining, according to the first total duration and the first duration, a development progress of the target iteration includes:
and determining 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 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 corresponding requirement of 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 a test case corresponding to the target first identification information as a target test case corresponding to the target requirement;
identifying target third identification information which is consistent with the second identification information in third identification information, and determining that the defect corresponding to the target third identification information is a 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 a possible implementation manner, if the target third identification information that is 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 one possible embodiment, the method further comprises:
and receiving and displaying code submitting line number information corresponding to each employee, which is sent by the Gitlab.
In one possible embodiment, the method further comprises:
receiving the working days of the target employee in the month, the number of completed development tasks, the number of repaired defects reopened and the number of newly added defects in the month sent by the JIRA;
determining the defect first pass rate of the target employee according to the repaired defect number and the reopened number;
determining the number of day defects of the target employee according to the number of newly increased defects in the month and the number of working days in the month;
displaying the number of completed development tasks, the number of repaired defects reopened, the number of newly added defects in the month, the defect first pass rate, and the number of daily defects.
In a possible implementation manner, 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 includes:
and counting the number of unsolved 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 embodiment, after receiving the JIRA-sent agile development progress information, the method further comprises:
and constructing the agile development speed chart according to the first duration and the first total duration carried in the progress information.
Since the principle of the problem solving by the computer readable medium is similar to that of the agile development progress determination method, after the processor executes the computer program in the computer readable medium, the steps implemented by the processor may refer to the other embodiments, and repeated details are not described herein.
As will be appreciated by one skilled in the art, 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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (10)
1. An agile development progress determination method, the method comprising:
receiving progress information of agile development sent by JIRA, wherein the progress information comprises a target iteration where the agile development is currently located, a predicted first total time length for completing the target iteration, a predicted first time length for completing the target iteration, a target requirement corresponding to the target iteration, a predicted second total time length for completing the target requirement, and a predicted second time length for completing 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.
2. The method of claim 1, wherein determining the development progress of the target iteration according to 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 for 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, further comprising:
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 corresponding requirement of 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 a test case corresponding to the target first identification information as a target test case corresponding to the target requirement;
identifying target third identification information which is consistent with the second identification information in third identification information, and determining that the defect corresponding to the target third identification information is a 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.
5. The method of claim 4, 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.
6. The method of claim 1, further comprising:
and receiving and displaying code submitting line number information corresponding to each employee, which is sent by the Gitlab.
7. The method of claim 1, further comprising:
receiving the working days of the target employee in the month, the number of completed development tasks, the number of repaired defects reopened and the number of newly added defects in the month sent by the JIRA;
determining the defect first pass rate of the target employee according to the repaired defect number and the reopened number;
determining the number of day defects of the target employee according to the number of newly increased defects in the month and the number of working days in the month;
displaying the number of completed development tasks, the number of repaired defects reopened, the number of newly added defects in the month, the defect first pass rate, and the number of daily defects.
8. The method according to claim 4, 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:
and counting the number of unsolved 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.
9. The method of claim 1, wherein after receiving the JIRA-sent agile development progress information, the method further comprises:
and constructing the agile development speed chart according to the first duration and the first total duration carried in the progress information.
10. An agile development progress determination apparatus, characterized in that the apparatus comprises:
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, and the progress information comprises a target iteration where the agile development is currently located, a predicted first total time length for completing the target iteration, a predicted first time length for executing the target iteration, a target requirement corresponding to the target iteration, a predicted second total time length for completing the target requirement and a predicted second time length 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.
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 true CN113094095A (en) | 2021-07-09 |
| CN113094095B 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) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114003311A (en) * | 2021-10-29 | 2022-02-01 | 平安国际智慧城市科技股份有限公司 | Progress bar configuration method based on artificial intelligence and related equipment |
Citations (9)
| 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 |
| US20170061360A1 (en) * | 2015-09-01 | 2017-03-02 | SmartSheet.com, Inc. | Interactive charts with dynamic progress monitoring, notification, and resource allocation |
| 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 |
-
2021
- 2021-03-26 CN CN202110325179.8A patent/CN113094095B/en active Active
Patent Citations (9)
| 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 |
| US20170061360A1 (en) * | 2015-09-01 | 2017-03-02 | SmartSheet.com, Inc. | Interactive charts with dynamic progress monitoring, notification, and resource allocation |
| 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 (5)
| Title |
|---|
| 一只鲸鱼: "Leangoo敏捷开发工具- 6.0.2 版发布", pages 1 - 4, Retrieved from the Internet <URL:https://www.cnblogs.com/shineshine/p/11818796.html> * |
| 徐晨: "基于敏捷模式的自动化测试管理***设计", 《中国优秀硕士学位论文全文数据库信息科技辑》, no. 03, pages 138 - 2642 * |
| 白云庄主: "测试人员与实施人员发现缺陷的效率对比", pages 1, Retrieved from the Internet <URL:https://blog.csdn.net/fuzengbin/article/details/7104768> * |
| 解群等: "军用软件过程质量度量实施方法研究", 微型机与应用, vol. 33, no. 17, pages 1 - 4 * |
| 顾翔: "缺陷度量结果分析带来的思考", pages 1 - 7, Retrieved from the Internet <URL:https://cloud.tencent.com/developer/article/1552203> * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114003311A (en) * | 2021-10-29 | 2022-02-01 | 平安国际智慧城市科技股份有限公司 | Progress bar configuration method based on artificial intelligence and related equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113094095B (en) | 2024-03-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Sharma | Quantitative analysis of automation and manual testing | |
| Guide Jr et al. | Hewlett-Packard company unlocks the value potential from time-sensitive returns | |
| CN110674047B (en) | Software testing method and device and electronic equipment | |
| WO2019056720A1 (en) | Automated test case management method and apparatus, device, and storage medium | |
| US11442847B2 (en) | Automated determination of software testing resources | |
| CN111198811A (en) | Page automatic test method and device, electronic equipment and storage medium | |
| CN110969600A (en) | Product defect detection method and device, electronic equipment and storage medium | |
| US9612944B2 (en) | Method and system for verifying scenario based test selection, execution and reporting | |
| CN110134598B (en) | Batch processing method, device and system | |
| CN113094095B (en) | Agile development progress determining method and device | |
| US20170364352A1 (en) | Release cycle optimization based on significant features values simulation | |
| CN109471787B (en) | Software quality evaluation method and device, storage medium and electronic equipment | |
| CN111191861B (en) | Machine number determination method and device, processing line, storage medium and electronic equipment | |
| JP5775803B2 (en) | Production line simulation model construction method, production line simulation model construction apparatus, and production line simulation model construction program | |
| KR20120111618A (en) | Apparatus and method for testing plc command | |
| CN115543435A (en) | Software development quality measuring method, device and equipment based on development contribution value | |
| US20230059609A1 (en) | Assistance information generation device, assistance information generation method, and program recording medium | |
| CN114443141A (en) | Method and device for determining cyclic constraint fault of measurement and control instruction | |
| US10552760B2 (en) | Training set creation for classifying features of a system under agile development | |
| US7996518B2 (en) | Detecting machine utilization activity | |
| Huff et al. | Systematic evaluation for bottleneck detection methods | |
| US11501226B1 (en) | Monitoring and creating customized dynamic project files based on enterprise resources | |
| US11847393B2 (en) | Computing device and method for developing a system model utilizing a simulation assessment module | |
| US11244269B1 (en) | Monitoring and creating customized dynamic project files based on enterprise resources | |
| Lavrenova et al. | Testing System for Corporation Productivity Improvement Department |
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 |