Rail transit integrated project engineering general use case set maintenance method, medium and device

Abstract

The invention relates to a rail transit integrated project engineering general use case set maintenance method, a medium and a device, and the method comprises the steps: obtaining an engineering general use case set under a current baseline, injecting a new demand description, carrying out the fuzzy matching of the new demand description, covering the new demand description, and obtaining a use case set draft; obtaining an implementation attribute of a function associated with each use case, and performing product design attribute interaction and strategy optimization on the use case set draft to obtain a strategy optimization use case set; extracting data configuration information of a function associated with each use case, and adjusting a test strategy of the strategy optimization use case set to obtain a test strategy use case set; obtaining defect records of each use case, performing statistical analysis, and perfecting and simplifying the test strategy use case set to obtain an optimized engineering general use case set; and taking the optimized engineered general use case set as the engineered general use case set under the new baseline, and completing maintenance of the engineered general use case set. Compared with the prior art, the maintenance efficiency is remarkably improved.

Description

Technical Field

[0001] This invention relates to the field of rail transit, and in particular to a method, medium, and device for maintaining a general use case set for integrated rail transit projects. Background Technology

[0002] Urban rail transit systems connect major cities. With the maintenance and upgrading of older lines and the continuous increase in new projects and demands, signaling system technology is becoming increasingly complex. The general test case sets for project engineering are also constantly iterating and upgrading, leading to a continuous increase in the size and complexity of standard test case sets in terms of the number of test cases, test case steps, and test case scenarios. This results in low efficiency and poor effectiveness of factory testing execution. To reduce costs and increase efficiency, and improve the quality and efficiency of factory testing execution in engineering projects, a test case maintenance device and method are needed to effectively streamline and optimize the large test case sets accumulated over many years, improve the effectiveness of factory test case sets, and thus achieve cost reduction and efficiency improvement in the testing phase of engineering projects.

[0003] The upgrade and maintenance of the current project's general test case set (including SYS confidence test, ATC confidence test, ATS confidence test, CI confidence test, DCS confidence test, and IOM confidence test) are triggered by front-end input. There are three main front-end inputs: 1) Add corresponding engineering test cases based on new product iteration requirements; 2) Based on the product defect repair iteration and data defect correction iteration, improve defect-related use cases or add new use cases; 3) Improve the test scenarios and add test cases according to the specific requirements of the new project.

[0004] The current project's maintenance of general test case sets lacks regular simplification and optimization strategies, resulting in increasingly large, cumbersome, and redundant test cases. This significantly increases test execution costs and negatively impacts test efficiency and quality. Specific manifestations are as follows: 1) The project's general engineering use case set is not directly linked to the product software design and implementation method. This prevents efficient maintenance, simplification, and optimization of the project's general engineering use case set from a top-down perspective. For example, if a function has changed from an engineering data configuration implementation process to a pure product software layer implementation, the project's general engineering use case set cannot obtain the changes in a timely manner because it is not integrated with the front-end process. This results in a lack of timely optimization of the use case strategy and a waste of manpower in engineering testing.

[0005] 2) The project's general engineering test case set and the data creation process and internal data verification strategies during the project's data phase are not effectively linked. The strategy optimization of the general engineering test cases was not carried out in a timely manner, resulting in duplication of test execution and wasted execution resources. For example, data traversal test items are automatically generated by tools at the data level, yet the project's general engineering test case set still performs traversal testing. The testing strategy in the project's general engineering test case set should be changed to sampling testing instead of tool-generated data. Alternatively, if the front-end self-testing phase can already implement partial data traversal testing, the downstream project's general engineering test case set still performs repetitive traversal testing. All of these lead to a large number of repetitive traversal tests, resulting in wasted manual execution.

[0006] 3) There are a large number of test cases that have not been found for a long time (greater than or equal to 5 years). These test cases need to be optimized and streamlined to find defects and improve test quality and efficiency.

[0007] 4) The failure to establish a mechanism for regularly triggering the simplification and optimization of the engineering common test case set in line with the product baseline resulted in inaccurate common test case set testing strategies.

