Multi-stage cooperative control and dynamic feedback system for project management
By using a multi-stage collaborative control and dynamic feedback system, the efficiency and quality issues of traditional project management methods in complex environments have been resolved. This has enabled standardized management and rational utilization of resources throughout the entire project lifecycle, thereby improving project success rates and customer satisfaction.
Patent Information
- Application Number
- CN202510943648.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-09
- Publication Date
- 2025-11-14
AI Technical Summary
Traditional project management methods cannot meet rapidly changing project needs and complex technical environments. They lack flexibility and real-time monitoring mechanisms, resulting in low project management efficiency and difficulty in ensuring quality.
It provides a multi-stage collaborative control and dynamic feedback system, including modules for requirements management, development management, test request management, test management, test case storage, bug management, release management, requirement change management, software system management, and statistical analysis. Through the collaborative work between modules, it achieves full lifecycle management of the project and clarifies the inputs, outputs, and operation processes of each stage.
It improves the efficiency and quality of project management, reduces the impact of human factors, ensures that projects are completed on time, with quality, and within budget, and supports project teams in achieving their goals efficiently.
Smart Images
Figure CN120950382A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of software project management, and more particularly to a multi-stage collaborative control and dynamic feedback system for project management. Background Technology
[0002] With the emergence of the concept of smart hospitals, various hospitals are exploring different approaches, using technologies such as big data, artificial intelligence, and the Internet of Things to form an information-based intelligent management model, thereby improving the work efficiency of medical staff and the medical experience of patients.
[0003] Smart hospitals typically include smart management projects for hospital administrators, smart service projects for patients, and smart healthcare projects for medical staff. Project development management encompasses the planning, organization, monitoring, and control of the entire project lifecycle, from planning to implementation. It covers the management of project scope, time, cost, and quality, ensuring projects are completed on time, to the required standard, and within budget. Project development management emphasizes the importance of teamwork, requirements analysis, and design, as well as the necessity of testing and quality assurance. Effective management can improve project success rates and customer satisfaction, while reducing project risks and costs, optimizing development processes, and enhancing the quality and efficiency of software development.
[0004] In today's era of rapid information technology development, project development is exhibiting increasing complexity. This complexity brings challenges to project management, and traditional project management methods are no longer sufficient to meet the rapidly changing project requirements and the ever-evolving technological environment. Therefore, there is an urgent need for a more efficient and intelligent project development management system to ensure the smooth progress and implementation of projects. Such a system needs to be able to flexibly adapt to various changes, provide real-time project monitoring and adjustment mechanisms, and ensure that projects maintain the right direction and pace in a dynamically changing environment. Summary of the Invention
[0005] The purpose of this invention is to provide a multi-stage collaborative control and dynamic feedback system for project management, in order to solve the problems mentioned in the background art.
[0006] To achieve the above-mentioned objectives, this invention provides a multi-stage collaborative control and dynamic feedback system for project management, comprising a requirements management module, a development management module, a test request management module, a test management module, and a test case storage module, wherein:
[0007] The requirements management module is used to create project requirements;
[0008] The development management module is used to create development tasks based on the project requirements.
[0009] The test submission management module is used to create test submissions based on the project requirements and the development tasks.
[0010] The test management module is used to create test tasks based on the test submission form and track the execution status of the test tasks; the test management module uses an adapter to extract test cases that are adapted to the test submission form to complete the corresponding test tasks.
[0011] The test case storage module is used to store and record all unit test cases corresponding to each unit task, so that they can be called by the test management module.
[0012] Furthermore, it also includes a bug management module, a release management module, a requirement change module, a software system module, and a statistical analysis module, among which:
[0013] The BUG management module is used to record, track, and manage defects found during the software development process;
[0014] The release management module is used to manage and track the release plans and release activities of software projects;
[0015] The requirement change module is used to manage and track requirement changes in software projects;
[0016] The software system module is used to manage and configure relevant information and personnel settings for each software system;
[0017] The statistical analysis module provides statistical and analytical functions for various data in the project internal control management system. Users can use this module to quickly understand the project's requirements, status, and progress, providing data support for project management and decision-making.
[0018] Furthermore, development tasks include unit tasks and integration tasks; the test submission management module is also used to create unit test submissions for unit tasks and integration test submissions for integration development tasks; the test management module is also used to call unit test cases adapted to unit test submissions, call integration test cases adapted to integration test submissions, and execute test tasks using unit test cases or integration test cases.
[0019] Furthermore, the integration task is related to at least one unit task. While calling the integration test cases, the test management module also calls the unit test cases adapted to the unit test forms of the unit tasks related to the integration task corresponding to the integration test form.
[0020] Furthermore, the integration test request form clearly defines the test objectives, which is used to clarify the unit tasks related to the integration task.
[0021] Furthermore, a mapping relationship is established between each unit test case and its corresponding unit test form, and an index of unit test cases is created using keywords.
[0022] Furthermore, the test management module includes an adapter, which is used to calculate the relevance of the integration test order and the unit test order based on semantics from at least two evaluation dimensions, and to use the unit test cases corresponding to the unit test orders with a relevance greater than a threshold as the unit test cases adapted to the integration test order.
[0023] Furthermore, the main body of the adapter is a large language model, which integrates the test requirement description on the test submission form through semantic analysis, and extracts the relevant task units or unit test cases from the integrated test submission form; if the relevant part is a task unit, then all unit test cases corresponding to the task unit are called; if the relevant part is a unit test case, then the corresponding unit test case is called.
[0024] Furthermore, the evaluation dimensions include correlation between the test version, test environment, task entity, operation type, keyword coverage, and task logic, wherein:
[0025] Version association is a calculation of the association degree of unit test cases used in multiple tests of the same requirement for the same task unit; the larger the version number, the higher the association degree.
[0026] Test environment correlation refers to the degree of correlation when the test environments are the same, which is greater than the degree of correlation when the test environments are different.
[0027] Task entity association refers to the degree of association between pointers and unit tasks;
[0028] Operation type association refers to the calculation of the degree of association for test operations;
[0029] Keyword coverage involves comparing the descriptions of test requirements in the integration test request form with the descriptions of test requirements in other unit test requests forms using keywords.
[0030] The semantic logic between tasks is analyzed through task logic association analysis. The semantic logic includes causality, parallelism, progression, and inclusion.
[0031] Furthermore, different evaluation dimensions are weighted to adjust the emphasis of correlation calculation according to actual needs and optimize the calling logic of the adapter to match more accurate test cases.
[0032] Compared with existing technologies, this system and method have the following advantages:
[0033] Each module collaborates across its corresponding project phases: the requirements management module works with the development management module, dynamically feeding back project requirements to the development management module after creation to trigger corresponding tasks; the development management module provides feedback, and the requirements management module collaborates with the test request management module, dynamically feeding back development tasks to the test request management module after creation to trigger corresponding tasks; the test request management module collaborates with the test management module, dynamically feeding back test requests to the test management module after creation to trigger corresponding tasks. The overall system standardizes and regulates all aspects of the project from requirements to testing, clearly defining the inputs, outputs, and operational processes for each phase, supporting full lifecycle management of project requirements. This helps improve the efficiency and quality of project management, reduces the impact of human factors, and makes project management more scientific, rigorous, and transparent. Simultaneously, unified management of project requirements, development tasks, test requests, and test tasks allows for the rational allocation of project resources and improves resource utilization efficiency. Attached Figure Description
[0034] Figure 1 This is a structural diagram of a multi-stage collaborative control and dynamic feedback system for project management. Detailed Implementation
[0035] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0036] like Figure 1 The diagram shown is a system structure diagram of the present invention. This application provides a multi-stage collaborative control and dynamic feedback system for project management, including: a requirements management module, a development management module, a test request management module, and a test management module, wherein:
[0037] The requirements management module is used to create project requirements;
[0038] The development management module is used to create development tasks based on project requirements.
[0039] The Test Submission Management module is used to create test submissions based on project requirements and development tasks;
[0040] The test management module is used to create test tasks based on the test submission form and track the execution status of the test tasks; the test management module schedules the appropriate test cases according to the test submission form to complete the corresponding test tasks.
[0041] The test case storage module is used to store and record all unit test cases corresponding to each unit task, so that they can be called by the test management module.
[0042] In this embodiment, the requirements management module enables the project team to clearly define project requirements, transforming vague business needs into clear and actionable project requirements documents. This helps all parties involved in the project (such as clients, project managers, developers, testers, etc.) reach a consensus on project goals and scope, avoiding project deviations or failures caused by inconsistent understanding of requirements.
[0043] During project execution, requirements may change. Project requirements created through this module can serve as a baseline, facilitating the management and traceability of requirement changes. It provides a clear understanding of which development tasks, test requests, and testing tasks are based on which requirements, ensuring timely adjustments to subsequent development and testing work when requirements change.
[0044] The development management module creates development tasks based on project requirements, breaking them down into specific development work units and allocating them appropriately to developers. Project managers can use this module to monitor the progress of development tasks, promptly identify problems and risks during development, and take appropriate measures to resolve them, ensuring that development work proceeds as planned.
[0045] Clearly defined development tasks help developers focus on specific tasks, avoiding confusion and duplication of effort. Furthermore, creating development tasks based on project requirements ensures alignment between development work and project goals, improving both efficiency and quality.
[0046] The test submission management module creates test submission forms based on project requirements and development tasks, providing a clear test scope and objectives for the testing work. The test management module creates test tasks based on the test submission forms and schedules appropriate test cases, enabling comprehensive and systematic testing of the software, timely discovery of defects and problems, and ensuring software quality.
[0047] The test management module tracks the execution of test tasks and provides real-time feedback on test progress and results, enabling project managers and relevant personnel to intuitively understand the progress of the testing work. Simultaneously, the correlation between test tasks and test requests, project requirements, and development tasks ensures the traceability of the testing process, facilitating the analysis of test results and problem localization.
[0048] Through the collaborative work of these modules, the system enables the management of the entire lifecycle of software development projects, supports project teams in efficiently achieving project goals, and improves the efficiency and transparency of project management.
[0049] The requirements management module includes functions such as requirements creation, evaluation, allocation, status updates, and historical record viewing, as detailed below:
[0050] 1. Requirements Creation:
[0051] Users can create new requirements through the requirements management module.
[0052] Enter basic information about the requirement, such as requirement number, OA order number, requirement name, systems involved, requirement specialist, priority, etc.
[0053] Submit your request, and the system will automatically generate the registration date.
[0054] 2. Needs assessment:
[0055] The requirements specialist assesses newly created requirements.
[0056] Prioritize based on the complexity and urgency of the needs.
[0057] Update the status of the requirements, such as pending confirmation of technical feasibility or pending product team review.
[0058] 3. Demand Allocation:
[0059] Based on the systems involved and the priority of the requirements, the requirements are assigned to the appropriate personnel.
[0060] Update the information of those whose requests have not yet been processed.
[0061] 4. Requirement status update:
[0062] After the handler completes the processing of the request, they update the status of the request.
[0063] The status can be under investigation, pending product team review, evaluated, terminated, etc.
[0064] 5. View historical request records:
[0065] Users can view the history of requirements, including information such as the creation, evaluation, allocation, and status updates of requirements.
[0066] The search bar allows you to quickly locate records that meet your specific needs.
[0067] 6. View requirements details:
[0068] Users can click the "Details" button in the list of requirements to view the detailed information of the requirements.
[0069] Detailed information includes the person who created the requirement, the creation time, the person who handled it, the processing time, and the description of the requirement.
[0070] 7. Need more operations:
[0071] Users can perform more operations on their requirements through the "More" button, such as editing, deleting, and exporting requirements.
[0072] The development management module includes functions such as task creation, assignment, status update, progress tracking, and historical record viewing, as detailed below:
[0073] 1. Task Creation:
[0074] Users can create new tasks through the development and management module.
[0075] Enter the basic information of the task, such as task number, task name, requirement number, system, and coding artist.
[0076] Submit the task, and the system will automatically generate the registration time.
[0077] 2. Task allocation:
[0078] Tasks are assigned to the appropriate coding artists based on their system and priority.
[0079] Update the coding artist information for the task.
[0080] 3. Task status update:
[0081] After completing a task, the coding artist updates the task status.
[0082] The status can be under development, developed, submitted for testing, under testing, tested, released, terminated, etc.
[0083] 4. Task progress tracking:
[0084] Users can view the progress of tasks, including registration time, development completion time, etc.
[0085] The task list allows you to quickly understand the current status and progress of tasks.
[0086] 5. View task history:
[0087] Users can view the task history, including information such as task creation, assignment, and status updates.
[0088] The search bar allows you to quickly locate records for specific tasks.
[0089] 6. View task details:
[0090] Users can click the "Details" button in the task list to view detailed task information.
[0091] Detailed information includes the task creator, creation time, handler, processing time, and task description.
[0092] 7. More Task Operations:
[0093] Users can perform more operations on tasks through the "More" button, such as editing tasks, deleting tasks, and exporting tasks.
[0094] The test order management module includes functions such as test order creation, allocation, status update, progress tracking, and historical record viewing, as detailed below:
[0095] 1. Test order creation:
[0096] Users can create new test orders through the test order management module.
[0097] Enter the basic information of the test form, such as the system it belongs to, its name, and the person submitting the test.
[0098] Submit a test request, and the system will automatically generate the latest test submission time.
[0099] 2. Test order allocation:
[0100] Based on the system to which the test order belongs and its priority, the test order is assigned to the appropriate tester.
[0101] Update the information of the person who submitted the test order.
[0102] 3. Test order status update:
[0103] After completing the test, the tester updates the status of the test form.
[0104] The status can be tested, untested, or bug found.
[0105] 4. Test order progress tracking:
[0106] Users can view the progress of test orders, including the number of tests completed, the number of tests not yet completed, and the number of bugs.
[0107] The test order list allows you to quickly understand the current status and progress of a test order.
[0108] 5. View test record history:
[0109] Users can view the history of test orders, including information such as the creation, assignment, and status updates of test orders.
[0110] The search bar allows you to quickly locate records for a specific test order.
[0111] 6. See test order details:
[0112] Users can click the "Details" button in the test order list to view the detailed information of the test order.
[0113] Detailed information includes the creator of the test order, creation time, handler, processing time, and test order description.
[0114] 7. Additional test orders:
[0115] Users can add to the test order using the "Append" button, such as adding new test cases or updating test content.
[0116] The test management module includes functions such as test task creation, assignment, status update, progress tracking, and historical record viewing, as detailed below:
[0117] 1. Test task creation:
[0118] Users can create new test tasks through the test management module.
[0119] Enter the basic information of the test task, such as task number, task name, requirement number, latest test submission form, and system.
[0120] Submit a test task, and the system will automatically generate the test submission time.
[0121] 2. Test task allocation:
[0122] Based on the system to which the test task belongs and its priority, the test task is assigned to the appropriate tester.
[0123] Update the tester information for the test task.
[0124] 3. Test task status update:
[0125] After completing the test, the tester updates the status of the test task.
[0126] The status can be under testing, pending development and modification, pending review and testing, tested, released, etc.
[0127] 4. Test task progress tracking:
[0128] Users can view the progress of test tasks, including test completion time and status.
[0129] The test task list allows you to quickly understand the current status and progress of test tasks.
[0130] 5. View test task history:
[0131] Users can view the history of test tasks, including information such as the creation, assignment, and status updates of test tasks.
[0132] The search bar allows you to quickly locate records for specific test tasks.
[0133] 6. View test task details:
[0134] Users can click the "Details" button in the test task list to view detailed information about the test tasks.
[0135] Detailed information includes the creator of the test task, creation time, handler, processing time, and test task description.
[0136] 7. More operations for test tasks:
[0137] Users can perform more operations on test tasks through the "More" button, such as editing test tasks, deleting test tasks, and exporting test tasks.
[0138] In other embodiments, the system also includes: a bug management module, a release management module, a requirement change module, a software system module, and a statistical analysis module.
[0139] The bug management module is used to record, track, and manage defects discovered during software development. It includes functions for reporting, assigning, fixing, verifying, and closing bugs, as detailed below:
[0140] 1. Bug Report:
[0141] Users can report new bugs through the bug management module.
[0142] Enter basic information about the bug, such as bug name, associated task, test time, and coding artist.
[0143] When you submit a bug report, the system will automatically generate a record.
[0144] 2. Bug allocation:
[0145] Based on the task to which the bug belongs and its severity, the bug is assigned to the appropriate developer or tester.
[0146] Update the information of the person who handled the bug.
[0147] 3. Bug fixes:
[0148] After the bug fixer completes the bug fix, they update the bug's status.
[0149] The status can be fixed, pending verification, etc.
[0150] 4. Bug verification:
[0151] Testers verify the fixed bugs to confirm that they have been correctly fixed.
[0152] Update the status of bugs, such as verified or closed.
[0153] 5. Bug status update:
[0154] Users can view the status of bugs, including the reporting time, fixing time, and verification time.
[0155] The bug list allows you to quickly understand the current status and progress of bugs.
[0156] 6. View bug history:
[0157] Users can view the bug history, including bug reports, assignments, fixes, verifications, and other information.
[0158] The search bar allows you to quickly locate records of specific bugs.
[0159] 7. For bug details, please see:
[0160] Users can click the "Details" button in the bug list to view detailed information about the bug.
[0161] Detailed information includes the person who reported the bug, the reporting time, the person who handled it, the handling time, and the bug description.
[0162] 8. More bug fixes:
[0163] Users can perform more operations on the bug through the "More" button, such as editing the bug, deleting the bug, and exporting the bug.
[0164] The release management module is used to manage and track software project release plans and release activities. It includes functions such as creating, approving, executing, and viewing release plans, as detailed below:
[0165] 1. Release plan creation:
[0166] Users can create new release plans through the release management module.
[0167] Enter the basic information of the release plan, such as the system, name, planned upgrade (preview and official version), version number, etc.
[0168] Submit a release plan, and the system will automatically generate a record.
[0169] 2. Approval of the release plan:
[0170] Based on the system to which the release plan belongs and its importance, the release plan will be submitted to the appropriate approver.
[0171] Update the approval status of the release plan.
[0172] 3. Implementation of the plan:
[0173] Once the release plan is approved, the release activity will be carried out.
[0174] Update the execution status of the release plan.
[0175] 4. Update the release plan status:
[0176] Users can view the status of the release plan, including the planned upgrade time, version number, number of tasks, and current stage.
[0177] The release list allows you to quickly understand the current status and progress of the release plan.
[0178] 5. View the history of published plans:
[0179] Users can view the history of release plans, including information on the creation, approval, and execution of release plans.
[0180] The search bar allows you to quickly locate records for specific publishing plans.
[0181] 6. See details of the release plan:
[0182] Users can click the "Details" button in the release list to view the release plan's details.
[0183] Detailed information includes the creator of the release plan, creation time, handler, processing time, and release plan description.
[0184] 7. Further steps for publishing the plan:
[0185] Users can perform more operations on the release plan through the "More" button, such as editing the release plan, deleting the release plan, and exporting the release plan.
[0186] The Requirements Change module is used to manage and track requirements changes in software projects. It includes functions for creating, approving, implementing, and viewing change requests, as detailed below:
[0187] 1. Change request creation:
[0188] Users can create new requirement change requests through the requirement change module.
[0189] Enter the basic information of the change request, such as the name of the change, the relevant requirement, and the type.
[0190] Submit a change request, and the system will automatically generate the application time.
[0191] 2. Change request approval:
[0192] Based on the scope and urgency of the change request, submit the change request to the appropriate approver.
[0193] Update the approval status of the change request.
[0194] 3. Implementation of the changes:
[0195] After the change request is approved, the change is implemented.
[0196] Update the implementation status of the change request.
[0197] 4. Status update:
[0198] Users can view the status of change requests, including the application time, applicant, and status.
[0199] The change list allows you to quickly understand the current status and progress of change requests.
[0200] 5. View change history:
[0201] Users can view the history of change requests, including information on the creation, approval, and implementation of change requests.
[0202] The search bar allows you to quickly locate records for specific change requests.
[0203] 6. View change details:
[0204] Users can click the "Details" button in the change list to view the detailed information of the change request.
[0205] Detailed information includes the creator of the change request, the creation time, the handler, the processing time, and the description of the change request.
[0206] 7. Change more operations:
[0207] Users can perform further operations on change requests through the "More" button, such as editing, deleting, or exporting the change request.
[0208] The software system module is used to manage and configure relevant information and personnel settings for each software system. It includes functions such as viewing and editing system information, as well as assigning personnel and setting roles, as detailed below:
[0209] 1. View system information:
[0210] Users can view detailed information about each software system.
[0211] This includes the system name, project team leader, project leader, project manager, etc.
[0212] 2. System Information Editing:
[0213] Users can modify relevant information about the software system using the editing function.
[0214] The revised information needs to go through an approval process.
[0215] 3. Staffing:
[0216] Users can assign roles such as project team leader, project manager, etc. to each software system.
[0217] You can assign specific roles to people such as searchers, publishers, and data group reviewers.
[0218] 4. System type and sequence settings:
[0219] Users can label the system type (e.g., self-developed, third-party).
[0220] You can set the display order of the system.
[0221] 5. View by system category:
[0222] Users can view the system list by system type.
[0223] It supports filtering by category, such as all, self-developed systems, and third-party systems.
[0224] 6. View system details:
[0225] Users can click on the system name to view detailed system information.
[0226] Detailed information includes a detailed description of the system and contact information for relevant personnel.
[0227] 7. More operations:
[0228] Users can perform more operations on the system through more buttons, such as deleting the system and exporting system information.
[0229] The statistical analysis module provides statistical and analytical functions for various data within the project internal control management system. Users can quickly understand the project's requirement status and progress through this module, providing data support for project management and decision-making. Its functions include requirement order progress statistics, overall requirement status, details of requirements awaiting approval, and details of newly submitted requirements, as detailed below:
[0230] 1. Select the statistical time interval:
[0231] Users select the time interval for which they want to conduct statistics using the time selector.
[0232] The system generates corresponding statistical reports based on the selected time interval.
[0233] 2. View the progress of all request orders:
[0234] Users can view the progress of all request orders, including statuses such as not started, in progress, and completed.
[0235] Filter and sort by criteria such as the specialist in charge of the requirement and the name of the requirement.
[0236] 3. Review the overall demand situation for this week:
[0237] Users can view the overall status of all requests this week, including statuses such as new requests, pending review, new submissions, signed agreements, and unsigned agreements.
[0238] Filter and sort by dimensions such as demand specialist and status.
[0239] 4. View the details of requests pending review this week:
[0240] Users can view the details of requests pending review this week.
[0241] This includes information such as the name of the requirement, the systems involved, and the priority.
[0242] 5. View the details of newly submitted requirements this week:
[0243] Users can view details of newly submitted requests this week.
[0244] This includes information such as the name of the requirement, the systems involved, and the priority.
[0245] 6. Export statistical reports:
[0246] Users can export statistical reports to Excel, PDF, and other formats for further analysis and archiving.
[0247] 7. Printing statistical reports:
[0248] Users can print out the statistical reports for easy offline viewing and sharing.
[0249] In one embodiment, the development task includes unit tasks and integration tasks; the test submission management module is also used to create unit test submissions for unit tasks and integration test submissions for integration development tasks; the test management module is also used to call unit test cases adapted to unit test submissions, call integration test cases adapted to integration test submissions, and execute test tasks using unit test cases or integration test cases.
[0250] A unit task refers to the inspection and verification of the smallest testable unit in software. In program design, the smallest unit task can be a function or a class. For example, consider a hospital's function to calculate the total price of medicines. By creating a test order for this unit task, we can verify whether it can correctly calculate the total price under different input quantities and unit prices of medicines. Based on this test order, we can call unit test cases. These unit test cases clearly define the specific test item as the total price calculation test, the test steps as inputting the quantity of medicines, inputting the unit price of medicines, and clicking the checkout button, the test data as such as the quantity of medicines, the name of medicines, and the amount, and the expected result as outputting the total price.
[0251] Integration tasks assemble unit tasks. The purpose of creating test orders for integration tasks is mainly to check whether the interfaces between modules are correct and whether the integrated module unit tasks can work properly. For example, the pharmaceutical supplier management module and the order management module can be integrated and tested as a single task. A test order can be created to verify whether the pharmaceutical inventory can be updated correctly when a user places an order.
[0252] In this embodiment, unit test cases and integration test cases can be pre-built by software testers for the target software; they can also be obtained after preliminary screening from a test case set based on the target software's attribute information; or they can be obtained by multiple test case writers writing them individually for the target software. This embodiment does not impose any limitations.
[0253] In one embodiment, the integration task is related to at least one unit task. While calling the integration test cases, the test management module also calls the unit test cases adapted to the unit test forms of the unit tasks related to the integration task corresponding to the integration test form.
[0254] Because integration tasks may be related to at least one unit task. For example, in a medical system, the requirement stipulates that users can add medicines to their shopping cart. In this case, unit task testing will write test cases for the single module that implements the "add medicines to cart" function (such as the shopping cart service module) to verify the basic functionality of the module. Integration task testing, on the other hand, will consider whether the "add medicines to cart" function still works properly when the module works in conjunction with other related modules (such as the medicine management module and the user account module). Both types of test cases revolve around this requirement.
[0255] Therefore, integration test cases can be built upon unit test cases. Once a single module passes unit testing, the approach of some unit test cases can be reused during integration testing to verify the functionality of the integrated modules. For example, if unit testing verifies the processing logic of a function for normal input data, integration testing can further verify whether this function still processes the same normal input data correctly when working with other functions. Therefore, if test cases from related unit tasks can be invoked during the testing of an integration task, it helps to accelerate the creation of integration test cases suitable for the integration task.
[0256] However, each task undergoes multiple rounds of testing, and different tasks may be assigned to different personnel. For example, the testing of an integration task might be assigned to a tester who is not responsible for its related unit tasks, causing the tester of the integration task to need to re-examine the processing logic. In other words, due to different personnel's familiarity with the project or other reasons, problems such as poor project testing efficiency and low test case reusability can easily occur.
[0257] In this embodiment, the test management module will first attempt to call integration test cases, which may or may not exist. Then, it will attempt to call the unit test cases of the relevant unit tasks on the integration test submission form as a reference, from which some or all of the data or code can be used to build or improve the integration test cases.
[0258] In one embodiment, the integration test request form clearly defines the testing objective, from which the related unit tasks can be inferred. For example, when developing an online payment system, various scenarios such as normal payment, payment failure, duplicate payment, and payment redirection need to be included. These descriptions on the integration test request form correspond to different unit tasks, thereby allowing the relevant unit test cases to be invoked.
[0259] In one embodiment, each unit task may correspond to multiple different test cases because their testing objectives may differ. For ease of management, a test case storage module is set up within the system to store and record all unit test cases corresponding to each unit task, for use by the test management module. To clarify the requirements of each unit test case for quick subsequent understanding, a mapping relationship is established between each unit test case and its corresponding unit test request form. An index of unit test cases is created using keywords, simplifying the test items associated with each unit test case.
[0260] In one embodiment, the test management module includes an adapter, which is used to calculate the correlation between the integration test order and the unit test order based on semantics from at least two evaluation dimensions, and to use the unit test cases corresponding to the unit test orders with a correlation greater than a threshold as the unit test cases adapted to the integration test order; wherein, the evaluation dimensions include test version correlation, test environment correlation, task entity correlation, operation type correlation, keyword coverage, and task logic correlation.
[0261] In this embodiment, the adapter's core is a large language model. It integrates the test requirements description on the test request form through semantic analysis, extracting relevant task units or unit test cases from the form. If the relevant element is a task unit, it calls all corresponding unit test cases. If the relevant element is a unit test case, it calls the corresponding unit test case.
[0262] The adapter's calling logic calculates the correlation between the integration test case and other unit test cases from multiple evaluation dimensions, and compares the correlation with a preset threshold. If the correlation is greater than the threshold, the test case is called; if it is less than the threshold, the test case is not called.
[0263] In the evaluation dimensions, the test version correlation calculates the correlation degree between unit test cases used in multiple test submissions for the same requirement within the same task unit. The later the version and the larger the version number, the higher the correlation degree. It should be noted that the version number needs to be normalized to eliminate the influence of the version number.
[0264] Test environment correlation refers to the degree of correlation when the test environments are the same, which is greater than the degree of correlation when the test environments are different.
[0265] Task entity association refers to the calculation of the degree of association between unit tasks. When descriptions such as "payment" and "inventory" appear in the integration test request, it can be determined that the associated unit tasks include drug management and payment management. Here, a knowledge graph approach can be used, with each unit task as an entity, to calculate the semantic degree of association using the graph relationships. For example, the settlement module and the payment module have a certain degree of association in the knowledge graph. When "payment" appears in the integration test request, the payment task and the settlement task are assigned a degree of association, with the payment task having a higher degree of association than the settlement task.
[0266] Operation type association refers to the calculation of the degree of association between test operations. For example, when an operation description of deleting items from the shopping cart appears, it can be determined that the integration test order is associated with the shopping cart module, and also associated with operations such as modifying the quantity of items in the shopping cart and adding items to the shopping cart.
[0267] Keyword coverage involves comparing the descriptions of test requirements in the integration test request form with those in other unit test requests using keywords. The presence of many identical or synonymous words usually indicates a high degree of relevance. Keywords are key words in the task description that reflect the core theme of the task.
[0268] Task logical association analysis examines the semantic logic between tasks, such as causal, parallel, progressive, and inclusive relationships. These logical relationships reflect the semantic tightness of the tasks. This association analysis can be combined with the aforementioned knowledge graph. For example, a payment task can only be initiated after settlement is completed, and the inventory level will change after payment is completed, indicating that the payment task is related to the settlement task and the inventory management task.
[0269] In this embodiment, different evaluation dimensions are weighted to adjust the emphasis of correlation calculation according to actual needs and optimize the calling logic of the adapter to match more accurate test cases.
[0270] The modules in the aforementioned multi-stage collaborative control and dynamic feedback device for project management can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the computer device's memory as software, so that the processor can invoke and execute the corresponding operations of each module.
[0271] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.
Claims
1. A multi-stage collaborative control and dynamic feedback system for project management, characterized in that, It includes a requirements management module, a development management module, a test submission management module, a test management module, and a test case storage module, among which: The requirements management module is used to create project requirements; The development management module is used to create development tasks based on the project requirements. The test submission management module is used to create test submissions based on the project requirements and the development tasks. The test management module is used to create test tasks based on the test submission form and track the execution status of the test tasks; the test management module uses an adapter to extract test cases that are adapted to the test submission form to complete the corresponding test tasks. The test case storage module is used to store and record all unit test cases corresponding to each unit task, so that they can be called by the test management module.
2. The multi-stage collaborative control and dynamic feedback system for project management according to claim 1, characterized in that, It also includes a bug management module, a release management module, a requirement change module, a software system module, and a statistical analysis module, among which: The BUG management module is used to record, track, and manage defects found during the software development process; The release management module is used to manage and track the release plans and release activities of software projects; The requirement change module is used to manage and track requirement changes in software projects; The software system module is used to manage and configure relevant information and personnel settings for each software system; The statistical analysis module provides statistical and analytical functions for various data in the project internal control management system. Users can use this module to quickly understand the project's requirements, status, and progress, providing data support for project management and decision-making.
3. The multi-stage collaborative control and dynamic feedback system for project management according to claim 1, characterized in that, Development tasks include unit tasks and integration tasks; the test submission management module is also used to create unit test submissions for unit tasks and integration test submissions for integration development tasks; the test management module is also used to call unit test cases adapted to unit test submissions, call integration test cases adapted to integration test submissions, and execute test tasks using unit test cases or integration test cases.
4. The multi-stage collaborative control and dynamic feedback system for project management according to claim 3, characterized in that, An integration task is associated with at least one unit task. While calling the integration test cases, the test management module also calls the unit test cases adapted to the unit test forms of the unit tasks associated with the integration task.
5. The multi-stage collaborative control and dynamic feedback system for project management according to claim 1, characterized in that, The integration test request form clearly defines the test objectives, which is used to clarify the unit tasks related to the integration task.
6. The multi-stage collaborative control and dynamic feedback system for project management according to claim 1, characterized in that, Establish a mapping relationship between each unit test case and its corresponding unit test form, and create an index of unit test cases using keywords.
7. The multi-stage collaborative control and dynamic feedback system for project management according to claim 1, characterized in that, The test management module includes an adapter, which is used to calculate the relevance of integration test orders and unit test orders based on semantics from at least two evaluation dimensions, and to use the unit test cases corresponding to unit test orders with a relevance greater than a threshold as unit test cases adapted to integration test orders.
8. The multi-stage collaborative control and dynamic feedback system for project management according to claim 7, characterized in that, The adapter's core is a large language model that integrates the test requirements description on the test request form through semantic analysis, extracting relevant task units or unit test cases from the integrated test request form. If the relevant task unit is involved, all unit test cases corresponding to that task unit are invoked; if the relevant unit test case is involved, the corresponding unit test case is invoked.
9. The multi-stage collaborative control and dynamic feedback system for project management according to claim 7, characterized in that, The evaluation dimensions include correlation between the test version, test environment, task entity, operation type, keyword coverage, and task logic, among which: Version association is a calculation of the association degree of unit test cases used in multiple tests of the same requirement for the same task unit; the larger the version number, the higher the association degree. Test environment correlation refers to the degree of correlation when the test environments are the same, which is greater than the degree of correlation when the test environments are different. Task entity association refers to the degree of association between pointers and unit tasks; Operation type association refers to the calculation of the degree of association for test operations; Keyword coverage involves comparing the descriptions of test requirements in the integration test request form with the descriptions of test requirements in other unit test requests forms using keywords. The semantic logic between tasks is analyzed through task logic association analysis. The semantic logic includes causality, parallelism, progression, and inclusion.
10. The multi-stage collaborative control and dynamic feedback system for project management according to claim 7, characterized in that, By assigning weights to different evaluation dimensions, the emphasis of correlation calculation can be adjusted according to actual needs, and the calling logic of the adapter can be optimized to match more accurate test cases.