Synchronization method, device, equipment, storage medium and program product of requirement use case

Abstract

The application provides a demand use case synchronization method and device, equipment, computer readable storage medium and computer program product; the method comprises the following steps: in the first area of the demand comparison view, displaying at least one first demand use case corresponding to the first demand service, displaying at least one second demand use case corresponding to the second demand service in the second area, and a synchronization control; wherein the first demand service and the second demand service are used to realize the target function; the synchronization control is used for synchronizing the different demand use cases in the first demand service and the second demand service; in response to the synchronization instruction triggered based on the synchronization control, the target demand use case in the first demand service is synchronized to the second demand service. Through the application, the synchronization efficiency and accuracy can be improved.

Description

Technical Field

[0001] This application relates to computer technology, and more particularly to a method, apparatus, device, computer-readable storage medium, and computer program product for synchronizing a requirement use case. Background Technology

[0002] The requirements management system contains many similar requirement services. For example, in payment scenarios, there are multiple payment channels such as application (APP) payment, webpage (H5) payment, and Java Servlet Application Programming Interface (JSAPI) payment. When the functionality of one of these similar requirement services is updated, and the updated functionality needs to be synchronized to other similar requirement services—for example, after APP payment adds fingerprint verification functionality, extending and synchronizing fingerprint verification to H5 payment or JSAPI payment channels—it is necessary to update the requirement use cases in multiple requirement services simultaneously.

[0003] The synchronization strategy used in related technologies usually involves comparing different code versions in the development code tool and inserting or replacing code content. This method requires comparing and synchronizing the code involved in each use case of each requirement service one by one. The synchronization efficiency is low, and the synchronization effect cannot be viewed intuitively. It is easy to miss or make mistakes, resulting in low synchronization accuracy. Summary of the Invention

[0004] This application provides a synchronization method, apparatus, device, computer-readable storage medium, and computer program product for a specific use case, which can improve synchronization efficiency and accuracy.

[0005] The technical solution of this application embodiment is implemented as follows:

[0006] This application provides a method for synchronizing requirement use cases, including:

[0007] In the first area of ​​the demand comparison view, at least one first demand use case corresponding to the first demand service is displayed, and in the second area, at least one second demand use case corresponding to the second demand service is displayed, along with a synchronization control.

[0008] The first requirement service and the second requirement service are used to implement the target function; the synchronization control is used to synchronize different requirement use cases in the first requirement service and the second requirement service.

[0009] In response to a synchronization command triggered by the synchronization control, the target requirement use case in the first requirement service is synchronized to the second requirement service.

[0010] This application provides a synchronization device for a required use case, including:

[0011] The display module is used to display at least one first requirement use case corresponding to the first requirement service in the first area of ​​the requirement comparison view, and at least one second requirement use case corresponding to the second requirement service in the second area, as well as a synchronization control.

[0012] The first requirement service and the second requirement service are used to implement the target function; the synchronization control is used to synchronize different requirement use cases in the first requirement service and the second requirement service.

[0013] The synchronization module is used to synchronize the target requirement use case in the first requirement service to the second requirement service in response to the synchronization command triggered by the synchronization control.

[0014] In the above scheme, the display module is further configured to display a synchronization start control in the demand comparison view; in response to a trigger operation on the synchronization start control, the demand comparison mode is adjusted to the demand synchronization mode; in the demand synchronization mode, in the first area of ​​the demand comparison view, at least one operable first demand use case corresponding to the first demand service is displayed, and in the second area, at least one operable second demand use case corresponding to the second demand service is displayed.

[0015] In the above scheme, the synchronization module is further configured to, in response to the selection operation of the target demand use case in the at least one first demand use case, use the target demand use case as the demand use case to be synchronized; and in response to the synchronization instruction triggered based on the target demand use case and the synchronization control, synchronize the target demand use case in the first demand service to the second demand service.

[0016] In the above scheme, the synchronization module is further configured to, in response to a selection operation for a target original requirement use case in the at least one second requirement use case, obtain the location of the target original requirement use case and determine a synchronization location based on the location; based on the target requirement use case, in response to a trigger operation for the synchronization control, receive the synchronization instruction; and in response to the synchronization instruction, synchronize the target requirement use case in the first requirement service to the synchronization location in the second requirement service.

[0017] In the above scheme, after determining the synchronization position based on the position, the device further includes: a clearing module, used to display a clearing control in an operable state in the demand comparison view; in response to a trigger operation on the clearing control, clearing the selection operation, and controlling the clearing control to switch from the operable state to the inoperable state.

[0018] In the above scheme, when the synchronization control is used to insert different requirement use cases in the first requirement service and the second requirement service, after the target requirement use case is selected as the requirement use case to be synchronized, the synchronization module is further configured to display at least one insertable original requirement use case in the second requirement use case in the second area using a first display style, and display non-insertable original requirement use cases in the second requirement use case using a second display style; wherein, the first display style indicates that the corresponding original requirement use case is in an operable state, and the second display style indicates that the corresponding original requirement use case is in an inoperable state; in response to the selection operation of the target original requirement use case in the at least one insertable original requirement use case, the location of the target original requirement use case is obtained.

[0019] In the above scheme, the synchronization module is further configured to determine the location of the target original requirement use case as the synchronization position when the synchronization control is used to replace different requirement use cases in the first requirement service and the second requirement service; and to replace the target original requirement use case in the second requirement service located at the synchronization position with the target requirement use case in the first requirement service.

[0020] In the above scheme, the synchronization module is further configured to, when the synchronization control is used to insert different requirement use cases in the first requirement service and the second requirement service, determine the next position in the second requirement service that is adjacent to the position of the target original requirement use case as the synchronization position; and insert the target requirement use case in the first requirement service into the synchronization position in the second requirement service.

[0021] In the above scheme, the synchronization module is further configured to obtain the first requirement type corresponding to the target requirement use case and the second requirement type corresponding to the target original requirement use case; based on the first requirement type and the second requirement type, to perform a legality verification on whether the target requirement use case can be inserted into the synchronization position in the second requirement service; and when the verification is successful, to insert the target requirement use case in the first requirement service into the synchronization position in the second requirement service.

[0022] In the above scheme, the synchronization module is further configured to, when the synchronization control is used to replace different requirement use cases in the first requirement service and the second requirement service, receive the synchronization instruction based on the target requirement use case and in response to the trigger operation of the synchronization control; and, in response to the synchronization instruction, automatically replace the original target requirement use case that was replaced in the second requirement service with the target requirement use case in the first requirement service; wherein the original target requirement use case and the target requirement use case are different in content but are used to achieve the same function.

[0023] In the above scheme, the synchronization module is further configured to, when the synchronization control is used to insert different demand use cases in the first demand service and the second demand service, based on the target demand use case, and in response to a first trigger operation on the synchronization control, display a position selection prompt message to prompt for selecting an insertion position in the second demand service; based on the position selection prompt message, in response to a selection operation on the target original demand use case in the at least one second demand use case, determine the location of the target original demand use case; in response to a second trigger operation on the synchronization control, receive the synchronization instruction; and in response to the synchronization instruction, determine the next position in the second demand service adjacent to the location of the target original demand use case as the target insertion position, and insert the target demand use case in the first demand service into the target insertion position in the second demand service.

[0024] In the above scheme, the synchronization module is further configured to, when the synchronization control is used to insert different demand use cases in the first demand service and the second demand service, based on the target demand use case, and in response to a third trigger operation on the synchronization control, display location recommendation information for recommending the insertion position in the second demand service, the location recommendation information including a recommended target insertion position; receive the synchronization instruction in response to a confirmation operation on the location recommendation information; and, in response to the synchronization instruction, insert the target demand use case in the first demand service into the target insertion position in the second demand service.

[0025] In the above scheme, the synchronization module is further configured to, in response to a selection operation for a target original requirement use case in the at least one second requirement use case, use the target original requirement use case as the requirement use case to be replaced; when the synchronization control is used to replace different requirement use cases in the first requirement service and the second requirement service, based on the target original requirement use case, receive the synchronization instruction in response to a trigger operation for the synchronization control; in response to the synchronization instruction, automatically filter out the target requirement use case corresponding to the target original requirement use case from the first requirement service, and replace the target original requirement use case in the second requirement service with the target requirement use case in the first requirement service.

[0026] In the above scheme, the synchronization module is further configured to, in response to a synchronization instruction triggered by the synchronization control, determine that the target requirement use case in the first requirement service is about to be synchronized to the requirement use case to be synchronized corresponding to the synchronization position in the second requirement service; obtain the association relationship between the target requirement use case and the requirement use case to be synchronized; and when the association relationship indicates that the target requirement use case and the requirement use case to be synchronized satisfy the synchronization association rule, synchronize the target requirement use case in the first requirement service to the synchronization position in the second requirement service.

