Method for managing item delivery, related device and computer program product

Abstract

The invention provides a management project delivery method and device, electronic equipment, a computer readable storage medium and a computer program product, and relates to the technical field of artificial intelligence such as natural language processing, data processing, quality evaluation and project management. A specific embodiment of the method comprises: in response to a detected processing result of a project, adding evaluation values corresponding to unsatisfied demand tags in a group of demand tags of the project to obtain an addition result, the unsatisfied demand tags being demand tags hit by unproduced tags in the group of demand tags, and the unsatisfied demand tags being demand tags hit by unproduced tags in the group of demand tags; the group of demand labels are determined based on project description information provided by a demand provider of the project, and the output labels are determined based on output description information provided by a producer providing the processing result; in response to the fact that the sum result is larger than or equal to the numerical threshold value, the processing result is returned to the producer, and the unmet demand label is provided for the producer. Therefore, collaboration between the demand provider and the producer of the project can be established, management and quality control are performed on the processing result of the producer for the project based on the collaboration, and the output quality of the project is guaranteed.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, specifically to the field of artificial intelligence technology such as natural language processing, data processing, quality assessment and project management, and especially to methods, devices, electronic devices, computer-readable storage media and computer program products for managing project delivery. Background Art

[0002] A project is a temporary activity that achieves a specific goal and creates a unique result. For example, in a software delivery scenario, a "project" can be a code, program, etc. that provides a specific function.

[0003] In this process, in order to ensure that the project can be successfully completed and delivered, or in other words, to ensure that the results of the delivered project can meet the requirements, it is often necessary to manage and evaluate the quality of the project, so as to avoid delivering (project) results that do not meet the requirements, which will cause troubles to the project's demanders, acceptance parties and other parties.

[0004] In this context, with the intensification of market competition and the improvement of customer expectations, quality management, as one of the key elements in modern project management, has received increasing attention. Therefore, how to better ensure that the project can be completed smoothly and meet the requirements, and how to improve the quality of project management are worthy of attention and urgent needs. Summary of the invention

[0005] The embodiments of the present disclosure provide a method, an apparatus, an electronic device, a computer-readable storage medium, and a computer program product for managing project delivery.

[0006] In a first aspect, an embodiment of the present disclosure proposes a method for managing project delivery, comprising: in response to detecting a processing result of a project, adding evaluation values ​​corresponding to unmet requirement tags in a set of requirement tags of the project to obtain a summed result, wherein the unmet requirement tags are requirement tags in a set of requirement tags that are not hit by output tags, a set of requirement tags are determined based on project description information provided by a requirement provider of the project, and the output tags are determined based on output description information provided by a producer providing the processing results; in response to the summed result being greater than or equal to a numerical threshold, returning the processing result to the producer, and providing the unmet requirement tags to the producer.

[0007] In the second aspect, an embodiment of the present disclosure proposes an apparatus for managing project delivery, comprising: an evaluation value adding unit, configured to, in response to detecting a processing result of a project, add evaluation values ​​corresponding to unmet requirement tags in a set of requirement tags of the project to obtain a summed result, wherein the unmet requirement tag is a requirement tag in a set of requirement tags that is not hit by an output tag, a set of requirement tags is determined based on project description information provided by a requirement provider of the project, and the output tag is determined based on output description information provided by a producer providing the processing result; a result return and label providing unit, configured to, in response to the summed result being greater than or equal to a numerical threshold, return the processing result to the producer and provide the unmet requirement tag to the producer.

[0008] In a third aspect, an embodiment of the present disclosure provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that when the at least one processor executes, it is possible to implement the method for managing project delivery as described in any implementation method in the first aspect.

[0009] In a fourth aspect, an embodiment of the present disclosure provides a non-transitory computer-readable storage medium storing computer instructions, which are used to enable a computer to implement the method for managing project delivery as described in any implementation manner in the first aspect when executed.

[0010] In a fifth aspect, an embodiment of the present disclosure provides a computer program product comprising a computer program, which, when executed by a processor, can implement the method for managing project delivery as described in any implementation manner in the first aspect.

[0011] The method, apparatus, electronic device, computer-readable storage medium and computer program product for managing project delivery provided by the embodiments of the present disclosure, when detecting the processing result of the project, add the evaluation values ​​corresponding to the unsatisfied requirement tags in a set of requirement tags of the project to obtain the summed result, wherein the unsatisfied requirement tags are requirement tags in a set of requirement tags that are not hit by the output tags, the set of requirement tags are determined based on the project description information provided by the requirement provider of the project, and the output tags are determined based on the output description information provided by the output party that provides the processing results; if the summed result is less than the numerical threshold, it can be responded to by returning the processing result to the output party and providing the unsatisfied requirement tags to the output party.

[0012] The present disclosure can establish collaboration between the project's demand providers and output parties, and based on the collaboration, manage and control the quality of the output party's processing results for the project to ensure the output quality of the project.

[0013] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Other features, objects and advantages of the present disclosure will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:

[0015] Figure 1 is an exemplary system architecture in which the present disclosure may be applied;

[0016] Figure 2 A flowchart of a process for managing project delivery provided by an embodiment of the present disclosure;

[0017] Figure 3 A flowchart of a process in which an acceptance party provides feedback on a processing result according to an embodiment of the present disclosure;

[0018] Figure 4 A flowchart of a process for managing project delivery in an application scenario provided by an embodiment of the present disclosure;

[0019] Figure 5 A structural block diagram of a device for managing project delivery provided in an embodiment of the present disclosure;

[0020] Figure 6 A schematic diagram of the structure of an electronic device suitable for executing a method for managing project delivery provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0021] The following is a description of exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Similarly, for clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description. It should be noted that the embodiments in the present disclosure and the features in the embodiments may be combined with each other without conflict.

