CN114138250A

CN114138250A - Method, device and equipment for generating steps of system case and storage medium

Info

Publication number: CN114138250A
Application number: CN202010913993.7A
Authority: CN
Inventors: 胡福星; 王鹏程; 郭计伟; 何光华; 邹世杰; 张癸鑫
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-09-03
Filing date: 2020-09-03
Publication date: 2022-03-04

Abstract

The application discloses a method, a device, equipment and a storage medium for generating steps of a system case, and relates to the field of system engineering. The method comprises the following steps: displaying an editing interface of the system case, wherein the editing interface comprises step adding controls; in response to the received adding operation on the step adding control, acquiring a target step template corresponding to the step type of the current action execution step from at least two types of preset step templates, wherein the target step template comprises the step sequence number of the current action execution step and the step description of the action execution step; editing the step description to obtain the edited step description; and generating the action execution step in the system case according to the step sequence number and the edited step description. The user can quickly add various types of action execution steps by combining the preset step template, the user does not need to manually edit the action execution steps one by one, the complete action execution steps can be directly added, and the compiling efficiency of the system use case is improved.

Description

Method, device and equipment for generating steps of system case and storage medium

Technical Field

The present application relates to the field of system engineering, and in particular, to a method, an apparatus, a device, and a storage medium for generating a system case.

Background

The system use case is used for representing the value which can be provided by the system for the executor and can be accepted by people, and the system use case comprises a step tree formed by a series of steps, and the step tree is used for describing the interaction process between the executor and the service provided by the system.

Taking the payment system as an example, the payment system receives a payment request of a user, acquires a payment order of the user according to the payment request of the user, changes the account balance of the user after the user pays, and feeds back successful payment information to the user. A professional designs a payment system by compiling a system case of the payment system, each step in the system case needs to be manually compiled by the professional when the system case is compiled, and when a new step is added before a certain step, the sequence number needs to be modified step by step.

In the technical scheme, the process of compiling and modifying the steps is relatively complicated, so that the efficiency of compiling the system use case is relatively low.

Disclosure of Invention

The embodiment of the application provides a method, a device, equipment and a storage medium for generating steps of a system case. The user can quickly add various types of action execution steps by combining the preset step template, the user does not need to manually edit the action execution steps one by one, the complete action execution steps can be directly added, and the compiling efficiency of the system use case is improved.

The technical scheme comprises the following steps:

according to an aspect of the present application, a method for generating a system use case is provided, where the method includes:

displaying an editing interface of the system case, wherein the editing interface comprises step adding controls;

in response to receiving the adding operation on the step adding control, acquiring a target step template corresponding to the step type of the current action execution step from at least two types of preset step templates, wherein the target step template comprises the step sequence number and the step description of the current action execution step;

editing the step description to obtain an edited step description;

and generating the action execution step according to the step sequence number and the edited step description.

According to another aspect of the present application, there is provided a system use case step generation apparatus, including:

the display module is used for displaying an editing interface of the system case, and the editing interface comprises step adding controls;

an obtaining module, configured to, in response to receiving an addition operation on the step addition control, obtain, from at least two types of preset step templates, a target step template corresponding to a step type of the current action execution step, where the target step template includes a step number of the current action execution step and a step description of the action execution step;

the editing module is used for editing the step description to obtain the edited step description;

and the generating module is used for generating the action execution step in the system case according to the step sequence number and the edited step description.

In an alternative embodiment, the editing interface includes a generated action execution step;

the acquiring module is configured to acquire a first step number corresponding to the generated action executing step, where the generated action executing step is a step before the action executing step;

the generating module is used for generating a second step sequence number in the target step template according to the first step sequence number; and generating the action execution step according to the second step serial number and the edited step description.

the display module is used for responding to the received first selection operation on the generated action execution step and displaying the step adding control; in response to receiving the add operation on the step add control, displaying a candidate step list, the candidate step list comprising at least two types of preset step templates; and the acquisition module is used for acquiring the target step template corresponding to the step type of the action execution step from the candidate step list.

In an optional embodiment, the obtaining module is configured to obtain, in response to receiving a second selection operation on the candidate step list, a step type of the action execution step; and acquiring the target step template corresponding to the step type from a template database according to the step type.

In an alternative embodiment, the editing interface does not include a generated action execution step;

the obtaining module is used for responding to a received turn adding control on the editing interface and obtaining a preset turn template corresponding to the system use case, wherein the preset turn template comprises preset step templates corresponding to n step types, the preset step templates corresponding to the n step types are arranged in sequence, and n is a positive integer;

the generation module is configured to generate a round step sequence in the system case according to the preset round template, where the round step sequence includes action execution steps corresponding to the preset step templates arranged in sequence.

In an optional embodiment, the obtaining module is configured to obtain an extension step type of the current path extension step in response to a result difference existing in the execution process of the current action execution step; obtaining a preset expansion template corresponding to the path expansion step according to the type of the expansion step; and the generation module is used for generating the step of the current extension path according to the preset extension template, wherein the step of the current extension path comprises at least one turn step sequence, and the turn step sequence comprises at least one action execution step.

In an optional embodiment, the apparatus includes a processing module, the editing interface includes a deletion control, and the action execution step in the system use case corresponds to a step node;

the obtaining module is configured to obtain, in response to receiving a deletion operation on the deletion control, a node identifier of a step node corresponding to an ith action execution step, where the ith action execution step corresponds to the deletion operation, and i is a positive integer;

the processing module is used for adding the ith action execution step into a list to be deleted according to the node identification; responding to the step node corresponding to the ith action execution step to correspond to a sub-step node, and adding the action execution step corresponding to the sub-step node to the list to be deleted; repeating the step of adding the action execution step corresponding to the sub-step node to the list to be deleted until all the step nodes in the system case are traversed; and deleting the step nodes in the list to be deleted.

In an optional embodiment, the editing interface includes a folding control and a generated action execution step, and the generated action execution step corresponds to a step node;

the processing module is used for responding to the received folding operation on the folding control and the node state of the step node corresponding to the generated action execution step is an unfolding state, and switching the node state of the step node into a folding state; in response to the step node corresponding to a sub-step node, switching a node state of the sub-step node to the folded state; repeating the step of switching the node state of the sub-step node into the folded state until all the step nodes in the system use case are traversed; and the display module is used for folding and displaying the generated action execution steps in the editing interface according to the folding state.

In an optional embodiment, the processing module is configured to, in response to receiving an expansion operation on the folding control and that the node state of the step node corresponding to the generated action execution step is a folded state, switch the node state of the step node to an expansion state; and the display module is used for expanding and displaying the generated action execution steps in the editing interface according to the expansion state.

According to another aspect of the present application, there is provided a computer device comprising a processor and a memory, wherein at least one instruction, at least one program, a set of codes, or a set of instructions is stored in the memory, and the at least one instruction, the at least one program, the set of codes, or the set of instructions is loaded and executed by the processor to implement the step generation method of the system use case as described in the above aspect.

According to another aspect of the present application, there is provided a computer-readable storage medium having at least one instruction, at least one program, a set of codes, or a set of instructions stored therein, which is loaded and executed by a processor to implement the method for generating steps for a system use case as described in the above aspect.

According to another aspect of the application, a computer program product or computer program is provided, comprising computer instructions stored in a computer readable storage medium. The computer instructions are read from the computer readable storage medium by a processor of a computer device, and the processor executes the computer instructions to cause the computer device to perform the method for generating system use cases as described above.

The beneficial effects brought by the technical scheme provided by the embodiment of the application at least comprise:

the corresponding preset step template is obtained according to the step type of the current action execution step, and the user can quickly add the current action execution step in the system case by combining the preset step template.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a block diagram of a computer system provided in an exemplary embodiment of the present application;

FIG. 2 is a flowchart of a method for generating system use cases according to an exemplary embodiment of the present application;