[0008] For example, patent application CN118860881A discloses a test case management system, method, and storage medium based on an AI model, which is a technical solution for automatically generating and optimizing test cases through a large AI model. This method extracts key information from requirement documents through a data processing module, generates initial test cases based on a test scenario database through a machine learning module, and optimizes the test cases based on historical test cases and defect data through a test case optimization module to obtain a continuously streamlined test case set. However, this method can only achieve general test case optimization based on requirement text and historical defect data. It cannot establish a direct connection with the product software implementation method, engineering data verification strategy, and baseline version. It cannot identify and streamline test case redundancy caused by product design changes, engineering data tool traversal verification strategies, and long-term stable functional modules in urban rail transit signaling systems. Furthermore, it cannot form a periodic automatic optimization mechanism bound to the product baseline. Therefore, it cannot effectively solve the core problems of increasingly large, cumbersome, and costly repetitive execution of engineering general test case sets, as well as low testing efficiency. Summary of the Invention

[0009] The purpose of this invention is to overcome the shortcomings of the existing technology and provide a method, medium and device for maintaining a general use case set for integrated rail transit projects, which significantly improves the maintenance efficiency of the general use case set for integrated rail transit projects.

[0010] The objective of this invention can be achieved through the following technical solutions: A method for maintaining a general use case set in an integrated rail transit project includes the following steps: Obtain the set of common engineering use cases under the current baseline and inject the new requirement description; The new requirement description is fuzzy matched with the engineering general use case set under the current baseline to obtain the fuzzy matching result. The new requirement description is then covered according to the fuzzy matching result to obtain a draft use case set that fully covers the new requirement description. Obtain the implementation attributes of the functions associated with each use case in the current baseline engineering general use case set, and perform product design attribute interaction and strategy optimization on the use case set draft based on the implementation attributes of the functions associated with each use case to obtain a strategy-optimized use case set based on product design attributes; Extract the data configuration information of the functions associated with each use case in the current baseline engineering general use case set, adjust the test strategy of the strategy optimization use case set according to the data configuration information, and obtain a test strategy use case set that is coordinated with the data production strategy; Obtain the defect records of each test case in the current baseline engineering general test case set, perform statistical analysis on the defect records, and improve and simplify the test strategy test case set based on the statistical analysis results to obtain the optimized engineering general test case set. The optimized engineering general use case set is used as the engineering general use case set under the new baseline to complete the maintenance of the engineering general use case set.

[0011] Furthermore, the engineering-standard general test case set includes test case ID, test case title, test case content, test case function points, and current test strategy.

[0012] Furthermore, the specific steps for covering the newly added requirement description based on the fuzzy matching results include: If no suitable test cases are found, a new test case suggestion will be automatically generated. Based on the new requirement description, test cases that cover the new requirement description will be created and the new test cases will be integrated into the test case set draft. If a suitable test case is found in the existing test cases, test steps are added and verification points are expanded based on the suitable test case to ensure that the requirements are fully covered, and the metadata of the existing test cases is updated.

[0013] Furthermore, the test cases contain complete structured information, including test case ID, title, test case content, associated functional points, and test case testing strategy.

[0014] Furthermore, the implementation attributes of the functions associated with the use cases include whether they are implemented purely in software and whether they involve safety-critical requirements.

[0015] Furthermore, the specific steps for optimizing the product design attribute interaction and strategy of the draft use case set based on the implementation attributes of the functions associated with each use case include: If the implementation attribute of the function associated with a use case is pure software implementation and is not related to safety-critical requirements, then the use case shall be removed from the use case set draft. If the implementation attribute of the function associated with the test case is pure software implementation but is related to safety-critical requirements, then the test case test strategy for that test case should be changed to functional testing. If the implementation attribute of the function associated with the test case is not a pure software implementation, then the original test case testing strategy for that test case shall be maintained.

[0016] Furthermore, the test case strategy includes functional testing, traversal testing, and sampling testing.

[0017] Furthermore, the data configuration information includes whether it is a global variable and whether it depends on data configuration.

