Project resource allocation method and device, computer equipment and readable storage medium

Abstract

The invention relates to the technical field of artificial intelligence, and particularly discloses a project resource allocation method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the steps of determining a business type of a to-be-assessed project, calling a target workload assessment model matched with the business type, pre-assessing the workload of the to-be-assessed project, and obtaining a workload pre-assessment result, the business type of the target historical item is the same as that of the to-be-evaluated item, evaluating the workload of the to-be-evaluated item in the execution period of the to-be-evaluated item to obtain a workload evaluation result, and allocating resources to the to-be-evaluated item based on the workload pre-evaluation result and the workload evaluation result to obtain a resource allocation result. By adopting the method, the resource allocation fineness can be improved.

Description

Technical Field

[0001] The present application relates to the field of artificial intelligence technology, and in particular to a project resource allocation method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] With the rapid development of the times, the requirements for refined project management and resource allocation in all walks of life are becoming increasingly higher. However, in the actual implementation of projects, there is often a problem that the total amount of resources is fixed, but the project requirements and workload are vague and difficult to define.

[0003] In traditional project resource management, it is necessary to pay real-time attention to the execution of the project in terms of task content, execution time, execution quality, etc., and then allocate resources to the project based on the execution of the project. However, with the trend of project complexity and the situation where multiple implementers collaborate to execute the project, it is still difficult to determine the real-time and accurate project execution status, and thus it is difficult to accurately allocate resources. It can be seen that the current project resource management solution has the problem of low resource allocation precision. Summary of the invention

[0004] Based on this, it is necessary to provide a project resource allocation method, apparatus, computer equipment, computer-readable storage medium and computer program product that can improve the precision of resource allocation in response to the above technical problems.

[0005] In a first aspect, the present application provides a project resource allocation method, comprising:

[0006] Determine the business type of the project to be evaluated;

[0007] Calling a target workload assessment model that matches the business type, pre-assessing the workload of the project to be assessed, and obtaining a workload pre-assessment result, wherein the target workload assessment model is trained based on the project feature data of the target historical project, and the target historical project has the same business type as the project to be assessed;

[0008] During the execution cycle of the project to be evaluated, evaluating the workload of the project to be evaluated and obtaining a workload evaluation result;

[0009] Based on the workload pre-assessment result and the workload assessment result, resources are allocated to the project to be assessed to obtain a resource allocation result.

[0010] In one embodiment, allocating resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result to obtain a resource allocation result includes:

[0011] Determine the priorities of the items to be evaluated;

[0012] According to the workload conversion coefficient matching the priority, the workload pre-assessment result is converted to obtain the workload of the project to be assessed after conversion;

[0013] Allocate resources to the project to be evaluated according to the converted workload of the project to be evaluated, and determine the resource pre-allocation result;

[0014] According to the workload evaluation result, the resource pre-allocation result is adjusted to determine the resource allocation result.

[0015] In one embodiment, allocating resources to the project to be evaluated according to the converted workload of the project to be evaluated to obtain a resource pre-allocation result includes:

[0016] According to the workload of the project to be evaluated after conversion, the project to be evaluated is divided into multiple sub-projects;

[0017] Taking each of the sub-projects as input, calling a preset resource allocation model to obtain a resource pre-allocation result for each sub-project, wherein the preset resource allocation model is trained based on the historical resource allocation results of the target historical project;

[0018] The resource pre-allocation results of the sub-projects are aggregated to determine the resource pre-allocation result of the project to be evaluated.

[0019] In one embodiment, obtaining the business type of the project to be evaluated includes:

[0020] Obtain the business requirements document for the project to be evaluated;

[0021] Extracting the business characteristics of the project to be evaluated from the business requirement document;

[0022] Based on the business characteristics, the project to be evaluated is classified into business categories to determine the business type of the project to be evaluated.

[0023] In one embodiment, extracting the business characteristics of the project to be evaluated from the business requirement document includes:

[0024] Extracting the business domain, business functions, and business elements of the project to be evaluated from the business requirements document;

[0025] The business characteristics are determined based on the business domain, the business functions, and the business elements.

[0026] In one embodiment, allocating resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result to obtain a resource allocation result includes:

[0027] Based on the workload pre-assessment result and the workload assessment result, resources are allocated to the project to be assessed to obtain the amount of resources, resource type, and resource level allocated to the project to be assessed;

[0028] Determine a resource allocation result according to the amount of resources, resource type, and resource level allocated to the project to be evaluated;

[0029] After allocating resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result, and obtaining the resource allocation result, the method further includes:

[0030] The resource allocation result is structured and displayed according to the resource quantity, the resource type and the resource level.

[0031] In one embodiment, after allocating resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result, and obtaining the resource allocation result, the method further includes:

[0032] When the resource amount is greater than a preset resource amount threshold, a warning message is generated and pushed to the terminal where the resource management personnel log in, and the warning message is used to remind the resource management personnel to adjust the resource allocation result.

[0033] In a second aspect, the present application also provides a project resource allocation device, comprising:

[0034] A business type acquisition module is used to determine the business type of the project to be evaluated;

[0035] A model calling module is used to call a target workload assessment model that matches the business type, pre-assess the workload of the project to be assessed, and obtain a workload pre-assessment result, wherein the target workload assessment model is trained based on the project feature data of the target historical project, and the target historical project has the same business type as the project to be assessed;

[0036] A workload evaluation module, used to evaluate the workload of the project to be evaluated during the execution cycle of the project to be evaluated, and obtain a workload evaluation result;

[0037] The resource allocation module is used to allocate resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result to obtain a resource allocation result.

[0038] In one embodiment, the resource allocation module includes:

[0039] A priority determination unit, used to determine the priority of the project to be evaluated;

[0040] A workload conversion unit, used to convert the workload pre-assessment result according to the workload conversion coefficient matching the priority, to obtain the workload of the project to be assessed after conversion;

[0041] A resource pre-allocation unit, configured to allocate resources to the project to be evaluated according to the converted workload of the project to be evaluated, and determine a resource pre-allocation result;

