Method, device, electronic device and storage medium for generating a project flow

The method and apparatus for generating project flows address the complexity of project organization by determining process nodes and dependencies, improving project management efficiency through standardized planning and digitization.

JP2024543144AActive Publication Date: 2024-11-19BEIJING ZITIAO NETWORK TECH CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2024531199
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-11-26
Filing Date
2022-11-03
Publication Date
2024-11-19
Estimated Expiration
2042-11-03

AI Technical Summary

Technical Problem

The increasing complexity and scale of projects make it difficult to effectively organize and integrate the work contents of multiple stages, leading to low project promotion efficiency.

Method used

A method and apparatus for generating a project flow that determines process nodes, their attributes, dependencies, and execution information, using modules to organize and plan projects efficiently.

Benefits of technology

This approach provides a standard and concise means for project organization and planning, enhancing project management efficiency by clarifying and digitizing project processes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024543144000001_ABST
    Figure 2024543144000001_ABST
Patent Text Reader

Abstract

An embodiment of the present disclosure provides a method, an apparatus, an electronic device, and a storage medium for generating a project flow, the method including: determining at least one process node corresponding to a target to-be-deployed project; determining node attribute information of the at least one process node; determining node dependencies of the at least one process node; and determining execution project flow information corresponding to the target to-be-deployed project based on the node dependencies and the node attribute information.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] This application claims priority to a Chinese patent application bearing application number 202111422126.4, filed with the State Intellectual Property Office of China on November 26, 2021, the entire contents of which are incorporated herein by reference.

[0002] TECHNICAL FIELD The present disclosure relates to the field of computer technology, and relates to a method, an apparatus, an electronic device, and a storage medium for generating a project flow, for example. [Background technology]

[0003] When an enterprise develops a product or expands its business in response to market and user needs, the relevant internal team must first establish a corresponding project based on the current work content. The project manager must organize and plan the project from the overall and detailed perspectives to promote the work of multiple stages of the project.

[0004] However, as the scale of the project continues to expand and the complexity of the project stages continues to deepen, the project process organization and planning work becomes more and more difficult. At the same time, there is a lack of effective means for organizing and integrating the work content of the project stages, which leads to low efficiency in project promotion. Summary of the Invention

[0005] The embodiments of the present disclosure provide a method, an apparatus, an electronic device, and a storage medium for generating a project flow that provides a standard and concise means for organizing and planning a project, and improves the convenience of building a corresponding project process based on an actual project.

[0006] In a first aspect, an embodiment of the present disclosure comprises: determining at least one process node corresponding to a target to-be-deployed project; and determining node attribute information of the at least one process node; determining node dependencies of the at least one process node; determining execution project flow information corresponding to the target deployment project based on the node dependency relationships and the node attribute information.

[0007] In a second aspect, an embodiment of the present disclosure comprises: a process node determination module configured to determine at least one process node corresponding to a target to-be-deployed project and determine node attribute information of the at least one process node; a node dependency determination module configured to determine node dependencies for the at least one process node; and an execution project flow information determining module configured to determine execution project flow information corresponding to the target deployment project based on the node dependency relationship and the node attribute information.

[0008] In a third aspect, an embodiment of the present disclosure comprises: one or more processors; a storage device configured to store one or more programs; The present invention further provides an electronic device that, when the one or more programs are executed by the one or more processors, causes the one or more processors to implement a method for generating a project flow described in any of the embodiments of the present disclosure.

[0009] In a fourth aspect, an embodiment of the present disclosure further provides a storage medium including computer-executable instructions, which, when executed by a processor of a computer, are configured to perform a method for generating a project flow as described in any of the embodiments of the present disclosure. [Brief description of the drawings]

[0010] Throughout the drawings, the same or similar reference numbers refer to the same or similar elements, and it should be understood that the drawings are schematic and that elements and components are not necessarily drawn to scale.

[0011] [Figure 1] FIG. 2 is a schematic diagram of a method for generating a project flow according to one embodiment of the present disclosure. [Diagram 2] FIG. 13 is a schematic flow diagram of a method for generating a project flow according to another embodiment of the present disclosure. [Diagram 3] FIG. 13 is a schematic diagram of a final generated project flow according to an embodiment of the present disclosure. [Figure 4] 1 is a template for generating a project flow according to one embodiment of the present disclosure. [Diagram 5] FIG. 13 is a schematic flow diagram of a method for generating a project flow according to another embodiment of the present disclosure. [Figure 6] 13 illustrates a node information editing page according to an embodiment of the present disclosure. [Figure 7] 1 is a node scheduling page according to one embodiment of the present disclosure. [Figure 8] 13 illustrates a node-associated role selection page according to one embodiment of the present disclosure. [Figure 9] FIG. 2 is a structural block diagram of an apparatus for generating a project flow according to an embodiment of the present disclosure. [Figure 10] FIG. 1 is a structural schematic diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] It should be understood that steps recited in method embodiments of the present disclosure may be performed in different orders and / or in parallel. Additionally, method embodiments may include additional steps and / or omit performance of steps as shown. The scope of the present disclosure is not limited in this respect.

[0013] As used herein, the term "including" and variations thereof are intended to be open inclusive, i.e., "including, but not limited to." The term "based on" means "based at least in part on." The term "in one embodiment" refers to "at least one embodiment," the term "in another embodiment" refers to "at least one other embodiment," and the term "in some embodiments" refers to "at least some embodiments." Relevant definitions of other terms are provided below.

[0014] It should be noted that concepts such as "first" and "second" referred to in this disclosure are merely intended to distinguish different devices, modules or units, and are not intended to limit the order or interdependence of functions performed by these devices, modules or units.

[0015] It should be understood that the modifications "one" and "multiple" referred to in the present disclosure are exemplary and not limiting, and that a person of ordinary skill in the art should understand "one or more" unless otherwise specified in the present specification.

[0016] 1 is a schematic diagram of a method for generating a project flow according to an embodiment of the present disclosure. This embodiment is applicable to a situation of determining an execution project flow for a plurality of projects waiting to be deployed, and the method can be executed by an apparatus for generating a project flow, which can be realized in the form of software and / or hardware, and the hardware can be an electronic device, such as a mobile terminal, a PC terminal, or a server, etc.

[0017] Before introducing the technical solution, an application scenario may be illustrated, and the technical solution can be applied to any scenario that requires generating a project flow for a project. For example, an enterprise creates a project according to market and user needs, and wants to create a visualized and digitalized project flow for the project. At this time, the execution project flow can be determined according to the technical solution.

[0018] As shown in FIG. 1, the method of this embodiment includes:

[0019] In S110, at least one process node corresponding to the target waiting for deployment project is determined, and node attribute information of the at least one process node is determined.

