Data processing method and device, storage medium and electronic equipment

Abstract

The invention discloses a data processing method and device, a storage medium and electronic equipment. The method can be used for object storage and acquisition, and comprises the steps that a use case event set corresponding to a target system use case is acquired, the use case event set comprises a use case step event and an execution result event, the use case step event indicates an operation event executed by a target object, and the execution result event indicates the operation event executed by the target object; the execution result event indicates a result event fed back by the target system based on the use case step event; target applications corresponding to the target system cases are sent to a plurality of terminals; obtaining operation data generated by operation of the target application in a plurality of terminals, and determining event execution times corresponding to each use case event in the use case event set; and determining an event conversion rate corresponding to each use case event in the target system use case according to the event execution times corresponding to each use case event. The technical problem that an existing conversion rate obtaining method is low in accuracy is solved.

Description

Technical Field

[0001] The present invention relates to the field of computers, and in particular to a data processing method and device, a storage medium and an electronic device. Background Art

[0002] Conversion rate is an important indicator of software systems, which directly reflects the rationality of software system design and determines whether the software system can make profits. Conversion rate analysis generally involves first confirming a certain operation path of the product and then analyzing the conversion of each link on the path.

[0003] In the process of evaluating the conversion rate of the software system based on the product's operation path, since the software system's operation path usually only includes the various control operations performed by the user on the client, the software system's operation path can usually only reflect the conversion rate of the user's operation. However, as the software system development process becomes increasingly complex, the conversion process between the various control operations in the software system has also become more complex. The system conversion rate determined based on the user's control operation can no longer accurately reflect the conversion status of each link in the entire software system. In other words, the existing conversion rate acquisition method has a technical problem of low accuracy.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present invention provide a data processing method and device, a storage medium and an electronic device, so as to at least solve the technical problem of low accuracy of the existing conversion rate acquisition method.

[0006] According to one aspect of an embodiment of the present invention, a data processing method is provided, comprising: obtaining a use case event set corresponding to a target system use case, wherein the use case event set includes a use case step event and an execution result event, the use case step event indicates an operation event performed by a target object, the execution result event indicates a result event fed back by a target system based on the use case step event, and the target object and the target system perform interactive operations based on the target system use case; sending a target application corresponding to the target system use case to multiple terminals respectively, wherein the target system use case is used to indicate the interactive logic of a target interactive function in the target application; obtaining operation data generated by the target application running in the multiple terminals, and determining the event execution times corresponding to each use case event in the use case event set, wherein the use case event includes the use case step event and the execution result event; determining the event conversion rate corresponding to each use case event in the target system use case according to the event execution times corresponding to each use case event, wherein the event conversion rate indicates the execution probability of the use case event based on the previous use case event.

[0007] According to another aspect of an embodiment of the present invention, a data processing device is further provided, comprising: an acquisition unit, configured to acquire a use case event set corresponding to a target system use case, wherein the use case event set includes a use case step event and an execution result event, wherein the use case step event indicates an operation event performed by a target object, and the execution result event indicates a result event fed back by a target system based on the use case step event, and the target object and the target system perform an interactive operation based on the target system use case; a sending unit, configured to send a target application corresponding to the target system use case to a plurality of terminals respectively, wherein the target system use case is used to indicate an interactive logic of a target interactive function in the target application; a first determination unit, configured to acquire operation data generated by the target application corresponding to the target system use case running in a plurality of terminals, and determine the event execution times corresponding to each of the use case events in the use case event set, wherein the use case event includes the use case step event and the execution result event; a second determination unit, configured to determine an event conversion rate corresponding to each of the use case events in the target system use case according to the event execution times corresponding to each of the use case events, wherein the event conversion rate indicates an execution probability of the use case event based on a previous use case event.

[0008] Optionally, the second determination unit comprises: an acquisition module for acquiring a first number of executions corresponding to each of the use case step events and a second number of executions corresponding to each of the execution result events; a determination module for determining a step conversion rate of each of the use case step events and a result conversion rate of each of the execution result events in the use case of the target system based on the first number of executions and the second number of executions, wherein the step conversion rate indicates the probability that the target object executes the use case step event based on the previous execution result event, and the result conversion rate indicates the probability that the target system executes the execution result event based on the previous use case step event.

[0009] Optionally, the above-mentioned determination module included in the above-mentioned second determination unit is used to: obtain one use case event in the above-mentioned use case event set as the current use case event in turn, execute the following steps, and traverse the above-mentioned use case event set: when the above-mentioned current use case event is the above-mentioned use case step event, obtain the above-mentioned first execution number corresponding to the above-mentioned use case step event, and obtain the above-mentioned second execution number corresponding to the above-mentioned execution result event executed before the above-mentioned use case step event, and determine the ratio between the above-mentioned first execution number and the above-mentioned second execution number as the above-mentioned step conversion rate of the above-mentioned use case step event; when the above-mentioned current use case event is the above-mentioned execution result event, obtain the above-mentioned second execution number corresponding to the above-mentioned execution result event, and obtain the above-mentioned first execution number corresponding to the above-mentioned use case step event executed before the above-mentioned execution result event, and determine the ratio between the above-mentioned second execution number and the above-mentioned first execution number as the above-mentioned result conversion rate of the above-mentioned execution result event.

[0010] Optionally, the above-mentioned determination module included in the above-mentioned second determination unit is used to: obtain an event execution path determined according to the above-mentioned use case event set, wherein the above-mentioned event execution path includes multiple event nodes corresponding to the above-mentioned multiple use case events, and the above-mentioned event nodes include step event nodes and result event nodes; respectively match the above-mentioned first execution times corresponding to the above-mentioned step event nodes in the above-mentioned event execution path, and respectively match the above-mentioned second execution times corresponding to the above-mentioned result event nodes in the above-mentioned event execution path; determine the step conversion rate of each of the above-mentioned use case step events and the result conversion rate of each of the above-mentioned execution result events in the above-mentioned target system use case based on the above-mentioned event execution path.

[0011] Optionally, the above-mentioned determination module included in the above-mentioned second determination unit is also used to: obtain the first use case step event in the above-mentioned use case event set as the current use case step event, and create a corresponding current step event node for the above-mentioned current use case step event, wherein the above-mentioned first use case step event is the first operation event performed by the above-mentioned target object indicated by the above-mentioned target system use case; repeat the following steps until each of the above-mentioned use case events in the above-mentioned use case event set is traversed: in the case of obtaining at least one target execution result event whose predecessor use case event is the above-mentioned current use case step event from the above-mentioned use case event set, and creating at least one target result event node corresponding to the above-mentioned at least one target execution result event after the above-mentioned current step event node; in the case of obtaining at least one target use case step event whose predecessor use case event is the above-mentioned target execution result event from the above-mentioned use case event set, use the above-mentioned at least one target use case step event as the updated above-mentioned current use case step event, and create at least one current step event node corresponding to at least one current use case step event after the above-mentioned at least one target result event node.

[0012] Optionally, the acquisition unit includes: an acquisition module for acquiring the use case identifier of the target system use case; a determination module for determining the event information of each of the use case events in the use case event set according to the interaction operation between the target object and the target system indicated by the target system use case, wherein the event information includes the use case identifier.

[0013] Optionally, the above-mentioned determination module included in the above-mentioned acquisition unit is used to: determine the target event identifier and the reference event identifier of each of the above-mentioned use case events according to the execution sequence of each of the above-mentioned use case events in the above-mentioned use case event set, wherein the above-mentioned target event identifier is used to indicate the execution order of the above-mentioned use case events in the above-mentioned use case event set, and the above-mentioned reference event identifier is used to indicate the predecessor use case event of the above-mentioned use case event; determine the event information of each of the above-mentioned use case events in the above-mentioned use case event set according to the above-mentioned use case identifier, the above-mentioned target event identifier and the above-mentioned reference event identifier.

[0014] Optionally, the first determination unit is used to: obtain the operation data generated by the target application running in multiple terminals, wherein the operation data includes event records of the operation events performed by the target object during the operation of the target application, and event records of the result events fed back by the target system to the target object, and the event records include a use case identifier and an event identifier; based on the use case identifier and the event identifier included in the event records, count the number of event executions corresponding to each of the use case events.

[0015] Optionally, the above-mentioned data processing device is also used to: obtain an event execution path determined according to the above-mentioned use case event set, wherein the above-mentioned event execution path includes multiple event nodes corresponding to the above-mentioned multiple use case events, and the above-mentioned event nodes include step event nodes and result event nodes; mark the corresponding event conversion rate on each of the above-mentioned event nodes in the above-mentioned event execution path; and determine the marked event execution path as the use case execution conversion diagram corresponding to the above-mentioned target system use case.

[0016] Optionally, the above-mentioned data processing device is also used to: when the target conversion rate corresponding to the target use case event in the above-mentioned use case event set is lower than the conversion rate threshold, adjust the application function associated with the above-mentioned target use case event in the above-mentioned target application.

[0017] Optionally, the above-mentioned data processing device is also used for: when the above-mentioned target use case event is the above-mentioned use case step event, adjusting the target application function in the above-mentioned target application for triggering the above-mentioned target use case event, wherein the above-mentioned target application function corresponds to the above-mentioned execution result event for triggering the above-mentioned target use case event; when the above-mentioned target use case event is the above-mentioned execution result event, adjusting the triggering condition of the target application function corresponding to the above-mentioned target use case event in the above-mentioned target application.

[0018] According to another aspect of the embodiments of the present invention, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the above data processing method when running.

[0019] According to another aspect of the embodiments of the present application, a computer program product is provided, the computer program product comprising a computer program / instruction, the computer instruction being stored in a computer-readable storage medium. A processor of a computer device reads the computer program / instruction from the computer-readable storage medium, and the processor executes the computer program / instruction, so that the computer device executes the above data processing method.

[0020] According to another aspect of an embodiment of the present invention, there is provided an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the data processing method through the computer program.

[0021] In an embodiment of the present invention, a use case event set corresponding to a target system use case is obtained, wherein the use case event set includes a use case step event and an execution result event, the use case step event indicates an operation event performed by a target object, the execution result event indicates a result event fed back by the target system based on the use case step event, and the target object and the target system perform interactive operations based on the target system use case; the target application corresponding to the target system use case is sent to multiple terminals respectively, wherein the target system use case is used to indicate the interactive logic of the target interactive function in the target application; the operation data generated by the target application running in multiple terminals is obtained, and the event execution times corresponding to each use case event in the use case event set are determined, wherein the use case event includes a use case step event and an execution result event; according to the event execution times corresponding to each use case event, the event conversion rate corresponding to each use case event in the target system use case is determined, thereby determining the conversion rates corresponding to multiple event links in the software system according to the target system use case of the software system.

[0022] In the above implementation of the present application, a use case event set including use case step events and execution result events is first obtained, and the number of event executions corresponding to each use case event in the use case event set is determined based on the operation data generated by the operation in multiple terminals. Since the step use case event reflects the operation performed by the target object, and the execution result event reflects the result event fed back by the target system based on the operation of the object, the event execution status on both the object side and the system side can be accurately determined through the number of event executions corresponding to each of the above use case events. Finally, the conversion rate corresponding to each event is determined through the number of event executions corresponding to each use case event. Since each event includes both the use case step event indicating the user operation and the execution result event indicating the system feedback, the conversion rate of each event in the software system can be accurately determined based on the above data, and the overall conversion status of the target system use case of the software system can be accurately evaluated, solving the technical problem of low accuracy of the existing conversion rate acquisition method and improving the accuracy of the acquired software system conversion rate. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0024] Figure 1 is a schematic diagram of a hardware environment of an optional data processing method according to an embodiment of the present invention;

[0025] Figure 2 is a flow chart of an optional data processing method according to an embodiment of the present invention;

[0026] Figure 3 is a schematic diagram of an optional data processing method according to an embodiment of the present invention;

[0027] Figure 4 is a schematic diagram of another optional data processing method according to an embodiment of the present invention;

[0028] Figure 5 is a schematic diagram of another optional data processing method according to an embodiment of the present invention;

[0029] Figure 6 is a schematic diagram of another optional data processing method according to an embodiment of the present invention;

[0030] Figure 7 is a schematic structural diagram of an optional data processing device according to an embodiment of the present invention;

[0031] Figure 8It is a schematic diagram of the structure of an optional electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0032] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0033] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0034] The following is an explanation of the technical terms used in this application:

[0035] System use case: System use case is a contract reached by various stakeholders of the system on the behavior of the system. System use case describes the system behavior that occurs when the system responds to a stakeholder's request under different conditions. The stakeholder who makes the request is called the "primary executor". The primary executor achieves a certain goal by initiating one or more interactions with the system. The system's response to any executor must ensure that the interests of all stakeholders are not violated.

[0036] System use case steps: System use case steps are an interaction between the main executor and the system. When a system use case has multiple steps, in order to achieve the ultimate goal of the system use case and ensure the interests of all stakeholders, the steps of the system use case may produce different results. The main executor then performs the next interaction based on the results. These different results and steps together constitute different paths of the system use case. The main success path is called the basic path, and other paths are called extended paths.

[0037] Conversion rate: Conversion rate refers to the ratio of the number of completed conversions to the number of initiated actions within a statistical period. In the conversion rate statistics of software systems, the conversion rate often refers to the proportion of each link relative to the previous link on a certain user operation path.

[0038] According to one aspect of an embodiment of the present invention, a data processing method is provided. As an optional implementation, the data processing method can be applied to, but is not limited to, Figure 1 The data processing system in the hardware environment shown in FIG. 1 includes, but is not limited to, a terminal device 102, a network 104, a server 106, a database 108, and a terminal device 110. The terminal device 102 runs a target client (such as Figure 1 As shown, the target client is a client that can count the time records of each use case event in the target system use case as an example). The above-mentioned terminal device 102 includes a human-computer interaction screen, a processor and a memory. The human-computer interaction screen is used to display the data processing operation interface, and is also used to provide a human-computer interaction interface to receive control operations for user execution. The processor is used to generate an interaction instruction in response to the above-mentioned human-computer interaction operation, and send the data operation request corresponding to the interaction instruction to the server corresponding to the client. The memory is used to store event records of the counted use case events. In this embodiment, there can be multiple terminal devices 102 above, so as to realize the recording of multiple use case events in the target system use case through the target application running in multiple terminal devices 102; another client can be running in the above-mentioned terminal device 110, and the client can initiate a conversion rate acquisition request for the target system use case to the server 106 to obtain the analysis result of the conversion rate of the target system use case from the server 106.

[0039] In addition, the server 106 includes a processing engine, which is used to perform storage or reading operations on the database 108. Specifically, the processing engine reads the event records returned by each terminal from the database 108.

[0040] Assumptions Figure 1 A first client is run in the terminal device 102, and the first client can be used to run a target application matching the target system use case. The specific process of this embodiment is as follows: the server 106 executes steps S102 and S104, and the server 106 obtains a use case event set corresponding to the target system use case, wherein the use case event set includes a use case step event and an execution result event, the use case step event indicates an operation event performed by the target object, and the execution result event indicates a result event fed back by the target system based on the use case step event, and the target object and the target system perform an interactive operation based on the target system use case; then, the target application is sent to the terminal device 102 through the network 104, wherein the target system use case is used to indicate the interactive logic of the target interactive function in the target application;

[0041] Next, as in step S106, the terminal device 102 generates an event record based on the interaction result between the client and the server, and sends the event record to the server 106 via the network 104;

[0042] Then, as in step S110 to step S112, the server 106 determines the event execution times corresponding to each use case event in the use case event set based on the operation data generated by the target application corresponding to the target system use case running in multiple terminals, wherein the use case events include use case step events and execution result events; and determines the event conversion rate corresponding to each use case event in the target system use case according to the event execution times corresponding to each use case event, wherein the event conversion rate indicates the execution probability of the use case event based on the previous use case event.

[0043] Finally, as in step S114, the server 106 network 104 sends the conversion rate analysis result corresponding to the target system use case to the terminal device 110. It can be understood that in this embodiment, a client for analyzing the conversion rate is running in the terminal device 110, and the client can initiate a conversion rate analysis request to the server 106, so that the server 106 responds to the conversion rate analysis request and performs conversion rate analysis based on the event records returned by each terminal.

[0044] Optionally, in this embodiment, the terminal device 102 may be a terminal device configured with a target client, which may include but is not limited to at least one of the following: a mobile phone (such as an Android phone, an iOS phone, etc.), a laptop, a tablet computer, a PDA, a MID (Mobile Internet Devices), a PAD, a desktop computer, a smart TV, etc. The target client may be a client that supports providing shooting game tasks, such as a video client, an instant messaging client, a browser client, an educational client, etc. The network may include but is not limited to: a wired network, a wireless network, wherein the wired network includes: a local area network, a metropolitan area network, and a wide area network, and the wireless network includes: Bluetooth, WIFI, and other networks that implement wireless communication. The server may be a single server, or a server cluster consisting of multiple servers, or a cloud server. The above is only an example, and this embodiment does not make any limitation to this.

[0045] The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal can be a smart phone, tablet computer, laptop computer, desktop computer, smart speaker, smart watch, etc., but is not limited to this. The terminal and the server can be directly or indirectly connected via wired or wireless communication, which is not limited in this application.

[0046] In an embodiment of the present invention, a data processing request is received, wherein the data processing request is used to obtain target node data corresponding to a target node set, and the target node set is a node set stored in a target distributed server; in the case that the target node data is not obtained from a reference node set stored locally, an operation type of a data processing operation performed on at least one node subset in the target node set is determined based on request description information carried in the data processing request, wherein the reference node set is a node set constructed based on a data set pre-returned by the target distributed server; based on the operation type of the data processing operation, a data operation request corresponding to at least one node subset is added to a request queue, wherein the request queue is used to asynchronously send the data operation request to the target distributed server; and the target node data returned by the target distributed server based on the data operation request is sent, thereby achieving the acquisition of the data in the target distributed server.

[0047] In an embodiment of the present invention, a use case event set corresponding to a target system use case is obtained, wherein the use case event set includes a use case step event and an execution result event, the use case step event indicates an operation event performed by a target object, the execution result event indicates a result event fed back by the target system based on the use case step event, and the target object and the target system perform interactive operations based on the target system use case; a target application corresponding to the target system use case is sent to a plurality of terminals respectively, wherein the target system use case is used to indicate the interactive logic of a target interactive function in the target application; based on the operation data generated by the target application corresponding to the target system use case running in a plurality of terminals, the event execution times corresponding to each use case event in the use case event set are determined, wherein the use case event includes a use case step event and an execution result event; according to the event execution times corresponding to each use case event, the event conversion rate corresponding to each use case event in the target system use case is determined, thereby determining the conversion rates corresponding to a plurality of event links in the software system according to the target system use case of the software system.

[0048] In the above implementation of the present application, a use case event set including use case step events and execution result events is first obtained, and the number of event executions corresponding to each use case event in the use case event set is determined based on the operation data generated by the operation in multiple terminals. Since the step use case event reflects the operation performed by the target object, and the execution result event reflects the result event fed back by the target system based on the operation of the object, the event execution status on both the object side and the system side can be accurately determined through the number of event executions corresponding to each of the above use case events. Finally, the conversion rate corresponding to each event is determined through the number of event executions corresponding to each use case event. Since each event includes both the use case step event indicating the user operation and the execution result event indicating the system feedback, the conversion rate of each event in the software system can be accurately determined based on the above data, and the overall conversion status of the target system use case of the software system can be accurately evaluated, solving the technical problem of low accuracy of the existing conversion rate acquisition method and improving the accuracy of the acquired software system conversion rate.

[0049] As an optional implementation, Figure 2 As shown, the above data processing method includes the following steps:

[0050] S202, obtaining a use case event set corresponding to a target system use case, wherein the use case event set includes a use case step event and an execution result event, the use case step event indicates an operation event performed by a target object, the execution result event indicates a result event fed back by the target system based on the use case step event, and the target object and the target system perform interactive operations based on the target system use case;

[0051] S204, sending the target application corresponding to the target system use case to multiple terminals respectively, wherein the target system use case is used to indicate the interaction logic of the target interaction function in the target application;

[0052] S206, obtaining operation data generated by the target application running in multiple terminals, and determining the event execution times corresponding to each use case event in the use case event set, wherein the use case event includes a use case step event and an execution result event;

[0053] S208, determining the event conversion rate corresponding to each use case event in the target system use case according to the event execution times corresponding to each use case event, wherein the event conversion rate indicates the execution probability of the use case event based on the previous use case event.

[0054] It should be noted that the system use case in the above step S202 is a contract reached by various objects in the software system on the system behavior. The system use case describes the system behavior that occurs when the system responds to a request from an object under different conditions. The object that makes the request is called the "primary executor". The primary executor achieves a certain goal by initiating one or more interactions with the system.

[0055] In a specific implementation, the above system use case may correspond to the implementation logic of a certain software function in the software system. It is understandable that the implementation of a certain software function in the software requires a certain way of interaction between the object (such as the object account logged in in the client) and the system (such as the server).

[0056] Correspondingly, the use case event set included in the above-mentioned use case event set may be a plurality of interactive operation events between the above-mentioned object (e.g., the object account logged in in the client) and the system (e.g., the server). It should be noted that the above-mentioned object may include but is not limited to the object account, the above-mentioned system may include but is not limited to the system server corresponding to the target application, and may also be the client. In other words, the interactive operation performed by the above-mentioned system is not limited to the response operation returned by the system server, but may also be feedback operations such as display operations and judgment operations performed by the client in response to user operations. In this embodiment, the types of the above-mentioned objects and the types of the above-mentioned systems are not limited.

[0057] For example, for the implementation of the payment function of application A, the corresponding system use case stipulates the following interactive operations: the object account triggers the payment function, the system prompts the user to enter the payment key, the object account performs the payment key input operation, and the system feedbacks the payment success. In this regard, the use case event set of the system use case corresponding to the payment function can include the above events.

[0058] In this embodiment, the above-mentioned use case event set includes two types of events, one of which is the use case step event, which indicates the operation event performed by the target object; the other is the execution result event, which indicates the result event fed back by the target system based on the use case step event.

[0059] For the events "the object account triggers the payment function", "the system prompts the user to enter the payment key", "the object account executes the payment key input operation" and "the system feedback on payment success" that appear in the above examples, it can be determined that the use case step events include "the object account triggers the payment function" and "the object account executes the payment key input operation"; and the execution result events can include "the system prompts the user to enter the payment key" and "the system feedback on payment success".

[0060] Furthermore, in the above steps S204 and S206, the operation data generated by the target application corresponding to the target system use case running in multiple terminals can be obtained, and the number of event executions corresponding to each use case event can be determined based on the operation data. It should be noted that the data in the above operation data may include but is not limited to event records generated during the operation of the above target application in multiple terminals, and the above event records include the number of executions of each use case event. It can be understood that by counting the event records recorded in each of the multiple terminals within the target statistical period, the total number of executions of each use case event corresponding to the target statistical period can be determined.

[0061] In the above step S208, the event conversion rate corresponding to each use case event in the target system use case may be determined according to the number of event executions corresponding to each use case event.

[0062] In the above implementation of the present application, a use case event set including use case step events and execution result events is first obtained, and the number of event executions corresponding to each use case event in the use case event set is determined based on the operation data generated by the operation in multiple terminals. Since the step use case event reflects the operation performed by the target object, and the execution result event reflects the result event fed back by the target system based on the operation of the object, the event execution status on both the object side and the system side can be accurately determined through the number of event executions corresponding to each of the above use case events. Finally, the conversion rate corresponding to each event is determined through the number of event executions corresponding to each use case event. Since each event includes both the use case step event indicating the user operation and the execution result event indicating the system feedback, the conversion rate of each event in the software system can be accurately determined based on the above data, and the overall conversion status of the target system use case of the software system can be accurately evaluated, solving the technical problem of low accuracy of the existing conversion rate acquisition method and improving the accuracy of the acquired software system conversion rate.

[0063] In an optional implementation, determining the event conversion rate corresponding to each use case event in the target system use case according to the event execution times corresponding to each use case event includes:

[0064] S1, obtaining the first execution times corresponding to each use case step event and the second execution times corresponding to each execution result event;

