CN107679683B - Software development progress early warning method and device - Google Patents
Software development progress early warning method and device Download PDFInfo
- Publication number
- CN107679683B CN107679683B CN201611239455.4A CN201611239455A CN107679683B CN 107679683 B CN107679683 B CN 107679683B CN 201611239455 A CN201611239455 A CN 201611239455A CN 107679683 B CN107679683 B CN 107679683B
- Authority
- CN
- China
- Prior art keywords
- early warning
- preset
- story
- delivery
- delivery rate
- 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
Images
Classifications
-
- 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/063116—Schedule adjustment for a person or group
-
- 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/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Abstract
The invention relates to a software development progress early warning method and a device, wherein the method comprises the following steps: acquiring a Story total point number corresponding to a current version and a preset development period corresponding to the current version; obtaining the number of Story points to be delivered in a preset monitoring period according to the preset development period and the total number of the Story points; acquiring the number of Story points actually delivered within the preset monitoring period, and obtaining the actual delivery rate according to the number of the Story points actually delivered and the number of the Story points to be delivered; reading a preset delivery rate threshold value from a database, comparing the actual delivery rate with the delivery rate threshold value, and generating early warning information corresponding to the version delivery progress according to the comparison result; and sending the early warning information corresponding to the version delivery progress to a terminal. The software development efficiency is improved.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a software development progress early warning method and device.
Background
Software development refers to the process of building a software system or software parts in a system according to user requirements. Among various software development methods, agile development (i.e., a method of developing software by using an iterative and progressive method with the evolution of user's needs as a core) is gradually welcomed by developers due to the characteristics of fast iteration and fast delivery.
In the whole agile development process, the processes of development, testing, defect repair and the like can be involved, and the development progress of the whole version can be influenced if one link is not processed in time. Generally, there is no related monitoring mechanism in the version development process, and when a version development progress is blocked, a manager often cannot timely know which link or process is not timely processed, so that the problem of blocking cannot be timely solved by arranging and adjusting personnel or work, and software development efficiency is affected.
Disclosure of Invention
Based on this, there is a need for a software development progress early warning method and apparatus for improving software development efficiency.
A software development progress early warning method comprises the following steps:
acquiring a Story total point number corresponding to a current version and a preset development period corresponding to the current version;
obtaining the number of Story points to be delivered in a preset monitoring period according to the preset development period and the total number of the Story points;
acquiring the number of Story points actually delivered within the preset monitoring period, and obtaining the actual delivery rate according to the number of the Story points actually delivered and the number of the Story points to be delivered;
reading a preset delivery rate threshold value from a database, comparing the actual delivery rate with the delivery rate threshold value, and generating early warning information corresponding to the version delivery progress according to the comparison result;
and sending the early warning information corresponding to the version delivery progress to a terminal.
In one embodiment, the step of obtaining total number of storeys corresponding to the current version includes:
acquiring a plurality of requirements corresponding to the current version and the number of Story points corresponding to each requirement;
and obtaining the total Story points corresponding to the current version according to the Story points corresponding to the requirements.
In one embodiment, the step of generating the warning information corresponding to the version delivery progress according to the comparison result includes:
when the actual delivery rate is larger than or equal to the delivery rate threshold, determining a first early warning level corresponding to the version delivery progress, and generating an early warning mark corresponding to the first early warning level;
when the actual delivery rate is smaller than the delivery rate threshold and is larger than or equal to the product of the delivery rate threshold and a preset delivery coefficient, determining a second early warning level corresponding to the version delivery progress, and generating an early warning mark corresponding to the second early warning level;
and when the actual delivery rate is smaller than the product of the delivery rate threshold and the preset delivery coefficient, determining a third early warning level corresponding to the version delivery progress, and generating an early warning mark corresponding to the third early warning level.
In one embodiment, the method further comprises:
calling an interface of a defect system to acquire defect information and a corresponding defect grade, and processing the actual aging of the defect information;
searching a preset aging corresponding to the defect grade, comparing the actual aging with the preset aging, and generating early warning information corresponding to the defect processing progress;
and sending the early warning information corresponding to the defect processing progress to the terminal.
In one embodiment, the pre-set age includes a defect repair age and/or a defect verification age.
A software development progress warning device, the device comprising:
the acquisition module is used for acquiring the total Story points corresponding to the current version and the preset development period corresponding to the current version;
the Story point determining module is used for obtaining the Story points to be delivered in the preset monitoring period according to the preset development period and the total Story points;
the delivery rate determining module is used for acquiring the number of the actual delivered Story points in the preset monitoring period and obtaining the actual delivery rate according to the number of the actual delivered Story points and the number of the Story points to be delivered;
the early warning information generation module is used for reading a preset delivery rate threshold value from a database, comparing the actual delivery rate with the delivery rate threshold value and generating early warning information corresponding to the version delivery progress according to a comparison result;
and the sending module is used for sending the early warning information corresponding to the version delivery progress to a terminal.
In one embodiment, the storage point determining module is further configured to obtain a plurality of requirements corresponding to the current version and storage points corresponding to the requirements; and obtaining the total Story points corresponding to the current version according to the Story points corresponding to the requirements.
In one embodiment, the early warning information generating module is further configured to determine a first early warning level corresponding to a version delivery progress when the actual delivery rate is greater than or equal to the delivery rate threshold, and generate an early warning mark corresponding to the first early warning level; when the actual delivery rate is smaller than the delivery rate threshold and is larger than or equal to the product of the delivery rate threshold and a preset delivery coefficient, determining a second early warning level corresponding to the version delivery progress, and generating an early warning mark corresponding to the second early warning level; and when the actual delivery rate is smaller than the product of the delivery rate threshold and the preset delivery coefficient, determining a third early warning level corresponding to the version delivery progress, and generating an early warning mark corresponding to the third early warning level.
In one embodiment, the acquiring module is further configured to call an interface of a defect system to acquire defect information and a corresponding defect level, and process actual aging of the defect information;
the device further comprises:
the searching module is used for searching for the preset aging corresponding to the defect grade;
the early warning information generation module is also used for comparing the actual aging with the preset aging to generate early warning information corresponding to the defect processing progress;
the sending module is further used for sending the early warning information corresponding to the defect processing progress to the terminal.
In one embodiment, the pre-set age includes a defect repair age and/or a defect verification age.
According to the software development progress early warning method and device, the total Story points corresponding to the current version and the preset development period corresponding to the current version are obtained; obtaining the number of Story points to be delivered in the preset monitoring period according to the preset development period and the total number of the Story points; acquiring the number of the actual delivery storeys points in a preset monitoring period, and obtaining the actual delivery rate according to the number of the actual delivery storeys points and the number of the stopys points to be delivered; reading a preset delivery rate threshold value from a database, comparing the actual delivery rate with the delivery rate threshold value, and generating early warning information corresponding to the version delivery progress according to the comparison result; and sending the early warning information corresponding to the version delivery progress to the terminal. The development delivery rate is monitored through the Story dimension, early warning information corresponding to the version delivery progress is generated, and therefore early warning processing personnel can be informed timely when the development delivery process is blocked. Therefore, the early warning processing personnel can timely know the reason of blockage, and can timely arrange and adjust to solve the problem of blockage. And further improves the software development efficiency.
Drawings
FIG. 1 is a schematic diagram of an application environment of a software development progress warning method in one embodiment;
FIG. 2 is an internal block diagram of a server in one embodiment;
FIG. 3 is a flowchart illustrating a software development progress warning method according to an embodiment;
FIG. 4 is a schematic flow chart illustrating a method for generating warning information according to another embodiment;
FIG. 5 is a flowchart illustrating a method for warning a progress of defect handling in one embodiment;
FIG. 6 is a schematic structural diagram of a software development progress warning device in one embodiment;
fig. 7 is a schematic structural diagram of a software development progress warning device in another embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Fig. 1 is an application environment diagram of a software development progress warning method in an embodiment. As shown in fig. 1, the server 110 communicates with the terminal 120 through a network. The server 110 obtains the total number of storeys corresponding to the current version and the preset development period corresponding to the current version, and obtains the number of storeys to be delivered in the preset monitoring period according to the preset development period and the total number of storeys. Further, the server 110 obtains the number of the actual delivery storeys points in the preset monitoring period, and obtains the actual delivery rate according to the number of the actual delivery storeys points and the number of the delivery storeys points. The server 110 reads a preset delivery rate threshold from the database, compares the actual delivery rate with the delivery rate threshold, and generates early warning information corresponding to the version delivery progress according to the comparison result. The server 110 transmits warning information corresponding to the version delivery progress to the terminal 120.
It is understood that the terminal 120 includes, but is not limited to, various personal computers, smart phones, tablet computers, notebook computers, portable wearable devices, and the like, which are not listed herein.
Fig. 2 shows a schematic internal structure diagram of the server 110 in one embodiment, which includes a processor, a nonvolatile storage medium, an internal memory, and a network interface connected by a system bus. The nonvolatile storage medium of the server stores an operating system, a database and a software development progress early warning device, wherein the database is used for storing data, such as a preset delivery rate threshold value and the like. The software development progress early warning device is used for realizing a software development progress early warning method. The processor is used for providing calculation and control capacity and supporting the operation of the whole server. The internal memory in the server provides an environment for the operation of the software development progress warning device in the non-volatile storage medium, and the internal memory can store computer readable instructions, and when the computer readable instructions are executed by the processor, the processor can be caused to execute a software development progress warning method. The network interface is used for network communication with the terminal. Those skilled in the art will appreciate that the architecture shown in fig. 2 is a block diagram of only a portion of the architecture associated with the subject application, and does not constitute a limitation on the servers to which the subject application applies, as a particular server may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
As shown in fig. 3, in an embodiment, a software development progress early warning method is provided, which is exemplified by applying the method to a server, and specifically includes the following steps:
It will be appreciated that in agile development, the development of the entire version will be divided into several requirements, each of which may include at least one Story (i.e., Story). Wherein Story is the function point with the minimum granularity. A software version is equivalently composed of multiple storeys.
The server obtains the total number of storeys corresponding to the current version (namely the version currently being developed) and the preset development period of the current version.
Wherein, one store corresponds to one point. The total number of Story points is the total number of Story.
Specifically, the server may directly obtain the total Story points corresponding to the current version from a correlation system (hereinafter referred to as a correlation system) in which the version division information is stored (for example, an electronic billboard system).
The server may obtain a plurality of requirements corresponding to the current version and the store points corresponding to the respective requirements, and specifically, the server may obtain the plurality of requirements corresponding to the current version and the store points corresponding to the respective requirements from the association system in which the version division information is stored, or obtain a plurality of requirements corresponding to the current version and the store points corresponding to the respective requirements stored by the server. This is not limitative.
Further, the server obtains the total number of the Story points corresponding to the current version according to the number of the Story points corresponding to each requirement. Specifically, the server sums the Story points corresponding to each requirement to obtain the total number of Story points corresponding to the current version. For example, the version is divided into 18 requirements, wherein 2 requirements respectively include 5 storeys, 3 requirements respectively include 3 storeys, 10 requirements respectively include 2 storeys, and 3 requirements respectively include 1 storery. Then the total number of store points corresponding to that version is 2 x 5+3 x 3+10 x 2+3 x 1 is 42.
It can be understood that the version division information is the demand information and the store point information for dividing the version or the store total points corresponding to the version. The electronic billboard system is a system for managing version information and version development processing information. It will be appreciated that the functionality of the electronic billboard system is not limited to the above-described functionality.
In other embodiments, the server itself may also store the versioning information, and the server may obtain the stored versioning information from its database.
The preset development period refers to a period for a developer to perform version development. It can be understood that after the version development is completed, the version is delivered to the testing department for version testing operation.
And step 304, obtaining the number of Story points to be delivered in the preset monitoring period according to the preset development period and the total number of the Story points.
In this embodiment, a preset monitoring period is preset in the server. The preset monitoring period may be in units of days, weeks, etc. For example, it may be one day, 2 days, 1 week, or the like. The preset monitoring period refers to a period for performing progress detection and generating early warning information.
The server obtains the number of the Story points to be delivered in the preset monitoring period according to the preset development period and the total number of the Story points. Specifically, the server may calculate a ratio of a preset version monitoring period to a preset development period, and then obtain the number of storery points to be delivered in the preset monitoring period according to a product of the ratio and the total number of storery points. It is understood that "delivery" in this embodiment refers to delivery from development to test, rather than going on-line to production after the entire development and test process is completed.
And step 306, acquiring the number of the actual delivery storeys points in the preset monitoring period, and obtaining the actual delivery rate according to the number of the actual delivery storeys points and the number of the stopys points to be delivered.
The server obtains the number of storey points actually delivered in the preset monitoring period. Specifically, the server may obtain the number of the storage points actually delivered from its own database, or call an interface of the association system to obtain the number of the storage points actually delivered within the preset monitoring period from the association system. This is not limitative.
Further, the server obtains the actual delivery rate according to the ratio of the actual delivered Story points to the delivered Story points.
And 308, reading a preset delivery rate threshold value from the database, comparing the actual delivery rate with the delivery rate threshold value, and generating early warning information corresponding to the version delivery progress according to the comparison result.
Specifically, a pre-set delivery rate threshold is stored in the database. The server reads a preset delivery rate threshold from the database. And comparing the actual delivery rate with a preset delivery rate threshold value, and generating early warning information corresponding to the version delivery progress according to the comparison result.
The early warning information includes an early warning mark or an early warning item (for example, an early warning for the fact of delivery). The method can also comprise the actual delivery rate, a preset delivery rate threshold value and a comparison condition between the actual delivery rate and the preset delivery rate threshold value. Further, the early warning mark is a mark capable of identifying early warning intensity or early warning grade, and may include a color mark or a graphic mark to distinguish and identify different early warning intensities or early warning grades.
In an embodiment, as shown in fig. 4, the step of generating the warning information corresponding to the version delivery progress according to the comparison result (referred to as the warning information generating step for short) specifically includes the following steps:
In this embodiment, when the server determines that the actual delivery rate is greater than or equal to the delivery rate threshold, it is determined that the version delivery progress corresponds to the first early warning level, and then the early warning mark corresponding to the first early warning level is generated.
It is understood that when the actual delivery rate is greater than or equal to the delivery rate threshold, it indicates that the progress is not blocked, and the progress is in a normal state. The determined first early warning level is zero-level early warning. And the generated corresponding early warning mark is a mark with normal identification progress. For example, whether the progress is blocked may be identified according to the traffic lights, and the warning mark corresponding to the first warning level is a green light mark.
And step 404, when the actual delivery rate is smaller than the delivery rate threshold and is larger than or equal to the product of the delivery rate threshold and the preset delivery coefficient, determining a second early warning level corresponding to the version delivery progress, and generating an early warning mark corresponding to the second early warning level.
In this embodiment, a delivery coefficient is preset in the server, where the delivery coefficient is a positive number smaller than 1. And when the server judges that the actual delivery rate is smaller than the delivery rate threshold and is larger than or equal to the product of the delivery rate threshold and the preset delivery coefficient, determining that the version delivery progress corresponds to a second early warning level, and further generating an early warning mark corresponding to the second early warning level.
It will be appreciated that when the actual delivery rate is less than the delivery rate threshold and greater than or equal to the product of the delivery rate threshold and the pre-set delivery factor, then some congestion is indicated in the schedule, and the schedule is in a slightly congested state. The determined second early warning level is a medium early warning. And the generated corresponding early warning mark is a mark for identifying slight progress blockage. Similarly, for example, if the progress is identified as being blocked according to the traffic lights, the warning mark corresponding to the second warning level is a yellow light mark.
And 406, when the actual delivery rate is smaller than the product of the delivery rate threshold and the preset delivery coefficient, determining a third early warning level corresponding to the version delivery progress, and generating an early warning mark corresponding to the third early warning level.
It will be appreciated that when the actual delivery rate is less than the product of the delivery rate threshold and the pre-set delivery factor, then the progress is severely blocked, and the progress is severely blocked. The determined second warning level is a high-level warning. And the generated corresponding early warning mark is a mark for marking serious progress blockage. Similarly, for example, if the progress is identified as being blocked according to the traffic lights, the warning mark corresponding to the third warning level is marked with a red light.
It is to be understood that the sequence of steps 402, 404, and 406 is not limited in the embodiment of the present invention, and is only used to distinguish different comparison results to generate different warning messages.
This is now explained with reference to an example of step 302. For example, if the development period is 7 days, the version monitoring period is every day, the number of store points to be delivered in the version monitoring period (that is, every day) is 42/7-6, the preset delivery rate threshold is 1, the preset delivery coefficient is 0.8, and if the number of store points actually delivered every day is 4, the actual delivery rate is 4/6-0.67-1-0.8, the corresponding early warning flag is determined to be a serious-jam flag of the progress, for example, a red light, if the number of store points actually delivered every day is 7, the actual delivery rate is 7/6>1, it is determined that the progress is not jammed, the early warning flag may be a green light, and if the number of store points actually delivered every day is 5, the actual delivery rate is 5/6, the actual delivery rate 5/6 is greater than 1, 0.8 is less than 1, the progress is in a light-slight-jam state, and the early warning flag may be a yellow light.
And step 310, sending the early warning information corresponding to the version delivery progress to the terminal.
Further, the server sends the early warning information corresponding to the version delivery progress to the terminal. Specifically, the server may directly send the warning information to the terminal. And an interface of a mail system can be called, and the early warning information corresponding to the version delivery progress is sent to the terminal in a mail mode. And an interface of an instant communication platform or a short message platform can be called, and the early warning information corresponding to the version delivery progress is sent to the terminal in the form of instant communication information or short messages. This is not limitative.
It is understood that the terminal herein refers to a terminal used by the warning processing personnel.
In the embodiment, the server acquires the total Story points corresponding to the current version and the preset development period corresponding to the current version; obtaining the number of Story points to be delivered in the preset monitoring period according to the preset development period and the total number of the Story points; acquiring the number of the actual delivery storeys points in a preset monitoring period, and obtaining the actual delivery rate according to the number of the actual delivery storeys points and the number of the stopys points to be delivered; reading a preset delivery rate threshold value from a database, comparing the actual delivery rate with the delivery rate threshold value, and generating early warning information corresponding to the version delivery progress according to the comparison result; and sending the early warning information corresponding to the version delivery progress to the terminal. The development delivery rate is monitored through the Story dimension, early warning information corresponding to the version delivery progress is generated, and therefore early warning processing personnel can be informed timely when the development delivery process is blocked. Therefore, the early warning processing personnel can timely know the reason of blockage, and can timely arrange and adjust to solve the problem of blockage. And further improves the software development efficiency.
As shown in fig. 5, in an embodiment, the method further includes a step of warning a defect processing progress, which specifically includes the following steps:
In this embodiment, the server may call an interface of the defect system, and obtain the defect information and the defect level corresponding to each defect information from the defect system.
Further, the server obtains the actual age for processing the defect information from the defect system. Wherein the aging (including actual aging and preset aging) for processing the defect information includes defect repair aging and/or defect verification aging.
And 504, searching for a preset aging corresponding to the defect grade, comparing the actual aging with the preset aging, and generating early warning information corresponding to the defect processing progress.
Specifically, the server is preset with a correspondence between the defect level and a preset aging. And searching for a preset aging corresponding to the defect grade according to the corresponding relation. Also, as described above, the pre-set age includes a defect repair age and/or a defect verification age. The server compares the actual aging with the preset aging, generates a corresponding early warning grade according to the comparison result, and generates early warning information corresponding to the defect processing progress according to the early warning grade.
Wherein one defect level corresponds to one or more preset aging.
In one embodiment, one defect level corresponds to one preset aging, the server compares the actual aging with the searched preset aging, and determines the corresponding early warning level according to the comparison result.
Specifically, when the actual aging is less than or equal to the preset aging, it is determined that the corresponding early warning level is a level that does not require early warning (e.g., zero level), and an early warning flag, such as a green light, corresponding to the early warning level is generated. And when the actual aging is greater than the preset aging, determining the time length that the actual aging exceeds the preset aging, and determining the corresponding early warning level according to the time length that the actual aging exceeds the preset aging. Furthermore, a plurality of segment time lengths are preset, a plurality of segment intervals are formed by taking the segment time lengths as segment points, different segment intervals correspond to different early warning levels, and the corresponding early warning levels are determined according to the segment intervals in which the exceeding time lengths are located. It can be understood that the number of the segmentation time points is not limited, and further, the number of the early warning grade division stages is not limited.
Furthermore, when the exceeding time length is less than or equal to the first subsection time length, corresponding to the primary early warning; when the exceeding time length is longer than the first subsection time length and is less than or equal to the second subsection time length, corresponding middle-level early warning is carried out; and when the exceeding time length is longer than the second section time length, corresponding to high-grade early warning. For example, if the exceeding time is greater than 0 and less than or equal to 4H, the corresponding primary early warning is performed; when the exceeding time is more than 8 and less than or equal to 8H, corresponding to middle-level early warning; and if the exceeding time is longer than 8H, corresponding to high-level early warning.
In another embodiment, one defect level corresponds to a plurality of preset aging times. The server takes a plurality of preset aging as segmentation points to form a plurality of reference intervals, different reference intervals correspond to different early warning levels, and the corresponding early warning levels are determined according to the reference interval where the actual aging is located. It can be understood that the number of the preset time periods is not limited, and further, the number of the division stages of the early warning grades is not limited.
Further, the preset aging is sequentially expressed as a first preset aging and a second preset aging from large to small. When the actual aging is less than or equal to the first preset aging, the level (such as zero level) which does not need early warning is corresponded; when the actual aging is larger than the first preset aging and smaller than or equal to the second preset aging, corresponding to middle-level early warning; and when the actual aging is larger than the second preset aging, corresponding to high-grade early warning. For example, the first preset aging is 4H, the second preset aging is 8H, and the actual aging is 7H, then the actual aging 7H is greater than the first preset aging 4H and less than the second preset aging 8H, so the corresponding early warning level is a middle-level early warning.
The server is preset with the corresponding relation between the early warning grade and the early warning information. And searching early warning information of the defect processing progress corresponding to the determined early warning level according to the corresponding relation. Wherein the early warning information comprises an early warning mark. Further, the warning mark includes a color mark or a graphic mark, etc. The specific representation form of the early warning mark is not limited, as long as different early warning levels can be identified and distinguished.
And step 506, sending the early warning information corresponding to the defect processing progress to the terminal.
And the server sends the early warning information corresponding to the defect processing progress to the terminal. Specifically, the server may directly transmit the warning information corresponding to the defect handling progress to the terminal. And an interface of a mail system can be called, and the early warning information corresponding to the defect processing progress is sent to the terminal in a mail mode. And an interface of an instant messaging platform or a short message platform can be called, and the early warning information corresponding to the defect processing progress is sent to the terminal in the form of instant messaging information or short messages. This is not limitative.
It is understood that the terminal herein refers to a terminal used by the warning processing personnel.
In one embodiment, a test execution rate threshold is also preset in the server. The server may also obtain the actual test execution rate. The actual test execution rate is obtained according to the ratio of the number of Story points actually completing the test to the number of Story points delivered by development.
And the server compares the actual test execution rate with a preset test execution rate threshold value and generates early warning information of the test processing progress according to the comparison result. Specifically, a test coefficient is preset in the server, wherein the test coefficient is a positive number smaller than 1. The server takes the product of the test system and the test execution rate threshold value as segmentation points respectively to form a plurality of comparison intervals, different comparison intervals correspond to different early warning levels, and the corresponding early warning levels are determined according to the comparison interval in which the actual test execution rate is located. And searching early warning information corresponding to the determined early warning level. The determined early warning information is the early warning information of the test processing progress.
It can be understood that, in one embodiment, the early warning information corresponding to the version delivery progress, the early warning information corresponding to the defect handling progress, and the early warning information corresponding to the test handling progress may be combined and sent to the terminal together. The 3 types of early warning information can be combined according to a preset early warning information combining template to generate a uniform early warning information, and the uniform early warning information is sent to the terminal.
As shown in fig. 6, in one embodiment, a software development progress warning apparatus 600 is provided. The device comprises an acquisition module 602, a storage point number determination module 604, a delivery rate determination module 606, an early warning information generation module 608 and a sending module 610, wherein:
the obtaining module 602 is configured to obtain total store points corresponding to a current version and a preset development period corresponding to the current version.
A storage point number determining module 604, configured to obtain the number of storage points to be delivered in the preset monitoring period according to the preset development period and the total number of storage points.
The delivery rate determining module 606 is configured to obtain the number of the storage points actually delivered within the preset monitoring period, and obtain the actual delivery rate according to the number of the storage points actually delivered and the number of the storage points to be delivered.
The early warning information generating module 608 is configured to read a preset delivery rate threshold from a database, compare the actual delivery rate with the delivery rate threshold, and generate early warning information corresponding to the version delivery progress according to a comparison result.
A sending module 610, configured to send the early warning information corresponding to the version delivery progress to a terminal.
In one embodiment, the store point determining module 604 is further configured to obtain a plurality of requirements corresponding to the current version and store points corresponding to the requirements; and obtaining the total Story points corresponding to the current version according to the Story points corresponding to the requirements.
In one embodiment, the early warning information generating module 608 is further configured to determine a first early warning level corresponding to the version delivery progress when the actual delivery rate is greater than or equal to the delivery rate threshold, and generate an early warning flag corresponding to the first early warning level; when the actual delivery rate is smaller than the delivery rate threshold and is larger than or equal to the product of the delivery rate threshold and a preset delivery coefficient, determining a second early warning level corresponding to the version delivery progress, and generating an early warning mark corresponding to the second early warning level; and when the actual delivery rate is smaller than the product of the delivery rate threshold and the preset delivery coefficient, determining a third early warning level corresponding to the version delivery progress, and generating an early warning mark corresponding to the third early warning level.
In one embodiment, the obtaining module 602 is further configured to call an interface of the defect system to obtain defect information and a corresponding defect level, and process an actual aging of the defect information. As shown in fig. 7, in this embodiment, the apparatus further includes:
and the searching module 607 is configured to search for the preset aging corresponding to the defect level.
In this embodiment, the warning information generating module 608 is further configured to compare the actual aging with the preset aging, and generate warning information corresponding to the defect processing progress;
the sending module 610 is further configured to send the warning information corresponding to the defect handling progress to the terminal.
In one embodiment, the pre-set age includes a defect repair age and/or a defect verification age.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the computer program is executed. The storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a Random Access Memory (RAM).
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (8)
1. A software development progress early warning method comprises the following steps:
acquiring a Story total point number corresponding to a current version and a preset development period corresponding to the current version; the Story is a function point with the minimum granularity;
obtaining the number of Story points to be delivered in a preset monitoring period according to the preset development period and the total number of the Story points; the preset monitoring period takes days or weeks as a unit;
acquiring the number of Story points actually delivered in the preset monitoring period, and obtaining the actual delivery rate in the preset monitoring period according to the number of the Story points actually delivered and the number of the Story points to be delivered;
reading a preset delivery rate threshold value from a database, comparing the actual delivery rate with the delivery rate threshold value, and generating early warning information corresponding to the version delivery progress according to the comparison result;
sending the early warning information corresponding to the version delivery progress to a terminal;
calling an interface of a defect system to acquire defect information and a corresponding defect grade, and processing the actual aging of the defect information;
searching a preset aging corresponding to the defect grade, comparing the actual aging with the preset aging, and generating early warning information corresponding to the defect processing progress;
sending the early warning information corresponding to the defect processing progress to the terminal;
the method for acquiring the total number of the Story points corresponding to the current version comprises the following steps:
the total number of storeys points corresponding to the current version is obtained from the correlation system in which the version division information is stored, or,
acquiring a plurality of requirements corresponding to the current version and Story points corresponding to the requirements, and acquiring Story total points corresponding to the current version according to the Story points corresponding to the requirements;
comparing the actual aging with the preset aging, and generating early warning information corresponding to the defect processing progress comprises:
when the actual time efficiency is less than or equal to the preset time efficiency, determining the corresponding early warning grade as a grade which does not need early warning, when the actual time efficiency is greater than the preset time efficiency, determining the corresponding early warning grade as a primary early warning according to the exceeding time length, when the exceeding time length is less than or equal to the first section time length, determining the corresponding early warning grade as a middle early warning, when the exceeding time length is greater than the first section time length and less than or equal to the second section time length, and determining the corresponding early warning grade as a high early warning;
the step of obtaining the number of the Story points to be delivered in the preset monitoring period according to the preset development period and the total number of the Story points comprises the following steps: and the server calculates the ratio of the preset monitoring period to the preset development period and then obtains the number of Story points to be delivered in the preset monitoring period according to the product of the ratio and the total number of the Story points.
2. The method according to claim 1, wherein the step of obtaining the total number of storeys points corresponding to the current version comprises:
acquiring a plurality of requirements corresponding to the current version and the number of Story points corresponding to each requirement;
and obtaining the total Story points corresponding to the current version according to the Story points corresponding to the requirements.
3. The method according to claim 1, wherein the step of generating the early warning information corresponding to the version delivery progress according to the comparison result comprises:
when the actual delivery rate is larger than or equal to the delivery rate threshold, determining a first early warning level corresponding to the version delivery progress, and generating an early warning mark corresponding to the first early warning level;
when the actual delivery rate is smaller than the delivery rate threshold and is larger than or equal to the product of the delivery rate threshold and a preset delivery coefficient, determining a second early warning level corresponding to the version delivery progress, and generating an early warning mark corresponding to the second early warning level;
and when the actual delivery rate is smaller than the product of the delivery rate threshold and the preset delivery coefficient, determining a third early warning level corresponding to the version delivery progress, and generating an early warning mark corresponding to the third early warning level.
4. The method of claim 1, wherein the pre-set age comprises a defect repair age and/or a defect verification age.
5. A software development progress early warning device, characterized in that the device comprises:
the acquisition module is used for acquiring the total Story points corresponding to the current version and the preset development period corresponding to the current version; the Story is a function point with the minimum granularity;
the Story point determining module is used for obtaining the Story points to be delivered in the preset monitoring period according to the preset development period and the total Story points; the preset monitoring period takes days or weeks as a unit; the step of obtaining the number of the Story points to be delivered in the preset monitoring period according to the preset development period and the total number of the Story points comprises the following steps: the server calculates the ratio of the preset monitoring period to the preset development period, and then the number of Story points to be delivered in the preset monitoring period is obtained according to the product of the ratio and the total number of the Story points;
the delivery rate determining module is used for acquiring the number of the actual delivery storeys points in the preset monitoring period and obtaining the actual delivery rate in the preset monitoring period according to the number of the actual delivery storeys points and the number of the corresponding delivery storeys points;
the early warning information generation module is used for reading a preset delivery rate threshold value from a database, comparing the actual delivery rate with the delivery rate threshold value and generating early warning information corresponding to the version delivery progress according to a comparison result;
the sending module is used for sending the early warning information corresponding to the version delivery progress to a terminal;
the searching module is used for searching for preset aging corresponding to the defect grade;
the acquiring module is also used for calling an interface of a defect system to acquire defect information and corresponding defect grades and processing the actual aging of the defect information;
the early warning information generation module is also used for comparing the actual aging with the preset aging to generate early warning information corresponding to the defect processing progress;
the sending module is further used for sending the early warning information corresponding to the defect processing progress to the terminal;
the method for acquiring the total number of the Story points corresponding to the current version comprises the following steps:
the total number of storeys points corresponding to the current version is obtained from the correlation system in which the version division information is stored, or,
acquiring a plurality of requirements corresponding to the current version and Story points corresponding to the requirements, and acquiring Story total points corresponding to the current version according to the Story points corresponding to the requirements;
comparing the actual aging with the preset aging, and generating early warning information corresponding to the defect processing progress comprises:
when the actual time efficiency is less than or equal to the preset time efficiency, determining the corresponding early warning grade as the grade without early warning, when the actual time efficiency is greater than the preset time efficiency, determining the corresponding early warning grade as the primary early warning according to the exceeding time length, when the exceeding time length is less than or equal to the first section time length, determining the corresponding early warning grade as the middle-grade early warning, when the exceeding time length is greater than the first section time length and less than or equal to the second section time length, and determining the corresponding early warning grade as the high-grade early warning.
6. The apparatus of claim 5, wherein the Story point determining module is further configured to obtain a plurality of requirements corresponding to a current version and Story points corresponding to each of the requirements; and obtaining the total Story points corresponding to the current version according to the Story points corresponding to the requirements.
7. The apparatus of claim 5, wherein the early warning information generating module is further configured to determine a first early warning level corresponding to a version delivery progress when the actual delivery rate is greater than or equal to the delivery rate threshold, and generate an early warning flag corresponding to the first early warning level; when the actual delivery rate is smaller than the delivery rate threshold and is larger than or equal to the product of the delivery rate threshold and a preset delivery coefficient, determining a second early warning level corresponding to the version delivery progress, and generating an early warning mark corresponding to the second early warning level; and when the actual delivery rate is smaller than the product of the delivery rate threshold and the preset delivery coefficient, determining a third early warning level corresponding to the version delivery progress, and generating an early warning mark corresponding to the third early warning level.
8. The apparatus of claim 5, wherein the pre-set age comprises a defect repair age and/or a defect verification age.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611239455.4A CN107679683B (en) | 2016-12-28 | 2016-12-28 | Software development progress early warning method and device |
| PCT/CN2017/099729 WO2018120891A1 (en) | 2016-12-28 | 2017-08-30 | Software development progress early warning method, device, server, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611239455.4A CN107679683B (en) | 2016-12-28 | 2016-12-28 | Software development progress early warning method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107679683A CN107679683A (en) | 2018-02-09 |
| CN107679683B true CN107679683B (en) | 2020-03-24 |
Family
ID=61133144
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611239455.4A Active CN107679683B (en) | 2016-12-28 | 2016-12-28 | Software development progress early warning method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107679683B (en) |
| WO (1) | WO2018120891A1 (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108737504A (en) * | 2018-04-25 | 2018-11-02 | 安徽沃屹智能装备有限公司 | A kind of software programmers' intelligent management system |
| CN108845943A (en) * | 2018-06-25 | 2018-11-20 | 郑州云海信息技术有限公司 | A kind of method and system that judgement software test stage is completed |
| CN111210099A (en) * | 2018-11-21 | 2020-05-29 | 鸿富锦精密电子（成都）有限公司 | Product aging information monitoring method and device and computer readable storage medium |
| CN110443480B (en) * | 2019-07-26 | 2023-10-27 | 中铁四局集团第一工程有限公司 | Construction progress monitoring and early warning method and system |
| CN113405608B (en) * | 2021-07-07 | 2022-11-18 | 淮南泰隆机械制造有限公司 | Iron wire galvanizing film monitoring system and working method thereof |
| CN115118571A (en) * | 2022-06-28 | 2022-09-27 | 中国平安财产保险股份有限公司 | Service monitoring method, platform, computer equipment and storage medium |
| CN115794045B (en) * | 2023-02-07 | 2023-05-12 | 山东信息职业技术学院 | Software development application data processing method based on big data |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102360465A (en) * | 2011-09-30 | 2012-02-22 | 镇江睿泰信息科技有限公司 | Software project schedule management method and system thereof |
| CN103092762A (en) * | 2013-02-19 | 2013-05-08 | 南京大学 | Real-time software defect detection method applicable to rapid software development model |
| US8458663B2 (en) * | 2008-02-14 | 2013-06-04 | International Business Machines Corporation | Static code analysis |
| CN105117348A (en) * | 2015-09-28 | 2015-12-02 | 佛山市朗达信息科技有限公司 | Method for monitoring test execution progress of software |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9654414B2 (en) * | 2014-09-18 | 2017-05-16 | International Business Machines Corporation | Scheduling cost efficient datacenter load distribution |
-
2016
- 2016-12-28 CN CN201611239455.4A patent/CN107679683B/en active Active
-
2017
- 2017-08-30 WO PCT/CN2017/099729 patent/WO2018120891A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8458663B2 (en) * | 2008-02-14 | 2013-06-04 | International Business Machines Corporation | Static code analysis |
| CN102360465A (en) * | 2011-09-30 | 2012-02-22 | 镇江睿泰信息科技有限公司 | Software project schedule management method and system thereof |
| CN103092762A (en) * | 2013-02-19 | 2013-05-08 | 南京大学 | Real-time software defect detection method applicable to rapid software development model |
| CN105117348A (en) * | 2015-09-28 | 2015-12-02 | 佛山市朗达信息科技有限公司 | Method for monitoring test execution progress of software |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2018120891A1 (en) | 2018-07-05 |
| CN107679683A (en) | 2018-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107679683B (en) | Software development progress early warning method and device | |
| US20110270770A1 (en) | Customer problem escalation predictor | |
| CN110442498B (en) | Abnormal data node positioning method and device, storage medium and computer equipment | |
| CN109685089B (en) | System and method for evaluating model performance | |
| CN109471783B (en) | Method and device for predicting task operation parameters | |
| CN110995459B (en) | Abnormal object identification method, device, medium and electronic equipment | |
| CN115330275B (en) | Echelon utilization method and device for retired battery | |
| CN112700131B (en) | AB test method and device based on artificial intelligence, computer equipment and medium | |
| CN113448862B (en) | Software version testing method and device and computer equipment | |
| CN110688536A (en) | Label prediction method, device, equipment and storage medium | |
| CN112632179A (en) | Model construction method and device, storage medium and equipment | |
| CN114896166A (en) | Scene library construction method and device, electronic equipment and storage medium | |
| CN115409283A (en) | Equipment failure prediction method, equipment failure prediction device, equipment and storage medium | |
| CN115237724A (en) | Data monitoring method, device, equipment and storage medium based on artificial intelligence | |
| CN103577882A (en) | Quantification project resource control method based on UML | |
| CN113469578A (en) | Multi-objective optimization-based business strategy generation method, device and system | |
| CN116843314A (en) | Monitoring terminal operation and maintenance management method, system, equipment and storage medium | |
| CN112163154A (en) | Data processing method, device, equipment and storage medium | |
| CN113076451B (en) | Abnormal behavior identification and risk model library establishment method and device and electronic equipment | |
| CN114968816A (en) | Data simulation-based strategy testing method, device, equipment and storage medium | |
| US20210027234A1 (en) | Systems and methods for analyzing user projects | |
| CN111625720B (en) | Method, device, equipment and medium for determining execution strategy of data decision item | |
| CN114356781A (en) | Software function testing method and device | |
| CN113934625A (en) | Software detection method, device and storage medium | |
| CN112199207A (en) | Alarm information pushing method, device, system, equipment and 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 |