[0020] For a project established by an enterprise for a certain product or business, the relevant personnel need to establish a project process corresponding to the actual work content of the project, so as to grasp and control multiple stages in the project after it is deployed. For example, it can be understood that the personnel need to first clarify the needs and actual work content of the project, and then organize and plan the entire project according to the needs of project management, divide the project into multiple stages, determine the main idea corresponding to the executor and work content of each stage of the project, and finally obtain the project process in the form of a document, flow chart or other specific form corresponding to the project in a computer.

[0021] Based on this, in this embodiment, if a project or product needs to be completed and a corresponding implementation project needs to be deployed, this project or product can be set as a target deployment waiting project, such as a project established by an enterprise to evaluate and develop an Internet product after the enterprise has conceived and launched an Internet product according to users' needs.

[0022] In this embodiment, the process node is the carrier of the relevant information of the stages of the target deployment project, and there may be one or more, and the specific number is determined according to the actual work content of the project and the needs of project management. At the same time, one process node may correspond to a certain stage in the project, or a certain step in a single stage of the project, for example, the process nodes of the target deployment project include review triggering node, score estimation node, need profit analysis node, development node, test node and release node, among which the review triggering node, score estimation node and need profit analysis node correspond to the start-up stage of the project, the development node and test node correspond to the development and testing stage of the project, and the release node corresponds to the online stage of the project.

[0023] For multiple process nodes of the target deployment project, there is further corresponding node attribute information. In this embodiment, the node attribute information may be information reflecting the workers and work contents of each stage of the project. For example, the node attribute information of the development node in the above example may include the department developing the product, the developer, and the time period required for development.

[0024] In the actual application process, for a target-to-be-allocated project, its process nodes and the node attribute information of each process node can be determined by a specific platform or system. Illustratively, after a target-to-be-allocated project is determined, an operator can use a specific control in a platform or system for generating a project flow to establish a corresponding process node for each stage or step of the project according to the actual work content of the project and the needs of managing the project process, and configure corresponding node attribute information for each process node according to the actual work content of the project.

[0025] Continuing with the above example, if the target-to-be-allocated project includes a start-up stage, a development test stage, and an online stage, the project manager can enter the space allocation background in the project flow generation platform, and select from multiple pre-allocated nodes by clicking, dragging, etc., a review trigger node, a score estimation node, a need profit analysis node, etc., suitable for the project as process nodes representing the above multiple stages. By selecting or editing the corresponding responsible department, developer, and development time period for each process node according to the actual work content of the project and the needs of project management, the node attribute information of each process node can be obtained.

[0026] At S120, node dependencies of at least one process node are determined.

[0027] In this embodiment, after the process nodes and the node attribute information of each process node are determined for the target deployment project, it is necessary to further determine the node dependency of at least one process node. Among them, the node dependency is also called logic relationship. In project management, when there is only one process node, the node dependency of the node is obtained after the start and end information of the node is determined. When there are multiple process nodes, the node dependency indicates a relationship in which the change of one of the two nodes affects the other one. Usually, it includes a forced node dependency (an inherent node dependency between multiple nodes), a freely manageable node dependency (a node dependency determined by the actual work content of the project and the needs of project management), and an external node dependency (a node dependency between a node and other external factors). Those skilled in the art should understand that the node dependency between process nodes can at least reflect the execution order of the work of multiple stages of the project.

[0028] It should be noted that, when generating a project flow of a target-to-be-configured project by a specific platform or system, there are multiple ways to determine the node dependency of the process nodes. For example, a user can connect multiple process nodes by clicking, dragging, etc. It can be understood that the connection lines between the nodes can be directional, and further, the association relationship between the nodes can be determined by setting corresponding indicators for each process node and editing the association relationship between the indicators in the configuration interface. Those skilled in the art should understand that the method of determining the process node dependency can be selected according to the platform or system actually selected by the user, and the embodiment of the present disclosure is not specifically limited here.

[0029] Continuing with the above example, based on the platform or system for generating a project flow, when it is determined that the process nodes of the target deployment awaiting project include a review initiation node, a score estimation node, a needs revenue analysis node, a development node, a test node and a release node, a project manager can use a dragging method to draw connecting lines with arrows between the multiple nodes to determine the execution order of the work in the multiple stages of the project as follows: first initiate a review of the project, then evaluate the project, then analyze the needs revenue of the project, then develop a product related to the project, test the product, and finally put the project product online and release it.

[0030] At S130, execution project flow information corresponding to the target deployment project is determined based on the node dependency relationship and the node attribute information.

[0031] In this embodiment, after the node attribute information of the process nodes for the target deployment waiting project is determined, based on the determined node dependencies between the process nodes, the association between the node attribute information of multiple nodes can be further established to obtain the execution project flow of the project.

[0032] For example, the execution project flow information of the target-to-be-allocated project can be determined based on the determined node dependency and node attribute information. In this embodiment, the execution project flow can be understood as the project process of the target-to-be-allocated project, i.e., the execution sequence of the substantial work of the multiple stages of the project. The execution project flow information also includes node attribute information of at least one process node, as well as the association relationships between the performers of the multiple nodes and the association relationships between the substantial work contents of the multiple stages. Finally, the determined execution project flow information is displayed in a document format, a flowchart format, or other format in a specific platform or system.

[0033] Continuing with the above example, after the node dependencies of the review trigger node, score estimation node, need profit analysis node, development node, test node and release node of the target deployment waiting project, as well as the responsible department, executor and task execution period of each node are determined, the platform or system for generating project flow can determine the handover tasks of the responsible department of each node of the project, the task files that the executor of each node needs to transmit, and the time period of the task execution period of each node in the entire project. The flowchart of the project is displayed on a specific page of the platform or system, and the project manager can click on multiple nodes in the flowchart to check the node attribute information of the node and the node dependency between the node and other nodes.

[0034] By determining the execution project flow information of the target-distribution-awaiting project, the work tasks of multiple nodes of the project can be automatically arranged and planned in a standardized form from the whole and the details, and after the project is deployed, the project manager can monitor the progress and completion status of the work of each stage of the project according to the obtained project process, thereby realizing high-efficiency management of the project. For example, in a certain platform or system, the project manager can view the dynamic project process diagram on a certain page and grasp the progress and completion status of the project based on the different status information of multiple nodes in the diagram, and at the same time, the execution project flow information includes the node dependency of at least one process node of the project, and multiple teams in charge of project evaluation, research and development, and online can determine their own work contents and handover tasks according to the node dependency, thereby realizing the integration of multiple departments in the team and executors of multiple stages of the project, which is favorable for the promotion of high efficiency of the project.

[0035] In addition, after obtaining the execution project flow information based on the node attribute information and the node dependency of at least one process node, the obtained execution project flow information and project process diagram may be stored in the template repository of the platform or system in the form of a template, and the template may be marked with a corresponding mark according to the description information of the project. If the execution project flow information and project process diagram need to be determined for other projects and have similar work contents and project management needs as the project waiting for target deployment, the execution project flow information and project process diagram of other projects can be directly determined by selecting the template saved this time from the template repository. Those skilled in the art should understand that in the platform or system generating the project flow, the user may further reasonably modify some deployment information in the template (such as the node attribute information of each process node and the node dependency between nodes) according to the actual situation of other projects, and the embodiments of the present disclosure will not be described again here.