[0022] In addition, in the technical solutions involved in this disclosure, the acquisition, storage, use, processing, transportation, provision and disclosure of user personal information (such as project description information, output description information, etc. involved in the subsequent disclosure) are in compliance with the relevant laws and regulations and do not violate public order and good morals.

[0023] Figure 1An exemplary system architecture 100 is shown to which embodiments of the method, apparatus, electronic device, and computer-readable storage medium for managing project delivery of the present disclosure may be applied.

[0024] like Figure 1 As shown, the system architecture 100 may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0025] The users of various parties (e.g., the party that provides the requirements for the project, the party that actually processes and completes the project, etc.) can use the terminal devices 101, 102, 103 to interact with the server 105 through the network 104 to receive or send messages, etc. The terminal devices 101, 102, 103 and the server 105 can be installed with various applications for realizing information communication between the two, such as project collaboration applications, project development applications, instant messaging applications, etc.

[0026] Terminal devices 101, 102, 103 and server 105 can be hardware or software. When terminal devices 101, 102, 103 are hardware, they can be various electronic devices with display screens, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, etc.; when terminal devices 101, 102, 103 are software, they can be installed in the electronic devices listed above, which can be implemented as multiple software or software modules, or as a single software or software module, and no specific limitation is made here. When server 105 is hardware, it can be implemented as a distributed server cluster composed of multiple servers, or as a single server; when the server is software, it can be implemented as multiple software or software modules, or as a single software or software module, and no specific limitation is made here.

[0027] The server 105 can provide various services through various built-in applications. For example, a project collaborative application that can provide project collaborative functions and assist the output party in project processing and development can be used as an example. When the server 105 runs the project collaborative application, it can achieve the following effects: First, the server 105 can communicate with the terminal devices 101, 102, and 103 (for example, the terminal devices can at least be used by the output party) through the network 104 to determine whether it can detect the processing results of the project in the terminal devices 101, 102, and 103, or the processing results for the project provided by the terminal devices 101, 102, and 103. Then, if the server 105 can detect the processing results of the project, it can respond to this and add the evaluation values ​​corresponding to the unsatisfied demand tags in a set of demand tags of the project to obtain the summed result; wherein the unsatisfied demand tags are demand tags in a set of demand tags that are not hit by the output tags, a set of demand tags are determined based on the project description information provided by the demand provider of the project, and the output tags are determined based on the output description information provided by the output party providing the processing results. Next, if the sum is greater than or equal to the numerical threshold, the server 105 may respond to this by returning the processing result to the producer and providing the producer with an unmet demand tag.

[0028] It should be pointed out that, as discussed above, with respect to the "processing result", in addition to being "detected" by the server 105, it can actually also be "detected" by the terminal devices 101, 102, and 103. For example, the terminal devices 101, 102, and 103 can detect the "processing result" locally, and after determining that the "processing result" has been detected, they choose to communicate and report the situation to the server 105, so that the server 105 can approximately achieve the "detection" effect.

[0029] In some embodiments, the above complete process can actually be implemented by terminal devices 101, 102, and 103. For example, after the terminal device used by the producer determines that the processing result is obtained based on the producer's action and is stored locally, it can obtain the processing result by "local reading" and similarly perform "adding the evaluation values ​​corresponding to the unsatisfied demand tags in a set of demand tags of the project" and the subsequent actions executed by the server 105 as exemplified above.

[0030] Accordingly, in such a case, the exemplary system architecture 100 may not include the server 105 , but utilize the terminal devices 101 , 102 , 103 to implement the above-mentioned process of managing project delivery.

[0031] Since, in the process of managing project delivery, it may be necessary to collaborate with multiple user entities such as demand providers and output parties, for the purposes of computing resource needs, ensuring data security and communication convenience, the method for managing project delivery provided in the subsequent embodiments of the present disclosure is generally executed by a server 105 with stronger computing power and more computing resources. Accordingly, the device for managing project delivery is generally also set in the server 105.

[0032] However, it should also be pointed out that, similar to what has been discussed above, when the terminal devices 101, 102, and 103 also have computing power and computing resources that meet the requirements, the terminal devices 101, 102, and 103 can also complete the various operations that are handed over to the server 105 through the project collaboration applications installed thereon, and then output the same results as the server 105. Especially in the case where there are multiple terminal devices with different computing power at the same time, but the project collaboration application determines that the terminal device where it is located has stronger computing power and more remaining computing resources, it can let the terminal device perform the above-mentioned operations, thereby appropriately reducing the computing pressure of the server 105. Correspondingly, the device for managing project delivery can also be set in the terminal devices 101, 102, and 103.

[0033] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to the implementation requirements.

[0034] Please refer to Figure 2 , Figure 2 A flowchart of a process for managing project delivery provided by an embodiment of the present disclosure, wherein process 200 includes the following steps:

[0035] Step 201: in response to detecting a processing result of a project, summing up evaluation values ​​corresponding to unsatisfied requirement tags in a set of requirement tags of the project to obtain a summing result;

