CN113537955A

CN113537955A - Milestone project management device and method, electronic equipment and storage medium

Info

Publication number: CN113537955A
Application number: CN202111090801.8A
Authority: CN
Inventors: 李太友; 李博雅; 林剑玮; 孙硕; 刘芳
Original assignee: Tianjin Zhongxin Zhiguan Information Technology Co ltd
Current assignee: Tianjin Zhongxin Zhiguan Information Technology Co ltd
Priority date: 2021-09-17
Filing date: 2021-09-17
Publication date: 2021-10-22

Abstract

The embodiment of the invention discloses a milestone project management device, a milestone project management method, a storage medium and electronic equipment. Wherein the milestone project management means comprises: the system comprises a milestone information management module, a milestone display module and a milestone display module, wherein the milestone information management module is used for determining project milestones associated with a current user, acquiring the milestone information in the project milestones and transmitting the project milestones and the corresponding milestone information to the milestone display module, and the project milestones at least comprise the first two stages of the following three-stage nodes: the system comprises a parent milestone, a plurality of child milestones included in the parent milestone and key task nodes included in each child milestone; and the milestone display module is used for forming a milestone interface based on the project milestones and the corresponding milestone information and rendering the milestone interface on a preset display interface. By forming the milestone interface, the method is convenient for quickly browsing and looking up the related information of the project milestone through the milestone interface, and simplifies the information management and query process.

Description

Milestone project management device and method, electronic equipment and storage medium

Technical Field

The embodiment of the invention relates to the technical field of computers, in particular to a milestone project management device and method, electronic equipment and a storage medium.

Background

With the increasing scale and complexity of software, it becomes increasingly important to scientifically manage development projects during software development. The project planning, development, maintenance and other different stages are usually responsible for different departments, and all the departments need to cooperate with each other, so that the daily management of the project is increasingly complicated.

The existing project management method has the problems of low management efficiency, complex flow and the like, the means for creating tasks are complex, the rules are unclear, each department is inconvenient to carry out task connection, and mistakes are easy to make.

Disclosure of Invention

The embodiment of the invention provides a milestone project management device and method, electronic equipment and a storage medium, so as to realize accurate management of multi-project information.

In a first aspect, an embodiment of the present invention provides a milestone project management apparatus, including:

the system comprises a milestone information management module, a milestone display module and a milestone display module, wherein the milestone information management module is used for determining project milestones associated with a current user, acquiring milestone information in the project milestones and transmitting the project milestones and corresponding milestone information to the milestone display module, and the project milestones at least comprise the first two stages of the following three-stage nodes: the system comprises a parent milestone, a plurality of child milestones included in the parent milestone and key task nodes included in each child milestone, wherein the execution state of each node at the next level in the project milestone determines the execution progress and the execution state of the node at the previous level;

and the milestone display module is used for forming a milestone interface based on the project milestones and the corresponding milestone information and rendering the milestone interface on a preset display interface.

In a second aspect, an embodiment of the present invention further provides a milestone project management method, including:

acquiring project milestones associated with a current user and milestone information in the project milestones, and sending the project milestones and corresponding milestone information to a milestone display module, wherein the project milestones at least comprise the first two levels of the following three-level nodes: the system comprises a parent milestone, a plurality of child milestones included in the parent milestone and key task nodes included in each child milestone, wherein the execution state of each node at the next level in the project milestone determines the execution progress and the execution state of the node at the previous level;

and forming a milestone interface based on the project milestone and the corresponding milestone information, and rendering the milestone interface on a preset display interface.

In a third aspect, an embodiment of the present invention further provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the computer program to implement the milestone item management method according to any embodiment of the present invention.

In a fourth aspect, the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the milestone project management method according to any embodiment of the present invention.

According to the technical scheme provided by the embodiment of the invention, the project milestone comprises a plurality of levels of information management frameworks, and each framework is provided with an execution state or an execution progress. By setting the project milestones, the execution state and the execution progress of each level of nodes can be obtained and recorded, and the information of each node in the project can be managed and inquired conveniently. By determining the project milestones associated with the current user, interference of irrelevant information is avoided, and the effectiveness and pertinence of the information are improved. The milestone information of the project milestones related to the current user is formed into a milestone interface to display the milestone information, so that the method is convenient for quickly browsing and looking up the related information of the project milestones through the milestone interface, and the information management and query process is simplified.

Drawings

Fig. 1 is a schematic structural diagram of a milestone project management apparatus according to an embodiment of the present invention;

FIG. 2 is a schematic illustration of a milestone interface provided by an embodiment of the invention;

FIG. 3 is a schematic diagram of a milestone interface provided by an embodiment of the invention;

FIG. 4 is a schematic illustration of a milestone interface provided by an embodiment of the invention;

FIG. 5 is a schematic diagram of a detail display interface for project milestones provided by embodiments of the present invention;

FIG. 6 is a schematic diagram of a man-hour display area provided by an embodiment of the present invention;

FIG. 7 is a diagram illustrating a display manner of target data according to an embodiment of the present invention;

FIG. 8 is a schematic illustration of a milestone interface provided by an embodiment of the invention;

FIG. 9 is a flowchart illustrating a milestone project management method according to an embodiment of the invention;

fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.

Fig. 1 is a schematic structural diagram of a milestone project management apparatus according to an embodiment of the present invention, where the milestone project management apparatus includes a milestone information management module 110 and a milestone display module 120. Wherein,

the milestone information management module 110 is configured to determine a project milestone associated with a current user, acquire milestone information in the project milestone, and send the project milestone and corresponding milestone information to the milestone display module, where the project milestone includes at least the first two of the following three levels of nodes: the system comprises a parent milestone, a plurality of child milestones included in the parent milestone and key task nodes included in each child milestone, wherein the execution state of each node at the next level in the project milestone determines the execution progress and the execution state of the node at the previous level;

the milestone display module 120 is configured to form a milestone interface based on the project milestones and the corresponding milestone information, and render the milestone interface on a preset display interface.

In this embodiment, the project milestone is a multi-level process architecture created based on an execution process of the project, where the project milestone may include three levels of architectures, such as a parent milestone, a child milestone, and a mission critical node, where the parent milestone is a one-level architecture, the child milestone is a two-level architecture, the mission critical node is a three-level architecture, and multiple child milestones may be included in the parent milestone, and each child milestone may include multiple mission critical nodes. In some embodiments, the project milestones may be tertiary structures formed by including parent milestones, child milestones, and mission-critical nodes, and in some embodiments, the project milestones may be secondary structures formed by including parent milestones and child milestones, without limitation.

The multiple child milestones within the same parent milestone may be in a sequential triggering relationship or may be in a simultaneous execution relationship, without limitation. The different sub-milestones can be executed by different departments or different execution objects in the same department, and similarly, the plurality of key task nodes in the same sub-milestone can be executed by different departments or different execution objects in the same department, which is not limited herein.

