CN113537954B - Project milestone processing method and device, storage medium and electronic equipment - Google Patents
Project milestone processing method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN113537954B CN113537954B CN202111090790.3A CN202111090790A CN113537954B CN 113537954 B CN113537954 B CN 113537954B CN 202111090790 A CN202111090790 A CN 202111090790A CN 113537954 B CN113537954 B CN 113537954B
- Authority
- CN
- China
- Prior art keywords
- node
- milestone
- milestones
- project
- child
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Abstract
The embodiment of the invention discloses a project milestone processing method, a project milestone processing device, a storage medium and electronic equipment. The method comprises the steps of obtaining creating information of project milestones, wherein the project milestones comprise a parent milestone, a plurality of child milestones in the parent milestone and a plurality of mission critical nodes in each child milestone; in response to a creation instruction of the project milestones, sequentially creating the parent milestone, each child milestone and each key task node based on the creation information to form the project milestone, and constructing an association relationship between a current node and an associated node for the current node in the project milestone. In the embodiment, the execution states of different departments or different users are uniformly managed by creating the project milestones, so that the accuracy and the effectiveness of information are improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a project milestone processing method and device, a storage medium and electronic equipment.
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. Meanwhile, the relation between different tasks needs to be determined through a manual communication mode, and the situations of information omission or time waste and the like caused by untimely communication exist.
Disclosure of Invention
The embodiment of the invention provides a project milestone processing method and device, a storage medium and electronic equipment, which are used for realizing information management in a project milestone mode and improving the information management efficiency and accuracy.
In a first aspect, an embodiment of the present invention provides a method for processing project milestones, including:
acquiring creation information of a project milestone, wherein the project milestone comprises a parent milestone, a plurality of child milestones in the parent milestone and a plurality of mission critical nodes in each child milestone;
in response to a creation instruction of the project milestones, sequentially creating the parent milestone, the child milestones and the key task nodes based on the creation information to form project milestones;
for a current node in the project milestone, constructing an incidence relation between the current node and an associated node, wherein the current node and the associated node are one of the following: parent milestones, child milestones, mission critical nodes, and child mission critical nodes, the mission critical nodes including the child mission critical nodes, the current node and the associated node belonging to different project milestones, wherein the association type of the current node and the associated node is one of: and triggering starting, triggering completion, synchronous completion and constraint relation of target data.
In a second aspect, an embodiment of the present invention further provides a device for processing project milestones, including:
the system comprises an information acquisition module, a task execution module and a task execution module, wherein the information acquisition module is used for acquiring the creation information of project milestones, and the project milestones comprise parent milestones, a plurality of child milestones in the parent milestones and a plurality of key task nodes in each child milestone;
a milestone creation module, configured to create, in response to a creation instruction of the project milestone, the parent milestone, the child milestones, and the key task nodes in sequence based on the creation information to form the project milestone;
an association relationship creating module, configured to, after the parent milestone, each child milestone, and each mission-critical node are sequentially created based on the creation information, construct, for a current node in the project milestone, an association relationship between the current node and an association node, where the current node and the association node are one of: parent milestones, child milestones, and mission critical nodes, the current node and the associated node belonging to different project milestones, wherein the association type of the current node and the associated node is one of: and triggering starting, triggering completion, synchronous completion and constraint relation of target data.
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 implements the processing method of the project milestone according to any embodiment of the present invention when executing the program.
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, when executed by a processor, implements the method for processing project milestones according to any embodiment of the present invention.
According to the technical scheme provided by the embodiment of the invention, the establishment information of the project milestones is acquired, the establishment instruction of the project milestones is generated when the establishment operation of the project milestones is detected, the establishment instruction of the project milestones is executed, and the project milestones are established based on the acquired establishment information. The execution states of different departments or different users are managed in a unified manner by creating the project milestones, so that the accuracy and the effectiveness of information are improved. After each level of nodes of the project milestone are created, the incidence relation is set between the nodes with the incidence relation through the incidence relation configuration information, so that the information transmission between the nodes is realized through the incidence relation, the manual transmission of the information is replaced, and the timeliness of the information transmission is improved.
Drawings
FIG. 1 is a flow chart of a method for processing project milestones in accordance with an embodiment of the present invention;
FIG. 2 is a schematic illustration of a project milestone provided by an embodiment of the invention;
FIG. 3 is a detailed schematic diagram of a project milestone provided by an embodiment of the invention;
FIG. 4 is a schematic structural diagram of a project milestone processing device according to an embodiment of the present invention;
fig. 5 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 flowchart of a project milestone processing method according to an embodiment of the present invention, where the embodiment is applicable to a case of creating a project milestone, the method may be executed by a project milestone processing apparatus according to an embodiment of the present invention, the project milestone processing apparatus may be implemented by software and/or hardware, and the project milestone processing apparatus may be configured on an electronic computing device such as a mobile phone, a PC, a tablet computer, and the like, and specifically includes the following steps:
s110, acquiring creating information of project milestones, wherein the project milestones comprise a parent milestone, a plurality of child milestones in the parent milestone and a plurality of mission critical nodes in each child milestone.
And S120, responding to a creation instruction of the project milestones, sequentially creating the parent milestone, the child milestones and the key task nodes based on the creation information, and forming the project milestones.
S130, for the current node in the project milestone, constructing an incidence relation between the current node and an associated node, wherein the current node and the associated node are one of the following nodes: parent milestones, child milestones, mission critical nodes, and child mission critical nodes, the mission critical nodes including the child mission critical nodes, the current node and the associated node belonging to different project milestones, wherein the association type of the current node and the associated node is one of: and triggering starting, triggering completion, synchronous completion and constraint relation of target data.
In this embodiment, the project milestone is a multi-level management architecture created based on an execution flow of a project, where the project may be made by an enterprise according to its own development requirement, and may be, for example, a development project, an operation project, a planning project, and the like, and the project may also be made by an individual according to its own requirement, and may be, for example, an event, an individual schedule, and the like. Optionally, the project milestone may include a three-level architecture, such as a parent milestone, a child milestone, and a mission critical node, where the parent milestone is a primary architecture, the child milestone is a secondary 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. 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 milestones is provided with an execution state or an execution progress, the execution state of each sub-milestone influences the execution progress of the parent milestone, and the execution state of each key task node influences 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.
In a task project, one or more project milestones may be created, and for each project milestone to be created, creation information of the project milestone to be created is obtained, and in some embodiments, the creation information may be a multi-level architecture of the project milestone to be created, and related information of each level of architecture, for example, the creation information includes a parent milestone identifier, a number of sub-milestones in the parent milestone, and creation requirements of each sub-milestone identifier and each sub-milestone, wherein the creation requirements of each sub-milestone may include, but are not limited to, the number of key task nodes in the sub-milestone, and execution information, target data, and the like of each key task node.
An information import control is arranged on the creation page of the project milestone, and preset creation information is imported based on the information import control, so that manual input of the creation information is avoided, and the information acquisition efficiency is improved. The project milestone creation page can also be provided with a milestone creation control, when the milestone creation control is detected to be selected, the project milestone is created based on the acquired creation information, one-key creation of the project milestone is realized, and the project milestone creation process is simplified.
Optionally, creating the project milestone based on the acquired creation information includes: and calling the stored project milestone templates based on the multilevel structure in the creation information, such as the structural relationship of parent milestones, child milestones and key task nodes, specifically, carrying out template matching based on the number of child milestones, or carrying out template matching on the number of child milestones and the number of key task nodes. And calling a successfully matched project milestone template, wherein the successfully matched project milestone template can be a project milestone template which meets the number of the sub-milestones or a project milestone template which meets the number of the sub-milestones and the number of the key task nodes. And configuring related information of each level of structure in the creation information into a project milestone template to form project milestones, such as parent milestone identifications, child milestone identifications, creation requirements of child milestones and the like. Wherein, the parent milestone identifier may be a name of the parent milestone, and the child milestone identifier may be a name of the child milestone.
Illustratively, referring to fig. 2 and 3, fig. 2 is a schematic diagram of a project milestone provided by an embodiment of the present invention, and fig. 3 is a detailed schematic diagram of a project milestone provided by an embodiment of the present invention.
In this embodiment, the project milestone is created based on the acquired creation information by acquiring the creation information of the project milestone, generating a creation instruction of the project milestone upon detecting the creation operation of the project milestone, executing the creation instruction of the project milestone, and creating the project milestone. The execution states of different departments or different users are managed in a unified manner by creating the project milestones, so that the accuracy and the effectiveness of information are improved.
On the basis of the above embodiment, the process of creating the project milestones may further include the creation operation of sequentially acquiring parent milestones, child milestones, and key task nodes, and creating structures of each level based on the corresponding information of the parent milestones, the child milestones, and the key task nodes in the creation information to form the project milestones.
Optionally, in response to the creation instruction of the project milestone, sequentially creating the parent milestone, the child milestones, and the mission-critical nodes based on the creation information to form the project milestone, including: creating a parent milestone based on the parent milestone identification in response to a creation instruction of the parent milestone; creating, in response to a creation instruction of the child milestones, a plurality of child milestones of the parent milestone based on the number of child milestones and each child milestone identification; and in response to the creation instruction of the key task nodes, creating a plurality of key task nodes in which each sub-milestone is located based on the creation requirement of each sub-milestone to form the project milestone.
In some embodiments, the creation page of the project milestone may be a creation control provided with a parent milestone and a creation control provided with a child milestone, respectively, for generating a corresponding creation instruction when the above controls are selected. For example, the creation control of the parent milestone and the creation control of the child milestone may be configured with information input controls respectively, and are configured to collect information, such as a parent milestone identifier and a child milestone identifier, input by a user, respectively. And creating sub-milestones in the project milestone in response to a creating instruction of the sub-milestone based on the sub-milestone identifications acquired by the information input control, wherein a plurality of sub-milestones in the parent milestone can be created multiple times, and can also be created synchronously by acquiring a plurality of sub-milestone identifications acquired by the information input control.
In some embodiments, after the parent milestone is created, a sub-milestone template corresponding to the project attribute (each sub-milestone identifier) may be determined in a preset sub-milestone template library, wherein the preset sub-milestone template library stores a plurality of sub-milestone templates, and the sub-milestone templates are stored in a one-to-one correspondence with the sub-milestone templates according to the project attribute. And when the matching is successful, responding to the creation instruction of the sub-milestone, calling the successfully matched sub-milestone template, and realizing the creation of the sub-milestone. The sub-milestone template is called to replace the creation process of the sub-milestone, and the creation efficiency of the project milestone is improved. Optionally, the preset sub-milestone template library may also be stored in a one-to-one correspondence manner based on the type of the parent milestone and the sub-milestone templates, and may be used for calling the corresponding sub-milestone templates according to the type of the created parent milestone.
Optionally, if the preset sub-milestone template library does not have the sub-milestone template corresponding to the project attribute, the sub-milestone template corresponding to the project attribute is created and stored in the preset sub-milestone template library, so that the sub-milestone template can be called conveniently in the subsequent process of creating the project milestone.
In this embodiment, a creation control of the mission-critical node is configured in the creation page of the project milestone or the detail page of the project milestone. The key node template library stores various types of key task node templates, and can call the corresponding key task node templates according to the types of the key task nodes included in the sub-milestones, and configure the relevant information of the key task nodes into the key task node templates to form the key task nodes. The corresponding information of the mission-critical nodes includes, but is not limited to, execution information, participating user identifiers, target data, and the like. Illustratively, referring to fig. 3, the mission critical nodes in the sub-milestone 2 are included in the display area of the mission critical nodes in fig. 3.
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 types comprise a plurality of tasks and multi-level tasks, the QA types comprise a plurality of QAs and a plurality of QAs, the flow types comprise flow sequences which can be defined by users and are stored as types, and the storage of the plurality of types is supported. The digital object comprises a table, supports annual and monthly tables, and automatically adds the digital object. Preferably, the key task nodes may include sub key task nodes, and exemplarily, the key task nodes are tables in the type of the digital target, and the tables include a planned amount setting digital target, a refund digital target, a sales planned amount digital target, and the like, and the planned amount setting digital target, the refund digital target, the sales planned amount digital target, and the like in the tables are all sub key task nodes. For another example, the key task node is a multi-level task in the task type, and each level of task in the multi-level task is a sub-key task node.
In the embodiment, the project milestones are created in the form of sequentially creating the parent milestone, the child milestone and the key task node, and the project milestones are used for acquiring and managing the execution information of different stages of each department, so that the unified management of the project information is realized, the problems of information delay, omission and the like are avoided, and the information accuracy and the real-time performance are improved.
On the basis of the above embodiments, there may be a constraint relationship between nodes in the same project milestone and between nodes in different project milestones, for example, the first node purchases equipment, the second node manufactures products for the equipment, and after the execution of the first node is completed, the second node can start the execution, so that there is a constraint relationship between the first node and the second node.
In some embodiments, the constraint relationship between nodes in the project milestone may be included in the creation information. Wherein, the current node and the associated node with the constraint relation are one of the following nodes: the method comprises the steps of creating a project milestone, creating a key task node and a sub key task node, wherein the key task node comprises the sub key task node, a current node and the associated node belong to the same project milestone, or belong to different project milestones, namely the current node can be any one of a parent milestone, a child milestone, a key task node and a sub key task node in the project milestone to be created, and the current node can be any one of a parent milestone, a child milestone, a key task node and a sub key task node in the project milestone to be created, or any one of a parent milestone, a child milestone, a key task node and a sub key task node in other project milestones which are created. For example, the current node may be a parent milestone and the associated nodes of the current node may be child milestones in the created project milestone; the current node can be a key task node, and the associated node of the current node can be a key task node in the created project milestone; the current node may be a sub-milestone, the associated node of the current node may be another sub-milestone in the same project milestone, the current node may be a key task node, and the associated node of the current node may be a sub-key task node in another key task node in different project milestones, which is not limited to this, and is set according to the actual requirements between task projects. In some embodiments, the project milestones to which the two nodes having the association relationship respectively belong may belong to the same project. In some embodiments, the project milestones to which the two nodes with the association relationship respectively belong may belong to different projects, so as to realize the association between the different projects.
Illustratively, if the current node is a key task node-task 1 of the project milestone a and the associated node of the current node is a refund digital object in a key task node-table of the project milestone B, an association relationship between the key task node-task 1 and the refund digital object in the key task node-table may be established.
And after the father milestone, the child milestones and the key task nodes are sequentially created based on the creation information, determining whether the nodes have associated nodes, and if so, constructing the association relationship between the current node and the associated nodes. The incidence relation is used for information transmission between two nodes with incidence, for example, the execution state of any node is automatically sent to the incidence node through the incidence relation without manual information transmission, so that the transmission efficiency of the information is improved, the transmission flow is simplified, and errors in the process of manual information transmission are avoided.
Optionally, the creation information may include association relationship configuration information, where the association relationship configuration information includes two node identifiers having an association relationship and an association type. The association type comprises a trigger start, a trigger completion, a synchronization completion and a constraint relation of target data, the trigger start is that a first preset execution state of the front node triggers the execution state of the rear node to be changed into a start, the trigger completion is that a second preset execution state of the front node triggers the execution state of the rear node to be changed into a completion, and when the synchronization completion is that two nodes with association are both in a completion state, the execution state of the two nodes with association is changed into a completion. The first preset execution state and the second preset execution state may be the same or different, and may be, for example, starting, completing, or an execution progress being at a preset progress value. The constraint relationship of the target data may be that a size constraint relationship exists between the target data of the front node and the rear node. The target data may be resource target data, such as fund target data, and may also be time target data. The constraint relation of the target data may be that the target data of the front node is larger than the target data of the back node, the target data of the front node is smaller than the target data of the back node, the target data of the front node is equal to the target data of the back node, the target data of the front node is larger than or equal to the target data of the back node, the target data of the front node is smaller than or equal to the target data of the back node, and the like.
For example, the front node is the contract amount of the a subcontractor, the back node is the actual payment amount of the a subcontractor, and since the contract amount of the a subcontractor should be greater than or equal to the actual payment amount of the a subcontractor in an actual scene, an association between the contract amount of the front node-a subcontractor and the actual payment amount of the back node-a subcontractor can be established such that the contract amount of the front node-a subcontractor is greater than or equal to the actual payment amount of the back node-a subcontractor. In this embodiment, the execution state of each node in each project milestone is obtained in real time, and if it is detected that the execution state of the front node is switched to a preset state, trigger information is generated and sent to the rear node. When the execution state of any node changes, whether the node exists in a post node is determined, if yes, whether the execution state after switching meets the triggering condition of the post node is determined, and if yes, triggering information of the post node is generated, wherein the triggering information comprises a pre-node identifier and a preset state after the pre-node is cut into flowers. And sending the trigger information to a post node based on a preset transmission channel so that the post node performs execution state switching according to the trigger information. The trigger information is generated when the execution state switching of the front node is detected, so that the timeliness of the trigger information is guaranteed, the trigger information is sent to the rear node, the automatic sending of the information is achieved, manual control is not needed, and the transmission efficiency is improved.
It should be noted that the current node may be a front node or a back node, and is determined according to an actual constraint relationship.
Wherein, constructing the incidence relation between the current node and the incidence node comprises: generating an association relationship construction request according to the current node identifier, the association node identifier and the association type with the association relationship in the association relationship configuration information, and sending the association relationship construction request to the association node, wherein the association relationship construction request is used for triggering the construction of the association relationship between the current node and the association node. For any current node in the current project milestone, if the association relationship configuration information comprises a current node identifier, acquiring an association node identifier and an association type corresponding to the current node identifier, and generating an association relationship construction request based on the current node identifier, the association node identifier and the association type. The association relationship construction request is sent to the association node, which may be sending the association relationship construction request to the participating user equipment of the association node, so that the participating user constructs the association relationship between the current node and the association node according to the association relationship construction request.
Optionally, constructing an association relationship between the current node and the associated node may further include: and receiving an incidence relation construction request sent by the incidence node, and constructing the construction incidence relation between the current node and the incidence node based on the incidence relation construction request.
On the basis of the above embodiment, constructing the association relationship between the current node and the associated node includes: creating a transmission channel between two nodes having an association relationship, and setting an association type between the two nodes. Optionally, the creating of the transmission channel between two nodes having an association relationship may be, for example, determining an information sending party, an information receiving party, and an information transmission manner, where the information transmission manner includes, but is not limited to, an instant messaging manner, an email manner, and the like, and is not limited thereto. The information sender and the information receiver are determined based on the current node identification and the associated node identification, wherein the information sender can be a front node, the information receiver can be a rear node, and the configuration information is determined according to the associated relationship configuration information.
For a transmission channel between two nodes, setting an association type for determining a state change mode of a post node, for example, when the relationship type is trigger start, the post node switches an execution state to start when receiving trigger information of the pre node; for example, the relationship type is trigger completion, and when the post node receives the trigger information of the pre node, the state change mode is to switch the execution state to completion.
Optionally, after the transmission channel between the two nodes is constructed, a trigger condition for setting information transmission is further included, for example, the trigger condition for triggering the start is that the execution state of the front node is switched to a first preset execution state, and the first preset execution state may be start, complete, or the execution progress is at a preset progress value.
On the basis of the above embodiment, before creating a transmission channel between two nodes having an association relationship, the method further includes: and verifying the association relationship construction request based on preset association relationship configuration information. And matching the association node identification and the current node identification in the received association relationship construction request in the association relationship configuration information, if the matching is successful, determining that the association relationship exists between the association node and the current node, executing a step of creating a transmission channel between the two nodes with the association relationship, if the matching is failed, determining that the association relationship does not exist between the association node and the current node, ignoring the association relationship construction request, and avoiding the condition of error in the association relationship construction.
On the basis of the embodiment, the two nodes with the incidence relation comprise a front node and a rear node; for any node in the project milestone, there may be multiple front-end nodes and/or multiple back-end nodes.
According to the technical scheme provided by the embodiment, after the nodes at all levels of the project milestone are created, the incidence relation is set between the nodes with the incidence relation through the incidence relation configuration information, so that the information transmission between the nodes is realized through the incidence relation, the manual transmission of the information is replaced, and the timeliness of the information transmission is improved.
Fig. 4 is a schematic structural diagram of a project milestone processing device according to an embodiment of the present invention, where the project milestone processing device includes:
an information obtaining module 310, configured to obtain creation information of a project milestone, where the project milestone includes a parent milestone, a plurality of child milestones in the parent milestone, and a plurality of key task nodes in each of the child milestones;
a milestone creation module 320, configured to create, in response to a creation instruction of the project milestone, the parent milestone, the child milestones, and the key task nodes in sequence based on the creation information to form the project milestone;
an association relationship creating module 330, configured to, after the parent milestone, each child milestone, and each mission-critical node are sequentially created based on the creation information, for a current node in the project milestone, construct an association relationship between the current node and an associated node, where the current node and the associated node are one of: parent milestones, child milestones, and mission critical nodes, the current node and the associated node belonging to different project milestones, wherein the association type of the current node and the associated node is one of: and triggering starting, triggering completion, synchronous completion and constraint relation of target data.
Optionally, the milestone creation module 320 is configured to:
the creating instruction in response to the project milestones sequentially creates the parent milestone, the child milestones and the key task nodes based on the creating information to form the project milestones, including:
creating a parent milestone based on the parent milestone identification in response to a creation instruction of the parent milestone;
creating, in response to a creation instruction of the child milestones, a plurality of child milestones of the parent milestone based on the number of child milestones and each child milestone identification;
and in response to the creation instruction of the key task nodes, creating a plurality of key task nodes in which each sub-milestone is located based on the creation requirement of each sub-milestone to form the project milestone.
Optionally, the association relationship creating module includes:
the first creating unit is used for generating an association relationship construction request according to a current node identifier, an association node identifier and an association type which have an association relationship in association relationship configuration information, and sending the association relationship construction request to an association node, wherein the association relationship construction request is used for triggering the construction of the association relationship between the current node and the association node; alternatively, the first and second electrodes may be,
and the second creating unit is used for receiving an incidence relation building request sent by the incidence node and building the building incidence relation between the current node and the incidence node based on the incidence relation building request.
Optionally, the second creating unit is configured to:
creating a transmission channel between two nodes having an association relationship, and setting an association type between the two nodes.
Optionally, the association relationship creating module further includes:
and the information verification unit is used for verifying the incidence relation construction request based on preset incidence relation configuration information.
Optionally, the two nodes having the association relationship include a front node and a rear node;
optionally, the apparatus further comprises:
and the trigger information sending module is used for generating trigger information and sending the trigger information to the rear node if the execution state of the front node is detected to be switched to a preset state.
The project milestone processing device provided by the embodiment of the invention can execute the project milestone processing method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects for executing the project milestone processing method.
Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. FIG. 5 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. 5 is only an example and should not bring any limitation to the function 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. 5, 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).
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.
The processor 16 executes various functional applications and data processing, such as a processing method of project milestones 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, which, when executed by a processor, implements a method for processing project milestones as provided by 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 project milestone processing 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 (8)
1. A method for processing project milestones, comprising:
acquiring creation information of a project milestone, wherein the project milestone comprises a parent milestone, a plurality of child milestones in the parent milestone and a plurality of mission critical nodes in each child milestone;
in response to a creation instruction of the project milestones, sequentially creating the parent milestone, the child milestones and the key task nodes based on the creation information to form project milestones;
for a current node in the project milestone, constructing an incidence relation between the current node and an associated node, wherein the current node and the associated node are one of the following: parent milestones, child milestones, mission critical nodes, and child mission critical nodes, the mission critical nodes including the child mission critical nodes, the current node and the associated node belonging to different project milestones, wherein the association type of the current node and the associated node is one of: triggering completion, synchronization completion and constraint relation of target data, wherein the triggering completion is used for triggering the execution state of the post node to be changed into completion in a second preset execution state of the front node, the synchronization completion is used for triggering the execution state of the two nodes in an association relation to be changed into completion when the two nodes with the association relation are both in a completion state, and the constraint relation of the target data is that a size constraint relation exists between the target data of the front node and the target data of the post node;
the constructing of the incidence relation between the current node and the incidence node includes:
generating an incidence relation construction request according to a current node identifier, an incidence node identifier and an incidence type with incidence relation in incidence relation configuration information, and sending the incidence relation construction request to an incidence node, wherein the incidence relation construction request is used for triggering the construction of the incidence relation between the current node and the incidence node; alternatively, the first and second electrodes may be,
and receiving an incidence relation construction request sent by the incidence node, and constructing the construction incidence relation between the current node and the incidence node based on the incidence relation construction request.
2. The method of claim 1, wherein the creation information comprises a parent milestone identification, a number of child milestones in the parent milestone, and a creation requirement for each child milestone identification and each child milestone;
the creating instruction in response to the project milestones sequentially creates the parent milestone, the child milestones and the key task nodes based on the creating information to form the project milestones, including:
creating a parent milestone based on the parent milestone identification in response to a creation instruction of the parent milestone;
creating, in response to a creation instruction of the child milestones, a plurality of child milestones of the parent milestone based on the number of child milestones and each child milestone identification;
and in response to the creation instruction of the key task nodes, creating a plurality of key task nodes in which each sub-milestone is located based on the creation requirement of each sub-milestone to form the project milestone.
3. The method of claim 1, wherein the constructing the association relationship between the current node and the associated node comprises:
creating a transmission channel between two nodes having an association relationship, and setting an association type between the two nodes.
4. The method according to claim 1, before creating a transmission channel between two nodes having an association relationship, further comprising:
and verifying the association relationship construction request based on preset association relationship configuration information.
5. The method according to claim 1, wherein the two nodes having an association relationship comprise a front node and a back node;
the method further comprises the following steps:
and if the execution state of the front node is detected to be switched to a preset state, generating trigger information and sending the trigger information to a rear node.
6. A processing apparatus for project milestones, comprising:
the system comprises an information acquisition module, a task execution module and a task execution module, wherein the information acquisition module is used for acquiring the creation information of project milestones, and the project milestones comprise parent milestones, a plurality of child milestones in the parent milestones and a plurality of key task nodes in each child milestone;
a milestone creation module, configured to create, in response to a creation instruction of the project milestone, the parent milestone, the child milestones, and the key task nodes in sequence based on the creation information to form the project milestone;
an association relationship creating module, configured to, after the parent milestone, each child milestone, and each mission-critical node are sequentially created based on the creation information, construct, for a current node in the project milestone, an association relationship between the current node and an association node, where the current node and the association node are one of: parent milestones, child milestones, and mission critical nodes, the current node and the associated node belonging to different project milestones, wherein the association type of the current node and the associated node is one of: triggering completion, synchronization completion and constraint relation of target data, wherein the triggering completion is used for triggering the execution state of the post node to be changed into completion in a second preset execution state of the front node, the synchronization completion is used for triggering the execution state of the two nodes in an association relation to be changed into completion when the two nodes with the association relation are both in a completion state, and the constraint relation of the target data is that a size constraint relation exists between the target data of the front node and the target data of the post node;
the incidence relation creating module comprises:
the first creating unit is used for generating an association relationship construction request according to a current node identifier, an association node identifier and an association type which have an association relationship in association relationship configuration information, and sending the association relationship construction request to an association node, wherein the association relationship construction request is used for triggering the construction of the association relationship between the current node and the association node; alternatively, the first and second electrodes may be,
and the second creating unit is used for receiving an incidence relation building request sent by the incidence node and building the building incidence relation between the current node and the incidence node based on the incidence relation building request.
7. An electronic device, characterized in that the device comprises:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of processing project milestones of any of claims 1-5.
8. A storage medium containing computer-executable instructions for performing the method of processing project milestones of any of claims 1-5 when executed by a computer processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111090790.3A CN113537954B (en) | 2021-09-17 | 2021-09-17 | Project milestone processing method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111090790.3A CN113537954B (en) | 2021-09-17 | 2021-09-17 | Project milestone processing method and device, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113537954A CN113537954A (en) | 2021-10-22 |
| CN113537954B true CN113537954B (en) | 2022-01-18 |
Family
ID=78092863
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111090790.3A Active CN113537954B (en) | 2021-09-17 | 2021-09-17 | Project milestone processing method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113537954B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101266669A (en) * | 2008-05-06 | 2008-09-17 | 广州市中联创通电脑有限公司 | Project process workflow based on plan template and its implementation method |
| CN104700239A (en) * | 2015-04-09 | 2015-06-10 | 山东中实易通集团有限公司 | Debugging method for improving nuclear power station debugging safety and quality |
| CN107153944A (en) * | 2017-02-22 | 2017-09-12 | 上海爱韦讯信息技术有限公司 | The method and system of task are researched and developed based on Flow driving |
| CN110321467A (en) * | 2019-05-30 | 2019-10-11 | 广东民航机场建设有限公司 | Airport engineering project information methods of exhibiting, device, system, equipment and medium |
| CN111178680A (en) * | 2019-12-09 | 2020-05-19 | 河北建投新能源有限公司 | Wind power plant engineering quality overall process management system, method and equipment |
| CN112561275A (en) * | 2020-12-08 | 2021-03-26 | 中铁第四勘察设计院集团有限公司 | Method and device for managing whole process of research and development project, computer equipment and readable medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112581104A (en) * | 2020-12-31 | 2021-03-30 | 北京达佳互联信息技术有限公司 | Information processing method, information processing apparatus, electronic device, storage medium, and program product |
| CN112633853A (en) * | 2020-12-31 | 2021-04-09 | 北京达佳互联信息技术有限公司 | Project management method and device and electronic equipment |
-
2021
- 2021-09-17 CN CN202111090790.3A patent/CN113537954B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101266669A (en) * | 2008-05-06 | 2008-09-17 | 广州市中联创通电脑有限公司 | Project process workflow based on plan template and its implementation method |
| CN104700239A (en) * | 2015-04-09 | 2015-06-10 | 山东中实易通集团有限公司 | Debugging method for improving nuclear power station debugging safety and quality |
| CN107153944A (en) * | 2017-02-22 | 2017-09-12 | 上海爱韦讯信息技术有限公司 | The method and system of task are researched and developed based on Flow driving |
| CN110321467A (en) * | 2019-05-30 | 2019-10-11 | 广东民航机场建设有限公司 | Airport engineering project information methods of exhibiting, device, system, equipment and medium |
| CN111178680A (en) * | 2019-12-09 | 2020-05-19 | 河北建投新能源有限公司 | Wind power plant engineering quality overall process management system, method and equipment |
| CN112561275A (en) * | 2020-12-08 | 2021-03-26 | 中铁第四勘察设计院集团有限公司 | Method and device for managing whole process of research and development project, computer equipment and readable medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113537954A (en) | 2021-10-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112036824A (en) | Business approval method, system, storage medium and electronic equipment | |
| US8539514B2 (en) | Workflow integration and portal systems and methods | |
| US11188560B2 (en) | Synchronizing object in local object storage node | |
| CN111813409A (en) | Code generation method, device, equipment and storage medium of interactive interface | |
| CN110688111A (en) | Configuration method, device, server and storage medium of business process | |
| US11206300B2 (en) | Providing instructions during remote viewing of a user interface | |
| CN111626602A (en) | Service processing method, service processing device, storage medium and electronic equipment | |
| CN115688715A (en) | Report generation method and device and computer readable medium | |
| CN114358742A (en) | Workflow execution method, device, equipment and storage medium | |
| CN112988600A (en) | Service scene testing method and device, electronic equipment and storage medium | |
| CN111061522B (en) | Method, device, equipment and storage medium for generating front-end card assembly based on back end | |
| CN110555732B (en) | Marketing strategy pushing method and device and marketing strategy operation platform | |
| CN113537954B (en) | Project milestone processing method and device, storage medium and electronic equipment | |
| CN113535318B (en) | Information reply method and device, storage medium and electronic equipment | |
| CN114661289A (en) | Knowledge and data driving-based micro application development system and method | |
| CN114253920A (en) | Transaction reordering method, device, equipment and readable storage medium | |
| CN113296772A (en) | Page configuration method and device, computer equipment and readable storage medium | |
| CN114201144A (en) | Micro service system construction method, device and medium based on domain-driven design | |
| US20170293599A1 (en) | Checklist Contexts and Completion | |
| CN113296912A (en) | Task processing method, device and system, storage medium and electronic equipment | |
| CN113779117A (en) | Data monitoring method and device, storage medium and electronic equipment | |
| CN115543969B (en) | Data migration method, device, equipment and medium | |
| CN115858049B (en) | RPA flow componentization arrangement method, device, equipment and medium | |
| US11604768B2 (en) | Optimizing resources in a disaster recovery cleanup process | |
| CN112445790B (en) | Report data storage method, device, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |