Use case recommendation method, apparatus, storage medium, and device

Abstract

The application discloses a use case recommendation method and device, a storage medium and equipment, and the method is: generating a test plan of a to-be-tested function; through a preset use case selection interface, parameter information of all use cases is displayed; based on a triggering operation of a user and a project name and a module name of each use case, a plurality of candidate use cases are determined; a use case recommendation value formula is used to calculate the recommendation values of the candidate use cases, and the recommendation values of the candidate use cases are obtained; the candidate use cases are sorted in descending order of the recommendation values, and a use case sequence is obtained; based on parameter information of the first m use cases in the use case sequence, a use case recommendation list is constructed; and through a preset use case recommendation interface, the use case recommendation list is displayed. The method calculates the recommendation values of the use cases through the use case recommendation value formula, and recommends the use cases to the user according to the recommendation values, so that the time spent by a person in screening the use cases is saved, and the selection efficiency and accuracy of the use cases required by the test plan can be improved.

Description

Technical Field

[0001] This application relates to the field of functional testing, and more particularly to a method, apparatus, storage medium, and device for recommending test cases. Background Technology

[0002] Currently, when performing multi-functional testing, in addition to testing the newly added or modified functions, it is also necessary to cover the surrounding related functions to prevent the changes from affecting other normal functions. When selecting test cases to cover the surrounding functions, it is generally necessary to manually select them one by one from the entire test case library based on one's own experience and understanding of the project functions. Moreover, if the relevant personnel are not experienced or familiar with the project functions, incomplete coverage may occur, resulting in low efficiency and accuracy in test case selection.

[0003] Therefore, improving the efficiency and accuracy of test case selection for test plans has become an urgent problem to be solved in this field. Summary of the Invention

[0004] This application provides a test case recommendation method, apparatus, storage medium, and device, with the aim of improving the efficiency and accuracy of test case selection for test plans.

[0005] To achieve the above objectives, this application provides the following technical solution:

[0006] A use case recommendation method, comprising:

[0007] Generate a test plan for the function to be tested as shown in the functional test requirements for user input; the test plan includes the project name of the project to which the function to be tested belongs and the module name of the module to which it belongs;

[0008] The user is shown parameter information of all pre-configured use cases through a preset use case selection interface; the parameter information includes at least the project name of the project to which the use case belongs.

[0009] Based on the user's triggering action, and the project name and module name of each test case, multiple candidate test cases are determined; the candidate test cases include test cases related to the test plan;

[0010] Using a preset use case recommendation value formula, a recommendation value is calculated for each of the candidate use cases to obtain a recommendation value for each candidate use case;

[0011] The candidate use cases are sorted in descending order of recommendation value to obtain a use case sequence;

[0012] Based on the parameter information of the first m test cases in the test case sequence, a test case recommendation list is constructed; m is a positive integer.

[0013] The user is presented with a list of recommended use cases through a pre-defined use case recommendation interface.

[0014] Optionally, based on the user's triggered action and the project name and module name of each use case, multiple candidate use cases are determined, including:

[0015] If the user does not trigger the selection of any of the test cases as test cases, the project belonging to the function under test will be marked as the target project;

[0016] All use cases belonging to the target project are identified as candidate use cases.

[0017] Optionally, based on the user's triggered action and the project name and module name of each use case, multiple candidate use cases are determined, including:

[0018] When the user triggers the selection of at least one of the test cases as test cases, the module to which the test case belongs is identified as the target module;

[0019] All use cases belonging to the target module are identified as candidate use cases.

[0020] Optionally, the step of using a preset use case recommendation value formula to calculate the recommendation value for each candidate use case, and obtaining the recommendation value for each candidate use case, includes:

[0021] The values ​​and weights of the recommendation factors for each test case are pre-configured to generate a test case information table; the recommendation factors include test case priority, the number of historical execution failures of the test case, and whether the test case is allowed to be admitted.

[0022] The recommendation value of each candidate use case is calculated by substituting the values ​​of the recommendation factors and their weight percentages into the preset use case recommendation value formula.