[0018] Furthermore, the specific steps for adjusting the test strategy of the strategy optimization test case set based on the data configuration information include: If the function associated with the test case depends on data configuration and is a global variable, and the test strategy for internal data verification is traversal testing, then the test strategy for this function in the optimized test case set will be adjusted to functional testing. If the function associated with the test case depends on data configuration but is not a global variable, then the test strategy for that function in the strategy optimization test case set will be adjusted to functional testing. If the function associated with the test case depends on data configuration and is a global variable, and the test case strategy for internal data verification is sampling testing, then the test strategy for this function in the optimized test case set will be adjusted to traversal testing.

[0019] Furthermore, the defect record includes basic defect information, defect association information, and defect attribute information.

[0020] Furthermore, the basic defect information includes defect ID, title, description, and status; the defect association information includes the use case ID that triggered the defect and the trigger time; and the defect attribute information includes defect cause, security level, and severity.

[0021] Furthermore, the specific steps for statistical analysis of the defect records include: By statistically analyzing the number of times each use case has encountered a defect in history, high-frequency use cases with defects can be identified. By statistically analyzing the time distribution of defects based on the most recent occurrence of a defect for each use case, long-term defect-free use cases can be identified.

[0022] Furthermore, the specific steps for improving and simplifying the test strategy test case set based on the statistical analysis results include: Improve the test cases with high incidence of defects, and add more stringent verification points, boundary value tests or abnormal scenario tests to the corresponding test cases based on the causes of defects, and change their test case testing strategy to traversal testing. The long-term defect-free test cases are streamlined. For test cases that are long-term defect-free and unrelated to safety-critical requirements, their test case strategies are changed to sampling or functional testing. Long-term defect-free test cases that have been evaluated and confirmed to have failed or have been completely covered by other test cases are archived or directly deleted from the test strategy test case set.

[0023] According to another aspect of the present invention, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, enables the maintenance method for the engineering general use case set of rail transit integrated projects as described above.

[0024] According to another aspect of the present invention, a general use case set maintenance device for integrated rail transit projects is provided, comprising: The initial data acquisition module is used to acquire the engineering common use case set under the current baseline and the version of the current baseline; The requirement and use case adaptation module is used to inject a new requirement description through the new requirement interface and perform fuzzy matching between the new requirement description and the engineering general use case set under the current baseline. The defect data statistics module is used to obtain defect records of each use case in the engineering general use case set under the current baseline from the project defect library through the project defect library interface, and to perform statistical analysis on the defect records; The test strategy logic relationship module determines the implementation attributes of the functions associated with the test cases through the product design interface, determines the data configuration information through the project data creation interface, and determines the test case test strategy through the project test data verification interface. It is used to perform automated logical judgment based on the implementation attributes, data configuration information, and test case test strategy, and output strategy optimization suggestions. The general engineering use case information module receives the statistical analysis results output by the defect data statistics module and the strategy optimization suggestions output by the test strategy logic relationship module. It is used to update the stored general engineering use case set based on the statistical analysis results and strategy optimization suggestions, and after the maintenance process is completed, it exports and stores the optimized general engineering use case set under the new baseline.

[0025] Compared with the prior art, the present invention has the following beneficial effects: 1. This invention obtains the implementation attributes of the functions associated with the test cases, makes strategy optimization decisions based on the implementation attributes, and outputs a strategy optimization test case set based on product design attributes, achieving initial simplification. By extracting the data configuration information of the functions associated with the test cases, making strategy adjustment decisions based on the data configuration information, and outputting a test strategy test case set that coordinates with the data production strategy, it achieves adaptive test intensity. This invention solves the limitations of existing technologies, such as redundant test case sets, high testing costs, and insufficient risk coverage caused by maintenance lag, rigid strategies, and front-end / back-end disconnect. It significantly improves the maintenance efficiency of the engineering general test case set for rail transit integrated projects.