FIG. 3 is a schematic diagram of an editing interface for a system use case provided by an exemplary embodiment of the present application;

FIG. 4 is a flowchart of a method for generating system use cases according to another exemplary embodiment of the present application;

FIG. 5 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 6 is a schematic diagram of an editing interface for a system use case provided in another exemplary embodiment of the present application;

FIG. 7 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 8 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 9 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 10 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 11 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 12 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 13 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 14 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 15 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 16 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 17 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 18 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 19 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 20 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

FIG. 21 is a schematic diagram of an editing interface for a system use case provided by another exemplary embodiment of the present application;

fig. 22 is a block diagram of a device for generating steps of a system use case according to an exemplary embodiment of the present application;

FIG. 23 is a block diagram of a computer device according to an exemplary embodiment of the present application;

fig. 24 is a schematic device structure diagram of a server according to an exemplary embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

First, terms related to embodiments of the present application will be described.

The system uses the case: the method is used for representing the value which can be provided by a system for an executor and is acceptable to people, and the system use case comprises a step tree which is formed by a series of steps and is used for describing the interaction process between the executor and the service provided by the system. The use cases are scenario descriptions in a text form, and system developers are enabled to clarify functions (or services) and interaction processes provided by the system for executors by writing the system use cases, so that the system developers can conveniently develop a system with comprehensive functions.

The executive is: refers to an entity external to the system that interacts with the system and that participates in the execution of use cases in some manner. The performers can be persons or objects, and can also be time or other systems, and the performers comprise main performers and auxiliary performers, and the main performers and at least one auxiliary performer are included in the process of interacting with the system. For example, in the interaction with the payment system, the primary actor is the user of the payment order and the secondary actors are the bank and credit system. It should be noted that the performer is not a person or thing itself, but a character that the person or thing represents in the interaction process. For example, xiao ming is a librarian who interacts with the book management system, and may be either a librarian or a borrower.

The method comprises the following steps: describing the actions performed by the performer or the system. For example, the payment system verifies whether the user's payment account is correct, and performs the step of verifying the payment account information. The system use case comprises a step tree formed by a plurality of steps, wherein each step is used for describing an action.

And (4) turning: the method refers to a group of step sequences corresponding to the step from the action execution step of the request type to the action execution step of the preset type in the system use case, namely a group of complete step sequences from the step of the main executor requesting the system to the jump step or the use case ending step. A sequence of round steps includes at least one step. In the embodiment of the present application, the turn is named a turn step sequence.

Expanding a path: refers to the path branch caused by the difference of the result generated when the step is executed in the process of the interaction between the executor and the system. The extended path includes at least one step, for example, the extended path a corresponds to when the payment account information is verified to be legal, and the extended path b corresponds to when the payment account information is wrong. The extended path a comprises the steps of subsequent operations when the payment system verifies that the payment account information is correct, such as the payment system requests a deduction from a bank; the expanded path b includes steps that are subsequent operations when the payment system verifies that the payment account information is wrong, such as the payment system rejecting the user's payment request.

It should be noted that, the steps, the sequence of round steps and the extension path are nested with each other, one step may include the extension path or not include the extension path, one extension path includes at least one sequence of round steps, and one sequence of round steps includes at least one step.

The method for generating the system case steps provided by the embodiment of the application can be applied to describing services provided by various functional modules of system modeling, or used for simulating functions provided by software when software developers develop the software. The method provided by the embodiment of the application can be used for defining the functions of the system or software to be developed and the interactive process with an executor. The method provided by the embodiment of the application can improve the efficiency of writing the system use case by professional personnel, and in some cases, non-professional personnel can write the simple system use case by the method provided by the embodiment of the application.

The method for generating the steps of the system case provided by the embodiment of the application can be applied to computer equipment with stronger data processing capacity. In a possible implementation manner, the method for generating the steps of the system use case provided in the embodiment of the present application may be applied to a personal computer, a workstation, or a server, that is, the method for generating the steps of the system use case may be implemented by the personal computer, the workstation, or the server.

FIG. 1 illustrates a schematic diagram of a computer system provided by an exemplary embodiment of the present application. The computer system 100 includes a terminal 101 and a server 102, wherein the terminal 101 and the server 102 perform data communication via a communication network, optionally, the communication network may be a wired network or a wireless network, and the communication network may be at least one of a local area network, a metropolitan area network, and a wide area network.

The terminal 101 runs a system use case platform supporting an action execution step in generating a system use case, and the system use case platform may be an application program, a web page, an applet (an application program depending on a host program), and the like, which is not limited in the embodiment of the present application. Illustratively, the preset round template, the preset step template and the preset extension template required by the system use case are stored in the terminal 101.

Illustratively, the terminal 101 includes a mobile terminal such as a smart phone, a smart watch, a tablet computer, a laptop portable notebook computer, and a smart robot, and also includes a terminal such as a desktop computer and a projection computer, and the type of the terminal is not limited in this embodiment of the application.

The server 102 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a Network service, cloud communication, a middleware service, a domain name service, a security service, a Content Delivery Network (CDN), a big data and artificial intelligence platform, and the like. In one possible implementation, the server 102 is a background server of a system use case platform in the terminal 101. Illustratively, the server 102 includes a preset round template, a preset step template and a preset extension template required for writing system use cases.

And the user generates action execution steps in the system use case through the system use case platform.

The terminal 101 starts a system use case platform and displays an editing interface of the system use case. Illustratively, at least one of a turn addition control and a step addition control is included on the editing interface. In some embodiments, the user creates a new system case, the editing interface does not include any action execution step, the user generates a round in the new system case by clicking a round addition control, the round refers to a complete step sequence from a step of requesting the system by a main executor to a step of jumping or a step of ending the case in the system case, and the step of jumping refers to a step of triggering the execution sequence of the action execution step to change, for example, jumping from step 1 to step 3; the use case ending step refers to an action execution step corresponding to the end of a system use case. In the present embodiment, the turn is again named a sequence of turn steps. In response to receiving an add operation on the round add control, the terminal 101 acquires a preset round template from a template database in the server 102. Illustratively, one preset round template includes four step types of action execution steps. Similarly, in response to receiving the adding operation on the step adding control, the terminal 101 obtains the preset step templates from the template database, the preset step templates correspond to the action executing steps one to one, each preset step template comprises a step sequence number and step description, and a user can edit, delete, expand, fold and the like each action executing step.

For convenience of description, the following embodiments are described as examples in which the method for generating the system case is executed by the terminal.

Fig. 2 is a flowchart illustrating a method for generating system use cases according to an exemplary embodiment of the present application. The embodiment is described by taking the method as an example for the terminal 101 in the computer system 100 shown in fig. 1, and the method comprises the following steps:

step 201, displaying an editing interface of the system case, wherein the editing interface comprises step adding controls.

Typically, system use cases are described in text form, and in some embodiments, by use of an illustration. An executor refers to an entity that interacts with the system outside the system and participates in the execution of a use case in some way. Actors include people, things, time or other systems, etc. The embodiment of the present application takes a system case of editing a text form as an example for explanation.

The system use case comprises at least one action execution step, wherein the action execution step is a step which can be generated when an executor interacts with the system, for example, the executor is a human, the system is a payment system, and one action execution step can be 'a user requests to pay a purchase order'. When the system use case comprises a plurality of action execution steps, the action execution steps form a step tree, and the tree structure of the step tree describes the sequence relation among the action execution steps and the result difference of the action execution steps in the execution process.

Illustratively, an editing application program supporting the function of editing system use cases is installed and run on a terminal used by a user. When the user starts the editing application program, the terminal displays an editing interface of a system case, and step adding controls for adding preset step templates are displayed in the editing interface. In some embodiments, the editing interface may further include a variety of add controls for adding different types of preset step templates. The names of the controls are not limited in the embodiments of the present application.