[0036] The technical solution of this embodiment determines at least one process node corresponding to the project waiting for target allocation, and determines the node attribute information of each process node to clarify the specific work content in each process of the project, determines the node dependency of at least one process node, and determines the execution project flow information corresponding to the target allocation project based on the node dependency and the node attribute information, thereby providing a standard and concise means for project organization and planning, and improving the convenience of constructing the corresponding project process based on the actual project. At the same time, the obtained clear and digitized project process facilitates workers' monitoring and management of the entire project and the work of multiple stages, and is favorable to the promotion of high efficiency of the project.

[0037] FIG. 2 is a flow diagram of a method for generating a project flow according to another embodiment of the present disclosure. Based on the above embodiment, a process node is determined according to the execution process of the project, and when it is detected that the process node is triggered, a node information editing page is displayed so that the user can customize the node attribute information with a higher degree of freedom, and the node dependency between the nodes is determined according to the preceding node indicator, or the node dependency between the nodes is determined according to the execution process of the project, thereby realizing a logical arrangement for the execution process of the project, determining the execution order of multiple process nodes based on the node dependency, generating execution project flow information, and being favorable for the efficient promotion of the project. The exemplary embodiment may refer to the technical solution of this embodiment. Wherein, technical terms similar or corresponding to the above embodiment will not be described again here.

[0038] As shown in FIG. 2, the method includes the following steps.

[0039] In S210, an execution process corresponding to the target waiting-for-allocation project is determined, and at least one process node is determined according to the execution process.

[0040] Among them, the execution process corresponding to the target-assigned project includes multiple stages in the process from project launch to project termination. It can be understood that the execution process is obtained by dividing and summarizing the work contents according to the needs of project management based on the substantial work contents of the project. In order to obtain the execution project flow information of the project, corresponding process nodes can be selected or created for multiple stages in the execution process in a specific platform or system, and the determined at least one process node corresponds to the execution process. The above process will be specifically described below with reference to FIG. 3.

[0041] Referring to FIG. 3, after the target waiting project is determined, in the platform or system for generating project flow, a space arrangement option can be selected, and a task of arranging the project flow can be created for the project on the page corresponding to the space arrangement. Based on the actual work content of the project and the project management needs of the enterprise, it can be determined that the execution process of the project includes multiple stages such as project review, research and development, and release. Therefore, in the task processing page for arranging the project flow, the project manager can select or create nodes such as needs creation, discussion alignment, product design, inline review, UX design, technical review, research and development completion, dark launch, release note entry, full release, and end as process nodes. It can be understood that the above nodes jointly reflect the execution process of the project and are the division and summary of the work content of multiple stages of the project.

[0042] For example, the process node includes a master process node and a slave process node, among which, for a plurality of process nodes corresponding to an executing process, the master process node and the slave process node are relative concepts, and the setting of the master-slave concept in the process node can at least reflect the execution order of the plurality of process nodes and the association relationship between the nodes.

[0043] Based on this, in the process of determining at least one process node according to the running process, at least one master process node is determined according to the running process, and for each master process node, when it is detected that the current master process node is triggered, a slave process node corresponding to the current master process node is added, and when it is detected that the slave process node is triggered, the slave process node is set as the current master process node. The process will be described below with reference to FIG. 3.

[0044] Referring to Fig. 3, for the needs creation node and the discussion matching node in the execution process, the project team must first clarify the needs information of the project, and then decide the actual work content of the project through discussion among multiple departments. Therefore, the needs creation node corresponding to the first stage of the project may be the master process node, and the discussion matching node in the next stage may be the slave process node. After the project person adds the needs creation node on the relevant page of the space layout according to the execution process, the project person can perform a click operation on the node, and after the operation is detected by the platform or the system, a discussion matching node corresponding to the next stage of the project can be automatically added for the node.

[0045] Similarly, for the discussion matching node and the product design node, when the trigger operation on the matching node is detected, the platform or system can set the matching node as the current master process node, and automatically add a product design node corresponding to the next one stage of the project. At the same time, for the same master process node, the slave process nodes can be not only multi-level, but also multiple. Take the project execution process in FIG. 3 as an example, when the needs creation node is set as the master process node, the discussion matching node and the product design node corresponding to the multiple stages of the project after the node are the multi-level slave process nodes of the node, and at the same time, when the research and development completion node is set as the master process node, the dark launch node and the release note entry node are both slave process nodes of the node. It can be understood that when multiple slave process nodes are at the same level, the work tasks corresponding to multiple nodes can be executed in parallel.

[0046] In addition, since the execution process and process nodes of the target allocation waiting project are generated by a specific platform or system, before the process nodes are determined, the platform or system may further pre-edit a number of templates that correspond to a number of types of projects and have a certain degree of versatility, based on which the process nodes for the execution process of the project can be directly determined by the templates.

[0047] For example, when it is detected that a template creation control on a target page is triggered, a configuration page corresponding to the creation of a template is popped up, in which the configuration page includes a template type control and a control for whether to reuse a template in the related technology, and based on the trigger operation on the configuration page, a waiting-to-use template corresponding to the target waiting-to-be-deployed project is determined, and at least one process node corresponding to the target waiting-to-be-deployed project is determined based on the waiting-to-use template.

[0048] In the actual application process, the projects created by an enterprise are generally complex, so the process nodes determined for the execution process of the project may be as shown in FIG. 4. As can be seen from FIG. 4, the multi-level process nodes indicate the stages of the project, and a single project stage may further include multiple work tasks. The project manager can select a node to make the node a master process node (e.g., the "Data Development" node selected by the project manager in FIG. 4 by clicking), and then click the plus sign in the upper right corner of the node or click the "Add Node" control in the lower left corner to create slave process nodes (e.g., the "Data Test" node in FIG. 4) corresponding to the subsequent stages of the project for the node. At the same time, since the platform or system for generating the project flow can provide the function of creating and reusing templates, after generating the execution project flow for the project according to the subsequent steps of the embodiment of the present disclosure, the generated project flow can be stored, updated, and deleted as a template for a certain type of project by clicking another control in the lower left corner.

[0049] In S220, when it is detected that the process node is triggered, a node information editing page corresponding to the process node is displayed, and node attribute information of the process node is edited in at least one editable item of the node information editing page.

[0050] In this embodiment, after a plurality of process nodes are determined for the execution process of the target waiting project, if a trigger operation for the node is detected, a node information editing page may be further displayed. For example, after a project manager performs a click operation for a process node on the space arrangement page of the platform or system, the current space arrangement page transitions to a node information editing page corresponding to the node. In the node information editing page, multiple types of editing operations, such as, for example, entry, selection, and modification, can be performed on at least the node, and it can be understood that the information obtained after the operation is completed is the node attribute information corresponding to the node.

