JP7709403B2 - Automatic execution device and automatic execution method - Google Patents

Description

The present invention relates to an automatic execution device and an automatic execution method.

Attempts to reduce the labor required for verifying the operation of applications are being widely undertaken. Patent Document 1 discloses an operation verification device that executes a test program for verifying the operation of a specified device, and is characterized by having an operation recording unit that detects a data input operation for the specified device and records a function that corresponds to the data input operation and has an interface for acquiring input data for the specified device in an operation content file in which a function to be set in the test program is recorded, a program generation unit that generates a test program for reproducing a series of operations executed for the specified device by setting program code according to the function recorded in the operation content file, and a program execution unit that executes the test program by acquiring input data from an input data file different from the operation content file and passing it to the function.

JP 2010-237841 A

The invention described in Patent Document 1 does not allow for efficient verification of pre-created operational definition data.

An automatic execution device according to a first aspect of the present invention is an automatic execution device that operates a component that reads parameters and previously created operation definition data, and comprises a scenario data acquisition unit that reads scenario data in which the parameters to be input to the component are defined, a parameter determination unit that determines the parameters to be input to the component based on the scenario data, and a scenario execution unit that inputs the parameters determined by the parameter determination unit based on the scenario data to the component, wherein the operation definition data is information indicating the use of an apparatus in the manufacture of a product, and the scenario data is information regarding the parameters to be input to the component and includes at least information on the order in which the parameters are to be input, and further comprises a provision unit that provides a user with the output of the component or a calculation result using the output of the component .
An automatic execution method according to a second aspect of the present invention is an automatic execution method executed by an automatic execution device that operates a component by reading parameters and previously created operation definition data, and includes a scenario data acquisition step of reading scenario data in which the parameters to be input to the component are defined, a parameter determination step of determining the parameters to be input to the component based on the scenario data, and a scenario execution step of inputting the parameters determined by the parameter determination step based on the scenario data to the component , wherein the operation definition data is information indicating the use of an apparatus in the manufacture of a product, and the scenario data is information regarding the parameters to be input to the component and includes at least information on the order in which the parameters are to be input, and further includes a providing step of providing to a user the output of the component or the result of a calculation using the output of the component .

According to the present invention, pre-created operational definition data can be efficiently verified.

Functional block diagram of an automatic execution device according to a first embodiment Hardware configuration diagram of the automatic execution device FIG. 1 shows an example of scenario data. A diagram showing an example of operation definition data FIG. 13 is a diagram showing an example of the operation of the first component; FIG. 13 is a diagram showing an example of the operation of the second component; Functional block diagram of an automatic execution device according to a second embodiment FIG. 1 is a diagram showing an example of evaluation data. FIG. 13 is a diagram showing an example of an evaluation result by an evaluation unit.

-First embodiment-
A first embodiment of an automatic execution device will be described below with reference to FIGS.

Figure 1 is a functional configuration diagram of an automatic execution device 100 in the first embodiment. The automatic execution device 100 comprises an input unit 101, a scenario data acquisition unit 102, a parameter determination unit 103, a scenario execution unit 104, an output unit 105, a storage device 200, and a component 300. The storage device 200 stores scenario data 210, operation definition data 220, and a database 240. In this embodiment, a person who commands the automatic execution device 100 to perform an operation is called a "user."

The automatic execution device 100 is connected to an input device 901 and a display device 902. The input device 901 is, for example, a keyboard or a mouse, and is used by the user to transmit commands to the automatic execution device 100. The display device 902 is, for example, a liquid crystal display, and is used by the automatic execution device 100 to convey the results of processing to the user.

The scenario data 210 is a collection of multiple "scenarios," which are definitions of a series of inputs to the component 300. Of the scenario data 210, the scenario specified by the user is executed by the scenario execution unit 104. The operation definition data 220 is data that is read by the component 300. The scenario data 210 and the operation definition data 220 are created in advance by the user. The database 240 is a data storage location where the component 300 writes the execution results. The database 240 is, for example, a relational database, and returns data corresponding to the transmitted SQL statement. The scenario execution unit 104 or the component 300 interprets the SQL statement, and the database 240 may be data itself without any calculation functions.