[0042] The resource adjustment unit is used to adjust the resource pre-allocation result and determine the resource allocation result according to the workload evaluation result.

[0043] In one of the embodiments, the workload conversion unit is specifically used to split the project to be evaluated into multiple sub-projects according to the converted workload of the project to be evaluated, and to call a preset resource allocation model with each sub-project as input to obtain a resource pre-allocation result for each sub-project. The preset resource allocation model is trained based on the historical resource allocation results of the target historical project, and the resource pre-allocation results of each sub-project are aggregated to determine the resource pre-allocation result of the project to be evaluated.

[0044] In one embodiment, the service type acquisition module includes:

[0045] Business requirements acquisition unit, used to obtain business requirements documents for the project to be evaluated;

[0046] A business feature extraction unit, used to extract the business features of the project to be evaluated from the business requirement document;

[0047] The business classification unit is used to classify the project to be evaluated based on the business characteristics and determine the business type of the project to be evaluated.

[0048] In one of the embodiments, the business feature extraction unit is specifically used to extract the business domain, business functions, and business elements of the project to be evaluated from the business requirement document, and determine the business features based on the business domain, the business functions, and the business elements.

[0049] In one embodiment, the resource allocation module includes:

[0050] A resource allocation unit, configured to allocate resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result, and obtain the amount of resources, resource type, and resource level allocated to the project to be evaluated;

[0051] A result determination unit, configured to determine a resource allocation result according to the amount of resources, resource type, and resource level allocated to the project to be evaluated;

[0052] The device also includes:

[0053] The structured display module is used to display the resource allocation result in a structured manner according to the resource quantity, the resource type and the resource level.

[0054] In one embodiment, the device further comprises:

[0055] The resource warning module is used to generate and push a warning message to the terminal logged in by the resource management personnel when the resource amount is greater than a preset resource amount threshold. The warning message is used to remind the resource management personnel to adjust the resource allocation result.

[0056] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps in any one of the above-mentioned project resource allocation method embodiments when executing the computer program.

[0057] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps in any one of the above-mentioned project resource allocation method embodiments are implemented.

[0058] In a fifth aspect, the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps in any one of the above-mentioned project resource allocation method embodiments.

[0059] The above-mentioned project resource allocation method, device, computer equipment, computer-readable storage medium and computer program product are different from the traditional scheme, which requires real-time attention to the execution of the project in terms of task content, execution time, execution quality, etc., and it is difficult to accurately allocate resources. In the scheme of this application, the workload of the project to be evaluated is used as the basis for resource allocation, and in the workload evaluation stage, a two-level evaluation is introduced, a pre-evaluation before the execution of the project to be evaluated, and an evaluation during the execution of the project to be evaluated, so that the workload of the project can be evaluated more comprehensively and accurately, providing an accurate basis for subsequent resource allocation. In addition, in the process of evaluating the workload, a target workload evaluation model that matches the business type of the project to be evaluated is used. The target workload evaluation model is trained based on the project feature data of the target historical project with the same business type as the project to be evaluated. Therefore, for the projects to be evaluated of the same business type, the target workload evaluation model can show better prediction performance, further improving the accuracy of the workload pre-evaluation results. Furthermore, considering that project requirements and workload may change during the execution of the project to be evaluated, the target workload evaluation model can also be used to evaluate the project workload during the execution of the project to be evaluated, so as to obtain more accurate workload evaluation results. Finally, the workload evaluation results and the workload pre-evaluation results are combined as the basis for allocating resources to the project to be evaluated, and the final resource allocation results are determined. This can effectively solve the lag in workload evaluation and the inaccurate workload evaluation of traditional solutions, thereby improving the sophistication of resource allocation. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0061] FIG1 is an application environment diagram of a project resource allocation method in one embodiment;

[0062] Figure 2 A schematic diagram of a process flow of a project resource allocation method in one embodiment;

[0063] Figure 3 A schematic diagram of a flow chart of a project resource allocation method in another embodiment;

[0064] Figure 4 A schematic diagram of a process for determining a resource allocation result in one embodiment;

[0065] Figure 5It is a flowchart of a project resource allocation method in another embodiment;

[0066] Figure 6 A schematic diagram of a process for determining the similarity of business types in one embodiment;

[0067] Figure 7 A schematic diagram of a process flow of a project resource allocation method in another embodiment;

[0068] Figure 8 A schematic diagram of a flow chart of a project resource allocation method in yet another embodiment;

[0069] Fig. 9 A schematic diagram of a process flow of a project resource allocation method in a detailed embodiment;

[0070] Fig.10 It is a structural block diagram of a project resource allocation device in one embodiment;

[0071] Fig.11 It is a structural block diagram of a project resource allocation device in yet another embodiment;

[0072] Fig.12 It is a structural block diagram of a project resource allocation device in another embodiment;

[0073] Fig.13 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0074] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application. It should be noted that in the embodiments of the present application, certain software, groups, models and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0075] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations. The acquisition, storage, use, and processing of data in the technical solution of this application are in compliance with relevant provisions of national laws and regulations.

[0076] The project resource allocation method provided in the embodiment of the present application can be applied in the application environment shown in FIG1 . In which, the terminal 102 communicates with the server 104 through a network. The data storage system can store data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers.

[0077] Specifically, the resource management personnel may upload the business type of the project to be evaluated to the server 104, or the server 104 may obtain the pre-stored business type of the project to be evaluated from the data storage system. Then, the server 104 calls the target workload evaluation model that matches the business type, pre-evaluates the workload of the project to be evaluated, and obtains the workload pre-evaluation result. The target workload evaluation model is trained based on the project feature data of the target historical project, and the target historical project has the same business type as the project to be evaluated. Finally, during the execution cycle of the project to be evaluated, the server 104 evaluates the workload of the project to be evaluated, obtains the workload evaluation result, and then allocates resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result, and obtains the resource allocation result.

