WO2018120891A1 - 软件开发进度预警方法、装置、服务器和存储介质 - Google Patents

软件开发进度预警方法、装置、服务器和存储介质 Download PDF

Info

Publication number
WO2018120891A1
WO2018120891A1 PCT/CN2017/099729 CN2017099729W WO2018120891A1 WO 2018120891 A1 WO2018120891 A1 WO 2018120891A1 CN 2017099729 W CN2017099729 W CN 2017099729W WO 2018120891 A1 WO2018120891 A1 WO 2018120891A1
Authority
WO
WIPO (PCT)
Prior art keywords
early warning
preset
delivery rate
delivery
points
Prior art date
Application number
PCT/CN2017/099729
Other languages
English (en)
French (fr)
Inventor
邓智
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2018120891A1 publication Critical patent/WO2018120891A1/zh

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

Definitions

  • the present application relates to the field of computer technology, and in particular, to a software development progress warning method, apparatus, server, and storage medium.
  • Software development refers to the process of building a software system or software part of a system according to user requirements.
  • agile development that is, the evolution of the user's needs as the core and the method of software development using iterative and step-by-step methods
  • agile development is gradually welcomed by developers due to its rapid iteration and fast delivery.
  • a software development progress warning method is provided.
  • a method for early warning of software development progress including:
  • a software development progress warning device includes:
  • An obtaining module configured to obtain a total number of points corresponding to the current version and a preset development period corresponding to the current version
  • a delivery rate determining module configured to obtain a number of Store points actually delivered in the preset monitoring period, and obtain an actual delivery rate according to the actually delivered Story points and the number of Store points to be delivered;
  • the warning information generating module is configured to read a preset delivery rate threshold from the database, compare the actual delivery rate with the delivery rate threshold, and generate early warning information corresponding to the version delivery progress according to the comparison result;
  • a sending module configured to send the alert information corresponding to the version delivery progress to the terminal.
  • a server comprising a memory and a processor, wherein the memory stores computer readable instructions, the computer readable instructions being executed by the processor, such that the processor performs the step of: acquiring a Story corresponding to a current version a total number of points and a preset development period corresponding to the current version;
  • the early warning information corresponding to the version delivery schedule is sent to the terminal.
  • the early warning information corresponding to the version delivery schedule is sent to the terminal.
  • FIG. 1 is a schematic diagram of an application environment of an early warning method for software development progress in an embodiment
  • Figure 2 is a diagram showing the internal structure of a server in an embodiment
  • FIG. 3 is a schematic flow chart of an early warning method for software development progress in an embodiment
  • FIG. 4 is a schematic flow chart of a method for generating an early warning information in another embodiment
  • FIG. 5 is a schematic flowchart of a method for warning of defect processing progress in an embodiment
  • FIG. 6 is a structural block diagram of a software development progress warning device in an embodiment.
  • FIG. 1 is an application environment diagram of an early warning method for software development progress in an embodiment.
  • server 110 communicates with terminal 120 over a network.
  • the server 110 obtains the total number of points corresponding to the current version and the preset development period corresponding to the current version, and obtains the number of the points to be delivered in the preset monitoring period according to the preset development period and the total number of the points of the program. Further, the server 110 acquires the number of Store points actually delivered within the preset monitoring period, and obtains the actual delivery rate according to the actually delivered Story points and the number of Story points to be delivered.
  • the server 110 reads the preset delivery rate threshold from the database, compares the actual delivery rate with the delivery rate threshold, and generates warning information corresponding to the version delivery progress based on the comparison result.
  • the server 110 transmits the warning information corresponding to the version delivery progress to the terminal 120.
  • the terminal 120 includes, but is not limited to, various personal computers, smart phones, tablets, notebook computers, portable wearable devices, etc., which are not enumerated here.
  • FIG. 2 shows a schematic diagram of the internal structure of a server 110 in one embodiment, the server including a processor connected via a system bus, a non-volatile storage medium, an internal memory, and a network interface.
  • the non-volatile storage medium of the server stores an operating system, a database, and computer readable instructions
  • the database is used to store data, such as a preset delivery rate threshold.
  • the processor can be implemented to implement a software development progress warning method. This processor is used to provide computing and control capabilities to support the operation of the entire server.
  • the internal memory in the server can store computer readable instructions that, when executed by the processor, cause the processor to perform a software development progress alert method.
  • the network interface is used for network communication with the terminal, such as sending warning information to the terminal.
  • FIG. 2 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied.
  • the specific server may include a ratio. More or fewer components are shown in the figures, or some components are combined, or have different component arrangements.
  • a software development progress warning method is provided.
  • the method is applied to a server as an example.
  • the method specifically includes the following steps:
  • S302 Obtain a total number of points corresponding to the current version and a preset development period corresponding to the current version.
  • Story is the smallest granularity of function points.
  • a software version is equivalent to consisting of multiple stories.
  • the server will obtain the total number of points corresponding to the current version (that is, the version currently being developed) and the preset development period of the current version.
  • one Story corresponds to one point.
  • the total number of stories is the total number of stories.
  • the server may obtain the total number of total points corresponding to the current version directly from the associated system (hereinafter referred to as an association system) in which the version division information is stored (for example, an electronic signage system).
  • an association system in which the version division information is stored
  • the server may obtain a plurality of requirements corresponding to the current version and a number of the points corresponding to the respective requirements. Specifically, the server may obtain multiple requirements corresponding to the current version and correspond to the respective requirements from the associated system that stores the version division information. The number of Story points, or the multiple requirements corresponding to the current version stored by itself and the number of Story points corresponding to each requirement. This is not limited.
  • the version division information is the demand information into which the version is divided, the total number of points corresponding to the Story point information or the version, and the like.
  • the electronic signage system refers to a system that manages version information and version development processing information. It will be appreciated that the functionality of the electronic signage system is not limited to the above functions.
  • the server itself may also store version division information, and the server may obtain the stored version division information from its own database.
  • the preset development cycle refers to a period in which a developer is pre-set to develop the version. It can be understood that after the version development is completed, the version will be delivered to the testing department for version testing.
  • the number of Story points that should be delivered in the preset monitoring period is obtained according to the preset development period and the total number of the Story points.
  • a preset monitoring period is preset in the server.
  • the preset monitoring period may be in units of days, weeks, and the like. For example, it can be one day, or two days or one week.
  • the preset monitoring period refers to the period during which the progress detection and the generation of the warning information are generated.
  • the server will get the number of Story points that should be delivered within the preset monitoring period according to the preset development cycle and the total number of Story points. Specifically, the server may calculate a ratio of the preset version monitoring period to the preset development period, and then obtain the number of Story points that should be delivered within the preset monitoring period according to the product of the ratio and the total number of the points. It can be understood that "delivery” in this embodiment refers to going from development to testing, and not going online to production after completing the entire development test process.
  • Step 306 Acquire the number of Store points actually delivered in the preset monitoring period, and obtain the actual delivery rate according to the actual number of Stored Points and the number of Stored Points to be delivered.
  • the server will get the number of Story points actually delivered during the preset monitoring period. Specifically, the server may obtain the actually delivered Story points from the database, and may also invoke the interface of the associated system to obtain the number of Store points actually delivered within the preset monitoring period from the associated system. There is no limit to this.
  • the server obtains the actual delivery rate based on the ratio of the actually delivered Story points to the number of Story points to be delivered.
  • S308 Read a preset delivery rate threshold from the database, compare the actual delivery rate with the delivery rate threshold, and generate an early warning information corresponding to the version delivery progress according to the comparison result.
  • a pre-set delivery rate threshold is stored in the database.
  • the server reads the preset delivery rate threshold from the database.
  • the actual delivery rate is compared with a preset delivery rate threshold, and the warning information corresponding to the version delivery progress is generated according to the comparison result.
  • the early warning information includes early warning signs or early warning items (for example, early warning of development and delivery of this matter). It can also include the actual delivery rate and the preset delivery rate threshold, and the alignment between the two.
  • the warning mark is a mark capable of identifying the early warning strength or the warning level, and may include a color mark or a graphic mark to distinguish different early warning strengths or early warning levels.
  • the step of generating the early warning information corresponding to the version delivery progress according to the comparison result includes the following steps:
  • the delivery coefficient is preset in the server, wherein the delivery coefficient is a positive number less than one.
  • the server determines that the actual delivery rate is less than the delivery rate threshold and is greater than or equal to the product of the delivery rate threshold and the preset delivery coefficient, determining that the second delivery level corresponds to the version delivery schedule, thereby generating a second warning level corresponding to the second early warning level. Alert tag.
  • the second early warning level determined is an intermediate warning.
  • the corresponding warning flag generated is a flag indicating that the progress is slightly blocked.
  • the warning mark corresponding to the second warning level is marked with a yellow light.
  • sequence of the steps 402, 404, and 406 is not limited in the embodiment of the present application, and is only used to distinguish different comparison results to generate different early warning messages.
  • the server sends an alert message corresponding to the version delivery progress to the terminal.
  • the server can directly send the warning information to the terminal. It is also possible to call the interface of the mail system, and send the warning information corresponding to the progress of the version delivery to the terminal in the form of an email.
  • the interface of the instant messaging platform or the short message platform may also be invoked, and the early warning information corresponding to the version delivery progress is sent to the terminal in the form of an instant communication message or a short message. This is not limited.
  • the terminal here refers to the terminal used by the early warning processor.
  • the server obtains the total number of points corresponding to the current version and the preset development period corresponding to the current version; and obtains the number of Story points that should be delivered in the preset monitoring period according to the preset development period and the total number of the total points; and obtains the preset monitoring period.
  • the actual number of Store points delivered, the actual delivery rate is obtained according to the actual number of Story points delivered and the number of Story points to be delivered; the preset delivery rate threshold is read from the database, and the actual delivery rate is compared with the delivery rate threshold.
  • the result is generated with warning information corresponding to the version delivery schedule; the warning information corresponding to the version delivery progress is sent to the terminal.
  • the development of the delivery rate is monitored by the Story dimension, and the warning information corresponding to the version delivery schedule is generated, so that the early warning handler can be notified in time when the development delivery process is blocked.
  • the early warning personnel can know the cause of the blockage in time, and then can arrange and adjust in time to solve the problem causing the blockage. This improves the efficiency of software development.
  • the method further includes the step of early warning of the defect processing progress, specifically including the following steps:
  • S502 Call an interface of the defect system to acquire defect information and a corresponding defect level, and process the actual time limit of the defect information.
  • the server invokes the interface of the defect system, and obtains the defect information and the defect level corresponding to each defect information from the defect system.
  • the server also obtains the actual timeliness of processing the defect information from the defect system.
  • the timeliness of processing defect information includes defect repair aging and/or defect verification aging.
  • S504 Find a preset aging corresponding to the defect level, compare the actual aging with the preset aging, and generate the early warning information corresponding to the defect processing progress.
  • the correspondence between the defect level and the preset aging is preset in the server. According to the correspondence, the preset aging corresponding to the defect level is found. Likewise, as described above, the preset aging includes defect repair aging and/or defect verification aging. The server compares the actual aging with the preset aging, generates a corresponding warning level according to the comparison result, and generates an early warning information corresponding to the defect processing progress according to the warning level.
  • one defect level corresponds to one or more preset aging effects.
  • a defect level corresponds to a preset aging
  • the server compares the actual aging with the found preset aging, and determines a corresponding early warning level according to the comparison result.
  • the corresponding early warning level is a level that does not require early warning (such as zero level), and an early warning flag corresponding to the early warning level, such as a green light, is generated.
  • the actual aging is greater than the preset aging, it is determined that the actual aging exceeds the preset aging time, and the corresponding early warning level is determined according to the excess time.
  • a plurality of segmentation durations are preset, and a plurality of segmentation durations are used as segmentation points to form a plurality of segmentation intervals, and different segmentation intervals correspond to different early warning levels, and corresponding segments are determined according to segmentation intervals in which the duration is exceeded. Warning level. It can be understood that the number of segmentation time points is not limited here, and the number of division levels of the warning level is not limited.
  • the primary warning when the excess time is less than or equal to the first segment duration, the primary warning is corresponding; when the excess duration is greater than the first segment duration and less than or equal to the second segment duration, the intermediate alert is corresponding; when the excess time is greater than the second
  • the segmentation time when the segmentation time is long, it corresponds to the advanced warning.
  • the excess time when the excess time is greater than 0 and less than or equal to 4H, it corresponds to the primary warning; if the excess time is greater than 8 and less than or equal to 8H, it corresponds to the intermediate warning; if the excess is greater than 8H, it corresponds to the advanced warning.
  • one defect level corresponds to a plurality of preset aging.
  • the server will use multiple preset aging as segmentation points to form multiple reference intervals. Different reference intervals correspond to different early warning levels, and the corresponding early warning levels are determined according to the reference interval in which the actual aging is performed. Understandably, here is the default The number of aging is not limited, and the number of levels of the warning level is not limited.
  • the preset aging is sequentially expressed as a first preset aging and a second preset aging in descending order.
  • the level corresponding to the unwarranted (such as zero level) is corresponding;
  • the intermediate warning is corresponding;
  • the actual aging is greater than the second preset aging, it corresponds to the advanced warning.
  • the first preset aging is 4H
  • the second preset aging is 8H
  • the actual aging is 7H
  • 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 intermediate. Early warning.
  • the correspondence between the warning level and the warning information is preset in the server. According to the correspondence relationship, the early warning information of the defect processing progress corresponding to the determined warning level is searched for.
  • the warning information includes an early warning mark.
  • the warning mark includes a color mark or a graphic mark or the like.
  • the specific expression form of the warning mark is not limited, as long as it can identify different early warning levels.
  • the server will send the warning information corresponding to the defect processing progress to the terminal.
  • the server may directly send the warning information corresponding to the defect processing progress to the terminal.
  • the interface of the mail system may also be invoked, and the warning information corresponding to the progress of the defect processing is sent to the terminal in the form of an email.
  • the interface of the instant messaging platform or the short message platform may also be invoked, and the early warning information corresponding to the defect processing progress is sent to the terminal in the form of an instant communication message or a short message. This is not limited.
  • the terminal here refers to the terminal used by the early warning processor.
  • a test execution rate threshold is also preset in the server.
  • the server can also get the actual test execution rate. Among them, the actual test execution rate is obtained based on the ratio of the number of points of the actual completed test to the number of stored points of the development.
  • the server compares the actual test execution rate with the preset test execution rate threshold, and generates an early warning information of the test processing progress according to the comparison result.
  • the test coefficient is preset in the server, wherein the test coefficient is a positive number less than 1.
  • the server combines the product of the test system and the test execution rate threshold and the test execution rate threshold as segmentation points to form a plurality of comparison intervals, and different comparison intervals correspond to different warning levels, according to the comparison interval in which the actual test execution rate is located. Determine the corresponding warning level. Find the warning information corresponding to the determined warning level.
  • the determined warning information is the warning information of the test processing progress.
  • the early warning information corresponding to the version delivery schedule, the early warning information corresponding to the defect processing progress, and the early warning information corresponding to the test processing progress may be combined and sent to the terminal together.
  • the three types of early warning information may be combined according to a preset early warning information merge template to generate a unified early warning information, which is sent to the terminal.
  • a software development progress alert device 600 includes an obtaining module 602, a Story point determining module 604, a delivery rate determining module 606, an early warning information generating module 608, and a sending module 610, where:
  • the obtaining module 602 is configured to obtain a total number of points corresponding to the current version and a preset development period corresponding to the current version.
  • the story point determination module 604 is configured to obtain the number of Story points that should be delivered within the preset monitoring period according to the preset development period and the total number of the points of the Story.
  • the delivery rate determination module 606 is configured to obtain the actual number of Store points delivered in the preset monitoring period, and obtain an actual delivery rate according to the actually delivered Story points and the number of Store points that should be delivered.
  • the warning information generating module 608 is configured to read a preset delivery rate threshold from the database, compare the actual delivery rate with the delivery rate threshold, and generate early warning information corresponding to the version delivery progress according to the comparison result.
  • the sending module 610 is configured to send the early warning information corresponding to the version delivery progress to the terminal.
  • the Story point determination module 604 is further configured to acquire a plurality of requirements corresponding to the current version and a number of Story points corresponding to the respective requirements; and obtain, according to the number of the Store points corresponding to the respective requirements, the current version. Story total points.
  • the warning information generating module 608 is further configured to: when the actual delivery rate is greater than or equal to the delivery rate threshold, determine a first early warning level corresponding to the version delivery progress, and generate the first An early warning flag corresponding to the warning level; 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 preset delivery coefficient, determining a second early warning level corresponding to the version delivery progress, generating An early warning flag corresponding to the second warning level; when the actual delivery rate is less than a product of the delivery rate threshold and the preset delivery coefficient, determining a third early warning level corresponding to the version delivery progress, generating and The warning sign corresponding to the three warning levels.
  • the obtaining module 602 is further configured to invoke an interface of the defect system to obtain defect information. And the corresponding defect level, and the actual time limit for processing the defect information.
  • the device further includes:
  • the searching module 607 is configured to find a preset aging corresponding to the defect level.
  • the early warning information generating module 608 is further configured to compare the actual aging with the preset aging, and generate early warning information corresponding to the defect processing progress;
  • the sending module 610 is further configured to send the early warning information corresponding to the defect processing progress to the terminal.
  • the preset aging includes defect repair aging and/or defect verification aging.
  • the software development progress warning device provided by the present application may be implemented in the form of a computer program executable on a server as shown in FIG. 2, the non-volatile storage medium of the server
  • Each program module constituting the software development progress warning device may be stored, for example, the acquisition module 602, the Story point determination module 604, the delivery rate determination module 606, the early warning information generation module 608, and the transmission module 610 shown in FIG.
  • Each of the program modules includes computer readable instructions for causing the server to perform the steps in the software development progress warning method of various embodiments of the present application described in the present specification, for example, the server may The obtaining module 602 of the software development progress warning device 600 shown in FIG.
  • the server 6 acquires the total number of points corresponding to the current version and the preset development period corresponding to the current version, and obtains the total number of points according to the preset development period and the total number of points by the stored points determining module 604.
  • the server obtains the actual number of stored points in the preset monitoring period by using the delivery rate determining module 606, and obtains the actual delivery rate according to the actually delivered Story points and the number of stored points, and reads the preset from the database through the early warning information generating module 608.
  • the delivery rate threshold, the actual delivery rate is compared with the delivery rate threshold, and the warning information corresponding to the version delivery progress is generated according to the comparison result.
  • the server transmits the warning information corresponding to the version delivery progress to the terminal through the sending module 610.
  • the storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disk, or a read-only memory (ROM).

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Debugging And Monitoring (AREA)