Step 202, in response to receiving the adding operation on the step adding control, obtaining a target step template corresponding to the step type of the current action execution step from at least two types of preset step templates, where the target action template includes a step number and a step description of the current action execution step.

When the terminal used by the user is a mobile terminal such as a smart phone and a tablet computer, the adding operation comprises at least one of a single-click operation, a double-click operation (including at least one of a single-finger double-click operation and a multi-finger double-click operation), a dragging operation, a sliding operation and a hovering operation. When the terminal used by the user is a terminal connected with the external input device, such as a desktop computer, a notebook computer, and the like, the adding operation includes an operation received by the external input device, for example, if the external input device is a mouse, the adding operation is an operation corresponding to a mouse click (including a mouse left click, a mouse right click, and a mouse right click) by the user, or if the external input device is a keyboard, the adding operation is an operation corresponding to a keyboard click by the user, or if the external input device is a keyboard and a mouse, the adding operation is an operation corresponding to a mouse click and a keyboard click by the user.

The preset step template refers to a step template corresponding to a pre-stored action execution step, and is illustratively stored in the terminal, or stored in a template database of the server. The preset step template includes at least two types of step templates, each type of step template corresponding to a step type of an action execution step.

The target step template refers to a step template selected by the user when editing the action execution step. If the user is editing the third action execution step in the system use case, the target step template used when editing the action execution step is determined by determining the step type of the third action execution step. In some embodiments, the editing application determines the step type of the present action execution step according to the step type of a step preceding the present action execution step. In other embodiments, the editing application determines the step type of the current action performing step according to a step (such as the content included in the step and the step number) before the current action performing step.

In some embodiments, a preset step template corresponds to an action execution step; in other embodiments, multiple action execution steps may be simultaneously corresponded by other preset step templates, i.e., other preset step templates may generate a sequence of steps.

The step types include at least one of the following types: basic step type (step 1 to step 5 shown in fig. 3), extended step type (extended a-step and extended b-step in fig. x), and round step type (round 1 → 5 shown in fig. 3). The basic step type includes at least one of a verification step type, a change step type, a feedback step type, and an auxiliary performer step type; the extension step type includes at least one of a request extension type, a verification extension type, and an auxiliary actor extension type.

And step 203, editing the step description to obtain the edited step description.

The step description refers to editable text description in the preset step template. Illustratively, the step description is edited by manually inputting a text by a user, or by switching a preset step description. In an example, as shown in fig. 3, the current action execution step being edited is step 6, and a plurality of preset step descriptions 12 are displayed in an editing interface 10 of the system case, for example, a user requests to query a purchase order, [ system ] feeds back payment success information, and the like. The user clicks on step description 12 "user request for purchase order", and the selected step description 12 is displayed in step input box 11. Schematically, the step description 12 is pre-set for the payment system. In some embodiments, the step description 12 may be preset for different scenarios or preset for different types of systems, which is not limited in this application.

And step 204, generating the action execution step according to the step sequence number and the edited step description.

As shown in fig. 3, the step number of the current operation execution step is generated based on the step number of the previous operation execution step, and for example, the step number of the current operation execution step is 6. The step description 12 is determined by the user selecting a preset step description, so as to generate the action execution step (the sixth action execution step in the system use case) this time.

In summary, according to the method provided in this embodiment, the corresponding preset step template is obtained according to the step type of the current action execution step, and the user can quickly add the current action execution step in the system case by combining the preset step template, and meanwhile, the various types of action execution steps can be quickly added through the various types of preset step templates, so that the user does not need to manually edit the action execution steps one by one, and the complete action execution step can be directly added, thereby improving the compiling efficiency of the system case.

Fig. 4 is a flowchart illustrating a method for generating system use cases according to another exemplary embodiment of the present application. The embodiment is described by taking the method as an example for the terminal 101 in the computer system 100 shown in fig. 1, and the method comprises the following steps:

step 401, displaying an editing interface of the system use case, wherein the editing interface comprises the step of adding a control.

In some embodiments, the editing interface includes already generated action execution steps, i.e., previously generated action execution steps are displayed in the editing interface 20. And the editing application program for editing the system use case displays an editing interface of the system use case.

As shown in the upper diagram of fig. 5, the previously generated actions are displayed on the editing interface 20 of the system use case to execute step 1 to step 5, and a step adding control 13 is also displayed, where the step adding control 13 is displayed on the editing interface 20 in a representation form of a plus sign. Illustratively, the action execution step of this time is an action execution step after the fifth step in the system case.

Step 402, in response to receiving the adding operation on the step adding control, obtaining a target step template corresponding to the step type of the current action execution step from at least two types of preset step templates, where the target action template includes a step number and a step description of the current action execution step.

As shown in the upper diagram of fig. 5, the user selects step 5 (the dotted line box indicates that the user selects to add a new action execution step after the step), step addition control 13 is displayed on step 5, the user clicks the step addition control 13, and target step template 14 is displayed, the target step template 14 being a step template selected from at least two types of preset step templates. The target step template 14 is of the verification type.

And step 403, editing the step description to obtain the edited step description.

As shown in the lower diagram of fig. 5, the target step template 14 is "[ system ] check xxx information", and the user may modify the target step template by manually inputting text, for example, modifying the target step template to "[ system ] check user's identity information".

In step 404, a first step number corresponding to a generated action execution step is obtained, where the generated action execution step is one step before the current action execution step.

Schematically, as shown in the lower diagram of fig. 5, the generated action execution steps 1 to 5 are displayed on the editing interface 20, and the action execution step generated this time is a step subsequent to step 5, so that the editing application acquires the first step number (number 5) corresponding to step 5.

Step 405, generating a second step number in the target step template according to the first step number.

Illustratively, the generated action execution steps are out of order, and the editing application arranges the generated action execution steps in order, or modifies the sequence number in the target step template according to the order of the generated action execution steps after the user selects the target step template.

In some embodiments, the editing application includes a ranking model, which is a machine learning model with a ranking function, with which to rank the action execution steps. And the sequencing model generates a second step sequence number in the target step template according to the first step sequence number corresponding to the generated action execution step.

And step 406, generating the action execution step according to the second step serial number and the edited step description.

Illustratively, the user edits the step description by manually entering text. And the editing application program generates an action execution step 6 (the action execution step 6 is 'system' for verifying the identity information of the user) according to the second step sequence number (sequence number 6) and the step description edited by the user.

In some embodiments, the user inserts a new action execution step between the generated action execution steps, that is, the action execution step of this time is not after the last action execution step of the system case, for example, the action execution step of this time is inserted after step 2 shown in fig. 5, then the step number of the action execution step of this time is 3, the step number of the original action execution step 3 (system requests bank information) is modified to 4 by the editing application program using the ranking model, and the action execution step after modification, that is, the step number of the action execution step 5 is finally modified to step number 6.

It is understood that step 403 may be performed after step 405, or step 403 may be performed before step 404, or step 403 may be performed simultaneously with

steps

404 and 405.

In summary, according to the method of the embodiment, the corresponding preset step template is obtained according to the step type of the current action execution step, and the user can quickly add the current action execution step in the system case by combining the preset step template, and meanwhile, the various types of action execution steps can be quickly added through the various types of preset step templates, so that the user does not need to manually edit the action execution steps one by one, and the complete action execution step can be directly added, thereby improving the compiling efficiency of the system case.

When a new action execution step is generated, the second step number of the action execution step of this time is determined according to the first step number corresponding to the generated action execution step, and the action execution step of this time can be accurately generated by combining the edited step description and the second step number. Even if the steps are inserted from the middle to execute the actions, the sequence of the steps can be automatically adjusted, the time for modifying the system use case by the user is reduced, and the editing efficiency is improved.

Various types of action execution steps generated in the system example are described below in conjunction with an interface diagram.