[0026] 2. This invention, by employing a multi-layered collaborative maintenance method consisting of attribute awareness, strategy arbitration, and feedback verification, achieves real-time linkage and adaptive fine-tuning of use case sets, product design changes, and data creation verification strategies. It solves the shortcomings of existing technologies, such as slow response, repetitive testing, and weak risk management due to lack of dynamic correlation and reliance on human experience. This significantly enhances the efficiency of testing activities and the reliability of overall quality assurance during the evolution of complex projects. Attached Figure Description

[0027] Figure 1 This is a flowchart illustrating a general use case set maintenance method for integrated rail transit projects proposed in this invention. Figure 2 This is a schematic diagram of the structure of a general-purpose use case set maintenance device for integrated rail transit projects proposed in this invention; Figure 3 A flowchart illustrating the process of maintaining engineering general use case sets using the maintenance device for integrated rail transit projects. Detailed Implementation

[0028] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments. These embodiments are based on the technical solution of the present invention and provide detailed implementation methods and specific operating procedures. However, the scope of protection of the present invention is not limited to the following embodiments.

[0029] Example 1 This embodiment provides a method for maintaining a general use case set in an integrated rail transit project, such as... Figure 1 As shown, it includes the following steps: S1. Obtain the set of general engineering use cases under the current baseline and inject the new requirement description.

[0030] Based on the current baseline of the product or project, obtain a complete set of general engineering test cases bound to that baseline version. This set of test cases serves as the input and foundation for all subsequent optimization operations. The general engineering test case set includes a test case ID (unique identifier), a test case title (summary description), a test case content (detailed test steps, expected results, etc.), test case functionalities (the functional modules being verified), and the current test case testing strategy. Test case testing strategies include functional testing, traversal testing, and sampling testing.

[0031] S2. Perform fuzzy matching between the new requirement description and the current baseline engineering general use case set to obtain the fuzzy matching result. Then, cover the new requirement description according to the fuzzy matching result to obtain a draft use case set that fully covers the new requirement description.

[0032] The injected new requirement description is compared with the structured fields such as title, content, and function points of all existing use cases in the current baseline engineering general use case set. The correlation between the requirement and the use case is evaluated by a preset algorithm model, and a reasonable similarity threshold is set to make a judgment. Finally, a fuzzy matching result is generated, which indicates whether a suitable use case is found or no suitable use case is found.

[0033] The specific steps for covering the new requirement description based on the fuzzy matching results include: If no suitable test cases are found, a new test case suggestion will be automatically generated. Based on the new requirement description, test cases that cover the new requirement description will be created and integrated into the test case set draft. The test cases contain complete structured information, including test case ID, title, test case content, associated functional points, and test case strategy.

[0034] If a matching test case is found in the existing test cases, it indicates that the existing test cases partially cover the requirement. In this case, instead of creating entirely new test cases, supplementary and extended operations are performed based on the existing framework and test steps of the matching test case. Specifically, this includes adding new verification points, supplementing test steps for boundary conditions or abnormal scenarios, and expanding test data combinations to ensure that the new requirement is fully and rigorously covered, while simultaneously updating the metadata of the existing test cases.

[0035] The final result is an updated draft of a general-purpose engineering use case set that fully covers all the new requirements.

[0036] S3. Obtain the implementation attributes of the functions associated with each use case in the current baseline engineering general use case set, and perform product design attribute interaction and strategy optimization on the use case set draft based on the implementation attributes of the functions associated with each use case to obtain a strategy-optimized use case set based on product design attributes.

[0037] Obtain the implementation attributes of the functions associated with each use case in the current baseline's engineering general use case set. The implementation attributes of the functions associated with the use cases include whether they are implemented by pure software and whether they involve safety-critical requirements.

[0038] The specific steps for optimizing the product design attributes, interaction, and strategies of the draft use case set based on the implementation attributes of the functions associated with each use case include: If the implementation attribute of the function associated with the use case is a pure software implementation and is not related to safety-critical requirements, then the use case will be removed from the use case set draft. In this scenario, the function has been fully guaranteed by product testing during the development phase. Therefore, the use case will be removed from the use case set draft, and its quality assurance responsibility will return to the product development and testing process to avoid repeated verification at the engineering system testing level.