Abstract

一种软件开发进度预警方法，包括：获取当前版本对应的Story总点数和所述当前版本对应的预设开发周期；根据所述预设开发周期和所述Story总点数得到预设监控周期内应交付的Story点数；获取所述预设监控周期内实际交付的Story点数，根据所述实际交付的Story点数和所述应交付的Story点数得到实际交付率；从数据库中读取预设的交付率阈值，将所述实际交付率与所述交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息；将所述与版本交付进度对应的预警信息发送至终端。

Description

软件开发进度预警方法、装置、服务器和存储介质
本申请要求于2016年12月28日提交中国专利局，申请号为2016112394554，申请名称为“软件开发进度预警方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，特别是涉及一种软件开发进度预警方法、装置、服务器和存储介质。
背景技术
软件开发，是指根据用户要求建造出软件系统或者系统中的软件部分的过程。在各种软件开发方法中，敏捷开发(即以用户的需求进化为核心，采用迭代、循序渐进的方法进行软件开发的方法)由于其快速迭代、快速交付的特性，逐渐受到开发人员的欢迎。
整个敏捷开发过程中，会涉及到开发、测试、缺陷修复等过程，其中一个环节的处理不及时就会影响到整个版本的开发进度。通常在版本开发过程中没有相关监控机制，在版本开发进度发生阻塞时，管理者往往不能够及时的获知到底是由哪一个环节或过程处理不及时而导致的，导致不能够及时的进行人员或工作方面的安排和调整来解决造成阻塞的问题，影响软件开发效率。
发明内容
根据本申请公开的各种实施例，提供一种软件开发进度预警方法、装置、服务器和存储介质。
一种软件开发进度预警方法，包括：
获取当前版本对应的Story总点数和所述当前版本对应的预设开发周期；
根据所述预设开发周期和所述Story总点数得到预设监控周期内应交付的 Story点数；
获取所述预设监控周期内实际交付的Story点数，根据所述实际交付的Story点数和所述应交付的Story点数得到实际交付率；
从数据库中读取预设的交付率阈值，将所述实际交付率与所述交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息；及
将所述与版本交付进度对应的预警信息发送至终端。
一种软件开发进度预警装置，包括：
获取模块，用于获取当前版本对应的Story总点数和所述当前版本对应的预设开发周期；
Story点数确定模块，用于根据所述预设开发周期和所述Story总点数得到预设监控周期内应交付的Story点数；
交付率确定模块，用于获取所述预设监控周期内实际交付的Story点数，根据所述实际交付的Story点数和所述应交付的Story点数得到实际交付率；
预警信息生成模块，用于从数据库中读取预设的交付率阈值，将所述实际交付率与所述交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息；及
发送模块，用于将所述与版本交付进度对应的预警信息发送至终端。
一种服务器，包括存储器和处理器，所述存储器中存储有计算机可读指令，所述计算机可读指令被所述处理器执行时，使得所述处理器执行如下步骤：获取当前版本对应的Story总点数和所述当前版本对应的预设开发周期；
根据所述预设开发周期和所述Story总点数得到预设监控周期内应交付的Story点数；
获取所述预设监控周期内实际交付的Story点数，根据所述实际交付的Story点数和所述应交付的Story点数得到实际交付率；
从数据库中读取预设的交付率阈值，将所述实际交付率与所述交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息；及
将所述与版本交付进度对应的预警信息发送至终端。
一个或多个存储有计算机可读指令的非易失性存储介质，所述计算机可读 指令被一个或多个处理器执行时，使得一个或多个处理器执行如下步骤：
获取当前版本对应的Story总点数和所述当前版本对应的预设开发周期；
根据所述预设开发周期和所述Story总点数得到预设监控周期内应交付的Story点数；
获取所述预设监控周期内实际交付的Story点数，根据所述实际交付的Story点数和所述应交付的Story点数得到实际交付率；
从数据库中读取预设的交付率阈值，将所述实际交付率与所述交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息；及
将所述与版本交付进度对应的预警信息发送至终端。
本申请的一个或多个实施例的细节在下面的附图和描述中提出。本申请的其它特征、目的和优点将从说明书、附图以及权利要求书变得明显。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为一个实施例中软件开发进度预警方法的应用环境示意图；
图2为一个实施例中服务器的内部结构图；
图3为一个实施例中软件开发进度预警方法的流程示意图；
图4为另一个实施例中预警信息生成方法的流程示意图；
图5为一个实施例中缺陷处理进度预警方法的流程示意图；
图6为一个实施例中软件开发进度预警装置的结构框图；及
图7为另一个实施例中软件开发进度预警装置的结构框图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅 用以解释本申请，并不用于限定本申请。
图1为一个实施例中软件开发进度预警方法的应用环境图。如图1所示，服务器110通过网络与终端120进行通信。服务器110获取当前版本对应的Story总点数和当前版本对应的预设开发周期，根据预设开发周期和Story总点数得到预设监控周期内应交付的Story点数。进一步，服务器110获取预设监控周期内实际交付的Story点数，根据实际交付的Story点数和应交付的Story点数得到实际交付率。服务器110从数据库中读取预设的交付率阈值，将实际交付率与交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息。服务器110将与版本交付进度对应的预警信息发送至终端120。
可以理解，终端120包括但不限于各种个人计算机、智能手机、平板电脑、笔记本电脑、便携式穿戴设备等，在此不一一列举。
图2示出了一个实施例中的服务器110的内部结构示意图，该服务器包括通过系统总线连接的处理器、非易失性存储介质、内存储器和网络接口。其中，该服务器的非易失性存储介质存储有操作系统、数据库和计算机可读指令，数据库用于存储数据，如预设交付率阈值等。该计算机可读指令被处理前执行时，可使得处理器实现一种软件开发进度预警方法。该处理器用于提供计算和控制能力，支撑整个服务器的运行。服务器中的内存储器可储存有计算机可读指令，该计算机可读指令被所述处理器执行时，可使得所述处理器执行一种软件开发进度预警方法。网络接口用于与终端进行网络通信，比如发送预警信息至终端。
本领域技术人员可以理解，图2中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的服务器的限定，具体的服务器可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
如图3所示，在一个实施例中，提供了一种软件开发进度预警方法，现以该方法应用于服务器为例进行举例说明，该方法具体包括以下步骤：
S302，获取当前版本对应的Story总点数和当前版本对应的预设开发周期。
可以理解，敏捷开发中，会将整个版本的开发划分为若干个需求，每个需求可以包括至少一个的故事(即Story)。其中，Story即为最小粒度的功能点。 一个软件版本相当于由多个Story组成。
服务器会获取当前版本(即当前进行开发的版本)对应的Story总点数和当前版本的预设开发周期。
其中，一个Story对应一个点数。Story总点数即为Story总数量。
具体地，可以是，服务器直接从存储有版本划分信息的关联系统(以下简称关联系统)(比如，电子看板系统)中获取当前版本对应的Story总点数。
也可以是，服务器获取当前版本对应的多个需求和与各个需求对应的Story点数，具体地，服务器可以从存储有版本划分信息的关联系统中获取当前版本对应的多个需求和与各个需求对应的Story点数，或获取自身存储的当前版本对应的多个需求和与各个需求对应的Story点数。对此不作限定。
进一步地，服务器会根据各个需求对应的Story点数得到与当前版本对应的Story总点数。具体地，服务器会将各个需求对应的Story点数进行求和计算得到与当前版本对应的Story总点数。比如，将版本划分成了18个需求，其中的2个需求分别包含5个Story，3个需求分别包括3个Story，10个需求分别包括2个Story以及3个需求分别包括1个Story。则与该版本对应的Story总点数＝2*5+3*3+10*2+3*1＝42。
可以理解，版本划分信息即为将版本划分成的需求信息和Story点数信息或版本对应的Story总点数等。电子看板系统，是指管理版本信息及版本开发处理信息的系统。可以理解，电子看板系统的功能并不局限于上述功能。
在其他实施例中，服务器自身也可以存储版本划分信息，服务器可以从自身数据库中获取存储的版本划分信息。
其中，预设开发周期，指预先设置的开发人员进行版本开发的周期。可以理解，版本开发完成后，会将版本交付至测试部门进行版本测试操作。
S304，根据预设开发周期和Story总点数得到预设监控周期内应交付的Story点数。
本实施例中，服务器中预先设置了预设监控周期。该预设监控周期可以是以天、周等为单位。比如，可以是一天、也可以是2天或1周等。预设监控周期，是指进行进度检测、生成预警信息的周期。
服务器会根据预设开发周期和Story总点数得到预设监控周期内应交付的Story点数。具体地，服务器可以计算预设版本监控周期与预设开发周期的比值，然后根据该比值与Story总点数的乘积得到预设监控周期内应交付的Story点数。可以理解，本实施例中的“交付”是指从开发交付至测试，而并非完成整个开发测试过程后上线至生产。
步骤306，获取预设监控周期内实际交付的Story点数，根据实际交付的Story点数和应交付的Story点数得到实际交付率。
服务器会获取预设监控周期内实际交付的Story点数。具体地，服务器可以从自身数据库中获取该实际交付的Story点数，也可以调用关联系统的接口，从关联系统中获取预设监控周期内实际交付的Story点数。对此不做限定。
进一步，服务器根据实际交付的Story点数和应交付的Story点数的比值，得到实际交付率。
S308，从数据库中读取预设的交付率阈值，将实际交付率与交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息。
具体地，数据库中存储了预先设置的交付率阈值。服务器从数据库中读取预设的交付率阈值。并将实际交付率与预设的交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息。
其中，预警信息包括预警标记或预警事项(比如，对开发交付这一事项进行预警)等。还可以包括实际交付率和预设的交付率阈值，及这两者之间的比对情况。进一步，预警标记是能够标识出预警强度或预警等级的标记，可以包括颜色标记或图形标记，以将不同的预警强度或预警等级进行区分标识。
在一个实施例中，如图4所示，根据比对结果生成与版本交付进度对应的预警信息的步骤(简称预警信息生成步骤)，具体包括以下步骤：
S402，当实际交付率大于或等于交付率阈值时，则确定出与版本交付进度对应的第一预警等级，生成与第一预警等级对应的预警标记。
本实施例中，当服务器判断出实际交付率大于或等于交付率阈值时，则确定与版本交付进度对应的是第一预警等级，进而生成与第一预警等级对应的预警标记。
可以理解，当实际交付率大于或等于交付率阈值时，则说明进度未出现阻塞，属于进度正常状态。则确定出的第一预警等级为零级预警。生成的对应预警标记，则为标识进度正常的标记。比如，可以根据红绿灯来标识进度是否阻塞，则该第一预警等级对应的预警标记为绿灯标记。
S404，当实际交付率小于交付率阈值且大于或等于交付率阈值和预设交付系数的乘积时，则确定出与版本交付进度对应的第二预警等级，生成与第二预警等级对应的预警标记。
本实施例中，服务器中预先设置了交付系数，其中交付系数为小于1的正数。当服务器判断出实际交付率小于交付率阈值且大于或等于交付率阈值和预设交付系数的乘积时，则确定与版本交付进度对应的是第二预警等级，进而生成与第二预警等级对应的预警标记。
可以理解，当实际交付率小于交付率阈值且大于或等于交付率阈值和预设交付系数的乘积时，则说明进度出现了一些阻塞，属于进度轻微阻塞状态。则确定出的第二预警等级为中级预警。生成的对应预警标记，则为标识进度轻微阻塞的标记。同样地，比如根据红绿灯来标识进度是否阻塞，则该第二预警等级对应的预警标记为黄灯标记。
S406，当实际交付率小于交付率阈值和预设交付系数的乘积时，则确定出与版本交付进度对应的第三预警等级，生成与第三预警等级对应的预警标记。
可以理解，当实际交付率小于交付率阈值和预设交付系数的乘积时，则说明进度出现了严重阻塞，属于进度严重阻塞状态。则确定出的第二预警等级为高级预警。生成的对应预警标记，则为标识进度严重阻塞的标记。同样地，比如根据红绿灯来标识进度是否阻塞，则该第三预警等级对应的预警标记为红灯标记。
可以理解，本申请实施例对步骤402、404及406的顺序不作限定，仅用于区分不同比对结果生成不同的预警消息。
现结合步骤302的例子进行解释说明。比如，开发周期为7天，版本监控周期为每天，则版本监控周期内(即每天)应交付的Story点数＝42/7＝6，预设的交付率阈值为1，预设交付系数为0.8，假设每天实际交付的Story点数为4， 则实际交付率＝4/6＝0.67＜1*0.8，则确定对应的预警标记为进度严重堵塞标记，比如红灯，假设每天实际交付的Story点数为7，则实际交付率＝7/6＞1，则说明进度未阻塞，预警标记可为绿灯，假设每天实际交付的Story点数为5，则实际交付率＝5/6，则该实际交付率5/6大于1*0.8小于1，则属于进度轻微阻塞状态，预警标记可为黄灯。
S310，将与版本交付进度对应的预警信息发送至终端。
进一步，服务器会将与版本交付进度对应的预警信息发送至终端。具体地，服务器可以直接将预警信息发送至终端。也可以调用邮件系统的接口，将与版本交付进度对应的预警信息以邮件的形式发送至终端。还可以调用即时通信平台或短信平台的接口，将与版本交付进度对应的预警信息以即时通信消息或短信的形式发送至终端。对此不作限定。
可以理解，这里的终端是指预警处理人员所使用的终端。
上述实施例中，服务器通过获取当前版本对应的Story总点数和当前版本对应的预设开发周期；根据预设开发周期和Story总点数得到预设监控周期内应交付的Story点数；获取预设监控周期内实际交付的Story点数，根据实际交付的Story点数和应交付的Story点数得到实际交付率；从数据库中读取预设的交付率阈值，将实际交付率与交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息；将与版本交付进度对应的预警信息发送至终端。即通过Story维度进行开发交付率的监控，并生成与版本交付进度对应的预警信息，进而在开发交付过程发生阻塞时，能够及时的告知预警处理人员。这样一来，预警处理人员及时获知发生阻塞的原因，就能够及时进行安排和调整，解决造成阻塞的该问题。进而提高了软件开发效率。
如图5所示，在一个实施例中，该方法还包括缺陷处理进度预警的步骤，具体包括以下步骤：
S502，调用缺陷系统的接口获取缺陷信息及对应的缺陷等级，以及处理所述缺陷信息的实际时效。
本实施例中，服务器会调用缺陷系统的接口，从缺陷系统中获取缺陷信息及各个缺陷信息所对应的缺陷等级。
进一步，服务器还会从缺陷系统中获取处理该缺陷信息的实际时效。其中，处理缺陷信息的时效(包括实际时效和预设时效)包括缺陷修复时效和/或缺陷验证时效。
S504，查找与缺陷等级对应的预设时效，将实际时效与预设时效进行比对，生成与缺陷处理进度对应的预警信息。
具体地，服务器中预先设置了缺陷等级和预设时效之间的对应关系。根据该对应关系，查找与缺陷等级对应的预设时效。同样地，如上文所述，预设的时效包括缺陷修复时效和/或缺陷验证时效。服务器会将实际时效与预设时效进行比对，根据比对结果生成对应的预警等级，根据预警等级生成与缺陷处理进度对应的预警信息。
其中，一个缺陷等级对应一个或多个预设时效。
在一个实施例中，一个缺陷等级对应一个预设时效，服务器将实际时效与该查找到的预设时效进行比对，根据比对结果确定出对应的预警等级。
具体地，当实际时效小于或等于该预设时效时，则确定对应的预警等级为不需预警的等级(比如零级)，则生成与该预警等级对应的预警标记，比如绿灯。当实际时效大于该预设时效时，则确定实际时效超出预设时效的时长，根据超出时长来确定对应的预警等级。进一步，预设多个分段时长，由多个分段时长作为分段点组成多个分段区间，不同的分段区间对应不同的预警等级，根据超出时长所处的分段区间确定出对应的预警等级。可以理解，这里对分段时长点的个数不做限定，进而对预警等级的划分级数也不做限定。
更进一步，当超出时长小于等于第一分段时长时，则对应初级预警；当超出时长大于第一分段时长且小于等于第二分段时长时，则对应中级预警；当超出时长大于第二分段时长时，则对应高级预警。比如，超出时长为大于0小于等于4H时，则对应初级预警；超出时长为大于8小于等于8H时，则对应中级预警；超出时长大于8H，则对应高级预警。
在另一个实施例中，一个缺陷等级对应多个预设时效。服务器会将多个预设时效作为分段点组成多个参考区间，不同的参考区间对应不同的预警等级，根据实际时效所处的参考区间确定出对应的预警等级。可以理解，这里对预设 时效的个数不做限定，进而对预警等级的划分级数也不做限定。
进一步，将预设时效按照由大到小的顺序依次表示为第一预设时效和第二预设时效。则当实际时效小于等于第一预设时效时，则对应不需预警的等级(比如零级)；当实际时效大于第一预设时效且小于等于第二预设时效时，则对应中级预警；当实际时效大于第二预设时效时，则对应高级预警。比如，第一预设时效为4H，第二预设时效为8H，实际时效为7H，则实际时效7H大于第一预设时效4H且小于第二预设时效8H，所以对应的预警等级是中级预警。
服务器中预先设置了预警等级与预警信息之间的对应关系。根据该对应关系，查找与确定出的预警等级对应的缺陷处理进度的预警信息。其中，预警信息包括预警标记。进一步，预警标记包括颜色标记或图形标记等。这里对预警标记的具体表现形式不作限定，只要能够标识区分不同的预警等级即可。
S506，将与缺陷处理进度对应的预警信息发送至终端。
服务器会将与缺陷处理进度对应的预警信息发送至终端。具体地，服务器可以直接将与缺陷处理进度对应的预警信息发送至终端。也可以调用邮件系统的接口，将与缺陷处理进度对应的预警信息以邮件的形式发送至终端。还可以调用即时通信平台或短信平台的接口，将与缺陷处理进度对应的预警信息以即时通信消息或短信的形式发送至终端。对此不作限定。
可以理解，这里的终端是指预警处理人员所使用的终端。
在一个实施例中，服务器中还预设了测试执行率阈值。服务器还可以获取实际的测试执行率。其中，实际测试执行率是根据实际完成测试的Story的点数与开发交付的Story点数的比值得到的。
服务器将实际测试执行率与预设测试执行率阈值进行比对，根据比对结果生成测试处理进度的预警信息。具体地，服务器中预设了测试系数，其中测试系数为小于1的正数。服务器将测试系统和测试执行率阈值的乘积、以及测试执行率阈值分别作为分段点，组成多个对照区间，不同的对照区间对应不同的预警等级，根据实际测试执行率所位于的对照区间来确定出对应的预警等级。查找与确定出的预警等级对应的预警信息。该确定出的预警信息即为测试处理进度的预警信息。
可以理解，在一个实施例中，可以将与版本交付进度对应的预警信息、与缺陷处理进度对应的预警信息以及与测试处理进度对应的预警信息进行合并，一起发送至终端。其中，可以是根据预设的预警信息合并模板，将这3种类型的预警信息进行合并，生成一份统一的预警信息，发送至终端。
如图6所示，在一个实施例中，提供了一种软件开发进度预警装置600。该装置包括获取模块602、Story点数确定模块604、交付率确定模块606、预警信息生成模块608以及发送模块610，其中：
获取模块602，用于获取当前版本对应的Story总点数和所述当前版本对应的预设开发周期。
Story点数确定模块604，用于根据所述预设开发周期和所述Story总点数得到预设监控周期内应交付的Story点数。
交付率确定模块606，用于获取所述预设监控周期内实际交付的Story点数，根据所述实际交付的Story点数和所述应交付的Story点数得到实际交付率。
预警信息生成模块608，用于从数据库中读取预设的交付率阈值，将所述实际交付率与所述交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息。
发送模块610，用于将所述与版本交付进度对应的预警信息发送至终端。
在一个实施例中，Story点数确定模块604还用于获取当前版本对应的多个需求和与各个所述需求对应的Story点数；根据各个所述需求对应的Story点数得到与所述当前版本对应的Story总点数。
在一个实施例中，预警信息生成模块608还用于当所述实际交付率大于或等于所述交付率阈值时，则确定出与版本交付进度对应的第一预警等级，生成与所述第一预警等级对应的预警标记；当实际交付率小于所述交付率阈值且大于或等于所述交付率阈值和预设交付系数的乘积时，则确定出与版本交付进度对应的第二预警等级，生成与所述第二预警等级对应的预警标记；当实际交付率小于所述交付率阈值和预设交付系数的乘积时，则确定出与版本交付进度对应的第三预警等级，生成与所述第三预警等级对应的预警标记。
在一个实施例中，获取模块602还用于调用缺陷系统的接口获取缺陷信息 及对应的缺陷等级，以及处理所述缺陷信息的实际时效。如图7所示，本实施例中，该装置还包括：
查找模块607，用于查找与所述缺陷等级对应的预设时效。
本实施例中，预警信息生成模块608还用于将所述实际时效与所述预设时效进行比对，生成与缺陷处理进度对应的预警信息；
发送模块610还用于将所述与缺陷处理进度对应的预警信息发送至所述终端。
在一个实施例中，预设时效包括缺陷修复时效和/或缺陷验证时效。
在一个实施例中，本申请提供的软件开发进度预警装置可以实现为一种计算机程序的形式，该计算机程序可在如图2所示的服务器上运行，所述服务器的非易失性存储介质可存储组成该软件开发进度预警装置的各个程序模块，比如，图6所示的获取模块602、Story点数确定模块604、交付率确定模块606、预警信息生成模块608以及发送模块610。各个程序模块中包括计算机可读指令，所述计算机可读指令用于使所述服务器执行本说明书中描述的本申请各个实施例的软件开发进度预警方法中的步骤，例如，服务器可以通过如图6所示的软件开发进度预警装置600中的获取模块602获取当前版本对应的Story总点数和当前版本对应的预设开发周期，并通过Story点数确定模块604根据预设开发周期和Story总点数得到预设监控周期内应交付的Story点数。服务器通过交付率确定模块606获取预设监控周期内实际交付的Story点数，根据实际交付的Story点数和应交付的Story点数得到实际交付率，并通过预警信息生成模块608从数据库中读取预设的交付率阈值，将实际交付率与交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息。服务器通过发送模块610将与版本交付进度对应的预警信息发送至终端。
在一个实施例中，提供了一个或多个存储有计算机可读指令的非易失性可读存储介质，该计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行上述各实施例方法中的全部或部分流程。上述的计算机可读指令为由上述各实施例方法中的全部或者部分流程实现的计算机程序对应的计算机可读指令。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，该计算机程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，前述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)等非易失性存储介质等。
以上所述实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对申请专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (20)

  1. 一种软件开发进度预警方法，包括：
    获取当前版本对应的Story总点数和所述当前版本对应的预设开发周期；
    根据所述预设开发周期和所述Story总点数得到预设监控周期内应交付的Story点数；
    获取所述预设监控周期内实际交付的Story点数，根据所述实际交付的Story点数和所述应交付的Story点数得到实际交付率；
    从数据库中读取预设的交付率阈值，将所述实际交付率与所述交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息；及
    将所述与版本交付进度对应的预警信息发送至终端。
  2. 根据权利要求1所述的方法，其特征在于，所述获取当前版本对应的Story总点数包括：
    获取当前版本对应的多个需求和与各个所述需求对应的Story点数；及
    根据各个所述需求对应的Story点数得到与所述当前版本对应的Story总点数。
  3. 根据权利要求1所述的方法，其特征在于，所述根据比对结果生成与版本交付进度对应的预警信息包括：
    当所述实际交付率大于或等于所述交付率阈值时，则确定出与版本交付进度对应的第一预警等级，生成与所述第一预警等级对应的预警标记；
    当实际交付率小于所述交付率阈值且大于或等于所述交付率阈值和预设交付系数的乘积时，则确定出与版本交付进度对应的第二预警等级，生成与所述第二预警等级对应的预警标记；及
    当实际交付率小于所述交付率阈值和预设交付系数的乘积时，则确定出与版本交付进度对应的第三预警等级，生成与所述第三预警等级对应的预警标记。
  4. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    调用缺陷系统的接口获取缺陷信息及对应的缺陷等级，以及处理所述缺 陷信息的实际时效；
    查找与所述缺陷等级对应的预设时效，将所述实际时效与所述预设时效进行比对，生成与缺陷处理进度对应的预警信息；及
    将所述与缺陷处理进度对应的预警信息发送至所述终端。
  5. 根据权利要求4所述的方法，其特征在于，所述预设时效包括缺陷修复时效和/或缺陷验证时效。
  6. 一种软件开发进度预警装置，包括：
    获取模块，用于获取当前版本对应的Story总点数和所述当前版本对应的预设开发周期；
    Story点数确定模块，用于根据所述预设开发周期和所述Story总点数得到预设监控周期内应交付的Story点数；
    交付率确定模块，用于获取所述预设监控周期内实际交付的Story点数，根据所述实际交付的Story点数和所述应交付的Story点数得到实际交付率；
    预警信息生成模块，用于从数据库中读取预设的交付率阈值，将所述实际交付率与所述交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息；及
    发送模块，用于将所述与版本交付进度对应的预警信息发送至终端。
  7. 根据权利要求6所述的装置，其特征在于，所述Story点数确定模块还用于获取当前版本对应的多个需求和与各个所述需求对应的Story点数；根据各个所述需求对应的Story点数得到与所述当前版本对应的Story总点数。
  8. 根据权利要求6所述的装置，其特征在于，所述预警信息生成模块还用于当所述实际交付率大于或等于所述交付率阈值时，则确定出与版本交付进度对应的第一预警等级，生成与所述第一预警等级对应的预警标记；当实际交付率小于所述交付率阈值且大于或等于所述交付率阈值和预设交付系数的乘积时，则确定出与版本交付进度对应的第二预警等级，生成与所述第二预警等级对应的预警标记；当实际交付率小于所述交付率阈值和预设交付系数的乘积时，则确定出与版本交付进度对应的第三预警等级，生成与所述第 三预警等级对应的预警标记。
  9. 根据权利要求6所述的装置，其特征在于，所述获取模块还用于调用缺陷系统的接口获取缺陷信息及对应的缺陷等级，以及处理所述缺陷信息的实际时效；
    所述装置还包括：
    查找模块，用于查找与所述缺陷等级对应的预设时效；
    所述预警信息生成模块还用于将所述实际时效与所述预设时效进行比对，生成与缺陷处理进度对应的预警信息；
    所述发送模块还用于将所述与缺陷处理进度对应的预警信息发送至所述终端。
  10. 根据权利要求9所述的装置，其特征在于，所述预设时效包括缺陷修复时效和/或缺陷验证时效。
  11. 一种服务器，包括存储器和处理器，所述存储器中存储有计算机可读指令，所述计算机可读指令被所述处理器执行时，使得所述处理器执行如下步骤：
    获取当前版本对应的Story总点数和所述当前版本对应的预设开发周期；
    根据所述预设开发周期和所述Story总点数得到预设监控周期内应交付的Story点数；
    获取所述预设监控周期内实际交付的Story点数，根据所述实际交付的Story点数和所述应交付的Story点数得到实际交付率；
    从数据库中读取预设的交付率阈值，将所述实际交付率与所述交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息；及
    将所述与版本交付进度对应的预警信息发送至终端。
  12. 根据权利要求11所述的服务器，其特征在于，所述处理器所执行的所述获取当前版本对应的Story总点数包括：
    获取当前版本对应的多个需求和与各个所述需求对应的Story点数；及
    根据各个所述需求对应的Story点数得到与所述当前版本对应的Story总 点数。
  13. 根据权利要求11所述的服务器，其特征在于，所述处理器所执行的所述根据比对结果生成与版本交付进度对应的预警信息包括：
    当所述实际交付率大于或等于所述交付率阈值时，则确定出与版本交付进度对应的第一预警等级，生成与所述第一预警等级对应的预警标记；
    当实际交付率小于所述交付率阈值且大于或等于所述交付率阈值和预设交付系数的乘积时，则确定出与版本交付进度对应的第二预警等级，生成与所述第二预警等级对应的预警标记；及
    当实际交付率小于所述交付率阈值和预设交付系数的乘积时，则确定出与版本交付进度对应的第三预警等级，生成与所述第三预警等级对应的预警标记。
  14. 根据权利要求11所述的服务器，其特征在于，所述计算机可读指令还使得所述处理器执行以下步骤：
    调用缺陷系统的接口获取缺陷信息及对应的缺陷等级，以及处理所述缺陷信息的实际时效；
    查找与所述缺陷等级对应的预设时效，将所述实际时效与所述预设时效进行比对，生成与缺陷处理进度对应的预警信息；及
    将所述与缺陷处理进度对应的预警信息发送至所述终端。
  15. 根据权利要求14所述的服务器，其特征在于，所述预设时效包括缺陷修复时效和/或缺陷验证时效。
  16. 一个或多个存储有计算机可读指令的非易失性存储介质，所述计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行如下步骤：
    获取当前版本对应的Story总点数和所述当前版本对应的预设开发周期；
    根据所述预设开发周期和所述Story总点数得到预设监控周期内应交付的Story点数；
    获取所述预设监控周期内实际交付的Story点数，根据所述实际交付的 Story点数和所述应交付的Story点数得到实际交付率；
    从数据库中读取预设的交付率阈值，将所述实际交付率与所述交付率阈值进行比对，根据比对结果生成与版本交付进度对应的预警信息；及
    将所述与版本交付进度对应的预警信息发送至终端。
  17. 根据权利要求16所述的非易失性存储介质，其特征在于，所述处理器所执行的所述获取当前版本对应的Story总点数包括：
    获取当前版本对应的多个需求和与各个所述需求对应的Story点数；及
    根据各个所述需求对应的Story点数得到与所述当前版本对应的Story总点数。
  18. 根据权利要求16所述的非易失性存储介质，其特征在于，所述处理器所执行的所述根据比对结果生成与版本交付进度对应的预警信息包括：
    当所述实际交付率大于或等于所述交付率阈值时，则确定出与版本交付进度对应的第一预警等级，生成与所述第一预警等级对应的预警标记；
    当实际交付率小于所述交付率阈值且大于或等于所述交付率阈值和预设交付系数的乘积时，则确定出与版本交付进度对应的第二预警等级，生成与所述第二预警等级对应的预警标记；及
    当实际交付率小于所述交付率阈值和预设交付系数的乘积时，则确定出与版本交付进度对应的第三预警等级，生成与所述第三预警等级对应的预警标记。
  19. 根据权利要求16所述的非易失性存储介质，其特征在于，所述计算机可读指令还使得所述处理器执行以下步骤：
    调用缺陷系统的接口获取缺陷信息及对应的缺陷等级，以及处理所述缺陷信息的实际时效；
    查找与所述缺陷等级对应的预设时效，将所述实际时效与所述预设时效进行比对，生成与缺陷处理进度对应的预警信息；及
    将所述与缺陷处理进度对应的预警信息发送至所述终端。
  20. 根据权利要求19所述的非易失性存储介质，其特征在于，所述预设 时效包括缺陷修复时效和/或缺陷验证时效。