[0027] In the above scheme, after the target requirement use case in the first requirement service is synchronized to the second requirement service, the device further includes: a saving module, used to display a saving control in the requirement comparison view; in response to a trigger operation on the saving control, the target requirement use case synchronized to the second requirement service is saved to the use case library of the second requirement service; wherein, the requirement use cases saved in the use case library are used to display when comparing the requirement use cases of the second requirement service.

[0028] In the above scheme, before synchronizing the target requirement use case in the first requirement service to the second requirement service, the device further includes: an undo display module, used to display an undo control in the requirement comparison view using a third display style, the third display style indicating that the undo control is in an inoperable state; before saving the target requirement use case synchronized to the second requirement service to the use case library of the second requirement service, the device further includes: an undo module, used to display the undo control using a fourth display style, the fourth display style indicating that the undo control is in an operable state; in response to a trigger operation on the undo control in the operable state, the synchronized target requirement use case is undoed from the second requirement service, and the undo control is controlled to revert from the fourth display style to the third display style.

[0029] This application provides an electronic device, including:

[0030] Memory, used to store executable instructions;

[0031] The processor, when executing executable instructions stored in the memory, implements the synchronization method for the required use cases provided in the embodiments of this application.

[0032] This application provides a computer-readable storage medium storing executable instructions for inducing a processor to execute a synchronization method for the required use cases provided in this application.

[0033] This application provides a computer program product, including a computer program or instructions, which, when executed by a processor, implements the synchronization method for the required use cases provided in this application.

[0034] The embodiments of this application have the following beneficial effects:

[0035] In the embodiments of this application, at least one first requirement use case corresponding to a first requirement service is displayed in the first area of ​​the requirement comparison view, and at least one second requirement use case corresponding to a second requirement service is displayed in the second area, along with a synchronization control. In response to a synchronization command triggered by the synchronization control, the target requirement use case in the first requirement service is synchronized to the second requirement service. Thus, when synchronizing a requirement use case for implementing different functions within requirement services with the same functionality, the requirement comparison view displays the requirement use cases included in different requirement services, facilitating the synchronization of the target requirement use case in the first requirement service that differs from that in the second requirement service to the second requirement service via the synchronization control. This improves synchronization efficiency, and the synchronization effect can be displayed in real-time in the requirement comparison view for user viewing, thereby improving synchronization accuracy. Attached Figure Description

[0036] Figure 1 A schematic diagram of the architecture of a synchronization system 100 for use cases provided in embodiments of this application;

[0037] Figure 2 This is a schematic diagram of the structure of the electronic device 500 provided in the embodiments of this application;

[0038] Figure 3 A flowchart illustrating the synchronization method for the required use cases provided in the embodiments of this application;

[0039] Figure 4 A comparative diagram of requirements provided for embodiments of this application;

[0040] Figure 5 A synchronization diagram illustrating the use cases required for embodiments of this application;

[0041] Figure 6 A synchronization diagram illustrating the use cases required for embodiments of this application;

[0042] Figure 7 A synchronization diagram illustrating the use cases required for embodiments of this application;

[0043] Figure 8 A flowchart illustrating the synchronization method for the required use cases provided in the embodiments of this application;

[0044] Figure 9 A flowchart illustrating the synchronization method for the required use cases provided in this application embodiment. Detailed Implementation

[0045] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0046] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0047] In the following description, the terms “first, second…” are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that “first, second…” may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0048] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0049] Before providing a further detailed description of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained, and the nouns and terms involved in the embodiments of this application shall be interpreted as follows.

[0050] 1) Client: An application running on a terminal that provides various services, such as a demand management client, a video client, a game client, etc.

[0051] 2) In response, used to indicate the conditions or states on which the operation performed depends. When the conditions or states on which it depends are met, one or more operations performed may be performed in real time or with a set delay. Unless otherwise specified, there is no restriction on the order in which the multiple operations are performed.

[0052] 3) A requirement use case refers to the steps an actor takes to implement a specific function within a corresponding requirement service. A requirement service may involve multiple requirement use cases, and the function corresponding to each requirement use case is a sub-function of the corresponding requirement service. For example, if a requirement service is used to implement a payment function, and implementing this requirement service requires execution according to four steps: request, verification, response, and feedback, then request, verification, response, and feedback each correspond to a requirement use case. That is, request requirement use case (used to implement the payment request function), verification requirement use case (used to implement the request verification function), response requirement use case (used to implement the payment response function), and feedback requirement use case (used to implement the payment feedback function). It can be understood that each requirement use case may include at least one sub-requirement use case. For example, taking the verification requirement use case as an example, the verification requirement use case is used to verify the legality of the payment request, which may include verifying the feedback result of the payment system, verifying whether to prompt the user of payment fraud risk, and so on.

[0053] See Figure 1 , Figure 1 The schematic diagram of the architecture of the synchronization system 100 for the required use case provided in the embodiments of this application shows that, in order to support an exemplary application, the terminal (terminal 400-1 and terminal 400-2 are shown as examples) connects to the server 200 through the network 300. The network 300 can be a wide area network or a local area network, or a combination of the two, and uses a wireless link to realize data transmission.

[0054] In practical applications, the terminal can be various types of user terminals such as smartphones, tablets, and laptops, or any combination of two or more of these data processing devices such as desktop computers, televisions, or data processing devices; the server 200 can be a single server configured to support various services, a server cluster, or a cloud server, etc.

[0055] In practical applications, the terminal is equipped with clients, such as demand management clients, video clients, and game clients. When a user compares different demand services (such as the first demand service and the second demand service) through the client on the terminal, the terminal sends a comparison request to the server 200. Based on the comparison request, the server 200 obtains at least one first demand use case included in the first demand service and at least one second demand use case included in the second demand service, identifies whether the first demand use case and the second demand use case are used to implement the same function, and feeds back the identification result to the terminal. After receiving the identification result, the terminal displays at least one first demand use case corresponding to the first demand service in the first area of ​​the demand comparison view, and displays at least one second demand use case corresponding to the second demand service in the second area, as well as a synchronization control. When the terminal receives a synchronization command triggered by the synchronization control, it can respond to the synchronization command and synchronize the target demand use cases in the first demand service that are different from those in the second demand service to the second demand service, improving synchronization efficiency. The synchronization effect can be displayed in real time in the demand comparison view for easy viewing by the user, and the accuracy of synchronization is improved.

[0056] See Figure 2 , Figure 2 This is a schematic diagram of the structure of the electronic device 500 provided in the embodiments of this application. In practical applications, the electronic device 500 can be... Figure 1 The terminal or server 200 in the middle, with electronic devices as Figure 1 Taking the terminal shown as an example, an electronic device implementing the synchronization method of the required use case of the embodiments of this application will be described. Figure 2 The illustrated electronic device 500 includes at least one processor 510, a memory 550, at least one network interface 520, and a user interface 530. The various components in the electronic device 500 are coupled together via a bus system 540. It is understood that the bus system 540 is used to implement communication between these components. In addition to a data bus, the bus system 540 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 3 The general labeled all buses as Bus System 540.

[0057] The processor 510 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0058] User interface 530 includes one or more output devices 531 that enable the presentation of media content, including one or more speakers and / or one or more visual displays. User interface 530 also includes one or more input devices 532, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0059] The memory 550 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state storage, hard disk drives, optical disk drives, etc. The memory 550 may optionally include one or more storage devices physically located away from the processor 510.

[0060] The memory 550 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), and the volatile memory may be random access memory (RAM). The memory 550 described in this application embodiment is intended to include any suitable type of memory.

[0061] In some embodiments, memory 550 is capable of storing data to support various operations, examples of which include programs, modules, and data structures or subsets or supersets thereof, as illustrated below.

[0062] Operating system 551 includes system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, driver layer, etc., for implementing various basic business functions and handling hardware-based tasks;

[0063] The network communication module 552 is used to reach other computing devices via one or more (wired or wireless) network interfaces 520, exemplary network interfaces 520 including: Bluetooth, WiFi, and Universal Serial Bus (USB), etc.

[0064] Presentation module 553 is configured to enable the presentation of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more output devices 531 (e.g., a display screen, a speaker, etc.) associated with user interface 530;

[0065] The input processing module 554 is used to detect and translate one or more user inputs or interactions from one or more input devices 532.

[0066] In some embodiments, the synchronization device for the required use cases provided in this application can be implemented in software. Figure 2 A synchronization device 555 for a required use case, stored in memory 550, is shown. It can be software in the form of programs and plug-ins, including the following software modules: display module 5551 and synchronization module 5552. These modules are logical and can therefore be arbitrarily combined or further split according to the functions implemented. The functions of each module will be described below.

