Collaborative design-oriented multi-role task issuing method and platform

Abstract

The invention discloses a collaborative design-oriented multi-role task issuing method and platform, and belongs to the field of project management.The collaborative design-oriented multi-role task issuing method comprises the following steps of: constructing a structured template library, presetting different templates for different project types, the template definitely defines roles related to a project and a standard responsibility range, and an applicable template is automatically recommended based on project keywords; the method comprises the steps that a project target is divided into a plurality of tasks after a template is selected, each task is associated with a selected role, and input conditions, output results, time limits and responsible parties required by the tasks are determined. And input conditions, output results, time limitation and responsible parties required by the tasks are defined, and project files of the whole process are recorded, so that rapid increase of management and coordination cost is effectively reduced, and efficiency loss is remarkably avoided.

Description

Technical Field

[0001] This invention belongs to the field of project management, and in particular relates to a multi-role task assignment method and platform for collaborative design. Background Technology

[0002] In the modern economy, the need for multi-role, cross-disciplinary collaboration to complete work is becoming increasingly common. Examples include the construction industry, film production, software development, automobile manufacturing, and advertising planning. The core characteristic of this type of work is that a single-role expert cannot complete the task independently. It requires clear division of labor, frequent communication, and close collaboration to integrate their respective professional knowledge into a complete and complex final product.

[0003] This collaborative model, with its clear division of labor, frequent communication, and close collaboration, while ensuring quality, may also lead to significant efficiency losses due to a sharp increase in management and coordination costs, thus requiring improvement. Summary of the Invention

[0004] Therefore, it is necessary to provide a multi-role task assignment method and platform for collaborative design to address the above-mentioned problems.

[0005] The present invention is implemented as follows: a multi-role task assignment method for collaborative design includes the following steps: Build a structured template library with different templates for different project types (such as architecture, software development, etc.). The templates clearly define the roles and standard responsibilities involved in the project and automatically recommend applicable templates based on project keywords (project initiators can select matching templates according to project goals). After selecting a template, the project goal is broken down into multiple tasks. Each task is associated with a selected role (selected by the project initiator, and the platform can also make recommendations). The required input conditions, output results, time limits, and responsible parties for each task are clearly defined. If the project initiator modifies the input conditions, output results, or responsible parties for a task, the changes must be confirmed and agreed upon by the responsible party before they take effect. Track task progress in real time and automatically detect abnormal situations (such as an input condition not being provided within a set time) through preset rules. If an abnormal situation occurs, send a reminder to the person responsible for the task via push notification or email to ensure that the problem can be detected and responded to in a timely manner. If any faults or defects are found in the deliverables after the project is completed, the entire project archive is retrieved. The project archive includes task execution records, communication logs between roles, and task responsibility allocation data. Based on the project archive, the responsibility for the problematic stage is traced, and a responsibility analysis report is generated to provide a basis for subsequent processing.

[0006] In one embodiment, the present invention provides a multi-role task assignment method for collaborative design, further comprising: Accumulate and store information on technical personnel who have participated in past projects, classify and archive them by professional field, and build an expert database; when a project requires technical personnel in a specific field to participate in judging the quality of task completion during the acceptance or post-review stage, the system will automatically recommend matching technical personnel based on the field type to support professional review needs.

[0007] In one embodiment, the present invention provides a multi-role task assignment method for collaborative design, further comprising: When unexpected problems arise during project execution (such as derivative problems caused by task errors, or encountering "no-man's-land" ambiguities not defined by the initial template), one or more relevant technical personnel (or multiple personnel if cross-domain issues) are recommended from the expert database based on the specific technical field of the problem. After the project initiator confirms the identity of the responsible party on the platform, the responsible party is granted temporary permissions to define the solution, required resources, and acceptance criteria for the problem, thereby creating a new task. The responsible party is then granted subtask initiator permissions to further decompose the new task into specific subtasks and assign them to relevant members.