PCT/CN2017/099729 2016-12-28 2017-08-30 软件开发进度预警方法、装置、服务器和存储介质 WO2018120891A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611239455.4A CN107679683B (zh) 2016-12-28 2016-12-28 软件开发进度预警方法和装置
CN201611239455.4 2016-12-28

Publications (1)

Publication Number Publication Date
WO2018120891A1 true WO2018120891A1 (zh) 2018-07-05

Family

ID=61133144

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/099729 WO2018120891A1 (zh) 2016-12-28 2017-08-30 软件开发进度预警方法、装置、服务器和存储介质

Country Status (2)

Country Link
CN (1) CN107679683B (zh)
WO (1) WO2018120891A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110443480A (zh) * 2019-07-26 2019-11-12 中铁四局集团第一工程有限公司 一种施工进度监控预警方法及系统
CN111210099A (zh) * 2018-11-21 2020-05-29 鸿富锦精密电子（成都）有限公司 产品时效信息监控方法、装置及计算机可读存储介质
CN113405608A (zh) * 2021-07-07 2021-09-17 淮南泰隆机械制造有限公司 一种铁丝镀锌膜监测系统及其工作方法
CN113778993A (zh) * 2021-09-14 2021-12-10 北京沃东天骏信息技术有限公司 一种业务数据的处理方法和装置
CN113806437A (zh) * 2021-09-29 2021-12-17 浪潮卓数大数据产业发展有限公司 一种基于Linux服务器的数据交付方法、设备、存储介质
CN114372709A (zh) * 2022-01-11 2022-04-19 中国工商银行股份有限公司 项目测试风险监控方法及装置
CN115118571A (zh) * 2022-06-28 2022-09-27 中国平安财产保险股份有限公司 业务监控方法、平台、计算机设备及存储介质
CN115794045A (zh) * 2023-02-07 2023-03-14 山东信息职业技术学院 基于大数据的软件开发应用数据处理方法

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108737504A (zh) * 2018-04-25 2018-11-02 安徽沃屹智能装备有限公司 一种软件编程人员用智能管理系统
CN108845943A (zh) * 2018-06-25 2018-11-20 郑州云海信息技术有限公司 一种判断软件测试阶段性完成的方法及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103092762A (zh) * 2013-02-19 2013-05-08 南京大学 一种适用于快速软件开发模式的实时软件缺陷检测方法
CN105117348A (zh) * 2015-09-28 2015-12-02 佛山市朗达信息科技有限公司 一种监控软件测试执行进度的方法
US20160087909A1 (en) * 2014-09-18 2016-03-24 International Business Machines Corporation Scheduling cost efficient datacenter load distribution

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8458663B2 (en) * 2008-02-14 2013-06-04 International Business Machines Corporation Static code analysis
CN102360465A (zh) * 2011-09-30 2012-02-22 镇江睿泰信息科技有限公司 软件项目进度管理方法及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103092762A (zh) * 2013-02-19 2013-05-08 南京大学 一种适用于快速软件开发模式的实时软件缺陷检测方法
US20160087909A1 (en) * 2014-09-18 2016-03-24 International Business Machines Corporation Scheduling cost efficient datacenter load distribution
CN105117348A (zh) * 2015-09-28 2015-12-02 佛山市朗达信息科技有限公司 一种监控软件测试执行进度的方法

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111210099A (zh) * 2018-11-21 2020-05-29 鸿富锦精密电子（成都）有限公司 产品时效信息监控方法、装置及计算机可读存储介质
CN110443480A (zh) * 2019-07-26 2019-11-12 中铁四局集团第一工程有限公司 一种施工进度监控预警方法及系统
CN110443480B (zh) * 2019-07-26 2023-10-27 中铁四局集团第一工程有限公司 一种施工进度监控预警方法及系统
CN113405608A (zh) * 2021-07-07 2021-09-17 淮南泰隆机械制造有限公司 一种铁丝镀锌膜监测系统及其工作方法
CN113778993A (zh) * 2021-09-14 2021-12-10 北京沃东天骏信息技术有限公司 一种业务数据的处理方法和装置
CN113806437A (zh) * 2021-09-29 2021-12-17 浪潮卓数大数据产业发展有限公司 一种基于Linux服务器的数据交付方法、设备、存储介质
CN114372709A (zh) * 2022-01-11 2022-04-19 中国工商银行股份有限公司 项目测试风险监控方法及装置
CN115118571A (zh) * 2022-06-28 2022-09-27 中国平安财产保险股份有限公司 业务监控方法、平台、计算机设备及存储介质
CN115794045A (zh) * 2023-02-07 2023-03-14 山东信息职业技术学院 基于大数据的软件开发应用数据处理方法
CN115794045B (zh) * 2023-02-07 2023-05-12 山东信息职业技术学院 基于大数据的软件开发应用数据处理方法