[0051] In addition, the node attribute information includes attribute information of multiple dimensions of the node, and this attribute information can not only reflect the actual work content of multiple stages of the project from multiple dimensions, but also determine the execution logic and execution sequence of the work corresponding to multiple nodes.

[0052] In S230, a node dependency relationship of at least one process node is determined according to a preceding node indicator in the node attribute information, or sequence information of at least one process node is determined according to an execution process of the project awaiting target placement, and a node dependency relationship of at least one process node is determined according to the sequence information.

[0053] In this embodiment, there are at least two ways to determine the dependency relationship of at least one process node. The first way is to determine sequence information of at least one process node in a platform or system that generates a project flow based on the execution process of a project waiting for target allocation, and establish node dependency relationships between multiple process nodes according to the determined sequence information. In this way, it can be understood that the node dependency relationships between nodes are substantially determined according to the actual work contents in multiple stages of the project and the needs of project management.

[0054] The second method is to determine an antecedent node indicator of each node in the node attribute information, and determine the node dependency of at least one process node according to the indicator. It can be understood that the execution process of the project does not flow to the current node related to the antecedent node until the project task or project event represented by the antecedent node is completed. It can be understood that the current node may have one or more antecedent nodes. At the same time, the current node itself may be the antecedent node of one or more nodes in the subsequent execution process. In the platform or system for generating a project flow, such node dependency is determined by the antecedent node indicator in the node attribute information of the current node. The following description will continue to take FIG. 4 as an example.

[0055] Referring to FIG. 4, when the "waiting for release" node is taken as the current node, the preceding node of the node can be determined by editing the node attribute information in the node information editing page. For example, five node indicators, namely "iOS test", "Android test", "service test", "front-end test" and "Data test", can be selected as preceding node indicators in the page. Based on the above five preceding node indicators, the platform or system can determine the node dependency between the above five nodes and the "waiting for release" node, that is, only after the iOS test task, the Android test task, the service test task, the front-end test task and the Data test task are all completed, the execution process of the project will flow to the "waiting for release node". At the same time, in the node information editing pages corresponding to the "online safety review" node and the "open platform file update" node, the node indicator of the "waiting for release" node is taken as the preceding node indicator of the above two nodes, thereby determining the node dependency between the online safety review task, the open platform file update task and the waiting for release task. That is, only after the execution of the task or event corresponding to the "waiting for release" node is completed, the execution process of the project flows to the "online security review" node and the "open platform file update" node.

[0056] For example, the preceding node indicator in the node attribute information is adjusted in accordance with the node dependency relationship, and the node attribute information is updated based on the adjusted preceding node indicator.

[0057] In the actual application process, when the actual work content or project management needs of a target-to-be-allocated project change, not only will the node attribute information of the related process nodes change, but new node dependencies may also arise between different process nodes. For a platform or system that generates a project flow, when generating a project flow based on new node dependencies of multiple process nodes of a project, it is necessary to modify the preceding node indicator in the related node attribute information according to the node dependencies, so as to realize the update to the node attribute information. The following description continues to take FIG. 4 as an example.

[0058] Referring to Figure 4, if an enterprise decides not to continue developing applications for iOS devices related products after the target deployment waiting project has been reviewed twice, it needs to delete the iOS-related branch from the execution process of the project. Based on this, in the platform or system generating the project flow, the "iOS score estimation scheduling", "iOS development" and "iOS testing" nodes are deleted, and at the same time, in the node attribute information corresponding to the "waiting for release" node, the node indicator corresponding to the "iOS testing" node among its predecessor node indicators is deleted, thereby realizing the update of the node attribute information of the related process nodes of the project.

[0059] In S240, an execution order corresponding to at least one process node is determined based on the node dependency relationship, and execution project flow information of the project waiting for target allocation is generated according to the node name and the node dependency relationship in the node attribute information of the at least one process node.

[0060] In this embodiment, after the node dependency of at least one process node of the target-to-be-allocated project is determined, the platform or system for generating the project flow determines the execution sequence corresponding to at least one node. It can be understood that the trigger conditions, completion conditions, and associated relationships of the tasks or events of the multiple stages of the project are determined. According to the node names in the multiple node attribute information and the node dependency between the multiple nodes, the execution project flow information can be generated in the form of a flowchart. At the same time, the project flow information is displayed on a specific page of the platform or system so that the relevant workers can monitor and manage the completion status of the entire project and the tasks of the multiple stages. The following description will be given with reference to FIG. 3 as an example.

[0061] 3, after the node attribute information of multiple nodes of the project and the node dependency between the nodes are determined, multiple process nodes can be connected with lines to display the execution process of the project waiting for target configuration in the form of left to right. At the same time, a mark representing node status information is set for each node, for example, a circle mark for each node in the figure, among which different marks can represent different status information, the circle mark with a check mark indicates that the execution of the task or event corresponding to the node has been completed and passed the assessment of the relevant authorized user, the black circle mark indicates that the task or event corresponding to the node has not been completed and the task or event has exceeded the pre-assigned work deadline for the task or event, and should be paid attention to, the circle mark with a diagonal line indicates that the project is currently executing the task or event corresponding to the node, and the gray circle mark indicates that the execution process of the project has not yet shifted to the node, that is, the task or event of the preceding node related to the node has not been completed, and the task or event of the node cannot be triggered.

[0062] In actual application, after generating execution project flow information for a project awaiting target deployment, project personnel can monitor and manage multiple process nodes through a platform or system; at the same time, the implementers corresponding to the multiple process nodes can similarly obtain the node attribute information of the corresponding nodes through the platform or system, thereby clarifying the corresponding relationships with other departments in their current project, and at the same time, execute corresponding tasks or events based on the node attribute information.

[0063] The technical solution of this embodiment determines a process node according to the execution process of the project, and when it is detected that a process node is triggered, a node information editing page is displayed, so that the user can customize the node attribute information with greater freedom, and determines the node dependency relationships between nodes according to the preceding node indicator, or determines the node dependency relationships between nodes based on the execution process of the project, thereby realizing a logical organization of the execution process of the project, determining the execution order of multiple process nodes based on the node dependency relationships, and generating execution project flow information, which is beneficial for promoting the project with high efficiency.

[0064] 5 is a schematic diagram of a method for generating a project flow according to another embodiment of the present disclosure, based on the above embodiment, the node attribute information includes attribute information of multiple dimensions of the process node, and the information is edited and arranged in the node editing page to realize a high degree of customization of the execution process of the project waiting for target arrangement in a visualized manner, and at the same time provide the user with a means to modify the execution process of the project. The exemplary embodiment may refer to the technical solution of this embodiment, where the same or corresponding technical terms as those in the above embodiment will not be described again here.

[0065] As shown in FIG. 5, the method includes the following steps.

[0066] In S310, at least one process node corresponding to a target to-be-allocated project is determined, and node attribute information of the at least one process node is determined.

[0067] At S320, node dependencies of at least one process node are determined.