[0008] In one embodiment, the present invention provides a multi-role task assignment method for collaborative design, further comprising: Archive the total investment of past projects, the actual cost of each task stage, and the corresponding project scale indicators (such as building area, software function points, automobile production, etc.) to build a dynamic cost knowledge base for multiple project categories. When the project initiator creates a new project and enters key scale parameters, the cost knowledge base is matched with successful projects of similar size. An algorithm model is used to generate a recommended budget table for each task stage of the project (this recommended value is not a fixed value, but a reasonable range based on historical data). During the project execution, if the actual declared cost of any task stage deviates continuously or significantly from the recommended budget table, an early warning is issued to the project initiator and the financial supervisor.

[0009] In one embodiment, the present invention provides a multi-role task assignment method for collaborative design, further comprising: When the cost of a certain task in a project deviates significantly from the baseline range of the cost knowledge base (whether too high or too low), it is marked as a cost anomaly. For cost anomalies, under the premise of strict anonymization and only retaining the cost structure and task logic, the anonymized task-cost structure of the case is recommended as a special analysis report to other reputable project initiators in the field, so that project initiators can judge for themselves whether the anomaly stems from an unrecorded emerging unspoken rule that needs to be guarded against, or a process optimization or technological innovation that is truly worth promoting.

[0010] In one embodiment, the present invention provides a multi-role task assignment platform for collaborative design, comprising: The template recommendation module is used to build a structured template library, which pre-sets different templates for different project types (such as architecture, software development, etc.). The templates clearly define the roles and standard responsibilities involved in the project, and automatically recommend applicable templates based on project keywords (the project initiator can select the matching template according to the project goals). The task division module is used to break down project goals into multiple tasks after a template is selected. Each task is associated with a selected role (selected by the project initiator, and the platform can also make recommendations). The module also clarifies the input conditions, output results, time limits, and responsible parties for each task. If the project initiator modifies the input conditions, output results, or responsible parties for a task, the modification must be confirmed and agreed upon by the responsible party before it takes effect. The anomaly alert module is used to track the progress of tasks in real time and automatically detect anomalies (such as an input condition not being provided within a set time) according to preset rules. If an anomaly occurs, an alert is sent to the person responsible for the task via push notification or email to ensure that the problem can be detected and responded to in a timely manner. The issue tracing module is used to retrieve the entire project archive if faults or defects are found in the deliverables after the project is completed. The project archive includes task execution records, communication logs between roles, and task responsibility allocation data. Based on the project archive, the module traces the responsibility for the problematic stage and generates a responsibility analysis report to provide a basis for subsequent processing.

[0011] In one embodiment, the present invention provides a multi-role task assignment platform for collaborative design, further comprising: The task completion quality assessment module is used to accumulate and store information on technical personnel who have participated in past projects, classify and archive them by professional field, and build an expert database. When a project requires technical personnel in a specific field to participate in judging the quality of task completion during the acceptance or post-review stage, the module automatically recommends matching technical personnel based on the field type to support professional review needs.

[0012] In one embodiment, the present invention provides a multi-role task assignment platform for collaborative design, further comprising: The new task creation module is used when unexpected problems arise during project execution (such as derivative problems caused by task errors, or encountering "no-man's-land" ambiguities not defined by the initial template). Based on the specific technical field of the problem, it recommends one or more relevant technical personnel from the expert database (multiple personnel are recommended when cross-domain problems are involved). After the project initiator confirms the identity of the responsible party for the problem on the platform, the responsible party is granted temporary permissions to define the solution, required resources, and acceptance criteria for the problem, thereby creating a new task. The responsible party is also granted subtask initiator permissions, which can further decompose the new task into specific subtasks and assign them to relevant members.

[0013] In one embodiment, the present invention provides a multi-role task assignment platform for collaborative design, further comprising: The fund anomaly early warning module is used to archive the total investment of past projects, the actual cost of each task stage, and the corresponding project scale indicators (such as building area, software function points, automobile production, etc.). It builds a dynamic cost knowledge base for multiple project categories. When the project initiator creates a new project and enters key scale parameters, it matches successful projects of similar size from the cost knowledge base and generates a fund budget recommendation table for each task stage of the project through an algorithm model (this recommendation value is not a fixed value, but a reasonable range based on historical data). During the project execution, if the actual declared cost of any task stage deviates continuously or significantly from the fund budget recommendation table, an early warning is issued to the project initiator and the financial supervisor.