[0023] A use case recommendation device, comprising:

[0024] The test planning unit is used to generate a test plan for the function to be tested as indicated by the functional test requirements input by the user; the test plan includes the project name of the project to which the function to be tested belongs and the module name of the module to which it belongs;

[0025] The test case selection unit is used to display parameter information of all pre-configured test cases to the user through a preset test case selection interface; the parameter information includes at least the project name of the project to which the test case belongs;

[0026] The use case determination unit is used to determine multiple candidate use cases based on the user's triggered operation and the project name and module name of each use case; the candidate use cases include use cases related to the test plan;

[0027] The recommendation value calculation unit is used to calculate the recommendation value of each candidate use case using a preset use case recommendation value formula, so as to obtain the recommendation value of each candidate use case.

[0028] The use case sorting unit is used to sort the candidate use cases in descending order of recommendation value to obtain a use case sequence;

[0029] The list construction unit is used to construct a recommended list of test cases based on the parameter information of the first m test cases in the test case sequence; m is a positive integer.

[0030] The list display unit is used to display the list of recommended use cases to the user through a preset use case recommendation interface.

[0031] Optionally, the use case determination unit is specifically used for:

[0032] If the user does not trigger the selection of any of the test cases as test cases, the project belonging to the function under test will be identified as the target project.

[0033] All use cases belonging to the target project are identified as candidate use cases.

[0034] Optionally, the use case determination unit is specifically used for:

[0035] When the user triggers the selection of at least one of the test cases as test cases, the module to which the test case belongs is identified as the target module;

[0036] All use cases belonging to the target module are identified as candidate use cases.

[0037] Optionally, the recommendation value calculation unit is specifically used for:

[0038] The values ​​and weights of the recommendation factors for each of the test cases are pre-configured to generate a test case information table; the recommendation factors include test case priority, the number of historical execution failures of the test case, and whether the test case is allowed to be admitted.

[0039] The recommendation value of each candidate use case is calculated by substituting the values ​​of the recommendation factors and their weight percentages into the preset use case recommendation value formula.

[0040] A computer-readable storage medium includes a stored program, wherein the program is executed by a processor to perform the use case recommendation method.

[0041] A use case recommendation device includes: a processor, a memory, and a bus; the processor and the memory are connected via the bus;

[0042] The memory is used to store the program, and the processor is used to run the program, wherein the program is executed by the processor to perform the use case recommendation method.

[0043] The technical solution provided in this application generates a test plan for the function to be tested, as indicated by the user-input functional test requirements. A preset test case selection interface displays the parameter information of all pre-configured test cases to the user. Based on the user's triggering operation and the project name and module name of each test case, multiple candidate test cases are identified. A preset test case recommendation value formula is used to calculate the recommendation value for each candidate test case. The candidate test cases are then sorted in descending order of recommendation value to obtain a test case sequence. Based on the parameter information of the first m test cases in the sequence, a test case recommendation list is constructed. This list is then displayed to the user through a preset test case recommendation interface. This application calculates the recommendation value of each test case related to the test plan using the test case recommendation value formula and recommends suitable test cases to the user based on these values. This eliminates the need for manual time-consuming test case selection, thereby improving the efficiency and accuracy of test case selection for the test plan and significantly saving testing time. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0045] Figure 1a A flowchart illustrating a use case recommendation method provided in an embodiment of this application;

[0046] Figure 1b A flowchart illustrating a use case recommendation method provided in an embodiment of this application;

[0047] Figure 2 A flowchart illustrating another use case recommendation method provided in an embodiment of this application;

[0048] Figure 3 This is a schematic diagram of the architecture of a use case recommendation device provided in an embodiment of this application. Detailed Implementation

[0049] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0050] like Figure 1a and Figure 1b The diagram shown is a flowchart illustrating a use case recommendation method provided in an embodiment of this application, including the following steps.

[0051] S101: Pre-configure each use case, as well as the parameter information, recommendation factor values, and weight percentages for each use case.