[0067] In other embodiments, the synchronization device for the requirement use cases provided in this application can be implemented in hardware. As an example, the synchronization device for the requirement use cases provided in this application can be a processor in the form of a hardware decoding processor, which is programmed to execute the synchronization method for the requirement use cases provided in this application. For example, the processor in the form of a hardware decoding processor can be one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0068] Based on the above description of the synchronization system for the requirement use cases provided in the embodiments of this application, the synchronization method for the requirement use cases provided in the embodiments of this application will be described below. In actual implementation, this method can be... Figure 1 The terminal or server 200 shown can be implemented independently, or it can be... Figure 1 The terminal and server 200 are shown in the diagram, working together. The following will combine... Figure 1 and Figure 3 , Figure 3 A flowchart illustrating the synchronization method for the required use cases provided in this application embodiment is shown below. Figure 1 The following is an example of a terminal implementing the synchronization method for the required use cases provided in the embodiments of this application.

[0069] Step 101: In the first area of ​​the demand comparison view, the terminal displays at least one first demand use case corresponding to the first demand service, and in the second area, it displays at least one second demand use case corresponding to the second demand service, as well as a synchronization control.

[0070] Among them, the first requirement service and the second requirement service are used to implement the target function, that is, these two requirement services are used to implement the same function. For example, the first requirement service is APP payment and the second requirement service is H5 payment. Both are used to implement the payment function. A requirement service can involve multiple requirement use cases. The function corresponding to each requirement use case belongs to the sub-function of the corresponding requirement service. For example, the first requirement service (used to implement the payment function) includes requirement use case A1 (used to implement the payment request function), requirement use case A2 (used to implement the request verification function), requirement use case A3 (used to implement the response function), and so on. Furthermore, requirement use cases that perform the same function within at least one first requirement use case included in the first requirement service and at least one second requirement use case included in the second requirement service may have a corresponding relationship. For example, requirement use case A1 in the first requirement service and requirement use case B1 in the second requirement service that perform the payment request function may be displayed in a corresponding relationship (left-right correspondence) in the requirement comparison view. If there are requirement use cases that perform different functions within at least one first requirement use case included in the first requirement service and at least one second requirement use case included in the second requirement service, i.e., requirement use cases to be synchronized, a blank line will be used to replace the requirement use case to be synchronized in the requirement service that does not have the requirement use case to be synchronized. For example, if the first requirement service has a first requirement use case A2 that performs function 1, and the second requirement service does not have a second requirement use case that performs function 1, a blank line will be displayed in the second requirement service at the position corresponding to the first requirement use case A2. Of course, in practical applications, requirement use cases that perform the same function within at least one first requirement use case included in the first requirement service and at least one second requirement use case included in the second requirement service may not be displayed in a corresponding relationship in the requirement comparison view.

[0071] The synchronization control is used to synchronize different use cases (use cases to be synchronized) in the first and second demand services. Different use cases include those with different functionalities in the two services. For example, if the first service is an app payment service with fingerprint verification and the second service is an H5 payment service without fingerprint verification, then the first service has use cases for implementing fingerprint verification, while the second service does not. Therefore, the use cases for implementing fingerprint verification are considered different use cases in the first and second services. Furthermore, different use cases can also include use cases with partially different functionalities in the two services. For instance, if both the first and second services have fingerprint verification, but the fingerprint verification in the first service is more secure than that in the second service, then the fingerprint verification in the first service is considered an upgraded version of the fingerprint verification in the second service. Therefore, the different use cases in these two fingerprint verification versions are considered different use cases in the first and second services.

[0072] In some embodiments, the terminal may display at least one first demand use case corresponding to a first demand service in a first area of ​​a demand comparison view and at least one second demand use case corresponding to a second demand service in a second area, by: displaying a synchronization enable control in the demand comparison view; adjusting the demand comparison mode to a demand synchronization mode in response to a trigger operation on the synchronization enable control; and in the demand synchronization mode, displaying at least one operable first demand use case corresponding to a first demand service in the first area of ​​the demand comparison view and at least one operable second demand use case corresponding to a second demand service in the second area.

[0073] See Figure 4 , Figure 4This is a schematic diagram of demand comparison provided in the embodiments of this application. The demand comparison view displays the demand use cases (observable but not operable) of the first demand service and the second demand service respectively in the demand comparison mode, as well as the synchronization start control 401. When the user triggers the synchronization start control, the terminal responds to the trigger operation and adjusts the demand comparison mode to the demand synchronization mode. In the demand synchronization mode, the demand use cases (such as demand use cases associated with operable options or selection boxes, which can be operated) of the first demand service and the second demand service respectively are displayed, as well as the synchronization control 402 (such as replacement control or insertion control). In this comparison view, the first demand service (the demand service to be synchronized) is located in the first area (left area), and the second demand service (the demand service to be synchronized) is located in the second area (right area). For example, the first demand service is an APP payment service with fingerprint verification, and the second demand service is an H5 payment service that does not yet have fingerprint verification. The fingerprint verification function in the APP payment service needs to be synchronized to the H5 payment service. In this comparison view, the first area displays multiple demand use cases (including demand use cases for implementing fingerprint verification) of the APP payment service, and the second area displays multiple demand use cases (excluding demand use cases for implementing fingerprint verification, or demand use cases for implementing fingerprint verification that need to be updated) of the H5 payment service. The synchronization control can be used to synchronize the demand use cases for implementing fingerprint verification in the APP payment service to the H5 payment service, so that the H5 payment service also has the fingerprint verification function of the APP payment service.

[0074] Step 102: In response to the synchronization command triggered by the synchronization control, synchronize the target requirement use case in the first requirement service to the second requirement service.

[0075] In some embodiments, the terminal may synchronize a target demand use case in a first demand service to a second demand service in response to a synchronization instruction triggered by a synchronization control in the following manner: in response to a selection operation for a target demand use case in at least one first demand use case, the target demand use case is selected as a demand use case to be synchronized; in response to a synchronization instruction triggered by a synchronization control based on the target demand use case, the target demand use case in the first demand service is synchronized to the second demand service.

[0076] Here, during synchronization, the target requirement use case to be synchronized is first selected from the requirement use cases included in the first requirement service to be synchronized. Then, based on the selected target requirement use case and the synchronization control, the corresponding synchronization instruction is triggered. In response to the synchronization instruction, the target requirement use case in the first requirement service is synchronized to the second requirement service, so that the second requirement service has the function implemented by the target requirement use case.

[0077] In some embodiments, the terminal may synchronize a target requirement use case in a first requirement service to a second requirement service in response to a synchronization instruction triggered based on a target requirement use case and a synchronization control, in the following manner: in response to a selection operation for a target original requirement use case in at least one second requirement use case, obtain the location of the target original requirement use case and determine a synchronization location based on the location; based on the target requirement use case, in response to a trigger operation for the synchronization control, receive a synchronization instruction; and in response to the synchronization instruction, synchronize the target requirement use case in the first requirement service to the synchronization location in the second requirement service.

[0078] Here, after selecting the target requirement use case to be synchronized from the requirement use cases included in the first requirement service to be synchronized, the synchronization position (such as the insertion position or replacement position) can be determined from the second requirement service to be synchronized. For example, by clicking the option or selection box corresponding to the target original requirement use case in the second requirement service, the location of the target original requirement use case can be determined first, and the synchronization position can be determined based on the location of the target original requirement use case. After determining the synchronization position, when the user triggers the synchronization control, the terminal responds to the trigger operation, receives the synchronization instruction, and responds to the synchronization instruction to synchronize the target requirement use case in the first requirement service to the synchronization position in the second requirement service, so as to display the target requirement use case at the synchronization position in the second requirement service.

[0079] In some embodiments, the terminal can determine the synchronization position based on location in the following manner: when the synchronization control is used to replace different requirement use cases in the first requirement service and the second requirement service, the location of the target original requirement use case is determined as the synchronization position; correspondingly, the terminal can synchronize the target requirement use case in the first requirement service to the synchronization position in the second requirement service in the following manner: replace the target original requirement use case in the second requirement service that is at the synchronization position with the target requirement use case in the first requirement service.

[0080] Here, after the original requirement use case in the second requirement service is determined, if the synchronization control is used to replace different requirement use cases, the location of the original requirement use case in the second requirement service is taken as the synchronization location (i.e., the replacement location), and the target original requirement use case in the second requirement service located at the synchronization location is replaced with the target requirement use case in the first requirement service, so that the second requirement service has the function implemented by the target requirement use case in the first requirement service.

[0081] In some embodiments, the terminal can determine the synchronization position based on location in the following manner: when the synchronization control is used to insert different demand use cases in the first demand service and the second demand service, the next position in the second demand service that is adjacent to the position of the target original demand use case is determined as the synchronization position; correspondingly, the terminal can synchronize the target demand use case in the first demand service to the synchronization position in the second demand service in the following manner: insert the target demand use case in the first demand service into the synchronization position in the second demand service.

[0082] Here, after the original requirement use case in the second requirement service is determined, if the synchronization control is used for insertion between different requirement use cases, the next position adjacent to the position of the original requirement use case in the second requirement service is determined as the synchronization position (i.e., the insertion position), and the target requirement use case in the first requirement service is inserted into the synchronization position in the second requirement service, so that the second requirement service has the function implemented by the target requirement use case in the first requirement service.