[0039] If the implementation attribute of the function associated with the test case is a pure software implementation but is related to safety-critical requirements, then the test case testing strategy for that test case will be changed to functional testing, that is, focusing on verifying the correctness of its core logic, while canceling any possible data-oriented or configuration-oriented traversal tests, thereby improving testing efficiency while ensuring security verification.

[0040] If the functionality associated with a test case is not a pure software implementation, then the original test case strategy for that test case should be maintained. Such functionality typically relies on hardware or engineering data configuration and is a key focus of engineering testing. Therefore, the original test case strategy should remain unchanged, and further optimization of the strategy will be handled in subsequent steps involving the association with data configuration information.

[0041] After this round of interaction and strategy optimization based on product design attributes, a set of strategy optimization use cases based on product design attributes, which has undergone the first round of simplification and strategy calibration, has been obtained.

[0042] S4. Extract the data configuration information of the functions associated with each test case in the current baseline engineering general test case set, adjust the strategy to optimize the test strategy of the test case set according to the data configuration information, and obtain a test strategy test case set that is coordinated with the data production strategy.

[0043] Extract the data configuration information of the functions associated with each use case in the current baseline's engineering general use case set. The data configuration information includes whether it is a global variable and whether it depends on the data configuration.

[0044] The specific steps for adjusting and optimizing the test strategy for the test case set based on the data configuration information include: If the functionality associated with a test case depends on data configuration and is a global variable, and the test strategy for internal data verification is traversal testing, then the test strategy for that functionality in the strategy optimization test case set should be adjusted to functional testing. Since the critical global data has already undergone comprehensive traversal verification in the early stages, its basic correctness is highly guaranteed. At the engineering system testing level, there is no need for repeated high-intensity traversal; it is only necessary to verify the normal performance of the function under this data configuration. This directly solves the resource waste caused by repeated verification upstream and downstream, significantly improving testing efficiency.

[0045] If the functionality associated with a test case depends on data configuration but is not a global variable, then the test strategy for that functionality in the strategy optimization test case set will be adjusted to functional testing. Non-global variables have a limited scope of impact; the testing focus is on confirming that the configuration function is working correctly, rather than conducting extensive impact testing. Functional testing is sufficient to meet the verification requirements, thus simplifying the test content and focusing the testing focus.

[0046] If the function associated with a test case depends on data configuration and is a global variable, and the test strategy for internal data verification is sampling, then the test strategy for that function in the strategy optimization test case set should be adjusted to traversal testing. Global data has a significant impact; if initial internal verification is insufficient (only sampling), there is a high risk. Traversal testing is required at the engineering testing level to compensate for insufficient verification strength, ensure overall system reliability, and achieve risk management.

[0047] After this round of refined strategy adjustments based on data configuration information, a test case set with a deep synergy with the data production strategy and reasonable test intensity settings was obtained.

[0048] This step is crucial for simplifying and improving the efficiency of testing. It dynamically adjusts the testing strategy through rule-based judgments, ultimately achieving precise allocation of testing resources. The beneficial effects include: Avoid redundant testing: When the data level has been sufficiently validated, engineering testing can be simplified, improving efficiency.

[0049] Strengthen risk management: When data verification is insufficient, engineering testing should be strengthened to ensure quality.

[0050] Achieve adaptive optimization: Establish a linkage mechanism with the front-end data production process, so that the testing strategy can be automatically adjusted as the data production method changes.

[0051] S5. Obtain the defect records of each test case in the current baseline engineering general test case set, perform statistical analysis on the defect records, and improve and simplify the test strategy test case set based on the statistical analysis results to obtain the optimized engineering general test case set.

[0052] Defect records include basic defect information, defect association information, and defect attribute information. Basic defect information includes defect ID, title, description, and status; defect association information includes the use case ID that triggered the defect and the trigger time; and defect attribute information includes the defect cause, security level, and severity.