Each level of architecture in the project milestone is provided with an execution state or an execution progress, the execution state of each node of the next level in the project milestone determines the execution progress and the execution state of the node of the previous level, the execution progress of the node of the previous level is the proportion of the node of which the execution state is finished in each node of the next level, and when the execution progress of the node of the previous level is finished or 100%, the execution state is switched from processing to finishing. And each level of nodes in the project milestone are a father milestone, a child milestone and a key task node in sequence. Specifically, the execution state of each sub-milestone affects the execution progress of the parent milestone, and the execution state of each key task node affects the execution progress of the sub-milestone. By setting the project milestones, the execution state and the execution progress of each level of nodes can be obtained and recorded, and the information of each node in the project can be managed and inquired conveniently.

For any project, one or more project milestones can be corresponding, each project milestone is respectively provided with a user authority or a participating user identifier, further, each sub-milestone in the same father milestone is provided with different user authorities or different participating user identifiers, and each key task node in the same father milestone can be provided with different user authorities or different participating user identifiers. The milestone information management module 110 obtains the user information of the current device, i.e., the current user information, which may be determined by login information, for example. Optionally, determining an associated project milestone based on the user authority of the current user information, determining a project milestone with user authority among a plurality of project milestones based on the authority of the current user information, that is, the project milestone associated with the current user, exemplarily, determining whether the current user information has the user authority of a parent milestone, and if so, determining the project milestone as the project milestone associated with the current user; if the current user information does not have the user authority of the parent milestone, sequentially determining whether the current user information has the user authority of each child milestone, and if so, determining the project milestone to which the child milestone belongs as the project milestone associated with the current user.

Optionally, the project milestones associated with the current user may also be determined based on the current user information and the participating user identifications of the project milestones. Specifically, the participating user identifiers of the project milestones are obtained, matching is performed on the basis of the user identifiers in the current user information and the participating user identifiers of the project milestones, and if matching is successful, the project milestone is determined to be the project milestone associated with the current user.

By determining the project milestones associated with the current user, interference of irrelevant information is avoided, and the effectiveness and pertinence of the information are improved. Meanwhile, the searching or editing of the project milestones by irrelevant users is avoided, and the information safety is improved.

The milestone display module 120 obtains milestone information of the project milestones associated with the current user, and the milestone information is used for generating a milestone interface, wherein the milestone information may be a set of information of each node in the project milestones. In some embodiments, the milestone display module 120 is configured to obtain all node information of a project milestone associated with the current user, and in some embodiments, the milestone display module 120 is configured to obtain corresponding milestone information based on user permissions of the current user, for example, if the current user has user permissions of parent milestones in the project milestone, obtain all node information in the project milestone, obtain the milestone information, and if the current user has user permissions of local (one or more) child milestones in the project milestone, obtain node information of local child milestones with user permissions, to form the milestone information.

In some embodiments, the milestone display module 120 obtains node information containing a user identification of the current user to form milestone information. For example, if the participating user id of the parent milestone in the project milestone includes the user id of the current user, all the node information in the project milestone is obtained, and if the participating user id of the local (one or more) child milestones in the project milestone includes the user id of the current user, the node information of the local child milestones is obtained to form the milestone information.

On the basis of the above embodiment, the milestone information includes, but is not limited to, one or more items of the execution status, the target data, and the attribute tag of each parent milestone, the execution status, the target data, and the executor information of each child milestone, and the execution information, the execution progress, and the execution status of each mission critical node in each child milestone. The milestone information for display acquired by the milestone display module 120 may be one or more of the above-mentioned information. Wherein, each father milestone is respectively provided with a father milestone name or a mark, such as XXX project, and the like, which can be determined according to the actual requirement of the project. The target data for each parent milestone may include, but is not limited to, a target time for completion of execution, a target revenue for completion of execution, and the like. Each parent project milestone may also be provided with an attribute tag, which may be determined according to the project attribute of each parent project milestone, for example, if the project attribute of the parent project milestone is a financial-type project, the attribute tag may be a financial attribute tag of a financial setting, such as CW-001, CW-002, etc. It is understood that the attribute tag of the parent milestone, once set, may be inherited by each sub-milestone and each key task node therebelow, for example, the parent milestone is provided with the attribute tag aa, each sub-milestone and each key task node therebelow have the attribute tag aa, and each sub-milestone and each key task node may further add other attribute tags according to their own characteristics on the basis of inheriting the attribute tag, for example, the attribute tag of the sub-milestone 1 under the parent milestone includes the attribute tag aa and the attribute tag bb, and the attribute tag of the key task node 1 under the sub-milestone 1 includes the attribute tag aa, the attribute tag bb and the attribute tag cc. Each sub-milestone is respectively provided with a sub-milestone name or identification, such as project starting, project design and the like, and the sub-milestone names or identifications can be set according to the actual requirements of projects. The execution states of the sub-milestones include non-starting, in execution, execution completion, suspension, stop, overdue and the like, and the execution states of the sub-milestones depend on the execution states of the key task nodes in the sub-milestones. The target data for the sub-milestones may include, but is not limited to, a target time for completion of the performance, a target revenue for completion of the performance, and the like. Mission critical node performance information is information performed by each mission critical node, such as, but not limited to, controlling device a to complete a first mission, purchasing a predetermined number of devices B, or receiving a remittance M, etc.

The milestone display module 120 sends the acquired milestone information to the milestone display module 120, and the milestone display module 120 forms a milestone interface based on the milestone information to display the milestone information, so that the milestone display module can be conveniently used for quickly browsing and looking up related information of the project milestones through the milestone interface, and the information management and query process is simplified.

The milestone display module 120 may form a display interface corresponding to the milestone information of each project milestone through a preset display layout or a preset display template, and render the display interface at the device side. In some embodiments, a milestone information display area is included in the milestone interface for displaying a plurality of project milestones.

In some embodiments, the milestone interface displays the key information of each project milestone, so that a user can conveniently and quickly view the key information of a plurality of project milestones through the milestone interface, and the interference of a large amount of information is avoided. Accordingly, the milestone information management module 110 is further configured to: extracts a preset type of display information (i.e., preset key information) from the milestone information, and transmits the extracted preset type of display information to the milestone display module 120. Accordingly, the milestone display module 120 forms a milestone interface based on the project milestones and the extracted preset type of display information.

The different types of project milestones correspond to the different types of display information, which can be preset, the types of the display information are determined according to the types of the project milestones, and the preset types of display information are extracted from the acquired milestone information. For example, the preset type of display information may be display information including an execution status of a parent milestone, target data, and an execution status, an execution progress, and target data of attribute tags and child milestones. In some embodiments, the preset type of display information may be set according to a user requirement, for example, the milestone information management module 110 stores the information type set by the user in advance, and extracts the display information of the information type from the obtained milestone information to form a personalized milestone interface meeting the user requirement, so that the display flexibility and diversity of the milestone interface are improved. For example, the target data selected by user a may be a target time and the target data selected by user B may be a target revenue.