[0014] In one embodiment, the present invention provides a multi-role task assignment platform for collaborative design, further comprising: The anomaly case recommendation module is used to mark a project as a cost anomaly when the cost of a certain task in a project deviates significantly from the baseline range of the cost knowledge base (whether too high or too low). For cost anomalies, under strict anonymization and only retaining the cost structure and task logic, the anonymized task-cost structure of the case is recommended as a special analysis report to other reputable project initiators in the field. This allows project initiators to determine whether the anomaly stems from an unrecorded emerging unspoken rule that requires vigilance, or a genuine process optimization or technological innovation worth promoting.

[0015] Compared with the prior art, the beneficial effects of the present invention are: by breaking down project objectives into multiple tasks, clarifying the input conditions, output results, time limits and responsible parties for each task, and recording the entire process in a project archive, the present invention effectively reduces the rapid increase in management and coordination costs and significantly avoids efficiency losses. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating a multi-role task assignment method for collaborative design, provided as an embodiment of the present invention.

[0017] Figure 2 This is a schematic diagram of a multi-role task assignment platform for collaborative design provided in an embodiment of the present invention. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0019] It is understood that the terms "first," "second," etc., used in this application may be used herein to describe various elements, but unless otherwise specified, these elements are not limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of this application, a first script may be referred to as a second script, and similarly, a second script may be referred to as a first script.

[0020] In one embodiment, such as Figure 1 As shown, a multi-role task assignment method for collaborative design includes the following steps: Step S1: Build a structured template library, pre-set different templates for different project types (such as architecture, software development, etc.). The templates clearly define the roles and standard responsibilities involved in the project, and automatically recommend applicable templates based on project keywords (the project initiator can select the matching template according to the project goals). Step S2: After selecting a template, break down the project goal into multiple tasks, associate each task with a selected role (the project initiator selects the role, and the platform can also make recommendations), and clarify the input conditions, output results, time limits, and responsible parties required for the task. If the project initiator modifies the input conditions, output results, or responsible parties of a task, it must be confirmed and agreed upon by the responsible party before it officially takes effect. Step S3: Track the progress of the task in real time and automatically detect abnormal situations (such as an input condition not being provided within a set time) through preset rules. If an abnormal situation occurs, send a reminder to the person responsible for the task through push notification or email to ensure that the problem can be detected and responded to in a timely manner. Step S4: After the project is completed, if any faults or defects are found in the deliverables, retrieve the project archives for the entire process. The project archives include task execution records, communication logs between roles, and task responsibility allocation data. Based on the project archives, trace the responsibility for the problematic links and generate a responsibility analysis report to provide a basis for subsequent processing.

[0021] To illustrate this further, let's take a specific smart library management system project as an example. The project initiator (the city library information center) decided to develop a smart library management system.

[0022] Step S1: The project initiator enters project keywords "smart library," "software," and "management system" into the platform. Based on these keywords, the platform automatically recommends a "medium-to-large software development project" template from its structured template library. This template predefines the roles that may be involved in the project, such as: project manager, system architect, front-end developer, back-end developer, test engineer, and data administrator, and sets standard responsibilities for each role. After review, the project initiator confirms the selection of this template.

[0023] Step S2: After selecting the template, the project initiator breaks down the overall goal of "building a smart library management system" into multiple tasks, including "requirements analysis and high-level design," "user interface and interaction development," "backend core service development," "data migration and initialization," and "system integration testing." Each task is associated with a role in the template. For example, the responsibility for the "backend core service development" task rests with the backend development engineer, whose input is "confirmed API interface documentation," and whose output is "a deployable backend service package," with a clear time limit. If the project initiator wants to add a task output item temporarily, the modification must be confirmed and approved by the backend development engineer before it takes effect.

