JP2022108058A - Scenario generation device, scenario generation system, scenario generation method and program - Google Patents

Abstract

To support creation of an RPA scenario based on a business analysis result.SOLUTION: A scenario generation device includes: an acquisition unit and a scenario generation unit. The acquisition unit acquires operation procedure data in which operation data items including execution order information indicating an execution order of operations and node names being names of nodes representing operations by a user interface are arranged. The scenario generation unit generates a scenario file in which a scenario expressed by arranging nodes corresponding to the operation data items included in the operation procedure data and provided with the node names included in the corresponding operation data items in order of the execution order information is described using a description format that can be executed by a scenario execution device.SELECTED DRAWING: Figure 3

Description

The present invention relates to a scenario generation device, a scenario generation system, a scenario generation method, a program, and operation procedure data.

Automation tools such as RPA (Robotic Process Automation) make it possible to automatically execute routine work that has been done manually using an information processing device such as a PC (Personal Computer). For example, a scenario describing a work procedure is created (see, for example, Patent Document 1), and a PC executes the scenario to reproduce the work previously performed manually (see, for example, Patent Document 2). RPA can also reduce time costs, human costs, and work errors. A scenario describes a procedure for automatically operating an application and information for the operation.

On the other hand, a BPR (Business Process Reengineering) tool is a tool that supports business reform. BPR collects and analyzes information on business activities and specifies actions that lead to business improvement. With the spread of RPA in society, recent BPR tools are becoming equipped with a function for extracting tasks that can be converted into RPA (see, for example, Non-Patent Document 1). A BPM (Business Process Management) tool is a general term for tools for integrally managing business processes and business systems. BPM tools are also beginning to come equipped with a function to clarify process changes related to business improvement and a function to replace business with RPA.

Japanese Patent No. 5026451 Japanese Patent No. 4883638

MasterScope IT Process Operations Operation Improvement Support Software, [online], NEC Corporation, [searched on December 10, 2020], Internet <https://jpn.nec.com/websam/itprocessoperations/index.html>

As described above, BPR tools and BPM tools are becoming equipped with the function of proposing business improvement by replacing business with RPA. However, RPA scenarios for causing PCs to execute tasks to be replaced have been created manually. Therefore, in some cases, the time and human costs required for replacement with RPA increased.

In view of the above circumstances, the present invention aims to provide a scenario generation device, a scenario generation system, a scenario generation method, a program, and operation procedure data that can support creation of an RPA scenario based on business analysis results. .

According to one aspect of the present invention, an acquisition unit that acquires operation procedure data in which operation data including execution order information indicating an execution order of operations and node names that are names of nodes representing operations by a user interface are arranged; A scenario executing device, in which the nodes corresponding to the operation data included in the operation procedure data and to which the node names included in the operation data are assigned are arranged in the order of the execution order information. and a scenario generation unit that generates a scenario file described using a description format executable in .

One aspect of the present invention is the scenario generation device described above, wherein the operation data includes an event indicating a type of the operation, and the scenario generation unit generates the node information according to the event included in the operation data. determine the type of

One aspect of the present invention is the above-described scenario generation device, wherein the operation data includes operation target information indicating a target of operation represented by the event, and operation data when the scenario execution device executes the operation represented by the event. Detailed information indicating one or both of additional information to be used is further included, and the scenario generation unit determines the type of the node according to a combination of the event and the detailed information included in the operation data.

One aspect of the present invention is the scenario generation device described above, wherein the scenario generation unit sets information obtained from the detailed information in property information added to the node and representing settings related to the node.

One aspect of the present invention is the scenario generation device described above, further comprising a scenario display unit that displays symbols representing nodes generated corresponding to the operation data and symbols representing the execution order of the nodes. .

One aspect of the present invention is the scenario generation device described above, wherein the operation data includes supplementary information that is not used for executing the operation represented by the operation data, and the scenario display unit corresponds to the operation data. The supplementary information included in the operation data is added to the symbol representing the node generated by the operation data.

One aspect of the present invention is the scenario generation device described above, wherein the execution order information represents a hierarchical execution order, and the scenario display unit corresponds to the operation data having the same execution order in the upper hierarchy. The symbol representing the node generated by the above is displayed within the symbol of the node representing the upper hierarchy.

An aspect of the present invention is the scenario generation device described above, wherein, when the operation data includes information indicating a group, the scenario display unit displays nodes generated corresponding to the operation data. Symbols are displayed including symbols representing nodes generated corresponding to the operation data in the lower hierarchy of the operation data.

According to one aspect of the present invention, an acquisition unit that acquires operation procedure data in which operation data including execution order information indicating an execution order of operations and node names that are names of nodes representing operations by a user interface are arranged; A scenario executing device, in which the nodes corresponding to the operation data included in the operation procedure data and to which the node names included in the operation data are assigned are arranged in the order of the execution order information. and a scenario generation unit that generates a scenario file described using a description format that can be executed in.

According to one aspect of the present invention, an acquisition step of acquiring operation procedure data in which operation data including execution order information indicating an execution order of operations and node names that are names of nodes representing operations by a user interface are arranged; A scenario executing device, in which the nodes corresponding to the operation data included in the operation procedure data and to which the node names included in the operation data are assigned are arranged in the order of the execution order information. and a scenario generation step of generating a scenario file described using a description format executable in .

One aspect of the present invention is a program for causing a computer to function as the scenario generation device described above.

One aspect of the present invention includes execution order information indicating the execution order of operations, a node name that is the name of a node representing an operation through a user interface, supplementary information that is not used for executing the operation, and a type of the operation. , operation target information indicating the target of the operation, and additional information used when executing the operation are arranged in a first direction, and the operation data are arranged in a second direction. It is operation procedure data arranged in one or more directions.

One aspect of the present invention is the operation procedure data described above, wherein each of the execution order information, the node name, the supplementary information, the event, the operation target information, and the additional information is identified. The information identifier is arbitrarily selected from one or more predetermined information identifiers.

According to the present invention, it is possible to support creation of an RPA scenario based on business analysis results.

1 is a diagram for explaining an overview of an RPA system according to one embodiment of the present invention; FIG. It is a figure which shows the example of a scenario display by the same embodiment. 3 is a functional block diagram of the scenario generation device according to the same embodiment; FIG. 3 is a functional block diagram of the scenario execution device according to the same embodiment; FIG. It is a figure which shows the example of the operation procedure data by the same embodiment. It is a flow diagram showing processing of the RPA system according to the same embodiment. It is a figure which shows the operation procedure data edit screen by the same embodiment. FIG. 5 is a flowchart showing scenario file generation processing by the scenario generation device according to the embodiment; It is a figure which shows the example of the scenario by the same embodiment. FIG. 7 is a flowchart showing scenario display screen generation processing by the scenario execution device according to the embodiment; FIG. 5 is a diagram showing a display example of a scenario file according to the same embodiment; It is a figure which shows the example of a display of the property setting screen by the same embodiment.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a diagram for explaining an overview of an RPA system 100 according to one embodiment of the present invention. The RPA system 100 is an example of a scenario generation system. The RPA system 100 has a scenario generation device 1 and a scenario execution device 5 . The scenario generation device 1 generates an RPA scenario. RPA is an example of an automation tool. A scenario is represented by arranging nodes representing operations performed by the user interface for functions executed by the scenario execution device 5 in the order in which the nodes are executed. A function that is a target of an operation represented by a node is, for example, an OS (Operation System) or a function realized by an application, and performs processing according to an operation performed through a user interface. Note that the scenario generation device 1 and the scenario execution device 5 may be an integrated device.