On the basis of the embodiment, the milestone interface can have various display modes, and the milestone information can be displayed in different display modes according to the requirements of users. Optionally, the milestone display module 120 is configured to: acquiring a milestone interface type, calling an interface template corresponding to the milestone interface type, updating the interface template with the structure of the project milestone, and adding corresponding milestone information to the corresponding position of the updated interface template to form a milestone interface conforming to the milestone interface type. The milestone interface types can include, but are not limited to, a form type, a calendar type, a crossroad graph type, a mixed arrangement type and the like, different milestone interface types are respectively and correspondingly stored with interface templates, when a selection operation for any one of the milestone interface types is detected, the corresponding interface template is called, and the milestone interface corresponding to the selected milestone interface type is obtained by displaying the milestone information based on the called interface model.

Optionally, the milestone display module 120 is configured with an expansion interface, and the expansion interface can obtain the interface type of the newly added milestone and the interface template corresponding to the interface type of the newly added milestone, store the newly added interface template, and set a corresponding selection control based on the interface type of the newly added milestone, so as to facilitate selection by a user in a subsequent display process. Optionally, after the milestone interface is displayed, a switching instruction of the type of the milestone interface may be received, where the switching instruction of the type of the milestone interface includes the switched type of the milestone interface, an interface template corresponding to the type of the milestone interface is called to form a switched milestone interface, and the switched milestone interface is rendered to display the switched milestone interface.

In the embodiment, by setting the multiple milestone interface types, the user can conveniently select and switch according to the requirements, the variety of the milestone information display is improved, the requirements of different users are met, and the applicability of the milestone information display is improved.

In some alternative embodiments, the milestone interface includes a display area for a plurality of project milestones; the display area of any project milestone comprises a sub display area of a parent milestone and a sub display area of each sub milestone, and the parent milestone and each sub milestone are respectively displayed in the corresponding sub display areas in the form of cards. For example, referring to fig. 2, fig. 2 is a schematic diagram of a milestone interface according to an embodiment of the present invention. Each of the display areas of the project milestones in fig. 2 includes a sub-display area of a parent milestone and a sub-display area of a plurality of sub-milestones, wherein the number of the sub-display areas is determined according to the number of the sub-milestones in the parent milestone, and different project milestones may include different numbers of the sub-milestones, which is not limited thereto. It should be noted that fig. 2 is only a schematic diagram, and in this embodiment, the number of sub-milestones in each project milestone is not limited. Meanwhile, the display layout of the parent milestone and the child milestone in fig. 2 is also an example, and other layout manners may be adopted in other milestone interface types, which is not limited to this.

The sub display area of the parent milestone is used for displaying one or more items of the name, the attribute tag, the affiliated item information, the execution state and the target data of the parent milestone, and the sub display area of the sub milestone is used for displaying the key information corresponding to the sub milestone, such as the target data, the execution state, the execution progress and the like. Each sub-display area displays the information in the form of a card.

In some optional embodiments, in each sub-display area, different information display manners are invoked based on the information type of the milestone information for display. The information display mode includes, but is not limited to, a text mode and a graphic mode, wherein the text mode may be a display mode including different fonts, different colors and different font sizes, and the graphic mode may include, but is not limited to, a histogram mode, a progress bar mode, a circle scale mode, and the like. Illustratively, referring to fig. 3, fig. 3 is a schematic diagram of a milestone interface provided by an embodiment of the invention. In fig. 3, "day 15 of month 4", "day 24 of month 8", and the like are target dates displayed in text form, and 3/10, 0/4, and the like are execution progress, and may be displayed in text form by displaying "completed", "overdue", "due soon", and "not started", "in progress", and "suspended" in text form as execution states. Optionally, the display mode of the information is determined based on the information type, and the milestone display module 120 stores the display modes of different information types, for example, the display mode of the target date is a year, month and day mode, the execution progress is displayed in a circular scale mode, and the like. After receiving the milestone information sent by the milestone information management module 110, the milestone display module 120 invokes a corresponding display mode based on the information type of each piece of milestone information, and renders corresponding milestone information based on the display mode. The display mode of each information type stored in the milestone information can be edited and set by the user in advance, so that personalized display meeting the requirements of the user is realized.

Optionally, the milestone display module 120 stores preset information for performing differentiated display and a display mode corresponding to the information, for example, the display mode of the status information "completion" may be green, four-size character, song style, and the display mode of the status information "overdue" may be yellow, three-size character, song style, and bold. The milestone display module 120 performs keyword recognition on each piece of milestone information after receiving the milestone information sent by the milestone information management module 110, and calls a corresponding display mode if the milestone information includes information for performing differential display, so that the information is displayed differentially, and high suggestive performance is achieved.

In fig. 3, the current user does not have the user right of the sub-milestone a6, or the current user is not a participating user of the sub-milestone a6, and does not acquire the milestone information of the sub-milestone a6, and the sub-display area corresponding to the sub-milestone a6 is displayed in the form of a blank card.

On the basis of the embodiment, the information of each level of nodes in the project milestone changes along with the change of time, and the obtained milestone information and the updated milestone interface are updated according to the change information, so that the real-time performance of the information in the milestone interface is improved.

The milestone information management module 110 is further configured to: if the execution state change of any key task node in the project milestones is detected, updating the associated information of the child milestones to which the key task nodes belong and the associated information of the parent milestones to which the key task nodes belong, or if the execution state change of the parent milestones is detected, updating the associated information of the child milestones in the parent milestones and the associated information of the key task nodes, or if the execution state change of the child milestones is detected, updating the associated information of the parent milestones to which the child milestones belong and the associated information of the key task nodes in the child milestones; the updated milestone information is transmitted to the milestone display module, or the updated milestone information is stored and transmitted to the milestone display module 120 upon receiving the milestone display request.

In this embodiment, the execution state and the execution progress of the parent milestone depend on the execution state of each child milestone, and the execution state of each child milestone depend on the execution states of a plurality of mission-critical nodes included in the child milestone. Similarly, the execution state and the execution progress of the parent milestone can also adversely affect the execution states of the child milestones and the mission-critical nodes under the parent milestone, and the execution states of the child milestones and the execution progress of the mission-critical nodes can also affect the execution states of the parent milestones and the mission-critical nodes under the child milestones. Namely, the execution states and the execution progress of the parent milestone, the child milestone and the key task node are mutually related and influenced, and the change of the execution state and the execution progress of any one node can influence the change of the other two related information. Illustratively, the change information of the execution state of each key task node in each project milestone is detected in real time. When the execution state of any key task node changes, the influence on the child milestone and the affiliated parent milestone exists, and correspondingly, when the execution state change of any key task node is detected, the associated information of the affiliated child milestone corresponding to the execution state change is determined. Alternatively, the associated information may be an execution progress of the sub-milestone, for example, the execution progress 0/4 in fig. 3 indicates that the sub-milestone includes four key task nodes, the number of key task nodes completed is 0, and when the execution state of one key task node in the sub-milestone is switched to be completed, the execution progress of the sub-milestone is changed to 1/4. Alternatively, the associated information may be an execution status of a sub-milestone, for example, the execution progress of the sub-milestone is 3/4, and if the execution status of a key task node that is not executed and completed in the sub-milestone is changed to be completed, the execution progress of the sub-milestone is changed to 4/4, and accordingly, the execution status of the sub-milestone is changed to be completed, and further, the execution progress of a parent milestone to which the sub-milestone belongs is increased by 1, that is, the associated information of the parent milestone to which the key task node belongs is the execution progress.