[0083] In some embodiments, the terminal may insert a target requirement use case in the first requirement service into the synchronization position in the second requirement service in the following manner: obtain the first requirement type corresponding to the target requirement use case and the second requirement type corresponding to the target original requirement use case; perform a legality verification on whether the target requirement use case can be inserted into the synchronization position in the second requirement service based on the first requirement type and the second requirement type; and insert the target requirement use case in the first requirement service into the synchronization position in the second requirement service after the verification is successful.

[0084] Here, before inserting the target requirement use case from the first requirement service into the synchronization position in the second requirement service, a validity check is performed to verify whether the target requirement use case can be inserted into the synchronization position in the second requirement service. For example, for the first and second requirement services used to implement the payment function, if the target requirement use case selected from the first requirement service is used to implement the payment response function, then the validity check is performed to verify whether the target requirement use case can be inserted into the synchronization position according to the four steps required to implement the requirement service: request-verification-response-feedback. If the synchronization position is after the requirement use case used to implement the request verification function (verification step) and before the requirement use case used to implement the payment feedback function (feedback step), then the verification is considered successful (i.e., the target requirement use case can be inserted into the synchronization position). Only after the verification is successful is the target requirement use case from the first requirement service inserted into the synchronization position in the second requirement service. In this way, the insertion of the target requirement use case from the first requirement service into an unsuitable position in the second requirement service can be avoided, thus improving the accuracy of synchronization.

[0085] In some embodiments, when the synchronization control is used to insert different demand use cases in the first demand service and the second demand service, after the terminal selects the target demand use case as the demand use case to be synchronized, it can also display at least one insertable original demand use case in the second demand use case in the second area using a first display style, and display non-insertable original demand use cases in the second demand use case using a second display style; wherein, the first display style indicates that the corresponding original demand use case is in an operable state, and the second display style indicates that the corresponding original demand use case is in an inoperable state; accordingly, the terminal can obtain the location of the target original demand use case in response to a selection operation for the target original demand use case in at least one second demand use case: in response to a selection operation for the target original demand use case in at least one insertable original demand use case, obtain the location of the target original demand use case.

[0086] Here, when the synchronization control is used to insert different requirement use cases from the first requirement service and the second requirement service, before the user selects the target requirement use case to be synchronized from the first requirement service in the first area, the second requirement use cases in the second requirement service are displayed in the same display style. After the user selects the target requirement use case to be synchronized from the first requirement service in the first area, the terminal can automatically filter out the original requirement use cases that can be inserted from at least one of the second requirement use cases included in the second requirement service. For example, for the first requirement service and the second requirement service used to implement the payment function, if the target requirement use case selected from the first requirement service is used to implement the payment response function, then the filtering is performed according to the four steps of request-verification-response-feedback required to implement the requirement service, and the original requirement use cases that can be inserted to implement the payment response function are filtered out from the second service. Initial requirement use cases, such as those following the requirement use case for implementing request verification (verification step) and preceding the requirement use case for implementing payment feedback (feedback step), are designated as insertable initial requirement use cases (i.e., in an operable state, such as selectable requirement use cases). Other use cases are designated as non-insertable initial requirement use cases (i.e., in an inoperable state, such as unselectable requirement use cases). Different types of initial requirement use cases are displayed differently. For example, an operable initial requirement use case is displayed using a first display style (e.g., highlighted), while an inoperable initial requirement use case is displayed using a second display style (e.g., grayscale). This provides users with significant prompts, allowing them to quickly select the most suitable target initial requirement use case to determine the corresponding synchronization position, avoiding invalid operations and improving synchronization efficiency.

[0087] See Figure 5 , Figure 5This is a schematic diagram of the synchronization of demand use cases provided in the embodiments of this application. When the synchronization control is used to insert different demand use cases in the first demand service and the second demand service, after the user selects the target demand use case 501 from the first demand service in the first area, the original demand use case that is in an operable state is automatically highlighted in the second demand service in the second area, and other original demand use cases other than the highlighted original demand use case are displayed in grayscale. When the user selects the target original demand use case 502, the location of the target original demand use case is obtained, and the next position in the second demand service adjacent to the location of the target original demand use case is determined as the synchronization position, so as to insert the target demand use case 501 in the first demand service into the next position adjacent to the location of the target original demand use case 502.

[0088] In some embodiments, after the terminal determines the synchronization location based on the location, it can also display a clear control in an operable state in the demand comparison view; in response to the trigger operation for the clear control, a clear selection operation is performed, and the clear control is controlled to switch from an operable state to an inoperable state.

[0089] Here, before the selection operation is performed, the clear control is in an inoperable state. At this time, the clear control can be displayed in grayscale. As the selection operation is performed, after selecting the target requirement use case to be synchronized in the first area or the target original requirement use case to be synchronized in the second area, the clear control switches from an inoperable state to an operable state. At this time, the clear control can be highlighted, and the previous selection operation can be cleared by clearing the clear control. After clearing the selection operation, the requirement use case to be synchronized can be selected again from the first area or the requirement use case to be synchronized can be selected again from the second area. In this way, it is convenient for users to reselect after making a mistake, which helps to improve the accuracy of synchronization.

[0090] In some embodiments, the terminal may synchronize a target requirement use case in a first requirement service to a second requirement service in response to a synchronization instruction triggered based on a target requirement use case and a synchronization control, as follows: when the synchronization control is used to replace different requirement use cases in the first and second requirement services, a synchronization instruction is received based on the target requirement use case in response to a triggering operation on the synchronization control; in response to the synchronization instruction, the original target requirement use case that was replaced in the second requirement service is automatically replaced with the target requirement use case in the first requirement service; wherein the original target requirement use case and the target requirement use case are different in content but are used to implement the same function.

[0091] Here, when the synchronization control is used to replace different requirement use cases in the first requirement service and the second requirement service, if the user selects a target requirement use case from the first requirement service and triggers the synchronization control (replacement control), the terminal receives the corresponding synchronization instruction and, in response to the instruction, automatically filters out replaceable original target requirement use cases from at least one second requirement use case included in the second requirement service. For example, the selected target requirement use case is matched with each second requirement use case included in the second requirement service, and the second requirement use case corresponding to the target requirement use case (which differs from the target requirement use case in content but is used to implement the same function as the target requirement use case) is filtered out as replaceable original target requirement use cases, and the original target requirement use case in the second requirement service is automatically replaced with the target requirement use case in the first requirement service. In this way, the replacement of the corresponding requirement use case can be achieved without selecting the original target requirement use case to be replaced in the second requirement service, thus improving synchronization efficiency.

[0092] In some embodiments, the terminal may synchronize a target requirement use case in a first requirement service to a second requirement service in response to a synchronization instruction triggered based on a target requirement use case and a synchronization control, as follows: when the synchronization control is used to insert different requirement use cases in the first and second requirement services, based on the target requirement use case, in response to a first triggering operation on the synchronization control, displaying a position selection prompt to prompt for selecting an insertion position in the second requirement service; based on the position selection prompt, in response to a selection operation on a target original requirement use case in at least one second requirement use case, determining the location of the target original requirement use case; in response to a second triggering operation on the synchronization control, receiving a synchronization instruction; and in response to the synchronization instruction, determining the next position in the second requirement service adjacent to the location of the target original requirement use case as the target insertion position, and inserting the target requirement use case in the first requirement service into the target insertion position in the second requirement service.

[0093] See Figure 6 , Figure 6This is a schematic diagram of the synchronization of demand use cases provided in the embodiments of this application. When the synchronization control is used to insert different demand use cases in the first demand service and the second demand service, if the user selects the target demand use case 601 from the first demand service and triggers the synchronization control (insertion control) 602, the terminal responds to the triggering operation and displays a location selection prompt message 603 such as "Please select the insertion position first". Based on the location selection prompt message 603, the user can select the target original demand use case from the second demand use cases included in the second demand service. The terminal responds to the selection operation and determines the location of the target original demand use case. At this time, when the user triggers the synchronization control 602 again, the terminal can receive the corresponding synchronization instruction and determine the next position in the second demand service adjacent to the location of the target original demand use case as the target insertion position, and insert the target demand use case in the first demand service into the target insertion position in the second demand service.

[0094] Understandably, while displaying the location selection prompt, the terminal can automatically filter out suitable original requirement use cases from at least one second requirement use case included in the second requirement service. For example, for a first requirement service and a second requirement service used to implement payment functionality, if the target requirement use case selected from the first requirement service is used to implement payment response functionality, then the filtering is performed according to the four steps required to implement the requirement service: request-verification-response-feedback. Original requirement use cases that can be inserted into the second requirement service to implement payment response functionality are then selected, such as those located after the requirement use case (verification step) used to implement request verification functionality and those located after the requirement use case (reply step) used to implement payment feedback functionality. The requirement use cases preceding the feedback step are designated as insertable original requirement use cases (i.e., in an operational state, such as selectable requirement use cases). Other use cases are designated as non-insertable original requirement use cases (i.e., in an inoperable state, such as unselectable requirement use cases). Different types of original requirement use cases are displayed differently. For example, an operational original requirement use case is displayed using a first display style (e.g., highlighted), while an inoperable original requirement use case is displayed using a second display style (e.g., grayscale). This provides users with clear prompts, allowing them to quickly select the most suitable target original requirement use case to determine the corresponding synchronization position, avoiding invalid operations and improving synchronization efficiency.