The scenario generation device 1 acquires operation procedure data in which operations to be performed on the scenario execution device 5 are described in a tabular format in order of execution. The operating procedure data may be created by, for example, a BPR tool or a BPM tool, or may be created manually by the user. The scenario generation device 1 converts the acquired operation procedure data into a scenario file. A scenario file is data describing an RPA scenario in a description format that can be executed by the scenario execution device 5 . The scenario execution device 5 executes the scenario described in the scenario file generated by the scenario generation device 1 . If you want to add missing information in the operating procedure data or execute the scenario under different conditions than the conditions referenced when the BPR tool or BPM tool generates the operating procedure data, the scenario file The user manually edits the scenario described in .

FIG. 2 is a diagram showing an example of scenario display by the scenario execution device 5. As shown in FIG. A scenario indicates nodes and the order in which the nodes are to be executed. The nodes are indicated by node symbols P1 and P2, and the order of execution of the nodes is indicated by an arrow Q. FIG. A node symbol P1 is a node symbol representing an operation performed by the user interface. A node symbol P2 is a symbol of a node representing a group. Node symbol P2 includes node symbols P1 of one or more nodes belonging to the group. If there is no node belonging to the group, the node symbol P1 is not included in the node symbol P2. An arrow Q is a symbol representing the execution order of the nodes represented by the symbols P1 and P2 connected to the arrow Q. FIG. That is, after the nodes represented by the node symbols P1 and P2 at the root of the arrow Q are executed, the nodes represented by the node symbols P1 and P2 at the tip of the arrow Q are executed. Execution of the node represented by the node symbol P2 means that all nodes represented by the node symbol P1 included in the node symbol P2 are executed. The node symbol Ps is a node symbol representing the start of the scenario, and the node symbol Pe is a node symbol representing the end of the scenario.

Property information is added to each node. The property information indicates settings related to the node. When an instruction to display property information is input, the scenario generation device 1 displays a screen G for displaying properties. Also, supplementary information may be added to the node. Supplementary information is information that is not used to execute the scenario. The supplementary information includes sticky note information displayed in association with the node symbols P1 and P2, and comment information set in the property information.

FIG. 3 is a functional block diagram of the scenario generation device 1. As shown in FIG. In FIG. 3, only functional blocks related to this embodiment are extracted and shown. The scenario generation device 1 is realized by, for example, a computer device such as a personal computer. The scenario generation device 1 has an input unit 11 , a display unit 12 , a storage unit 13 and a processing unit 14 . The input unit 11 is a user interface operated by the user when inputting user instructions to the scenario generation device 1 . The input unit 11 is configured using existing input devices such as a keyboard, pointing device (mouse, tablet, etc.), buttons, touch panel, and the like. The display unit 12 displays data. The display unit 12 is an image display device such as a CRT (Cathode Ray Tube) display, a liquid crystal display, an organic EL (Electro Luminescence) display, or the like.

The storage unit 13 stores various types of information including information used for processing by the processing unit 14 . The storage unit 13 stores operation procedure data and scenario files.

Operation procedure data is data in which one or more pieces of operation data are arranged. One piece of operation data corresponds to an operation of giving one instruction to the functions of the OS and applications of the scenario execution device 5 . Also, one piece of operation data corresponds to one node in the scenario. The operation data includes execution order information and node name information. The execution order information indicates the execution order of operations. The order of execution may be hierarchical. The node name information indicates the name of the node corresponding to the operation data. Operation data may further include event information and detailed information. The event information indicates the type of operation. The detailed information includes operation target information, additional information, and supplementary information. The operation target information indicates the target of the operation represented by the event. The additional information is information used when the scenario execution device 5 executes the operation indicated by the event. Supplementary information is information that is not used to execute an operation, and is supplementary information regarding an operation or a node.

A scenario file is a file that describes a scenario. A scenario file contains multiple node information. The node information includes execution order information, node type, property information, and tag information. The execution order information indicates the order in which nodes are executed. The node type indicates the type of operation represented by the node. Property information includes node name information, comment information, and various parameters. A parameter is information used when the scenario execution device 5 executes an operation represented by a node type.

The processing unit 14 is realized by recording a program for realizing the functions of the processing unit 14 in a computer-readable recording medium, and causing the computer system to read and execute the program recorded in the recording medium. be. The "computer system" here includes hardware such as a CPU (central processing unit), OS, and peripheral devices.

The processing unit 14 includes an acquisition unit 141 , a data editing unit 142 and a scenario generation unit 143 . The acquisition unit 141 acquires operation procedure data and writes it to the storage unit 13 . The data editing section 142 edits the operating procedure data stored in the storage section 13 according to the input from the input section 11 . The data editing unit 142 writes the edited operating procedure data to the storage unit 13 .

The scenario generation unit 143 generates a scenario file in which node information generated based on each piece of operation data included in the operation procedure data is arranged. A scenario file is a file that describes a scenario using a description format that can be executed by the scenario execution device 5 . The scenario generation unit 143 sets the node name and execution order information included in the operation data as node information. Furthermore, the scenario generation unit 143 determines the node type according to the event information included in the operation data or according to the combination of the event information and at least part of the detailed information, and sets it in the node information. The scenario generation unit 143 also sets information obtained from the detailed information of the operation data as property information included in the node information. That is, the scenario generation unit 143 determines the types of parameters used for property information according to the node types. The scenario generation unit 143 sets information obtained from the detailed information to the parameter of the property information based on the mapping rule between the type of parameter used in the property information and the detailed information included in the operation data. Mapping rules are predetermined. The scenario generation unit 143 also sets the supplementary information included in the operation data to the tag information and property information of the node information.

FIG. 4 is a functional block diagram of the scenario execution device 5. As shown in FIG. In FIG. 4, only functional blocks related to this embodiment are extracted and shown. The scenario execution device 5 is implemented by, for example, a computer device such as a personal computer. The scenario execution device 5 has a storage section 51 , an input section 52 , a display section 53 and a processing section 54 .

The storage unit 51 stores scenario files generated by the scenario generation device 1 . The input unit 52 is a user interface operated by the user when inputting user instructions to the scenario execution device 5 . The input unit 52 is configured using existing input devices such as a keyboard, pointing device (mouse, tablet, etc.), buttons, touch panel, and the like. The display unit 53 displays data. The display unit 53 is an image display device such as a CRT display, liquid crystal display, or organic EL display.

The processing unit 54 is realized by recording a program for realizing the functions of the processing unit 54 in a computer-readable recording medium, and causing the computer system to read and execute the program recorded in the recording medium. . A "computer system" includes hardware such as a CPU, an OS, and peripheral devices.