And updating the acquired milestone information based on the information changes of the parent milestone, the child milestone and the key task node, and regenerating a new milestone interface through the updated milestone information, so that the real-time updating of the information in the milestone interface is ensured, and the information delay is avoided.

Optionally, after determining the changed milestone information, the changed milestone information is sent to the milestone display module 120, and the milestone display module 120 updates the milestone interface based on the changed milestone information, and updates only the changed milestone information, thereby reducing the amount of updated information and reducing the amount of calculation.

Optionally, the updated milestone information is stored, and a new milestone interface is generated according to a preset time interval. Wherein the preset time interval may be according to user settings, for example, may be 10 seconds, 1 minute or 10 minutes, a day, etc. And updating the milestone interface at a preset time interval to avoid resource occupation caused by frequent updating of the milestone interface. For example, different project milestones may be set at different preset time intervals to meet the display requirements of different projects.

Optionally, the updated milestone information is stored, and a new milestone interface is generated according to the milestone display request. Wherein the milestone display request can be generated when the milestone control is selected or when a refresh operation is detected in the milestone interface.

In the detection of the above embodiment, the change of the execution state of the mission-critical node may be implemented in different forms. Optionally, the milestone information management module 110 generates execution state change information when detecting that the state control at any of the mission-critical nodes is switched. The mission-critical node may be configured with a state control, which may be, for example, a button control that triggers the milestone information management module 110 to generate execution state change information when the button control is clicked; the state control may also be a selection control, and the selection control may include at least two options, such as incomplete and complete, or the selection control includes two display states, and when the option or the display state of the selection control is switched, the milestone information management module 110 is triggered to generate execution state change information. The switching operation of the state control can be realized by clicking operation by a user. It should be noted that, when receiving a switching operation of a state control at any key task node, which is input by a user, verifying user information, and if the user information has a user right of state change, or the user information is a participating user of the key task node, continuing to execute the switching operation; if the user information does not have the user authority of state change and the user is determined not to be a participating user of the key task node based on the user information, the switching operation is ignored, so that the accuracy of the change of the milestone information is ensured, and the misoperation of an unrelated user is avoided.

Optionally, the milestone information management module 110 matches the received message with the execution information of each key task node, and if the matching is successful, generates execution state change information. The message may be any form of message, such as a mail, a short message, an instant messaging message, etc., the sender and the receiver of the message are determined, and the matching key task node is determined based on the sender and the receiver, specifically, whether the message includes a name or an identifier of the key task node is determined, and if yes, the key task node is determined as the matching key task node. Or, it may be determined whether the sender and the receiver of the message satisfy the preset participation objects of the key task node, for example, both the sender and the receiver are participating users of the key task node, or the sender and the sender are one of the associated device and the participating user of the key task node, respectively, and then the key task node is determined as the matching key task node.

And matching the received message with the execution information of the determined key task node. For example, the execution information of the mission-critical node may be "device a arrives at a good", and when the arrival information of the device a is received, the matching with the execution information of the mission-critical node is successful, and it is determined that the execution state of the mission-critical node is changed to be completed, that is, the execution state change information is generated, and is used to change the execution state of the mission-critical node to be completed.

By matching the received message with the execution information of the key task node and generating the execution state change information when the matching is successful, the situation that a user manually switches the execution state is replaced, the information management mode is simplified, and the automation of information management is improved.

Optionally, the milestone information management module 110 receives completion information sent by a key task node, a child milestone or a parent milestone with preset association relationship, and generates execution state change information. In this embodiment, association relationships are preset between nodes in different project milestones, where the association relationships may include, but are not limited to, pre-trigger completion, post-trigger completion, synchronous completion, pre-trigger start, post-trigger start, number size restriction relationships, and the like. The pre-triggering completion triggers the execution completion of the nodes in the current project milestone for the execution completion of the associated nodes; the post-triggering completion is the execution completion of the associated node at the execution completion position of the node in the current project milestone; when the synchronous completion is that the associated node and the node in the current project milestone are both in execution completion, triggering the execution states of the associated node and the node to be switched to completion; the pre-triggering starting is that the execution of the associated node is completed to trigger the execution starting of the node in the current project milestone; the post-trigger initiation is the initiation of execution of the associated node where execution of the node in the current project milestone is complete. The two nodes provided with the association relationship may be any one of a key task node, a child milestone and a parent milestone, for example, the key task node and the key task node have an association relationship therebetween, the key task node and the child milestone have an association relationship therebetween, the milestone and the parent milestone have an association relationship therebetween, and the like, which is not limited herein. The two nodes provided with the association relationship may be respectively located in two different project milestones, or may also be located in the same project milestone.

The milestone information management module 110 detects that when any node receives completion information sent by an associated node, execution state change information is generated based on the association relationship between the node and the associated node, for example, if the association relationship is pre-trigger start, the generated execution state change information is used for switching the execution state from non-start to processing; and if the correlation is that the preposition trigger is completed, the generated execution state change information is used for switching the execution state from processing to completion. Optionally, the milestone information management module 110 determines whether the node exists in a post-associated node after receiving the information of completion of execution of any node in the project milestone, and if so, generates execution state change information based on the information of completion of execution and sends the execution state change information to the post-associated node.

By setting the incidence relation among different nodes, the execution states of different departments or different users are transmitted in time through the incidence relation, the efficiency of information transmission and information management is improved, and the delay and the error of artificially transmitting the information are avoided.

On the basis of the above embodiment, the milestone information management module 110 is further configured to: acquiring preset target time of each node in each project milestone; and generating countdown prompt information when the prompt condition corresponding to the target time is met. The method comprises the steps that target time can be set in a father milestone, each child milestone and each key task node in a project milestone respectively, the target time of each node in the father milestone, each child milestone and each key task node is obtained, whether the current time meets a prompt condition is determined for the target time of any node, the prompt condition can be that the time length from the target time is less than the preset time length, if yes, countdown prompt information is generated and displayed in a prompt area of the corresponding node, countdown prompt is convenient for a user, and prompt degree is increased. Optionally, the node performing countdown prompting may be determined according to the importance of each node in the project milestone, for example, the node with the higher importance level is determined as the node performing countdown prompting, so as to prompt the importance of the node, and avoid interference of the non-important node. Optionally, the prompting conditions corresponding to different nodes are different, that is, the time lengths from the target time are different, and the prompting conditions may be set according to the node grade or user requirements, which is not limited. Optionally, the countdown prompting message of the specific node is sent to the milestone display module 120, so that the milestone display module 120 displays the countdown prompting message on the milestone interface. The specific node may be a parent milestone, each child milestone, or a node whose importance level meets a preset requirement, a preset node, or the like.