The input unit 101 reads user instructions input to the input device 901. The scenario data acquisition unit 102 reads a specific scenario from the scenario data 210 based on the user instructions and outputs it to the parameter determination unit 103 and the scenario execution unit 104. The output unit 105 outputs the calculation results of the component 300 to the display device 902.

Component 300 is a collection of programs having specific functions, and in this embodiment, component 300 includes a first component 310 and a second component 320. At least one of first component 310 and second component 320 reads operation definition data 220 when executing processing. Component 300 also writes the processing results to database 240.

Figure 2 is a hardware configuration diagram of the automatic execution device 100. The automatic execution device 100 comprises a CPU 41, which is a central processing unit, a ROM 42, which is a read-only storage device, a RAM 43, which is a readable and writable storage device, and an input/output device 44 connected to a user interface. The CPU 41 deploys a program stored in the ROM 42 into the RAM 43 and executes it, thereby realizing a scenario data acquisition unit 102, a parameter determination unit 103, a scenario execution unit 104, and a component 300.

The automatic execution device 100 may be realized by a field programmable gate array (FPGA), which is a rewritable logic circuit, or an application specific integrated circuit (ASIC), which is an integrated circuit for a specific application, instead of the combination of the CPU 41, ROM 42, and RAM 43. The automatic execution device 100 may also be realized by a combination of different configurations, for example, a combination of the CPU 41, ROM 42, RAM 43, and an FPGA, instead of the combination of the CPU 41, ROM 42, and RAM 43.

The input/output device 44 is an interface between the input device 901 and the display device 902. The input/output device 44 is, for example, an input interface connected to the input device 901, such as a receptacle and processing board compatible with a universal serial bus, and a display control device connected to the display device 902. The input/output device 44 realizes the input unit 101 and the output unit 105.

Figure 3 is a diagram showing an example of scenario data 210. The scenario data 210 is composed of multiple records, and each record has fields for a scenario code 211, an execution order 212, a component name 213, a parameter name 214, a parameter type 215, and input information 216. The scenario code 211 is an identifier that identifies a scenario. The execution order 212 indicates the order of execution in the same scenario. The component name 213 is the name of the component for which a parameter is to be input. The parameter type 215 is the type of parameter to be input to the component 300. The input information 216 is information to be input as a parameter to the component 300.

In the example shown in FIG. 3, there are three records with scenario code 211 "C123", two of which are used for the first execution because their execution order 212 is "1", and the remaining one record is used for the next execution. In execution order "1", "ABCD" is entered into the column with parameter name 214 "A-1", and the result of the function "date(TODAY, "+ 3M", "yyyy/mm/dd")", that is, the date three months after the execution date, is entered in a specified format into the column with parameter name 214 "A-2". For example, if the execution date is April 20, 2022, "2022/07/20" is entered. In execution order "2", the SQL statement "Select AAA From BBB Where CC=X1" is entered into the database 240, and the output of the database 240 is entered into the second component 320.

Figure 4 is a diagram showing an example of operation definition data 220. Operation definition data 220 is information used by component 300, and is used, for example, by second component 320 for calculations. Operation definition data 220 is composed of multiple records, and each record has fields for product name 221, device used 222, parameter name 224, and parameter value 225. Operation definition data 220 indicates, for example, that a device indicated by device used 222 is used in the manufacture of a product indicated by product name 221. Furthermore, operation definition data 220 indicates that the value of parameter value 225 is set for the parameter indicated by parameter name 224 for the device indicated by device used 222.

Figure 5 is a diagram showing an example of the operation of the first component 310. However, Figure 5 is merely illustrated for convenience of explanation, and screen display is not a required configuration in this embodiment. In the example shown in Figure 5, the first component 310 accepts the product name and production deadline, performs calculations, and outputs a plan number. In the first input screen 951 shown in the upper part of Figure 5, "ABCD" is entered in "Product Name" and "2022/07/20" is entered in "Deadline". Therefore, a set of parameter name "A-1" and value "ABCD", and a set of parameter name "A-2" and value "2022/07/20" are input to the first component 310.

The first component 310 determines the value of "P0123" as a consecutive number of the existing plan number, for example, and records this plan number together with the input product name and deadline in a new record in the database 240. At this time, the first component 310 stores the plan number in the database 240 as the value of the parameter "X1". The first component 310 may output the determined value of the plan number "P0123" to the display device 902 via the output unit 105 together with the input values of "ABCD" and "2022/07/20", as in the first output screen 952 shown in the lower part of FIG. 5.