[0053] The specific steps for statistical analysis of defect records include: Based on the number of times each use case has a defect in history, the frequency of use case defects is statistically analyzed, and high-frequency use cases with defects are identified based on a preset threshold. Based on the time point of the most recent defect occurrence for each use case, defect time distribution statistics are performed, and use cases that have not been found to have any defects for more than a preset period of time are identified as long-term defect-free use cases.

[0054] The specific steps for improving and streamlining the test strategy test case set based on statistical analysis results include: Improve test cases with high defect rates. Based on the cause of the defect, add more stringent verification points, boundary value tests or abnormal scenario tests to the corresponding test cases, and change the test case testing strategy to traversal testing to strengthen the verification intensity and control quality risks.

[0055] Simplify long-term defect-free test cases. For test cases that have been defect-free for a long time and are not related to safety-critical requirements, change their test case strategy to sampling or functional testing. For long-term defect-free test cases that have been evaluated and confirmed to have no function or have been completely covered by other test cases, archive them or delete them directly from the test strategy test case set to maintain the simplicity and efficiency of the test case set.

[0056] After this round of refinement and simplification based on objective defect data, the optimized engineering-grade general test case set was finally obtained. This optimization enables the intelligent reallocation of test resources, focusing more effort on areas where problems have been proven to occur frequently, while reducing inefficient investment in stable areas, ensuring that the test case set can continuously adapt to changes in the project's quality status.

[0057] S6. Use the optimized engineering general use case set as the engineering general use case set under the new baseline, and complete the maintenance of the engineering general use case set.

[0058] The final output of this step is a set of general engineering use cases under the new baseline. This output not only directly guides the engineering testing activities of the new baseline version, ensuring the accuracy and efficiency of the tests; more importantly, it serves as a set of general engineering use cases under the current baseline for the next maintenance process (i.e., the input of step S1), providing a new starting point for subsequent continuous optimization cycles, thus forming a self-evolving and continuously improving closed loop.

[0059] Example 2 This embodiment provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, it can implement the general use case set maintenance method for integrated rail transit projects as proposed in Embodiment 1.

[0060] The rest is the same as in Example 1.

[0061] Example 3 This embodiment proposes a general-purpose use case set maintenance device for integrated rail transit projects, such as... Figure 2 As shown, it includes: The initial data acquisition module is used to acquire the engineering common use case set under the current baseline and the version of the current baseline; The requirement and use case adaptation module is used to inject new requirement descriptions through the new requirement interface and perform fuzzy matching between the new requirement descriptions and the engineering general use case set under the current baseline. The defect data statistics module is used to obtain defect records of each use case in the current baseline engineering general use case set from the project defect library through the project defect library interface, and to perform statistical analysis on the defect records; The test strategy logic relationship module determines the implementation attributes of the functions associated with the test cases through the product design interface, determines the data configuration information through the project data creation interface, and determines the test case test strategy through the project test data verification interface. It is used to perform automated logical judgment based on the implementation attributes, data configuration information, and test case test strategy, and output strategy optimization suggestions. The general engineering use case information module receives statistical analysis results from the defect data statistics module and strategy optimization suggestions from the test strategy logic relationship module. Based on the statistical analysis results and strategy optimization suggestions, it updates the stored general engineering use case set and exports and stores the optimized general engineering use case set under the new baseline after the maintenance process is completed.