[0036] This step is intended for the implementation of the method for managing project delivery (e.g. Figure 1 The server 105 shown in the figure, when detecting the processing result of the project (for example, the processing result obtained by the producer using the terminal device 103 to process the project) (for example, the terminal device 103 can obtain the processing result of the project locally, and then, based on the operation of the user of the producer, provide the processing result to the execution entity, or request the execution entity to determine whether the processing result can be actually issued and whether the processing result can be used as the output result of the "project"), in response, add up the evaluation values ​​corresponding to the unsatisfied demand tags in a set of demand tags of the project to obtain the summed result.

[0037] The requirement tag (in a set of requirement tags) can be determined based on the project description information provided by the requirement provider of the project. For example, the requirement provider can provide the project description information for the project to the execution subject through the terminal devices 101, 102, 103 (for example, the description can record the functions that the project is expected to achieve, the implementation methods of each function, the constraints on the implementation methods, etc.), so that the execution subject can determine the tag result hit by the project information by parsing the project description information, and use the tag result as the requirement tag.

[0038] For example, the execution subject may perform semantic analysis on the project description information and determine the requirement tag based on the semantic analysis result. For example, the execution subject may determine each keyword, entity, etc. included in the semantic analysis result as the requirement tag.

[0039] In some optional implementations of this embodiment, the demand provider may be allowed to provide project description information by providing a "description document" written in natural language or other pre-agreed language. Thus, the demand provider (for example, the project initiator, or the person who interfaces with the external project initiator) can directly provide and indicate the demand (label) through the project description information in the form of "natural language", so that the demand provider can determine the demand label more efficiently and with less difficulty.

[0040] That is, if the execution subject receives the project description information provided by the requirement provider, it can respond to it to generate a semantic analysis result of the project description information. Then, the execution subject determines a set of requirement tags based on the semantic analysis result.

[0041] For example, in a software delivery scenario, the description document may indicate in natural language: the programming language used by the code, the functions of the code, the operating environment to which the code can be adapted, and so on.

[0042] Accordingly, the execution subject can determine each requirement tag based on the semantic parsing result of the project description information corresponding to the description document. For example, for "the programming language used by the code", the specific form of the requirement tag can be indicated as "C language", "Java language" and so on.

[0043] In practice, the project producer can usually obtain the description document based on direct communication with the demand provider or through forwarding by the execution entity to obtain the project description information, determine the project requirements, and process the project based on its understanding of the project description information and project requirements.

[0044] In some optional implementations of this embodiment, it is also possible to choose to pre-maintain a tag knowledge base so that the execution subject can use the pre-maintained tag knowledge base to determine a set of requirement tags based on the semantic analysis results.

[0045] Specifically, at least one reference tag and the semantic information corresponding to the reference tag (for example, the specific form may be a semantic vector or a semantic matrix) may be maintained in the tag knowledge base. Accordingly, after the semantic analysis result of the project description information is determined, the semantic analysis result may be vectorized or matrixed, for example, so that the vectorized or matrixed result may be compared with the semantic information included in the tag knowledge base to extract the reference tag corresponding to the semantic analysis result (for example, the similarity between the two is greater than or equal to a predetermined similarity threshold) as the requirement tag, thereby determining a set of requirement tags.

[0046] Therefore, by means of a pre-maintained tag knowledge base, not only can the content of tags be standardized, but also the required tags can be determined more quickly. For example, by using a tag knowledge base, it is possible to avoid duplicate marking due to differences in semantic analysis results, which results in actually identical or highly similar content being determined differently as different required tags.

[0047] Similarly, for output labels, their content is actually determined corresponding to the content, capabilities, etc. included in the processing results.

[0048] In some optional implementations of this embodiment, the producer may also choose to provide output description information to utilize the execution subject to actually determine the output label, so as to reduce the difficulty of the producer in determining the output label.

[0049] For example, for the project's output party (for example, software engineers who actually write code in software delivery scenarios, etc.), output description information can be provided based on their understanding of the content and capabilities that the processing results can satisfy, so that the execution entity can determine the output label based on the output description information.

[0050] Similar to the demand tag, the execution subject may also generate a semantic analysis result of the output description information in response to receiving the output description information provided by the producer, and then determine the output tag based on the semantic analysis result of the output description information.

[0051] In some optional implementations of this embodiment, whether for demand tags or output tags, the execution subject may further choose to delete tags with semantic duplication based on the semantic analysis results.

[0052] Taking the requirement tag as an example, the execution subject can determine the requirement tags that have duplicate semantics with other requirement tags based on the semantic analysis results of the requirement tags. For example, after generating the semantic analysis result of a requirement tag, the execution subject can compare the semantic analysis result with the semantic analysis results of other requirement tags. If the similarity between the semantic analysis result of the requirement tag and at least one other requirement tag in a group of requirement tags is greater than or equal to the similarity threshold, then the requirement tag can be determined to be a "requirement tag with duplicate semantics".

[0053] Then, the execution subject can choose to delete the demand tags with repeated semantics in a set of demand tags, thereby avoiding duplication of demand tags and output tags, which will interfere with the subsequent comparison and query process of demand tags that are not hit by the output tags, and avoid wasting computing resources due to repeated computing.

[0054] In some optional implementations of the present embodiment, when there are (or have) labels with repeated semantics (for example, demand labels, output labels), the executing entity may select the specific labels to be "deleted" or "removed" based on the semantic completeness of the labels (for example, removing labels with low semantic completeness and retaining only labels with the highest semantic completeness), or may select the order in which the semantic analysis results are identified and choose to retain only the label for which the semantic analysis results are generated first, or may choose to retain only the label for which the semantic analysis results are generated last.

[0055] Next, when the execution subject detects the processing result, it responds by comparing the (set of) demand tags provided by the demand provider and the (set of) output tags provided by the output party to determine the demand tags in the set of demand tags that are not hit by the output tags.

[0056] Typically, the execution entity can determine whether a demand tag is hit by at least one output tag by directly comparing the text information of the demand tag and the output tag (for example, for the demand tag "AAA", if there is an output tag in the form of "AAA", then the demand tag of "AAA" can be considered to be "hit by at least one output tag").

[0057] In some optional implementations of this embodiment, in order to improve the comparison quality under this method, if both the demand labels and the output labels are provided by the execution entity (for example, determined by semantic analysis of the project description information and the output description information), then in this process, a "semantic analysis" standard can be selected to uniformly determine the demand labels and output labels (for example, using the same corpus), so that the "same semantics" can have the same "label" in textual form.

[0058] This can avoid "false hits" or "missed recognition" due to differences in text form. For example, when using a label knowledge base to determine a required label, the output label can also be determined using the label knowledge base so that the "semantic standards" of the two labels are equivalent.

[0059] In some optional implementations of this embodiment, the execution entity may also choose to determine whether the demand tag is hit by (at least one) output tag based on the semantic similarity between the demand tag and the output tag.

[0060] For example, the execution entity may compare the semantic information of the demand tag with the semantic information of each output tag. If there is a similarity with the semantic information of the demand tag that is greater than or equal to a preset similarity threshold (the similarity threshold may be the same as the numerical value of the similarity threshold discussed above, or may be different, and the present disclosure is not intended to limit this), it is determined that the demand tag is hit by (at least one) output tag.

[0061] Then, after determining the unsatisfied requirement tags among a set of requirement tags of the project, the execution entity may add up the evaluation values ​​corresponding to these requirement tags to obtain a summed result.

[0062] Usually, the evaluation value corresponding to the requirement tag can be directly determined by the instruction of the requirement provider (for example, after the requirement tag is determined, the requirement tag is provided to the requirement provider to require the requirement provider to "assign" each requirement tag). Accordingly, for each requirement tag, the requirement provider can "assign" each requirement tag according to the "importance" of the requirement tag that it believes.

[0063] In some optional implementations of this embodiment, for the "value assignment" process of the demand provider, in order to facilitate its more accurate and quality "value assignment", the execution entity may provide it with a "reference value assignment table". The "reference value assignment table" may indicate the numerical range of the evaluation value corresponding to each "importance" for reference by the demand provider. For example, if the "importance" is high, the corresponding evaluation value should be between [a1, a2]; if the "importance" is medium, the corresponding evaluation value should be between [b1, b2], where the value of b2 is less than a1.

[0064] In some optional implementations of this embodiment, for the evaluation value corresponding to the requirement tag, a reference evaluation value may be pre-configured so that the execution subject can subsequently determine the evaluation value of the requirement tag directly based on the reference evaluation value.

[0065] For example, the reference evaluation value can be obtained based on the statistics of the assignment results of the "demand tag" that has been "assigned", thereby reducing the user consumption of the demand provider.

[0066] Accordingly, after determining the unmet requirement tags in a set of requirement tags of the project, the subsequent execution entity can use the reference evaluation values ​​corresponding to these requirement tags as “evaluation values” to add them up to obtain a summed result.

[0067] In some optional implementations of this embodiment, since the reference evaluation value may be set by the executing entity through, for example, "statistical" methods, it may not accurately fit the "value evaluation" of the demand provider. Therefore, the demand provider may also choose to issue a reference evaluation value adjustment instruction for a target demand tag in a group of demand tags to adjust the reference evaluation value to meet its personalized "value standard".

[0068] Accordingly, the execution entity may respond to the situation in which the demand provider issues a reference evaluation value adjustment instruction for a target demand tag in a group of demand tags, and update the reference evaluation value corresponding to the target demand tag based on the instructions of the reference evaluation value adjustment instruction.

[0069] It should be understood that the reference evaluation value may also be pre-configured by the demand provider (for example, the demand provider configures the corresponding reference evaluation value for each reference tag in the tag knowledge base based on the interaction with the execution subject). In this case, the demand provider may also choose to issue a reference evaluation value adjustment instruction for the target demand tag in a group of demand tags to update the reference evaluation value corresponding to the target demand tag, so as to achieve "personalization" more flexibly and dynamically.

[0070] Step 202: In response to the sum being greater than or equal to the numerical threshold, the processing result is returned to the producer, and an unmet demand label is provided to the producer.

[0071] The purpose of this step is that after the execution entity determines the sum result based on the above steps, if the sum result is greater than or equal to a (predetermined, preset) numerical threshold, the execution entity can respond to this by returning the processing result to the producer and providing the producer with an unmet demand label.

[0072] Typically, the numerical threshold can be determined in advance based on the criteria for considering that the "processing result" cannot meet the processing requirements. That is, if the total evaluation value corresponding to the unsatisfied requirement tags is greater than or equal to the numerical threshold, it can be considered that the processing result cannot meet the processing requirements of a set of requirement tags.

[0073] Accordingly, if the executing entity determines that the sum of the evaluation values ​​corresponding to the unmet demand tags exceeds the threshold, that is, the "quality quantification results" of the unmet demand tags have reached the standard of "unable to meet the processing requirements", the executing entity may choose to return the processing results to the producer and provide these unmet demand tags to the producer.

[0074] In practice, if the output party provides the executing party with a "file" of the processing results, the executing party may choose to return the "file" together with the output party to facilitate its review and clarify the "file" to which the return is directed.

[0075] In some scenarios, if the producer does not actually provide these "files", the execution entity may choose to prompt the producer by, for example, sending a return message through a return node to achieve "return".

[0076] Accordingly, after determining that the processing result is rolled back, the producer can modify the processing result based on the situation of these unmet demand tags, in the hope of satisfying and hitting more demand tags, thereby improving the processing quality of the project.

[0077] The method for managing project delivery provided by the embodiment of the present disclosure, in response to detecting the processing result of the project, adds the evaluation values ​​corresponding to the unsatisfied demand tags in a set of demand tags of the project to obtain the summed result, wherein the unsatisfied demand tags are demand tags in a set of demand tags that are not hit by the output tags, a set of demand tags are determined based on the project description information provided by the demand provider of the project, and the output tags are determined based on the output description information provided by the output party that provides the processing result; in response to the summed result being greater than or equal to the numerical threshold, the processing result is returned to the output party, and the unsatisfied demand tags are provided to the output party. In this way, it is possible to establish collaboration between the demand provider and the output party of the project, and based on the collaboration, the output party is managed and the quality is controlled for the processing results of the project to ensure the output quality of the project.

[0078] In some embodiments, the demand tags determined by the execution subject may not fully meet the needs of the demand provider. For example, when determining the demand tags using the tag knowledge base, the tag knowledge base does not maintain reference tags that can meet the expectations of the demand provider; for another example, a demand tag that is not expected by the user is provided.

[0079] In such a case, in order to satisfy the demand provider, the execution entity may also choose to provide a set of demand tags to the corresponding demand provider after determining a set of demand tags.

[0080] Accordingly, if the requirement provider returns a set of requirement tags and sends a first tag update instruction, the execution subject can respond to this and update the set of requirement tags based on the instructions of the first tag update instruction. For example, the update method can be to add a new requirement tag to the set of requirement tags, delete a certain requirement tag provided by the execution subject, etc.

[0081] In some embodiments, during the management and delivery process of the entire project, the processing results of the project may not be provided to the "demand provider" in the end (for example, the "demand provider" is only an internal staff member related to the project who communicates with external customers about the requirements, and the final processing results may be provided to the external customers of the project). At this time, the overall process may also include the project acceptance party, for example, the acceptance party is the client party who actually uses the processing results of the project (correspondingly, the project demand party may be the internal staff member who communicates with the acceptance party and the client party).

[0082] In such a case, the executing entity may also choose to provide the determined set of requirement tags to the project acceptance party, and allow the acceptance party to adjust the set of requirement tags similar to the requirement provider.

[0083] For example, after receiving a group of requirement tags, the acceptance party may also instruct the execution subject to update the group of requirement tags by sending a second tag update instruction for the group of requirement tags to the execution subject.

[0084] Accordingly, the execution subject can respond to receiving the second tag update instruction for a set of requirement tags from the acceptance party and update the set of requirement tags based on the instruction of the second tag update instruction. Thus, in the process of "determining the requirements and requirement tags for the project", the "opinions" of the acceptance party can be referred to to more accurately determine the project requirements.

[0085] Based on any of the above embodiments, if the execution subject uses a tag knowledge base in the process of determining tags, in order to ensure the quality of the tag knowledge base, the execution subject may choose to update the tag knowledge base regularly and periodically.

[0086] Specifically, the execution subject may respond when (determining) the current time has reached the periodic update time for the tag knowledge base, and clear the reference tags whose extraction rate is less than the extraction rate threshold in the tag knowledge base.

[0087] For example, the execution entity may detect the "extraction rate" (for example, the ratio of the number of hits to the total number of hits of all reference tags in this cycle) of reference tags in the tag knowledge base being used and hit during each update cycle.

[0088] If the "extraction rate" of the reference tag is lower than the extraction rate value, the executor can choose to clear the reference tag to prevent these "low extraction rate" and "possibly low-quality demand tags" from interfering with the matching and tag determination process and occupying storage resources.

[0089] In some embodiments, the maintainer of the tag knowledge base may also choose to periodically (or non-periodically, the present disclosure is not intended to be limiting of this) provide new reference tags to the tag knowledge base to achieve "iteration of reference tags" to improve the quality of reference tags.

[0090] In some embodiments, if the execution entity determines that the sum result is less than the numerical threshold, the execution entity may "believe" that the processing result is usable and meets the requirements, and may choose to output it and provide it to, for example, the "acceptance party" discussed above, thereby achieving "automatic" delivery of the results of the project.

[0091] It should be understood that, for ease of understanding, although the "acceptance party" and the "demand provider" are chosen here as different entities for illustrative purposes, in some scenarios, the "acceptance party" and the "demand provider" may actually be the same entity (for example, the customer provides the requirements and conducts the acceptance), and the present disclosure is not intended to limit this.

[0092] Accordingly, for the processing results that have been provided and issued, the recipient of the subsequent processing results (for example, the demand provider, the acceptance party) can also further instruct the adjustment of the processing results based on the interaction and communication with the execution subject.

[0093] For ease of understanding, the following example is given using "a situation including the acceptance party", that is, the acceptance party is used as the recipient of the final "processing result".

[0094] For this, please refer to Figure 3 , Figure 3 A flowchart of a process of feedback of a processing result by an acceptance party provided in an embodiment of the present disclosure includes process 300. Process 300 specifically includes the following steps:

[0095] Step 301: In response to the sum result being less than the numerical threshold, the processing result is pushed to the project acceptance party;

[0096] Step 302: In response to the acceptance party returning updated feedback information regarding the processing result, determining a feedback tag corresponding to the updated feedback information;

[0097] Specifically, as discussed above, if the acceptance party returns updated feedback information for the processing result, the execution entity may determine a feedback tag corresponding to the updated feedback information.

[0098] Generally, if the feedback tag is directly provided in the update feedback information, the execution subject can use the feedback tag. Alternatively, if the feedback tag is not directly provided in the update feedback information, the execution subject can determine the feedback tag hit by the update feedback information by parsing the semantics of the update feedback information, similar to the requirement tag and output tag, as discussed above.

[0099] Step 303: In response to the feedback tag being a subtag of a requirement tag in a group of requirement tags, replacing the corresponding requirement tag with the subtag;

[0100] Specifically, if the executing entity determines that the feedback tag determined based on the above step 302 is a sub-tag of a requirement tag in a set of requirement tags (that is, the feedback tag is actually a subordinate tag of the requirement tag, a refined requirement tag), then the executing entity may choose to update a set of requirement tags (previously provided to the output party) (that is, replace the corresponding requirement tags with the sub-tags).

[0101] Step 304: providing the demand tags that are not matched by the output tags in the set of demand tags obtained after replacement to the output party.

[0102] Specifically, after completing the replacement of the requirement tags and updating a set of requirement tags based on the above step 303, the execution subject can provide the requirement tags that are not hit by the output tags in the set of requirement tags obtained after the replacement to the output party. Thus, a reference is provided to the output party, so that the output party can adjust the processing results according to the direction of these unhit requirement tags to improve the quality of the processing results.

[0103] It should be understood that the acceptance party can also feedback updated requirement tags that are independent of a set of requirement tags (for example, updated requirement tags are not "sub-tags of existing requirement tags"). Thus, the acceptance party can adjust requirements more flexibly based on the processing results and improve the delivery quality of the project.

[0104] In some embodiments, in order to facilitate project management and trace the quality of the project, after the acceptance party actually receives and returns the receiving instruction to the execution entity, the execution entity can also choose to respond to the acceptance party's return of the receiving instruction regarding the processing result and request the acceptance party to provide a satisfaction evaluation value.

[0105] Then, if the acceptance party returns a satisfaction rating value, the execution entity can respond to this by selecting a combination of the satisfaction rating value and the label rating value corresponding to the output label (usually, the label rating value of the output label can be determined by referring to the rating value of the corresponding requirement label) to generate project evaluation information for the project.

[0106] Therefore, the execution and processing results of the project can be "backtracked" based on the project evaluation information to assist in the execution decisions of subsequent projects.

[0107] It should be understood that in some scenarios, the output labels of the processing results may actually include "output labels" that do not correspond to the requirement labels. In such a case, when determining the project evaluation information, the executing entity can choose to refer only to those output labels that hit the requirement labels, or refer to each output label at the same time according to different requirements.

[0108] In some embodiments, a "complete project" may actually be composed of multiple different "sub-projects". In this case, the execution subject may determine the project evaluation information of the "complete project" based on the project evaluation information of each "sub-project". For example, the project evaluation information of each "sub-project" may be added up, the project evaluation information of each "sub-project" may be weighted, or the project evaluation information of the "complete project" may be determined and obtained based on the average result of the project evaluation information of each "sub-project".

[0109] To deepen understanding, this disclosure also provides a specific implementation solution for managing project delivery process in combination with a specific application scenario, please refer to Figure 4 Process 400 is shown.

[0110] For easier understanding, you can also refer to Figure 1 The system architecture 100 is shown. For example, in process 400, the server 105 can be used as the execution subject of the process of managing project delivery, the terminal device 101 can be used as the device used by the demand provider and the acceptance party, and the terminal device 103 can be used as the device used by the output party.

[0111] The process 400 is specifically as follows:

[0112] First, the demand provider (not shown in the figure) can use the terminal device 101 to execute S401 to provide the server 105 with project description information 401 for the project (not shown in the figure).

[0113] Then, after receiving the project description information 401 , the server 105 may execute S402 to generate a semantic analysis result 403 of the project description information 401 .

[0114] Then, the server 105 continues to execute S403 to determine (a set of) requirement tags of the project based on the semantic analysis result 403, for example, requirement tags 411, 412...41N, where N is a positive integer.

[0115] Subsequently, if the producer (not shown) processes the project using the terminal device 103 and obtains the processing result of the project, the producer can use the terminal device 103 to execute S404 to provide the server 105 with the processing result 421 and output description information 422 of the project.

[0116] After receiving the processing result 421 and output description information 422 of the project, the server 105 may execute S405 to generate a semantic analysis result 405 of the output description information 422 .

[0117] Next, the server 105 may similarly execute S406 to determine (a set of) output tags based on the semantic analysis result 405 , for example, output tags 431 , 432 , . . . 43n , where n is a positive integer.

[0118] Then, the server 105 continues to execute S406 to determine the demand tags among the demand tags 411, 412, ... 41N that are not hit by the output tags 431, 432, ... 43n.

[0119] For the convenience of explanation, illustratively, among the requirement tags 411 , 412 . . . 41N, the requirement tags 411 and 412 are not hit.

[0120] In this regard, the server 105 may add the evaluation values ​​corresponding to the unhit requirement tags (ie, requirement tags 411 and 412 ) based on executing S407 to obtain a sum result 441 .

[0121] Exemplarily, if the sum result 411 is greater than or equal to the numerical threshold, the server 105 may respond by selecting to execute S408 to return the processing result 421 of the project to the terminal device 103 and provide the requirement tags 411 and 412 to the terminal device 103 (for reference by the producer).

[0122] Further references Figure 5 As an implementation of the methods shown in the above figures, the present disclosure provides an embodiment of a device for managing project delivery. Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0123] like Figure 5As shown, the device 500 for managing project delivery of this embodiment may include: an evaluation value summing unit 501, and a result return and label providing unit 502. The evaluation value summing unit 501 is configured to, in response to detecting the processing result of the project, sum the evaluation values ​​corresponding to the unsatisfied demand tags in a set of demand tags of the project to obtain a summed result, wherein the unsatisfied demand tag is a demand tag in a set of demand tags that is not hit by the output tag, the set of demand tags is determined based on the project description information provided by the demand provider of the project, and the output tag is determined based on the output description information provided by the output party that provides the processing result; the result return and label providing unit 502 is configured to, in response to the summed result being greater than or equal to a numerical threshold, return the processing result to the output party, and provide the unsatisfied demand tag to the output party.