When the first component 310 displays the first input screen 951 as shown in FIG. 5, the scenario execution unit 104 may input parameters into an input field using image matching processing or on-screen coordinate information, and then press the "Register" button at the bottom right to send the necessary information to the first component 310. The scenario execution unit 104 may also generate information generated when the "Register" button is pressed on the first input screen 951, such as an XML file, and output it to the first component 310.

Figure 6 is a diagram showing an example of the operation of the second component 320. However, Figure 6 is also shown merely for convenience of explanation, and screen display is not a required configuration in this embodiment. In the example shown in Figure 6, the second component 320 accepts a deadline and a plan number, performs calculations, and outputs the scheduled execution date and the usage time of the equipment to the database 240. In the second input screen 953 shown in the upper part of Figure 6, "2022/07/20" is entered in "Deadline" and "P0123" is entered in "Plan number". Therefore, a set of the parameter name "A-2" and the value "2022/07/20", and a set of the parameter name "X1" and the value "P0123" are input to the second component 320.

When the second component 320 displays the second input screen 953 as shown in FIG. 6, the scenario execution unit 104 may input parameters into the input fields using image matching processing or on-screen coordinate information, and then press the "Register" button at the bottom right to send the necessary information to the second component 320. The scenario execution unit 104 may also generate information generated when the "Register" button is pressed on the second input screen 953, such as an XML file, and output it to the second component 320.

The second component 320 refers to the operation definition data 220 and the database 240, calculates a manufacturing equipment usage plan, i.e., the time period during which each piece of equipment will be occupied, so that plan number "P0123" can be manufactured by the deadline of "2022/07/20", and outputs the plan to the database 240. The second component 320 may output the determined scheduled execution date "2022/07/15" and the usage time of each piece of equipment to the display device 902 via the output unit 105, together with the input plan number, as in the second output screen 954 shown in the lower part of FIG. 6.

The user may confirm that the processing by component 300 has been performed appropriately by visually checking the output of second component 320 displayed on display device 902. The user may also confirm that the processing by component 300 has been performed appropriately by checking the data stored in database 240 using means not shown.

According to the above-described first embodiment, the following advantageous effects can be obtained.
(1) The automatic execution device 100 operates a component 300 that operates by reading parameters and pre-created operation definition data 220. The automatic execution device 100 includes a scenario data acquisition unit 102 that reads scenario data 210 in which parameters to be input to the component are defined, a parameter determination unit 103 that determines parameters to be input to the component 300 based on the scenario data 210, and a scenario execution unit 104 that inputs the parameters determined by the parameter determination unit 103 based on the scenario data 210 to the component 300. Therefore, the automatic execution device 100 can operate the component 300 that operates by reading the operation definition data 220 based on the pre-created scenario data 210, and therefore can efficiently verify the pre-created operation definition data 220.

If the automatic execution device 100 were not used, the user would have to input information into the component 300 one by one, making it cumbersome to operate the component 300. However, by using the automatic execution device 100, the component 300 can be easily operated, and the user only needs to determine the appropriateness of the processing results of the component 300. Therefore, by using the automatic execution device 100, the efficiency of verifying the operation definition data 220 is improved.

(2) The scenario data 210 includes multiple processes with a set input order. Specifically, as shown in FIG. 3, multiple processes with different values for the execution order 212 are included for the same scenario code 211. The component 300 stores the calculation result for the execution order 212 of "1" in the database 240. The scenario data 210 includes the calculation result for the execution order 212 of "1" stored in the database 240 as input information 216 for the process with the execution order 212 of "2", specifically, the execution result of the query "Select X1 From BBB Where Product name=ABCD". Therefore, the automatic execution device 100 can input to the component 300 not only predetermined fixed values but also values output by the component 300.

(3) The scenario data 210 includes an SQL statement for obtaining the calculation result of the first process stored in the database 240, for example, "Select X1 From BBB Where Product Name = ABCD." The parameter determination unit 103 obtains the calculation result from the database 240 using the SQL statement.

(4) The scenario data 210 includes parameter values that are fixed values, such as the first record in FIG. 3. The parameter determination unit 103 uses the parameter values included in the scenario data 210 as input to the component 300.