[0052] Each test case includes those required in previous testing processes. Parameter information includes the project name (referred to as a feature point) of the project to which the test case belongs, priority, whether the test case is admitted, creator, version tag, test case title, and whether it is automated. Recommendation factors include test case priority, the number of historical execution failures of the test case, and whether the test case is admitted.

[0053] Use case priorities include first priority P0, second priority P1, third priority P2, fourth priority P3, and fifth priority P4. P0 has a higher priority than P1, P1 has a higher priority than P2, P2 has a higher priority than P3, and P3 has a higher priority than P4.

[0054] The number of times a test case has failed to execute in the past can be obtained by counting the number of times the test case failed to execute in previous testing processes.

[0055] A value of 2 for the "Whether to Allow" test case indicates that the test case involves functions related to the main business process (the entire main operational flow of the business). A value of 1 for the "Whether to Allow" test case indicates that the test case does not involve functions related to the main business process. In this embodiment, the "Whether to Allow" test case is used to: indicate whether the test case can be used for self-testing by R&D, to ensure the completeness of the delivered main functional flow, and is a test case that needs to be executed when R&D delivers the test version.

[0056] It should be noted that, for the same use case, the sum of the weight percentages of the use case priority, the weight percentage of whether the use case is admitted, and the weight percentage of the number of times the use case has failed in the past is 1.

[0057] S102: Analyze the functional test requirements input by the user to obtain the functions to be tested.

[0058] The types of functions to be tested include, but are not limited to, new functions and correction functions.

[0059] S103: Generate a test plan for the function to be tested.

[0060] The test plan includes the project name, plan name, requirement address (i.e., the link address of the requirement function being tested), and plan schedule (i.e., the execution time period of the test plan).

[0061] S104: Through the preset test case selection interface, the parameter information of all pre-configured test cases is displayed to the user.

[0062] S105: If the user does not trigger the selection of any test case as a test case, the project belonging to the function under test will be marked as the target project.

[0063] S106: Mark all use cases belonging to the target project as candidate use cases.

[0064] After executing S106, continue executing S109.

[0065] S107: When a user triggers the selection of at least one test case as a test case, the module to which the test case belongs is identified as the target module.

[0066] S108: Mark all use cases belonging to the target module as candidate use cases.

[0067] After executing S108, continue executing S109.

[0068] S109: Substitute the values ​​of the recommendation factors and weight percentages of each candidate use case into the preset use case recommendation value formula to calculate the recommendation value of each candidate use case.

[0069] The specific expression of the use case recommendation value formula is shown in formula (1).

[0070]