[0124] In the device for managing project delivery 500, the specific processing of the evaluation value adding unit 501 and the result return and label providing unit 502 and the technical effects thereof can be referred to in Figure 2 The relevant descriptions of steps 201 - 202 in the corresponding embodiment are not repeated here.

[0125] In some optional implementations of this embodiment, the device 500 also includes: a project description information analysis unit, configured to generate a semantic analysis result of the project description information in response to receiving the project description information provided by the demand provider; and a demand label determination unit, configured to determine a set of demand labels based on the semantic analysis result.

[0126] In some optional implementations of this embodiment, the requirement tag determination unit is further configured to extract reference tags corresponding to the semantic analysis results from a pre-maintained tag knowledge base as requirement tags, and determine a group of requirement tags.

[0127] In some optional implementations of this embodiment, the device 500 also includes: a first requirement label providing unit, configured to provide a group of requirement labels to the requirement provider; a first requirement label updating unit, configured to update the group of requirement labels based on the instructions of the first label update instruction in response to receiving a first label update instruction from the requirement provider for a group of requirement labels.

[0128] In some optional implementations of this embodiment, the device 500 also includes: a second requirement label providing unit, configured to provide a group of requirement labels to the acceptance party of the project; a second requirement label updating unit, configured to update a group of requirement labels based on the instructions of the second label update instruction in response to receiving a second label update instruction from the acceptance party for a group of requirement labels.