(Variation 1)
The functions and configuration of the automatic execution device 100 described above may be realized by a plurality of hardware devices. For example, the storage device 200 and the component 300 may be realized by hardware devices different from the input unit 101, the scenario data acquisition unit 102, the parameter determination unit 103, the scenario execution unit 104, and the output unit 105.

(Variation 2)
The type of database 240 is not limited to a relational database. Various known database formats can be applied to the database 240, and any of a hierarchical type, a network type, and NoSQL can be used. Furthermore, the database 240 may be a combination of multiple types of databases.

(Variation 3)
In the first embodiment described above, the component 300 includes two components, the first component 310 and the second component 320. However, the component 300 may include three or more components, or may be composed of only one component.

--Second embodiment--
A second embodiment of the automatic execution device will be described with reference to Figures 7 to 9. In the following description, the same components as in the first embodiment are denoted by the same reference numerals, and differences will be mainly described. Points that are not specifically described are the same as in the first embodiment. This embodiment differs from the first embodiment mainly in that the automatic execution device verifies the output of the component 300 by itself.

Figure 7 is a functional configuration diagram of the automatic execution device 100A in the second embodiment. The automatic execution device 100A includes all of the configuration of the automatic execution device 100 in the first embodiment, and further includes an evaluation unit 106 and evaluation data 250. The evaluation unit 106, like the parameter determination unit 103 and scenario execution unit 104, is realized by the CPU 41 expanding a program stored in the ROM 42 into the RAM 43 and executing it. The evaluation data 250 is created in advance by the user and stored in the storage device 200.

Figure 8 is a diagram showing an example of evaluation data 250. The evaluation data 250 is composed of multiple records, and each record has fields for a scenario code 251, an evaluation order 252, and an evaluation query 253. The scenario code 251 is an identifier that identifies a scenario and is similar to the scenario code 211 in Figure 3. The evaluation order 252 indicates the order in which evaluations are performed in the same scenario. The evaluation query 253 is a query to be executed against the database 240.

When the scenario execution unit 104 completes execution of the scenario, the evaluation unit 106 reads the evaluation data 250 and evaluates whether the processing by the component 300 was performed as intended. However, since the operation of the component 300 itself has been checked in advance, the evaluation by the evaluation unit 106 is an evaluation of whether the operation definition data 220 read by the component 300 was appropriate.

The processing of the evaluation unit 106 will be described in detail with reference to FIG. 8. When the scenario execution unit 104 has completed the execution of all scenarios with the scenario code 251 of "C123", the evaluation unit 106 reads the first to third lines in the evaluation data 250 with the scenario code 251 of "C123", and performs the next processing. That is, the evaluation unit 106 executes evaluation queries according to the evaluation order, and reads the information stored in the database 240. The evaluation unit 106 evaluates that the verification was successful if there is one or more pieces of data for each evaluation query executed, and evaluates that the verification was unsuccessful if there is even one evaluation query with zero pieces of data. The evaluation unit 106 outputs the evaluation result to the display device 902 via the output unit 105.

The evaluation unit 106 may use the character string written in the evaluation data 250 as the evaluation query itself, or may combine information obtained by other means to create the evaluation query. For example, as in the fifth record in FIG. 8, the evaluation query 253 may include a pre-query, and the result of the pre-query may be used in the query. In this example, the result obtained by executing the query "Select X1 From BBB Where Product Name=ABCD" is set as "PlanNum" and used in the query. For example, if the execution result of "Select X1 From BBB Where Product Name=ABCD" is "P765", the query will be "Select DDD From EEE Where Plan Number=P765".

Figure 9 is a diagram showing an example of the evaluation results by the evaluation unit 106 output to the display device 902. A success example screen 961 shown in the upper part of Figure 9 is an example of output when the evaluation unit 106 judges that the verification is successful. A failure example screen 962 shown in the lower part of Figure 9 is an example of output when the evaluation unit 106 judges that the verification is successful. As shown in Figure 9, the evaluation unit 106 clearly indicates that the verification is successful, and clearly indicates the problem area when the verification is unsuccessful. The example shown in Figure 9 shows that the verification failed for "2" and "3" in the evaluation order.