[0071] In formula (1), n ​​represents the total number of recommendation factors (n = 3 in this embodiment), i represents the index of the recommendation factor, and Y k The recommendation factors are represented by Y1 (test case priority, Y2 (test case admission), and Y3 (test case historical failure count). k This represents the weight percentage of the recommendation factor.

[0072] It should be noted that in this embodiment, when making user recommendations, the scope of recommended use cases is first determined based on whether the user has selected the target use case (i.e., candidate use cases are determined), and then the recommendation value of each candidate use case is calculated according to the use case recommendation value formula.

[0073] Specifically, assuming the priority weight is set to 0.2, the weight of whether a test case is admitted is 0.3, and the weight of the number of historical execution failures of a test case is 0.5, if a certain priority is P1, the admission of a test case is not allowed, and the historical execution failure count of this candidate test case is 6, then the recommended value of this candidate test case is: 4*0.2+1*0.3+6*0.5=4.1. The recommended values ​​of all candidate test cases are calculated in turn, and then the candidate test cases are sorted according to the order of the recommended values ​​from high to low to obtain the test case sequence. The top 100 test cases in the test case sequence are selected as the test cases recommended to the user.

[0074] S110: Sort the candidate use cases in descending order of recommendation value to obtain a use case sequence.

[0075] S111: Construct a recommended list of test cases based on the parameter information of the first m test cases in the test case sequence.

[0076] Where m is a positive integer.

[0077] S112: Display a list of recommended use cases to the user through a preset use case recommendation interface.

[0078] Based on the processes shown in S101-S112 above, this embodiment can achieve the following beneficial effects.

[0079] 1. Add a test case recommendation function to the test plan test case maintenance to improve the efficiency of test case selection and the accuracy of test case coverage.

[0080] 2. By using the historical execution failure count of test cases, test case priority, and whether a test case is an admission test case as calculation parameters in the test case recommendation value formula, the recommendation value of each candidate test case is calculated. Based on the recommendation value, reasonable candidate test cases are selected and recommended to the user. The recommendation results are highly reliable and can ensure that the test cases recommended to the user meet the requirements of the test plan.

[0081] In summary, this embodiment calculates the recommended value of each test case related to the test plan using the test case recommendation value formula, and recommends suitable test cases to the user based on the recommended value. This eliminates the need for manual time to filter test cases, thereby improving the efficiency and accuracy of test case selection for the test plan and greatly saving testing time.

[0082] It should be noted that S101 mentioned in the above embodiments is an optional specific implementation of the use case recommendation method shown in the embodiments of this application. Furthermore, S108 mentioned in the above embodiments is also an optional specific implementation of the use case recommendation method shown in the embodiments of this application. Therefore, the process mentioned in the above embodiments can be summarized as follows: Figure 2 The method shown.

[0083] like Figure 2The diagram shown is a flowchart illustrating another use case recommendation method provided in this application embodiment, which includes the following steps.

[0084] S201: Test plan for the function to be tested as shown in the functional test requirements for generating user input.

[0085] The test plan includes the project name of the project to which the function to be tested belongs.

[0086] S202: Through the preset test case selection interface, the parameter information of all pre-configured test cases is displayed to the user.

[0087] The parameter information includes at least the project name of the project to which the test case belongs and the module name of the module to which it belongs.

[0088] S203: Based on the user's triggering action, and the project name and module name of each use case, identify multiple candidate use cases.

[0089] Candidate test cases include those related to the test plan.

[0090] S204: Using the preset use case recommendation value formula, calculate the recommendation value for each candidate use case to obtain the recommendation value for each candidate use case.

[0091] S205: Sort the candidate use cases in descending order of recommendation value to obtain a use case sequence.

[0092] S206: Construct a recommended list of test cases based on the parameter information of the first m test cases in the test case sequence.

[0093] Where m is a positive integer.

[0094] S207: Display a list of recommended use cases to users through a preset use case recommendation interface.

[0095] In summary, this embodiment calculates the recommended value of each test case related to the test plan using the test case recommendation value formula, and recommends suitable test cases to the user based on the recommended value. This eliminates the need for manual time to filter test cases, thereby improving the efficiency and accuracy of test case selection for the test plan and greatly saving testing time.

[0096] Corresponding to the use case recommendation method provided in the above embodiments of this application, the embodiments of this application also provide a use case recommendation device.

[0097] like Figure 3 The diagram shown is an architectural schematic of a use case recommendation device provided in an embodiment of this application, which includes the following units.

[0098] The test planning unit 100 is used to generate a test plan for the function to be tested as indicated by the user-input functional test requirements. The test plan includes the project name of the project to which the function to be tested belongs and the module name of the module to which it belongs.

[0099] The test case selection unit 200 is used to display the parameter information of all pre-configured test cases to the user through a preset test case selection interface; the parameter information includes at least the project name of the project to which the test case belongs.

[0100] The use case determination unit 300 is used to determine multiple candidate use cases based on the user's triggered operation and the project name and module name of each use case; the candidate use cases include use cases related to the test plan.

[0101] Optionally, the use case determination unit 300 is specifically used to: identify the project belonging to the function under test as the target project when the user does not trigger the selection of any use case as a test case; and identify all use cases belonging to the target project as candidate use cases.

[0102] The use case determination unit 300 is specifically used to: when a user triggers the selection of at least one use case as a test case, identify the module to which the test case belongs as the target module; and identify all use cases belonging to the target module as candidate use cases.

[0103] The recommendation value calculation unit 400 is used to calculate the recommendation value of each candidate use case using a preset use case recommendation value formula, so as to obtain the recommendation value of each candidate use case.

[0104] Optionally, the recommendation value calculation unit 400 is specifically used to: pre-configure the values ​​and weight ratios of the recommendation factors for each use case, and generate a use case information table; the recommendation factors include use case priority, the number of historical execution failures of the use case, and whether the use case is allowed; substitute the values ​​and weight ratios of the recommendation factors for each candidate use case into the preset use case recommendation value formula to calculate the recommendation value of each candidate use case.

[0105] The test case sorting unit 500 is used to sort the candidate test cases in descending order of recommendation value to obtain a test case sequence.

[0106] List building unit 600 is used to build a recommended list of test cases based on the parameter information of the first m test cases in the test case sequence; m is a positive integer.

[0107] The list display unit 700 is used to display a list of recommended use cases to users through a preset use case recommendation interface.

[0108] In summary, this embodiment calculates the recommended value of each test case related to the test plan using the test case recommendation value formula, and recommends suitable test cases to the user based on the recommended value. This eliminates the need for manual time to filter test cases, thereby improving the efficiency and accuracy of test case selection for the test plan and greatly saving testing time.

[0109] This application also provides a computer-readable storage medium including a stored program, wherein the program executes the recommended method for the use cases provided in this application.

[0110] This application also provides a use case recommendation device, including a processor, a memory, and a bus. The processor and the memory are connected via the bus. The memory is used to store programs, and the processor is used to run the programs. When the program runs, it executes the use case recommendation method provided in this application, including the following steps:

[0111] Generate a test plan for the function to be tested as shown in the functional test requirements for user input; the test plan includes the project name of the project to which the function to be tested belongs and the module name of the module to which it belongs;

[0112] The user is shown parameter information of all pre-configured use cases through a preset use case selection interface; the parameter information includes at least the project name of the project to which the use case belongs.

[0113] Based on the user's triggering action, and the project name and module name of each test case, multiple candidate test cases are determined; the candidate test cases include test cases related to the test plan;

[0114] Using a preset use case recommendation value formula, a recommendation value is calculated for each of the candidate use cases to obtain a recommendation value for each candidate use case;

[0115] The candidate use cases are sorted in descending order of recommendation value to obtain a use case sequence;

[0116] Based on the parameter information of the first m test cases in the test case sequence, a test case recommendation list is constructed; m is a positive integer.

[0117] The user is presented with a list of recommended use cases through a pre-defined use case recommendation interface.

[0118] Specifically, based on the above embodiments, the determination of multiple candidate use cases based on the user's triggering operation and the project name and module name of each use case includes:

[0119] If the user does not trigger the selection of any of the test cases as test cases, the project belonging to the function under test will be marked as the target project;

[0120] All use cases belonging to the target project are identified as candidate use cases.

[0121] Specifically, based on the above embodiments, the determination of multiple candidate use cases based on the user's triggering operation and the project name and module name of each use case includes:

[0122] When the user triggers the selection of at least one of the test cases as test cases, the module to which the test case belongs is identified as the target module;

[0123] All use cases belonging to the target module are identified as candidate use cases.

[0124] Specifically, based on the above embodiments, the step of using a preset use case recommendation value formula to calculate the recommendation value for each candidate use case to obtain the recommendation value for each candidate use case includes:

[0125] The values ​​and weights of the recommendation factors for each test case are pre-configured to generate a test case information table; the recommendation factors include test case priority, the number of historical execution failures of the test case, and whether the test case is allowed to be admitted.

[0126] The recommendation value of each candidate use case is calculated by substituting the values ​​of the recommendation factors and their weight percentages into the preset use case recommendation value formula.

[0127] If the functions described in the embodiments of this application are implemented as software functional units and sold or used as independent products, they can be stored in a computing device readable storage medium. Based on this understanding, the parts of the embodiments of this application that contribute to the prior art or the technical solutions can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a computing device (which may be a personal computer, server, mobile computing device, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory, random access memory, magnetic disks, or optical disks.

[0128] The various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0129] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A use case recommendation method, characterized in that, include: The test plan for the function to be tested, as shown in the functional test requirements for generating user input; The test plan includes the project name of the project to which the function to be tested belongs; The user is presented with parameter information for all pre-configured test cases through a preset test case selection interface; the parameter information includes at least the project name of the project to which the test case belongs and the module name of the module to which it belongs. Based on the user's triggering action, and the project name and module name of each test case, multiple candidate test cases are determined; the candidate test cases include test cases related to the test plan; Using a preset use case recommendation value formula, a recommendation value is calculated for each of the candidate use cases to obtain a recommendation value for each candidate use case; The candidate use cases are sorted in descending order of recommendation value to obtain a use case sequence; Based on the parameter information of the first m test cases in the test case sequence, a test case recommendation list is constructed; m is a positive integer; The user is shown a list of recommended use cases through a pre-defined use case recommendation interface. The step of using a preset use case recommendation value formula to calculate the recommendation value for each candidate use case, thereby obtaining the recommendation value for each candidate use case, includes: The values ​​and weighting of recommendation factors for each test case are pre-configured; the recommendation factors include test case priority, the number of historical execution failures of the test case, and whether the test case is allowed to be admitted. The recommendation value of each candidate use case is calculated by substituting the values ​​of the recommendation factors and their weight percentages into the preset use case recommendation value formula.

2. The method according to claim 1, characterized in that, Based on the user's triggered action, and the project name and module name of each use case, multiple candidate use cases are determined, including: If the user does not trigger the selection of any of the test cases as test cases, the project to which the function under test belongs is marked as the target project; All use cases belonging to the target project are identified as candidate use cases.

3. The method according to claim 1, characterized in that, Based on the user's triggered action, and the project name and module name of each use case, multiple candidate use cases are determined, including: When the user triggers the selection of at least one of the test cases as test cases, the module to which the test case belongs is identified as the target module; All use cases belonging to the target module are identified as candidate use cases.

4. A use case recommendation device, characterized in that, include: The test planning unit is used to generate test plans for the functions to be tested as indicated by the functional test requirements input by the user. The test plan includes the project name of the project to which the function to be tested belongs; The test case selection unit is used to display parameter information of all pre-configured test cases to the user through a preset test case selection interface; the parameter information includes at least the project name of the project to which the test case belongs and the module name of the module to which it belongs; The use case determination unit is used to determine multiple candidate use cases based on the user's triggered operation and the project name and module name of each use case; the candidate use cases include use cases related to the test plan; The recommendation value calculation unit is used to calculate the recommendation value of each candidate use case using a preset use case recommendation value formula, so as to obtain the recommendation value of each candidate use case. The use case sorting unit is used to sort the candidate use cases in descending order of recommendation value to obtain a use case sequence; The list construction unit is used to construct a recommended list of test cases based on the parameter information of the first m test cases in the test case sequence; m is a positive integer; The list display unit is used to display the list of recommended use cases to the user through a preset use case recommendation interface; The recommendation value calculation unit is specifically used for: The values ​​and weights of the recommendation factors for each test case are pre-configured to generate a test case information table; the recommendation factors include test case priority, the number of historical execution failures of the test case, and whether the test case is allowed to be admitted. The recommendation value of each candidate use case is calculated by substituting the values ​​of the recommendation factors and their weight percentages into the preset use case recommendation value formula.

5. The apparatus according to claim 4, characterized in that, The use case determination unit is specifically used for: If the user does not trigger the selection of any of the test cases as test cases, the project belonging to the function under test will be marked as the target project; All use cases belonging to the target project are identified as candidate use cases.

6. The apparatus according to claim 4, characterized in that, The use case determination unit is specifically used for: When the user triggers the selection of at least one of the test cases as test cases, the module to which the test case belongs is identified as the target module; All use cases belonging to the target module are identified as candidate use cases.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program is executed by a processor to perform the use case recommendation method according to any one of claims 1-3.

8. A use case recommendation device, characterized in that, include: Processor, memory, and bus; The processor and the memory are connected via the bus; The memory is used to store a program, and the processor is used to run the program, wherein the program is executed by the processor to perform the use case recommendation method according to any one of claims 1-3.

Images