[0129] In some optional implementations of this embodiment, the device 500 also includes: a label knowledge base updating unit, configured to clear the reference labels whose extraction rate is less than the extraction rate threshold in the label knowledge base in response to the current moment reaching the periodic update moment for the label knowledge base.

[0130] In some optional implementations of the present embodiment, the device 500 also includes: a duplicate tag deletion unit, which is configured to delete requirement tags with duplicate semantics in a group of requirement tags based on the semantic analysis results of the requirement tags, wherein the similarity between the requirement tags with duplicate semantics and the semantic analysis results of at least one other requirement tag in the group of requirement tags is greater than or equal to a similarity threshold.

[0131] In some optional implementations of this embodiment, the device 500 also includes: an output description information analysis unit, configured to generate a semantic analysis result of the output description information in response to receiving the output description information provided by the producer; and an output label determination unit, configured to determine the output label based on the semantic analysis result of the output description information.

[0132] In some optional implementations of this embodiment, the requirement tags in a group of requirement tags are correspondingly preset with reference evaluation values, and the evaluation value and determination unit 501 is further configured to add the reference evaluation values ​​corresponding to the unmet requirement tags in the group of requirement tags of the project to obtain the summed result.

[0133] In some optional implementations of this embodiment, the device 500 also includes: a reference evaluation value updating unit, which is configured to respond to the demand provider issuing a reference evaluation value adjustment instruction for a target demand tag in a group of demand tags, and update the reference evaluation value corresponding to the target demand tag based on the instructions of the reference evaluation value adjustment instruction.