The processing unit 54 includes a scenario editing unit 541 , a scenario execution unit 542 and a function X execution unit 543 .

The scenario editing unit 541 edits scenario files. The scenario editing section 541 also functions as a scenario display section that displays the scenario indicated by the scenario file on the display section 53 . The scenario editing unit 541 displays on the display unit 53 node symbols representing nodes corresponding to respective pieces of node information in the scenario file, and execution order symbols representing the execution order of the nodes represented by the node symbols. The scenario editing unit 541 displays the node name information set in the property information of the node information on the node symbol. If the node information includes tag information, the scenario editing unit 541 displays the node symbol in association with the tag information. Further, when the execution order information represents a hierarchical execution order, the scenario editing unit 541 inserts the node information of the child hierarchy included in the parent hierarchy into the node symbol corresponding to the node information of the parent hierarchy. Include and display the corresponding node symbols. The scenario editing unit 541 changes the scenario file displayed on the display unit 53 based on the information input by the user through the input unit 52 .

The scenario execution unit 542 reads out node information from the scenario file in order of execution, and controls the input unit 52 to perform operations indicated by the node information. The function X executing section 543 executes the function X according to the operation using the input section 52 . Function X is a function that can be used to execute a scenario and can be any function. Function X is optional, but examples include functions realized by applications such as spreadsheets, document editing, graphic drawing, web browsers, sending and receiving emails, and functions realized by the OS such as application startup and clipboard. . In FIG. 4, the function X executing section 543 (X=A, B, C) that executes the function X is described as a function A executing section 543a, a function B executing section 543b, and a function C executing section 543c.

The above-mentioned "computer-readable recording medium" storing the program of the processing unit 14 or the processing unit 54 includes portable media such as flexible discs, magneto-optical discs, ROMs, CD-ROMs, etc., and A storage device such as a hard disk that Furthermore, "computer-readable recording medium" means a medium that dynamically retains a program for a short period of time, like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. It may also include something that holds the program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in that case. Further, the program may be for realizing a part of the functions of the processing unit 14 or the processing unit 54, and the functions of the processing unit 14 or the processing unit 54 may be combined with a program already recorded in the computer system. It may be realized by a combination of

When the scenario generation device 1 is integrated with the scenario execution device 5, the storage unit 51, the input unit 52, and the display unit 53 correspond to the storage unit 13, the input unit 11, and the display unit 12, respectively. has the function of the processing unit 14 . Also, the processing unit 14 of the scenario generation device 1 may have the function of the scenario editing unit 541 of the scenario execution device 5 . In this case, the scenario executing device 5 may or may not have the scenario editing section 541 . A device different from the scenario generation device 1 and the scenario execution device 5 may have the scenario editing section 541 .

The scenario generation device 1 and the scenario execution device 5 may each be realized by a plurality of computer devices. In this case, each functional unit included in the scenario generation device 1 and each functional unit included in the scenario execution device 5 may be distributed and implemented in a plurality of computer devices. It is possible to arbitrarily decide which computer device implements each functional unit included in the scenario generation device 1 and each functional unit included in the scenario execution device 5 . Also, the same functional unit may be realized by a plurality of computer devices.

FIG. 5 is a diagram showing an example of operating procedure data. The operating procedure data is data that can be edited by, for example, a commonly used spreadsheet application. The operational procedure data includes a header row and one or more pieces of operational data. The header row indicates column names for identifying the types of information included in the operation data. One piece of operation data corresponds to one node in the scenario and is described in one line. The operation data are "No", "node name", "comment", "sticky note", "event", "application", "window title", "additional information 1" to "additional information N" (N is a positive number) as a column name. In FIG. 5, "additional information 3" to "additional information N" are omitted.

The information with the column name "No" is execution order information. The execution order information indicates a hierarchical execution order, and the numbers of each hierarchy are connected by "-". When M numbers (M is an integer of 2 or more) are combined with "-", the mth number (m is an integer of 1 or more and M or less) is the 1st to (m-1)th number of the hierarchy. Numbers represent the order of execution in groups with the same parent. For example, if "1", "1-1", and "1-2" are set in the execution order information for each of the three operation data, the operation data with the execution order information "1" is Operation data corresponding to a node and having execution order information "1-1" or "1-2" set corresponds to a child node of its parent node. After the child node of the execution order information "1-1", the child node of the execution order information "1-2" is executed.

The information of the column name "node name" is node name information. The node name information of operation data is mapped to the node name information of property information. The information with the column name “comment” is comment information. Comment information is one of supplementary information. The comment information of the operation data is mapped to the comment information of the property information. The information with the column name “sticky note” is sticky note information. Sticky note information is one type of supplementary information. Sticky note information is displayed in addition to the node symbol. The information of the column name "event" is event information. The event information indicates the type of group or operation. Operation types include, for example, activation, opening, clipboard, copy, paste, selection, and key input. If no value is set in the event information, it is assumed that the group is set. The information with the column name "application" is target application information. The target application information is operation target information when the operation target is an application. The information of the column name "window title" is the target window information. The target window information is the operation target information when the operation target is the display window. The information with the column name “additional information n” (n=1, 2, . . . N) is additional information used when executing the operation. Target application information, target window information, and additional information n are mapped to parameters of property information.

Predetermined (reserved) names are used as column names. The type of information set in each column of the operation data can be identified by the column name described in the header row. Therefore, arbitrarily change the description order of "No", "Node name", "Comment", "Sticky note", "Event", "Application", "Window title", "Additional information 1" to "Additional information N". It is possible. Alternatively, a predetermined alias column name may be used for the same information. For example, "node name", "name", "node-name", "name", etc. may be used as column names of the node name information. Also, "event", "event type", "operation type", "action", "event-type", "event", "action", etc. may be used as the column names of the event information. Therefore, it becomes possible for a user to select and use a column name that is easy for a user to understand individually from among a plurality of possible column names.

Further, the operating procedure data may include information on column names other than the predetermined column names. These information are not used for scenario generation. By enabling such information to be set, for example, information used by a BPR tool, a BPM tool, or a user but not used for scenario generation can be set in the operating procedure data.

FIG. 6 is a flow diagram showing the processing of the RPA system 100. As shown in FIG. First, the acquisition unit 141 of the scenario generation device 1 acquires operation procedure data (step S110). For example, the acquisition unit 141 may receive operation procedure data from an external device, or read the operation procedure data from a recording medium according to instructions input by the user through the input unit 11 . The acquisition unit 141 writes the acquired operation procedure data to the storage unit 13 .

When the user inputs an instruction to read operation procedure data through the input unit 11 , the data editing unit 142 reads out the instructed operation procedure data from the storage unit 13 and displays it on the display unit 12 . At this time, the data editing unit 142 may check the normality of each piece of operation data in the operation procedure data, extract the operation data determined to be normal, and display the operation data on the display unit 12 . The data editing unit 142 may also output a log of operation data determined to be in error. Items for checking the normality include, for example, whether essential information is set, whether multiple column names representing the same column type are included, whether the execution order indicated by the execution order information is consecutive, and whether each For example, are pre-approved characters used for the information? The data editing unit 142 edits the operating procedure data according to the information input by the user through the input unit 11 (step S120). The data editing unit 142 writes the edited operating procedure data to the storage unit 13 . Note that the scenario generation device 1 does not have to edit the operation procedure data.