[0062] A flowchart illustrating the process of maintaining engineering general use case sets using the rail transit integrated project engineering general use case set maintenance device is shown below. Figure 3As shown. The process begins with a new baseline trigger, importing the existing standardized engineering test case set under the current baseline into the device processing environment as the baseline version and optimization basis for this maintenance. After injecting new requirements through the new requirement interface, the process determines whether there are compatible test cases. No compatible test cases: If the determination is no, the process executes the add test case operation, creating a complete test case based on the new requirement and integrating it into the test case set. Compatible test cases exist: If the determination is yes, the process executes the add step operation on the corresponding test case, supplementing or expanding the test content based on the identified compatible test cases to ensure that the requirement is fully covered. The process obtains the functional implementation attributes through the product design interface and enters the pure software determination node. Pure software function processing: If it is a pure software implementation, it further enters the determination of whether it is related to security. If it is not related to security, the test case is removed from the engineering general test case set. If it is related to security, the test strategy of the test case is uniformly changed to functional testing. Non-pure software function processing: If the function is not a pure software implementation, the process directly enters the next stage, and the optimization of its test strategy will be associated with the data configuration attributes. For non-pure software functions, the process sequentially performs three key checks: determining if the data is a global variable, determining if it depends on data, confirming the function's dependency on data configuration, and determining if the data has been internally verified, confirming the strength of verification implemented during the data creation phase. If the data is a global variable and has already been internally verified, the testing strategy for this function in the engineering general test case set is adjusted to functional testing to avoid redundant verification. If the data is a global variable but only sampled internally, the engineering testing strategy is strengthened to traversal testing to compensate for insufficient verification in the early stages and manage risks. After the above complete check and optimization path, the process executes the export of standardized test cases under the new baseline, binds the final optimized engineering general test case set with the new product baseline version, and releases it, after which the process ends.

[0063] The rest is the same as in Example 1.

[0064] The preferred embodiments of the present invention have been described in detail above. It should be understood that those skilled in the art can make numerous modifications and variations based on the concept of the present invention without creative effort. Therefore, all technical solutions that can be obtained by those skilled in the art based on the concept of the present invention through logical analysis, reasoning, or limited experimentation on the basis of existing technology should be within the scope of protection defined by the claims.

Claims

1. A method for maintaining a general use case set in an integrated rail transit project, characterized in that, Includes the following steps: Obtain the set of common engineering use cases under the current baseline and inject the new requirement description; The new requirement description is fuzzy matched with the engineering general use case set under the current baseline to obtain the fuzzy matching result. The new requirement description is then covered according to the fuzzy matching result to obtain a draft use case set that fully covers the new requirement description. Obtain the implementation attributes of the functions associated with each use case in the current baseline engineering general use case set, and perform product design attribute interaction and strategy optimization on the use case set draft based on the implementation attributes of the functions associated with each use case to obtain a strategy-optimized use case set based on product design attributes; Extract the data configuration information of the functions associated with each use case in the current baseline engineering general use case set, adjust the test strategy of the strategy optimization use case set according to the data configuration information, and obtain a test strategy use case set that is coordinated with the data production strategy; Obtain the defect records of each test case in the current baseline engineering general test case set, perform statistical analysis on the defect records, and improve and simplify the test strategy test case set based on the statistical analysis results to obtain the optimized engineering general test case set. The optimized engineering general use case set is used as the engineering general use case set under the new baseline to complete the maintenance of the engineering general use case set.

2. The method for maintaining a general use case set for integrated rail transit projects according to claim 1, characterized in that, The engineering-standard general test case set includes test case ID, test case title, test case content, test case function points, and current test strategy.

3. The method for maintaining a general use case set for integrated rail transit projects according to claim 1, characterized in that, The specific steps for covering the new requirement description based on the fuzzy matching results include: If no suitable test cases are found, a new test case suggestion will be automatically generated. Based on the new requirement description, test cases that cover the new requirement description will be created and the new test cases will be integrated into the test case set draft. If a suitable test case is found in the existing test cases, test steps are added and verification points are expanded based on the suitable test case to ensure that the requirements are fully covered, and the metadata of the existing test cases is updated.

4. The method for maintaining a general use case set for integrated rail transit projects according to claim 3, characterized in that, The test cases contain complete structured information, including test case ID, title, test case content, associated functional points, and test case strategy.

5. The method for maintaining a general use case set for integrated rail transit projects according to claim 1, characterized in that, The implementation attributes of the functions associated with the use cases include whether they are implemented purely in software and whether they involve security-critical requirements.

6. The method for maintaining a general use case set for integrated rail transit projects according to claim 5, characterized in that, The specific steps for optimizing the product design attribute interaction and strategy of the draft use case set based on the implementation attributes of the functions associated with each use case include: If the implementation attribute of the function associated with a use case is pure software implementation and is not related to safety-critical requirements, then the use case shall be removed from the use case set draft. If the implementation attribute of the function associated with the test case is pure software implementation but is related to safety-critical requirements, then the test case test strategy for that test case should be changed to functional testing. If the implementation attribute of the function associated with the test case is not a pure software implementation, then the original test case testing strategy for that test case shall be maintained.