[0134] In some optional implementations of this embodiment, the device 500 also includes: a processing result pushing unit, configured to push the processing result to the project acceptance party in response to the addition result being less than a numerical threshold; a feedback tag determination unit, configured to determine the feedback tag corresponding to the updated feedback information in response to the acceptance party returning updated feedback information for the processing result; a requirement tag replacement unit, configured to replace the corresponding requirement tag with the sub-tag in response to the feedback tag being a sub-tag of a requirement tag in a group of requirement tags; a third requirement tag providing unit, configured to provide the requirement tags in the group of requirement tags obtained after replacement that are not hit by the output tags to the output party.

[0135] In some optional implementations of this embodiment, the device 500 also includes: a satisfaction evaluation value request unit, configured to request the acceptance party to provide a satisfaction evaluation value in response to the acceptance party returning a receiving instruction regarding the processing result; and a project evaluation information generation unit, configured to generate project evaluation information for the project based on a combination result of the satisfaction evaluation value and the label evaluation value corresponding to the output label in response to the acceptance party returning the satisfaction evaluation value.

[0136] This embodiment exists as an apparatus embodiment corresponding to the above-mentioned method embodiment. The apparatus for managing project delivery provided by this embodiment, in response to detecting the processing result of the project, adds the evaluation values ​​corresponding to the unsatisfied demand tags in a set of demand tags of the project to obtain the summed result, wherein the unsatisfied demand tags are demand tags in a set of demand tags that are not hit by the output tags, a set of demand tags are determined based on the project description information provided by the demand provider of the project, and the output tags are determined based on the output description information provided by the output party that provides the processing result; in response to the summed result being greater than or equal to the numerical threshold, the processing result is returned to the output party, and the unsatisfied demand tags are provided to the output party. In this way, it is possible to establish collaboration between the demand provider and the output party of the project, and based on this collaboration, the output party is managed and the quality is controlled for the processing results of the project to ensure the output quality of the project.

