Project process management method and device, medium, equipment and computer program product

Abstract

The invention discloses a project process management method and device, a medium, equipment and a computer program product, and relates to the technical field of computers. The method comprises the steps that in response to a first configuration instruction, deliverable sub-attributes are added to review element attributes in a first data model, and the first data model comprises node attributes in a process template; in response to a second configuration instruction, associated deliverable attributes are added to a second data model, and the second data model is used for representing attributes of a target process created based on the process template; and according to the review element attribute, the deliverable sub-attribute and the associated deliverable attribute, associating deliverable for the review element in the target process. According to the method provided by the invention, the review element and the deliverable are associated in advance on the configuration side template of the project process, the association relationship can be added and deleted on the instance side, and the delivery state can be checked, so that the review efficiency in the project is improved, the deliverable can be tracked in the project conveniently, and the management flexibility is enhanced.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of computer, in particular, to a project process management method, device, medium, equipment and computer program product. BACKGROUND

[0002] In an IPD (Integrated Product Development) solution, management capabilities such as step-by-step coverage, disassembly, and aggregation of projects by work items are supported. A project is composed of multiple work items, and different work items are assigned different business semantics in different scenarios, such as WBS (Work Breakdown Structure) sub-processes, deliverables, and review elements.

[0003] The IPD solution can include multiple decision points. When a decision point is reviewed and decided, each review element that affects the decision needs to be reviewed, and each review element needs corresponding materials and data for decision support, and these materials or data are some deliverables under the project. A large project is usually disassembled into hundreds or thousands of work items. How to conveniently view the deliverables corresponding to a review element is a problem to be solved. SUMMARY

[0004] This summary is provided to introduce a selection of concepts, which will be described with greater specificity below in the detailed description section. This summary is not intended to identify key or essential features of the claimed technology, nor is it intended to limit the scope of the claimed technology.

[0005] In a first aspect, the present disclosure provides a project process management method, the method comprising: in response to a first configuration instruction, adding a deliverable sub-attribute to a review element attribute in a first data model, wherein the first data model contains node attributes in a process template; in response to a second configuration instruction, adding an associated deliverable attribute to a second data model, wherein the second data model is used to represent attributes of a target process created based on the process template; associating deliverables for a review element in the target process according to the review element attribute, the deliverable sub-attribute, and the associated deliverable attribute.

[0006] In a second aspect, the present disclosure provides a project process management device, the device comprising: a first processing module configured to add a deliverable sub-attribute to a review element attribute in a first data model in response to a first configuration instruction, wherein the first data model contains node attributes in a process template; a second processing module, configured to add associated deliverable attributes to a second data model in response to a second configuration instruction, wherein the second data model is used to represent attributes of a target process created based on the process template; The association module is configured to associate deliverables with the review elements in the target process according to the review element attributes, the deliverable sub-attributes, and the associated deliverable attributes.

[0007] In a third aspect, the present disclosure provides a computer-readable medium having a computer program stored thereon, which implements the steps of the method described in the first aspect when executed by a processing device.

[0008] In a fourth aspect, the present disclosure provides an electronic device, comprising: a storage device having a computer program stored thereon; A processing device is used to execute the computer program in the storage device to implement the steps of the method described in the first aspect.

[0009] In a fifth aspect, the present disclosure provides a computer program product, comprising a computer program, which implements the steps of the method described in the first aspect when executed by a processor.

[0010] Through the above technical solution, it is possible to pre-configure deliverables for the review elements in the process when configuring the process template, so that when reviewing the review nodes in the process instance generated based on the process template, the deliverables can be quickly located without the review user having to query and filter from a large number of deliverables, thereby improving the review efficiency and accuracy of the review elements. In addition, the review elements in a specific target process can be updated separately, so that the matching degree between the target process and the actual application scenario can be improved on the basis of the general template configuration, providing more comprehensive and accurate associated deliverables for the review of the review elements, and further improving the efficiency of reviewing the review elements. The method provided by the present disclosure improves the review efficiency in the project, facilitates the tracking of deliverables in the project, and enhances management flexibility by pre-associating the review elements with the deliverables in the template on the configuration side of the project process, and can add and delete the association relationship and view the delivery status on the instance side.

[0011] Other features and advantages of the present disclosure will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The above and other features, advantages and aspects of the various embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that the originals and elements are not necessarily drawn to scale. In the drawings: Figure 1 It is a flowchart of a project process management method provided according to an embodiment of the present disclosure.

[0013] Figure 2 This is an interface diagram for updating deliverables associated with review elements provided according to an embodiment of the present disclosure.

[0014] Figure 3 It is a schematic diagram of a first metadata table and a second metadata table for storing a first data model provided according to an embodiment of the present disclosure.

[0015] Figure 4 It is an architectural diagram of a project process management method provided according to an embodiment of the present disclosure.

[0016] Figure 5 A block diagram of a project process management device provided according to an embodiment of the present disclosure.

[0017] Figure 6 A schematic structural diagram of an electronic device suitable for implementing the embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0018] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0019] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0020] As used herein, the term "including" and its variations are open-ended, i.e., "including but not limited to." The term "based on" means "based, at least in part, on." The term "one embodiment" means "at least one embodiment," the term "another embodiment" means "at least one additional embodiment," and the term "some embodiments" means "at least some embodiments." Other terms are defined in the following description.

[0021] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0022] It should be noted that the modifications of "one" and "multiple" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, they should be understood as "one or more".

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

[0024] It is understandable that before using the technical solutions disclosed in the various embodiments of this disclosure, the type, scope of use, usage scenarios, etc. of the personal information involved in this disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0025] For example, in response to a user's active request, a prompt message is sent to the user to clearly inform the user that the operation requested will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the electronic device, application, server, storage medium, or other software or hardware that performs the operations of the disclosed technical solution based on the prompt message.

[0026] As an optional but non-limiting implementation, in response to receiving a user's active request, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. Furthermore, the pop-up window may also contain a selection control for the user to select "agree" or "disagree" to provide personal information to the electronic device.

[0027] It is understandable that the above notification and user authorization process are merely illustrative and do not limit the implementation of the present disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0028] At the same time, it is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.

[0029] Figure 1 As shown, it is a flowchart of a project process management method provided according to an embodiment of the present disclosure, as shown in Figure 1 As shown, the method may include: In step 11, in response to the first configuration instruction, a deliverable sub-attribute is added to the review element attribute in the first data model, wherein the first data model includes the node attribute in the process template.