[0095] In some embodiments, the terminal may synchronize a target requirement use case in a first requirement service to a second requirement service in response to a synchronization instruction triggered based on a target requirement use case and a synchronization control, as follows: when the synchronization control is used to insert different requirement use cases in the first and second requirement services, based on the target requirement use case, in response to a third triggering operation on the synchronization control, displaying location recommendation information for recommending the insertion position in the second requirement service, the location recommendation information including a recommended target insertion position; receiving a synchronization instruction in response to a confirmation operation on the location recommendation information; and inserting the target requirement use case in the first requirement service into the target insertion position in the second requirement service in response to the synchronization instruction.

[0096] See Figure 7 , Figure 7 This is a schematic diagram illustrating the synchronization of demand use cases provided in an embodiment of this application. When the synchronization control is used to insert different demand use cases in the first demand service and the second demand service, if the user selects a target demand use case 701 from the first demand service and triggers the synchronization control (insertion) 702, the terminal responds to the triggering operation and displays recommendation information 703 such as "It is recommended to insert below the second demand use case 3". The recommended target insertion position included in the recommendation information 703 is the next position adjacent to the position of the second demand use case 3. The target insertion position included in the recommendation information is based on the degree of connection (or coherence) between the target demand use case selected from the first demand service and the various second demand use cases included in the second demand service. For example, for the first and second demand services used to implement the payment function, if the target demand use case selected from the first demand service is used to implement the payment response function, then the four steps of request-verification-response-feedback required to implement the demand service are used for filtering. The original demand use cases that can be inserted into the second demand service to implement the payment response function are filtered out. For example, the demand use case located after the demand use case (verification step) used to implement the request verification function and before the demand use case (feedback step) used to implement the payment feedback function are recommended as insertable demand use cases in the recommendation information (such as the second demand use case 3). Then, the target insertion position is determined based on the position of the insertable demand use cases recommended in the recommendation information.

[0097] In practical applications, while presenting recommended information, the terminal can also display "Confirm" and "Change" buttons for the corresponding recommended information. When the user triggers the "Confirm" button, the terminal receives the confirmation operation for the recommended information, i.e., receives a synchronization instruction. In response to this instruction, the terminal inserts the target requirement use case from the first requirement service into the target insertion position in the second requirement service, and postpones all other original requirement use cases that were previously at that target insertion position. When the user triggers the "Change" button, the terminal responds to this trigger operation and updates the display with a new recommended information. The target insertion position in the new recommended information differs from the target insertion position in the original recommended information (e.g., below the second requirement use case 3). The user can use the target insertion position in the new recommended information as the insertion position for the target requirement use case. Of course, if the user is still not satisfied with the target insertion position in the new recommended information, they can trigger the corresponding "Change" button to select a new target insertion position until they are satisfied. Through this method, the terminal can intelligently recommend insertion positions to the user, improving synchronization efficiency and accuracy.

[0098] In some embodiments, the terminal may synchronize a target requirement use case in a first requirement service to a second requirement service in response to a synchronization instruction triggered based on a target requirement use case and a synchronization control, in the following manner: in response to a selection operation for a target original requirement use case in at least one second requirement use case, the target original requirement use case is used as the requirement use case to be replaced; when the synchronization control is used to replace different requirement use cases in the first and second requirement services, a synchronization instruction is received based on the target original requirement use case in response to a trigger operation on the synchronization control; in response to the synchronization instruction, a target requirement use case corresponding to the target original requirement use case is automatically selected from the first requirement service, and the target original requirement use case in the second requirement service is replaced with the target requirement use case in the first requirement service.

[0099] Here, when the synchronization control is used to replace different requirement use cases in the first requirement service and the second requirement service, if the user selects the target original requirement use case from the second requirement service and triggers the synchronization control (replacement control), the terminal receives the corresponding synchronization instruction and, in response to the synchronization instruction, automatically filters out the target requirement use case corresponding to the original target requirement use case from at least one first requirement use case included in the first requirement service. For example, the target original requirement use case selected from the second requirement service is matched with each of the first requirement use cases included in the first requirement service, and the first requirement use case corresponding to the target original requirement use case (which differs from the target original requirement use case in content but is used to implement the same function as the target requirement use case) is filtered out as the target requirement use case to be replaced, and the original target requirement use case in the second requirement service is automatically replaced with the target requirement use case in the first requirement service. In this way, the replacement of the corresponding requirement use case can be achieved without selecting the target requirement use case to be replaced in the first requirement service, thus improving the synchronization efficiency.

[0100] In some embodiments, the terminal may synchronize a target demand use case in the first demand service to the second demand service in response to a synchronization command triggered by a synchronization control as follows: in response to a synchronization command triggered by a synchronization control, it determines that the target demand use case in the first demand service is about to be synchronized to the corresponding synchronization position in the second demand service; obtains the association relationship between the target demand use case and the synchronization position; when the association relationship indicates that the target demand use case and the synchronization position satisfy the synchronization association rule, it synchronizes the target demand use case in the first demand service to the synchronization position in the second demand service.

[0101] Here, the synchronization association rules are described in ways that are not limited to, but include, the following: field list, rule constraints, quality constraints, and design constraints. The field list is used to determine the legality of some field information involved in the synchronization instruction; the rule constraints are used to perform logical judgments on the synchronization operation indicated by the synchronization instruction; the quality constraints are used to constrain the quality and security of system operation during the synchronization operation indicated by the synchronization instruction; and the design constraints are used to constrain the product presentation in the requirement comparison view. Taking a synchronization instruction used to instruct the synchronization of a requirement use case implementing payment functionality as an example, the field information indicated by the synchronization instruction may include merchant information, transaction information (payee, payer, payment amount), etc. Logical judgments can be used to determine whether the payment account is subject to usage restrictions, whether there are coupons, and the conditions for coupon usage, etc.; quality constraints judge the payment synchronization request volume, system throughput, etc., to ensure the quality and security of system operation during synchronization. During synchronization, the target requirement use case selected in the first requirement service is associated with the requirement use case to be synchronized to the second requirement service (i.e., the aforementioned target original requirement use case). Only when both satisfy the above synchronization association rules will the target requirement use case in the first requirement service be synchronized to the synchronization position in the second requirement service.

[0102] In some embodiments, after the terminal synchronizes the target requirement use case in the first requirement service to the second requirement service, a save control may also be displayed in the requirement comparison view; in response to the trigger operation of the save control, the target requirement use case synchronized to the second requirement service is saved to the use case library of the second requirement service; wherein, the requirement use cases saved in the use case library are used to be displayed when comparing the requirement use cases of the second requirement service.

[0103] Here, after synchronization is complete, the user can save the synchronization result using the save control. The target requirement use case synchronized becomes the new second requirement use case in the second requirement service, which is displayed when requirement comparison is performed again, thereby updating the second requirement use cases in the second requirement service. In practical applications, the requirement comparison view can also display a re-comparison control. The user can use the re-comparison control to re-compare the requirement use cases in the first and second requirement services. When the user triggers the re-comparison control to re-compare, if there are any edited or unsaved synchronization operations, an entry will be prompted to save or cancel the save, so that the re-comparison can be performed after saving or without saving.

[0104] In some embodiments, before the terminal synchronizes the target requirement use case in the first requirement service to the second requirement service, the undo control may be displayed in the requirement comparison view using a third display style, which indicates that the undo control is in an inoperable state. Correspondingly, before the terminal saves the target requirement use case synchronized to the second requirement service to the use case library of the second requirement service, the undo control may also be displayed using a fourth display style, which indicates that the undo control is in an operable state. In response to a trigger operation on the undo control in an operable state, the synchronized target requirement use case is undoed from the second requirement service, and the undo control is controlled to revert from the fourth display style to the third display style.

[0105] Here, after the synchronization command is executed but before the synchronization result is saved, the execution result can be undone using the undo control. This makes it easier for users to reselect after synchronization and helps improve the accuracy of synchronization.