Optionally, the milestone information management module 110 is further configured to: when the execution state change is not detected in the target time of any node in the project milestone, generating prompt information based on the attribute information of the node, and sending the prompt information to the milestone display module, wherein the milestone display module displays the prompt information in a preset prompt area, and illustratively, the preset prompt area may be a milestone display area, an instant chat display area (that is, the prompt information is sent as instant chat information), or a mail display area (that is, the prompt information is sent as mail), and the like. The attribute information of the node may include, but is not limited to, a node identifier, and a node participating user. By setting the preset prompting area, the prompting information of different project milestones can be displayed in the preset prompting area, so that a user can conveniently check all the prompting information in the preset prompting area without entering a detailed interface of the project milestones, and the prompting performance of the user is enhanced.

In some embodiments, the reminder information may be a strong reminder information, which may be an information including @. The strong reminding information may be configured to be displayed differently, for example, an unprocessed identifier or a differentiated display identifier is set, and when the execution state of the corresponding node is changed to be completed, the strong reminding information is triggered to cancel the differentiated display of the strong reminding information, for example, the unprocessed identifier or the differentiated display identifier is cancelled. Through setting up strong warning information, avoid the problem that the promptness of conventional information reduces after the user clicks, improve the validity of suggestion.

On the basis of the above embodiment, the milestone information management module 110 is further configured to: responding to an information sending instruction at any node, and sending the milestone information corresponding to the node to a receiver of the information sending instruction, wherein the node is any one of a father milestone, a child milestone and a key task node. The receiving party may be any one of the parent milestone, the child milestone and the key task node of any project milestone, that is, all participating users corresponding to any one of the parent milestone, the child milestone and the key task node, or the receiving party may be participating users in the parent milestone, the child milestone and the key task node of any project milestone.

And when the information sending control of any node (namely any one of the parent milestone, the child milestone and the key task node of a project milestone) is detected to be triggered, generating an information sending instruction. The milestone information corresponding to the information sending node is obtained, for example, the milestone information may be packaged into a data packet and transmitted to the receiving party based on a preset information sending form, where the preset information sending form may be a mail or any instant messaging method, which is not limited to this. By transmitting the milestone information corresponding to the nodes, information interaction among different milestones is realized.

On the basis of the above embodiment, one or more of the parent milestone, each child milestone and each key task node in the project milestone is provided with associated device information, the associated devices include but are not limited to computers, mobile phones, task execution devices such as lathes, vehicles, printers, sensors and the like, and the associated device information includes but is not limited to device identifications of the associated devices, control conditions of the associated devices and preset control information; the control condition of the associated device may be a preset execution state of the node, for example, the start, completion or execution progress meets a preset threshold, and the preset control information may be state control information or parameter adjustment information on the associated device, where the state control information of the associated device is used to control the start, pause, stop, and the like of the associated device, and the parameter adjustment information may include a target parameter or a parameter adjustment value, and the like, which is not limited to this. Optionally, the same node may be provided with multiple associated devices, and associated device information of different associated devices may be the same or different.

Accordingly, the milestone information management module 110 is further configured to: and if the state information of any one of the parent milestone, the child milestone and the key task node is detected to be switched to a preset execution state, sending control information to associated equipment based on corresponding associated equipment information. When any one of the parent milestone, the child milestone and the key task node is switched in the execution state, whether the node switched in the execution state is provided with associated equipment information is determined, if yes, whether the switched execution state meets the control condition of the associated equipment is determined, if yes, corresponding control information is called or produced, and the control information is sent to the associated equipment based on the associated equipment identification, so that the automatic control of the associated equipment is realized, the control process of the equipment is simplified, and the control efficiency of the equipment is improved.

Optionally, any one of the parent milestone, the child milestone and the key task node in the project milestone receives the associated information sent by the associated device, and the milestone information management module 110 stores and displays the associated information. The associated information may be a task execution progress of the associated device, a device exception parameter, and the like, which is not limited herein. By receiving the associated information sent by the associated equipment, the acquiring process of the equipment information is simplified, and meanwhile, the associated information of the associated equipment is stored, so that the subsequent inquiry and management of the associated information are facilitated, further, the associated information is displayed, a user can conveniently acquire the latest associated information, and the inquiring process of the equipment information is omitted.

On the basis of the above embodiment, the milestone information management module 110 is further configured to: classifying a plurality of project milestones to be displayed based on the sub-milestone information in each project milestone; the milestone display module is used for performing aggregation display on project milestones in the same category. In this embodiment, the different project milestones may include the same or different sub-milestones, the plurality of project milestones are classified by the sub-milestone identifiers, and the plurality of project milestones are displayed in an aggregated manner based on the classification result, thereby improving the reasonability of the project milestone display. Illustratively, project milestones with the same sub-milestone identification are classified into the same category. And regarding the project milestones in the same category, using the same sub-milestone marks as shared information, and displaying the display cards corresponding to the sub-milestones in the project milestones at the corresponding positions of the shared sub-milestone marks. Illustratively, referring to fig. 4, fig. 4 is a schematic diagram of a milestone interface provided by an embodiment of the invention. In fig. 4, project milestone 1 and project milestone 2 have the same sub-milestone identification, i.e., project milestone 1 and project milestone 2 belong to the same category, and project milestone 3 has a sub-milestone identification that is different from project milestone 1 and project milestone 2 and belongs to another category. The project milestone 1 and the project milestone 2 share the same sub-milestone mark, the same sub-milestone mark does not need to be repeatedly displayed, and occupation and interference of repeated information to an interface space are avoided.

On the basis of the above embodiment, the milestone information management module 110 is further configured to: a history display layout of the project milestones is stored. The distribution of the project milestones in fig. 4 is a display layout, and in this embodiment, the display layout of the project milestones can be adjusted according to the user's needs. For example, the task items are classified according to the task items to which the project milestones belong, the project milestones of the same task item are divided into a class, and the project milestones of the same class are displayed in an aggregation mode. For example, the project milestones are classified according to the attribute tags of the parent milestones in the project milestones, the project milestones with the same attribute tag are classified into one type, and the project milestones of the same type are displayed in an aggregation manner. For example, the project milestones may be classified according to their importance or urgency, the project milestones with the same importance level or urgency level may be classified into one category, and the project milestones of the same category may be displayed in an aggregate manner. The milestone information management module 110 records and stores the historical display layout set by the user, and facilitates the formation of a personalized milestone interface meeting the user's needs based on the historical display layout.