[0030] Integrated Product Development IPD is a set of models, concepts and methods for product development. A standard IPD product development process is clearly divided into six stages: concept, planning, development, verification, release, and life cycle, and there are clearly defined decision review points in the process. Each decision review point contains its corresponding review element attributes, which are used to represent the indicators for review at the decision review point. For example, the review element is used to represent the reviewer's judgment in the decision review point (DCP) on whether the content to be reviewed passes the dimensions and standards of concern, such as stability, scalability, etc. The multiple nodes of the process template include at least one review node, and the review node includes at least one review element, which can be configured in the review node based on the actual application scenario. The process template in the present disclosure can be a process template pre-configured based on the IPD model. Based on the process template, multiple processes can be generated to achieve monitoring of processes in actual scenarios.

[0031] The following is an example of the software development process. The software development process may include a technical solution confirmation node A, a technical solution sorting node B, a technical solution review node C, a back-end development node D, etc. Each node can produce results, such as documents, design drafts, and the results of the process execution. The output results can be used as the deliverables of the node. For example, the deliverable of the technical solution confirmation node can be document F1, which is used to represent the confirmed technical solution. The technical solution sorting node can be document F2, etc. The corresponding deliverables can be configured by configuring the node attributes when configuring the process template, so as to obtain the first data model. Among them, the technical solution review can be used as a review node. When reviewing the technical solution in this node, it is necessary to pay attention to multiple review factors, such as the stability of the technical solution, the scalability of the technical solution, etc.

[0032] To improve the processing efficiency and accuracy of review nodes, a common deliverable sub-attribute can be pre-configured for the review element attributes within the node attributes of the process template during process template configuration. For example, by analyzing the relationships between nodes within the process template, the deliverables required for reviewing the review element of the review node are determined. Based on these deliverables, the attribute value of the deliverable sub-attribute of the review element attribute is determined. The attribute value of this deliverable sub-attribute can be a deliverable produced by other nodes or other processes. Therefore, in this step, the deliverables configured for the review element during process template configuration can be obtained through the first configuration instruction and recorded based on the deliverable sub-attribute.

[0033] In some possible embodiments, the first configuration instruction may be generated in the following manner: Display the review element attributes of the target node to be configured. The review element can be displayed based on the configuration information of the process template.

[0034] Afterwards, in response to receiving a configuration operation on the review element attribute, candidate configuration deliverables corresponding to the review element attribute are obtained, wherein the candidate configuration deliverables include the output deliverables configured by the predecessor node before the target node in the process template, and the output deliverables configured in the process template associated with the predecessor node.

[0035] Taking the process template corresponding to the process described above as an example, if the technical solution review node is used as the target node and the stability review element in the target node is configured, the candidate configuration deliverables corresponding to the review element attributes can be obtained based on the configuration information of the process template. For example, the nodes in the process template may also be associated with sub-processes. For example, in the above example, the technical solution combing node can be associated with a combing sub-process. For example, the combing sub-process associated with the technical solution combing node can include nodes b1, b2, and b3. In this embodiment, the deliverables of the node before the target review node in the process template and the deliverables of each node in the sub-process associated with the node before the target review node can be used as candidate configuration deliverables. For example, the candidate configuration deliverables corresponding to the review element in the technical solution review node can be the deliverables of nodes A, B, and nodes b1, b2, and b3.

[0036] After displaying the candidate configuration deliverables, in response to receiving a selection operation for the candidate configuration deliverable, generating the first configuration instruction based on the path information and deliverable information of the process template to which the selected candidate configuration deliverable belongs, the first configuration instruction including the path information and deliverable information.

[0037] As an example, if the candidate configuration deliverable is a deliverable in the process template, the path information may include the template identifier of the process template to which the deliverable belongs. If the candidate configuration deliverable is a deliverable in the associated process template, the path information may include the associated node of the process template to which the deliverable belongs in the target process template and the template identifier of the associated process template. The deliverable information may include the deliverable type and the attribute information corresponding to the deliverable type. For example, the deliverable type may include a field type and an instance type. If the deliverable type is a field type, its attribute information may include the field identifier field_key of the deliverable. If the deliverable type is an instance type, the attribute information may include the deliverable resource instance identifier resource_id and the node identifier state_key of the node to which the deliverable belongs, as well as the task identifier task_key of the task to which the deliverable belongs. The above examples can be configured based on actual application scenarios.

[0038] For example, a node in the first data model may have hundreds of attributes and the number will continue to grow. These attributes include the node name, deliverables required to be submitted on the node, review elements on the node, etc. Each attribute can also contain sub-attributes, as shown in Table 1 below:

[0039] Table 1 In this step, based on the first data model, a deliverable sub-attribute may be added under the review element attribute to record the deliverables required for reviewing the corresponding review element.

[0040] In step 12, in response to the second configuration instruction, associated deliverable attributes are added to the second data model, wherein the second data model is used to represent attributes of the target process created based on the process template.

[0041] Among them, when generating different processes based on the process template to cope with various scenarios, the deliverables required in different scenarios may also be slightly different. Therefore, in this step, when generating the target process based on the process template, the deliverables of the nodes in the target process can be modified to add associated deliverable attributes.

[0042] As an example, each process can be displayed in the interface, and a configuration button can be associated with the process. If the user wants to configure one of the processes, the configuration button associated with the process can be selected to trigger the configuration operation and display the target process, such as displaying each node in the target process. Furthermore, the review nodes in the target process can also be highlighted so that the user can quickly understand the review nodes that can be configured. The highlighting method can be a highlight display or a hover mark display, etc., which can be set based on the actual application scenario, and the present disclosure does not limit this.

[0043] Afterwards, when the user selects a target review element for configuration, in response to receiving a configuration operation for the target review element in the target review node, the first deliverable and the second deliverable of the target review element are determined, wherein the first deliverable is determined based on the first data model, and the second deliverable is the deliverable in the sub-process associated with the target process and the node in the target process. For example, the first deliverable can be displayed in the interface, and a delete control B1 can be displayed for each first deliverable, and an add control B2 can be displayed at the same time, such as Figure 2As shown, the review process of review element 1 can be displayed, which can include nodes 1, 2, and 3, and the first deliverables X1, X2, and X3 of review element 1 can be displayed. If the user believes that one or more of the deliverables are not necessary for the review of the target review element, they can delete them through the delete control associated with the corresponding first deliverable. If the user believes that other deliverables are required for the review of the target review element, they can select the add control to determine the deliverables to be added from the second deliverables. Accordingly, after the user configuration, the generation of a second configuration instruction can be triggered. The second configuration instruction can include the process identifier and association type of the target process, and can also include the path information or deliverable identification code of the associated deliverable.

