Multi-dimensional complex task association management method and system based on WBS
By adopting a WBS-based multi-dimensional complex task association management method, the problem of managing multi-dimensional data in reactor R&D process that cannot be managed in existing technologies has been solved. This method enables task execution status tracking and change impact analysis, thus meeting the business needs in the reactor R&D process.
Patent Information
- Application Number
- CN202510979076.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-16
- Publication Date
- 2025-11-25
AI Technical Summary
Existing WBS methods cannot effectively manage the task relationships of multi-dimensional data during reactor development, making it difficult for task decomposition to meet business needs.
By using a WBS-based multi-dimensional complex task association management method, project data is acquired, decomposed into task information, task types are determined, and data type attribute information is configured to form data types. This enables the association configuration of task input and output attributes and establishes a multi-dimensional complex task association model.
It enables comprehensive management of complex task relationships, supports task execution status tracking and change impact analysis, and meets the needs for displaying multi-dimensional data during reactor development.
Smart Images

Figure CN121010123A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of scientific research project management technology, and in particular to a multi-dimensional complex task association management method and system based on WBS. Background Technology
[0002] Work Breakdown Structure (WBS) is a tool and methodology in project management. By breaking down and assigning tasks for each project and displaying them in a tree structure, it helps project managers clarify project goals and improve communication efficiency.
[0003] While project management tools can be developed based on the WBS method, these products present task relationships in a relatively simple way. They use simple pre- and post-processing settings to represent task relationships, control task execution, and display task status, which cannot effectively connect and display tasks with multi-dimensional data relationships in actual scientific research and engineering projects.
[0004] Taking reactor development as an example, reactor design is a field with complex upstream and downstream business relationships, numerous related interfaces, and strict data generation processes. When decomposing and monitoring tasks using a Work Breakdown Structure (WBS), it is necessary to consider the data types of various upstream and downstream relationships, the execution status of related data, and the progress of downstream task execution. However, the WBS management tools used in reactor development cannot display multi-dimensional data related to tasks, making it difficult for WBS task decomposition to meet the needs of business applications in the reactor development process. Summary of the Invention
[0005] In view of this, embodiments of this application provide a method and system for managing multi-dimensional complex task associations based on WBS, in order to solve the problem that the WBS method cannot manage multi-dimensional data related to tasks.
[0006] According to one aspect of this application, a multi-dimensional complex task association management method based on WBS is provided, the method comprising: Acquire management project data, wherein the management project data includes at least one management project; Based on the preset task decomposition structure standard, the management project data is decomposed into task information, which includes multiple decomposed tasks divided according to task level and task control method. The task type is determined based on the task information. The task type includes a basic task type and an extended task type. The basic task type is the task type of the decomposed task extracted from the task type library. The extended task type is the task type obtained by configuring extended attributes of the decomposed task through the basic task information data model. Based on the task association type library, data type attribute information is configured for the task type to form a data type; For the task input attributes and task output attributes in the task type, the associated configuration is performed by selecting the data type.
[0007] In some embodiments, based on a preset task decomposition structure standard, the management project data is decomposed into task information, including: Obtain the preset task decomposition structure standard; Read the hierarchical decomposition standard from the preset task decomposition structure standard. The hierarchical decomposition standard includes at least one of the stage decomposition standard, topic decomposition standard, and task decomposition standard. According to the aforementioned hierarchical decomposition criteria, the management project data is decomposed into multiple decomposition tasks layer by layer.
[0008] In some embodiments, the management project data is decomposed layer by layer into multiple decomposition tasks according to the hierarchical decomposition criteria, including: Based on the stage decomposition criteria, stage information is extracted from the management project data, and the stage information includes at least one task stage. According to the aforementioned topic decomposition criteria, the task stage in the stage information is decomposed into topics to obtain topic information, which includes at least one task topic. Based on the task decomposition criteria, decomposed tasks are extracted from the task topics; Construct a task decomposition structure tree based on the stage information, the topic information, and the task information.
[0009] In some embodiments, the method further includes: Obtain sample project data in the current application field; Extract sample hierarchy information and sample task information from the sample project data; The hierarchical decomposition criteria are constructed based on the sample hierarchical information, and the task structure is constructed based on the sample task information; The hierarchical standard and the task structure are encapsulated to establish the preset task decomposition structure standard.
[0010] In some embodiments, determining the task type based on the task information includes: Call the task type library, which is used to classify and manage the task types of decomposed tasks; Extract the task identification information of the decomposed task from the task information; Based on the task identification information, the task type of the decomposed task is matched in the task type library to obtain the basic task type.
[0011] In some embodiments, determining the task type based on the task information includes: Call the basic task information data model, which is a configuration model developed based on task information standard specifications; Based on the basic task information data model, extended attribute configuration is performed on the decomposed tasks to form extended task types; Based on the preset task decomposition structure standard, hierarchical application control configuration is applied to the extended task types.
[0012] In some embodiments, the method further includes: Obtain sample task information from sample project data in the current application domain; Determine the extended attributes associated with the sample task information; Establish a task information standard specification based on the extended attributes and the sample task information; The basic task information data model is constructed based on the aforementioned task information standard specifications.
[0013] In some embodiments, the method further includes: Record the association relationship between the task type and the data type in the association configuration; Obtain the task display command used to display the target task; In response to the task display instruction, the association information corresponding to the target task is queried according to the association relationship; the association information includes data types that are associated with the task type corresponding to the target task and related tasks of the target task; Display the target task and the associated information.
[0014] In some embodiments, the method further includes: Obtain user demand data; Create a new task based on the user demand data; Based on the basic task information data model, the new task is configured with extended attributes to obtain the task type of the new task. Based on the task association type library, data type attribute information is configured for the task type of the new task to form a new data type.
[0015] Establish a task association model based on the task type and data type of the new task.
[0016] According to another aspect of this application, a multi-dimensional complex task association management system based on WBS is provided, the system comprising: The data acquisition module is used to acquire management project data, which includes at least one management project. The task decomposition module is used to decompose the management project data into task information based on a preset task decomposition structure standard. The task information includes multiple decomposed tasks divided according to task level and task control method. The task type determination module is used to determine the task type based on the task information. The task type includes a basic task type and an extended task type. The basic task type is the task type of the decomposed task extracted from the task type library. The extended task type is the task type obtained by configuring extended attributes of the decomposed task through the basic task information data model. The data type configuration module is used to configure data type attribute information for the task type based on the task association type library to form a data type; The association configuration module is used to perform association configuration for the task input attributes and task output attributes in the task type by selecting the data type.
[0017] According to another aspect of this application, a computer device is provided, including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor executes the program to implement the above-described WBS-based multi-dimensional complex task association management method.
[0018] According to another aspect of this application, a storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the above-described WBS-based multi-dimensional complex task association management method.
[0019] By employing the above technical solutions, embodiments of this application provide a method and system for managing multi-dimensional complex task associations based on WBS. After acquiring project data, the method decomposes the project data into task information based on a preset task decomposition structure standard. Then, it determines the task type based on the task information and configures data type attribute information for the task type based on a task association type library to form a data type. Thus, for the task input and output attributes within the task type, association configuration is performed by selecting the data type. This method can comprehensively consider complex upstream and downstream business relationships, numerous associated interfaces, and multiple associated attributes, satisfying the complex task relationships in management projects. It provides basic data management functions to support task execution status tracking and task change impact analysis, thereby solving the problem that the WBS method cannot manage multi-dimensional data related to tasks.
[0020] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description
[0021] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 This is a schematic diagram of the WBS method flow provided in the embodiments of this application; Figure 2 A schematic diagram of the process for a multi-dimensional complex task association management method based on WBS provided in this application embodiment; Figure 3 This is a schematic diagram of the decomposition results of item A provided in an embodiment of this application; Figure 4 This is a schematic diagram of the decomposition process of Project B provided in an embodiment of this application; Figure 5 A schematic diagram of a multi-dimensional complex task association model based on WBS provided in this application embodiment; Figure 6 A schematic diagram illustrating the on-demand task creation and related data types provided in this application embodiment; Figure 7 This is a schematic diagram illustrating the task flow in an embodiment of this application; Figure 8 This is a schematic diagram of the structure of a multi-dimensional complex task association management system based on WBS provided in an embodiment of this application. Detailed Implementation
[0022] The present application will be described in detail below with reference to the accompanying drawings and embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in the embodiments of the present application can be combined with each other.
[0023] In this embodiment, the Work Breakdown Structure (WBS) is a method for project management. It breaks down a project into manageable work units, each containing all the work necessary to complete the project. Through WBS, complex projects can be transformed into a series of relatively simple, clear, and easy-to-manage tasks. By breaking down and assigning tasks for project progress and displaying them in a tree structure, project managers can better understand project objectives and improve communication efficiency.
[0024] like Figure 1 As shown, in some embodiments, when performing project management based on the WBS method, the project objectives and expected deliverables can be obtained first. Then, based on the project objectives, the main deliverables that the project needs to deliver are identified. These main deliverables characterize the key tasks that the project ultimately needs to complete. For example, in a reactor R&D project, the main deliverables might include R&D equipment information, equipment layout status, and equipment test reports.
[0025] After identifying the main deliverables that the project needs to deliver, these main deliverables can be decomposed into smaller, relatively independent work units. These work units can be sub-deliverables, work packages, or tasks. The decomposition of main deliverables can be based on the project's workflow, product structure, project phases, etc. The depth of decomposition can be determined according to the project's complexity and management requirements.
[0026] Based on the decomposition of deliverables, the relationships between work units can be determined. This can be achieved by analyzing the logical relationships between each work unit. For example, these logical relationships can include sequence and dependencies. Since some work units can only begin after other work units are completed, while others can be carried out in parallel, analyzing the logical relationships between work units allows for the rational scheduling of the project schedule, ensuring the smooth progress of the project. After determining the relationships between work units, responsibilities and resources can be assigned to each work unit. This involves identifying the responsible person for each work unit and determining the necessary resources, including human, material, and financial resources.
[0027] After completing the WBS decomposition, the entire decomposition result needs to be reviewed to check for any missing work content, the rationality of the decomposition, and the correctness of the relationships between work units. Based on the review results, the WBS should be adjusted and optimized as necessary to ensure that it accurately reflects the project's work content and requirements.
[0028] In some embodiments, project management tools can be developed based on the WBS methodology. For example, project management applications, drawing and design applications, and office applications can be developed based on WBS principles. Project management applications can integrate essential industry management tools, such as Gantt charts, Kanban boards, and timesheets, to achieve project management and data visualization. Drawing and design applications may include work breakdown structure tools, which can be used to create WBSs and their various decomposition results. Elements can be added and rearranged via drag and drop, and the work can be saved. Office applications can be used to draw and display the created WBS diagrams.
[0029] However, the way related products represent task relationships in the WBS structure is relatively simple. They rely on simple pre- and post-processing settings to represent task relationships, control task execution, and display task status. This fails to adequately address the multi-dimensional data relationships involved in actual scientific research and engineering projects. Taking reactor development as an example, reactor design is a field with complex upstream and downstream business relationships, numerous interfaces, and strict data generation processes. When decomposing and monitoring tasks in the WBS, it's necessary to consider the various types of upstream and downstream related data, the execution status of related data, and the progress of downstream task execution. However, the WBS management tools used in reactor development cannot display the multi-dimensional data of task relationships, making it difficult for WBS task decomposition to meet the needs of business applications in reactor development.
[0030] To address the issue that the WBS method cannot manage multi-dimensional data associated with tasks, some embodiments of this application provide a WBS-based method for managing multi-dimensional complex task associations. This method can be applied to electronic devices with data processing capabilities. These electronic devices include, but are not limited to, computers, servers, mobile terminals, smart wearable devices, and industrial control machines. For ease of description, electronic devices are used as the execution subject in these embodiments. It should be understood that the method can also be applied to other types of execution subjects, which are not illustrated in these embodiments.
[0031] To meet the needs of business applications in fields such as nuclear reactor design, the aforementioned multi-dimensional complex task association management method based on WBS can, based on WBS technology, consider the multiple association attributes of tasks to form a multi-dimensional complex task association model based on WBS. This supports the monitoring and traceability of the execution status of complex business processes in related industries, while ensuring clear relationships between tasks and orderly task execution. Figure 2 As shown, the method includes: S101. Obtain management project data.
[0032] To manage projects in a specific field, electronic devices can first acquire project management data. This project management data includes at least one project. A project can include multiple management phases, and each phase can be divided into multiple topics according to business content, with each topic containing multiple specific tasks.
[0033] In some embodiments, electronic devices can acquire project management data through specific project management applications. For example, project management applications may have built-in reporting and analysis tools, allowing electronic devices to run the application and automatically generate project progress reports, resource usage reports, cost reports, and other project management data based on these tools. Therefore, when project management data is needed, the electronic device can directly run the project management application's reporting and analysis tools to obtain relevant project data in real time.
[0034] In some embodiments, electronic devices can also acquire project management data based on user input data. For example, electronic devices can obtain project management data such as task progress, encountered problems, and resource requirements by recording project meetings. To this end, electronic devices can be connected to data acquisition devices such as microphones and cameras. When relevant personnel hold regular project meetings, the audio and video signals during the project meetings can be acquired through the data acquisition devices, and the audio and video signals can be converted into text information through a text conversion tool, thereby acquiring project management data.
[0035] In some embodiments, the electronic device can also obtain management project data based on project files. That is, when the electronic device needs to obtain management project data, it can send a data retrieval request to a storage device storing the project files. The storage device then responds to the data retrieval request and sends the requested management project data back to the electronic device, enabling the electronic device to obtain the management project data. For example, project files used to obtain management project data may include project plan documents, change request documents, meeting minutes, etc.
[0036] To ensure that the acquired management project data meets the execution requirements of subsequent WBS technology, electronic devices can perform preprocessing on the acquired management project data. Preprocessing may include data format conversion, data content filtering, data analysis, and key information extraction.
[0037] Therefore, in some embodiments, when an electronic device acquires management project data, it can first acquire the raw data and then perform format conversion on the raw data to transform it into a specific data format. For example, after acquiring an audio signal through a data acquisition device, the electronic device can call a speech-to-text tool to convert the audio signal into text information in text format.
[0038] After data format conversion, electronic devices can also filter the original data to obtain correct data. For example, for text information converted from audio signals, electronic devices can process meaningless symbols, duplicate content, missing content, and erroneous content in the text information based on a preset dictionary to obtain key text information.
[0039] Then, by invoking data analysis tools, relevant data content for the management project is identified from the correct data, and key information is extracted from this relevant data to obtain management project data. For example, after acquiring key text information, an electronic device can invoke a semantic analysis model to determine the semantics of the key text information. Then, based on the semantics, relevant data for representing the management project is determined. Next, a key information extraction tool is invoked to extract specific data content for the management project from the relevant data representing the management project, such as project progress, cost, and resource usage, forming management project data for subsequent WBS technology.
[0040] S102. Based on the preset task decomposition structure standard, the management project data is decomposed into task information.
[0041] After acquiring project management data, the electronic device can obtain a preset task breakdown structure (WBS) standard and, based on this standard, decompose the project management data into task information. The preset WBS standard is a pre-established Work Breakdown Structure (WBS) standard that can be used to determine task levels and task control methods. For example, the WBS structure can be determined based on the execution process, including a first-level stage. Under the first-level stage, topics, themes, and various types of tasks can be established, forming multiple levels. Furthermore, task types can be configured, and topics and themes can also be understood as types of tasks.
[0042] Task Breakdown Structure (WBS) standards can include the goals and scope of WBS task decomposition, the decomposition levels of the WBS, and the task decomposition methods. WBS standards can serve as a reference template, enabling electronic devices to quickly establish a task breakdown structure. For example, an established WBS task breakdown structure standard can include decomposition levels, level attributes, level decomposition permissions, level collaborative decomposition control, task assignment mechanisms, and task status promotion mechanisms. Through a unified WBS task breakdown structure standard, task levels and task management methods can be determined.
[0043] When establishing a task breakdown structure (TBS) standard, the independence, completeness, manageability, and estimability of tasks need to be considered. This ensures that each task in the project breakdown is independent, reducing overlap and facilitating clear responsibility allocation and schedule tracking. Furthermore, the task breakdown should comprehensively cover all project work. The size and complexity of tasks should be moderate for easy management and control. Additionally, tasks should be specific enough to allow for accurate schedule and cost estimates.
[0044] In some embodiments, electronic devices can establish task decomposition structure standards based on sample data in the application domain. That is, electronic devices can acquire sample project data in the current application domain and extract sample hierarchical information and sample task information from the sample project data.
[0045] The sample project data is a dataset constructed by collecting standard data related to management projects in the current application domain. The sample project data can demonstrate characteristics such as the smallest decomposition unit, task scale, and resource consumption of management projects in the current application domain. After acquiring the sample project data, the electronic device can extract sample hierarchical information and sample task information from the sample project data using information extraction tools such as machine learning models. For example, sample hierarchical information can include multiple levels that each management project in the sample project data can be decomposed into, including but not limited to stages, topics, and tasks. Sample task information can include multiple task units that each management project in the sample project data can be decomposed into, such as task 1, task 2, ..., task N, etc.
[0046] After extracting sample hierarchical information and sample task information, the electronic device constructs a hierarchical decomposition standard based on the sample hierarchical information and a task structure based on the sample task information. Then, by encapsulating the hierarchical standard and the task structure, a preset task decomposition structure standard is established.
[0047] For example, such as Figure 3 As shown, for project A, it can be pre-decomposed using WBS technology to obtain the corresponding task decomposition structure tree. The task decomposition structure tree can include two phases: Phase 1 and Phase 2. Phase 1 can be decomposed into Topic 1 and Task 1; Phase 2 can be decomposed into Topic 2 and Task 2, and so on. Based on the decomposition results, the management project data corresponding to project A can be labeled to determine the sample hierarchical information and sample task information contained in project A. The sample hierarchical information represents the hierarchical relationship of "project-phase-topic-task" and determines which information is judged as information features of different levels. The sample task information represents all the tasks obtained after decomposition and the logical relationships between each task. Based on this, after extracting the sample hierarchical information and sample task information through a machine learning model, the electronic device can establish a hierarchical partitioning template based on the sample hierarchical information to form a hierarchical decomposition standard. Furthermore, a task structure template can be constructed based on the sample task information to obtain the task decomposition structure standard.
[0048] After establishing a task decomposition structure standard, electronic devices can decompose the managed project data into task information based on the task decomposition structure standard. The task information includes multiple decomposed tasks divided according to task level and task control method.
[0049] To achieve task decomposition of management project data, in some embodiments, when an electronic device decomposes the management project data into task information based on a preset task decomposition structure standard, it can first obtain the preset task decomposition structure standard, and then read the hierarchical decomposition standard from the preset task decomposition structure standard. The hierarchical decomposition standard includes at least one of a stage decomposition standard, a topic decomposition standard, and a task decomposition standard. Then, according to the hierarchical decomposition standard, the management project data is decomposed layer by layer into multiple decomposed tasks.
[0050] When an electronic device decomposes the management project data into multiple decomposition tasks layer by layer according to the aforementioned hierarchical decomposition criteria, it can first extract stage information from the management project data based on the stage decomposition criteria. This stage information includes at least one task stage. Then, according to the aforementioned topic decomposition criteria, topic decomposition is performed on the task stages in the stage information to obtain topic information, which includes at least one task topic. Finally, based on the aforementioned task decomposition criteria, decomposition tasks are extracted from the task topics.
[0051] For example, such as Figure 4 As shown, for project B in the project management data, the electronic device can first decompose project B into phase 1 and phase 2 based on the phase decomposition criteria. Then, based on the task decomposition criteria, phase 1 is decomposed into tasks to obtain task 1 that meets the task decomposition criteria and task 1 that does not meet the task decomposition criteria. Similarly, the electronic device can also decompose phase 2 into tasks based on the task decomposition criteria to obtain task 2 and task 2.
[0052] For certain levels, larger stages or topics can be further decomposed based on the same hierarchical decomposition criteria. For example, ... Figure 5 As shown, for Topic 1, Topic 1 can be further decomposed into Topic 1.1 based on the Topic Decomposition Criteria, and Task 1.4 can be decomposed from Topic 1 based on the Task Decomposition Criteria. Then, based on the Task Decomposition Criteria, Topic 1.1 can be further decomposed into Task 1.3. And so on, each stage and topic can be decomposed into tasks to obtain multiple decomposed tasks, i.e., task information.
[0053] After obtaining multiple stages, topics, and tasks through task decomposition, the electronic device can also construct a task decomposition structure tree based on the stage information, topic information, and task information. By establishing a unified WBS structure tree, unified management and display of multi-dimensional complex task relationships can be achieved.
[0054] S103. Determine the task type based on the task information.
[0055] Based on a preset task decomposition structure standard, after the managed project data is decomposed into task information, the electronic device can determine the task type according to the task information. The task type includes a basic task type and an extended task type. The basic task type is the task type of the decomposed task extracted from a task type library; the extended task type is the task type obtained by configuring extended attributes of the decomposed task through a basic task information data model.
[0056] The basic task information data model is a task attribute information model. For example, the basic task information data model can record task level, task name, task code, task responsible unit, responsible department, responsible person, start time, end time, creator, creation time, etc. as the basic attributes of the task in the above WBS structure.
[0057] Electronic devices can first establish task information standards and specifications. These standards and specifications can serve as the basic attribute specifications for tasks. For example, the established basic attribute specifications are used to define task information, which may include task number, task name, task type, names of preceding and following tasks, task input, task output, and task output data type, etc.
[0058] After establishing task information standards and specifications, electronic devices can develop basic task information data models based on these standards and specifications, and construct configurable task type libraries to achieve classified management of task types. Therefore, in some embodiments, in order to determine the basic task type, when the electronic device performs task type determination based on task information, it can first call the task type library used for classifying and managing the task types of decomposed tasks, extract the task identification information of the decomposed tasks from the task information, and then match the task types of the decomposed tasks in the task type library based on the task identification information to obtain the basic task type.
[0059] A task type library is a database used to store task types. It can be built by storing the association between task identification information and task types. For example, the task type library can store multiple task types in the current application domain, including type 1, type 2, ..., type n. Each task type can be associated with at least one type of task identification information, such as task A, task B, ..., task m. By reading the task information and obtaining the task identification information task B, the task type of the corresponding decomposed task, i.e., type 2, can be determined based on the association between the task type and the task identification information.
[0060] The task type library can adopt a configurable data construction method, which allows the task type library to support data configuration in different fields. That is, electronic devices can expand the configuration of task categories as needed according to the industry characteristics of the current application field.
[0061] In some embodiments, to determine the extended task type, the electronic device may invoke a basic task information data model when performing the task type determination based on the task information. This basic task information data model is a configuration model developed based on task information standard specifications. The electronic device can obtain sample task information from sample project data in the current application domain, determine the extended attributes associated with the sample task information, establish task information standard specifications based on the extended attributes and the sample task information, and construct the basic task information data model based on the task information standard specifications.
[0062] After invoking the basic task information data model, the electronic device can configure extended attributes for the decomposed tasks based on the basic task information data model to form extended task types, such as task supervisor, task requirement description, task output, and task input. It can also apply hierarchical control configuration to the extended task types based on the preset task decomposition structure standard.
[0063] For example, in determining task types, electronic devices can establish a Work Breakdown Structure (WBS) standard to define task levels and control methods, then create task information standards and develop a basic task information data model. A configurable task type library can then be built to manage task types by category. Based on the basic task information data model, electronic devices can configure extended attributes to create new task types and configure hierarchical application control for these new task types based on the WBS standard. When configuring extended attributes, attributes can be configured according to the task categories in the WBS structure, extending the configuration based on business requirements. Attribute types can include text, numbers, time, relationships, attachments, etc.
[0064] It is evident that electronic devices can classify and manage task types by establishing a task type library and constructing a configurable task type library. Furthermore, when task types need to be expanded, they can be flexibly configured based on task attributes and application mode configured based on task management rules.
[0065] S104. Based on the task association type library, configure data type attribute information for the task type to form a data type.
[0066] After the task type is determined, the electronic device can also configure the attribute information of each data type to form a new data type. That is, based on the task association type library, the data type attribute information is configured for the task type to form a data type.
[0067] The task association type library can store multiple task types and data types, as well as the association relationships between task types and data types. After determining the task type, the electronic device can configure the data type based on that task type. For example, after obtaining the task type as task C, the data type corresponding to that task type, i.e., data type-03, can be determined based on the association relationship between the task type and the data type.
[0068] Similarly, for extended task types, after electronic devices configure extended attribute settings for decomposed tasks based on the basic task information data model to form extended task types, they can configure the attribute information of each extended task type and data type based on the constructed task-related data type library to form new data types. Furthermore, the task-related data type library can also be a configurable database, thereby supporting the extended configuration of data types that can be associated with different task inputs and outputs, and realizing flexible expansion of the associated data source.
[0069] As can be seen, by establishing a task-related data type library, it is possible to manage the input and output data types of the upstream and downstream of the decomposed task, and to configure the associative data types based on the task input attributes and task output attributes.
[0070] S105. For the task input attributes and task output attributes in the task type, configure the association by selecting the data type.
[0071] After the data type is formed, the electronic device can select the data type to associate the task input attributes and task output attributes in the task type, thereby establishing an association relationship between the task type corresponding to the decomposed task in the current management project and the data type of the extended data. That is, the electronic device can select the data type created in step S104 to associate the task input attributes and task output attributes in the task type created in step S103.
[0072] After the association configuration is performed, electronic devices can also establish a multi-dimensional complex task association model based on the association configuration relationship. The association model can be used to realize execution status tracking and task change impact analysis.
[0073] By applying the technical solutions of the above embodiments, the WBS-based multi-dimensional complex task association management method provided by the above embodiments can be applied to fields such as reactor research and development. Based on the WBS multi-dimensional complex task association relationship model, the method can comprehensively consider the task decomposition and association methods such as complex upstream and downstream business relationships, numerous association interfaces, and multiple association attributes. Under the premise of meeting the complex task relationships in the reactor research and development process, it supports task execution status tracking and task change impact analysis, thereby providing a basic data management model.
[0074] The method described above can support the creation of Work Breakdown Structure (WBS) data models for systems with complex multi-dimensional task relationships in design and production operations. It is particularly useful in application areas such as reactor development, where there is an urgent need for monitoring, visualization, and traceability of complex production processes involving complex upstream and downstream interface relationships, multiple interface layers, and diverse interface data types. By establishing a WBS task decomposition structure standard, it provides support for constructing complex tasks in project management, and by establishing task basic attribute specifications, it supports unified standard task attribute information. The method also provides a task type library, allowing for task expansion based on the characteristics of different business areas, and a task-related data type library, supporting the expansion of associative data types for different task inputs and outputs. Furthermore, it supports the creation of WBS data models for systems with complex multi-dimensional task relationships in design and production operations, and further guides the development of related application tools, demonstrating significant social and economic benefits.
[0075] In some embodiments, as a refinement and extension of the specific implementation of the above embodiments, in order to fully illustrate the specific implementation process of this embodiment, some embodiments of this application also provide a WBS multi-dimensional complex task association management method. Based on the association configuration performed in the above embodiments, this method can also support the on-demand creation of tasks and related data types, thereby forming a WBS-based multi-dimensional complex task association relationship model. For example... Figure 6 As shown, the method includes: S201. Obtain user demand data; S202. Create a new task based on the user demand data; S203. Based on the basic task information data model, perform extended attribute configuration on the new task to obtain the task type of the new task; S204. Based on the task association type library, configure data type attribute information for the task type of the new task to form a new data type.
[0076] S205. Establish a task association model based on the task type and data type of the new task.
[0077] After electronic devices can perform the association configuration of task types and data types, they can record the association relationships generated during the configuration process to construct a multi-dimensional complex task association relationship model based on Work Breakdown Structure (WBS). This WBS-based multi-dimensional complex task association relationship model can be used to maintain the association relationships between task types and data types.
[0078] When a user creates a new task based on actual needs, they can input user requirement data into the electronic device. After acquiring the user requirement data, the electronic device can create a new task based on it. Then, based on the basic task information data model, it performs extended attribute configuration on the new task to obtain the task type; and based on the task association type library, it configures data type attribute information for the task type of the new task to form a new data type.
[0079] After obtaining the task type and data type of the new task, the electronic device can update the established task association model based on the task type and data type of the new task, so that the constructed task association model can create tasks and related data types as needed and perform model updates, thereby knowing the subsequent task execution process.
[0080] In some embodiments, as a refinement and extension of the specific implementation of the above embodiments, and to fully illustrate the specific implementation process of this embodiment, some embodiments of this application also provide a multi-dimensional complex task association management method for WBS. Based on the association configuration in the above embodiments, this method can also display the target task, i.e., as shown... Figure 7 As shown, the method includes: S301. Record the association relationship between the task type and the data type in the association configuration; S302. Obtain the task display instruction used to display the target task; S303. In response to the task display instruction, query the associated information corresponding to the target task according to the association relationship; S304. Display the target task and the associated information.
[0081] After configuring the association between task types and data types, the electronic device can record the association between task types and data types and receive control commands input by the user. When the user inputs a task display command to show the target task, the device can respond to the task display command by querying the associated information corresponding to the target task based on the association relationship. The associated information includes data types associated with the task type corresponding to the target task, as well as related tasks of the target task.
[0082] For example, when a user clicks the option control corresponding to Task 1.3 in the project management interface, they can input a task display command to the electronic device to show Task 1.3. At this time, the electronic device can extract the identification information of the target task, i.e., task 1.3, from the task display command. Then, based on the identification information task 1.3, it obtains the association relationship obtained by Task 1.3 in the execution association configuration, and queries the data type associated with Task 1.3 based on the association relationship.
[0083] While retrieving the data types associated with the target task, the electronic device can also determine related tasks based on the task decomposition results of the target task. Related tasks are those decomposed tasks in the task decomposition results that have a logical or sequential relationship with the target task. For example, when the target task is task 1.3, the device can query the management project to which task 1.3 belongs, and based on the task decomposition results of the management project, determine the related tasks that have a logical relationship with task 1.3, namely topic 1.1 and task 1.4. Here, topic 1.1 is the next higher-level task in task 1.3, and task 1.4 is a downstream task of task 1.3 in terms of logical relationship.
[0084] In some embodiments, as a specific implementation of the WBS multi-dimensional complex task association management method described in the above embodiments, some embodiments of this application also provide a WBS multi-dimensional complex task association management system, such as... Figure 8 As shown, the system includes: The data acquisition module is used to acquire management project data, which includes at least one management project. The task decomposition module is used to decompose the management project data into task information based on a preset task decomposition structure standard. The task information includes multiple decomposed tasks divided according to task level and task control method. The task type determination module is used to determine the task type based on the task information. The task type includes a basic task type and an extended task type. The basic task type is the task type of the decomposed task extracted from the task type library. The extended task type is the task type obtained by configuring extended attributes of the decomposed task through the basic task information data model. The data type configuration module is used to configure data type attribute information for the task type based on the task association type library to form a data type; The association configuration module is used to perform association configuration for the task input attributes and task output attributes in the task type by selecting the data type.
[0085] By applying the technical solutions of the above embodiments, the WBS-based multi-dimensional complex task association management system provided in the above embodiments can acquire management project data through the data acquisition module. Then, the task decomposition module decomposes the management project data into task information based on a preset task decomposition structure standard. After the task type determination module determines the task type based on the task information, the data type configuration module can configure data type attribute information for the task type based on the task association type library to form a data type. This allows the association configuration module to configure associations for the task input and output attributes in the task type by selecting the data type. The system can comprehensively consider complex upstream and downstream business relationships, numerous association interfaces, and multiple association attributes, satisfying the complex task relationships in management projects. It provides basic data management functions to support task execution status tracking and task change impact analysis, thus solving the problem that the WBS method cannot display multi-dimensional data related to tasks.
[0086] It should be noted that other corresponding descriptions of the functional units involved in the WBS multi-dimensional complex task association management system provided in the embodiments of this application can be found in the corresponding descriptions in the WBS multi-dimensional complex task association management method provided in the above embodiments, and will not be repeated here.
[0087] This application also provides a computer device, specifically a personal computer, server, network device, etc. The computer device includes a bus, processor, memory, and communication interface, and may also include input / output interfaces and a display device. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database of the computer device stores location information. The network interface of the computer device is used for communication with external terminals via a network connection. When the computer program is executed by the processor, it implements the steps in the various method embodiments.
[0088] Those skilled in the art will understand that the structure of the computer device described above is only a partial structure related to the solution of this application, and does not constitute a limitation on the computer device to which the solution of this application is applied. A specific computer device may include more or fewer components, or combine certain components, or have different component arrangements.
[0089] In one embodiment, a computer-readable storage medium is also provided, which may be non-volatile or volatile, and a computer program is stored thereon, which, when executed by a processor, implements the steps in the above method embodiments.
[0090] In one embodiment, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.
[0091] 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, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.
[0092] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. 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 methods.
[0093] Any references to memory, database, or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may 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.
[0094] Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can take many forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).
[0095] The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchain. The processors involved in the embodiments provided in this application may be, but are not limited to, general-purpose processors, graphics processors, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc.
[0096] 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.
[0097] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.
Claims
1. A multi-dimensional complex task association management method based on WBS, characterized in that, The method includes: Acquire management project data, wherein the management project data includes at least one management project; Based on the preset task decomposition structure standard, the management project data is decomposed into task information, which includes multiple decomposed tasks divided according to task level and task control method. The task type is determined based on the task information. The task type includes a basic task type and an extended task type. The basic task type is the task type of the decomposed task extracted from the task type library. The extended task type is the task type obtained by configuring extended attributes of the decomposed task through the basic task information data model. Based on the task association type library, data type attribute information is configured for the task type to form a data type; For the task input attributes and task output attributes in the task type, the associated configuration is performed by selecting the data type.
2. The method according to claim 1, characterized in that, Based on a preset task decomposition structure standard, the managed project data is decomposed into task information, including: Obtain the preset task decomposition structure standard; Read the hierarchical decomposition standard from the preset task decomposition structure standard. The hierarchical decomposition standard includes at least one of the stage decomposition standard, topic decomposition standard, and task decomposition standard. According to the aforementioned hierarchical decomposition criteria, the management project data is decomposed into multiple decomposition tasks layer by layer.
3. The method according to claim 2, characterized in that, According to the aforementioned hierarchical decomposition criteria, the management project data is decomposed layer by layer into multiple decomposition tasks, including: Based on the stage decomposition criteria, stage information is extracted from the management project data, and the stage information includes at least one task stage. According to the aforementioned topic decomposition criteria, the task stage in the stage information is decomposed into topics to obtain topic information, which includes at least one task topic. Based on the task decomposition criteria, decomposed tasks are extracted from the task topics; Construct a task decomposition structure tree based on the stage information, the topic information, and the task information.
4. The method according to claim 2, characterized in that, The method further includes: Obtain sample project data in the current application field; Extract sample hierarchy information and sample task information from the sample project data; The hierarchical decomposition criteria are constructed based on the sample hierarchical information, and the task structure is constructed based on the sample task information; The hierarchical standard and the task structure are encapsulated to establish the preset task decomposition structure standard.
5. The method according to claim 1, characterized in that, The task type is determined based on the task information, including: Call the task type library, which is used to classify and manage the task types of decomposed tasks; Extract the task identification information of the decomposed task from the task information; Based on the task identification information, the task type of the decomposed task is matched in the task type library to obtain the basic task type.
6. The method according to claim 1, characterized in that, The task type is determined based on the task information, including: Call the basic task information data model, which is a configuration model developed based on task information standard specifications; Based on the basic task information data model, extended attribute configuration is performed on the decomposed tasks to form extended task types; Based on the preset task decomposition structure standard, hierarchical application control configuration is applied to the extended task types.
7. The method according to claim 6, characterized in that, The method further includes: Obtain sample task information from sample project data in the current application domain; Determine the extended attributes associated with the sample task information; Establish a task information standard specification based on the extended attributes and the sample task information; The basic task information data model is constructed based on the aforementioned task information standard specifications.
8. The method according to claim 1, characterized in that, The method further includes: Record the association relationship between the task type and the data type in the association configuration; Obtain the task display command used to display the target task; In response to the task display instruction, the association information corresponding to the target task is queried according to the association relationship; the association information includes data types that are associated with the task type corresponding to the target task and related tasks of the target task; Display the target task and the associated information.
9. The method according to claim 1, characterized in that, The method further includes: Obtain user demand data; Create a new task based on the user demand data; Based on the basic task information data model, the new task is configured with extended attributes to obtain the task type of the new task. Based on the task association type library, data type attribute information is configured for the task type of the new task to form a new data type. Establish a task association model based on the task type and data type of the new task.
10. A multi-dimensional complex task association management system based on WBS, characterized in that, The system includes: The data acquisition module is used to acquire management project data, which includes at least one management project. The task decomposition module is used to decompose the management project data into task information based on a preset task decomposition structure standard. The task information includes multiple decomposed tasks divided according to task level and task control method. The task type determination module is used to determine the task type based on the task information. The task type includes a basic task type and an extended task type. The basic task type is the task type of the decomposed task extracted from the task type library. The extended task type is the task type obtained by configuring extended attributes of the decomposed task through the basic task information data model. The data type configuration module is used to configure data type attribute information for the task type based on the task association type library to form a data type; The association configuration module is used to perform association configuration for the task input attributes and task output attributes in the task type by selecting the data type.