[0024] In step S3, during project execution, the platform tracks the status of each task in real time. For example, a pre-defined rule detects that the input condition for the "Data Migration and Initialization" task, the "Original Book Data CSV File," should have been provided by the data administrator before a certain time, but the system detects that the file was not uploaded on time. Therefore, the platform automatically sends a reminder to the data administrator and their project manager via message and email: "The input of the 'Original Book Data CSV File' you are responsible for has been delayed; please handle it as soon as possible," ensuring that the problem is addressed promptly.

[0025] Step S4: After the system went live, it was discovered that the borrowing status of some books was not updating in real time on mobile devices. The project team immediately retrieved the entire project archive and, by reviewing the task execution records, found that a cache update task in the "Backend Core Service Development" was marked as "skipped." Further analysis of inter-role communication logs revealed that the backend and frontend engineers had disagreed on this issue but had not reached a formal agreement. Based on these records, the platform generated a responsibility analysis report, clearly identifying the root cause as a lax cross-task communication mechanism, providing a basis for subsequent fixes and team performance evaluation.

[0026] In one embodiment, such as Figure 1 As shown, a multi-role task assignment method for collaborative design also includes: Step S5: Accumulate and store information on technical personnel who have participated in past projects, classify and archive them according to professional fields, and build an expert database; when a project requires technical personnel in a specific field to participate in judging the quality of task completion during the acceptance or post-review stage, automatically recommend matching technical personnel according to the field type to support professional review needs.

[0027] Step S5: The project enters the acceptance phase, requiring a review of the "accuracy of the book recommendation algorithm" within the professional field. Based on the tags "machine learning algorithm" and "data science," the platform automatically recommended Data Scientist A, who had previously participated in the "e-commerce intelligent recommendation system" project, from its built expert database to participate in the assessment of the task's completion quality, ensuring the professionalism of the review.

[0028] In one embodiment, such as Figure 1 As shown, a multi-role task assignment method for collaborative design also includes: Step S6: When unexpected problems occur during project execution (such as derivative problems caused by task errors, or encountering a "no-man's-land" ambiguity not defined by the initial template), based on the specific technical field of the problem, recommend one or more relevant technical personnel from the expert database (or multiple personnel if cross-domain issues are involved). After the project initiator confirms the identity of the responsible party on the platform, grant the responsible party temporary permissions to define the solution, required resources, and acceptance criteria for the problem, and create a new task accordingly. Grant the responsible party subtask initiator permissions to further decompose the new task into specific subtasks and assign them to relevant members.

[0029] In step S6, during development, the team encountered an unexpected problem: new municipal fire safety regulations required the system to integrate with the building's fire alarm system. This was not defined in the initial software development template, creating a gray area. Based on technical fields such as "IoT device integration" and "security systems," the platform recommended B, an expert with relevant experience, from its expert database. After the project initiator confirmed B as the responsible party for the problem, temporary permissions were granted to B. B defined the solution, required resources (fire system API documentation, testing equipment), and acceptance criteria, and created a new "Fire Alignment Interface Development" task. As the sub-task initiator, B further broke down this task into sub-tasks such as "protocol parsing," "interface development," and "integration testing," assigning them to relevant developers.

[0030] In one embodiment, such as Figure 1 As shown, a multi-role task assignment method for collaborative design also includes: Step S7: Archive the total investment of previous projects, the actual cost of each task stage, and the corresponding project scale indicators (such as building area, software function points, automobile production, etc.) to build a dynamic cost knowledge base for multiple project categories. When the project initiator creates a new project and enters key scale parameters, the cost knowledge base is matched with successful projects of similar size. An algorithm model is used to generate a recommended budget table for each task stage of the project (this recommended value is not a fixed value, but a reasonable range based on historical data). During the project execution, if the actual declared cost of any task stage deviates continuously or significantly from the recommended budget table, an early warning is issued to the project initiator and the financial supervisor.

[0031] In step S7, during project initiation, the initiator input key scale parameters: "expected support for 100,000 books, 50,000 registered users, and 10,000 daily visits." The platform matched several successful projects of similar scale (such as "a university library system") from its dynamic cost knowledge base and generated a recommended budget table using an algorithmic model. For example, the recommended budget range for the "backend core service development" task was 150,000-180,000 yuan. During project execution, the backend development team twice submitted server procurement expense reports that significantly exceeded the upper limit of this range. The platform immediately issued a cost overrun warning to the project initiator and financial supervisor.