According to the above-described second embodiment, the following advantageous effects can be obtained.
(5) The automatic execution device 100A includes an evaluation unit 106 that evaluates the appropriateness of the operation definition data 220 based on the output of the component 300. Therefore, the user does not need to evaluate the calculation results of the component 300 himself, and can easily test the operation definition data 220.

(6) The component 300 stores the calculation result in the database 240. The evaluation unit 106 reads the evaluation data 250 including the evaluation query 253, which is a query to the database 240, and evaluates the appropriateness of the operation definition data 220 based on the query execution result.

In each of the above-described embodiments and variations, the functional block configurations are merely examples. Some functional configurations shown as separate functional blocks may be configured together, or a configuration shown in a single functional block diagram may be divided into two or more functions. In addition, some of the functions of each functional block may be provided by other functional blocks.

In the above-mentioned embodiments and variants, the program is stored in ROM 42, but the program may be stored in a non-volatile storage device (not shown). Furthermore, the automatic execution device 100 may be provided with an input/output interface (not shown), and the program may be read from another device when necessary via the input/output interface and a medium available to the automatic execution device 100. Here, the medium refers to, for example, a storage medium that is detachable from the input/output interface, or a communication medium, i.e., a network such as a wired, wireless, or optical network, or a carrier wave or digital signal that propagates through the network. Furthermore, some or all of the functions realized by the program may be realized by a hardware circuit or an FPGA.

The above-mentioned embodiments and modifications may be combined with each other. Although various embodiments and modifications have been described above, the present invention is not limited to these. Other aspects that are conceivable within the scope of the technical concept of the present invention are also included within the scope of the present invention.

Reference Signs List 100, 100A: Automatic execution device 102: Scenario data acquisition unit 103: Parameter determination unit 104: Scenario execution unit 106: Evaluation unit 210: Scenario data 220: Operation definition data 240: Database 250: Evaluation data 300: Component 310: First component 320: Second component 450: Evaluation data

Claims (7)

An automatic execution device that reads parameters and pre-created operation definition data to operate a component,
a scenario data acquisition unit that reads scenario data in which the parameters to be input to the components are defined;
a parameter determination unit that determines the parameters to be input to the components based on the scenario data;
a scenario execution unit that inputs the parameters determined by the parameter determination unit based on the scenario data to the component ,
The operation definition data is information indicating use of an apparatus in manufacturing a product;
the scenario data is information regarding the parameters to be input to the components, and includes at least information regarding the order in which the parameters are to be input;
The automatic execution device further comprises an output unit that provides a user with an output of the component or a result of a calculation using the output of the component . 2. The automatic execution device according to claim 1,
The scenario data includes a plurality of processes whose input order is determined,
The component stores a calculation result of the first processing in a database as a first processing result,
The scenario data includes information indicating the result of the first processing stored in the database as the parameter for a second processing subsequent to the first processing. 3. The automatic execution device according to claim 2,
the scenario data includes an SQL statement for acquiring the first processing result stored in the database,
The parameter determination unit obtains the first processing result from the database using the SQL statement. 2. The automatic execution device according to claim 1,
the scenario data includes values of the parameters;
The parameter determination unit uses the parameter value contained in the scenario data. 2. The automatic execution device according to claim 1,
An evaluation unit that evaluates the appropriateness of the operation definition data based on an output of the component ,
The output unit outputs the evaluation result of the evaluation unit . 6. The automatic execution device according to claim 5,
The component stores the calculation results in a database;
The evaluation unit reads evaluation data including a query that is an inquiry to the database, and evaluates the appropriateness of the operation definition data based on a result of executing the query. An automatic execution method executed by an automatic execution device that reads parameters and pre-created operation definition data to operate a component, the method comprising:
a scenario data acquisition step of reading scenario data in which the parameters to be input to the components are defined;
a parameter determination step of determining the parameters to be input to the components based on the scenario data;
a scenario execution step of inputting the parameters determined by the parameter determination step based on the scenario data to the components ;
The operation definition data is information indicating use of an apparatus in manufacturing a product;
the scenario data is information regarding the parameters to be input to the components, and includes at least information regarding the order in which the parameters are to be input;
The automatic execution method further includes a providing step of providing to a user an output of the component or a result of a calculation using the output of the component .