[0106] It is understood that, in the embodiments of this application, the data related to selection operations, confirmation operations, etc., are essentially user information. When the embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0107] The following describes an exemplary application of this application embodiment in a practical application scenario. A requirement management system is a platform that describes product requirements in a structured form. It describes product requirements in natural language, referencing the formatting requirements of the Unified Modeling Language (UML), following a four-step structure of request-validation-response-feedback. Specific constraints and requirements for product performance are described in supplementary constraints using field lists, rule constraints, quality constraints, and design constraints. This application embodiment provides a method for synchronizing requirement use cases. By comparing the structured requirement use case content of a first requirement service (e.g., APP payment) and a second requirement service (e.g., H5 payment) that implement the same function (e.g., payment function) on the requirement management system, the different requirement use case contents are quickly synchronized. In practical applications, synchronization may include replacement and insertion. The following will describe the requirement use case synchronization method provided by this application embodiment from the perspectives of replacement and insertion of requirement use cases between different requirement services.

[0108] like Figure 4As shown, in the demand comparison view under demand comparison mode, the first area (left area) displays at least one first demand use case (observable but not operable) included in the first demand service, and the second area (right area) displays at least one second demand use case (observable but not operable) included in the second demand service, as well as a synchronization start control. When the user triggers the synchronization start control, the terminal responds to the trigger operation by adjusting the demand comparison mode to demand synchronization mode. In demand synchronization mode, the first area displays at least one operable first demand use case in the first demand service (such as one associated with an operable option or checkbox, which is observable and operable), and the second area displays at least one operable second demand use case in the second demand service (such as one associated with an operable option or checkbox, which is observable and operable), as well as synchronization controls (including insert control and replace control).

[0109] For example, if the first required service is an app payment service with fingerprint verification, and the second required service is an H5 payment service that does not yet have fingerprint verification, and the fingerprint verification function in the app payment service needs to be synchronized to the H5 payment service, then the first area of ​​the requirement comparison view will display multiple first requirement use cases included in the app payment service (including requirement use cases for implementing fingerprint verification, or requirement use cases of higher versions for implementing fingerprint verification), and the second area of ​​the comparison view will display multiple second requirement use cases included in the H5 payment service (excluding requirement use cases for implementing fingerprint verification, or including requirement use cases of lower versions for implementing fingerprint verification). When the user triggers the synchronization enable control, the terminal responds to the trigger operation, controls each requirement use case to be in an operable state, and displays synchronization controls (including insert control, replace control), cancel control, clear control, re-compare control, and save control.

[0110] See Figure 8 , Figure 8 The flowchart illustrates the synchronization method for the required use case provided in this application embodiment. Taking the synchronization operation as an insertion operation (i.e., triggering an insertion control) as an example, the method includes:

[0111] Step 201: In response to the selection operation for the target requirement use case in at least one first requirement use case, the terminal selects the target requirement use case as the requirement use case to be inserted.

[0112] For example, the target requirement use case in the first requirement service is used to implement the fingerprint verification function, while the second requirement service does not yet have the fingerprint verification function. Therefore, the target requirement use case is used as the requirement use case to be inserted.

[0113] Step 202: In response to the selection operation for the target original requirement use case in at least one second requirement use case, determine the location of the target original requirement use case.

[0114] Step 203: In response to the trigger operation for the insert control, determine the next position in the second requirement service that is adjacent to the position of the target original requirement use case as the insertion position.

[0115] Step 204: Copy the node data corresponding to the target requirement use case in the first area, and add a new insertion node at the insertion position in the second area.

[0116] Step 205: Insert the node data corresponding to the target requirement use case in the copied first region into the insertion node in the second region.

[0117] In the above steps, the node containing the target requirement use case in the first region (left region) is denoted as leftItemList, and the node containing the target original requirement use case in the second region is denoted as rightItem, with its subscript being targetIndex. The overall step lists for the left and right regions are leftTree and rightTree. When inserting the selected node in the left region into the targetIndex in the right region, a new insertion node is added in the right region, denoted as rightTree.splice(targetIndex,0,…deepClone(leftItemList)). The node data corresponding to the target requirement use case in the first region is pasted into the insertion node. At the same time, other original requirement use cases located at the insertion node and its after can be extended to the right, or a blank row can be added to the same position in the first region, denoted as leftTree.splice(targetIndex,0,…cloneBlankNode(leftItemList)).

[0118] By following the steps above, the target requirement use case in the first requirement service can be inserted into the corresponding position in the second requirement service, so that the second requirement service has the function corresponding to the target requirement use case, such as fingerprint verification function. After successful insertion, the newly inserted target requirement use case in the second requirement service can be highlighted in the requirement comparison view.

[0119] See Figure 9 , Figure 9 The flowchart illustrates the synchronization method for the required use case provided in this application embodiment. Taking the synchronization operation as a replacement operation (i.e., triggering a replacement control) as an example, the method includes:

[0120] Step 301: In response to the selection operation for the target requirement use case in at least one first requirement use case, the terminal selects the target requirement use case as the requirement use case to be replaced.

[0121] Step 302: In response to the selection operation for the target original requirement use case in at least one second requirement use case, determine the location of the target original requirement use case.

[0122] For example, both the first requirement service and the second requirement service have fingerprint verification functions, but the fingerprint verification function in the first requirement service (corresponding to the target requirement use case) is more secure than the fingerprint verification function in the second requirement service (corresponding to the target original requirement use case). Therefore, the fingerprint verification function in the first requirement service can be considered an upgraded version of the fingerprint verification function in the second requirement service, and the target original requirement use case in the second requirement service needs to be replaced with the target requirement use case in the first requirement service.

[0123] Step 303: In response to the trigger operation for the replacement control, determine the location of the target original requirement use case in the second requirement service as the replacement location.

[0124] Step 304: Copy the node data corresponding to the target requirement use case in the first area, and delete the node data corresponding to the original target requirement use case at the replacement position in the second area.

[0125] Step 305: Paste the node data corresponding to the target requirement use case in the copied first area into the replacement position in the second area.

[0126] In the above steps, the node containing the target requirement use case in the first region (left region) is denoted as leftItemList, and the node containing the target original requirement use case in the second region is denoted as rightItem, with its subscript being targetIndex. The overall step lists for the left and right regions are leftTree and rightTree. When replacing the selected node in the left region with the node in the right region, the selected node in the right region is first deleted, denoted as rightTree.splice(startIndex, endIndex – startIndex + 1), and the data of the selected node in the left region is pasted into the selected node in the right region.

[0127] By following the steps above, the target original requirement use case in the second requirement service can be replaced with the target requirement use case in the first requirement service, so that the second requirement service has the function corresponding to the target requirement use case, such as having an upgraded version (the same version as the first requirement service) of fingerprint verification function. After the replacement is successful, the newly replaced target requirement use case in the second requirement service can be highlighted in the requirement comparison view.

[0128] In practical applications, during synchronization (such as the insertion or replacement mentioned above), users can re-compare the use cases in the first and second requirement services through the re-comparison control. When the user triggers the re-comparison control to re-compare, if there are any edited or unsaved synchronization operations, the user will be prompted to save or cancel the save entry so that the re-comparison can be performed after saving or without saving.

[0129] Before performing the selection operation in steps 201-202 or 301-302, the clear control is in an inoperable state. At this time, the clear control can be displayed in grayscale. As the selection operation is performed, after selecting the target requirement use case to be synchronized (inserted or replaced) in the first area or selecting the target original requirement use case to be synchronized (inserted or replaced) in the second area, the clear control switches from an inoperable state to an operable state. At this time, the clear control can be highlighted, and the previous selection operation can be cleared by clearing the clear control. After clearing the selection operation, the target requirement use case to be synchronized can be selected again from the first area or the target original requirement use case to be synchronized can be selected again from the second area. This makes it convenient for users to reselect after making a mistake, which helps to improve the accuracy of synchronization.

[0130] After the synchronization operation is completed but before saving the synchronization results, the undo control can be used to undo the synchronization. This allows users to easily reselect after synchronization, improving the accuracy of the synchronization. After synchronization is complete, users can save the synchronization results using the save control. The synchronized target requirement use case will then be used as a new second requirement use case in the second requirement service for display during subsequent requirement comparisons, thereby updating the second requirement use cases in the second requirement service.

[0131] By using the above method, when synchronizing a requirement use case that implements different functions in requirement services with the same function, the requirement use cases included in different requirement services are displayed in the requirement comparison view. This makes it easy to synchronize the target requirement use case in the first requirement service that is different from that in the second requirement service to the second requirement service through the synchronization control, which improves the synchronization efficiency. Moreover, the synchronization effect can be displayed in real time in the requirement comparison view for easy viewing by the user, and the accuracy of the synchronization is improved.

[0132] The following description continues to illustrate the exemplary structure of the synchronization device 555 for the required use cases provided in the embodiments of this application as a software module. In some embodiments, it is stored in... Figure 2 The software modules in the synchronization device 555 for the use case of the intermediate memory 550 may include:

[0133] Display module 5551 is used to display at least one first requirement use case corresponding to the first requirement service in a first area of ​​the requirement comparison view, and at least one second requirement use case corresponding to the second requirement service in a second area, as well as a synchronization control; wherein the first requirement service and the second requirement service are used to implement the target function; the synchronization control is used to synchronize different requirement use cases in the first requirement service and the second requirement service; synchronization module 5552 is used to synchronize the target requirement use case in the first requirement service to the second requirement service in response to a synchronization command triggered by the synchronization control.