[0032] In one embodiment, such as Figure 1 As shown, a multi-role task assignment method for collaborative design also includes: Step S8: When the cost of a certain task in a project deviates significantly from the baseline range of the cost knowledge base (whether too high or too low), it is marked as a cost anomaly case. For cost anomaly cases, under the premise of strict anonymization and only retaining the cost structure and task logic, the anonymized task-cost structure of the case is recommended as a special analysis report to other reputable project initiators in the field, so that the project initiators can judge for themselves whether the anomaly is due to an unrecorded emerging unspoken rule that needs to be guarded against, or a process optimization or technological innovation that is truly worth promoting.

[0033] In step S8, in the aforementioned cost warning case, the cost of the "backend core service development" task was marked as abnormal. After strict anonymization (removing project name, personnel, organization, etc.), and retaining only the cost structure and task logic of "high-concurrency system," "microservice architecture," and "cloud-native deployment," the platform recommended this anonymous "high-cost, high-performance backend architecture" case as a special analysis report to other reputable software project initiators within the platform. These initiators can study this case and determine for themselves whether it's due to the adoption of expensive but high-performance new technologies (a process optimization worth promoting) or unreasonable resource waste (a hidden rule to be wary of).

[0034] In one embodiment, such as Figure 2 As shown, a multi-role task assignment platform for collaborative design includes: Template recommendation module 1 is used to build a structured template library, which pre-sets different templates for different project types (such as architecture, software development, etc.). The templates clearly define the roles and standard responsibilities involved in the project, and automatically recommend applicable templates based on project keywords (the project initiator can select the matching template according to the project goals). Task division module 2 is used to break down the project goal into multiple tasks after a template is selected. Each task is associated with a selected role (selected by the project initiator, and the platform can also make recommendations). The input conditions, output results, time limits and responsible parties of the task are clearly defined. If the project initiator modifies the input conditions, output results and responsible parties of the task, it must be confirmed and agreed by the responsible party before it officially takes effect. The exception notification module 3 is used to track the task progress status in real time and automatically detect abnormal situations (such as an input condition not being provided within a set time) according to preset rules. If an abnormal situation occurs, a reminder is sent to the task responsible party via push notification or email to ensure that the problem can be detected and responded to in a timely manner. Problem tracing module 4 is used to retrieve the entire project archive if faults or defects are found in the deliverables after the project is completed. The project archive includes task execution records, communication logs between roles, and task responsibility allocation data. Based on the project archive, the responsibility for the problematic link is traced and a responsibility analysis report is generated to provide a basis for subsequent processing.

[0035] Template Recommendation Module 1 aims to solve the challenge of starting a project from scratch by standardizing templates to improve efficiency and ensure basic compliance. However, when projects encounter new problems (such as "no-man's-land" issues), the blind spots of existing templates are exposed. These exceptions, in turn, serve as important input for iterating and optimizing the template library, enabling it to cover more scenarios and thus achieving the platform's self-evolution.

[0036] In one embodiment, such as Figure 2 As shown, a multi-role task assignment platform for collaborative design also includes: The Task Completion Quality Assessment Module 5 is used to accumulate and store information on technical personnel who have participated in past projects, classify and archive them by professional field, and build an expert database. When a project requires technical personnel in a specific field to participate in judging the quality of task completion during the acceptance or post-review stage, the module automatically recommends matching technical personnel based on the field type to support professional review needs.

[0037] The platform assigns precise domain tags (such as "machine learning" and "data security") to each technical staff member and each review request. When a review is required, the platform first matches the tags and then ranks and recommends requests based on three core dimensions: 1. Professional Matching: Calculate the degree of fit between the applicant's past project experience and the current task domain.

[0038] 2. Capability verification: retrieve the final results of the projects they have participated in and user evaluations as proof of their capabilities.

[0039] 3. Availability and Conflict Avoidance: Check the current workload and automatically exclude personnel with a conflict of interest in the current project. Finally, generate a recommended list sorted by matching score.