[0065] S2. Determine the step conversion rate of each use case step event and the result conversion rate of each execution result event in the target system use case based on the first execution number and the second execution number, wherein the step conversion rate indicates the probability that the target object executes the use case step event based on the previous execution result event, and the result conversion rate indicates the probability that the target system executes the execution result event based on the previous use case step event.

[0066] It can be understood that in this embodiment, the event execution times corresponding to each use case event can be further divided into the first execution times corresponding to each use case step event, and the second execution times corresponding to each execution result event, and the conversion rate of each use case event can be accurately determined based on the above first execution times and second execution times.

[0067] In this embodiment, the above step conversion rate is used to indicate the probability that the target object executes the use case step event based on the previous execution result event.

[0068] In an optional implementation, determining the step conversion rate of each use case step event and the result conversion rate of each execution result event in the target system use case according to the first execution number and the second execution number includes:

[0069] Get one use case event in the use case event collection in turn as the current use case event, and execute the following steps to traverse the use case event collection:

[0070] S1, when the current use case event is a use case step event, obtain a first execution count corresponding to the use case step event, and obtain a second execution count corresponding to an execution result event executed before the use case step event, and determine the ratio between the first execution count and the second execution count as the step conversion rate of the use case step event;

[0071] S2, when the current use case event is an execution result event, obtain the second execution number corresponding to the execution result event, and obtain the first execution number corresponding to the use case step event executed before the execution result event, and determine the ratio between the second execution number and the first execution number as the result conversion rate of the execution result event.

[0072] For example, for the use case step event "the object account performs the input operation of the payment key" in the target system use case, the corresponding previous use case event is the execution result event "the system prompts the user to enter the payment key", and it is determined that the first execution number of the use case step event "the object account performs the input operation of the payment key" in the target statistical period is 90, and the second execution number of the execution result event "the system prompts the user to enter the payment key" in the target statistical period is 100, and then the step conversion rate corresponding to the use case step event is determined to be 90 / 100, that is, 90%; indicating that the probability of 90% of user accounts continuing to execute the step "the object account performs the input operation of the payment key" after receiving the execution result event "the system prompts the user to enter the payment key" is 90%;

[0073] For another example, for the execution result event "system feedback payment success" in the target system use case, its corresponding previous use case event is the use case step event "the object account executes the payment key input operation", and it is determined that the second execution number of the execution result event "system feedback payment success" corresponding to the target statistical period is 81, and the first execution number of the use case step event "the object account executes the payment key input operation" within the target statistical period is 90, and then the result conversion rate corresponding to the execution result event "system feedback payment success" is determined to be 81 / 90, that is, 90%; in the case of 90%, the system responds to the user account after the user account executes the step "the object account executes the payment key input operation", and feedbacks the execution result event "system feedback payment success" to the user account.

[0074] For another example, for the execution result event "system prompts for face verification" in the target system use case, its corresponding previous use case event is the use case step event "the object account performs the input operation of the payment key"; and it is determined that the second execution number of the execution result event "system prompts for face verification" within the target statistical period is 9, and the first execution number of the use case step event "the object account performs the input operation of the payment key" within the target statistical period is 90, and then the result conversion rate corresponding to the execution result event "system feedback payment success" is determined to be 9 / 90, that is, 10%; in the case of indicating 10% (for example, when the system detects that the current payment environment is less secure), the system responds to the user account after the user account executes the step "the object account performs the input operation of the payment key", and feedbacks the execution result event "system prompts for face verification" to the user account.

[0075] Through the above-mentioned implementation mode of the present application, the first execution number corresponding to each use case step event and the second execution number corresponding to each execution result event are obtained; based on the first execution number and the second execution number, the step conversion rate of each use case step event and the result conversion rate of each execution result event in the target system use case are determined, so that according to the execution number corresponding to each use case step event and the execution result event, the step conversion rate determined based on the user selection and the result conversion rate determined based on the system decision are accurately determined, thereby improving the accuracy of the software system conversion rate.

[0076] In an optional implementation, determining the step conversion rate of each use case step event and the result conversion rate of each execution result event in the target system use case according to the first execution number and the second execution number includes:

[0077] S1, obtaining an event execution path determined according to a use case event set, wherein the event execution path includes a plurality of event nodes corresponding to a plurality of use case events, and the event nodes include step event nodes and result event nodes;

[0078] S2, respectively matching the first execution times corresponding to the step event of the use case and the second execution times corresponding to the execution result event for the step event nodes in the event execution path, and respectively matching the second execution times corresponding to the result event nodes in the event execution path;

[0079] S3, determining the step conversion rate of each use case step event and the result conversion rate of each execution result event in the target system use case based on the event execution path.

[0080] It can be understood that in this embodiment, the event execution path can be determined based on the use case event set, and then the step conversion rate of each use case step event and the result conversion rate of each execution result event in the target system use case can be accurately determined based on the event execution path and the first execution times corresponding to each use case step event, and the second execution times corresponding to each execution result event.

[0081] In an optional embodiment, the step event nodes and result event nodes included in the above event execution path can be represented in the same node form; in another optional embodiment, the step event nodes and result event nodes included in the above event execution path can be represented in different node forms.

[0082] For example, in the first embodiment mentioned above, the step event nodes and result event nodes are drawn as different types of nodes connected by arrows in the event execution path; in the second embodiment mentioned above, the step event nodes can be drawn as nodes connected by arrows in the event execution path, and the result event nodes in the event execution path can be represented by arrows connecting two different nodes.

[0083] like Figure 3 As shown, it is a schematic diagram of the first event execution path mentioned above, the step event nodes may include S302, S304, S304-1, S304-2 shown in the form of nodes; the result event nodes may include R1, R2, R3 and R4 shown in the form of arrows between nodes; according to Figure 3 It can be seen that two types of result event nodes can be generated based on the step event node S302, namely, result event node R2 and result event node R3, among which the result event node R3 is an extension node generated based on the step event node S302, and then generates extended paths S302, S304-1, and S304-2; event R2 can further generate a step event node S306.

[0084] like Figure 4 As shown, it is a schematic diagram of the above-mentioned second event execution path, and the step event nodes may include S402, S404, S404-1, S404-2, S406 shown in node form; the result event nodes may include R1, R2, R3 and R4 shown in node form.

[0085] It can be understood that the above event execution path is merely an example, and this implementation does not limit the specific form of the above event execution path.

[0086] In an optional implementation, before obtaining the event execution path determined according to the use case event set, the process further includes:

[0087] S1, obtaining the first use case step event in the use case event set as the current use case step event, and creating a corresponding current step event node for the current use case step event, wherein the first use case step event is the first operation event performed by the target object indicated by the target system use case;

[0088] S2, repeat the following steps until every use case event in the use case event set is traversed:

[0089] S2-1, in the case where the preceding use case event is at least one target execution result event of the current use case step event, from the use case event set, and at least one target result event node corresponding to the at least one target execution result event is created after the current step event node;

[0090] S2-2, when obtaining at least one target use case step event whose predecessor use case event is a target execution result event from the use case event set, use at least one target use case step event as the updated current use case step event, and create at least one current step event node corresponding to at least one current use case step event after at least one target result event node.

[0091] It can be understood that this embodiment provides a method for obtaining the above event execution path based on a use case event set. In this embodiment, after determining the first use case step event (i.e., triggered based on a user operation), the event identifier of the preceding event stored in the event information of each use case event is filtered, and the next event node of the current event is filtered from the use case event set in turn.

[0092] Specifically, the drawing steps are as follows: for each newly drawn execution result in the previous step (when the preceding execution result of the step event node is drawn for the first time, if it is empty, the first step will be read), filter out all steps from the system use case steps by the preceding execution result, and draw them with the step identifier (e.g., draw them in the style of a node); then, for each newly drawn step in the previous step, filter out all execution results of the step from the step execution results by the preceding step, and draw them in the style of the execution result (e.g., draw them in the style of a line with an arrow). Repeat the above steps until all steps and execution results are drawn.

[0093] The following combination Figure 5 A method for determining conversion rate data corresponding to a target system use case based on an event execution path is described.

[0094] like Figure 5 As shown, the total number of executions of the first step, i.e., step S502, is 100;

[0095] Next, after step S502 is executed, only one result R1 is generated, and the quantity is also 100, so the conversion rate of step S502 is 100%;

[0096] exist Figure 5 In the example, the number of executions of step S504 is 80. That is, the user gave up 20 times and did not continue to perform subsequent operations. Therefore, the conversion rate of the result R1 here is 80%, which reflects the conversion rate of user selections.

[0097] The execution of step S504 generates two results, one is result R2 located on the main path, and the other is result R3 located on the extended path. The number of these two results is 60 and 20 respectively, so relative to step S504, the conversion rate of step S504 to result R2 is 60 / 80*100%=75%, and the conversion rate of step S504 to result R3 is 20 / 80*100%=25%. It can be understood that the conversion rate of step events to result events reflects the conversion rate of system decisions, that is, the software system can return different types of result events based on different conditions based on an operation performed by the user;

[0098] After R2, step S506 was executed 30 times, which means that half of the users gave up, so the conversion rate of step S506 relative to R2 is 50%;

[0099] Similarly, with respect to result R3, half of the users also gave up, and step S504-1 was only executed 10 times. As a result, the conversion rate from step R3 to step S504-1 was also 50%, reflecting the user's choice;

[0100] Similarly, the number of times step S504-1 generates result R4 is 1, and thus the conversion rate of step S504-1 to result R4 is 10%; the number of times step S504-2 is executed is 1, and the conversion rate of step S504-2 to result R4 is 100%.

[0101] Through the above implementation of the present application, the method of analyzing conversion rate based on the path of the system use case does not need to manually screen the product path, and the conversion rate of all paths of a product function can be seen. In addition, in the context of the current software system design tending to reduce user choices, the method defined in the present invention can simultaneously pay attention to the proportion of several extensions generated by the step and the conversion rate of each subsequent step of the extension, that is, it takes into account the conversion rate of user choices and system decisions at the same time, providing software makers with a clearer data basis for making subsequent decisions.

[0102] In an optional implementation, the above-mentioned obtaining a use case event set corresponding to the target system use case includes:

[0103] S1, obtain the use case identifier of the target system use case;

[0104] S2, determining event information of each use case event in the use case event set according to the interactive operation between the target object indicated by the use case of the target system and the target system, wherein the event information includes a use case identifier.

[0105] Optionally, the above-mentioned determining the event information of each use case event in the use case event set according to the interactive operation between the target object indicated by the use case of the target system and the target system includes:

[0106] S1, according to the execution sequence of each use case event in the use case event set, determine the target event identifier and the reference event identifier of each use case event, wherein the target event identifier is used to indicate the execution sequence of the use case event in the use case event set, and the reference event identifier is used to indicate the preceding use case event of the use case event;

[0107] S2, determining event information of each use case event in the use case event set according to the use case identifier, the target event identifier and the reference event identifier.

[0108] It is understandable that in this embodiment, after the software system is produced, the software operator enters the structure of the system use case, that is, the metadata of the system use case, through the software background operation system. The system use case metadata is divided into three parts: system use case, system use case steps and step execution results.

[0109] The system use case can be recorded through two fields, including the system use case number (first identifier) ​​and the system use case name (second identifier), wherein the system use case name can be named by the application function corresponding to the system use case, such as "payment function" etc.;

[0110] The system use case step metadata can be used to indicate the event information of the above use case step event, and can specifically include the following fields: system use case number (used to indicate the target system use case where the current use case step event is located), step number (i.e. event identifier), step name (i.e. another event identifier), and the number of the previous execution result (i.e. the event identifier of the previous execution result event of the current use case event); optionally, in this embodiment, the above step number can adopt the identification form of "path + sequence number", and the above step name can adopt the system use case step name that is easy to read and understand; it can be understood that the system use case step whose number of the previous execution result is empty can be considered as the first use case step;

[0111] The step execution result metadata can be used to indicate the event information of the above-mentioned execution result event, and may specifically include the following fields: system use case number (used to indicate the target system use case where the current execution result event is located), execution result number (i.e. event identifier), execution result name (i.e. another event identifier), and the number of the preceding step (i.e. the event identifier of the previous use case step event of the current execution result event); optionally, in this embodiment, the above-mentioned execution result name may adopt an execution result name that is easy to read and understand.

[0112] Through the above-mentioned implementation mode of the present application, the use case identification of the target system use case is obtained; according to the interaction operation between the target object indicated by the target system use case and the target system, the event information of each use case event in the use case event set is determined, thereby realizing the entry of system use case metadata, and a system use case execution path diagram corresponding to the system use case can be generated according to the above-mentioned system use case metadata.

[0113] The specific method of generating a system use case execution path diagram corresponding to the system use case can be as follows:

[0114] S1, for each newly drawn execution result in the previous step (if it is empty for the first time, the first step will be read), filter out all steps from the system use case steps according to the previous execution results, and draw them with the symbols of the steps (such as drawing them in the style of nodes);

[0115] S2, for each newly drawn step in the previous step, filter out all execution results of the step from the step execution results according to the previous steps, and draw them in the style of the execution results (such as drawing them in the style of arrow line segments);

[0116] S3, repeat the above steps S1 and S2 until all steps and execution results are drawn.

[0117] In an optional implementation, the operation data generated by the target application corresponding to the target system use case running in multiple terminals includes:

[0118] S1, obtaining operation data generated by the target application running in multiple terminals, wherein the operation data includes event records of operation events performed by the target object during the operation of the target application, and event records of result events fed back by the target system to the target object, and the event records include a use case identifier and an event identifier;

[0119] S2, counting the event execution times corresponding to each use case event according to the use case identifier and event identifier included in the event record.

[0120] It is understandable that during the user's use of the software system, the software system can record each execution result event and use case step event in the format of system use case name, system use case step name and execution result name after the execution of the system use case step is completed, and report them to the system.

[0121] In an optional implementation, after determining the event conversion rate corresponding to each use case event in the target system use case according to the event execution times corresponding to each use case event, the method further includes:

[0122] S1, obtaining an event execution path determined according to a use case event set, wherein the event execution path includes a plurality of event nodes corresponding to a plurality of use case events, and the event nodes include step event nodes and result event nodes;

[0123] S2, mark the corresponding event conversion rate on each event node in the event execution path;

[0124] S3, determining the annotated event execution path as the use case execution transformation diagram corresponding to the target system use case.

[0125] In an optional embodiment, after determining the event conversion rate corresponding to each use case event in the target system use case based on the number of event executions corresponding to each use case event, the method further includes: when the target conversion rate corresponding to the target use case event in the use case event set is lower than the conversion rate threshold, adjusting the application function associated with the target use case event in the target application.

[0126] Optionally, the adjusting of the application function associated with the target use case event in the target application includes:

[0127] Method 1: When the target use case event is a use case step event, the target application function in the target application for triggering the target use case event is adjusted, wherein the target application function corresponds to the execution result event for triggering the target use case event;

[0128] Method 2: When the target use case event is an execution result event, the triggering condition of the target application function corresponding to the target use case event in the target application is adjusted.

[0129] It is understandable that in the above implementation of the present application, the target system use case may correspond to a specific application function in the target application, and the above target use case event may correspond to each interaction step for realizing the function. After determining the conversion rate of each use case event based on the acquired operation data, certain adjustments may be made to the use case events with lower conversion rates.

[0130] Optionally, the conversion rate threshold may be a numerical condition determined according to each event use case.

[0131] In the case where the use case event with a conversion rate lower than the above conversion rate threshold is a use case step event (that is, the event is an interactive event performed by the user), the target application function used to trigger the event can be adjusted accordingly. Taking the above target application as an application that can realize the "payment function" as an example, the above target use case event can be "the object account performs the input operation of the payment key." Assuming that the conversion rate of the event is lower than the conversion rate threshold of 80%, the reasons for the low conversion rate of this step can be further analyzed. For example, the reason may be that the prompt interface of the system prompt function "the system prompts the user to enter the payment key" used to trigger the step is not user-friendly, or the verification code input in the interface is difficult, and then the system prompt function (corresponding to the execution result event executed by the system) is adjusted. For example, the event content of the event can be adjusted, such as reducing the difficulty of entering the verification code;