[0078] The terminal 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, IoT devices, and portable wearable devices. The IoT devices may be smart speakers, smart TVs, smart air conditioners, smart car devices, projection devices, etc. Portable wearable devices may be smart watches, smart bracelets, head-mounted devices, etc. Head-mounted devices may be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. The server 104 may be an independent physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides cloud computing services.

[0079] In an exemplary embodiment, Figure 2 As shown, a project resource allocation method is provided, which is described by taking the method applied to the server 104 in FIG. 1 as an example, and includes the following steps:

[0080] S100, determining the business type of the project to be evaluated.

[0081] Among them, the project to be evaluated refers to the project that currently needs resource allocation and workload evaluation, and the business type refers to the classification of the project in the business field, such as front-end development, back-end development, database management, etc. in software development. Projects of different business types generally have different workflows and required resources. Business type similarity is a measure of the similarity between the business types of two projects, which can be determined by some similarity algorithms such as cosine similarity, Euclidean distance, etc.

[0082] For example, since projects of different business types have different resource requirements and workloads, the server first needs to obtain the business type of the project to be evaluated, which can be pre-evaluated by experts and stored in the server's database. Further, the server compares the business type of the project to be evaluated with the business types of multiple historical projects, such as using a cosine similarity algorithm to calculate the similarity, and obtains the business relevance of the historical projects used to measure the project to be evaluated. The basis for calculating the similarity includes but is not limited to the functional requirements, technical architecture, and implementation environment of the project.

[0083] S200, calling a target workload assessment model that matches the business type, pre-assessing the workload of the project to be assessed, and obtaining a workload pre-assessment result. The target workload assessment model is trained based on project feature data of a target historical project, and the target historical project has the same business type as the project to be assessed.

[0084] Among them, the target workload assessment model is a model trained based on the project characteristic data of the target historical project, which is used to predict the workload of the project to be assessed. The model architecture of the target workload assessment model can be a linear regression model, a decision tree model, a neural network model, etc. Among them, the project characteristic data includes but is not limited to project scale, project delivery time, project workload, project structure, etc. Pre-assessment refers to a workload estimation conducted before the project officially starts, which is used to provide a preliminary basis for resource allocation for the project to be assessed. The workload pre-assessment process includes but is not limited to activities such as demand analysis, solution design, development, testing, and production of the project to be assessed, which can be expressed in man-months.

[0085] Exemplarily, the server calls the target workload assessment model trained based on the target historical project to perform a preliminary assessment of the project to be assessed. Since the model is trained based on the workload data of the target historical project and utilizes the historical experience of projects with similar business types, it can more accurately predict the workload of the project to be assessed and obtain a workload preliminary assessment result.

[0086] In addition, when the business type of the project to be evaluated does not match the business type of the historical project in the server database, that is, the project to be evaluated is a newly added project, the similarity between the project to be evaluated and the historical project in the dimension of business type can still be calculated, and the historical project with the highest similarity can be determined as the target historical project, thereby correspondingly retrieving the target workload evaluation model that matches the business type of the target historical project. Exemplarily, assuming that the business type of the project to be evaluated is front-end development, through the above steps of calculating the similarity of business types and screening target historical projects, a historical project that is most similar to the business type of the project to be evaluated is finally screened out, such as another front-end development project. Even if there is no project with a business type of front-end development project in the historical project, a historical project that is most similar to the business type of the project to be evaluated can still be screened out, such as a back-end development project. In this way, even if the project to be evaluated is a project of a newly added business type compared to the historical project, the target historical project with the most relevant business type can be quickly screened out as a reference for workload evaluation and resource allocation.

[0087] S300, evaluating the workload of the project to be evaluated within the execution cycle of the project to be evaluated, and obtaining a workload evaluation result.

[0088] The execution cycle refers to the phased execution time of the project to be evaluated after the formal execution of the project to be evaluated. For example, the execution cycle can be one week, one month, etc. Similar to the above pre-evaluation, during the execution cycle of the project to be evaluated, the technology of the neural network model can also be used to evaluate the workload of the project to be evaluated.

[0089] For example, one month after the project to be evaluated is implemented, the workload of the project to be evaluated can be evaluated again based on the execution of the project to be evaluated within this month and the neural network model. Alternatively, the party proposing the requirements, the project leader, and the implementer can send an expert group to evaluate the workload of the project to be evaluated and obtain the workload evaluation result. This is because the pre-evaluation stage is time-sensitive, but as the project to be evaluated progresses, the workload may change. Therefore, during the execution cycle of the project to be evaluated, the workload of the project to be evaluated is evaluated again, and the workload evaluation result obtained is more accurate than the workload pre-evaluation result.

[0090] S400, allocating resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result to obtain a resource allocation result.

[0091] Among them, the resources in this embodiment include but are not limited to funds, human resources, equipment resources, time resources, etc., and the resource allocation results include but are not limited to the financial budget, manpower, and equipment issued to the project to be evaluated, as well as the proportion of resources allocated to multiple sub-projects in the project to be evaluated.

[0092] Exemplarily, based on the workload pre-assessment results and the workload assessment results, the timeliness of the workload pre-assessment results and the accuracy of the workload assessment results can be considered at the same time, so as to more accurately allocate resources to the project to be assessed, and the methods of allocating resources include but are not limited to expert evaluation, neural network models, etc. It should be noted that in the process of allocating resources, taking human resources as an example, the following principles need to be met: the allocation of various types of human resources does not exceed the resource budget, simple tasks are not allocated or low-end resources (experts, senior employees, etc.) are allocated, etc., and the call for self-owned human resources and third-party human resources does not exceed the corresponding human resources budget.

[0093] Furthermore, after obtaining the resource allocation results, the resource allocation results need to be reviewed, for example, the project leader and the project implementer need to confirm, and after no objection, the project leader can initiate a review request to the project demander. The review of resource allocation results includes reviewing the evaluation results of the workload and reviewing the resource allocation results. The evaluation results of the workload include but are not limited to: whether the workload is within the implementation scope of the project, whether the workload exceeds the standard, and whether the collaborative implementers and subsystems are complete; the review of resource allocation results includes but is not limited to: whether the total resource budget is within the implementation scope of the project, whether the total resource budget is reasonable (for example, when the project is about to end, third-party resources should not be purchased), whether the human resources at all levels exceed the standard, etc. If all the above reviews are passed, the resource allocation results are executed, that is, according to the resource allocation results, resources are issued to the relevant implementers of the project to be evaluated. At the same time, hierarchical resource allocation information is required, and the use of resources is supervised and inspected during the execution of the project to be evaluated.