1. An action execution step that generates a basic step type.

In an alternative embodiment based on fig. 4, the editing interface of the system use case includes the generated action execution step, the system use case generates the step of the basic step type by the following way, and step 402 can be replaced by the following steps:

step 4021, responding to the received generated action to execute the first selection operation in the step, and displaying the step adding control.

As shown in fig. 6, the generated action execution step is displayed on the editing interface 30 of the system use case, and schematically, the user performs the first selection operation on the generated action execution step 1. The first selection operation includes at least one of a single-click operation, a double-click operation (including at least one of a single-finger double-click operation and a multi-finger double-click operation), a drag operation, a slide operation, and a hover operation. If the user clicks the action to execute step 1 (the dotted box indicates that the user has performed the selection operation), the step adding control 13 is displayed.

Step 4022, in response to receiving the adding operation on the step adding control, displaying a candidate step list, wherein the candidate step list comprises at least two types of preset step templates.

Illustratively, when the user clicks on the step addition control 13, a list of candidate steps 15 is displayed, as shown in FIG. 6. The candidate step list 15 includes a preset step template corresponding to the extension step type, a preset step template corresponding to the verification step type, and a preset step template corresponding to the auxiliary executor step type.

Step 4023, obtaining a target step template corresponding to the step type of the current action execution step from the candidate step list.

Responding to the received second selection operation on the candidate step list, and acquiring the step type of the action execution step; and acquiring a target step template corresponding to the step type from the template database according to the step type.

The second selection operation includes at least one of a single-click operation, a double-click operation (including at least one of a single-finger double-click operation and a multi-finger double-click operation), a drag operation, a slide operation, and a hover operation. Illustratively, the user clicks on the check step type 16 in the candidate step list 15 (the dashed box indicates that the user has performed a selection operation). And acquiring a target step template from a template database according to the type of the verification step, wherein the template database is stored in a server. Illustratively, the target step template corresponding to the verification step type 16 is "2. [ system ] to verify the fingerprint information of the user".

In some embodiments, the step of generating the change step type in the system use case in the same manner as in the above embodiments, as shown in fig. 7, the generated action execution step is displayed on the editing interface 31 of the system use case, the step addition control 13 is displayed on the action execution step 2, when the user clicks the step addition control 13, the candidate step list 15 is displayed, the user clicks the change step type 17, and the editor program obtains the target step template corresponding to the change step type 17 from the template database. Illustratively, the target step template corresponding to change step type 17 is "3. [ system ] requesting the bank to change the account balance of the paying user".

In other embodiments, the step of generating the feedback step type in the system use case in the same manner as in the above embodiments is, as shown in fig. 8, a generated action execution step is displayed on an editing interface 32 of the system use case, a step addition control 13 is displayed on the action execution step 4, when the user clicks the step addition control 13, a candidate step list 15 is displayed, the user clicks the feedback step type 18, and the editor program obtains a target step template corresponding to the feedback step type 18 from the template database. Illustratively, the target step template corresponding to the feedback step type 18 is "5. [ system ] to feed back payment success information to the user.

In other embodiments, in the same manner as in the above-described embodiment, in the step of generating an assistant executor step type in a system use case, as shown in fig. 9, the generated action execution step is displayed on the editing interface 33 of the system use case, a step addition control 13 is displayed on a certain action execution step, when the user clicks the step addition control 13, the candidate step list 15 is displayed, the user clicks the assistant executor step type 19, and the editor program obtains a target step template corresponding to the assistant executor step type 19 from the template database. Illustratively, the target step template corresponding to the auxiliary actor step type 19 is "16. [ system ] request auxiliary actor action xx events". It should be noted that, according to the use case writing protocol, the action execution steps corresponding to the auxiliary executor step types are added and deleted in pairs, so that the two types of steps, namely the "system request auxiliary executor step" and the "system request auxiliary executor feedback step", are bound to the same preset step template, that is, the steps of the two types of steps can be generated through one preset step template.

In summary, the method provided in this embodiment enables the user to add a new action execution step after any generated action execution step by displaying the step addition control on the generated action execution step. Storing multiple types of pre-set step templates with the template database allows the user more options when adding new action execution steps.

And acquiring the preset step template of the corresponding type from the template database according to different step types, so that the user can accurately add new actions to execute the steps according to actual conditions.

2. An action execution step of the generate round step type.

In an alternative embodiment based on fig. 4, the editing interface of the system use case does not include the generated action execution step, and the system use case generates the step of the round step type by the following method, including the following steps:

step 411, in response to receiving the round addition control on the editing interface, acquiring a preset round template corresponding to the system use case, where the preset round template includes preset step templates corresponding to n step types, the preset step templates corresponding to the n step types are arranged in sequence, and n is a positive integer.

In some embodiments, no generated action is executed on the editing interface, and the step of the round step type is generated by triggering the round adding control, for example, a typeface of "add round" is displayed on the editing interface, and the user clicks the "round" two word to generate the step of the round step type. Illustratively, a one-round step sequence includes four action-performing steps, respectively a step of requesting a step type, a step of verifying a step type, a step of changing a step type, and a step of feeding back a step type.

As shown in the upper diagram of fig. 10, the generated sequence of the turn steps is displayed on the editing interface 34 of the system use case, and the turn adding control 21 is displayed at the parent node corresponding to the turn steps. Illustratively, different add controls are displayed on different step types, such as a step add control on a basic step type of action execution step and a round add control on a round step type of step. When the user clicks the round addition control 21, a list of candidate steps 15 is displayed, the list of candidate steps 15 including the new round option.

Illustratively, the preset-round template includes corresponding preset-step templates of two step types, which are a verification step type and a feedback step type, respectively.

Step 412, generating a round step sequence in the system case according to the preset round template, where the round step sequence is used to represent a group of step sequences corresponding to the start of the action execution step of the request type to the end of the action execution step of the preset type in the system case.

The round step sequence refers to a complete set of step sequences from the request system step of the main executor to the jump step or the use case ending step in the system use case. The round step sequence comprises action execution steps corresponding to threshold step templates arranged in sequence. When the user clicks on the add-on-turn option, as shown in the lower diagram of fig. 10, a newly generated sequence of turn steps is displayed on the editing interface 34 of the system use case (turn 7 → 10). The preset turn template refers to a step template corresponding to a pre-stored turn step sequence, and one preset turn template comprises at least one preset step template corresponding to an action execution step.

In summary, in the method provided in this embodiment, some basic step sequences can be quickly added through the preset round template, so that the user can quickly create the basic path of the system use case, and the user does not need to generate a new round step sequence by adding editing steps for multiple times, thereby improving the writing efficiency of the system use case.

3. And generating an action execution step of the extension step type.

In an alternative embodiment based on fig. 4, the step of generating the extension step type by the system use case in the following manner includes the following steps:

step 421, responding to the result difference existing in the execution process of the current action execution step, obtaining the extension step type of the current path extension step.

When the system is performing an action execution step, there may be different execution results for the action execution step. For example, the system verifies whether the account password of the user is correct, and if the account password is correct, the step a is executed; and if the account number and the password are incorrect, executing a step b, wherein the step a is an expanding step a, and the step b is an expanding step b.

The extension step type includes at least one of a request extension type, a verification extension type, and an auxiliary actor extension type.

And 422, acquiring a preset extension template corresponding to the path extension step according to the extension step type.

As shown in fig. 11, the generated action execution step is displayed on the editing interface 35 of the system use case, where there is a difference in the result in the execution process of the action execution step 1, and according to the above embodiment, when the user clicks the step addition control 13, the candidate step list 15 is displayed, the user clicks the request extension type 22, and the editor program obtains the target step template corresponding to the request extension type 22 from the template database. Illustratively, the target step template corresponding to the request extension type 22 is "extend a-submit request information" (the dashed box represents the extend path step).