[0132] In the case where the use case event with a conversion rate lower than the above conversion rate threshold is an execution result event (that is, the event is an interactive event executed by the system), the triggering conditions for triggering the execution result event can be adjusted accordingly. For example, the above execution result event is "the system prompts that password-free payment is currently supported", and the triggering condition of the execution result event can be that the security detection result of the user's current payment environment meets the target result. If the conversion rate of the execution result event is low, the triggering conditions of the event can be further adjusted to reduce the difficulty of triggering the execution result event and improve the user's payment experience.

[0133] The following combination Figure 5 , Figure 6 A complete process of this application is described.

[0134] like Figure 6 As shown, first, the software operator executes step S602 through the client to enter metadata; specifically, after the software system is completed, the software operator enters the structure of the system use case, that is, the metadata of the system use case, through the software background operation system. The system use case metadata is divided into three parts: system use case, system use case steps, and step execution results.

[0135] Then, as in step S604, the system use case execution data is entered; it can be understood that when the user uses the target application corresponding to the current system use case, each execution result event and use case step event can be recorded in the format of system use case name, system use case step name and execution result name, and reported to the system.

[0136] Finally, the software operator executes step S606 through the client to view the system use case conversion view. Specifically, the corresponding system use case conversion view can be drawn based on the acquisition of the system use case metadata and the system use case execution data.

[0137] The specific steps to draw the corresponding system use case transformation view are as follows:

[0138] First, draw the system use case execution path diagram according to the system use case metadata, including the following steps: 1) For each newly drawn execution result in the previous step (if it is empty for the first time, the first step will be read), filter out all the steps from the system use case steps according to the previous execution results, and draw them with the step symbols (such as drawing them in the style of nodes); 2) For each newly drawn step in the previous step, filter out all the execution results of the step from the step execution results according to the previous steps in turn, and draw them in the style of the execution results (such as drawing them in the style of arrow segments); then repeat the above steps: 1)-2) until all the steps and execution results are drawn. The drawn system use case execution path diagram can be shown as follows: Figure 4 As shown;

[0139] Next, fill the conversion rate data on the system use case execution diagram according to the system use case execution data. The methods of filling the steps and execution results are as follows: 1) fill the execution amount of the step and the conversion rate relative to its previous execution result on the step; 2) fill the execution result with the total amount of the execution result and the conversion rate relative to its previous step.

[0140] like Figure 5 The figure below shows a completed system use case transformation view.

[0141] The following is a specific example Figure 5 Let's explain further. Assume Figure 5 Transform the view for the system use case corresponding to the payment functionality.

[0142] Among them, step S502 corresponds to the step "triggering payment function" executed by the object account; step S504 corresponds to the step "entering payment password" executed by the object account; step S506 corresponds to the step "confirming payment" executed by the object account; step S504-1 corresponds to the step "entering verification code" executed by the object account; step S504-2 corresponds to the step "confirming payment" executed by the object account;

[0143] Result R1 corresponds to the software system feedback result "prompt to enter payment password"; Result R2 corresponds to the software system feedback result "prompt to confirm whether to complete payment"; Result R3 corresponds to the software system feedback result "prompt to enter verification code"; Result R4 corresponds to the software system feedback result "prompt to confirm whether to complete payment";

[0144] Furthermore, if Figure 5 In the example, the total number of executions of step S502 is 100, indicating that within the target statistical period, the number of executions of the step “triggering the payment function” executed by the target account in the target application running in multiple terminals is 100;

[0145] Next, after step S502 is executed, only one result R1 is generated, and the quantity is also 100, so the conversion rate of step S502 is 100%; that is, in response to the step "triggering payment function" executed by the target account, the software system fully feedbacks the result "prompt to enter payment password";

[0146] exist Figure 5 In the example, the number of executions of step S504 is 80. That is to say, there were 20 times when the user gave up and did not continue to perform the subsequent operation. Therefore, the conversion rate of the result R1 here is 80%, which reflects the conversion rate of user selection; that is, after the result "prompt to enter the payment password" was fed back to the target account, 80% of the target accounts continued to perform the operation step "enter the payment password";

[0147] The execution of step S504 produces two results, one is the result R2 feedback result located on the main path "prompt whether to confirm the completion of payment", and the other is the result R3 feedback result located on the extended path "prompt to enter the verification code". The number of these two results is 60 and 20 respectively, so relative to step S504, the conversion rate of step S504 to result R2 is 60 / 80*100%=75%, and the conversion rate of step S504 to result R3 is 20 / 80*100%=25%. It can be understood that in the current scenario, the software system detects that 25% of the payment environments have risk factors after testing the payment environment, and then chooses to respond to the result R3 feedback result "prompt to enter the verification code", and for the other 75% of the environments, it is detected as safe, and then responds to the feedback result "prompt whether to confirm the completion of payment";

[0148] After R2, step S506 was executed 30 times, which means that half of the users gave up payment, so the conversion rate of step S506 relative to R2 is 50%;

[0149] Similarly, in result R3, half of the users gave up payment, and step S504-1 was only executed 10 times. As a result, the conversion rate from step R3 to step S504-1 was also 50%, reflecting the user's choice.

[0150] Similarly, the number of times step S504-1 generates result R4 is 1, and thus the conversion rate of step S504-1 to result R4 is 10%; the number of times step S504-2 is executed is 1, and the conversion rate of step S504-2 to result R4 is 100%.

[0151] It should be further explained that the current design of software systems tends to reduce user choices and leave more decisions to the system. Therefore, the interaction path between users and systems is determined by both user choices and system decisions. Therefore, through the above implementation, the conversion rate analysis method based on system use cases can take into account both user choices and system decisions, and improve the accuracy of conversion rate calculation;

[0152] In addition, the system use case defines all the paths, so the conversion rate analysis method based on the system use case can see the conversion rates of all the paths at the same time;

[0153] In addition, in the above implementation, different users will produce different results for the same interaction with the system, which is reflected as extensions in the system use case. That is, a step may produce different extensions, and the extension has a conversion rate relative to the step, and then each subsequent step of the extension has another conversion rate. The conversion rate analysis method based on the system use case can reflect these two conversion rates at the same time. Usually, the proportion of several extensions generated by the step and the conversion rate of the subsequent steps of the extension are both of concern to the software maker. Therefore, through the above implementation, the technical problem of low accuracy of the existing conversion rate acquisition method is solved, and the accuracy of the acquired software system conversion rate is improved.

[0154] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the described action sequence, because according to the present invention, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

[0155] According to another aspect of the embodiments of the present invention, a data processing device for implementing the above data processing method is also provided. Figure 7 As shown, the device comprises:

[0156] The acquisition unit 702 is used to acquire a use case event set corresponding to the target system use case, wherein the use case event set includes a use case step event and an execution result event, the use case step event indicates an operation event performed by the target object, and the execution result event indicates a result event fed back by the target system based on the use case step event, and the target object and the target system perform interactive operations based on the target system use case;

[0157] A sending unit 704 is used to send target applications corresponding to target system use cases to multiple terminals respectively, wherein the target system use cases are used to indicate the interaction logic of the target interaction function in the target application;

[0158] A first determining unit 706 is used to determine the event execution times corresponding to each use case event in the use case event set based on the operation data generated by the target application corresponding to the target system use case running in multiple terminals, wherein the use case event includes a use case step event and an execution result event;

[0159] The second determination unit 708 is used to determine the event conversion rate corresponding to each use case event in the target system use case according to the number of event executions corresponding to each use case event, wherein the event conversion rate indicates the execution probability of the use case event based on the previous use case event.

[0160] Optionally, the second determining unit 708 includes:

[0161] An acquisition module, used to acquire a first execution number corresponding to each of the use case step events, and a second execution number corresponding to each of the execution result events;

[0162] A determination module is used to determine the step conversion rate of each use case step event and the result conversion rate of each execution result event in the target system use case based on the first execution number and the second execution number, wherein the step conversion rate indicates the probability that the target object executes the use case step event based on the previous execution result event, and the result conversion rate indicates the probability that the target system executes the execution result event based on the previous use case step event.