[0094] The above-mentioned project resource allocation method is different from the traditional solution, which requires real-time attention to the execution of the project in terms of task content, execution time, execution quality, etc., and it is difficult to accurately allocate resources. In the present application scheme, the workload of the project to be evaluated is used as the basis for resource allocation, and in the workload evaluation stage, a two-level evaluation is introduced, a pre-evaluation before the execution of the project to be evaluated, and an evaluation during the execution of the project to be evaluated. In this way, the workload of the project can be evaluated more comprehensively and accurately, providing an accurate basis for subsequent resource allocation. In addition, in the process of evaluating the workload, a target workload evaluation model that matches the business type of the project to be evaluated is used. The target workload evaluation model is trained based on the project feature data of the target historical project with the same business type as the project to be evaluated. Therefore, for the projects to be evaluated of the same business type, the target workload evaluation model can show better prediction performance, further improving the accuracy of the workload pre-evaluation results. Furthermore, considering that project requirements and workload may change during the execution of the project to be evaluated, the target workload evaluation model can also be used to evaluate the project workload during the execution of the project to be evaluated, so as to obtain more accurate workload evaluation results. Finally, the workload evaluation results and the workload pre-evaluation results are combined as the basis for allocating resources to the project to be evaluated, and the final resource allocation results are determined. This can effectively solve the lag in workload evaluation and the inaccurate workload evaluation of traditional solutions, thereby improving the sophistication of resource allocation.

[0095] In an exemplary embodiment, Figure 3 As shown, S400 can be further divided into the following sub-steps, each of which plays an important role in the resource allocation process, including determining the priority of the project to be evaluated, workload conversion processing, and pre-allocation and adjustment of resources. Specifically, S400 includes:

[0096] S410, determining the priority of the project to be evaluated, and converting the workload pre-evaluation result according to the workload conversion coefficient matching the priority to obtain the converted workload of the project to be evaluated.

[0097] S420, allocating resources to the project to be evaluated according to the converted workload of the project to be evaluated, and determining a resource pre-allocation result.

[0098] S430: According to the workload evaluation result, adjust the resource pre-allocation result and determine the resource allocation result.

[0099] Among them, the priority of the project to be evaluated is used to characterize the importance or urgency of the project. It can be divided into high, medium, low and other levels according to factors such as corporate strategic goals, market demand, and customer requirements. The workload conversion coefficient is a coefficient pre-set according to the project priority, which is used to adjust the workload pre-evaluation results. The coefficient is between 0 and 1. The higher the priority, the closer the coefficient is to 1. The types and quantities of resources can include human resources (developers, project managers, testers of different levels, etc.), physical resources (hardware equipment, network bandwidth, etc.), and time resources (working hours within the project cycle). The workload evaluation result refers to the actual total workload of the project obtained through real-time monitoring and evaluation during the project execution. Unlike the workload pre-evaluation result, the workload evaluation result is usually more accurate.

[0100] Exemplarily, the server first needs to determine the priority of the project to be evaluated. The priority of the project to be evaluated determines the relative importance of the project in resource allocation. For projects with higher priorities, more resources should be allocated to reduce the risk of projects being difficult to advance due to insufficient resources, while projects with lower priorities receive fewer resource allocations, thereby reducing the risk of other projects with higher priorities receiving insufficient resources. Then, the server calls the workload conversion coefficient that matches the priority based on the priority of the project to be evaluated, and adjusts the workload pre-evaluation result obtained previously. For example, the workload pre-evaluation result of a project to be evaluated is 100 people / day, and the project priority is medium. The workload conversion coefficient set by the server for medium priority is 0.8, then after conversion, the workload obtained is 80 people / day.

[0101] It should be noted that the workload conversion coefficient in this embodiment can be set in a variety of ways, including but not limited to: pre-setting a fixed workload conversion coefficient, for example, the workload conversion coefficient of a high-priority project is 1.0, the workload conversion coefficient of a medium-priority project is 0.8, and the workload conversion coefficient of a low-priority project is 0.6; it can also be combined with other factors (such as project complexity, available resources) in addition to priority to perform a more detailed conversion processing on the workload pre-assessment results.

[0102] Furthermore, after determining the workload of the project to be evaluated after conversion, the server allocates corresponding resources to the project to be evaluated based on the converted workload pre-evaluation result, and generates a resource pre-allocation result. The resource pre-allocation result includes but is not limited to: pre-allocating more senior resources (such as project experts) for complex tasks; if multiple projects to be evaluated are executed at the same time, resource sharing issues need to be considered when pre-allocating resources, so that the resources of high-priority projects are not occupied by low-priority projects, etc. During the execution of the project to be evaluated, the server continuously monitors and evaluates the workload of the project to obtain a workload evaluation result. When there is a difference between the workload evaluation result and the workload pre-evaluation result, the server adjusts the resource pre-allocation result according to the actual situation. For example, if the workload evaluation result is greater than the converted workload pre-evaluation result, the resource input should be increased on the basis of the resource pre-allocation result to obtain a resource allocation result.

[0103] In this embodiment, through priority, workload conversion coefficient, resource pre-allocation and dynamic adjustment of resource pre-allocation results, a preliminary resource allocation plan can be determined before the execution of the project to be evaluated, and the resource allocation plan can be optimized during the actual execution of the project to be evaluated, thereby determining a more flexible, efficient and sophisticated resource allocation plan for the project to be evaluated.

[0104] In accordance with the above embodiment, in the process of determining the resource allocation result based on the workload, the project to be evaluated can be divided into multiple sub-projects, and resources can be pre-allocated for each sub-project, so as to finally obtain the resource pre-allocation result of the entire project to be evaluated. This method can improve the accuracy of resource allocation. Figure 4 As shown, S420 includes:

[0105] S421, split the project to be evaluated into multiple sub-projects according to the converted workload of the project to be evaluated.

[0106] S422, taking each sub-project as input, calling a preset resource allocation model to obtain a resource pre-allocation result for each sub-project.

[0107] S423, collecting resource pre-allocation results of each sub-project, and determining the resource pre-allocation result of the project to be evaluated.

[0108] Among them, a subproject is a smaller, independent work unit obtained by splitting a larger project. The project to be evaluated can be split into multiple subprojects based on work modules, functional parts or time stages. The resource allocation model is a model used to allocate resources based on project requirements, workload and historical experience. The preset resource allocation model is trained based on the historical resource allocation results of the target historical project.

[0109] Exemplarily, the server splits the project to be evaluated according to its converted workload to generate multiple sub-projects. The basis for the split can be the phased work of the project, different functional modules, or divided into multiple smaller manageable units according to the team's work content. For example, in a development project, interface development, function development and testing can be independent sub-projects. Then, for each sub-project, a preset resource allocation model is called. Since the resource allocation model is trained based on the resource allocation results of multiple historical projects, by learning the historical resource allocation results of similar historical projects, the preset resource allocation model can automatically identify the resource requirements of the current sub-project, and finally obtain the resource pre-allocation results of each sub-project. It should be noted that the training data of the resource allocation model can contain information of multiple dimensions, such as workload, project type, project implementation time, project complexity, etc. Based on multi-dimensional historical data training, the resource allocation model obtained can more accurately allocate appropriate resources to sub-projects.

[0110] Finally, the resource allocation results of each sub-project are summarized to form the resource pre-allocation results of the entire project to be evaluated. It should be noted that the aggregation process is not just a simple addition of the number of resources, but also needs to consider the mutual influence between sub-projects. For example, some resources (such as servers, network bandwidth) may be shared among multiple sub-projects, and servers need to avoid repeated allocation. Similarly, some senior human resources (such as experts or project managers) may need to be scheduled across multiple sub-projects. When aggregating the resource allocation results of each sub-project, the above situations also need to be taken into consideration.

[0111] In this embodiment, by splitting a larger project to be evaluated into multiple sub-projects, complex projects are easier to manage, the efficiency of resource allocation can be improved, and by calling a preset resource allocation model, resources can be accurately allocated to each sub-project. In addition, since the resource allocation model is trained based on historical data, its allocation results can better fit the actual project needs, reducing the risk of insufficient or over-allocation of resources. Finally, the resource pre-allocation results of each sub-project are aggregated, making resource allocation more comprehensive and systematic, and the aggregated resource pre-allocation results are also more reasonable and accurate.

[0112] Following the above embodiment, determining the business type of the project to be evaluated is the basis of the entire project evaluation process. In an exemplary embodiment, Figure 5 As shown, S100 includes:

[0113] S110, obtaining a business requirement document of the project to be evaluated, and extracting business features of the project to be evaluated from the business requirement document.

[0114] S120, classifying the project to be evaluated based on the business characteristics, and determining the business type of the project to be evaluated.

[0115] Among them, the business requirements document is a document provided by the customer or business party at the beginning of the project to be evaluated, which describes in detail the project's goals, requirements, functions, limitations, etc. Business characteristics are key information extracted from the business requirements document that can describe the characteristics of the project. Business characteristics include but are not limited to the project's scale, functional modules, technical requirements, time nodes, etc. Business type indicates the business category to which the project to be evaluated belongs. For example, the project to be evaluated can be classified into different business types such as "software development", "hardware deployment", and "data analysis".

[0116] Exemplarily, the server first needs to obtain the core information of the project to be evaluated from the business requirement document. Specifically, the server can parse the business requirement document through natural language processing technology, including but not limited to keyword extraction, semantic analysis and other steps, and extract the business characteristics related to the workload of the evaluation project from the business requirement document. The business characteristics include but are not limited to the functional modules, project scale, delivery time, technical requirements and industry background mentioned in the business requirement document. For example, suppose the business requirement document of a project to be evaluated describes the development of a customer relationship management system. The business requirement document mentions information such as "needs to be delivered within 3 months" and "supports 1,000 users at the same time". The above information is extracted and parsed through natural language processing technology to obtain the business characteristics of the project to be evaluated.

[0117] Then, the server classifies the items to be evaluated based on the extracted business features. The classification process can be matched based on an existing business type library, or it can be classified through a machine learning model to obtain the business type of the item to be evaluated.

[0118] In this embodiment, by extracting business features from the business requirement document, the project requirements and project characteristics of the project to be evaluated can be quickly identified. The extracted business features provide basic data for subsequent business classification. The business type determined after the project to be evaluated is classified can quickly find historical projects similar to the project to be evaluated, thereby providing a basis for subsequent workload prediction and improving the efficiency and accuracy of workload evaluation.

[0119] Following the above embodiment, by parsing the business requirement document and extracting the key information of the project, it can be converted into business features that can be used for evaluation and classification. In an exemplary embodiment, Figure 6 As shown, S110 includes:

[0120] S111, obtaining a business requirement document of the project to be evaluated, and extracting the business domain, business functions, and business elements of the project to be evaluated from the business requirement document.

[0121] S112, determining business characteristics based on the business domain, business functions, and business elements.

[0122] Among them, the business field refers to the industry or application field to which the project belongs. For example, the project may belong to different fields such as "finance", "medical care", "manufacturing", etc. Business functions refer to the core functional modules that the project needs to implement, which may include specific functional requirements. For example, a financial management system may include business functions such as "budget management", "report generation", and "financial accounting". Business elements are more fine-grained business features, which may include key requirements, user scenarios, constraints, etc. of the project, such as project delivery time, the maximum number of users that can be supported at the same time, etc.