[0134] In some embodiments, the display module is further configured to display a synchronization enable control in the demand comparison view; in response to a trigger operation on the synchronization enable control, adjust the demand comparison mode to a demand synchronization mode; in the demand synchronization mode, in the first area of ​​the demand comparison view, display at least one operable first demand use case corresponding to the first demand service, and in the second area, display at least one operable second demand use case corresponding to the second demand service.

[0135] In some embodiments, the synchronization module is further configured to, in response to a selection operation for a target demand use case in the at least one first demand use case, designate the target demand use case as a demand use case to be synchronized; and in response to a synchronization instruction triggered based on the target demand use case and the synchronization control, synchronize the target demand use case in the first demand service to the second demand service.

[0136] In some embodiments, the synchronization module is further configured to, in response to a selection operation for a target original requirement use case in the at least one second requirement use case, obtain the location of the target original requirement use case and determine a synchronization location based on the location; based on the target requirement use case, in response to a trigger operation for the synchronization control, receive the synchronization instruction; and in response to the synchronization instruction, synchronize the target requirement use case in the first requirement service to the synchronization location in the second requirement service.

[0137] In some embodiments, after determining the synchronization position based on the position, the device further includes: a clearing module, configured to display a clearing control in an operable state in the demand comparison view; in response to a trigger operation on the clearing control, clear the selection operation, and control the clearing control to switch from the operable state to the inoperable state.

[0138] In some embodiments, when the synchronization control is used to insert different requirement use cases in the first requirement service and the second requirement service, after the target requirement use case is selected as the requirement use case to be synchronized, the synchronization module is further configured to display at least one insertable original requirement use case in the second requirement use case in the second area using a first display style, and display non-insertable original requirement use cases in the second requirement use case using a second display style; wherein, the first display style indicates that the corresponding original requirement use case is in an operable state, and the second display style indicates that the corresponding original requirement use case is in an inoperable state; in response to the selection operation of the target original requirement use case in the at least one insertable original requirement use case, the location of the target original requirement use case is obtained.

[0139] In some embodiments, the synchronization module is further configured to, when the synchronization control is used to replace different requirement use cases in the first requirement service and the second requirement service, determine the location of the target original requirement use case as the synchronization location; and replace the target original requirement use case in the second requirement service located at the synchronization location with the target requirement use case in the first requirement service.

[0140] In some embodiments, the synchronization module is further configured to, when the synchronization control is used to insert different requirement use cases in the first requirement service and the second requirement service, determine the next position in the second requirement service adjacent to the position of the target original requirement use case as the synchronization position; and insert the target requirement use case in the first requirement service into the synchronization position in the second requirement service.

[0141] In some embodiments, the synchronization module is further configured to obtain a first requirement type corresponding to the target requirement use case and a second requirement type corresponding to the target original requirement use case; based on the first requirement type and the second requirement type, to perform a validity verification on whether the target requirement use case can be inserted into the synchronization position in the second requirement service; and when the verification is successful, to insert the target requirement use case in the first requirement service into the synchronization position in the second requirement service.

[0142] In some embodiments, the synchronization module is further configured to, when the synchronization control is used to replace different requirement use cases in the first requirement service and the second requirement service, receive the synchronization instruction based on the target requirement use case in response to a trigger operation on the synchronization control; and, in response to the synchronization instruction, automatically replace the original target requirement use case that was replaced in the second requirement service with the target requirement use case in the first requirement service; wherein the original target requirement use case and the target requirement use case are different in content but are used to achieve the same function.

[0143] In some embodiments, the synchronization module is further configured to, when the synchronization control is used to insert different demand use cases in the first demand service and the second demand service, based on the target demand use case, and in response to a first trigger operation on the synchronization control, display a position selection prompt message to prompt for selecting an insertion position in the second demand service; based on the position selection prompt message, in response to a selection operation on a target original demand use case in the at least one second demand use case, determine the location of the target original demand use case; in response to a second trigger operation on the synchronization control, receive the synchronization instruction; and in response to the synchronization instruction, determine the next position in the second demand service adjacent to the location of the target original demand use case as the target insertion position, and insert the target demand use case in the first demand service into the target insertion position in the second demand service.

[0144] In some embodiments, the synchronization module is further configured to, when the synchronization control is used to insert different demand use cases in the first demand service and the second demand service, based on the target demand use case and in response to a third trigger operation on the synchronization control, display location recommendation information for recommending the insertion position in the second demand service, the location recommendation information including a recommended target insertion position; receive the synchronization instruction in response to a determination operation on the location recommendation information; and, in response to the synchronization instruction, insert the target demand use case in the first demand service into the target insertion position in the second demand service.

[0145] In some embodiments, the synchronization module is further configured to, in response to a selection operation for a target original requirement use case in the at least one second requirement use case, use the target original requirement use case as the requirement use case to be replaced; when the synchronization control is used to replace different requirement use cases in the first requirement service and the second requirement service, based on the target original requirement use case, receive the synchronization instruction in response to a trigger operation for the synchronization control; in response to the synchronization instruction, automatically filter out the target requirement use case corresponding to the target original requirement use case from the first requirement service, and replace the target original requirement use case in the second requirement service with the target requirement use case in the first requirement service.

[0146] In some embodiments, the synchronization module is further configured to, in response to a synchronization instruction triggered based on the synchronization control, determine that a target demand use case in the first demand service is about to be synchronized to a demand use case to be synchronized at a synchronization position in the second demand service; obtain the association relationship between the target demand use case and the demand use case to be synchronized; and when the association relationship indicates that the target demand use case and the demand use case to be synchronized satisfy a synchronization association rule, synchronize the target demand use case in the first demand service to the synchronization position in the second demand service.

[0147] In some embodiments, after the target requirement use case in the first requirement service is synchronized to the second requirement service, the apparatus further includes: a saving module, configured to display a saving control in the requirement comparison view; and in response to a trigger operation on the saving control, to save the target requirement use case synchronized to the second requirement service to the use case library of the second requirement service; wherein the requirement use cases saved in the use case library are used to display when performing requirement comparison on the requirement use cases of the second requirement service.

[0148] In some embodiments, before synchronizing the target requirement use case in the first requirement service to the second requirement service, the apparatus further includes: an undo display module, configured to display an undo control in the requirement comparison view using a third display style, the third display style indicating that the undo control is in an inoperable state; before saving the target requirement use case synchronized to the second requirement service to the use case library of the second requirement service, the apparatus further includes: an undo module, configured to display the undo control using a fourth display style, the fourth display style indicating that the undo control is in an operable state; in response to a trigger operation on the undo control in the operable state, undoing the synchronized target requirement use case from the second requirement service, and controlling the undo control to revert from the fourth display style to the third display style.

[0149] This application provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the synchronization method described in the above-described use case of this application.

[0150] This application provides a computer-readable storage medium storing executable instructions. When these executable instructions are executed by a processor, they cause the processor to execute a synchronization method for a required use case provided in this application, such as... Figure 3 The method shown.

[0151] In some embodiments, the computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or it may be a variety of devices including one or any combination of the above-mentioned memories.

[0152] In some embodiments, executable instructions may take the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0153] As an example, executable instructions may, but do not necessarily, correspond to files in a file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple collaborating files (e.g., a file that stores one or more modules, subroutines, or code sections).

[0154] As an example, executable instructions can be deployed to execute on a single computing device, or on multiple computing devices located in one location, or on multiple computing devices distributed across multiple locations and interconnected via a communication network.

[0155] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of this application are included within the scope of protection of this application.

Claims

1. A method for synchronizing requirement use cases, characterized in that, The method includes: In the first area of ​​the demand comparison view, at least one first demand use case corresponding to the first demand service is displayed, and in the second area, at least one second demand use case corresponding to the second demand service is displayed, along with a synchronization control. The first requirement service and the second requirement service are used to implement the target function; the synchronization control is used to synchronize different requirement use cases in the first requirement service and the second requirement service. In response to the selection operation for a target requirement use case in the at least one first requirement use case, the target requirement use case is selected as the requirement use case to be synchronized. When the synchronization control is used to insert different demand use cases in the first demand service and the second demand service, the original demand use cases available for insertion are filtered from the at least one second demand use case. In the second area, at least one insertable original requirement use case in the second requirement use case is displayed using a first display style, and an uninsertable original requirement use case in the second requirement use case is displayed using a second display style; wherein, the first display style indicates that the corresponding original requirement use case is in an operable state, and the second display style indicates that the corresponding original requirement use case is in an inoperable state. In response to a selection operation for a target original requirement use case among the at least one insertable original requirement use cases, the location of the target original requirement use case is obtained, and a synchronization location is determined based on the location. In response to a synchronization command triggered based on the target requirement use case and the synchronization control, the target requirement use case in the first requirement service is synchronized to the synchronization position in the second requirement service.