[0163] Optionally, the above-mentioned determination module is also used to: obtain one use case event in the use case event set in turn as the current use case event, execute the following steps, and traverse the use case event set: when the current use case event is a use case step event, obtain the first execution number corresponding to the use case step event, and obtain the second execution number corresponding to the execution result event executed before the use case step event, and determine the ratio between the first execution number and the second execution number as the step conversion rate of the use case step event; when the current use case event is an execution result event, obtain the second execution number corresponding to the execution result event, and obtain the first execution number corresponding to the use case step event executed before the execution result event, and determine the ratio between the second execution number and the first execution number as the result conversion rate of the execution result event.

[0164] Optionally, the above-mentioned determination module is also used to: obtain an event execution path determined according to a use case event set, wherein the event execution path includes multiple event nodes corresponding to multiple use case events, and the event nodes include step event nodes and result event nodes; match the corresponding first execution times for the step event nodes in the event execution path, and match the corresponding second execution times for the result event nodes in the event execution path; determine the step conversion rate of each use case step event and the result conversion rate of each execution result event in the target system use case based on the event execution path.

[0165] Optionally, the above-mentioned determination module is also used to: obtain the first use case step event in the use case event set as the current use case step event, and create a corresponding current step event node for the current use case step event, wherein the first use case step event is the first operation event performed by the target object indicated by the target system use case; repeat the following steps until each use case event in the use case event set is traversed: in the case of obtaining at least one target execution result event whose predecessor use case event is the current use case step event from the use case event set, and creating at least one target result event node corresponding to the at least one target execution result event after the current step event node; in the case of obtaining at least one target use case step event whose predecessor use case event is the target execution result event from the use case event set, use at least one target use case step event as the updated current use case step event, and create at least one current step event node corresponding to at least one current use case step event after the at least one target result event node.

[0166] Optionally, the acquisition unit 702 includes:

[0167] An acquisition module, used to acquire the use case identifier of the target system use case;

[0168] The determination module is used to determine the event information of each use case event in the use case event set according to the interactive operation between the target object indicated by the target system use case and the target system, wherein the event information includes the use case identifier.

[0169] Optionally, the determination module included in the acquisition unit 702 is also used to: determine the target event identifier and the reference event identifier of each use case event according to the execution sequence of each use case event in the use case event set, wherein the target event identifier is used to indicate the execution sequence of the use case event in the use case event set, and the reference event identifier is used to indicate the predecessor use case event of the use case event; determine the event information of each use case event in the use case event set according to the use case identifier, the target event identifier and the reference event identifier.

[0170] Optionally, the first determination unit 706 is also used to: obtain operation data generated by the target application running in multiple terminals, wherein the operation data includes event records of operation events performed by the target object during the operation of the target application, and event records of result events fed back by the target system to the target object, and the event records include use case identifiers and event identifiers; based on the use case identifiers and event identifiers included in the event records, count the number of event executions corresponding to each use case event.

[0171] Optionally, the above-mentioned data processing device is also used to: obtain an event execution path determined according to a use case event set, wherein the event execution path includes multiple event nodes corresponding to multiple use case events, and the event nodes include step event nodes and result event nodes; mark the corresponding event conversion rate on each event node in the event execution path; and determine the marked event execution path as the use case execution conversion diagram corresponding to the target system use case.

[0172] Optionally, the above-mentioned data processing device is also used to: when the target conversion rate corresponding to the target use case event in the above-mentioned use case event set is lower than the conversion rate threshold, adjust the application function associated with the above-mentioned target use case event in the above-mentioned target application.

[0173] Optionally, the above-mentioned data processing device is also used for: when the above-mentioned target use case event is the above-mentioned use case step event, adjusting the target application function in the above-mentioned target application for triggering the above-mentioned target use case event, wherein the above-mentioned target application function corresponds to the above-mentioned execution result event for triggering the above-mentioned target use case event; when the above-mentioned target use case event is the above-mentioned execution result event, adjusting the triggering condition of the target application function corresponding to the above-mentioned target use case event in the above-mentioned target application.

[0174] Optionally, in this embodiment, the embodiments to be implemented by the above-mentioned various unit modules can refer to the above-mentioned various method embodiments, which will not be repeated here.

[0175] According to another aspect of the embodiments of the present invention, there is also provided an electronic device for implementing the above data processing method, which may be Figure 8 The terminal device or server shown in the figure. This embodiment is described by taking the electronic device as a terminal device as an example. Figure 8 As shown, the electronic device includes a memory 802 and a processor 804. The memory 802 stores a computer program. The processor 804 is configured to execute the steps in any of the above method embodiments through the computer program.

[0176] Optionally, in this embodiment, the electronic device may be located in at least one network device among a plurality of network devices of a computer network.

[0177] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0178] S1, obtaining a use case event set corresponding to a target system use case, wherein the use case event set includes a use case step event and an execution result event, the use case step event indicates an operation event performed by a target object, the execution result event indicates a result event fed back by the target system based on the use case step event, and the target object and the target system perform interactive operations based on the target system use case;

[0179] S2, sending the target application corresponding to the target system use case to multiple terminals respectively, wherein the target system use case is used to indicate the interaction logic of the target interaction function in the target application;

[0180] S3, obtaining operation data generated by the target application running in multiple terminals, and determining the event execution times corresponding to each use case event in the use case event set, wherein the use case event includes a use case step event and an execution result event;

[0181] S4, determining the event conversion rate corresponding to each use case event in the target system use case according to the event execution times corresponding to each use case event, wherein the event conversion rate indicates the execution probability of the use case event based on the previous use case event.

[0182] Alternatively, a person skilled in the art may understand that: Figure 8 The structure shown is for illustration only, and the electronic device may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (MID), a PAD, and other terminal devices. Figure 8 The electronic device and the electronic equipment described above are not limited in structure. Figure 8 More or fewer components (such as network interfaces, etc.) as shown in, or with Figure 8 Different configurations are shown.

[0183] Among them, the memory 802 can be used to store software programs and modules, such as program instructions / modules corresponding to the data processing method and device in the embodiments of the present invention. The processor 804 executes various functional applications and data processing by running the software programs and modules stored in the memory 802, that is, realizing the above-mentioned data processing method. The memory 802 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 802 may further include a memory remotely located relative to the processor 804, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. Among them, the memory 802 can be specifically, but not limited to, used to store information such as various elements in the scene screen, data processing information, etc. As an example, such as Figure 8 As shown, the memory 802 may include but is not limited to the acquisition unit 702, the first determination unit 704 and the second determination unit 706 in the data processing device. In addition, other module units in the data processing device may also be included but are not limited to, which will not be repeated in this example.

[0184] Optionally, the transmission device 806 is used to receive or send data via a network. Specific examples of the network may include wired networks and wireless networks. In one example, the transmission device 806 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices and routers via a network cable so as to communicate with the Internet or a local area network. In one example, the transmission device 806 is a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0185] In addition, the electronic device further includes: a display 808 for displaying a virtual scene in an interface; and a connection bus 810 for connecting various module components in the electronic device.

[0186] In other embodiments, the terminal device or server may be a node in a distributed system, wherein the distributed system may be a blockchain system, and the blockchain system may be a distributed system formed by connecting the multiple nodes in the form of network communication. Among them, a peer-to-peer network may be formed between the nodes, and any form of computing device, such as a server, a terminal or other electronic device, may become a node in the blockchain system by joining the peer-to-peer network.

[0187] According to one aspect of the present application, a computer program product is provided, the computer program product comprising a computer program / instruction, the computer program / instruction comprising a program code for executing the method shown in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication part, and / or installed from a removable medium. When the computer program is executed by a central processing unit, various functions provided by the embodiments of the present application are executed.

[0188] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0189] According to one aspect of the present application, a computer-readable storage medium is provided, and a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the above-mentioned data processing method.

[0190] Optionally, in this embodiment, the computer-readable storage medium may be configured to store a computer program for performing the following steps:

[0191] S1, obtaining a use case event set corresponding to a target system use case, wherein the use case event set includes a use case step event and an execution result event, the use case step event indicates an operation event performed by a target object, the execution result event indicates a result event fed back by the target system based on the use case step event, and the target object and the target system perform interactive operations based on the target system use case;