[0123] Exemplarily, the server first extracts three key dimensions of information related to the project from the business requirements document: business domain, business function and business element. Each dimension of information has different impacts on the overall evaluation of the project. For example, the business domain represents the industry background of the project, the business function represents the realization goal of the project, and the business element represents the operation requirements of the project. For example, assuming that the project to be evaluated is an electronic medical record system for the medical industry, the business requirements document clearly states that the system needs to support doctors to fill in patient information, generate diagnosis and treatment reports, manage medical record data and other functions, and the system needs to support concurrent operations of more than 500 patients per day. Through natural language processing technology, the server can extract keywords such as "electronic medical records", "medical care", "fill in patient information", "generate diagnosis and treatment reports" from the business requirements document, thereby further determining that the business domain is the medical field, the business functions include medical record management, diagnosis and treatment report generation, etc., and the business element information includes that the system needs to support concurrent operations of more than 500 patients per day. Finally, the server combines the extracted business domain, business functions and business elements to generate business features that can be used for evaluation.

[0124] In this embodiment, by extracting business areas, business functions and business elements from the business requirements document, the extracted information will provide a basis for the subsequent determination of business characteristics, business type classification and similarity calculation, thereby improving the efficiency of business feature extraction of the project to be evaluated, and ultimately generating the business characteristics of the project, providing support for subsequent workload prediction and resource allocation, and improving the accuracy of workload evaluation and resource allocation.

[0125] Following the above embodiment, after determining the resource allocation result, it is also necessary to perform statistics and analysis on the entire workload assessment and resource allocation process, and display the resource allocation result in a structured manner. In an exemplary embodiment, Figure 7 As shown, S400 includes:

[0126] S440, allocating resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result, and obtaining the resource quantity, resource type, and resource level allocated to the project to be evaluated.

[0127] S450: Determine a resource allocation result according to the amount of resources, resource types, and resource levels allocated to the project to be evaluated.

[0128] After S400, the method further includes:

[0129] S500, displaying the resource allocation result in a structured manner according to the resource quantity, resource type and resource level.

[0130] Among them, the resource quantity refers to the specific number of resources allocated to the project to be evaluated, such as manpower, equipment, funds, etc. Resource types refer to the different types of resources required for the project to be evaluated, including but not limited to human resources, equipment resources, and time resources, among which human resources can be further divided into developers, testers, project managers, etc. Resource level refers to the level of skills, experience or qualifications of the resources allocated to the project to be evaluated. For example, human resources include senior developers, mid-level developers, etc. The resource allocation results include but are not limited to the number and type of resources allocated to the project to be evaluated, as well as the level of each resource. Structured presentation refers to presenting complex data in an organized and easy-to-read manner, such as in the form of tables, charts, etc.

[0131] Exemplarily, the server comprehensively analyzes the workload pre-assessment results and the actual workload assessment results, allocates resources to the project to be assessed, and determines the amount of resources, resource type, and resource level allocated to the project to be assessed. This process can be implemented through a resource pool. Specifically, a resource pool management system is pre-stored in the server. The resource pool includes various types of resources that can be allocated, as well as the current status of each type of resource (idle or occupied). Through the resource pool management system, the server can efficiently allocate resources to the project to be assessed.

[0132] Further, after the above resource allocation process, the server can determine the resource type, resource level and resource quantity allocated to the project to be evaluated, such as whether the project to be evaluated requires developers, testers, test equipment, etc., as well as the specific number of developers and testers required, whether some sub-projects need to be completed by senior developers, and whether some sub-projects only need to be completed by junior developers. Finally, during the execution of the project to be evaluated or after the execution is completed, the resource quantity, resource type and resource level allocated to the project to be evaluated are presented in a table or graphical form. Taking the table as an example, the server displays the quantity, type and level of each resource in a table, which is convenient for resource managers to view and check. In addition, the server can also display the usage of resources through charts or other visualization tools. For example, a pie chart of resource allocation can show the proportion of different resources, and a bar chart can show the specific number of different resource types. It should be noted that the above structured display can be dynamic, allowing resource managers to update the resource allocation and usage in real time according to the execution progress of the project to be evaluated, and whether during or after the project execution, resource managers can quickly query the relevant resource allocation through the results of the structured display by entering keywords (such as implementers, resource types, resource levels, etc.).

[0133] In this embodiment, based on the structured display of resource allocation results, resource management personnel can quickly understand the amount of resources, resource types, and resource levels allocated to the project to be evaluated, which not only improves the efficiency of project management, but also provides a data basis for subsequent review and query of resource allocation.

[0134] During the execution of the project to be evaluated, the resource allocation result obtained by the server analysis may not meet the actual situation, or the actual resource budget may be difficult to meet the resource allocation result. Figure 8 As shown, after S400, the method further includes:

[0135] S600, when the resource amount is greater than a preset resource amount threshold, generate and push a warning message to a terminal logged in by a resource management personnel, the warning message is used to remind the resource management personnel to adjust the resource allocation result.

[0136] The resource quantity threshold is a preset maximum limit of the resource quantity. For example, before the project is executed, the project leader or the project demander will pre-set a maximum resource quantity as the resource quantity threshold.

[0137] Exemplarily, during the resource allocation process, the server introduces an alarm mechanism to monitor in real time whether the amount of resources exceeds the standard. Specifically, during the resource allocation process, the server will monitor the allocation and usage of each type of resources in real time, determine the amount of resources of each type, and compare it with the pre-set resource threshold. When it is detected that the amount of resources exceeds the resource threshold, it means that the project to be evaluated may face the problem of over-allocation of resources, thereby triggering the warning mechanism. The server will automatically generate a warning message and push the warning message to the terminal where the resource manager logs in. Among them, the warning message can also include specific information that exceeds the resource threshold, such as "the number of developers exceeds the preset upper limit by 10%", "the allocation of equipment resources has exceeded the maximum available limit", etc. After the resource manager receives the warning message, the resource manager needs to evaluate the current resource allocation situation and make appropriate adjustments according to actual needs.