[0068] At S330, execution project flow information corresponding to the target deployment project is determined based on the node dependency relationship and the node attribute information.

[0069] In S340, the node corresponding to the node attribute information is processed based on the editing status of each attribute information in the node attribute information.

[0070] In this embodiment, the node attribute information includes multiple dimensions of attribute information of the node. For example, the node related information includes at least one of the following: node indicator, node name, node cooperation user, node authorization information, node execution time length, node operation type, node transfer type, node restriction type, preceding node indicator, and node event. In the editing page, editable items corresponding to any of the above multiple information can be provided. The above information will be specifically described below with reference to FIG. 6.

[0071] Referring to FIG. 6, the node label is the ID of the process node. It can be understood that the node label is unique for any node, and setting a node label for each node is advantageous for a platform or system to call these nodes through an application programming interface (API), and further realize the arrangement of nodes and the generation of project flows. For the "Data Development" process node, the corresponding node label is "waiting_for_data_development". The node name reflects the event that the project needs to complete at the node, and may be a key field, for example, "Data Development" indicates the work related to the big data development of the project that needs to be completed at the stage. The naming of the project stages facilitates intuitive display of the project task stages corresponding to the node to the user, and is also advantageous for the interaction between the user and the platform or system that generates the project flow.

[0072] In this embodiment, if it is detected that the node mark of the current process node has changed and an upgrade operation has been performed on the current process node, the current process node and the process nodes that the current process node depends on are deleted. For example, a project manager can modify the node mark of the current node in a platform or system, and after the modification operation on the node mark is detected in the platform or system, the current node and the already edited node attribute information of the node before the node mark is modified are deleted. At the same time, according to the node dependency between multiple process nodes, other nodes that have a node dependency with the current node are also deleted. Similarly, the already placed node attribute information of other nodes is also deleted. This process can be understood that after modifying the work content of any one current stage of the project, the work content of other stages that have a node dependency with the project stage will also change.

[0073] Still referring to FIG. 6, in the process of actually executing the project, according to the needs of project management, some nodes in the execution process may also need to be confirmed by many people after completion, and the project task will not flow to the next node in the execution process until all confirmations by many people are completed. Based on this, in the process of editing the node attribute information, editing of node restriction type, editing of node transfer type and editing of node cooperation user are further included. For the node restriction type, "Yes" or "No" can be selected in the option of "Whether it is a restricted node" which respectively indicates whether the node is a restricted node or a non-restricted node, and for the node transfer type, "Yes" or "No" can be selected in the option of "Whether it needs confirmation by multiple people" which respectively indicates whether the task corresponding to the node needs to be confirmed by multiple people after completion.

[0074] For example, if the node restriction type in the node attribute information of the current process node is the first type, when the processing of the current process node by the target operation user corresponding to the first type is detected, the node state of the current process node is changed. Taking the "Data development" node in Fig. 6 as an example, the current process node is set to the restriction type (first type) by the option of "restricted node or not" in the node attribute information, and at this time, after the work task (Data development task) of the node is completed, the project person in charge (target operation user corresponding to the first type) must assess and confirm the related work task before the node state information can be modified from "under development" to "development completed", and the project does not flow to the next node ("data test" node) in the execution process. Note that, if the node restriction type is the first type and there are multiple corresponding target operation users, the project task in the execution process does not flow for the task of the node unless one of them confirms the completion status of the task.

[0075] For example, if the node restriction type in the node attribute information of the current process node is the second type and the node cooperation user includes a cooperation user, the node status of the current process node is updated according to the trigger operation of the cooperation user on the current process node. Take the "Data development" node in Fig. 6 as an example, the current process node is set to a non-restricted type (second type) according to the option of "restricted node or not" in the node attribute information, and user A and user B other than the project person in charge are selected from the node cooperation users. At this time, after the work task (Data development task) of the node is completed, in addition to the project person in charge checking the project, any one of the selected node cooperation users A and B can also check the task completion status, and the node status information can be modified from "under development" to "development completed", and at the same time, the project flows to the next node ("data test" node) in the execution process.

[0076] Continuing to refer to FIG. 6, in the node attribute information, it is necessary to further edit the node authorization information to clarify the executor of the project task corresponding to the node. In this regard, the executor of the node project task can be selected in the role set pre-set in the "authorization operation role". For the task "Data development", the task executor can be selected as "Data engineer", that is, the "Data engineer" performs the work related to big data development. At the same time, the execution time length can be further determined for the project work of the node, for which "Yes" can be selected in "Whether scheduling information needs to be entered" and a specific time period can be entered as the execution time length of the "Data development" work. As shown in FIG. 7, in the scheduling page corresponding to the node, an execution time length of 2 days can be set for the data engineer, and the corresponding time period in the project deadline is from July 14, 2021 to July 15, 2021. At the same time, the executor can be further added for the current "Data development" node by clicking the "Add person in charge" control in the page. In addition, if no task performer is selected for the node, the "authorized operation role" of the node defaults to the project manager who creates the project, and at the same time, the node defaults to "not schedulable", i.e., there is no need to define the task execution time length.

[0077] Continuing to refer to FIG. 6, in the node attribute information, the node operation type can be further edited. In this regard, "Yes" or "No" can be selected in the option of "Can be deleted or not". It can be understood that the attribute of node operation type is for determining whether the node can be deleted or not. Therefore, the above two options indicate whether the target project does not need to execute the task corresponding to the node. For the node, the "associated role" can be further edited, and in this embodiment, the "associated role" can determine at least the deletion operation for the associated node. That is, when the role selected in the associated role is deleted from the platform or system, the node related to the selected role will also be deleted in the execution process corresponding to the project.

[0078] For example, if an associated role is set for a current process node, the current process node is deleted when the deletion of the associated role is detected. As shown in FIG. 8, from multiple types of roles provided by a preset set of associated roles, a "Data Engineer" can be selected as an associated role of a "Data Development" node, and when the role is deleted from the platform or system, the "Data Development" node (and multiple nodes involved in the subsequent big data tasks) corresponding to the role are also deleted together. Those skilled in the art should understand that the platform or system can further provide a restoration function of the associated role and the nodes associated therewith, and the embodiments of the present disclosure will not be described repeatedly here.

[0079] In addition, after editing a node to "deletable", only a user with the corresponding operation authority for the node can perform the delete operation. At the same time, the attribute of "deletable" can be edited for a node only if the related role of the node in the platform or system is deletable, and in this case, the delete operation is reversible, that is, even if a node is mistakenly deleted by a project manager or a user with the relevant authority, the node can be restored again by re-adding the related role corresponding to the node.