When the user inputs a scenario generation instruction through the input unit 11 , the scenario generation unit 143 reads out the operation procedure data edited by the data editing unit 142 from the storage unit 13 . The scenario generator 143 generates a scenario file describing a scenario based on the read operation procedure data (step S130). Detailed processing of scenario file generation will be described later with reference to FIG. The scenario generation unit 143 writes the generated scenario file to the storage unit 13 . When correcting the scenario file, the scenario generation device 1 repeats the processing from step S120 for editing the operation procedure data according to the information input by the user. The scenario files stored in the storage unit 13 are output to the scenario execution device 5 . The output may be transmitted via a network or recorded on a recording medium readable by the scenario executing device 5 . The scenario execution device 5 acquires the scenario file generated by the scenario generation device 1 and stores it in the storage unit 51 .

When the user inputs a scenario display instruction through the input unit 52 of the scenario execution device 5, the scenario editing unit 541 reads the scenario file from the storage unit 51 and displays the scenario indicated by the scenario file on the display unit 53 (step S140). Detailed processing of the scenario display will be described later with reference to FIG. The scenario editing unit 541 edits the scenario according to the instructions input by the user through the input unit 52 (step S150). The scenario editing unit 541 creates a scenario file of the edited scenario and writes it to the storage unit 51 . Note that if editing the scenario is unnecessary, the scenario execution device 5 does not have to perform the process of step S150.

The user inputs the file name of the scenario file, the scenario execution instruction, and the scenario execution timing through the input unit 52 of the scenario execution device 5 . The scenario execution unit 542 reads the scenario file from the storage unit 51 at the scenario execution timing, and executes the scenario described in the read scenario file (step S160).

FIG. 7 is a diagram showing an operation procedure data editing screen. When the user sets the file name of the operating procedure data in the file name input field F1 using the input unit 11 of the scenario generation device 1 and selects the read button B1, the data editing unit 142 reads the operating procedure data with the specified file name. read out. The data editing unit 142 confirms the normality of each piece of operation data in the operation procedure data, and displays the operation data determined to be normal side by side in the data display area A1. The user selects a cell to be edited in the data display area A1 by using the input unit 11, and edits the selected cell, such as inputting or deleting information. When the user selects the save button B<b>2 using the input unit 11 , the data editing unit 142 stores the edited operating procedure data in the storage unit 13 . When the user selects the scenario generation button B3 using the input unit 11, the scenario generation unit 143 generates a scenario file using the edited operating procedure data.

FIG. 8 is a flowchart showing scenario file generation processing by the scenario generation device 1. As shown in FIG. FIG. 8 shows detailed processing of step S130 in FIG. First, the scenario generation unit 143 sets the initial value 1 to the variable i (step S210). The scenario generator 143 reads the i-th row of operation data from the operation procedure data (step S220). The read operation data of the i-th row is described as operation data (i). The scenario generation unit 143 determines whether or not the operation data (i) is a blank line (step S230). When the scenario generation unit 143 determines that the line is not a blank line, it determines whether or not the information of the required column is set in the operation data (i) (step S240). Information in the required columns is execution order information and node name information.

If the scenario generation unit 143 determines that the information in the required column is set (step S240: YES), it generates node information corresponding to the operation data (i) and adds it to the scenario file. Node information to be added corresponding to operation data (i) is described as additional node information (i). The scenario generation unit 143 reads the execution order information from the operation data (i) and sets it in the additional node information (i) (step S250).

The scenario generation unit 143 determines the node type according to the event included in the operation data (i) or the combination of the event and at least part of the detailed information (step S260). The scenario generation unit 143 sets the determined node type to the additional node information (i). The scenario generation unit 143 determines the types of parameters included in the property information based on the node types (step S270). All property information includes node name information and comment information.

The scenario generation unit 143 reads the node name information from the operation data (i) and sets it in the property information included in the additional node information (i) (step S280). Further, when additional information is set in the operation data (i), the scenario generation unit 143 sets the additional information in the additional node information (i) (step S290). That is, the scenario generation unit 143 sets the tag information to the additional node information (i) when the tag information is set to the operation data (i). Further, when comment information is set in operation data (i), scenario generation unit 143 sets comment information in property information included in additional node information (i).

The scenario generation unit 143 sets the parameter values obtained from the detailed information of the operation data (i) to each parameter of the property information included in the additional node information (i) (step S300). The mapping between the type of each parameter included in the property information and the detailed information of the operation data (i) is determined in advance according to the node type. Note that if information corresponding to the parameter of the property information is not set in the operation data (i), the scenario generation unit 143 sets no value to the parameter or sets it to blank. Operation data (i) may include information that is not mapped to parameters of property information.

If the scenario generation unit 143 determines that some or all of the information in the essential column is not set in the operation data (i) (step S240: NO), or after the process of step S300, the scenario generation unit 143 sets the variable i to 1. Add (step S310). The scenario generator 143 repeats the process from step S220. Then, when the scenario generation unit 143 determines that the operation data (i) is a blank line (step S230: YES), it generates a scenario file including the additional node information arranged in the execution order indicated by the execution order information (step S320).

Details of the processing of steps S260 and S270 in FIG. 8 will be described. The scenario generation unit 143 determines whether or not one or more of the event information setting contents, the target application information, the target window information, and the additional information 1 to N are set, or a combination of the setting contents. determines the node type. Scenario generation unit 143 determines whether or not target application information, target window information, and additional information 1 to additional information N can be obtained depending on the determined node type. . An example of this is described below.

If the event information of the operation data indicates a group, the scenario generation unit 143 determines that the node type is a group node. When the event information is a group, the scenario generation unit 143 determines that the target application information, the target window information, and additional information 1 to additional information N are not used. The scenario generation unit 143 determines to use property information that includes node name information and comment information but does not include parameters.

The scenario generation unit 143 determines that the node type is a start node when "start" is set in the event information. The activation node performs an operation of activating the execution file having the execution file name set in the additional information 1 using the arguments set after the additional information 2 . The scenario generation unit 143 determines to use the property information including parameters for setting the executable file name set in the additional information 1 and the arguments set in the additional information 2, additional information 3, . . . . Additional information 2 and subsequent information can be omitted.

The scenario generation unit 143 determines that the node type is an open node when "open" is set in the event information. The open node performs an operation to open the file with the file name set in the additional information 1 . The scenario generation unit 143 determines to use the property information including the parameter for setting the file name set in the additional information 1 .

The scenario generation unit 143 determines that the node type is a clipboard node when "clipboard" is set in the event information. The clipboard node is an operation to copy the character string set in the additional information 1 to the clipboard. The scenario generation unit 143 determines to use the property information including the parameter for setting the character string set in the additional information 1 .