[0137] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.

[0138] Figure 6 A schematic block diagram of an example electronic device 600 that can be used to implement an embodiment of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present disclosure described and / or required herein.

[0139] like Figure 6As shown, the device 600 includes a computing unit 601, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 602 or a computer program loaded from a storage unit 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the device 600 can also be stored. The computing unit 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0140] A number of components in the device 600 are connected to the I / O interface 605, including: an input unit 606, such as a keyboard, a mouse, etc.; an output unit 607, such as various types of displays, speakers, etc.; a storage unit 608, such as a disk, an optical disk, etc.; and a communication unit 609, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 609 allows the device 600 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0141] The computing unit 601 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 601 performs the various methods and processes described above, such as the method for managing project delivery. For example, in some embodiments, the method for managing project delivery may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 608. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 600 via the ROM 602 and / or the communication unit 609. When the computer program is loaded into the RAM 603 and executed by the computing unit 601, one or more steps of the method for managing project delivery described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform the method for managing project delivery in any other appropriate manner (e.g., by means of firmware).

[0142] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0143] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0144] 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, device, or equipment. 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, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, 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 foregoing.

[0145] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0146] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by 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), and the Internet.

[0147] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship between the client and the server is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or a cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and virtual private servers (VPS) services. The server can also be divided into a server of a distributed system, or a server combined with a blockchain.