[0044] Through this step, an attribute may be added to the second data model, where the attribute is an associated deliverable attribute, and the attribute value of the associated deliverable attribute is determined based on the information in the second configuration instruction.

[0045] In step 13, deliverables are associated with the review elements in the target process based on the review element attributes, deliverable sub-attributes, and associated deliverable attributes.

[0046] Among them, based on the review element attributes, the review element to be displayed can be determined, based on the deliverable sub-attribute, the deliverable configured for the review element when the process template is configured can be determined, and based on the associated deliverable attribute, the associated deliverable independently configured in the target process can be determined. In this step, the attribute values ​​of the above attributes can be combined to determine all the deliverables corresponding to the review element to display to the user, providing data reference for the user to review the review element.

[0047] Therefore, through the above technical solution, it is possible to pre-configure deliverables for the review elements in the process when configuring the process template, so that when reviewing the review node in the process instance generated based on the process template, the deliverables can be quickly located without the review user having to query and filter from a large number of deliverables, thereby improving the review efficiency and accuracy of the review elements. In addition, the review elements in the specific target process can be updated separately, so that the matching degree between the target process and the actual application scenario can be improved on the basis of the general template configuration, providing more comprehensive and accurate associated deliverables for the review of the review elements, and further improving the efficiency of reviewing the review elements. The method provided by the present disclosure improves the review efficiency in the project, facilitates the tracking of deliverables in the project, and enhances management flexibility by pre-associating the review elements with the deliverables in the template on the configuration side of the project process, and can add and delete the association relationship and view the delivery status on the instance side.

[0048] In some possible embodiments, in response to the first configuration instruction, adding a deliverable sub-attribute to the review element attribute in the first data model may include: In response to the first configuration instruction, an identification code of a target review element in the first configuration instruction is determined.

[0049] Among them, the target review element is a configured review element, and the identification code of the target review element is used to uniquely identify the review element. The identification code can be a UUID (Universally Unique Identifier), for example, it can be determined by the process template identifier, node identifier, sub-work item identifier and random code, and the identification code is obtained by splicing the above identifiers, and the target review element can be quickly located through the above identifiers in the identification code.

[0050] Afterwards, the path information and deliverable information of the process template to which the deliverable in the first configuration instruction belongs are obtained, wherein the path information and deliverable information can be obtained by parsing the first configuration instruction.

[0051] Furthermore, the path information and the deliverable information are used as attribute values ​​of the deliverable sub-attribute, and the deliverable sub-attribute and the attribute value are added to the first data model based on the identification code, and the deliverable sub-attribute is associated with the review factor attribute.

[0052] As an example, you can add deliverable sub-attributes to the sub-attributes of the review factor attributes. For example, you can create multiple wide tables to store all the attributes of this node, and each column in the table corresponds to a sub-attribute.

[0053] As another example, Figure 3 As shown, the first data model is stored through the first metadata table and the second metadata table. The first metadata table contains the node identifier and basic information of the node. The basic information may include the creation time, update time, deletion time and version number of the node. The second metadata table contains the node attributes of the node, wherein the default node attributes may be used as columns of the second metadata table, such as creation time, update time, deletion time, identification code, parent node identification code, sub-attribute, attribute value and version number. The sub-attribute is used to indicate which attribute of a node a row of data belongs to. The attribute name may be resource_key in Table 1, and the attribute value is used to indicate the value of the sub-attribute. The first metadata table and the second metadata table are associated through the node identifier uuid in the first metadata table and the parent node identification code parent_uuid in the second metadata table.

[0054] In this embodiment, a deliverable sub-attribute can be added, that is, LinkDelivery can be added to resource_key, and the attribute value can be the path information and deliverable information. For example, a row of data can be added to the second metadata table, where the sub-attribute is LinkDelivery and the attribute value is the path information and deliverable information. The values ​​of other attributes in this row of data, such as creation time, version number, etc., can be determined based on the general methods in related technologies, and this disclosure does not limit this.

[0055] Therefore, by storing the data in the first data model in the metadata table, unified management of the first data model can be achieved, while reducing the modification and intrusion of the existing first data model by the newly added deliverable sub-attributes, thereby facilitating the maintenance and management of the first data model.

[0056] In some possible embodiments, in response to the second configuration instruction, adding an associated deliverable attribute to the second data model includes: In response to the second configuration instruction, determining whether the second configuration instruction satisfies operation permissions, wherein the operation permissions include user permissions of the operation user corresponding to the second configuration instruction and / or operation type permissions indicated by the second configuration instruction; If it is determined that the second configuration instruction satisfies the operation permission, an associated deliverable attribute is added to the second data model.

[0057] As an example, the operation authority of the review element can be pre-configured. Then, when configuring the review element in the target process, it can be determined based on the operation authority whether the second configuration instruction triggered by the configuration operation on the review element meets the operation authority.

[0058] As an example, the user permissions of the operating users who can operate the review elements in the target process can be pre-set. When such operating users add or delete review elements, it can be determined that the second configuration instruction triggered by the operation of the operating user meets the operating permissions.

[0059] As an example, the operation type permission can be used to indicate the update type of the deliverables associated with the review element, which can include the add permission and the delete permission. The add permission is used to constrain the addition of new deliverables to the review element, and the delete permission is used to constrain the deletion of deliverables already associated with the review element. In order to ensure the review accuracy of the review elements, the operation permission of one or more review elements can be set to the add permission, which means that the user can only add other deliverables to the review element in the future, but cannot delete the deliverables configured in the template. In this scenario, if the second configuration instruction is an instruction to add deliverables, it can be determined that it meets the operation permission. For another example, in order to reduce data redundancy in the review process of the review elements, the operation permission of one or more review elements can be set to the delete permission, which means that the user can only delete one or more deliverables configured in the template in the future, but cannot add other deliverables to the review element. In this scenario, if the second configuration instruction is an instruction to delete deliverables, it can be determined that it meets the operation permission. For example, the operating permissions of one or more review elements can be set to include adding permissions and deleting permissions. The user can subsequently add other deliverables to the review element, or delete the deliverables configured in the template. In this scenario, if the second configuration instruction is an instruction to delete the deliverable, or an instruction to add a deliverable, or the second configuration instruction includes both added deliverables and deleted deliverables, it can be determined that the operating permissions are met.