When "copy" is set in the event information and application identification information of a specific application is set in the target application information, the scenario generation unit 143 determines that the node type is a script copy node. Application identification information is information that identifies an application. The script copy node performs an operation to copy information in the screen displayed on the display unit 53 by the function X execution unit 543 of the scenario execution device 5 that executes the application specified by the application identification information, using a script language or the like. . Additional information 1 to additional information n are set with information indicating the position of the object to be copied within the screen. For example, in the case of a spreadsheet application, additional information 1 indicates a file name, additional information 2 indicates a sheet name in the file, and additional information 3 indicates a cell position within the sheet. When additional information 1 to additional information n are omitted, the active position before the script copy node is inherited. The scenario generation unit 143 determines to use property information including each parameter for setting each value of the additional information 1 to n.

When "copy" is set in the event information and window identification information is set in the target window information, the scenario generation unit 143 determines that the node type is an emulation copy node. The emulation copy node performs a key operation for instructing copying by emulation for the window specified by the window identification information. The scenario generation unit 143 determines to use property information including parameters for setting the window identification information indicated by the target window information.

When "paste" is set in the event information and application identification information of a specific application is set in the target application information, the scenario generation unit 143 determines that the node type is a script paste node. The script paste node performs a paste operation using a script language or the like on the screen displayed on the display unit 53 by the function X execution unit 543 of the scenario execution device 5 that executes the application specified by the application identification information. . Additional information 1 to additional information n are set with information indicating the position to be pasted within the screen. For example, in the case of a spreadsheet application, this position is indicated in the same way as for the script copy node above. Scenario generator 143 determines to use property information including parameters for setting values of additional information 1 to additional information n.

When "paste" is set in the event information and window identification information is set in the target window information, the scenario generation unit 143 determines that the node type is an emulation paste node. The emulation paste node performs a key operation for instructing paste by emulation to the window specified by the window identification information. The scenario generation unit 143 determines to use property information including parameters for setting the window identification information indicated by the target window information.

The scenario generation unit 143 determines that the node type is a selected node when "selection" is set in the event information. A selection node performs an operation of selecting a specific position within a screen displayed on the display unit 53 by a specific application. Information indicating the position of the object to be selected within the screen is set in the additional information 1 to the additional information n. For example, in the case of a spreadsheet application, this position is indicated in the same way as for the script copy node above. Scenario generator 143 determines to use property information including parameters for setting values of additional information 1 to additional information n.

The scenario generation unit 143 determines that the node type is a key input node when "key input" is set in the event information. A key input node performs a key operation for inputting a designated key by emulation for a window specified by window identification information set in target window information. Scenario generator 143 determines that the input key is set to additional information 1 to additional information n. In the case of single key input, the key to be input is set in additional information 1, and in the case of compound key input, in addition to additional information 1, additional information 2 to additional information n are used. Scenario generator 143 determines to use property information including parameters for setting target window information, values of additional information 1 to additional information n, and input positions on the screen.

FIG. 9 is a diagram showing an example of a scenario generated based on the operating procedure data of FIG.
The scenario generator 143 sets the operation data in the first row of the operation procedure data as operation data (1). Since the execution order information (No) and the node name information are set in the operation data (1), the scenario generation unit 143 adds the additional node information (1) to the scenario file (step S240 in FIG. 8: YES). . The scenario generation unit 143 sets the execution order information (No) of the operation data (1) to the additional node information (1) (step S250 in FIG. 8). Since a group is set in the event information of operation data (1), the scenario generation unit 143 determines that the node type is a group node (step S260 in FIG. 8). The scenario generation unit 143 determines that the parameter is not included in the property information of the group node (step S270 in FIG. 8). The scenario generation unit 143 sets the node name information and comment information of the operation data (1) to the property information of the additional node information (1), and sets the tag information of the operation data (1) to the additional node information (1). (Steps S280 and S290 in FIG. 8).

Next, the scenario generation unit 143 sets the operation data in the second row of the operation procedure data as operation data (2). Since the execution order information (No) and the node name information are set in the operation data (2), the scenario generation unit 143 adds the additional node information (2) to the scenario file (step S240 in FIG. 8: YES). . The scenario generation unit 143 sets the execution order information (No) of the operation data (2) to the additional node information (2) (step S250 in FIG. 8). Since "key input" is set in the event information of operation data (2), the scenario generation unit 143 determines that the node type is a key input node (step S260 in FIG. 8). The scenario generation unit 143 determines that the property information of the key input node includes the parameters of the window identification name, the key operations 1, 2, 3, . The scenario generation unit 143 sets the node name information and comment information of the operation data (2) to the property information of the additional node information (2) (steps S280 and S290 in FIG. 8). The scenario generation unit 143 adds operation data (2) when the target window information (window title) of operation data (2) corresponds to the window identification name of the property information and a value is set only in additional information 1. According to the mapping rule that the information 1 corresponds to the key operations 1 and 2 of the property information, the setting contents of the operation data (2) are set as the values of each parameter of the property information (step S300 in FIG. 8). Specifically, based on the set value "Down" of the additional information 1 of the operation data (2), the scenario generation unit 143 sets the key operation 1 of the property information to "keyboard [Down] down" (press the "Down" key). "Keyboard [Down] up" (value indicating the operation of releasing the "Down" key) is set in key operation 2 of the property information.

Next, the scenario generation unit 143 sets the operation data in the third row of the operation procedure data as operation data (3). Since the execution order information (No) and the node name information are set in the operation data (3), the scenario generation unit 143 adds the additional node information (3) to the scenario file (step S240 in FIG. 8: YES). . The scenario generation unit 143 sets the execution order information (No) of the operation data (3) to the additional node information (3) (step S250 in FIG. 8). Since "copy" is set in the event information of operation data (3) and "spreadsheet application E" is set in the target application information (application), the scenario generation unit 143 determines that the node type is a script copy node. (step S260 in FIG. 8). The scenario generation unit 143 determines that the property information of the script copy node includes application, window identification name, file name, sheet, and cell parameters (step S270 in FIG. 8). The scenario generation unit 143 sets the node name information and comment information of the operation data (3) to the property information of the additional node information (3), and sets the tag information of the operation data (3) to the additional node information (3). (Steps S280 and S290 in FIG. 8). The scenario generation unit 143 converts the target application information (application), the target window information (window title), the additional information 1, the additional information 2, and the additional information 3 of the operation data (3) into the application of the property information, the window identification name, and the window identification name, respectively. The setting contents of the operation data (3) are set as the values of the parameters of the property information according to the mapping rule corresponding to the file name, sheet, and cell (step S300 in FIG. 8).

Next, the scenario generation unit 143 sets the operation data in the fourth row of the operation procedure data as operation data (4). Since the execution order information (No) and the node name information are set in the operation data (4), the scenario generation unit 143 adds the additional node information (4) to the scenario file (step S240 in FIG. 8: YES). . The scenario generation unit 143 sets the execution order information (No) of the operation data (4) to the additional node information (4) (step S250 in FIG. 8). Since a group is set in the event information of the operation data (4), the scenario generation unit 143 determines that the node type is a group node (step S260 in FIG. 8). The scenario generation unit 143 sets the node name information and comment information of the operation data (4) to the property information of the additional node information (4) (steps S280 and S290 in FIG. 8).