[0080] Still referring to FIG. 6, in the node attribute information, the preceding node indicator of the current node can be further edited. For example, a preceding node indicator can be added to "node arrival event", and an event corresponding to the preceding node can trigger an event corresponding to the current node. That is, the task of the current node can be triggered after the task corresponding to the preceding node is completed. For example, if "Data development" is taken as the current node, its preceding node indicator can be edited to an indicator corresponding to the "Data score estimation scheduling" node. That is, the execution process will not flow to the big data development task until the relevant worker performs score estimation scheduling for the big data task of the project. It can be understood that besides the function of adding a preceding node indicator, the platform or system further provides a deletion function for the preceding node indicator.

[0081] At the same time as editing the preceding node indicator, the event type and the flow status information of the current node when the execution process of the project reaches the current node can also be edited. As shown in Figure 6, after the execution of the score estimation scheduling event of the big data task is completed, the current "Data development" node can realize the promotion of the project according to the selected "event flow" in the event type. At the same time, based on the flow status information selected in "can flow to when the node reaches", the node can be adaptively displayed as "under development" on the display page of the platform or system.

[0082] Continuing to refer to FIG. 6, in the node attribute information, a node form of a current node can be further set. Wherein, the node form is for editing and configuring the deliverable list in the process node. Those skilled in the art should understand that multiple process nodes can configure deliverables according to the actual needs of a project, and the deliverables can be physical objects, such as the hardware of a certain product, or virtual objects, such as package files, program codes, and component data platforms. After editing the node form for a process node, attribute information of the deliverables can be further configured in the form configuration page. For example, if the deliverable corresponding to a process node is a front-end web page, the attribute information of the deliverable is a link corresponding to the web page. Those skilled in the art should understand that the attribute information of the deliverable corresponding to the node form of a process node can be configured according to the actual needs of a project, and the embodiment of the present disclosure is not specifically limited here.

[0083] In addition, when editing and arranging multiple node attribute information based on the node information editing page of a particular platform or system, the user can inquire about a detailed interpretation explanation of that attribute of the node attribute information by clicking on a question mark or other indicator following each attribute information.

[0084] In S350, after detecting that the task completion information corresponding to the current process node is filled, the node state of the current process node is changed.

[0085] Continuing to refer to FIG. 6, in the node attribute information, the node task or event of the current node can be further edited. For example, in the option of "node completion event", specific event information can be added as a mark that the current node is completed, and at the same time, after the added event information is completed and filled into the node attribute information, the status information of the process node also changes adaptively. It can be understood that this process is similar to the process of the node arrival event. For example, for a "Data development" node, its node completion information may be "project-related big data platform construction completed", and after an authorized user of the node practically considers the big data and confirms that the completion information is real and reliable, the execution process can be promoted from the current "Data development" node to the next node "Data testing", and at this time, the node status information of the "Data development" node changes from "under development" to "development completed".

[0086] In the technical solution of this embodiment, the node attribute information includes multiple-dimensional attribute information of the process node, and by editing and configuring this information on the node editing page, a high level of customization of the execution process of the project awaiting target configuration is realized in a visualization manner, and at the same time, a means for the user to modify the project execution process is provided.

[0087] 9 is a structural block diagram of an apparatus for generating a project flow according to an embodiment of the present disclosure, the apparatus can execute the method for generating a project flow according to any embodiment of the present disclosure, and includes functional modules and beneficial effects corresponding to the execution of the method. As shown in FIG. 9, the apparatus includes a process node determination module 410, a node dependency determination module 420, and an execution project flow information determination module 430.

[0088] The process node determination module 410 is configured to determine at least one process node corresponding to a target to-be-deployed project and determine node attribute information for the at least one process node.

[0089] The node dependency determination module 420 is configured to determine node dependencies for the at least one process node.

[0090] The execution project flow information determination module 430 is configured to determine execution project flow information corresponding to the target deployment project based on the node dependency relationship and the node attribute information.

[0091] Based on the above-mentioned technical solutions, the process node includes a master process node and a slave process node, and the process node determination module 410 includes an execution process determination unit, a process node determination unit and a node attribute information editing unit.

[0092] The execution process determination unit is configured to determine an execution process corresponding to the target to-be-deployed project, and determine at least one process node according to the execution process.

[0093] The process node determination unit is configured to determine at least one master process node according to the executing process, and for each master process node, add a slave process node corresponding to the current master process node when it is detected that the current master process node is triggered, and set the slave process node as the current master process node when it is detected that the slave process node is triggered.

[0094] The node attribute information editing unit is configured, when it is detected that a process node is triggered, to display a node information editing page corresponding to the process node, and edit the node attribute information of the process node in at least one editable item of the node information editing page.

[0095] For example, the node dependency determination module 420 is further configured to determine node dependencies of at least one process node according to an antecedent node indicator in the node attribute information, or determine sequence information of at least one process node according to an execution process of the target deployment awaiting project, and determine node dependencies of at least one process node according to the sequence information.

[0096] For example, the apparatus for generating a project flow further comprises a predecessor node indicator adjustment module.

[0097] The antecedent node adjustment module is configured to adjust an antecedent node indicator in the node attribute information according to the node dependency relationship, and update the node attribute information based on the adjusted antecedent node indicator.

[0098] Based on the above-mentioned technical solutions, the execution project flow information determination module 430 includes a process node execution order determination unit and an execution project flow information generation unit.

[0099] The process node execution order determination unit is configured to determine an execution order corresponding to at least one process node based on the node dependency relationships.

[0100] The execution project flow information generating unit is configured to generate execution project flow information of the target awaiting deployment project according to a node name in the node attribute information of at least one process node and the node dependency relationship.

[0101] Based on the above-mentioned technical proposals, the node attribute information includes at least one of a node indicator, a node name, a node cooperation user, a node authorization information, a node execution time length, a node operation type, a node transition type, a node restriction type, a preceding node indicator, and a node event.

[0102] Based on the above technical proposals, the apparatus for generating a project flow further includes a process node processing module.

[0103] The process node processing module is configured to delete the current process node and process nodes on which the current process node depends if it is detected that a node indicator of the current process node has changed and an upgrade operation has been performed on the current process node.

[0104] For example, the process node processing module is further configured to change a node state of the current process node when a node restriction type in the node attribute information of the current process node is a first type and processing of the current process node by a target operation user corresponding to the first type is detected.

[0105] For example, the process node processing module is further configured to update the node state of the current process node based on a trigger operation of the collaborating user on the current process node if the node restriction type in the node attribute information of the current process node is a second type and the node collaborating user includes a collaborating user.

[0106] For example, the process node processing module is further configured to, if an association role is set for a current process node, delete said current process node upon detecting deletion of said association role.

[0107] Based on the above technical proposals, the device for generating a project flow further includes a node state change module.

[0108] The node state change module is configured to change a node state of a current process node after detecting that the task completion information corresponding to the current process node is filled.

[0109] The technical solution of this embodiment determines at least one process node corresponding to a project waiting for target deployment, and determines node attribute information of the at least one process node, thereby clarifying the specific work content in multiple processes of the project, determining the node dependency of at least one process node, and determining execution project flow information corresponding to the target deployment project based on the node dependency and the node attribute information, providing a standard and concise means for project organization and planning, and improving the convenience of constructing the corresponding project process based on the actual project. At the same time, the obtained clarified and digitized project process facilitates workers' monitoring and management of the entire project and the work of multiple stages, which is beneficial to the promotion of high efficiency of the project.