In some embodiments, in the same manner as in the above embodiments, the step of verifying the extension type in the system case is used, as shown in fig. 12, a generated action execution step is displayed on an editing interface 36 of the system case, and if there is a difference in the result in the execution process of the action execution step 2, according to the above embodiments, when the user clicks the step adding control 13, the candidate step list 15 is displayed, the user clicks the verification extension type 23, and the editor program obtains the target step template corresponding to the verification extension type 23 from the template database. Illustratively, the target step template corresponding to the authentication extension type 23 is "extend a-authenticate payment account request illegal" (the dashed box represents the extension path step).

In other embodiments, the step of assisting the executor extension type in the system use case in the same manner as in the above embodiments is, as shown in fig. 13, a generated action execution step is displayed on an editing interface 37 of the system use case, and if there is a difference in the result in the execution process of the action execution step 5, according to the above embodiments, when the user clicks the step addition control 13, the candidate step list 15 is displayed, the user clicks the assistant executor extension type 24, and the editor program obtains the target step template corresponding to the assistant executor extension type 24 from the template database. Illustratively, the target step template corresponding to the auxiliary performer extension type 24 is "extend a-verify the result of the auxiliary performer feedback is xx result" (the dashed box represents the extended path step).

Step 423, generating the path extension step according to the preset extension template, where the path extension step includes at least one round step sequence, and the round step sequence includes at least one action execution step.

One step of extending the step type includes the step of the round step type. As shown in fig. 13, the expanding step a includes a round 1 → 5a2, and the step of one round step type includes at least one action performing step, such as action performing step 5a1 and action performing step 5a 2.

In summary, according to the method provided in this embodiment, when there is a result difference in the execution process of the action execution step, by obtaining the preset extension template, the user can quickly combine the preset extension template to generate the extension path, so that the user can accurately generate the extension path according to the actual situation when writing the system use case.

It will be appreciated that, in an alternative embodiment based on fig. 4, the action-performing step can also be deleted, the deletion mode including the following steps:

and 431, responding to the received deletion operation on the deletion control, and acquiring the node identifier of the step node corresponding to the ith action execution step, wherein the ith action execution step corresponds to the deletion operation, and i is a positive integer.

The editing interface comprises a deleting control, step nodes correspond to action execution steps in the system case, and each step node corresponds to a unique node identifier. Illustratively, the node identifier includes expressions such as characters, english, numbers, punctuation marks, and the like, which is not limited in the present application.

As shown in fig. 7, a delete control 25 is displayed on the editing interface 31 of the system use case. Illustratively, the delete operation includes: a single click operation, a double click operation (including at least one of a single-finger double click operation and a multi-finger double click operation), a drag operation, a slide operation, and a hover operation. When the user clicks the delete control 25, the delete action performs step 2 and its corresponding sub-steps. For example, the node of the step node corresponding to the action execution step 4 is identified as 4, and the action execution step 4 corresponds to the substep nodes (substep nodes 4a, 4a1, and 4a 2).

And step 432, adding the ith action execution step into the list to be deleted according to the node identification.

For example, when the user wants to delete the action execution step 4, the editor adds the action execution step 4 to the list to be deleted.

Step 433, in response to that the step node corresponding to the ith action execution step corresponds to the sub-step node, adding the action execution step corresponding to the sub-step node to the list to be deleted.

And the editing program determines whether the action execution step 4 has a corresponding sub-step node, and if the action execution step 4 has a corresponding sub-step node, the sub-step node is also added to the list to be deleted.

And 434, repeating the step of adding the action execution step corresponding to the sub-step node to the list to be deleted until the step nodes in the system case are traversed.

And in analogy, the traversal action executes all the substep nodes corresponding to the step 4, and the substep nodes are also added to the list to be deleted.

Step 435, deleting the step nodes in the list to be deleted.

And deleting all the step nodes in the list to be deleted by the editing application program.

It is to be understood that the above-described deletion action performing step includes at least one of a step of deleting a basic step type, a step of extending a step type, and a step of a round step type. As shown in fig. 14 to 16, the delete control is displayed on a different type of step.

In summary, according to the method provided in this embodiment, when a user needs to delete some steps, the substep nodes corresponding to the step nodes are added to the list to be deleted by traversing the step nodes corresponding to the action execution steps in the system case, and then the step nodes in the list to be deleted are deleted in a unified manner, so that the terminal does not need to delete the step nodes repeatedly for many times, and the operation pressure of the terminal is relieved.

The following describes how the operation execution procedure is displayed on the editing interface of the system case.

1. And (5) folding and displaying.

In an optional embodiment based on fig. 4, the editing interface includes a folding control and a generated action execution step, the generated action execution step corresponds to a step node, and the action execution step is displayed in the editing interface of the system use case in a folded manner, which includes the following steps:

step 441, in response to receiving the folding operation on the folding control and the node state of the step node corresponding to the generated action execution step being the unfolded state, switching the node state of the step node to the folded state.

As shown in fig. 17, a first state 26 and a second state 27 of a folding control (indicated by a triangle) are displayed on the editing interface, wherein the first state 26 corresponds to the folding state of the folding control, and the second state 27 corresponds to the unfolding state of the folding control. It is understood that when the user clicks the folding control with the first state 26, the action corresponding to round 1 → 6 is performed and the step is expanded; when the user clicks the collapse control with the second state 27, the action corresponding to the round 7 → 22 performs the step of collapsing display.

Step 442, in response to the step node corresponding to the sub-step node, switching the node state of the sub-step node to the folded state.

The display mode of switching the action execution step by switching the node state of the step node is realized by the following codes:

wherein id represents a unique node identifier, label represents a step node type (round step type, basic step type and extended step type), fullLabel represents a node display full name, extended represents whether a step node is expanded and displayed, visible represents whether a subsidy node is rendered, level represents a node level of the step node, and children represents a substep node list.

And step 443, repeating the step of switching the node state of the sub-step node into the folded state until all the step nodes in the system use case are traversed.

By analogy, as shown in fig. 17, the traversal action executes all the sub-step nodes corresponding to step 7, and switches the node states of the sub-step nodes to the folded state.

And step 444, folding and displaying the generated action in the editing interface according to the folding state.

As shown in fig. 17, the node state of the step node of the action execution step corresponding to the round 1 → 6 is the folded state, and the action execution step corresponding to the round 1 → 6 is displayed in the folded state.

2. And (5) unfolding and displaying.

In an optional embodiment based on fig. 4, the editing interface includes a folding control and a generated action execution step, the generated action execution step corresponds to a step node, and the action execution step is expanded and displayed in the editing interface of the system use case, and includes the following steps:

step 445, in response to receiving the unfolding operation on the folding control and that the node state of the step node corresponding to the generated action execution step is the folding state, switching the node state of the step node to the unfolding state.

Similarly, the unfolding display is opposite to the folding display, the node state of the step node is switched from the folding state to the unfolding state, and the editing interface displays the unfolded action execution step.

Step 446, expanding and displaying the generated action execution step in the editing interface according to the expansion state.

Different step types of action execution steps the content displayed differs when the display is expanded.

As shown in fig. 18, when the action execution step of the round step type is expanded to be displayed, steps of the basic step type, that is, basic step paths when the system interacts with the performer are displayed in the editing interface.

As shown in fig. 19, in comparison with fig. 18, when the basic step type action execution step expansion display is performed, the respective expansion path steps, such as expansion a, expansion b, expansion c, and the like, are displayed in the editing interface.

As shown in fig. 20, in comparison with fig. 19, when the action execution step of the extension step type is expanded to be displayed, the action execution steps at the respective extension path steps are displayed in the editing interface, such as step 8a1, step 8a2, and the like.

In summary, in the method provided in this embodiment, the folding operation is received through the folding control on the editing interface, and the editing interface can display the steps in the system use case in a folding manner. When more steps exist in the editing interface, a user can quickly browse the steps in the editing interface through a folding display mode and observe the basic path of the system case, so that a developer can quickly know the main functions provided by the system.

And receiving the expansion operation through a folding control on the editing interface, wherein the editing interface can display steps in the system use case in an expansion mode. When a developer wants to know the action execution steps in the system use case in detail, the developer can know the context relationship among the action execution steps in detail through the unfolding operation, and the developer does not influence the basic path of the system use case, so that the developer can know more functional details of the system.

For example, as shown in fig. 21, as can be seen from fig. 21, an editing interface of a system case includes action execution steps of a basic step type (e.g., action execution step 1, step 2b, etc.), a round step type (e.g., action execution step round 1 → 2b4), and an extension step type (e.g., extension a), where various types of steps are displayed in a folding display manner or in an expanding display manner on the editing interface, e.g., extension path step b is displayed in an expanding state, and steps 2b to 2b2 are displayed in an expanding display manner on the editing interface.

It should be noted that, in the editing interface of each of the above embodiments, the hidden control 28 and the prompt control 29 are displayed, and after the action execution step, the hidden control 28 is displayed, which indicates that the action execution step can be hidden and displayed in the editing interface, and the user can select whether to hide the action execution step through manual operation, where the action execution step is a virtual step and cannot be edited, and is only used to prompt the user that some action execution steps are sub-steps of the action execution step. The prompt control 29 is used to indicate that the action execution step is incomplete, and is used to prompt the system builder to pay attention to the corresponding implementation manner of the action execution step when building the system.

It should be understood that the above embodiments of the generating step, the deleting step, the folding display step and the unfolding display step can be implemented individually or in any combination, and the combination mode of the embodiments of the present application is not limited.

The table one shows the efficiency comparison result between the method provided by the embodiment of the present application and the method for compiling system use cases in the related art.

Watch 1

Fig. 22 is a block diagram illustrating a structure of a device for generating a system use case according to an exemplary embodiment of the present application, where the device includes the following components:

the display module 2210 is configured to display an editing interface of the system use case, where the editing interface includes step adding controls;

an obtaining module 2220, configured to, in response to receiving an add operation on the step add control, obtain, from at least two types of preset step templates, a target step template corresponding to a step type of the current action execution step, where the target step template includes a step number of the current action execution step and a step description of the action execution step;

an editing module 2230, configured to edit the step description to obtain an edited step description;

and the generating module 2240 is used for generating the action execution step in the system case according to the step sequence number and the edited step description.

the acquiring module 2220 is configured to acquire a first step number corresponding to a generated action performing step, where the generated action performing step is a step before the action performing step of this time;

the generating module 2240 is configured to generate a second step number in the target step template according to the first step number; and generating the action execution step according to the second step sequence number and the edited step description.

the display module 2210 is configured to display a step addition control in response to receiving a first selection operation in a step executed by a generated action; in response to receiving an adding operation on the step adding control, displaying a candidate step list, wherein the candidate step list comprises at least two types of preset step templates;

the obtaining module 2220 is configured to obtain, from the candidate step list, a target step template corresponding to the step type of the step executed by the current action.

In an optional embodiment, the obtaining module 2220 is configured to, in response to receiving the second selection operation on the candidate step list, obtain the step type of the step executed by the current action; and acquiring a target step template corresponding to the step type from the template database according to the step type.

In an alternative embodiment, the editing interface does not include the generated action execution step;

the obtaining module 2220 is configured to, in response to receiving a round addition control on the editing interface, obtain a preset round template corresponding to a system use case, where the preset round template includes preset step templates corresponding to n types of steps, the preset step templates corresponding to the n types of steps are arranged in sequence, and n is a positive integer;

the generating module 2240 is configured to generate a round step sequence in the system case according to the preset round template, where the round step sequence includes action execution steps corresponding to the preset step templates arranged in sequence.

In an optional embodiment, the obtaining module 2220 is configured to, in response to a result difference existing in the execution process of the current action execution step, obtain an extension step type of the current path extension step; obtaining a preset expansion template corresponding to the path expansion step according to the type of the expansion step; a generating module 2240, configured to generate the path expanding step according to a preset expansion template, where the path expanding step includes at least one round step sequence, and the round step sequence includes at least one action executing step.

In an optional embodiment, the apparatus includes a processing module 2250, where the editing interface includes a delete control, and the action execution step in the system use case corresponds to a step node;

the obtaining module 2220 is configured to, in response to receiving a deletion operation on the deletion control, obtain a node identifier of a step node corresponding to an ith action execution step, where the ith action execution step corresponds to the deletion operation, and i is a positive integer;

the processing module 2250 is configured to add the ith action execution step to the to-be-deleted list according to the node identifier; responding to the step node corresponding to the ith action execution step to correspond to the substep node, and adding the action execution step corresponding to the substep node to a list to be deleted; repeating the step of adding the action execution step corresponding to the sub-step node to the list to be deleted until all the step nodes in the system case are traversed; and deleting the step nodes in the list to be deleted.

the processing module 2250 is configured to, in response to that the node state of the step node corresponding to the step executed by the generated action is the expanded state after the folding operation on the folding control is received, switch the node state of the step node to the folded state; responding to the substep node corresponding to the step node, and switching the node state of the substep node into a folding state; repeating the step of switching the node state of the sub-step node into the folding state until all the step nodes in the system case are traversed; the display module 2210 is configured to fold and display the generated action execution steps in the editing interface according to the folded state.

In an optional embodiment, the processing module 2250 is configured to, in response to receiving the unfolding operation on the folding control and that the node state of the step node corresponding to the generated action execution step is the folded state, switch the node state of the step node to the unfolded state; the display module 2210 is configured to expand and display the generated action execution steps in the editing interface according to the expanded state.

In summary, in the apparatus provided in this embodiment, the preset step template corresponding to the step type of the current action execution step is obtained, and the user can quickly add the current action execution step in the system case by combining the preset step template, and meanwhile, the multiple types of action execution steps can be quickly added through the multiple types of preset step templates, and the user does not need to manually edit the action execution steps one by one, and thus, the complete action execution step can be directly added, and the compiling efficiency of the system case is improved.

By displaying a step addition control over the generated action execution steps, the user is enabled to add a new action execution step after any generated action execution step. Storing multiple types of pre-set step templates with the template database allows the user more options when adding new action execution steps.

Some basic step sequences can be added quickly through the preset turn template, so that a user can quickly create a basic path of the system use case, the user does not need to add editing steps for multiple times to generate a new turn step sequence, and the writing efficiency of the system use case is improved.

When the action execution step has a result difference in the execution process, the preset extension template is obtained, so that a user can quickly combine the preset extension template to generate an extension path, and the user can accurately generate the extension path according to the actual situation when compiling a system case.

When a user needs to delete some steps, the substep nodes corresponding to the step nodes are added into the list to be deleted by traversing the step nodes corresponding to the action execution steps in the system case, and then the step nodes in the list to be deleted are deleted in a unified mode, so that the terminal does not need to be deleted repeatedly for many times, and the operation pressure of the terminal is relieved.

And receiving the folding operation through a folding control on the editing interface, wherein the editing interface can display steps in the system use case in a folding mode. When more steps exist in the editing interface, a user can quickly browse the steps in the editing interface through a folding display mode and observe the basic path of the system case, so that a developer can quickly know the main functions provided by the system.

It should be noted that: the step generation device for the system use case provided in the foregoing embodiment is only illustrated by dividing each functional module, and in practical applications, the function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the step generation device of the system case and the step generation method embodiment of the system case provided in the above embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiments and are not described herein again.