Also Published As

Publication number Publication date
CN107679683A (zh) 2018-02-09
CN107679683B (zh) 2020-03-24

Similar Documents

Publication Publication Date Title
WO2018120891A1 (zh) 软件开发进度预警方法、装置、服务器和存储介质
US9652507B2 (en) Dynamic interest-based notifications
CN109685089B (zh) 评估模型性能的系统及方法
CN113987074A (zh) 分布式服务全链路监控方法、装置、电子设备及存储介质
CN112650685B (zh) 自动化测试方法、装置、电子设备及计算机存储介质
CN111818136A (zh) 数据处理方法、装置、电子设备及计算机可读介质
WO2019047482A1 (zh) 应用程序兼容性测试方法、装置、计算机设备和存储介质
CN107193714B (zh) 一种告警展示方法及装置
WO2019019356A1 (zh) 应用程序测试方法、装置、计算机设备和存储介质
CN113190427B (zh) 卡顿监控方法、装置、电子设备及存储介质
CN109254922A (zh) 一种服务器BMC Redfish功能的自动化测试方法及装置
CN110728498A (zh) 一种信息交互方法和装置
CN113051245A (zh) 用于迁移数据的方法、装置及系统
CN109189677B (zh) 一种针对变量数值更新状态的测试方法及装置
US11741588B2 (en) Systems and methods for visual anomaly detection in a multi-display system
US11734057B2 (en) Method and apparatus for processing a service of an abnormal server
CN113132429B (zh) 用于推送消息的方法和装置
US9530112B2 (en) Common conditions for past projects as evidence for success causes
CN113468053B (zh) 一种应用系统的测试方法和装置
CN113704079B (zh) 基于Protobuf的接口测试方法和装置
CN114928603A (zh) 客户端软件的升级方法、装置、电子设备和介质
CN114710397A (zh) 服务链路的故障根因定位方法、装置、电子设备及介质
CN111090574B (zh) 一种回归测试方法、装置及存储介质
CN117592311B (zh) 一种工作流的多等级模拟方法、装置、设备及可读介质
US9264323B2 (en) Controlling computer nodes through social media

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17886505

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 17.09.2019)

122 Ep: pct application non-entry in european phase

Ref document number: 17886505

Country of ref document: EP

Kind code of ref document: A1