[0110] The apparatus for generating a project flow according to an embodiment of the present disclosure is capable of executing the method for generating a project flow according to any embodiment of the present disclosure, and has functional modules and beneficial effects corresponding to the execution of the method.

[0111] The multiple units and modules provided in the above-mentioned device are merely divided according to functional logic, but are not limited to the above divisions as long as they can realize the corresponding functions, and it should be noted that the specific names of the multiple functional units are merely intended to make it easier to distinguish them from each other, and are not intended to limit the scope of protection of the embodiments of the present disclosure.

[0112] FIG. 10 is a structural schematic diagram of an electronic device according to an embodiment of the present disclosure. Hereinafter, reference will be made to FIG. 10, which shows a structural schematic diagram of an electronic device (for example, a terminal device or a server in FIG. 10) 500 suitable for implementing an embodiment of the present disclosure. The terminal device in the embodiment of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (for example, in-vehicle navigation terminals), and the like, and fixed terminals such as digital TVs, desktop computers, and the like. The electronic device shown in FIG. 10 is merely an example, and does not impose any limitations on the functions and scope of use of the embodiment of the present disclosure.

[0113] 10, the electronic device 500 may include a processing unit (e.g., a central processing unit, a graphic processor, etc.) 501, which can execute various appropriate operations and processes based on a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 506 into a random access memory (RAM) 503. The RAM 503 further stores various programs and data necessary for the operation of the electronic device 500. The processing unit 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An edit / output (I / O) interface 505 is also connected to the bus 504.

[0114] Typically, the I / O interface 505 can be connected to an editing device 506 including, for example, a touch panel, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc., an output device 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc., a storage device 506 including, for example, a magnetic tape, a hard disk, etc., and a communication device 509. The communication device 509 allows the electronic device 500 to communicate wirelessly or wired with other devices to exchange data. Although the electronic device 500 having various devices is shown in FIG. 10, it should be understood that it is not required to implement or include all the devices shown. Instead, more or less devices may be implemented or included.

[0115] According to an embodiment of the present disclosure, the process described with reference to the above flowcharts can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product including a computer program carried on a non-transitory computer-readable medium, the computer program including program code for performing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network by the communication device 509, or may be installed from the storage device 506, or may be installed from the ROM 502. When the computer program is executed by the processing device 501, it performs the above-mentioned functions defined in the method of the embodiment of the present disclosure.

[0116] The names of messages or information interacted between multiple devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0117] The electronic device according to the embodiment of the present disclosure belongs to the same disclosed concept as the method for generating a project flow according to the above embodiment, and the technical details not described in detail in this embodiment can be referred to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0118] An embodiment of the present disclosure provides a computer storage medium having a computer program stored thereon, which, when executed by a processor, implements the method for generating a project flow according to the embodiment above.

[0119] It should be noted that the above-mentioned computer-readable medium of the present disclosure may be a computer-readable signal medium, or a computer-readable storage medium, or any combination of the above. The computer-readable storage medium may be, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of the computer-readable storage medium may include, but are not limited to, an electrical connection having one or more leads, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program usable by or in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, in which computer-readable program code is carried. Such a propagated data signal may take a variety of forms, including, but not limited to, an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may transmit, propagate, or transmit a program for use in or in conjunction with an instruction execution system, apparatus, or device. The program code contained in the computer-readable medium may be transmitted over any suitable medium, including, but not limited to, electrical wire, optical cable, RF (radio frequency), and the like, or any suitable combination of the above.

[0120] In some embodiments, the clients and servers may communicate using any now known or later developed network protocol, such as HTTP (Hyper Text Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communications networks include a local area network ("LAN"), a wide area network ("WAN"), a network off a network (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), and any now known or later developed network.

[0121] The computer-readable medium may be included in the electronic device, or may exist separately and not attached to the electronic device.

[0122] The computer-readable medium carries one or more programs, and the one or more programs are executed by the electronic device, causing the electronic device to: Determine at least one process node corresponding to the target placement awaiting project; and determine node attribute information for the at least one process node; determining node dependencies for the at least one process node; Execution project flow information corresponding to the target deployment project is determined based on the node dependency relationships and the node attribute information.

[0123] Computer program code for carrying out the operations of the present disclosure can be written in one or more program design languages ​​or combinations thereof, including, but not limited to, object-oriented program design languages ​​such as Java, Smalltalk, C++, and further including conventional procedural program design languages ​​such as "C" or similar program design languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a single separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet Service Provider).

[0124] The flowcharts and block diagrams in the drawings illustrate possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams may represent a module, program segment, or part of code, which includes one or more executable instructions for implementing a certain logical function. It should be noted that in some alternative implementations, the functions depicted in the blocks may occur in a different order than the order depicted in the drawings. For example, two consecutively shown blocks may in fact be essentially executed in parallel depending on such functions, and they may be executed in the reverse order. It should be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented in a system based on dedicated hardware that performs a certain function or operation, or may be implemented in a combination of dedicated hardware and computer instructions.

[0125] The units described in the embodiments of the present disclosure may be implemented in a software manner or a hardware manner, and the names of the units may not necessarily be used to limit the units themselves, for example, the first acquiring unit may be described as "a unit for acquiring at least two Internet Protocol addresses".

[0126] The functionality described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard parts (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0127] In the context of the present invention, a machine-readable medium may be a tangible medium that can contain or store a program for use in or in conjunction with an instruction execution system, apparatus or device. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or any suitable combination of the above. More specific examples of machine-readable storage media include an electrical connection by one or more wires, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0128] According to one or more embodiments of the present disclosure, [Example 1] is determining at least one process node corresponding to a target awaiting placement project and determining node attribute information of the at least one process node; determining node dependencies of the at least one process node; determining execution project flow information corresponding to the target deployment project based on the node dependency relationships and the node attribute information.

[0129] According to one or more embodiments of the present disclosure, [Example 2] is For example, a method for generating a project flow is provided, further comprising: determining an execution process corresponding to the target to-be-deployed project; and determining at least one process node according to the execution process.

[0130] According to one or more embodiments of the present disclosure, [Example 3] is For example, the process nodes include a master process node and a slave process node; determining at least one master process node according to the executing process; The method for generating a project flow further includes, for each master process node, adding a slave process node corresponding to the current master process node when it is detected that the current master process node is triggered, and making the slave process node the current master process node when it is detected that the slave process node is triggered.

[0131] According to one or more embodiments of the present disclosure, [Example 4] is For example, a method for generating a project flow is provided, which further includes, when it is detected that a process node is triggered, displaying a node information edit page corresponding to the process node and editing node attribute information of the process node in at least one editable item of the node information edit page.