[0060] Among them, whether to display the add control and delete control can be determined based on the pre-configured operation permissions for the review elements, so as to further facilitate the user's accurate operation and ensure the accuracy and effectiveness of the second configuration instruction.

[0061] Therefore, through the above technical solution, before adjusting the deliverables associated with the review elements in the target process, it is possible to determine whether the second configuration instruction meets the operation authority, thereby ensuring the effectiveness of the adjustment of the deliverables associated with the review elements in the target process, and thus ensuring the accuracy of updating the second data model to provide support for the subsequent review process.

[0062] In some possible embodiments, in response to the second configuration instruction, adding an associated deliverable attribute to the second data model includes: In response to the second configuration instruction, a process identifier for adding the associated deliverable attribute is determined.

[0063] After processes are generated based on a process template, each process will have a corresponding identifier that uniquely identifies it, known as a process ID. Accordingly, when a user adjusts a deliverable associated with a review element in a process, the process ID can be recorded and added to the second configuration instruction. In this step, the second configuration instruction can be parsed to obtain the process ID contained therein, and then, based on the process ID, the process to which the associated deliverable attributes need to be added can be determined.

[0064] If the association type of the associated deliverable in the second configuration instruction is add, path information of the process to which the associated deliverable belongs is obtained, and a deliverable identification code of the associated deliverable is generated, and the attribute value of the associated deliverable attribute includes the path information and the deliverable identification code.

[0065] For example Figure 2 As shown in , when the configuration user clicks the add control B2, the operation of adding a deliverable can be triggered. Accordingly, the candidate deliverables of the review element can be displayed, and the user can select from the candidate deliverables to obtain the deliverables to be added. Among them, after the process is created, the process can be directly located based on the process identifier of the process. In this embodiment, the path information of the added associated deliverable can be the process identifier of the process to which the deliverable belongs. The deliverable identification code can be a unique identifier generated by splicing the path information and the deliverable information, and the identifier can be represented by a UUID. The content of the deliverable information is the same as the deliverable information in the first data model described above, and will not be repeated here.

[0066] Based on the path information and the deliverable identification code, a deliverable under the process indicated by the process identifier can be directly located, thereby improving the rapid query of deliverables. For example, relevant information about the deliverable to be added can also be added to the attribute value based on the actual application scenario, which is not limited by this disclosure.

[0067] Accordingly, the corresponding attribute value can be determined based on the path information and the deliverable information. The following is an exemplary representation of the attribute value added_confs of the deliverable 4234 added in process A: "added_confs": [ { "wbs_paths": [ { "template_uuid": "root_template", "state_key": "node_225" }, { "template_uuid": "template_2", "state_key": "" } ], "uuid": "instance_add_4234", "work_item_id":1234, "delivery_instance_id": 4234 } ] wbs_paths represents path information. In the example above, deliverable 4234 from process ID 1234 is associated with process A. The wbs path for process ID 1234 is from node node_225 in the root template root_template to the associated sub-process template template_2. This value's unique UUID, instance_add_4234, allows for quick location of the deliverable.

[0068] If the association type of the associated deliverable is deletion, the deliverable identification code of the associated deliverable is used as the attribute value of the associated deliverable attribute.

[0069] For example Figure 2 As shown in the example, if a user clicks the delete control B1 associated with deliverable X1, the associated deliverable F1 is deleted, and the deliverable is considered the deliverable to be deleted. After creating the target process, the identifiers of the deliverables associated with each review element in the target process can be determined. The deliverable identification code uniquely identifies a deliverable. When deleting a deliverable, the deliverable can be directly identified based on the deliverable identification code. The corresponding attribute value, deleted_confs, is shown below: "deleted_confs": [ { "uuid":"root_template:state_0:task_1:123", "deleted_at":"2025-06-19 16:20:57.002", "deleted_by": "user2" } ] } Among them, root_template:state_0:task_1:123 is the deliverable identification code used to represent the deliverable to be deleted. For example, this attribute value can also include the deletion time and the deletion operator to record the user's operation and provide data support for subsequent operation rollback and monitoring.

[0070] Afterwards, the associated deliverable attribute and the attribute value may be added to the second data model based on the process identifier.

[0071] As an example, the second data model can be stored through a third metadata table, and the third metadata table contains attribute information in the process, wherein the attribute information can include default attributes and configuration attributes. The default attributes can be used as columns of the third metadata table, such as creation time, update time, deletion time, and process ID. The configuration attributes include attribute domains and attribute values. The attribute domain can be used to indicate which attribute a row of data belongs to on a certain instance, and its value can be a configured attribute, such as a process name, process ID, etc. The attribute value is used to indicate the value under the value of the attribute domain. If the value of the attribute domain in a row of records is "process name", the attribute value represents the value of the process name.

[0072] In this embodiment, adding a related deliverable attribute to the second data model may be adding a related deliverable attribute LinkDeliveryConfOnInstanceSide in the attribute field, and the attribute value in this row of records is the attribute value of the related deliverable attribute.

[0073] As another example, multiple wide tables can be created to store all attributes of a node, with each column in the table corresponding to one attribute.

[0074] Therefore, the metadata table can be used to store updated information on deliverables associated with the process, which facilitates the maintenance and management of deliverables associated with the process and provides effective data support for the subsequent display of deliverables associated with the review elements.

[0075] As an example, for added or deleted deliverables, a row of records may be directly generated based on the associated deliverable attributes and their attribute values ​​and added to the second data model.

[0076] As another example, adding the associated deliverable attribute and the attribute value to the second data model based on the process identifier may include: Determine whether the process identifier is associated with the associated deliverable attribute in the second data model.

[0077] Specifically, for the same process, multiple users may adjust the deliverables, or a single user may adjust the deliverables of the same process multiple times. To ensure the validity of the attribute values ​​of the deliverable attributes, in this embodiment, all adjustment operations on the deliverables of the same process may be combined into the same attribute value for recording.