Referring to fig. 23, a block diagram of a computer device 2300 according to an exemplary embodiment of the present application is shown. The computer device 2300 may be a portable mobile terminal such as: smart phones, tablet computers, MP3 players (Moving Picture Experts Group Audio Layer III, motion video Experts compression standard Audio Layer 3), MP4 players (Moving Picture Experts Group Audio Layer IV, motion video Experts compression standard Audio Layer 4). Computer device 2300 may also be referred to by other names such as user equipment, portable terminal, and the like.

Generally, computer device 2300 includes: a processor 2301 and a memory 2302.

The processor 2301 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so on. The processor 2301 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 2301 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 2301 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the display screen. In some embodiments, the processor 2301 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.

Memory 2302 may include one or more computer-readable storage media, which may be tangible and non-transitory. Memory 2302 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in the memory 2302 is used to store at least one instruction for execution by the processor 2301 to implement the method for generating the steps of the system use case provided in the embodiments of the present application.

In some embodiments, computer device 2300 may also optionally include: a peripheral interface 2303 and at least one peripheral. Specifically, the peripheral device includes: at least one of a radio frequency circuit 2304, a touch display 2305, a camera assembly 2306, an audio circuit 2307, a positioning assembly 2308, and a power supply 2309.

The peripheral interface 2303 may be used to connect at least one peripheral related to I/O (Input/Output) to the processor 2301 and the memory 2302. In some embodiments, the processor 2301, memory 2302, and peripheral interface 2303 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 2301, the memory 2302, and the peripheral device interface 2303 can be implemented on separate chips or circuit boards, which are not limited by this embodiment.

The Radio Frequency circuit 2304 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuit 2304 communicates with communication networks and other communication devices via electromagnetic signals. The rf circuit 2304 converts an electrical signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 2304 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, etc. The radio frequency circuit 2304 may communicate with other terminals through at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: the world wide web, metropolitan area networks, intranets, generations of mobile communication networks (2G, 3G, 4G, 5G, and combinations thereof), Wireless local area networks, and Wireless Fidelity (WiFi). In some embodiments, the rf circuit 2304 may also include NFC (Near Field Communication) related circuits, which are not limited in this application.

The touch display 2305 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. Touch display 2305 also has the ability to capture touch signals on or over the surface of touch display 2305. The touch signal may be input to the processor 2301 as a control signal for processing. The touch screen display 2305 is used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the touch display screen 2305 may be one, providing the front panel of the computer device 2300; in other embodiments, the touch screen display 2305 can be at least two, each disposed on a different surface of the computer device 2300 or in a folded design; in other embodiments, touch display 2305 may be a flexible display disposed on a curved surface or on a folded surface of computer device 2300. Even more, the touch screen 2305 can be arranged in a non-rectangular irregular pattern, i.e., a shaped screen. The touch Display 2305 can be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), and other materials.

The camera assembly 2306 is used to capture images or video. Optionally, camera assembly 2306 includes a front camera and a rear camera. Generally, a front camera is used for realizing video call or self-shooting, and a rear camera is used for realizing shooting of pictures or videos. In some embodiments, the number of the rear cameras is at least two, and each of the rear cameras is any one of a main camera, a depth-of-field camera and a wide-angle camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize a panoramic shooting function and a VR (Virtual Reality) shooting function. In some embodiments, camera assembly 2306 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.

The audio circuit 2307 is used to provide an audio interface between a user and the computer device 2300. The audio circuit 2307 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals into the processor 2301 for processing or inputting the electric signals into the radio frequency circuit 2304 to realize voice communication. For stereo capture or noise reduction purposes, multiple microphones may be provided, each at a different location on computer device 2300. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 2301 or the radio frequency circuit 2304 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuit 2307 may also include a headphone jack.

The Location component 2308 is used to locate the current geographic Location of the computer device 2300 for navigation or LBS (Location Based Service). The Positioning component 2308 may be a Positioning component based on the Global Positioning System (GPS) in the united states, the beidou System in china, or the galileo System in russia.

The power supply 2309 is used to supply power to various components in the computer device 2300. The power source 2309 may be alternating current, direct current, disposable batteries, or rechargeable batteries. When the power supply 2309 includes a rechargeable battery, the rechargeable battery may be a wired rechargeable battery or a wireless rechargeable battery. The wired rechargeable battery is a battery charged through a wired line, and the wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, computer device 2300 also includes one or more sensors 2310. The one or more sensors 2310 include, but are not limited to: an acceleration sensor 2311, a gyro sensor 2312, a pressure sensor 2313, a fingerprint sensor 2314, an optical sensor 2315, and a proximity sensor 2316.

The acceleration sensor 2311 can detect the magnitude of acceleration in three coordinate axes of a coordinate system established with the computer device 2300. For example, the acceleration sensor 2311 may be used to detect components of the gravitational acceleration in three coordinate axes. The processor 2301 may control the touch display screen 2305 to display a user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 2311. The acceleration sensor 2311 may also be used for game or user motion data acquisition.

The gyro sensor 2312 may detect the body direction and the rotation angle of the computer device 2300, and the gyro sensor 2312 may cooperate with the acceleration sensor 2311 to acquire the 3D motion of the user on the computer device 2300. The processor 2301 may implement the following functions according to the data collected by the gyro sensor 2312: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.

Pressure sensors 2313 can be disposed on the side bezel of computer device 2300 and/or on the lower layers of touch display screen 2305. When the pressure sensor 2313 is provided on the side frame of the computer device 2300, a user's grip signal on the computer device 2300 can be detected, and left-right hand recognition or shortcut operation can be performed based on the grip signal. When the pressure sensor 2313 is arranged at the lower layer of the touch display screen 2305, the operability control on the UI interface can be controlled according to the pressure operation of the user on the touch display screen 2305. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.

The fingerprint sensor 2314 is used for collecting a fingerprint of a user to identify the identity of the user according to the collected fingerprint. Upon recognizing that the user's identity is a trusted identity, the processor 2301 authorizes the user to perform relevant sensitive operations including unlocking a screen, viewing encrypted information, downloading software, paying, and changing settings, etc. The fingerprint sensor 2314 may be provided on the front, back or side of the computer device 2300. When a physical key or vendor Logo is provided on the computer device 2300, the fingerprint sensor 2314 may be integrated with the physical key or vendor Logo.

The optical sensor 2315 is used to collect ambient light intensity. In one embodiment, the processor 2301 may control the display brightness of the touch display screen 2305 based on the ambient light intensity collected by the optical sensor 2315. Specifically, when the ambient light intensity is high, the display brightness of the touch display screen 2305 is increased; when the ambient light intensity is low, the display brightness of the touch display screen 2305 is turned down. In another embodiment, the processor 2301 may also dynamically adjust the shooting parameters of the camera assembly 2306 according to the intensity of ambient light collected by the optical sensor 2315.

A proximity sensor 2316, also known as a distance sensor, is typically provided on the front side of the computer device 2300. The proximity sensor 2316 is used to capture the distance between the user and the front of the computer device 2300. In one embodiment, the processor 2301 controls the touch display screen 2305 to switch from a bright screen state to a dark screen state when the proximity sensor 2316 detects that the distance between the user and the front surface of the computer device 2300 is gradually decreased; when the proximity sensor 2316 detects that the distance between the user and the front surface of the computer device 2300 is gradually increased, the touch display screen 2305 is controlled by the processor 2301 to switch from a breath screen state to a bright screen state.

Those skilled in the art will appreciate that the architecture shown in FIG. 23 is not intended to be limiting of the computer device 2300, and may include more or fewer components than those shown, or may combine certain components, or may employ a different arrangement of components.

Fig. 24 is a schematic structural diagram of a server according to an exemplary embodiment of the present application. The server may be the server 102 in the computer system 100 shown in fig. 1.