[0132] According to one or more embodiments of the present disclosure, [Example 5] is For example, determining a node dependency relationship of at least one process node according to a predecessor node indicator in the node attribute information; or The method for generating a project flow further includes determining sequence information of at least one process node according to an execution process of the target deployment awaiting project, and determining node dependencies of the at least one process node according to the sequence information.

[0133] According to one or more embodiments of the present disclosure, [Example 6] is For example, the present invention provides a method for generating a project flow, which further includes adjusting a preceding node indicator in the node attribute information according to the node dependency relationship, and updating the node attribute information based on the adjusted preceding node indicator.

[0134] According to one or more embodiments of the present disclosure, [Example 7] is determining an execution order corresponding to at least one process node based on, for example, the node dependencies; generating execution project flow information of the target awaiting deployment project according to a node name in node attribute information of at least one process node and the node dependency relationship.

[0135] According to one or more embodiments of the present disclosure, [Example 8] is For example, the method for generating a project flow further includes the node attribute information including at least one of a node indicator, a node name, a node collaborating user, a node authorization information, a node execution time length, a node operation type, a node transfer type, a node restriction type, a previous node indicator, and a node event.

[0136] According to one or more embodiments of the present disclosure, [Example 9] is For example, a method for generating a project flow further includes deleting the current process node and process nodes on which the current process node depends if it is detected that a node indicator of the current process node has changed and an upgrade operation has been performed on the current process node.

[0137] According to one or more embodiments of the present disclosure, [Example 10] is For example, the method for generating a project flow further includes changing a node state of the current process node when a node restriction type in node attribute information of a current process node is a first type and processing of the current process node by a target operation user corresponding to the first type is detected.

[0138] According to one or more embodiments of the present disclosure, [Example 11] is For example, if the node restriction type in the node attribute information of the current process node is a second type and the node collaborating users include a collaborating user, the method for generating a project flow further includes updating a node state of the current process node based on a trigger operation of the collaborating user on the current process node.

[0139] According to one or more embodiments of the present disclosure, [Example 12] is For example, if an associated role is set for a current process node, the method for generating a project flow further includes deleting the current process node when deletion of the associated role is detected.

[0140] According to one or more embodiments of the present disclosure, [Example 13] is For example, a method for generating a project flow further includes changing a node state of a current process node after detecting that task completion information corresponding to the current process node has been filled.

[0141] According to one or more embodiments of the present disclosure, [Example 14] is a process node determination module configured to determine at least one process node corresponding to a target awaiting placement project and to determine node attribute information of the at least one process node; a node dependency determination module configured to determine node dependencies for the at least one process node; and an execution project flow information determining module configured to determine execution project flow information corresponding to the target deployment project based on the node dependency relationship and the node attribute information.

[0142] Also, although certain operations have been described in a particular order, it should not be understood that these operations must be performed in the particular order shown, or in a forward order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, the above discussion includes certain specific implementation details, which should not be understood as limiting the scope of the disclosure. Any features that are described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may be implemented in multiple embodiments alone or in any suitable subcombination.

Claims

1. determining at least one process node corresponding to a target to-be-deployed project and determining node attribute information for the at least one process node; determining node dependencies for the at least one process node; determining execution project flow information corresponding to the target deployment project based on the node dependency relationship and the node attribute information; How to generate a project flow.

2. Determining at least one process node corresponding to a target pending project, as described above, comprises: determining an execution process corresponding to the target to-be-deployed project; and determining at least one process node according to the execution process. The method of claim 1.

3. The process nodes include a master process node and a slave process node, and determining at least one process node according to the execution process includes: determining at least one master process node in response to the executing process; for each master process node, in response to detecting that a current master process node has been triggered, adding a slave process node corresponding to the current master process node, and in response to detecting that the slave process node has been triggered, making the slave process node the current master process node; The method of claim 2.

4. Determining node attribute information of the at least one process node includes: In response to detecting that a process node is triggered, displaying a node information edit page corresponding to the process node and editing node attribute information of the corresponding process node in at least one editable item of the node information edit page. The method of claim 1.

5. Determining node dependencies of the at least one process node, determining node dependencies of the at least one process node in response to a predecessor node indicator in the node attribute information; or determining sequence information of the at least one process node according to an execution process of the target to-be-deployed project; and determining node dependencies of the at least one process node according to the sequence information. The method of claim 1.

6. After determining sequence information of the at least one process node according to the execution process of the target to-be-deployed project and determining node dependencies of the at least one process node according to the sequence information, The method further includes adjusting a preceding node indicator in the node attribute information according to the node dependency relationship, and updating the node attribute information based on the adjusted preceding node indicator. The method according to claim 5.

7. Determining execution project flow information corresponding to the target placement project based on the node dependency relationship and the node attribute information, determining an execution order corresponding to the at least one process node based on the node dependencies; generating execution project flow information of the target awaiting deployment project according to a node name in the node attribute information of the at least one process node and the node dependency relationship; The method of claim 1.

8. The node attribute information includes at least one of a node indicator, a node name, a node cooperation user, a node authorization information, a node execution time length, a node operation type, a node transfer type, a node restriction type, a previous node indicator, and a node event. The method according to any one of claims 1 to 4.

9. and in response to detecting that a node indicator of a current process node has changed and that an upgrade operation has been performed on the current process node, deleting the current process node and process nodes on which the current process node depends. The method according to claim 8.

10. The method further includes determining that a node restriction type in the node attribute information of the current process node is a first type, and in response to detecting a process of the current process node by a target operation user corresponding to the first type, changing a node state of the current process node. The method according to claim 8.

11. The method further includes: determining that a node restriction type in the node attribute information of the current process node is a second type, and in response to the node collaboration users including a collaboration user, updating a node state of the current process node based on a trigger operation of the collaboration user on the current process node. The method according to claim 8.

12. setting an association role for the current process node, and deleting the current process node in response to detecting a deletion of the association role. The method according to claim 8.

13. After detecting that the task completion information corresponding to the current process node is filled, changing a node state of the current process node. The method of claim 1.

14. a process node determination module configured to determine at least one process node corresponding to a target to-be-deployed project and determine node attribute information of the at least one process node; a node dependency determination module configured to determine node dependencies for the at least one process node; and an execution project flow information determination module configured to determine execution project flow information corresponding to the target deployment project based on the node dependency relationship and the node attribute information. A device for generating project flows.

15. one or more processors; a storage device configured to store one or more programs; The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method for generating a project flow according to any one of claims 1 to 13. electronic equipment.

16. A storage medium containing computer-executable instructions, comprising: The computer executable instructions, when executed by a processor of a computer, are configured to perform the method for generating a project flow according to any one of claims 1 to 13. storage medium.

Citation Information

Patent Citations

  • Operation progress management system and program storage medium

    JP1999066159A

  • Project management device

    JP2008146182A

  • Project planning device

    JP2011095918A

  • Design support device, method and program

    JP2014021823A

  • Project management system, control method and program

    JP2020181335A