[0078] For example, when user U1 first updates a deliverable in process A and adds deliverable 4234, a query can be performed based on the process ID of process A to determine whether the associated deliverable attribute is associated in the second data model. If it is determined that the associated deliverable attribute is not associated in the second data model, a row of records can be generated based on the associated deliverable attribute and its aforementioned attribute values ​​and added to the second data model. This row of records is stored in association with the process ID of process A. When user U2 deletes deliverable root_template:state_0:task_1:123 from process A, a query can be performed based on the process ID of process A to determine whether the associated deliverable attribute is associated in the second data model. In this scenario, the associated deliverable attribute is associated in the second data model.

[0079] Correspondingly, if the process identifier is associated with the associated deliverable attribute, the attribute value is merged with the attribute value of the associated deliverable attribute in the second data model to obtain a new attribute value.

[0080] That is, in this embodiment, the added_confs and deleted_confs can be merged to obtain a new attribute value. It should be noted that if there are new deliverables to be deleted later, their deliverable identification codes can be added to deleted_confs for merging. If there are new deliverables to be added later, their corresponding path information and deliverable information can be added to added_confs for merging.

[0081] Afterwards, the associated deliverable attribute and the new attribute value are added to the second data model based on the process identifier.

[0082] For example, the attribute values ​​of the added deliverables and the deleted deliverables can be merged and stored in a row of records in the second data model. In this way, the accuracy and effectiveness of the data storage in the second data model can be guaranteed, so that when the deliverables are subsequently associated with the review elements, all updates can be obtained by obtaining a row of records, thereby improving the efficiency of associating deliverables.

[0083] As an example, Figure 4As shown, an architecture diagram of a project process management method provided based on an embodiment of the present disclosure is shown, in which a business function interface can be provided externally at a business layer to support configuration of a process template and consumption of configuration data of the process template in a target process, such as deletion of associated deliverables in the target process and addition of candidate deliverables. The data in the first data model and the second data model can be stored in a database, such as the first metadata table, the second metadata table, and the third metadata table can be stored in a MySQL database. Accordingly, to improve the access efficiency of data, the associated deliverables corresponding to the update operation in the target process can be stored in a cache-type database, such as a Redis database, to facilitate quick access of the associated deliverables. The deliverables can be obtained through a service of the associated deliverables, such as the service can include a method for obtaining deliverables in the process template, a method for obtaining associated deliverables of the target process update. As described above, the deliverables can include field-type deliverables and instance-type deliverables, and the service can further include a method for obtaining field-type deliverables and a method for obtaining instance-type deliverables. To improve the availability of the obtained deliverables, other information associated with the deliverables can also be obtained, and the service can further include a method for obtaining additional information of field-type deliverables and a method for obtaining additional information of instance-type deliverables.

[0084] Through the above scheme, the configuration of the associated deliverables in the process template can be performed, so that the review elements in the process generated based on the process template can include the general associated deliverables, and the target process can be updated only for the deliverables associated with the target process to perform individualized configuration for the target process. Through the above configuration, in the review process of the review elements in the target process, it can be convenient to view whether the deliverables corresponding to the review elements at different positions in the project are completed or submitted based on the first data model and the second data model.

[0085] In some possible embodiments, according to the review element attribute, the deliverable sub-attribute, and the associated deliverable attribute, the associated deliverables for the review elements in the target process can include: Based on the identification of the review element of the target process, a first attribute value of the deliverable sub-attribute corresponding to the review element is determined.

[0086] Wherein, after the target process configuration is completed, the process can be transferred based on the target process. Accordingly, when transferred to a review node, the review elements of the review node are displayed, and the user can trigger the review operation of the review elements by clicking the review control. As an example, based on the permission of the currently logged-in user, the review elements for which the user has the review permission are displayed.

[0087] For example, the first data model may be queried based on the identifier of the review element, and the value of the deliverable sub-attribute in the queried data is used as the first attribute value, which records the deliverable associated with the review element when the process template is configured.

[0088] Based on the process identifier of the target process, a second attribute value of the associated deliverable attribute corresponding to the review element is determined.

[0089] For example, the second data model may be queried based on the process identifier of the target process, and the value of the associated deliverable attribute in the queried data is used as the second attribute value, which records the operations of adding and / or deleting deliverables for the target process.

[0090] Thereafter, a target deliverable associated with the review element is determined based on the first attribute value and the second attribute value.

[0091] Thus, the target deliverables for the review elements in the target process can be determined by combining the basic deliverable configuration in the process template and the personalized configuration of deliverables for the target process. This allows the target deliverables to be automatically displayed during the user's review, providing data reference for the user's review process. This also ensures, to a certain extent, the universality and personalization of the deliverables associated with the review elements, ensuring the accuracy of the target deliverables and improving the user experience.

[0092] In some possible embodiments, determining the target deliverable associated with the review factor based on the first attribute value and the second attribute value may include: Add the deliverable in the first attribute value to the deliverable set.

[0093] If the deliverables in the first attribute value include deliverables X1, X2, and X3, all of them can be added to the deliverable set.

[0094] If the second attribute value includes an associated deliverable of an added type, the associated deliverable of the added type is added to the deliverable set.

[0095] If the associated deliverables of the added type determined in the second attribute value are X4 and X5, then X4 and X5 are added to the deliverable set. In this example, the deliverables included in the deliverable set are X1-X5.

[0096] If the second attribute value includes an associated deliverable of a deletion type, the associated deliverable of the deletion type is deleted from the deliverable set.

[0097] If the associated deliverables of the deletion type determined in the second attribute value are X2 and X4, then X2 and X4 in the deliverable set are deleted, and the deliverables in the deliverable set are now X1, X3, and X5.

[0098] Then, the target deliverable is determined based on the deliverables in the deliverable set. In this way, the associated deliverables required by the review element can be comprehensively determined by combining the configuration of the process template and the configuration in the target process, ensuring the rationality and accuracy of the deliverable association of the review element.

[0099] In actual application scenarios, deliverables are produced by nodes in a process. Due to the influence of the process operating environment or review results, some deliverables may not be produced. Based on this, the present disclosure also provides the following embodiments. Determining the target deliverable based on the deliverables in the deliverable set may include: querying the deliverables associated with the target process based on the query information of the deliverables in the deliverable set, and using the queried deliverables as the target deliverables; Among them, if the deliverable is a deliverable in the first attribute value, the query information of the deliverable includes the path information and deliverable information of the process template to which the deliverable belongs; if the deliverable is a deliverable in the second attribute value, the query information of the deliverable includes the path information and deliverable identification code of the process to which the deliverable belongs.