[0040] In one embodiment, such as Figure 2 As shown, a multi-role task assignment platform for collaborative design also includes: The new task creation module 6 is used when unexpected problems arise during project execution (such as derivative problems caused by task errors, or encountering "no-man's-land" ambiguities not defined by the initial template). Based on the specific technical field of the problem, it recommends one or more relevant technical personnel from the expert database (multiple personnel are recommended when cross-domain problems are involved). After the project initiator confirms the identity of the responsible party for the problem on the platform, the responsible party is granted temporary permissions to define the solution, required resources, and acceptance criteria for the problem, and a new task is created accordingly. The responsible party is also granted sub-task initiator permissions, which can further decompose the new task into specific sub-tasks and assign them to relevant members.

[0041] When the platform recommends multiple technical personnel for cross-disciplinary issues, the project initiator, as the final decision-maker, will select one as the primary responsible party based on multi-dimensional data provided by the platform. This data includes each candidate's domain relevance, historical project success rate, current workload, and evaluation of their collaborative leadership in similar complex problems. After comprehensive judgment, the project initiator will confirm the candidate who best combines technical authority and project management capabilities to serve as the responsible party.

[0042] When creating new tasks and breaking down subtasks, the person granted temporary authority does not act unilaterally but needs to consult and confirm with other recommended technical personnel. They must break down the task into subtasks of different professional areas based on the technical logic of the solution and invite or assign them to the appropriate technical personnel. This process also follows the principle of "equal rights and responsibilities," requiring confirmation from the executor of each subtask's allocation and specific requirements, thus forming a temporary collaborative team with clear responsibilities and consensus.

[0043] In one embodiment, such as Figure 2 As shown, a multi-role task assignment platform for collaborative design also includes: The Funding Anomaly Early Warning Module 7 is used to archive the total investment of past projects, the actual expenses of each task stage, and the corresponding project scale indicators (such as building area, software function points, automobile production, etc.). It constructs a dynamic cost knowledge base for multiple categories of projects. When the project initiator creates a new project and enters key scale parameters, it matches successful projects of similar size from the cost knowledge base and generates a funding budget recommendation table for each task stage of the project through an algorithm model (this recommendation value is not a fixed value, but a reasonable range based on historical data). During the project execution, if the actual declared expenses of any task stage continuously or significantly deviate from the funding budget recommendation table, an early warning is issued to the project initiator and the financial supervisor.

[0044] The core purpose of the abnormal funding early warning module 7 is to address the widespread problem of cost opacity in the industry. Since embezzlement and misconduct often hide within project budgets, managers (including project initiators) find it difficult to determine the reasonableness of certain expenditures based solely on experience. This method builds a historical cost knowledge base to generate a scientific budget range as a benchmark. Once actual spending consistently deviates from this benchmark, the system will issue an early warning, thereby exposing potential abnormal cost structures and prompting project initiators and financial supervisors to pay attention to and verify the reasonableness of cost overruns, assisting managers in making informed decisions.

[0045] Building a cost knowledge base first requires automatically archiving the total investment, actual costs of each task stage, and key scale indicators (such as software functionalities) after project completion, followed by data cleaning and standardization. Then, this massive, multi-category project data is stored according to a structure of "project type - scale indicators - task breakdown - actual cost," forming a continuously growing historical database. When a new project is entered with scale parameters, the system uses algorithms to accurately match a cluster of successful cases of similar size from the database. Instead of simply calculating an average, it uses statistical models to analyze the distribution patterns of costs for each task, ultimately generating a reasonable budget range based on historical data, providing a dynamic and scientific benchmark for cost monitoring.

[0046] In one embodiment, such as Figure 2 As shown, a multi-role task assignment platform for collaborative design also includes: The abnormal case recommendation module 8 is used to mark a project as a cost anomaly when the cost of a certain task in a project deviates significantly from the baseline range of the cost knowledge base (whether too high or too low). For cost anomalies, under the premise of strict anonymization and only retaining the cost structure and task logic, the anonymized task-cost structure of the case is recommended as a special analysis report to other reputable project initiators in the field, so that project initiators can judge for themselves whether the anomaly stems from an unrecorded emerging unspoken rule that needs to be guarded against, or a process optimization or technological innovation that is truly worth promoting.