[0148] According to the technical solution of the embodiment of the present disclosure, in response to detecting the processing result of the project, the evaluation values ​​corresponding to the unsatisfied demand tags in a set of demand tags of the project are added to obtain the summed result, wherein the unsatisfied demand tags are demand tags in a set of demand tags that are not hit by the output tags, a set of demand tags are determined based on the project description information provided by the demand provider of the project, and the output tags are determined based on the output description information provided by the output party that provides the processing results; in response to the summed result being greater than or equal to the numerical threshold, the processing result is returned to the output party, and the unsatisfied demand tags are provided to the output party. In this way, it is possible to establish collaboration between the demand provider and the output party of the project, and based on the collaboration, the output party can manage and control the processing results of the project, thereby ensuring the output quality of the project.

[0149] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions provided by this disclosure can be achieved, and this document does not limit this.

[0150] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A method for managing project delivery, comprising: In response to detecting a processing result of the project, summing up evaluation values ​​corresponding to unsatisfied demand tags in a set of demand tags of the project to obtain a summing result, wherein the unsatisfied demand tags are demand tags in the set of demand tags that are not hit by output tags, the set of demand tags are determined based on project description information provided by a demand provider of the project, and the output tags are determined based on output description information provided by an output provider that provides the processing result; In response to the sum being greater than or equal to a numerical threshold, the processing result is returned to the producer, and the unmet demand tag is provided to the producer.

2. The method according to claim 1, further comprising: In response to receiving the project description information provided by the demand provider, generating a semantic analysis result of the project description information; The set of requirement tags is determined based on the semantic analysis result.

3. The method according to claim 2, wherein: The determining the set of requirement tags based on the semantic analysis result includes: A reference tag corresponding to the semantic analysis result is extracted from a pre-maintained tag knowledge base as the required tag, and the set of required tags is determined.

4. The method according to claim 3, further comprising: Providing the set of requirement tags to the requirement provider; In response to receiving a first label update instruction from the requirement provider for the set of requirement labels, the set of requirement labels is updated based on an instruction of the first label update instruction.

5. The method according to claim 3, further comprising: Providing the set of requirement tags to an acceptor of the project; In response to receiving a second tag update instruction from the acceptor for the set of required tags, the set of required tags is updated based on instructions of the second tag update instruction.

6. The method according to claim 3, further comprising: In response to the current time reaching the periodic update time for the tag knowledge base, the reference tags whose extraction rates are less than the extraction rate threshold in the tag knowledge base are cleared.

7. The method according to claim 1, further comprising: Based on the semantic analysis results of the requirement tags, requirement tags with repeated semantics in the group of requirement tags are deleted, wherein the similarity between the semantic analysis results of the requirement tags with repeated semantics and at least one other requirement tag in the group of requirement tags is greater than or equal to a similarity threshold.

8. The method according to claim 1, further comprising: In response to receiving the output description information provided by the producer, generating a semantic analysis result of the output description information; The output label is determined based on a result of semantic analysis of the output description information.

9. The method according to claim 1, wherein: The requirement tags in the set of requirement tags are correspondingly preset with reference evaluation values, and the adding of evaluation values ​​corresponding to the unsatisfied requirement tags in the set of requirement tags of the project to obtain a summing result includes: The reference evaluation values ​​corresponding to the unsatisfied requirement tags in the set of requirement tags of the project are added to obtain a summed result.

10. The method according to claim 9, further comprising: In response to the requirement provider issuing a reference evaluation value adjustment instruction for a target requirement tag in the group of requirement tags, the reference evaluation value corresponding to the target requirement tag is updated based on the instruction of the reference evaluation value adjustment instruction.

11. The method according to any one of claims 1 to 10, further comprising: In response to the sum being less than the numerical threshold, pushing the processing result to the acceptance party of the project; In response to the acceptance party returning updated feedback information regarding the processing result, determining a feedback tag corresponding to the updated feedback information; In response to the feedback tag being a subtag of a requirement tag in the set of requirement tags, replacing the corresponding requirement tag with the subtag; The demand tags among the set of demand tags obtained after replacement that are not hit by the output tags are provided to the output party.

12. The method according to claim 11, further comprising: In response to the acceptance party returning a receiving instruction for the processing result, requesting the acceptance party to provide a satisfaction evaluation value; In response to the acceptance party returning the satisfaction evaluation value, project evaluation information for the project is generated based on a combination result of the satisfaction evaluation value and a label evaluation value corresponding to the output label.

13. An apparatus for managing project delivery, comprising: an evaluation value adding unit, configured to add evaluation values ​​corresponding to unsatisfied demand tags in a set of demand tags of the project in response to detecting a processing result of the project, to obtain a summed result, wherein the unsatisfied demand tags are demand tags in the set of demand tags that are not hit by output tags, the set of demand tags are determined based on project description information provided by a demand provider of the project, and the output tags are determined based on output description information provided by an output provider that provides the processing result; The result return and label providing unit is configured to return the processing result to the producer in response to the sum result being greater than or equal to a numerical threshold, and provide the unmet demand label to the producer.

14. An electronic device comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method for managing project delivery according to any one of claims 1 to 12.

15. A non-transitory computer-readable storage medium storing computer instructions for causing the computer to execute the method for managing project delivery according to any one of claims 1 to 12.

16. A computer program product, comprising a computer program, which, when executed by a processor, implements the method for managing project delivery according to any one of claims 1 to 12.

Images