2. The method as described in claim 1, characterized in that, The first area of ​​the demand comparison view displays at least one first demand use case corresponding to a first demand service, and the second area displays at least one second demand use case corresponding to a second demand service, including: Display the synchronization enable control in the requirements comparison view; In response to the trigger operation of the synchronization start control, the demand comparison mode is adjusted to the demand synchronization mode; In the demand synchronization mode, in the first area of ​​the demand comparison view, at least one operable first demand use case corresponding to the first demand service is displayed, and in the second area, at least one operable second demand use case corresponding to the second demand service is displayed.

3. The method as described in claim 1, characterized in that, The step of synchronizing the target requirement use case in the first requirement service to the synchronization position in the second requirement service in response to a synchronization instruction triggered based on the target requirement use case and the synchronization control includes: Based on the target requirement use case, in response to a trigger operation on the synchronization control, the synchronization instruction is received; In response to the synchronization instruction, the target demand use case in the first demand service is synchronized to the synchronization position in the second demand service.

4. The method as described in claim 3, characterized in that, Determining the synchronization position based on the location includes: When the synchronization control is used to replace different requirement use cases in the first requirement service and the second requirement service, the location of the target original requirement use case is determined as the synchronization location; The step of synchronizing the target demand use case in the first demand service to the synchronization position in the second demand service includes: Replace the target original requirement use case in the second requirement service that is at the synchronization position with the target requirement use case in the first requirement service.

5. The method as described in claim 3, characterized in that, Determining the synchronization position based on the location includes: When the synchronization control is used to insert different requirement use cases in the first requirement service and the second requirement service, the next position in the second requirement service that is adjacent to the position of the target original requirement use case is determined as the synchronization position; The step of synchronizing the target demand use case in the first demand service to the synchronization position in the second demand service includes: Insert the target requirement use case in the first requirement service into the synchronization position in the second requirement service.

6. The method as described in claim 5, characterized in that, The step of inserting the target requirement use case in the first requirement service into the synchronization position in the second requirement service includes: Obtain the first requirement type corresponding to the target requirement use case and the second requirement type corresponding to the target original requirement use case, respectively; Based on the first requirement type and the second requirement type, a legality verification is performed on whether the target requirement use case can be inserted into the synchronization position in the second requirement service; Once the verification is successful, the target requirement use case in the first requirement service is inserted into the synchronization position in the second requirement service.

7. The method as described in claim 3, characterized in that, After determining the synchronization position based on the location, the method further includes: In the demand comparison view, the clear control is displayed in an operable state; In response to a trigger operation on the clear control, the selection operation is cleared, and the clear control is switched from the operable state to the inoperable state.

8. The method as described in claim 1, characterized in that, The method further includes: When the synchronization control is used to replace different requirement use cases in the first requirement service and the second requirement service, the synchronization instruction is received based on the target requirement use case in response to the triggering operation of the synchronization control. In response to the synchronization command, the original target requirement use case that was replaced in the second requirement service is automatically replaced with the target requirement use case in the first requirement service; The original target requirement use case and the target requirement use case differ in content but are used to achieve the same function.

9. The method as described in claim 1, characterized in that, The method further includes: When the synchronization control is used to insert different demand use cases in the first demand service and the second demand service, based on the target demand use case, in response to the first trigger operation for the synchronization control, a position selection prompt message is displayed to prompt the selection of the insertion position in the second demand service; Based on the location selection prompt information, in response to the selection operation for the target original requirement use case in the at least one second requirement use case, the location of the target original requirement use case is determined; In response to a second triggering operation on the synchronization control, the synchronization instruction is received; In response to the synchronization instruction, the next position in the second demand service that is adjacent to the position of the target original demand use case is determined as the target insertion position, and the target demand use case in the first demand service is inserted into the target insertion position in the second demand service.

10. The method as described in claim 1, characterized in that, The method further includes: When the synchronization control is used to insert different demand use cases in the first demand service and the second demand service, based on the target demand use case, in response to a third trigger operation on the synchronization control, location recommendation information for recommending the insertion position in the second demand service is displayed, and the location recommendation information includes the recommended target insertion position. In response to the operation of determining the location recommendation information, the synchronization instruction is received; In response to the synchronization instruction, the target requirement use case in the first requirement service is inserted into the target insertion position in the second requirement service.

11. The method as described in claim 1, characterized in that, The method further includes: In response to the selection operation for the target original requirement use case in the at least one second requirement use case, the target original requirement use case is used as the requirement use case to be replaced. When the synchronization control is used to replace different requirement use cases in the first requirement service and the second requirement service, the synchronization instruction is received based on the target original requirement use case in response to the trigger operation of the synchronization control; In response to the synchronization command, a target requirement use case corresponding to the target original requirement use case is automatically selected from the first requirement service, and the target original requirement use case in the second requirement service is replaced with the target requirement use case in the first requirement service.

12. The method as described in claim 1, characterized in that, The method further includes: In response to a synchronization command triggered by the synchronization control, it is determined that the target requirement use case in the first requirement service is about to be synchronized to the requirement use case to be synchronized at the corresponding synchronization position in the second requirement service; Obtain the association between the target requirement use case and the requirement use case to be synchronized; When the association relationship indicates that the target requirement use case and the requirement use case to be synchronized meet the synchronization association rule, the target requirement use case in the first requirement service is synchronized to the synchronization position in the second requirement service.

13. The method as described in claim 1, characterized in that, After synchronizing the target demand use case in the first demand service to the synchronization position in the second demand service, the method further includes: A save control is displayed in the requirements comparison view; In response to a trigger operation on the save control, the target requirement use case synchronized to the second requirement service is saved to the use case library of the second requirement service; The requirement use cases stored in the use case library are used to display when comparing the requirement use cases of the second requirement service.

14. The method as described in claim 13, characterized in that, Before synchronizing the target demand use case in the first demand service to the synchronization position in the second demand service, the method further includes: In the demand comparison view, the undo control is displayed using a third display style, which indicates that the undo control is in an inoperable state. Before saving the target requirement use case synchronized to the second requirement service to the use case library of the second requirement service, the method further includes: The undo control is displayed using a fourth display style, which indicates that the undo control is in an operable state. In response to a trigger operation on the undo control which is in an operable state, the synchronized target requirement use case is undone from the second requirement service, and the undo control is controlled to revert from the fourth display style to the third display style.

15. A synchronization device for demand use cases, characterized in that, The device includes: The display module is used to display at least one first requirement use case corresponding to the first requirement service in the first area of ​​the requirement comparison view, and at least one second requirement use case corresponding to the second requirement service in the second area, as well as a synchronization control. The first requirement service and the second requirement service are used to implement the target function; the synchronization control is used to synchronize different requirement use cases in the first requirement service and the second requirement service. A synchronization module is configured to: respond to a selection operation for a target demand use case among the at least one first demand use case, and designate the target demand use case as a demand use case to be synchronized; when the synchronization control is used to insert different demand use cases in the first demand service and the second demand service, filter out insertable original demand use cases from the at least one second demand use case; in the second area, display at least one insertable original demand use case among the second demand use cases using a first display style, and display non-insertable original demand use cases among the second demand use cases using a second display style; wherein, the first display style indicates that the corresponding original demand use case is in an operable state, and the second display style indicates that the corresponding original demand use case is in an inoperable state; respond to a selection operation for a target original demand use case among the at least one insertable original demand use case, obtain the location of the target original demand use case, and determine a synchronization position based on the location; respond to a synchronization instruction triggered based on the target demand use case and the synchronization control, synchronize the target demand use case in the first demand service to the synchronization position in the second demand service.

16. The apparatus according to claim 15, characterized in that, The display module is also used to display a synchronization start control in the demand comparison view; In response to the trigger operation of the synchronization start control, the demand comparison mode is adjusted to the demand synchronization mode; In the demand synchronization mode, in the first area of ​​the demand comparison view, at least one operable first demand use case corresponding to the first demand service is displayed, and in the second area, at least one operable second demand use case corresponding to the second demand service is displayed.

17. The apparatus according to claim 15, characterized in that, The synchronization module is further configured to receive the synchronization instruction in response to a trigger operation on the synchronization control, based on the target requirement use case. In response to the synchronization instruction, the target demand use case in the first demand service is synchronized to the synchronization position in the second demand service.

18. An electronic device, characterized in that, include: Memory, used to store executable instructions; A processor, when executing executable instructions stored in the memory, implements the synchronization method of the required use case as described in any one of claims 1 to 14.

19. A computer-readable storage medium, characterized in that, It stores executable instructions for implementing the synchronization method of the required use case as described in any one of claims 1 to 14 when executed by a processor.

20. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by the processor, they implement the synchronization method of the use case of the requirement as described in any one of claims 1 to 14.

Images