Next, the scenario generation unit 143 sets the operation data in the fifth row of the operation procedure data as operation data (5). Since the node name information is not set in the operation data (5), the scenario generation unit 143 determines not to generate node information (step S240 in FIG. 8: NO).

Next, the scenario generation unit 143 sets the operation data in the sixth row of the operation procedure data as operation data (6). Since the execution order information (No) and the node name information are set in the operation data (6), the scenario generation unit 143 adds the additional node information (6) to the scenario file (step S240 in FIG. 8: YES). . The scenario generation unit 143 sets the execution order information (No) of the operation data (6) to the additional node information (6) (step S250 in FIG. 8). Since "paste" is set in the event information of the operation data (6) and an application other than the specific "spreadsheet application E" is set in the target application information (application), the scenario generation unit 143 selects the node The type is determined as an emulation paste node (step S260 in FIG. 8). The scenario generation unit 143 determines that the property information of the emulation paste node includes the window identification name parameter (step S270 in FIG. 8). The scenario generation unit 143 sets the node name information and comment information of the operation data (6) to the property information of the additional node information (6) (steps S280 and S290 in FIG. 8). The scenario generation unit 143 sets the target window information (window title) of the operation data (6) as the parameter value of the window identification name of the property information (step S300 in FIG. 8).

The scenario generation unit 143 performs the same processing as described above on the operation data on and after the 7th row of the operation procedure data.

FIG. 10 is a flowchart showing scenario display screen generation processing by the scenario execution device 5. As shown in FIG. FIG. 10 shows the process of generating screen data displayed in step S140 of FIG. First, the scenario editing unit 541 arranges the symbol of the starting node at a predetermined position on the scenario display screen (step S410). The scenario editing unit 541 sets the initial value 1 to the variable j (step S420). The scenario editing unit 541 reads the j-th node information from the scenario (step S430). The scenario editing unit 541 determines whether node information has been read (step S440). When the scenario editing unit 541 determines that the node information has been read (step S440: YES), the process of step S450 is performed. The read j-th node information is described as display node information (j).

The scenario editing unit 541 reads the execution order information from the display node information (j) (step S450). The scenario editing unit 541 determines the end of the node symbol representing the layer one level higher than the layer indicated by the execution order information as the placement position (step S460). The scenario editing unit 541 arranges a node symbol displaying the node name information read from the property information included in the display node information (j) at the determined addition position on the scenario display screen (step S470). The scenario editing unit 541 uses a node symbol with a design corresponding to the node type set in the display node information (j). The added node symbol is described as an added symbol. If the tag information is set in the display node information (j), the scenario editing unit 541 associates the additional symbols with the tag information and arranges them on the scenario display screen (step S480).

The scenario editing unit 541 adds 1 to the variable j (step S490). The scenario editing unit 541 repeats the processing from step S430. If the scenario editing unit 541 determines that the node information has not been read (step S440: NO), the scenario editing unit 541 arranges the node symbol of the end node at the end of the scenario. An arrow display is arranged on the scenario display screen (step S500). The scenario editor 541 displays the generated scenario screen.

FIG. 11 is a diagram showing a display example of the scenario file shown in FIG. A scenario creation screen 600 shown in FIG. 11 has a scenario creation area 610 and a library display area 620 . A scenario creation area 610 is an area for designating the execution order of nodes. The library display area 620 is an area for displaying a list of nodes that can be used by user designation by node name. A node symbol corresponding to display node information (j) is described as a node symbol Pj.

The scenario editing unit 541 arranges the start node symbol Ps in front of the node symbol P-0 representing the node of the highest layer (step S410 in FIG. 10). The execution order information of display node information (1) is "1" and the node type is "group". The scenario editing unit 541 adds a group to the head of the node symbol P-0 because the layer immediately above the execution order information "1" is the highest layer and no node symbol has been placed in the highest layer. The node symbol P-1 to represent is placed (step S470 in FIG. 10). The scenario editing unit 541 displays the node name information set in the property information of the display node information (1) on the node symbol P-1, and displays the tag information set in the display node information (1) on the node symbol P-1. It is arranged in association with symbol P-1 (step S480 in FIG. 10).

The execution order information of display node information (2) is "1-1" and the node type is "key input". The scenario editing unit 541 selects the node symbol P- 1 has not yet been assigned a node symbol, the node symbol (2) representing the operation is placed at the beginning of the node symbol P-1 (step S470 in FIG. 10). The scenario editing unit 541 displays the node name information set in the property information of the display node information (2) on the node symbol P-2.

The execution order information of display node information (3) is "1-2", and the node type is "script copy". The scenario editing unit 541 selects the node symbol P- 1, a node symbol P-3 representing an operation is placed after the node symbol P-2 in the node symbol P-1 (step S470 in FIG. 10). The scenario editing unit 541 displays the node name information set in the property information of the display node information (3) on the node symbol P-3, and displays the sticky note information set in the display node information (3) on the node symbol P-3. It is arranged in association with symbol P-3 (step S480 in FIG. 10).

The execution order information of display node information (4) is "2" and the node type is "group". The scenario editing unit 541 determines that the layer immediately above the execution order information "2" is the highest layer, and the node symbol P-1 is placed at the node symbol P-0 of the highest layer. Next to the node symbol P-1 in P-1, the node symbol P-4 representing the group is arranged (step S470 in FIG. 10). The scenario editing unit 541 displays the node name information set in the property information of the display node information (4) on the node symbol P-4.

The execution order information of the display node information (5) is "2-2", and the node type is "emulation paste". The scenario editing unit 541 selects the node symbol P- 4 does not contain a node symbol yet, a node symbol P-5 representing an operation is arranged at the beginning of the node symbol P-4 (step S470 in FIG. 10). The scenario editing unit 541 displays the node name information set in the property information of the display node information (5) at the node symbol P-5.

The scenario editing unit 541 repeats the above processing. Then, when the scenario editing unit 541 determines that the node information has not been read (step S440 in FIG. 10: NO), it places the node symbol of the end node next to the node symbol P-0, and furthermore, arranges the node symbol P-0. An arrow display based on the execution order information is arranged on the scenario display screen (step S500 in FIG. 10). The scenario editor 541 displays the generated scenario screen.

When the user instructs to input a node property using the input unit 52 such as a mouse, the scenario editing unit 541 displays a property screen on the display unit 53 . For example, the property input instruction is an operation of double-clicking on the displayed node symbol.

FIG. 12 is a diagram showing a display example of the property screen. The property screen displays and inputs node name information, comment information, operation target information, various parameters, and the like. FIG. 12 shows a display example of the property screen 650 when the node type is key input. The scenario editing unit 541 displays the value set in the property information of the node information corresponding to the selected node symbol P-2 on the property screen 650 by default. 12, node name information is displayed in a display field 651, comment information is displayed in a display field 652, window identification names are displayed in a display field 653, and key operations 1, 2, 3, . . . are displayed in a display field 654. Is displayed. Although the display area 655 displays the value of the input position, the default value is displayed in FIG. 12 because no value is set for the input position of the property information.