[0192] S2, sending the target application corresponding to the target system use case to multiple terminals respectively, wherein the target system use case is used to indicate the interaction logic of the target interaction function in the target application;

[0193] S3, obtaining operation data generated by the target application running in multiple terminals, and determining the event execution times corresponding to each use case event in the use case event set, wherein the use case event includes a use case step event and an execution result event;

[0194] S4, determining the event conversion rate corresponding to each use case event in the target system use case according to the event execution times corresponding to each use case event, wherein the event conversion rate indicates the execution probability of the use case event based on the previous use case event.

[0195] Optionally, in this embodiment, a person of ordinary skill in the art may understand that all or part of the steps in the various methods of the above embodiments may be completed by instructing hardware related to the terminal device through a program, and the program may be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.

[0196] If the integrated units in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they can be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling one or more computer devices (which can be personal computers, servers or network devices, etc.) to perform all or part of the steps of the above methods of various embodiments of the present invention.

[0197] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0198] In the several embodiments provided in the present application, it should be understood that the disclosed client can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0199] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0200] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0201] The above are only preferred embodiments of the present invention. It should be pointed out that, for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A data processing method, characterized in that: include: Acquire a use case event set corresponding to a target system use case, wherein the use case event set includes a use case step event and an execution result event, the use case step event indicates an operation event performed by a target object, the execution result event indicates a result event fed back by the target system based on the use case step event, and the target object and the target system perform an interactive operation based on the target system use case; Sending a target application corresponding to the target system use case to a plurality of terminals respectively, wherein the target system use case is used to indicate the interaction logic of a target interaction function in the target application; Acquire operation data generated by the target application running in the multiple terminals, and determine the event execution times corresponding to each use case event in the use case event set, wherein the use case event includes the use case step event and the execution result event; According to the event execution times corresponding to each of the use case events, the event conversion rate corresponding to each of the use case events in the target system use case is determined, wherein the event conversion rate indicates the execution probability of the use case event based on the previous use case event.

2. The method according to claim 1, characterized in that Determining the event conversion rate corresponding to each of the use case events in the target system use case according to the event execution times corresponding to each of the use case events includes: Obtaining the first execution times corresponding to the use case step events and the second execution times corresponding to the execution result events; Based on the first execution number and the second execution number, determine the step conversion rate of each use case step event and the result conversion rate of each execution result event in the target system use case, wherein the step conversion rate indicates the probability that the target object executes the use case step event based on the previous execution result event, and the result conversion rate indicates the probability that the target system executes the execution result event based on the previous use case step event.

3. The method according to claim 2, characterized in that Determining the step conversion rate of each of the use case step events and the result conversion rate of each of the execution result events in the target system use case according to the first execution number and the second execution number includes: Obtain one use case event in the use case event set in turn as the current use case event, and execute the following steps to traverse the use case event set: In the case where the current use case event is the use case step event, obtaining the first execution number corresponding to the use case step event, and obtaining the second execution number corresponding to the execution result event executed before the use case step event, and determining the ratio between the first execution number and the second execution number as the step conversion rate of the use case step event; In the case where the current use case event is the execution result event, the second execution number corresponding to the execution result event is obtained, and the first execution number corresponding to the use case step event executed before the execution result event is obtained, and the ratio between the second execution number and the first execution number is determined as the result conversion rate of the execution result event.

4. The method according to claim 2, characterized in that: Determining the step conversion rate of each of the use case step events and the result conversion rate of each of the execution result events in the target system use case according to the first execution number and the second execution number includes: Acquire an event execution path determined according to the use case event set, wherein the event execution path includes a plurality of event nodes corresponding to the plurality of use case events, respectively, and the event nodes include step event nodes and result event nodes; Matching the first execution times corresponding to the step event nodes in the event execution path respectively, and matching the second execution times corresponding to the result event nodes in the event execution path respectively; The step conversion rate of each of the use case step events and the result conversion rate of each of the execution result events in the target system use case are determined based on the event execution path.

5. The method according to claim 4, characterized in that Before obtaining the event execution path determined according to the use case event set, the method further includes: Obtaining the first use case step event in the use case event set as the current use case step event, and creating a corresponding current step event node for the current use case step event, wherein the first use case step event is the first operation event performed by the target object indicated by the target system use case; Repeat the following steps until each of the use case events in the use case event set is traversed: In the case where the preceding use case event is obtained from the use case event set as at least one target execution result event of the current use case step event, and at least one target result event node corresponding to the at least one target execution result event is created after the current step event node; In the case of obtaining at least one target use case step event whose predecessor use case event is the target execution result event from the use case event set, the at least one target use case step event is used as the updated current use case step event, and at least one current step event node corresponding to the at least one current use case step event is created after the at least one target result event node.

6. The method according to claim 1, characterized in that The obtaining of a use case event set corresponding to a target system use case includes: Obtaining a use case identifier of the target system use case; According to the interactive operation between the target object indicated by the target system use case and the target system, event information of each of the use case events in the use case event set is determined, wherein the event information includes the use case identifier.

7. The method according to claim 6, characterized in that Determining the event information of each of the use case events in the use case event set according to the interactive operation between the target object indicated by the use case of the target system and the target system includes: Determine the target event identifier and the reference event identifier of each use case event according to the execution sequence of each use case event in the use case event set, wherein the target event identifier is used to indicate the execution sequence of the use case event in the use case event set, and the reference event identifier is used to indicate the preceding use case event of the use case event; The event information of each of the use case events in the use case event set is determined according to the use case identifier, the target event identifier and the reference event identifier.

8. The method according to claim 1, characterized in that The operation data generated by the target application corresponding to the target system use case running in multiple terminals includes: Acquire the operation data generated by the target application running in multiple terminals, wherein the operation data includes event records of the operation events performed by the target object during the operation of the target application, and event records of the result events fed back by the target system to the target object, wherein the event records include a use case identifier and an event identifier; According to the use case identifier and the event identifier included in the event record, the event execution times corresponding to each of the use case events are counted.

9. The method according to claim 1, characterized in that: After determining the event conversion rate corresponding to each of the use case events in the target system use case according to the event execution times corresponding to each of the use case events, the method further includes: Acquire an event execution path determined according to the use case event set, wherein the event execution path includes a plurality of event nodes corresponding to the plurality of use case events, respectively, and the event nodes include step event nodes and result event nodes; Marking the event conversion rate corresponding to each event node in the event execution path; The marked event execution path is determined as the use case execution transformation diagram corresponding to the target system use case.

10. The method according to claim 1, characterized in that After determining the event conversion rate corresponding to each of the use case events in the target system use case according to the event execution times corresponding to each of the use case events, the method further includes: When the target conversion rate corresponding to the target use case event in the use case event set is lower than the conversion rate threshold, the application function associated with the target use case event in the target application is adjusted.

11. The method according to claim 10, characterized in that The adjusting of the application function associated with the target use case event in the target application includes: In the case where the target use case event is the use case step event, adjusting a target application function in the target application for triggering the target use case event, wherein the target application function corresponds to the execution result event for triggering the target use case event; In the case where the target use case event is the execution result event, a trigger condition of a target application function in the target application corresponding to the target use case event is adjusted.

12. A data processing device, characterized in that: include: An acquisition unit, configured to acquire a use case event set corresponding to a target system use case, wherein the use case event set includes a use case step event and an execution result event, wherein the use case step event indicates an operation event performed by a target object, and the execution result event indicates a result event fed back by a target system based on the use case step event, and the target object and the target system perform an interactive operation based on the target system use case; A sending unit, configured to send target applications corresponding to the target system use case to a plurality of terminals respectively, wherein the target system use case is used to indicate an interaction logic of a target interaction function in the target application; A first determining unit is configured to obtain operation data generated by the target application running in the plurality of terminals, and determine the event execution times corresponding to each use case event in the use case event set, wherein the use case event includes the use case step event and the execution result event; The second determination unit is used to determine the event conversion rate corresponding to each of the use case events in the target system use case according to the number of event executions corresponding to each of the use case events, wherein the event conversion rate indicates the execution probability of the use case event based on the previous use case event.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein the program executes the method described in any one of claims 1 to 11 when executed.

14. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented.

15. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to execute the method according to any one of claims 1 to 11 through the computer program.

Images