On the basis of the foregoing embodiment, the milestone information includes an attribute tag of the parent milestone, and accordingly, the milestone information management module is further configured to: in response to an operation of inputting an attribute tag of a target parent milestone at a preset screening location, screening a tagged project milestone matching the target parent milestone attribute tag; the milestone display module is used for displaying the labeled project milestones. The milestone information management module can screen out the project milestones corresponding to the attribute labels according to the attribute labels of the parent milestones and display the project milestones, can help a user to quickly locate the target project milestones, and is convenient for the user to perform subsequent operations.

The milestone display module is further to: and determining the display position and the display mode of each project milestone based on the historical display layout, and displaying each project milestone. The history display layout comprises one or more of the classification mode of each project milestone, the display sequence (or display position) of each classification and the milestone interface type corresponding to each classification. And determining the affiliated classification of each acquired project milestone based on the classification mode in the historical display layout, and determining the display position in the display sequence corresponding to the affiliated classification. And calling the corresponding interface template based on the milestone interface type corresponding to the belonged classification, and displaying the milestone information.

Optionally, the historical display layout may be a display layout corresponding to a previous layout storage instruction, or a display layout with the highest historical use frequency. If the history display layout does not exist, the default display layout is called to display the project milestones. In the embodiment, by recording the historical display layout, the adjustment process of the layout by the user is omitted, the intellectualization of the milestone information display is improved, and the personalized display layout meeting the requirements of the user is obtained.

On the basis of the above embodiment, the milestone display module 120 is further configured to: responding to a detail switching operation, and switching to a detail display interface of the project milestone corresponding to the detail switching operation, wherein the detail display interface comprises a parent milestone information display area, a child milestone information display area and a key task node display area. The detail switching operation may be a click operation of any project milestone, or a selection operation of a detail control of any project milestone, which is not limited herein. In response to the detail switching operation, the milestone information of the project milestone is acquired, and the milestone information can be the whole milestone information of the project milestone or the local milestone information and can be set according to the requirements of the user. And calling a detail template, and adding the milestone information to the corresponding position of the detail template to form a detail display interface. The parent milestone information display area is used for displaying relevant information of the parent milestone, such as participation user identification, labels, importance, target data and the like, the child milestone information display area is used for displaying relevant information of each child milestone, and the key task node display area can be used for displaying relevant information of key task nodes corresponding to each child milestone or relevant information of key task nodes corresponding to currently selected child milestones.

Illustratively, referring to fig. 5, fig. 5 is a schematic diagram of a detail display interface of project milestones provided by an embodiment of the invention. In fig. 5, the key task node display area displays the relevant information of each key task node corresponding to the sub-milestone 2. Fig. 5 is only an example, and optionally, the information types of the mission-critical nodes include: task type, QA type (question and answer type), prompt text type, progress type, digital object type and flow type. The mission critical nodes included in any of the sub-milestones may be one or more of the above information types. The task type may include a plurality of tasks and a plurality of levels of tasks, for example, the task type may include a common task type, a time task type (for example, may include a day, month, quarter, half year, and year task type), and the like, and is not particularly limited herein, the QA type includes a plurality of QAs and a plurality of QAs, and the flow type includes a user-definable flow sequence and is a type, and supports storing the plurality of types. The digital object comprises a table, supports annual and monthly tables, and automatically adds the digital object.

On the basis of the above embodiment, a key task node is configured with a man-hour timing control, and is configured to accumulate man-hour information of any user at the key task node when the man-hour timing control is triggered by the user. The key task node is provided with a man-hour timing control, which can be triggered to start by user operation and start timing, and the timing is stopped when the user operation is triggered to stop, and the timing obtained man-hour information is stored. And the next time, the system is triggered and started by the user operation, and accumulated timing is carried out on the basis of the stored working hour information. And the working hour information of each key task node is independently stored and independently displayed. The working hours of each key task node are independently recorded by setting the working hour timing control at each key task node, so that the time cost of a user at each key task node is conveniently acquired. Optionally, when the man-hour timing control is triggered, a trigger user identifier is obtained, and associated storage is performed based on the user identifier and corresponding man-hour information. Optionally, when the man-hour timing control is triggered, a trigger timestamp is obtained, and the timestamp and the man-hour information are stored in an associated manner.

Optionally, the milestone information management module 110 is further configured to: counting the working hour information of the current user at each key task node in each project milestone to form the accumulated working hour of the current user, and sending the accumulated working hour to the milestone display module; and the milestone display module displays the accumulated working hours of the current user in a working hour display area. And in each project milestone, matching the labor hour information based on the user identification of the current user, determining a plurality of labor hour information corresponding to the user identification, and counting the accumulated labor hour of the current user. Optionally, the plurality of working hour information within the preset time range are accumulated to obtain the accumulated working hours within the preset time range, where the preset time range may be within a day, a week, or a month. Exemplarily, referring to fig. 6, fig. 6 is a schematic diagram of a man-hour display area provided by an embodiment of the present invention.

Optionally, a man-hour detail control is arranged in the man-hour display area, when the man-hour detail control is clicked, man-hour information details of the user in the current year are displayed, and the man-hour information details include man-hour information corresponding to each key task node. Through setting up man-hour display area, statistics shows man-hour information, and the user of being convenient for directly perceivedly obtains the man-hour that has accumulated, has simplified man-hour statistical process.

On the basis of the above embodiment, the milestone information management module 110 is further configured to: counting target data of each sub-project milestone or each key task node in each project milestone and the deadline of the target data to form total target data corresponding to preset deadline, determining the completion progress of the total target data based on the completion progress of the target data of each sub-project milestone or each key task node, and sending the total target data and the total target data to a milestone display module; the milestone display module 120 displays the total target data and the corresponding completion progress in the target data display area. Each mission critical node may set one or more target data that may include, but is not limited to, sales, invoicing, product production quantities, etc. It is to be understood that, in order to ensure that the total target data can be successfully completed, it is preferable that decomposition plan target data be set for each key task node, the decomposition plan target data be preferably equal to or greater than the target data, the decomposition plan target data at each key task node be summed to obtain the total decomposition plan target data, and the total decomposition plan target data be displayed in the target data display area. The content displayed in the target data display area may be set according to the actual needs of the user, and the above-mentioned cases are only examples, and are not limited herein.

Specifically, taking statistics of target data at each key task node in each project milestone as an example, matching the target data at each key task node of each project milestone, summing up the target data at each key task node which is successfully matched to obtain total target data, and summing up the completion progress at each key task node which is successfully matched to obtain the completion progress of the total target data. For example, the mission critical nodes in project milestone 1 may have target data for 7-month 20-day product production quantities of up to 1000 pieces and 600 pieces produced, and the mission critical nodes in project milestone 2 may have target data for 7-month 30-day product production quantities of up to 500 pieces and 400 pieces produced. And inquiring 1500 pieces of total target data of each project milestone based on the production quantity of the product as target data, wherein the total target data and the completion are 1000 pieces, namely the completion progress is 1000 pieces, and displaying the total target data and the completion in a display area of the target data so as to comprehensively count a plurality of project milestones and conveniently display the overall execution progress of a plurality of project milestones.