The user inputs setting values to the property screen 650 using the input unit 52 as necessary. For example, when the user clicks a display window displayed on the display unit 53 after clicking the button 661 using the input unit 52, the content of the display field 653 is updated to the window identification name of the clicked display window. . Also, the user sets the keys and buttons to be input, the input position on the screen, etc. by selecting from the pull-down menu and inputting to the display field. When the user performs a save operation such as clicking an OK button using the input unit 52, the scenario editing unit 541 stores the setting value input on the property screen 650 in the property information of the node information corresponding to the selected node symbol. set.

When adding a node, the user selects the node name of the node to be added from the list of node names displayed in the library display area 620 using the input unit 52 such as the mouse, and adds the selected additional node to the scenario. Drag to creation area 610 . As a result, the scenario editing unit 541 additionally displays the symbol of the additional node at the drag end position in the scenario creation area 610 . In this way, a node can be added to the scenario file generated by the scenario generating device 1 based on the operating procedure data.

Also, when the user wants to add another scenario to the currently displayed scenario, the user inputs the scenario name of the other scenario to be added and the position of addition in the scenario displayed in the scenario creation area 610 using the input unit 52 . input. As a result, the scenario editing unit 541 adds the specified scenario to the additional position of the currently displayed scenario. Further, by saving a scenario file generated by the scenario generating device 1 based on the operation procedure data or a part of the scenario indicated by the scenario file as a scenario file, the saved scenario file can be generated. can be incorporated into other scenario files as subroutines.

According to the scenario generation device 1 described above, it is possible to automatically or semi-automatically generate a scenario using operation procedure data generated by a business analysis tool or a visualization tool. Semi-automatic scenario generation means that the scenario is generated to the extent that it is sufficient for the user to supplement some of the information, without the need for the user to generate the scenario from the beginning.

BPR tools and BPM tools are becoming equipped with the function of proposing work improvements to replace work to RPA, but RPA scenarios for work to be replaced have been created manually. Also, the description format of the business improvement proposal differs depending on the BPR tool. Therefore, by using the operation procedure data of the present embodiment, it is possible to support scenario generation for replacing conventionally manually performed tasks with RPA without relying on BPR tools or BPM tools. Therefore, it is possible to further reduce the human cost and time cost required for scenario creation of the RPA tool.

In addition, by making the operation procedure data in a data format that can be edited by a general spreadsheet application, even users without knowledge of scenario creation can easily edit the operation procedure data generated by BPR tools and BPM tools. Editable. Since the scenario generation device 1 generates a scenario from the edited operation procedure data, it is possible to further reduce the cost of creating the scenario.

Users of BPM tools and BPR tools specialize in business analysis, but in many cases they are unfamiliar with creating RPA scenarios. According to the present embodiment, the BPM tool or BPR tool generates operation procedure data as an analysis result, or the user of the BPM tool or BPR tool generates operation procedure data based on the analysis result. It is possible to create an RPA scenario from the operating procedure data and pass it to the scenario creator. Scenario creators can efficiently create scenarios based on business analysis results without having to create scenarios from the beginning.

In the title line of the operation procedure data, column names such as "node name" used in the RPA scenario can be changed to column names that are easy to understand even for users who do not have knowledge of RPA. Therefore, even a user who has no knowledge of RPA can easily edit the operation procedure data. In addition, since one line of operation procedure data corresponds to a set of an RPA node and a parameter to be set for the node, even users of BPM tools and BPR tools can easily understand the operation procedure data. Further, by hierarchizing the execution order information, it is possible to group related operations. Therefore, it becomes easy to grasp the flow of business as a whole. Also, in the operation procedure data, the grouped processes can be confirmed in detail. Also, by grouping a plurality of nodes for one task output from the BPM tool or BPR tool, it is easy to compare the task and the RPA scenario.

In addition, since a scenario node corresponds to one operation for the OS or application, scenarios can be created more easily than creating code in a programming language or script language. Also, since each line of the operating procedure data is converted into a node, mistakes in conversion into a scenario are less likely to occur. In addition, by using supplementary information such as tag information, it becomes easier to grasp whether a node in the scenario corresponds to any operation data in the operation procedure data. It is also useful for confirming the normality of the scenario and for changing the scenario.

In addition, although the case where one operation data corresponds to one operation has been described above, one operation data may correspond to a plurality of operations. Also, in the above description, a case where one piece of operation data corresponds to one node has been described, but one piece of operation data may correspond to a plurality of nodes.

In addition, it is also possible to create scenarios by dividing parts to be automated by operating procedure data into several functional units, and then link a plurality of scenarios. By using the scenario subroutine and the import function that incorporates other scenarios into the scenario being created, multiple scenarios can be linked, so large-scale processing can be assembled reliably.

According to the embodiments described above, the scenario generation device has the acquisition unit and the scenario generation unit. The acquisition unit acquires operation procedure data in which operation data including execution order information indicating an execution order of operations and node names that are names of nodes representing operations by the user interface are arranged. The scenario generation unit generates a scenario in which nodes corresponding to each operation data included in the operation procedure data and given node names included in the corresponding operation data are arranged in order of execution order information. A scenario file described using a description format that can be executed by an execution device is generated.

The operation data may include an event indicating the type of operation. The scenario generator determines the node type according to the event included in the operation data.

The operation data may further include detailed information indicating one or both of operation target information indicating the target of the operation represented by the event and additional information used when the scenario execution device executes the operation represented by the event. The scenario generator determines the node type according to the combination of the event and the detailed information included in the operation data.

The scenario generation unit may set information obtained from the detailed information in property information that is added to a node and represents settings related to the node.

The scenario generation device may further include a scenario display section. The scenario display unit is, for example, the scenario editing unit 541 of the embodiment. The scenario display section displays symbols representing nodes generated corresponding to operation data and symbols representing the execution order of the nodes.

Operational data may include supplemental information that is not used to perform the operation represented by the operational data. The scenario display section adds supplementary information included in the operation data to symbols representing nodes generated corresponding to the operation data, and displays the symbols.

The execution order information may represent a hierarchical execution order. The scenario display unit displays a symbol representing a node generated corresponding to the operation data having the same execution order in the upper hierarchy within the symbol of the node representing the upper hierarchy.

When the operation data includes information indicating a group, the scenario display section displays a symbol representing a node generated corresponding to the operation data, and a symbol generated corresponding to the operation data in the lower layer of the operation data. may include symbols representing nodes that

The operation procedure data includes execution order information indicating the execution order of operations, node names representing operations by the user interface, supplementary information that is not used for the execution of operations, and events indicating the types of operations. , one or more pieces of operation data arranged in a first direction in which fields for setting operation target information indicating an operation target and additional information used in executing the operation are arranged in a second direction. The data may be In the embodiment, the first direction is the horizontal direction and the second direction is the vertical direction, but the first direction may be the vertical direction and the second direction may be the horizontal direction. The operation procedure data may also include information identification names for identifying each of the execution order information, node name, supplementary information, event, operation target information, and additional information. The information identifier may be arbitrarily selected from one or more predetermined information identifiers.

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design and the like are included within the scope of the gist of the present invention.