[0100] In this embodiment, for each deliverable in the deliverable set, a query can be performed based on its query information. If a query is found, it means that the deliverable has been produced and submitted. If no query is found, it means that the deliverable has not been submitted and is in an unavailable state, and there is no need to associate it.

[0101] The deliverable in the first attribute value is configured when the process template is configured. At this point, no actual deliverables have been produced. Therefore, the deliverable can be located and queried based on the path and deliverable information of the process template to determine whether it has been submitted. The deliverable in the second attribute value is configured after the target process is generated based on the process template. At this point, the deliverable has a unique deliverable identification code. This allows for rapid location and query based on the path and deliverable identification code of the process to determine whether the deliverable has been submitted. This further improves the accuracy and availability of the identified target deliverables.

[0102] Afterwards, the target deliverables can be displayed so that reviewers can quickly review the displayed target deliverables. This allows users to easily view the associated deliverables of the review elements. These associated deliverables may be located in different locations within the project, allowing reviewers to quickly locate and view the corresponding deliverables without having to manually query them. This provides effective and comprehensive data support for user review, improving review efficiency while reducing user operations.

[0103] Based on the same inventive concept, the present disclosure also provides a project process management device, such as Figure 5 As shown, the device 10 includes: A first processing module 100 is configured to add a deliverable sub-attribute to a review element attribute in a first data model in response to a first configuration instruction, wherein the first data model includes a node attribute in a process template; A second processing module 200 is configured to add associated deliverable attributes to a second data model in response to a second configuration instruction, wherein the second data model is used to represent attributes of a target process created based on the process template; The association module 300 is configured to associate deliverables with the review elements in the target process according to the review element attributes, the deliverable sub-attributes, and the associated deliverable attributes.

[0104] Optionally, the first processing module 100 includes: A first determining submodule, configured to determine, in response to the first configuration instruction, an identification code of a target review element in the first configuration instruction; A first acquisition submodule is configured to acquire path information and deliverable information of a process template to which a deliverable in the first configuration instruction belongs; a first processing submodule, configured to use the path information and the deliverable information as attribute values ​​of the deliverable sub-attribute, add the deliverable sub-attribute and the attribute value to the first data model based on the identification code, and associate the deliverable sub-attribute with the review factor attribute.

[0105] Optionally, the second processing module 200 includes: a second determining submodule, configured to determine, in response to the second configuration instruction, a process identifier for adding the associated deliverable attribute; a second acquisition submodule configured to, if the association type of the associated deliverable in the second configuration instruction is add, acquire path information of the process to which the associated deliverable belongs, and generate a deliverable identification code for the associated deliverable, wherein the attribute value of the associated deliverable attribute includes the path information and the deliverable identification code; a third determining submodule, configured to use the deliverable identification code of the associated deliverable as the attribute value of the associated deliverable attribute if the association type of the associated deliverable is deletion; The second processing submodule is configured to add the associated deliverable attribute and the attribute value to the second data model based on the process identifier.

[0106] Optionally, the second processing submodule includes: a fourth determining submodule, configured to determine whether the process identifier is associated with the associated deliverable attribute in the second data model; a merging submodule, configured to merge the attribute value with the attribute value of the associated deliverable in the second data model to obtain a new attribute value if the process identifier is associated with the associated deliverable attribute; The third processing submodule is configured to add the associated deliverable attribute and the new attribute value to the second data model based on the process identifier.

[0107] Optionally, the association module 300 includes: a fifth determining submodule, configured to determine, based on the identifier of the review element of the target process, a first attribute value of the deliverable sub-attribute corresponding to the review element; a sixth determining submodule, configured to determine, based on the process identifier of the target process, a second attribute value of the associated deliverable attribute corresponding to the review factor; A seventh determination submodule is configured to determine a target deliverable associated with the review element based on the first attribute value and the second attribute value.

[0108] Optionally, the seventh determining submodule includes: A first adding submodule, configured to add the deliverable in the first attribute value to the deliverable set; a second adding submodule, configured to add the associated deliverable of the added type to the deliverable set if the second attribute value includes the associated deliverable of the added type; a deletion submodule, configured to delete the associated deliverable of the deletion type from the deliverable set if the second attribute value includes an associated deliverable of the deletion type; An eighth determining submodule is configured to determine the target deliverable based on the deliverables in the deliverable set.

[0109] Optionally, the eighth determining submodule is configured to: querying the deliverables associated with the target process based on the query information of the deliverables in the deliverable set, and using the queried deliverables as the target deliverables; Among them, if the deliverable is a deliverable in the first attribute value, the query information of the deliverable includes the path information and deliverable information of the process template to which the deliverable belongs; if the deliverable is a deliverable in the second attribute value, the query information of the deliverable includes the path information and deliverable identification code of the process to which the deliverable belongs.

[0110] Optionally, the second processing module 200 is further configured to: In response to the second configuration instruction, determining whether the second configuration instruction satisfies operation permissions, wherein the operation permissions include user permissions of the operation user corresponding to the second configuration instruction and / or operation type permissions indicated by the second configuration instruction; If it is determined that the second configuration instruction satisfies the operation permission, an associated deliverable attribute is added to the second data model.

[0111] Reference below Figure 6 , which shows a schematic diagram of the structure of an electronic device (e.g., a terminal device or a server) 600 suitable for implementing the embodiments of the present disclosure. The terminal device in the embodiments of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 6 The electronic device shown is only an example and should not limit the functions and scope of use of the embodiments of the present disclosure.

[0112] like Figure 6 As shown, electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to programs stored in a read-only memory (ROM) 602 or programs loaded from a storage device 608 into a random access memory (RAM) 603. RAM 603 also stores various programs and data required for the operation of electronic device 600. Processing device 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to bus 604.

[0113] Typically, the following devices may be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication device 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. Figure 6 The electronic device 600 is shown with various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.

[0114] In particular, the processes described above with reference to the flowcharts can be implemented as a computer software program in accordance with embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program comprising program code for executing the methods illustrated by the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via the communication device 609, or installed from the storage device 608, or installed from the ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the methods of the embodiments of the present disclosure are performed.