[0138] In addition, different levels of warning mechanisms can be set up in the server. For example, when the resource amount is close to the resource threshold, the server automatically sends an early warning message to the resource management personnel's terminal to remind the resource management personnel to pay attention to adjusting subsequent resource allocation. When the resource amount exceeds the resource threshold, the server will send a warning message to remind the resource management personnel to adjust the resource allocation results.

[0139] In this embodiment, by real-time monitoring and early warning of the resource amount of the project to be evaluated, when the resource amount exceeds the resource amount threshold, the warning message can promptly notify the resource management personnel to adjust the resource allocation result, thereby improving the efficiency of resource management.

[0140] In order to make a clearer description of the project resource allocation method provided by the present application, the following is a specific embodiment and the attached Fig. 9 To illustrate, this specific embodiment includes the following steps:

[0141] S901, obtaining a business requirement document of the project to be evaluated, extracting the business domain, business function, and business elements of the project to be evaluated from the business requirement document, classifying the project to be evaluated, and determining the business type of the project to be evaluated.

[0142] S902, calling a target workload assessment model that matches the business type, pre-assessing the workload of the project to be assessed, and obtaining a workload pre-assessment result.

[0143] S903, during the execution cycle of the project to be evaluated, evaluating the workload of the project to be evaluated and obtaining a workload evaluation result.

[0144] S904, allocating resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result, and obtaining the resource quantity, resource type, and resource level allocated to the project to be evaluated.

[0145] S905, determining a resource allocation result according to the amount of resources, resource type, and resource level allocated to the project to be evaluated, and performing a structured display of the resource allocation result.

[0146] S906: When the resource amount is greater than a preset resource amount threshold, generate and push a warning message to the terminal where the resource management personnel log in.

[0147] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0148] Based on the same inventive concept, the embodiment of the present application also provides a project resource allocation device for implementing the project resource allocation method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more project resource allocation device embodiments provided below can refer to the limitations of the project resource allocation method above, and will not be repeated here.

[0149] In an exemplary embodiment, Fig.10 As shown, a project resource allocation device 100 is provided, comprising: a business type acquisition module 110, a model calling module 120, a workload evaluation module 130 and a resource allocation module 130, wherein:

[0150] The business type acquisition module 110 is used to determine the business type of the project to be evaluated.

[0151] The model calling module 120 is used to call the target workload assessment model that matches the business type, pre-assess the workload of the project to be assessed, and obtain the workload pre-assessment result. The target workload assessment model is trained based on the project feature data of the target historical project, and the target historical project has the same business type as the project to be assessed.

[0152] The workload evaluation module 130 is used to evaluate the workload of the project to be evaluated within the execution cycle of the project to be evaluated and obtain a workload evaluation result.

[0153] The resource allocation module 140 is used to allocate resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result to obtain a resource allocation result.

[0154] In one embodiment, Fig.11 As shown, the resource allocation module 140 includes: a priority determination unit 141, a workload conversion unit 142, a resource pre-allocation unit 143 and a resource adjustment unit 144, wherein the priority determination unit 141 is used to determine the priority of the project to be evaluated; the workload conversion unit 142 is used to convert the workload pre-evaluation result according to the workload conversion coefficient matching the priority, and obtain the workload of the project to be evaluated after conversion; the resource pre-allocation unit 143 is used to allocate resources to the project to be evaluated according to the workload of the project to be evaluated after conversion, and determine the resource pre-allocation result; the resource adjustment unit 144 is used to adjust the resource pre-allocation result according to the workload evaluation result, and determine the resource allocation result.

[0155] In one embodiment, the workload conversion unit 142 is specifically used to split the project to be evaluated into multiple sub-projects according to the converted workload of the project to be evaluated, and to call a preset resource allocation model with each sub-project as input to obtain the resource pre-allocation result of each sub-project. The preset resource allocation model is trained based on the historical resource allocation results of the target historical project, and the resource pre-allocation results of each sub-project are aggregated to determine the resource pre-allocation result of the project to be evaluated.

[0156] In one embodiment, Fig.11 As shown, the business type acquisition module 110 includes: a business requirement acquisition unit 111, a business feature extraction unit 112 and a business classification unit 113; the business requirement acquisition unit 111 is used to obtain the business requirement document of the project to be evaluated; the business feature extraction unit 112 is used to extract the business features of the project to be evaluated from the business requirement document; the business classification unit 113 is used to classify the project to be evaluated based on the business features and determine the business type of the project to be evaluated.

[0157] In one embodiment, the business feature extraction unit 112 is specifically used to extract the business domain, business function, and business elements of the project to be evaluated from the business requirement document, and determine the business features based on the business domain, business function, and business elements.

[0158] In one embodiment, Fig.12As shown, the resource allocation module 140 includes: a resource allocation unit 145 and a result determination unit 146. The resource allocation unit 145 is used to allocate resources to the project to be evaluated based on the workload pre-assessment result and the workload assessment result, and obtain the resource amount, resource type, and resource level allocated to the project to be evaluated; the result determination unit 146 is used to determine the resource allocation result according to the resource amount, resource type, and resource level allocated to the project to be evaluated. The project resource allocation device 100 also includes a structured display module 150, which is used to perform a structured display of the resource allocation result according to the resource amount, resource type, and resource level.

[0159] In one embodiment, Fig.12 As shown, the project resource allocation device 100 also includes a resource warning module 160, which is used to generate and push a warning message to the terminal logged in by the resource management personnel when the resource amount is greater than a preset resource amount threshold. The warning message is used to remind the resource management personnel to adjust the resource allocation result.

[0160] Each module in the above-mentioned project resource allocation device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0161] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Fig.13 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data such as business types. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a project resource allocation method is implemented.

[0162] Those skilled in the art will understand that Fig.13The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0163] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the steps in any one of the above-mentioned project resource allocation method embodiments are implemented.

[0164] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in any one of the above-mentioned project resource allocation method embodiments are implemented.

[0165] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in any one of the above project resource allocation method embodiments when executed by a processor.