Reference Signs List 1 scenario generation device 5 scenario execution device 11 input unit 12 display unit 13 storage unit 14 processing unit 51 storage unit 52 input unit 53 display unit 54 processing unit 100 RPA system 141 acquisition unit 142...Data editing unit 143...Scenario generating unit 541...Scenario editing unit 542...Scenario executing unit 543a...Function A executing unit 543b...Function B executing unit 543c...Function C executing unit

The present invention relates to a scenario generation device, a scenario generation system, a scenario generation method, and a program .

In view of the above circumstances, it is an object of the present invention to provide a scenario generation device, a scenario generation system, a scenario generation method, and a program capable of supporting creation of an RPA scenario based on business analysis results.

One aspect of the present invention includes execution order information indicating an execution order of operations, a node name that is a name of a node representing an operation through a user interface, an event that indicates the type of the operation, and an operation target that indicates the target of the operation. Operation procedure data in which one or more pieces of operation data in which fields for setting information and additional information used when the scenario execution device executes the operation are arranged in a first direction are arranged in a second direction. is displayed in a tabular format, and edits the operation procedure data according to an input user operation; and a node corresponding to each of the operation data included in the operation procedure data edited by the editing unit , Scenario generation for generating a scenario file describing a scenario in which the nodes to which the node names included in the operation data are assigned are arranged in the order of the execution order information using a description format executable by a scenario execution device. wherein the scenario generation unit is configured to generate the scenario according to the event included in the operation data, or the event included in the operation data and one or both of the operation target information and the additional information; A scenario generation device that determines the type of the node according to the combination, and sets information obtained from one or both of the operation target information and the additional information in property information that is added to the node and represents settings related to the node. is.

One aspect of the present invention includes execution order information indicating an execution order of operations, a node name that is a name of a node representing an operation through a user interface, an event that indicates the type of the operation, and an operation target that indicates the target of the operation. Operation procedure data in which one or more pieces of operation data in which fields for setting information and additional information used when the scenario execution device executes the operation are arranged in a first direction are arranged in a second direction. is displayed in a tabular format, and edits the operation procedure data according to an input user operation; and a node corresponding to each of the operation data included in the operation procedure data edited by the editing unit , Scenario generation for generating a scenario file describing a scenario in which the nodes to which the node names included in the operation data are assigned are arranged in the order of the execution order information using a description format executable by a scenario execution device. wherein the scenario generation unit is configured to generate the scenario according to the event included in the operation data, or the event included in the operation data and one or both of the operation target information and the additional information; A scenario generation system that determines the type of the node according to the combination, and sets information obtained from one or both of the operation target information and the additional information in property information that is added to the node and represents settings related to the node. is.

One aspect of the present invention is a scenario generation method executed by a scenario generation device, wherein an editing unit includes execution order information indicating the execution order of operations, a node name that is the name of a node representing an operation by a user interface, Columns for setting an event indicating the type of the operation, operation target information indicating the target of the operation, and additional information used when the scenario execution device executes the operation are arranged in a first direction. an editing step of displaying, in a tabular format, operation procedure data in which one or more of the operation data obtained are arranged in a second direction, and editing the operation procedure data in accordance with an input user operation; a scenario in which the nodes corresponding to each of the operation data included in the edited operation procedure data and to which the node names included in the operation data are assigned are arranged in order of the execution order information; and a scenario generation step of generating a scenario file described using a description format that can be executed by a scenario execution device , wherein the scenario generation unit responds to the event included in the operation data, or determining the type of the node according to a combination of the event included in the operation data and one or both of the operation target information and the additional information; The scenario generation method includes setting information obtained from one or both of the operation target information and the additional information .

Claims (13)

an acquisition unit that acquires operation procedure data in which operation data including execution order information indicating the execution order of operations and node names that are names of nodes representing operations by a user interface are arranged;
A scenario is executed by executing a scenario in which the nodes corresponding to the operation data included in the operation procedure data and to which the node names included in the operation data are assigned are arranged in order of the execution order information. a scenario generation unit that generates a scenario file described using a description format executable by the device;
A scenario generation device comprising: the operation data includes an event indicating a type of the operation;
wherein the scenario generation unit determines the type of the node according to the event included in the operation data;
The scenario generation device according to claim 1. The operation data further includes detailed information indicating one or both of operation target information indicating an operation target represented by the event and additional information used when the scenario execution device executes the operation represented by the event. ,
wherein the scenario generation unit determines the type of the node according to a combination of the event and the detailed information included in the operation data;
3. The scenario generation device according to claim 2. The scenario generation unit sets information obtained from the detailed information in property information added to the node and representing settings related to the node.
4. The scenario generation device according to claim 3. further comprising a scenario display unit that displays symbols representing nodes generated corresponding to the operation data and symbols representing the execution order of the nodes;
The scenario generation device according to any one of claims 1 to 4. the operation data includes supplementary information that is not used to execute the operation represented by the operation data;
The scenario display unit adds the supplementary information included in the operation data to the symbols representing the nodes generated corresponding to the operation data, and displays the symbols.
6. The scenario generation device according to claim 5. The execution order information represents a hierarchical execution order,
wherein the scenario display unit displays a symbol representing a node generated corresponding to the operation data having the same execution order in the upper hierarchy within the symbol of the node representing the upper hierarchy;
7. The scenario generation device according to claim 5 or 6. When the operation data includes information indicating a group, the scenario display unit causes a symbol representing a node generated corresponding to the operation data to correspond to the operation data in the lower hierarchy of the operation data. including symbols representing the nodes generated by
The scenario generation device according to claim 7. an acquisition unit that acquires operation procedure data in which operation data including execution order information indicating the execution order of operations and node names that are names of nodes representing operations by a user interface are arranged;
A scenario is executed by executing a scenario in which the nodes corresponding to the operation data included in the operation procedure data and to which the node names included in the operation data are assigned are arranged in order of the execution order information. a scenario generation unit that generates a scenario file described using a description format executable by the device;
scenario generation system. an acquisition step of acquiring operation procedure data in which operation data including execution order information indicating the execution order of operations and node names that are names of nodes representing operations by the user interface are arranged;
A scenario is executed by executing a scenario in which the nodes corresponding to the operation data included in the operation procedure data and to which the node names included in the operation data are assigned are arranged in order of the execution order information. a scenario generation step of generating a scenario file described using a description format executable by the device;
Scenario generation method with A program for causing a computer to function as the scenario generation device according to any one of claims 1 to 8. Execution order information indicating the execution order of operations, a node name that is the name of a node representing an operation by a user interface, supplementary information that is not used for execution of the operation, an event indicating the type of the operation, and the operation One or more pieces of operation data arranged in a first direction in which fields for setting operation object information indicating the object of the operation and additional information used in executing the operation are arranged in a second direction. Operating procedure data. including an information identification name for identifying each of the execution order information, the node name, the supplementary information, the event, the operation target information, and the additional information;
The information identifier is arbitrarily selected from one or more predetermined information identifiers,
Operation procedure data according to claim 12.

Images