[0115] It should be noted that the computer-readable medium described above in the present disclosure can be a computer-readable signal medium or a computer-readable storage medium or any combination thereof. The computer-readable storage medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any suitable combination thereof. More specific examples of the computer-readable storage medium can include, but are not limited to, 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 thereof. In the present disclosure, the computer-readable storage medium can be any tangible medium that contains or stores a program used by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, the computer-readable signal medium can include a data signal propagated in baseband or propagated as a carrier wave in a propagated data signal, in which the computer-readable program code is carried. Such a propagated data signal can take a variety of forms, including but not limited to, an electromagnetic signal, an optical signal, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium that can be used to carry or store a program for use by or in connection with an instruction execution system, apparatus, or device, other than the computer-readable storage medium. The program code contained in the computer-readable medium can be transmitted by any suitable medium, including but not limited to, wire, cable, RF (radio frequency), or the like, or any suitable combination thereof.

[0116] In some embodiments, the client and server can communicate using any currently known or later developed network protocol, such as HTTP (HyperText Transfer Protocol), and can be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or later developed network.

[0117] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0118] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: responds to a first configuration instruction, adds a deliverable sub-attribute to the review element attribute in the first data model, wherein the first data model includes the node attribute in the process template; responds to a second configuration instruction, adds an associated deliverable attribute to the second data model, wherein the second data model is used to represent the attribute of the target process created based on the process template; associates a deliverable with the review element in the target process according to the review element attribute, the deliverable sub-attribute and the associated deliverable attribute.

[0119] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving 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).

[0120] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0121] The modules described in the embodiments of the present disclosure may be implemented in software or hardware. In some cases, the name of a module does not limit the module itself. For example, the first processing module may be described as "a module that, in response to a first configuration instruction, adds a deliverable sub-attribute to the review factor attribute in the first data model."

[0122] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and 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 products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0123] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by 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 foregoing. More specific examples of machine-readable storage media may include an electrical connection based on 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), optical fibers, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0124] According to one or more embodiments of the present disclosure, Example 1 provides a project process management method, the method comprising: In response to the first configuration instruction, adding a deliverable sub-attribute to the review element attribute in the first data model, wherein the first data model includes a node attribute in the process template; In response to the second configuration instruction, adding associated deliverable attributes to a second data model, wherein the second data model is used to represent attributes of a target process created based on the process template; Deliverables are associated with the review elements in the target process according to the review element attributes, the deliverable sub-attributes, and the associated deliverable attributes.

[0125] According to one or more embodiments of the present disclosure, Example 2 provides the method of Example 1, wherein, in response to the first configuration instruction, adding a deliverable sub-attribute to the review factor attribute in the first data model includes: In response to the first configuration instruction, determining an identification code of a target review element in the first configuration instruction; Obtaining path information and deliverable information of the process template to which the deliverable in the first configuration instruction belongs; The path information and the deliverable information are used as attribute values ​​of the deliverable sub-attribute, and the deliverable sub-attribute and the attribute value are added to the first data model based on the identification code, and the deliverable sub-attribute is associated with the review factor attribute.

[0126] According to one or more embodiments of the present disclosure, Example 3 provides the method of Example 1, wherein, in response to the second configuration instruction, adding an associated deliverable attribute to the second data model includes: In response to the second configuration instruction, determining a process identifier for adding the associated deliverable attribute; If the association type of the associated deliverable in the second configuration instruction is add, obtaining path information of the process to which the associated deliverable belongs, and generating a deliverable identification code of the associated deliverable, wherein the attribute value of the associated deliverable attribute includes the path information and the deliverable identification code; If the association type of the associated deliverable is deletion, using the deliverable identification code of the associated deliverable as the attribute value of the associated deliverable attribute; The associated deliverable attribute and the attribute value are added to the second data model based on the process identifier.

[0127] According to one or more embodiments of the present disclosure, Example 4 provides the method of Example 3, wherein adding the associated deliverable attribute and the attribute value to the second data model based on the process identifier includes: determining whether the process identifier is associated with the associated deliverable attribute in the second data model; If the process identifier is associated with the associated deliverable attribute, merging the attribute value with the attribute value of the associated deliverable attribute in the second data model to obtain a new attribute value; The associated deliverable attribute and the new attribute value are added to the second data model based on the process identifier.

[0128] According to one or more embodiments of the present disclosure, Example 5 provides the method of Example 1, wherein associating the review element in the target process with the deliverable based on the review element attribute, the deliverable sub-attribute, and the associated deliverable attribute includes: Determining, based on an identifier of a review element of the target process, a first attribute value of a deliverable sub-attribute corresponding to the review element; Determining, based on the process identifier of the target process, a second attribute value of the associated deliverable attribute corresponding to the review element; A target deliverable associated with the review element is determined based on the first attribute value and the second attribute value.

[0129] According to one or more embodiments of the present disclosure, Example 6 provides the method of Example 5, wherein determining the target deliverable associated with the review factor based on the first attribute value and the second attribute value includes: Adding the deliverable in the first attribute value to the deliverable set; If the second attribute value includes an associated deliverable of an added type, adding the associated deliverable of the added type to the deliverable set; If the second attribute value includes an associated deliverable of a deletion type, deleting the associated deliverable of the deletion type from the deliverable set; The target deliverable is determined based on the deliverables in the deliverable set.

[0130] According to one or more embodiments of the present disclosure, Example 7 provides the method of Example 6, wherein determining the target deliverable based on the deliverables in the deliverable set includes: querying the deliverables associated with the target process based on the query information of the deliverables in the deliverable set, and using the queried deliverables as the target deliverables; Among them, if the deliverable is a deliverable in the first attribute value, the query information of the deliverable includes the path information and deliverable information of the process template to which the deliverable belongs; if the deliverable is a deliverable in the second attribute value, the query information of the deliverable includes the path information and deliverable identification code of the process to which the deliverable belongs.

[0131] According to one or more embodiments of the present disclosure, Example 8 provides the method of Example 1, wherein, in response to the second configuration instruction, adding an associated deliverable attribute to the second data model includes: In response to the second configuration instruction, determining whether the second configuration instruction satisfies operation permissions, wherein the operation permissions include user permissions of the operation user corresponding to the second configuration instruction and / or operation type permissions indicated by the second configuration instruction; If it is determined that the second configuration instruction satisfies the operation permission, an associated deliverable attribute is added to the second data model.