[0047] Reputable project initiators are users whose project success rate is high (e.g., 90%), whose cost reports are accurate and truthful, and who have no bad credit records in the platform's history.

[0048] If the industry's unspoken rules have become widespread, making it impossible for the platform to identify them (the abnormal fund warning module 7 cannot identify them), then if a low-cost project that deviates from the cost knowledge base appears (although it is common, there are still some or individual projects that do not have unspoken rules for embezzlement or have embezzlement less), it will be recommended to other project initiators in this field so as to understand whether unspoken rules exist or the project structure has been optimized.

[0049] In Module 8, which recommends anomalies, project initiators who receive reports can anonymously analyze and discuss the causes of the cost structure based on their own experience in a controlled forum. This process aims to pool collective wisdom to jointly identify the anomaly, thereby transforming the anomaly of an individual project into a collective learning opportunity for the entire platform's user base.

[0050] It should be understood that although the steps in the flowcharts of the various embodiments of the present invention are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the various embodiments may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0051] The technical features of the above embodiments can be combined in any way. For the sake of brevity, 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 specification.

[0052] The embodiments described above are merely illustrative of several implementations of the present invention, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these modifications and improvements all fall within the scope of protection of the present invention. Therefore, the scope of protection of this patent should be determined by the appended claims.

[0053] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

[0054] Furthermore, it should be understood that although this specification describes embodiments, not every embodiment contains only one independent technical solution. This narrative style is merely for clarity. Those skilled in the art should consider the specification as a whole, and the technical solutions in each embodiment can also be appropriately combined to form other embodiments that can be understood by those skilled in the art.

Claims

1. A multi-role task assignment method for collaborative design, characterized in that, This multi-role task assignment method for collaborative design includes the following steps: Build a structured template library with different templates for different project types. The templates clearly define the roles and standard responsibilities involved in the project and automatically recommend applicable templates based on project keywords. After selecting a template, the project objectives are broken down into multiple tasks. Each task is associated with a selected role, and the required input conditions, output results, time limits, and responsible parties for each task are clearly defined. If the project initiator modifies the input conditions, output results, or responsible parties for a task, the changes must be confirmed and agreed upon by the responsible party before they take effect. Track task progress in real time, automatically detect abnormal situations through preset rules, and send reminders to the task responsible party via push notification or email if an abnormal situation occurs, so as to ensure that the problem can be detected and responded to in a timely manner; If any faults or defects are found in the deliverables after the project is completed, the entire project archive is retrieved. The project archive includes task execution records, communication logs between roles, and task responsibility allocation data. Based on the project archive, the responsibility for the problematic stage is traced, and a responsibility analysis report is generated to provide a basis for subsequent processing.

2. The multi-role task assignment method for collaborative design according to claim 1, characterized in that, Also includes: Accumulate and store information on technical personnel who participated in past projects, classify and archive them according to their professional fields, and build an expert database; When a project requires technical personnel from a specific field to assess the quality of task completion during the acceptance or post-project review phase, the system automatically recommends matching technical personnel based on the field type to support professional review needs.

3. The multi-role task assignment method for collaborative design according to claim 2, characterized in that, Also includes: When unexpected problems arise during project execution, one or more relevant technical personnel are recommended from the expert database based on the specific technical field of the problem. After the project initiator confirms the identity of the responsible party on the platform, the responsible party is granted temporary permissions to define the solution, required resources, and acceptance criteria for the problem, and a new task is created accordingly. The responsible party is then granted subtask initiator permissions to further decompose the new task into specific subtasks and assign them to relevant members.

4. The multi-role task assignment method for collaborative design according to any one of claims 1 to 3, characterized in that, Also includes: Archive the total investment of past projects, the actual cost of each task stage, and the corresponding project scale indicators to build a dynamic cost knowledge base for multiple project categories. When a project initiator creates a new project and enters key scale parameters, the cost knowledge base is matched with successful projects of similar size. An algorithm model is used to generate a recommended budget table for each task stage of the project. During the project execution, if the actual declared cost of any task stage deviates continuously or significantly from the recommended budget table, an early warning is issued to the project initiator and the financial supervisor.