7. The method for maintaining a general use case set for integrated rail transit projects according to claim 6, characterized in that, The test case strategy includes functional testing, traversal testing, and sampling testing.

8. The method for maintaining a general use case set for integrated rail transit projects according to claim 1, characterized in that, The data configuration information includes whether it is a global variable and whether it depends on data configuration.

9. The method for maintaining a general use case set for integrated rail transit projects according to claim 8, characterized in that, The specific steps for adjusting the test strategy of the strategy optimization test case set based on the data configuration information include: If the function associated with the test case depends on data configuration and is a global variable, and the test strategy for internal data verification is traversal testing, then the test strategy for this function in the optimized test case set will be adjusted to functional testing. If the function associated with the test case depends on data configuration but is not a global variable, then the test strategy for that function in the strategy optimization test case set will be adjusted to functional testing. If the function associated with the test case depends on data configuration and is a global variable, and the test case strategy for internal data verification is sampling testing, then the test strategy for this function in the optimized test case set will be adjusted to traversal testing.

10. The method for maintaining a general use case set for integrated rail transit projects according to claim 1, characterized in that, The defect record includes basic defect information, defect association information, and defect attribute information.

11. The method for maintaining a general use case set for integrated rail transit projects according to claim 10, characterized in that, The basic information of the defect includes defect ID, title, description and status; the defect association information includes the use case ID that triggered the defect and the trigger time; and the defect attribute information includes defect cause, security level and severity.

12. The method for maintaining a general use case set for integrated rail transit projects according to claim 1, characterized in that, The specific steps for statistical analysis of the defect records include: By statistically analyzing the number of times each use case has encountered a defect in history, high-frequency use cases with defects can be identified. By statistically analyzing the time distribution of defects based on the most recent occurrence of a defect for each use case, long-term defect-free use cases can be identified.

13. The method for maintaining a general use case set for integrated rail transit projects according to claim 12, characterized in that, The specific steps for improving and simplifying the test strategy test case set based on the statistical analysis results include: Improve the test cases with high incidence of defects, and add more stringent verification points, boundary value tests or abnormal scenario tests to the corresponding test cases based on the causes of defects, and change their test case testing strategy to traversal testing. The long-term defect-free test cases are streamlined. For test cases that are long-term defect-free and unrelated to safety-critical requirements, their test case strategies are changed to sampling or functional testing. Long-term defect-free test cases that have been evaluated and confirmed to have failed or have been completely covered by other test cases are archived or directly deleted from the test strategy test case set.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, enables the maintenance method for the engineering general use case set of rail transit integrated projects as described in any one of claims 1 to 12.

15. A maintenance device for a general-purpose use case set for integrated rail transit projects, characterized in that, include: The initial data acquisition module is used to acquire the engineering common use case set under the current baseline and the version of the current baseline; The requirement and use case adaptation module is used to inject a new requirement description through the new requirement interface and perform fuzzy matching between the new requirement description and the engineering general use case set under the current baseline. The defect data statistics module is used to obtain defect records of each use case in the engineering general use case set under the current baseline from the project defect library through the project defect library interface, and to perform statistical analysis on the defect records; The test strategy logic relationship module determines the implementation attributes of the functions associated with the test cases through the product design interface, determines the data configuration information through the project data creation interface, and determines the test case test strategy through the project test data verification interface. It is used to perform automated logical judgment based on the implementation attributes, data configuration information, and test case test strategy, and output strategy optimization suggestions. The general engineering use case information module receives the statistical analysis results output by the defect data statistics module and the strategy optimization suggestions output by the test strategy logic relationship module. It is used to update the stored general engineering use case set based on the statistical analysis results and strategy optimization suggestions, and after the maintenance process is completed, it exports and stores the optimized general engineering use case set under the new baseline.

Images