[0132] According to one or more embodiments of the present disclosure, Example 9 provides a project process management device, the device comprising: a first processing module configured to, in response to a first configuration instruction, add a deliverable sub-attribute to a review element attribute in a first data model, wherein the first data model includes a node attribute in a process template; a second processing module, configured to add associated deliverable attributes to a second data model in response to a second configuration instruction, wherein the second data model is used to represent attributes of a target process created based on the process template; The association module is configured to associate deliverables with the review elements in the target process according to the review element attributes, the deliverable sub-attributes, and the associated deliverable attributes.

[0133] According to one or more embodiments of the present disclosure, Example 10 provides a computer-readable medium having a computer program stored thereon, which implements the steps of the method described in any one of Examples 1-8 when executed by a processing device.

[0134] According to one or more embodiments of the present disclosure, Example 11 provides an electronic device, including: a storage device having a computer program stored thereon; A processing device is used to execute the computer program in the storage device to implement the steps of the method described in any one of Examples 1-8.

[0135] According to one or more embodiments of the present disclosure, Example 12 provides a computer program product, including a computer program, which implements the steps of any one of the methods of Examples 1-8 when executed by a processor.

[0136] The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of the present disclosure is not limited to technical solutions formed by specific combinations of the aforementioned technical features. It also encompasses other technical solutions formed by any combination of the aforementioned technical features or their equivalents, without departing from the scope of the above disclosure. For example, a technical solution formed by replacing the aforementioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

[0137] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details have been included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0138] Although the subject matter has been described using language specific to structural features and / or methodological logical acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims. Regarding the apparatus in the above-described embodiments, the specific manner in which each module performs operations has been described in detail in the embodiments related to the method and will not be elaborated upon here.

Claims

1. A project process management method, characterized in that: The method comprises: In response to the first configuration instruction, adding a deliverable sub-attribute to the review element attribute in the first data model, wherein the first data model includes a node attribute in the process template; In response to the second configuration instruction, adding associated deliverable attributes to a second data model, wherein the second data model is used to represent attributes of a target process created based on the process template; Deliverables are associated with the review elements in the target process according to the review element attributes, the deliverable sub-attributes, and the associated deliverable attributes.

2. The method according to claim 1, characterized in that The step of adding a deliverable sub-attribute to the review element attribute in the first data model in response to the first configuration instruction includes: In response to the first configuration instruction, determining an identification code of a target review element in the first configuration instruction; Obtaining path information and deliverable information of the process template to which the deliverable in the first configuration instruction belongs; The path information and the deliverable information are used as attribute values ​​of the deliverable sub-attribute, and the deliverable sub-attribute and the attribute value are added to the first data model based on the identification code, and the deliverable sub-attribute is associated with the review factor attribute.

3. The method according to claim 1, characterized in that The step of adding an associated deliverable attribute to the second data model in response to the second configuration instruction includes: In response to the second configuration instruction, determining a process identifier for adding the associated deliverable attribute; If the association type of the associated deliverable in the second configuration instruction is add, obtaining path information of the process to which the associated deliverable belongs, and generating a deliverable identification code of the associated deliverable, wherein the attribute value of the associated deliverable attribute includes the path information and the deliverable identification code; If the association type of the associated deliverable is deletion, using the deliverable identification code of the associated deliverable as the attribute value of the associated deliverable attribute; The associated deliverable attribute and the attribute value are added to the second data model based on the process identifier.

4. The method according to claim 3, wherein The adding the associated deliverable attribute and the attribute value to the second data model based on the process identifier includes: determining whether the process identifier is associated with the associated deliverable attribute in the second data model; If the process identifier is associated with the associated deliverable attribute, merging the attribute value with the attribute value of the associated deliverable attribute in the second data model to obtain a new attribute value; The associated deliverable attribute and the new attribute value are added to the second data model based on the process identifier.

5. The method according to claim 1, wherein Associating the review element with the deliverable in the target process based on the review element attribute, the deliverable sub-attribute, and the associated deliverable attribute includes: Determining, based on an identifier of a review element of the target process, a first attribute value of a deliverable sub-attribute corresponding to the review element; Determining, based on the process identifier of the target process, a second attribute value of the associated deliverable attribute corresponding to the review element; A target deliverable associated with the review element is determined based on the first attribute value and the second attribute value.

6. The method according to claim 5, characterized in that The determining, based on the first attribute value and the second attribute value, the target deliverable associated with the review factor includes: Adding the deliverable in the first attribute value to the deliverable set; If the second attribute value includes an associated deliverable of an added type, adding the associated deliverable of the added type to the deliverable set; If the second attribute value includes an associated deliverable of a deletion type, deleting the associated deliverable of the deletion type from the deliverable set; The target deliverable is determined based on the deliverables in the deliverable set.

7. The method according to claim 6, characterized in that The determining the target deliverable based on the deliverables in the deliverable set includes: querying the deliverables associated with the target process based on the query information of the deliverables in the deliverable set, and using the queried deliverables as the target deliverables; Among them, if the deliverable is a deliverable in the first attribute value, the query information of the deliverable includes the path information and deliverable information of the process template to which the deliverable belongs; if the deliverable is a deliverable in the second attribute value, the query information of the deliverable includes the path information and deliverable identification code of the process to which the deliverable belongs.

8. The method according to claim 1, characterized in that The step of adding an associated deliverable attribute to the second data model in response to the second configuration instruction includes: In response to the second configuration instruction, determining whether the second configuration instruction satisfies operation permissions, wherein the operation permissions include user permissions of the operation user corresponding to the second configuration instruction and / or operation type permissions indicated by the second configuration instruction; If it is determined that the second configuration instruction satisfies the operation permission, an associated deliverable attribute is added to the second data model.

9. A project process management device, characterized in that: The device comprises: a first processing module configured to, in response to a first configuration instruction, add a deliverable sub-attribute to a review element attribute in a first data model, wherein the first data model includes a node attribute in a process template; a second processing module, configured to add associated deliverable attributes to a second data model in response to a second configuration instruction, wherein the second data model is used to represent attributes of a target process created based on the process template; The association module is configured to associate deliverables with the review elements in the target process according to the review element attributes, the deliverable sub-attributes, and the associated deliverable attributes.

10. A computer-readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processing device, the steps of the method according to any one of claims 1 to 8 are implemented.

11. An electronic device, characterized in that: include: a storage device having a computer program stored thereon; A processing device, configured to execute the computer program in the storage device to implement the steps of the method according to any one of claims 1 to 8.

12. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images