The server 2400 includes a Central Processing Unit (CPU) 2401, a system Memory 2404 including a Random Access Memory (RAM) 2402 and a Read Only Memory (ROM) 2403, and a system bus 2405 connecting the system Memory 2404 and the Central Processing Unit 2401. The server 2400 also includes a basic Input/Output System (I/O System)2406 for facilitating information transfer between devices within the computer, and a mass storage device 2407 for storing an operating System 2413, application programs 2414, and other program modules 2415.

The basic input/output system 2406 includes a display 2408 for displaying information and an input device 2409 such as a mouse, keyboard, etc. for a user to input information. Wherein the display 2408 and the input device 2409 are both connected to the central processing unit 2401 through an input-output controller 2410 connected to the system bus 2405. The basic input/output system 2406 may also include an input/output controller 2410 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, the input-output controller 2410 also provides output to a display screen, a printer, or other type of output device.

The mass storage device 2407 is connected to the central processing unit 2401 through a mass storage controller (not shown) connected to the system bus 2405. The mass storage device 2407 and its associated computer-readable media provide non-volatile storage for the server 2400. That is, the mass storage device 2407 may include a computer-readable medium (not shown) such as a hard disk or Compact disk Read Only Memory (CD-ROM) drive.

Computer-readable media may include computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash Memory or other Solid State Memory technology, CD-ROM, Digital Versatile Disks (DVD), or Solid State Drives (SSD), other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage, or other magnetic storage devices. The Random Access Memory may include a resistive Random Access Memory (ReRAM) and a Dynamic Random Access Memory (DRAM). Of course, those skilled in the art will appreciate that computer storage media is not limited to the foregoing. The system memory 2404 and mass storage device 2407 described above may be collectively referred to as memory.

The server 2400 may also operate as a remote computer connected to a network through a network, such as the internet, according to various embodiments of the present application. That is, the server 2400 may be connected to the network 2412 through the network interface unit 2411 coupled to the system bus 2405, or may be connected to another type of network or remote computer system (not shown) using the network interface unit 2411.

The memory further includes one or more programs, and the one or more programs are stored in the memory and configured to be executed by the CPU.

In an alternative embodiment, a computer device is provided, which includes a processor and a memory, wherein at least one instruction, at least one program, a set of codes, or a set of instructions is stored in the memory, and the at least one instruction, at least one program, set of codes, or set of instructions is loaded and executed by the processor to implement the step generation method for a system use case as described above.

In an alternative embodiment, a computer-readable storage medium is provided, in which at least one instruction, at least one program, code set, or instruction set is stored, and the at least one instruction, at least one program, code set, or instruction set is loaded and executed by a processor to implement the method for generating system use cases as described above.

Optionally, the computer-readable storage medium may include: a Read Only Memory (ROM), a Random Access Memory (RAM), a Solid State Drive (SSD), or an optical disc. The Random Access Memory may include a resistive Random Access Memory (ReRAM) and a Dynamic Random Access Memory (DRAM). The above-mentioned serial numbers of the embodiments of the present application are for description only and do not represent the merits of the embodiments.

Embodiments of the present application also provide a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. The computer instructions are read from the computer readable storage medium by a processor of a computer device, and the processor executes the computer instructions to cause the computer device to perform the method for generating system use cases as described above.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The above description is intended to be exemplary only, and not to limit the present application, and any modifications, equivalents, improvements, etc. made within the spirit and scope of the present application are intended to be included therein.

Claims

1. A method for generating a system case, the method comprising:

in response to receiving the adding operation on the step adding control, acquiring a target step template corresponding to the step type of the current action execution step from at least two types of preset step templates, wherein the target step template comprises the step sequence number of the current action execution step and the step description of the action execution step;

editing the step description to obtain an edited step description;

and generating the action execution step in the system case according to the step sequence number and the edited step description.

2. The method of claim 1, wherein the editing interface comprises a generated action execution step;

the step of generating the action execution step according to the step sequence number and the edited step description comprises the following steps:

acquiring a first step number corresponding to the generated action execution step, wherein the generated action execution step is one step before the action execution step;

generating a second step sequence number in the target step template according to the first step sequence number;

and generating the action execution step according to the second step serial number and the edited step description.

3. The method of claim 1, wherein the editing interface comprises a generated action execution step;

the step of obtaining a target step template corresponding to the step type of the action execution step from at least two types of preset step templates in response to receiving the adding operation on the step adding control comprises the following steps:

in response to receiving a first selection operation on a step executed by the generated action, displaying the step adding control;

in response to receiving the add operation on the step add control, displaying a candidate step list, the candidate step list comprising at least two types of preset step templates;

and acquiring a target step template corresponding to the step type of the action execution step from the candidate step list.

4. The method according to claim 3, wherein the obtaining the target step template corresponding to the step type of the current action performing step from the candidate step list comprises:

responding to the received second selection operation on the candidate step list, and acquiring the step type of the action execution step;

and acquiring the target step template corresponding to the step type from a template database according to the step type.

5. The method according to any one of claims 1 to 4, wherein the editing interface does not include a generated action execution step;

the method further comprises the following steps:

responding to a received turn adding control on the editing interface, and acquiring a preset turn template corresponding to the system use case, wherein the preset turn template comprises preset step templates corresponding to n step types, the preset step templates corresponding to the n step types are arranged in sequence, and n is a positive integer;

and generating a round step sequence in the system use case according to the preset round template, wherein the round step sequence is used for expressing a group of step sequences corresponding to the step from the step of executing the action of the request type to the step of executing the action of the preset type in the system use case.

6. The method of any of claims 1 to 4, further comprising:

responding to the result difference of the action execution step in the execution process, and acquiring the expansion step type of the path expansion step;

obtaining a preset expansion template corresponding to the path expansion step according to the type of the expansion step;

generating the current extension path according to the preset extension template, wherein the current extension path comprises at least one turn step sequence, and the turn step sequence comprises at least one action execution step.

7. The method according to any one of claims 1 to 4, wherein the editing interface comprises a deletion control, and the action execution steps in the system use case correspond to step nodes;

the method further comprises the following steps:

responding to the received deletion operation on the deletion control, and acquiring a node identifier of a step node corresponding to the ith action execution step, wherein the ith action execution step corresponds to the deletion operation, and i is a positive integer;

adding the ith action execution step to a list to be deleted according to the node identification;

responding to the step node corresponding to the ith action execution step to correspond to a sub-step node, and adding the action execution step corresponding to the sub-step node to the list to be deleted;

repeating the step of adding the action execution step corresponding to the sub-step node to the list to be deleted until all the step nodes in the system case are traversed;

and deleting the step nodes in the list to be deleted.

8. The method according to any one of claims 1 to 4, wherein the editing interface comprises a folding control and a generated action execution step, and the generated action execution step corresponds to a step node;

the method further comprises the following steps:

in response to receiving the folding operation on the folding control and the node state of the step node corresponding to the generated action execution step being an unfolded state, switching the node state of the step node to a folded state;

in response to the step node corresponding to a sub-step node, switching a node state of the sub-step node to the folded state;

repeating the step of switching the node state of the sub-step node into the folded state until all the step nodes in the system use case are traversed;

and folding and displaying the generated action in the editing interface according to the folding state.

9. The method of claim 8, further comprising:

in response to receiving the unfolding operation on the folding control and the node state of the step node corresponding to the generated action execution step being a folded state, switching the node state of the step node to an unfolded state;

and expanding and displaying the generated action in the editing interface according to the expansion state.

10. An apparatus for generating system use cases, the apparatus comprising:

11. A computer device comprising a processor and a memory, said memory having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, said at least one instruction, said at least one program, said set of codes, or said set of instructions being loaded and executed by said processor to implement a method of step generation for a system use case according to any one of claims 1 to 9.

12. A computer-readable storage medium, having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, which is loaded and executed by a processor to implement the method for generating system use cases according to any one of claims 1 to 9.