Optionally, a plurality of target data are determined, the total target data of each target data point and the completion progress of the total target data are respectively determined, a plurality of display cards of the target data are formed, and the display cards are displayed in the display area of the target data. Exemplarily, referring to fig. 7, fig. 7 is a schematic diagram of a display manner of target data according to an embodiment of the present invention. Fig. 7 is only an example, and the layout manner of the target data in the display area is not limited in this embodiment.

On the basis of the above embodiment, referring to fig. 8, fig. 8 is a schematic diagram of a milestone interface provided by an embodiment of the present invention, where the milestone interface includes a milestone display area, a target data display area, a man-hour display area, and a comment hotspot display area. The comment hotspot display area is used for displaying the latest comment information and the hotspot information in the project milestones, and the comment information can be visually acquired without entering a detail interface. Meanwhile, a quick reply interface can be arranged in the comment hotspot display area, and corresponding comment information and hotspot information can be replied without entering a detail interface. By setting the milestone interface in fig. 8, multiple types of information are displayed in the same interface, so that convenience of a user in inquiring information is improved.

On the basis of the foregoing embodiment, a milestone project management method is further provided, referring to fig. 9, and fig. 9 is a schematic flow chart of the milestone project management method provided in the embodiment of the present invention, and this embodiment is applicable to a case of managing and displaying multi-level milestone information, and this method may be executed by the milestone project management apparatus provided in the embodiment of the present invention, and this milestone project management apparatus may be implemented by software and/or hardware, and this milestone project management apparatus may be configured on an electronic device such as a computer or a server, and specifically includes the following steps:

s210, acquiring project milestones associated with the current user and milestone information in the project milestones, and sending the project milestones and corresponding milestone information to a milestone display module, wherein the project milestones at least comprise the first two stages of the following three-stage nodes: a parent milestone, a plurality of child milestones included in the parent milestone, and a mission critical node included in each of the child milestones.

And S220, forming a milestone interface based on the project milestones and the corresponding milestone information, and rendering the milestone interface on a preset display interface.

On the basis of the above embodiment, the milestone information includes one or more items of execution status, target data, and executor information of each sub-milestone, and one or more items of execution information, execution progress, and execution status of each critical task node in each sub-milestone.

On the basis of the above embodiment, after acquiring the project milestone associated with the current user and the milestone information in the project milestone, the method further includes:

extracting preset type display information from the milestone information, and sending the extracted preset type display information to the milestone display module;

accordingly, forming a milestone interface based on the project milestones and corresponding milestone information, comprising: forming a milestone interface based on the project milestones and the extracted preset types of display information.

On the basis of the above embodiment, the method further includes:

classifying a plurality of project milestones to be displayed based on the sub-milestone information in each project milestone;

the milestone display module is used for carrying out aggregation display on project milestones in the same classification

On the basis of the above embodiment, the method further includes:

storing a historical display layout of project milestones;

and determining the display position and the display mode of each project milestone based on the historical display layout, and displaying each project milestone.

On the basis of the above embodiment, forming a milestone interface based on the project milestones and corresponding milestone information includes:

acquiring a milestone interface type, calling an interface template corresponding to the milestone interface type, updating the interface template with the structure of the project milestone, and adding corresponding milestone information to the corresponding position of the updated interface template to form a milestone interface conforming to the milestone interface type.

Based on the above embodiment, the milestone interface includes a display area for a plurality of project milestones; the display area of any project milestone comprises a sub display area of a parent milestone and a sub display area of each sub milestone, and the parent milestone and each sub milestone are respectively displayed in the corresponding sub display areas in the form of cards.

In addition to the above-described embodiment, in each sub-display area, different information display modes are invoked based on the information type of the milestone information to be displayed.

On the basis of the above embodiment, the method further includes:

if the execution state change of any key task node in the project milestones is detected, updating the associated information of the child milestones to which the key task nodes belong and the associated information of the parent milestones to which the key task nodes belong;

and sending the updated milestone information to the milestone display module, or storing the updated milestone information and sending the updated milestone information to the milestone display module when receiving a milestone display request.

Optionally, detecting the execution state change of any key task node in the project milestone includes:

when detecting that the state control at any key task node is switched, generating execution state change information; or,

matching the received message with the execution information of each key task node, and if the matching is successful, generating execution state change information; or,

and receiving completion information sent by the key task node, the child milestone or the father milestone which are preset with the incidence relation, and generating execution state change information.

On the basis of the above embodiment, the method further includes:

acquiring preset target time of each node in each project milestone;

when the prompt condition corresponding to the target time is met, generating countdown prompt information; or,

when the execution state change is not detected in the target time, generating prompt information based on attribute information of a corresponding node in the project milestone, and sending the prompt information to the milestone display module, wherein the milestone display module displays the prompt information in a preset prompt area.

On the basis of the above embodiment, the method further includes:

responding to a detail switching operation, and switching to a detail display interface of the project milestone corresponding to the detail switching operation, wherein the detail display interface comprises a parent milestone information display area, a child milestone information display area and a key task node display area.

On the basis of the above embodiment, the key task node is configured with a man-hour timing control, and is configured to accumulate man-hour information of any user at the key task node when the man-hour timing control is triggered by the user.

Optionally, the method further includes:

counting the working hour information of the current user at each key task node in each project milestone to form the accumulated working hour of the current user, and sending the accumulated working hour to the milestone display module;

and displaying the accumulated working hours of the current user in a working hour display area.

On the basis of the above embodiment, the method further includes:

counting target data at each key task node in each project milestone and deadline of the target data to form total target data corresponding to preset deadline, determining completion progress of the total target data based on completion progress of the target data at each key task node, and sending the total target data and the total target data to the milestone display module;

and displaying the total target data and the corresponding completion progress in a target data display area.

On the basis of the above embodiment, the method further includes:

responding to an information sending instruction at any node, and sending the milestone information corresponding to the node to a receiver of the information sending instruction, wherein the node is any one of a father milestone, a child milestone and a key task node.

On the basis of the above embodiment, one or more of the parent milestone, the child milestone and the mission-critical node is provided with associated device information;

correspondingly, the method further comprises the following steps:

if the state information of any one of the parent milestone, the child milestone and the key task node is detected to be switched to a preset execution state, sending control information to associated equipment based on corresponding associated equipment information; and/or the presence of a gas in the gas,

and any one of the parent milestone, the child milestone and the key task node receives the associated information sent by the associated equipment, stores the associated information and displays the associated information.

On the basis of the above embodiment, the information types of the mission-critical nodes include: task type, QA type, prompt text type, progress type, digital object type, and flow type.

Fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. FIG. 10 illustrates a block diagram of an electronic device 12 suitable for use in implementing embodiments of the present invention. The electronic device 12 shown in fig. 10 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiment of the present invention. The device 12 is typically an electronic device that undertakes image classification functions.

As shown in FIG. 10, electronic device 12 is embodied in the form of a general purpose computing device. The components of electronic device 12 may include, but are not limited to: one or more processors 16, a memory device 28, and a bus 18 that connects the various system components (including the memory device 28 and the processors 16).

Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

Electronic device 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by electronic device 12 and includes both volatile and nonvolatile media, removable and non-removable media.

Storage 28 may include computer system readable media in the form of volatile Memory, such as Random Access Memory (RAM) 30 and/or cache Memory 32. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 10, and commonly referred to as a "hard drive"). Although not shown in FIG. 10, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a Compact disk-Read Only Memory (CD-ROM), a Digital Video disk (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. Storage 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

A program 36 having a set (at least one) of program modules 26 may be stored, for example, in storage 28, such program modules 26 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may include an implementation of a gateway environment. Program modules 26 generally perform the functions and/or methodologies of the described embodiments of the invention.

Electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, camera, display 24, etc.), with one or more devices that enable a user to interact with electronic device 12, and/or with any devices (e.g., network card, modem, etc.) that enable electronic device 12 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 22. Also, the electronic device 12 may communicate with one or more gateways (e.g., Local Area Network (LAN), Wide Area Network (WAN), etc.) and/or a public gateway, such as the internet, via the Network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device 12 via the bus 18. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with electronic device 12, including but not limited to: microcode, device drivers, Redundant processing units, external disk drive Arrays, disk array (RAID) systems, tape drives, and data backup storage systems, to name a few.

The processor 16 executes various functional applications and data processing, such as implementing the milestone project management method provided by the above-described embodiments of the present invention, by running a program stored in the storage device 28.

Embodiments of the present invention also provide a computer-readable storage medium on which a computer program is stored, where the computer program, when executed by a processor, implements the milestone project management method provided by the embodiments of the present invention.

Of course, the embodiment of the present invention provides a computer-readable storage medium on which a computer program is stored, which is not limited to the method operations described above, and can also perform the milestone project management method provided in any embodiment of the present invention.

Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable source code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Source code embodied on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer source code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, or the like, as well as conventional procedural programming languages, such as the "C" programming language or similar programming languages. The source code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of gateway, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A milestone project management apparatus, comprising:

2. The milestone project management apparatus according to claim 1, wherein the milestone information comprises one or more of execution status, target data, and attribute tags of each parent milestone, one or more of execution status, target data, and performer information of each child milestone, and one or more of performance information, execution progress, and execution status of each key task node in each child milestone.

3. The milestone item management device according to claim 2, wherein the milestone information management module is further configured to: extracting preset type display information from the milestone information, and sending the extracted preset type display information to the milestone display module;

correspondingly, the milestone display module is used for forming a milestone interface based on the project milestones and the extracted preset type of display information.

4. The milestone item management device as recited in claim 1, wherein the milestone information management module is further configured to: classifying a plurality of project milestones to be displayed based on the sub-milestone information in each project milestone;

the milestone display module is used for performing aggregation display on project milestones in the same category.

5. The milestone item management device as recited in claim 1, wherein the milestone information management module is further configured to: storing a historical display layout of project milestones;

the milestone display module is further to: and determining the display position and the display mode of each project milestone based on the historical display layout, and displaying each project milestone.

6. The milestone item management device as recited in claim 1, wherein the milestone display module is configured to: acquiring a milestone interface type, calling an interface template corresponding to the milestone interface type, updating the interface template with the structure of the project milestone, and adding corresponding milestone information to the corresponding position of the updated interface template to form a milestone interface conforming to the milestone interface type.

7. The milestone project management apparatus according to any of claims 1-6, wherein the milestone interface comprises a display area for a plurality of project milestones; the display area of any project milestone comprises a sub display area of a parent milestone and a sub display area of each sub milestone, and the parent milestone and each sub milestone are respectively displayed in the corresponding sub display areas in the form of cards.

8. The milestone item management apparatus according to claim 7, wherein in each sub-display area, a different information display mode is invoked based on an information type of the milestone information to be displayed.

9. The milestone item management device as recited in claim 1, wherein the milestone information management module is further configured to:

if the execution state change of any key task node in the project milestones is detected, updating the associated information of the child milestones to which the key task nodes belong and the associated information of the parent milestones to which the key task nodes belong; or if the execution state change of the parent milestone is detected, updating the associated information of the child milestones in the parent milestone and the associated information of the key task nodes, or if the execution state change of the child milestone is detected, updating the associated information of the parent milestone to which the child milestones belong and the associated information of the key task nodes in the child milestones;

10. The milestone item management device according to claim 9, wherein the milestone information management module is further configured to:

acquiring preset target time of each node in each project milestone;

11. The milestone item management device according to claim 9, wherein the milestone information management module is further configured to:

12. The milestone item management device as recited in claim 1, wherein the milestone display module is further configured to: responding to a detail switching operation, and switching to a detail display interface of the project milestone corresponding to the detail switching operation, wherein the detail display interface comprises a parent milestone information display area, a child milestone information display area and a key task node display area.

13. The milestone project management apparatus according to claim 1, wherein the mission-critical nodes are configured with a man-hour timing control for accumulating man-hour information of any user at the mission-critical nodes when the man-hour timing control is triggered by the user;

the milestone information management module is further configured to:

the milestone display module is also used for displaying the accumulated working hours of the current user in a working hour display area.

14. The milestone item management device as recited in claim 1, wherein the milestone information management module is further configured to:

counting target data of each sub-project milestone or each key task node in each project milestone and the deadline of the target data to form total target data corresponding to preset deadline, determining the completion progress of the total target data based on the completion progress of the target data of each sub-project milestone or each key task node, and sending the total target data and the total target data to a milestone display module;

the milestone display module is further used for displaying the total target data and the corresponding completion progress in a target data display area.

15. The milestone item management device as recited in claim 1, wherein the milestone information management module is further configured to:

16. The milestone project management apparatus according to claim 1, wherein one or more of the parent milestone, the child milestone and the mission-critical node is provided with associated equipment information;

the milestone information management module is further configured to:

17. The milestone project management apparatus according to claim 1, wherein the information types of the mission critical nodes comprise: task type, QA type, prompt text type, progress type, digital object type, and flow type.

18. The milestone item management device according to claim 1, wherein the milestone information comprises attribute tags of parent milestones, and accordingly, the milestone information management module is further configured to:

in response to an operation of inputting an attribute tag of a target parent milestone at a preset screening location, screening a tagged project milestone matching the target parent milestone attribute tag;

the milestone display module is used for displaying the labeled project milestones.

19. A milestone project management method, comprising:

20. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the milestone item management method of claim 19 when executing the program.

21. A computer-readable storage medium having stored thereon a computer program, wherein the program, when executed by a processor, implements the milestone project management method of claim 19.