[0166] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0167] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0168] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A project resource allocation method, characterized in that: The method comprises: Determine the business type of the project to be evaluated; Calling a target workload assessment model that matches the business type, pre-assessing the workload of the project to be assessed, and obtaining a workload pre-assessment result, wherein the target workload assessment model is trained based on the project feature data of the target historical project, and the target historical project has the same business type as the project to be assessed; During the execution cycle of the project to be evaluated, evaluating the workload of the project to be evaluated and obtaining a workload evaluation result; Based on the workload pre-assessment result and the workload assessment result, resources are allocated to the project to be assessed to obtain a resource allocation result.

2. The method according to claim 1, characterized in that The allocating resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result to obtain a resource allocation result includes: Determine the priorities of the items to be evaluated; According to the workload conversion coefficient matching the priority, the workload pre-assessment result is converted to obtain the converted workload of the project to be assessed; Allocate resources to the project to be evaluated according to the converted workload of the project to be evaluated, and determine a resource pre-allocation result; According to the workload evaluation result, the resource pre-allocation result is adjusted to determine the resource allocation result.

3. The method according to claim 2, characterized in that The step of allocating resources to the project to be evaluated according to the converted workload of the project to be evaluated to obtain a resource pre-allocation result includes: According to the workload of the project to be evaluated after conversion, the project to be evaluated is divided into multiple sub-projects; Taking each of the sub-projects as input, calling a preset resource allocation model to obtain a resource pre-allocation result for each sub-project, wherein the preset resource allocation model is trained based on the historical resource allocation results of the target historical project; The resource pre-allocation results of the sub-projects are aggregated to determine the resource pre-allocation result of the project to be evaluated.

4. The method according to claim 1, characterized in that: Determining the business type of the project to be evaluated includes: Obtain the business requirements document for the project to be evaluated; Extracting the business characteristics of the project to be evaluated from the business requirement document; Based on the business characteristics, the project to be evaluated is classified into business categories to determine the business type of the project to be evaluated.

5. The method according to claim 4, characterized in that Extracting the business characteristics of the project to be evaluated from the business requirement document includes: Extracting the business domain, business functions, and business elements of the project to be evaluated from the business requirements document; The business characteristics are determined based on the business domain, the business functions, and the business elements.

6. The method according to any one of claims 1 to 5, characterized in that: The allocating resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result to obtain a resource allocation result includes: Based on the workload pre-assessment result and the workload assessment result, resources are allocated to the project to be assessed to obtain the amount of resources, resource type, and resource level allocated to the project to be assessed; Determine a resource allocation result according to the amount of resources, resource type, and resource level allocated to the project to be evaluated; After allocating resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result, and obtaining the resource allocation result, the method further includes: The resource allocation result is structured and displayed according to the resource quantity, the resource type and the resource level.

7. The method according to claim 6, characterized in that After allocating resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result, and obtaining the resource allocation result, the method further includes: When the resource amount is greater than a preset resource amount threshold, a warning message is generated and pushed to the terminal where the resource management personnel log in, and the warning message is used to remind the resource management personnel to adjust the resource allocation result.

8. A project resource allocation device, characterized in that: The device comprises: A business type acquisition module is used to determine the business type of the project to be evaluated; A model calling module is used to call a target workload assessment model that matches the business type, pre-assess the workload of the project to be assessed, and obtain a workload pre-assessment result, wherein the target workload assessment model is trained based on the project feature data of the target historical project, and the target historical project has the same business type as the project to be assessed; A workload evaluation module, used to evaluate the workload of the project to be evaluated during the execution cycle of the project to be evaluated, and obtain a workload evaluation result; The resource allocation module is used to allocate resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result to obtain a resource allocation result.

9. The device according to claim 8, characterized in that The resource allocation module comprises: A priority determination unit, used to determine the priority of the project to be evaluated; A workload conversion unit, used to convert the workload pre-assessment result according to the workload conversion coefficient matching the priority, to obtain the workload of the project to be assessed after conversion; A resource pre-allocation unit, configured to allocate resources to the project to be evaluated according to the converted workload of the project to be evaluated, and determine a resource pre-allocation result; The resource adjustment unit is used to adjust the resource pre-allocation result and determine the resource allocation result according to the workload evaluation result.

10. The device according to claim 9, characterized in that The workload conversion unit is specifically used to split the project to be evaluated into multiple sub-projects according to the converted workload of the project to be evaluated, and to call a preset resource allocation model with each sub-project as input to obtain a resource pre-allocation result for each sub-project. The preset resource allocation model is trained based on the historical resource allocation results of the target historical project, and the resource pre-allocation results of each sub-project are aggregated to determine the resource pre-allocation result of the project to be evaluated.

11. The device according to claim 8, characterized in that The business type acquisition module includes: Business requirements acquisition unit, used to obtain business requirements documents for the project to be evaluated; A business feature extraction unit, used to extract the business features of the project to be evaluated from the business requirement document; The business classification unit is used to classify the project to be evaluated based on the business characteristics and determine the business type of the project to be evaluated.

12. The device according to claim 11, characterized in that The business feature extraction unit is specifically used to extract the business domain, business function, and business elements of the project to be evaluated from the business requirement document, and determine the business features based on the business domain, the business function, and the business elements.

13. The device according to any one of claims 8 to 12, characterized in that The resource allocation module comprises: A resource allocation unit, configured to allocate resources to the project to be evaluated based on the workload pre-evaluation result and the workload evaluation result, and obtain the amount of resources, resource type, and resource level allocated to the project to be evaluated; A result determination unit, configured to determine a resource allocation result according to the amount of resources, resource type, and resource level allocated to the project to be evaluated; The device also includes: The structured display module is used to display the resource allocation result in a structured manner according to the resource quantity, the resource type and the resource level.

14. The device according to claim 13, characterized in that The device also includes: The resource warning module is used to generate and push a warning message to the terminal logged in by the resource management personnel when the resource amount is greater than a preset resource amount threshold. The warning message is used to remind the resource management personnel to adjust the resource allocation result.

15. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

16. A computer-readable storage medium having a computer program stored thereon, 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 7 are implemented.

17. 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 7 are implemented.

Images