5. The multi-role task assignment method for collaborative design according to claim 4, characterized in that, Also includes: When the cost of a certain task in a project deviates significantly from the baseline range of the cost knowledge base, it is marked as a cost anomaly case. For cases of cost anomalies, under the premise of strict anonymization and retaining only the cost structure and task logic, the anonymized task-cost structure of the case is recommended as a special analysis report to other reputable project initiators in the field, so that project initiators can judge for themselves whether the anomaly stems from an unrecorded emerging unspoken rule that needs to be guarded against, or a process optimization or technological innovation that is truly worth promoting.

6. A multi-role task assignment platform for collaborative design, characterized in that, include: The template recommendation module is used to build a structured template library, which pre-sets different templates for different project types. The templates clearly define the roles and standard responsibilities involved in the project and automatically recommend applicable templates based on project keywords. The task division module is used to break down project goals into multiple tasks after a template is selected. Each task is associated with a selected role, and the required input conditions, output results, time limits, and responsible parties are clearly defined. If the project initiator modifies the input conditions, output results, or responsible parties of a task, it must be confirmed and agreed upon by the responsible party before it officially takes effect. The anomaly alert module is used to track the progress of tasks in real time, automatically detect anomalies according to preset rules, and send reminders to the task responsible party via push notification or email if an anomaly occurs, ensuring that the problem can be detected and responded to in a timely manner. The issue tracing module is used to retrieve the entire project archive if faults or defects are found in the deliverables after the project is completed. The project archive includes task execution records, communication logs between roles, and task responsibility allocation data. Based on the project archive, the module traces the responsibility for the problematic stage and generates a responsibility analysis report to provide a basis for subsequent processing.

7. The multi-role task assignment platform for collaborative design according to claim 6, characterized in that, Also includes: The task completion quality assessment module is used to accumulate and store information on technical personnel who have participated in past projects, classify and archive them according to professional fields, and build an expert database. When a project requires technical personnel from a specific field to assess the quality of task completion during the acceptance or post-project review phase, the system automatically recommends matching technical personnel based on the field type to support professional review needs.

8. The multi-role task assignment platform for collaborative design according to claim 7, characterized in that, Also includes: The new task creation module is used to recommend one or more relevant technical personnel from the expert database when unexpected problems occur during project execution, based on the specific technical field of the problem. After the project initiator confirms the identity of the responsible party on the platform, the responsible party is granted temporary permissions to define the solution, required resources, and acceptance criteria for the problem, and a new task is created accordingly. The responsible party is also granted subtask initiator permissions, which can further decompose the new task into specific subtasks and assign them to relevant members.

9. The multi-role task assignment platform for collaborative design according to any one of claims 6 to 8, characterized in that, Also includes: The fund anomaly early warning module is used to archive the total investment of past projects, the actual expenses of each task stage, and the corresponding project scale indicators, and to build a dynamic cost knowledge base for multiple types of projects. When the project initiator creates a new project and enters key scale parameters, the module matches successful projects of similar size from the cost knowledge base and generates a fund budget recommendation table for each task stage of the project through an algorithm model. During the project execution, if the actual declared expenses of any task stage continuously or significantly deviate from the fund budget recommendation table, an early warning is issued to the project initiator and the financial supervisor.

10. The multi-role task assignment platform for collaborative design according to claim 9, characterized in that, Also includes: The abnormal case recommendation module is used to mark a project as an abnormal cost case when the cost of a certain task in a project deviates significantly from the baseline range of the cost knowledge base. For cases of cost anomalies, under the premise of strict anonymization and retaining only the cost structure and task logic, the anonymized task-cost structure of the case is recommended as a special analysis report to other reputable project initiators in the field, so that project initiators can judge for themselves whether the anomaly stems from an unrecorded emerging unspoken rule that needs to be guarded against, or a process optimization or technological innovation that is truly worth promoting.

Images