Automatic execution device, automatic execution method

Abstract

To efficiently verify previously created operation definition data.SOLUTION: An automatic execution device operates a component which operates by reading a parameter and previously created operation definition data. The automatic execution device comprises a scenario data acquisition unit which reads scenario data in which the parameter inputted to the component is defined, a parameter determination unit which determines the parameter inputted to the component based on the scenario data, and a scenario execution unit which inputs the parameter determined by the parameter determination unit based on the scenario data to the component.SELECTED DRAWING: Figure 1

Description

Technical Field

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

Background Art

[0002] Attempts have been widely made to streamline the operation verification of applications. Patent Document 1 discloses a device for executing a test program for verifying the operation of a predetermined device, which includes an operation recording unit that detects a data input operation on the predetermined device and records a function corresponding to the data input operation in an operation content file in which functions to be set in the test program are recorded, and an interface for acquiring input data to the predetermined device corresponding to the data input operation; a program generation unit that generates a test program for reproducing a series of operations performed on the predetermined device by setting program codes according to the functions 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 the input data to the function.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the invention described in Patent Document 1, it is not possible to efficiently verify operation definition data created in advance.

Means for Solving the Problems

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

Advantages of the Invention

[0006] According to the present invention, pre-created operation definition data can be efficiently verified.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Embodiments for Carrying out the Invention

[0008] - First Embodiment - Hereinafter, with reference to FIGS. 1 to 6, the first embodiment of the automatic execution device will be described.

[0009] FIG. 1 is a functional configuration diagram of the automatic execution device 100 in the first embodiment. The automatic execution device 100 includes 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 the present embodiment, a person who gives an operation command to the automatic execution device 100 is called a "user".

[0010] 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 the user conveys command contents to the automatic execution device 100. The display device 902 is, for example, a liquid crystal display, and the automatic execution device 100 conveys a processing result to the user.

[0011] Scenario data 210 is a collection of multiple "scenarios" that define a series of inputs to component 300. Among 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 component 300 reads. 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 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 interpretation of the SQL statement, etc. is performed by the scenario execution unit 104 or component 300, and the database 240 may be the data itself without a computing function.

[0012] The input unit 101 reads the user's command 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's command and outputs it to the parameter determination unit 103 and the scenario execution unit 104. The output unit 105 outputs the calculation result of the component 300 to the display device 902.

[0013] Component 300 is a collection of programs having specific functions. In the present embodiment, component 300 includes a first component 310 and a second component 320. At least one of the first component 310 and the second component 320 reads the operation definition data 220 when executing the process. Also, component 300 writes the processing result to the database 240.

[0014] Figure 2 is a hardware configuration diagram of the automatic execution device 100. The automatic execution device 100 includes 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 rewritable storage device, and an input / output device 44 connected to a user interface. By expanding and executing the program stored in the ROM 42 in the RAM 43 by the CPU 41, a scenario data acquisition unit 102, a parameter determination unit 103, a scenario execution unit 104, and a component 300 are realized.

[0015] The automatic execution device 100 may be realized by an FPGA (Field Programmable Gate Array) which is a rewritable logic circuit or an ASIC (Application Specific Integrated Circuit) which is an application-specific integrated circuit, instead of the combination of the CPU 41, the ROM 42, and the RAM 43. Further, the automatic execution device 100 may be realized by a combination of different configurations, for example, a combination of the CPU 41, the ROM 42, the RAM 43, and the FPGA, instead of the combination of the CPU 41, the ROM 42, and the RAM 43.

[0016] The input / output device 44 is an interface with 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, for example, a receptacle corresponding to a universal serial bus and a processing board, and a display control device connected to the display device 902. The input / output device 44 realizes an input unit 101 and an output unit 105.

[0017] FIG. 3 is a diagram showing an example of scenario data 210. The scenario data 210 is composed of a plurality of records, and each record has fields of 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 for identifying 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 to which a parameter is input. The parameter type 215 is the type of the parameter input to the component 300. The input information 216 is the information input as a parameter to the component 300.

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

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

[0020] FIG. 5 is a diagram showing an example of the operation of the first component 310. However, FIG. 5 is only shown for convenience of explanation, and the screen display is not an essential configuration in this embodiment. In the example shown in FIG. 5, the first component 310 receives a product name and a production deadline, performs calculations, and outputs a plan number. On the first input screen 951 shown at the top of FIG. 5, "ABCD" is entered for "Product Name" and "2022 / 07 / 20" is entered for "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.

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

[0022] 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 the input fields using image matching processing or coordinate information on the screen, and press the "Register" button in the lower right corner to send the necessary information to the first component 310. Also, the scenario execution unit 104 may generate information such as an XML file generated when the "Register" button is pressed on the first input screen 951 and output it to the first component 310 on its own.

[0023] FIG. 6 is a diagram showing an operation example of the second component 320. However, FIG. 6 is only shown for convenience of explanation, and screen display is not an essential configuration in this embodiment. In the example shown in FIG. 6, the second component 320 receives a deadline and a plan number, performs calculations, and outputs the scheduled execution date and the device usage time to the database 240. In the second input screen 953 shown at the top of FIG. 6, "2022 / 07 / 20" is entered for "Deadline" and "P0123" is entered for "Plan Number". Therefore, a set of parameter name "A-2" and value "2022 / 07 / 20" and a set of parameter name "X1" and value "P0123" are input to the second component 320.

[0024] 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 coordinate information on the screen, and press the "Register" button in the lower right corner to send the necessary information to the second component 320. Also, the scenario execution unit 104 may generate information such as an XML file generated when the "Register" button is pressed on the second input screen 953 and output it to the second component 320 on its own.

[0025] The second component 320 calculates the usage plan of the manufacturing equipment, that is, the time period during which each device is occupied, with reference to the operation definition data 220 and the database 240, so that the production can be completed by "2022 / 07 / 20" when the plan number "P0123" expires, and outputs it to the database 240. The second component 320 may output to the display device 902 via the output unit 105 the determined scheduled execution date "2022 / 07 / 15" and the usage time of each device, together with the input plan number, as in the second output screen 954 shown at the bottom of FIG. 6.

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

[0027] According to the first embodiment described above, the following operational effects can be obtained. (1) The automatic execution device 100 operates the component 300 that reads the parameters and the pre-created operation definition data 220. The automatic execution device 100 includes a scenario data acquisition unit 102 that reads the scenario data 210 in which the parameters input to the component are defined, a parameter determination unit 103 that determines the parameters 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 to the component 300 based on the scenario data 210. Therefore, the automatic execution device 100 can operate the component 300 that reads the operation definition data 220 based on the pre-created scenario data 210, so that the pre-created operation definition data 220 can be efficiently verified.

[0028] If the automatic execution device 100 is not used, the user has to input data one by one to the component 300, and it is complicated to operate the component 300. However, by using the automatic execution device 100, the component 300 can be easily operated, so the user only needs to judge the appropriateness of the processing result of the component 300. Therefore, by using the automatic execution device 100, the efficiency of verifying the operation definition data 220 is improved.

[0029] (2) The scenario data 210 includes a plurality of processes with a defined input order. Specifically, as shown in FIG. 3, the same scenario code 211 includes a plurality of processes with different execution order 212 values. The component 300 stores the calculation result with the execution order 212 of "1" in the database 240. The scenario data 210 includes, as input information 216 for the process with the execution order 212 of "2", the calculation result with the execution order 212 of "1" stored in the database 240, specifically, the execution result of the query "Select X1 From BBB Where product name = ABCD". Therefore, the automatic execution device 100 can input the value output by the component 300 to the component 300, in addition to the predefined fixed values.

[0030] (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.

[0031] (4) The scenario data 210 includes the values of parameters that are fixed values like the first record in FIG. 3. The parameter determination unit 103 uses the values of the parameters included in the scenario data 210 for input to the component 300.

[0032] (Modification Example 1) The functions and configurations of the above-described automatic execution device 100 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.

[0033] (Modification 2) The type of the 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 may be used. Furthermore, the database 240 may combine a plurality of types of databases.

[0034] (Modification 3) In the above-described first embodiment, the component 300 includes two configurations, i.e., the first component 310 and the second component 320. However, the component 300 may include three or more configurations or may be composed of only one configuration.

[0035] - Second Embodiment - With reference to FIGS. 7 to 9, a second embodiment of the automatic execution device will be described. In the following description, the same reference numerals are given to the same components as those in the first embodiment, and the differences will be mainly described. Points not particularly described are the same as those in the first embodiment. In this embodiment, it is mainly different from the first embodiment in that the automatic execution device itself verifies the output of the component 300.

[0036] FIG. 7 is a functional configuration diagram of the automatic execution device 100A in the second embodiment. The automatic execution device 100A includes all the configurations 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 is realized by the CPU 41 expanding and executing a program stored in the ROM 42 in the RAM 43, similar to the parameter determination unit 103 and the scenario execution unit 104. The evaluation data 250 is created in advance by the user and stored in the storage device 200.

[0037] FIG. 8 is a diagram showing an example of the evaluation data 250. The evaluation data 250 is composed of a plurality of records, and each record has fields of a scenario code 251, an evaluation order 252, and an evaluation query 253. The scenario code 251 is an identifier for identifying a scenario and is the same as the scenario code 211 in FIG. 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.

[0038] When the execution of the scenario by the scenario execution unit 104 is completed, 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 check of the component 300 itself has been completed 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.

[0039] The processing of the evaluation unit 106 will be specifically described with reference to FIG. 8. When all the executions in which the scenario code 251 by the scenario execution unit 104 is "C123" are completed, the evaluation unit 106 reads the first to third lines in the evaluation data 250 in which the scenario code 251 is "C123" and performs the following processing. That is, the evaluation unit 106 executes the evaluation query according to the evaluation order and reads the information stored in the database 240. The evaluation unit 106 evaluates that the verification is successful if there is at least one piece of data for each executed evaluation query, and evaluates that the verification has failed if there is an evaluation query with 0 pieces of data. The evaluation unit 106 outputs this evaluation result to the display device 902 via the output unit 105.

[0040] Note that the evaluation unit 106 may use the string itself described in the evaluation data 250 as the evaluation query, or may use information obtained by other means in combination as the evaluation query. For example, as in the fifth record of FIG. 8, the pre-query may be included in the evaluation query 253, and the result of the pre-query may be used as a query. In this example, the result obtained by executing the query "Select X1 From BBB Where product name = ABCD" is used as "PlanNum" and used in the query. For example, when the execution result of "Select X1 From BBB Where product name = ABCD" is "P765", the query becomes "Select DDD From EEE Where plan number = P765".

[0041] FIG. 9 is a diagram showing an example of the evaluation result by the evaluation unit 106 output to the display device 902. The success example screen 961 shown at the upper part of FIG. 9 is an output example when it is determined that the verification by the evaluation unit 106 is successful. The failure example screen 962 shown at the lower part of FIG. 9 is an output example when it is determined that the verification by the evaluation unit 106 is successful. As shown in FIG. 9, when the verification is successful, the evaluation unit 106 indicates to that effect, and when the verification fails, the problem location is indicated. In the example shown in FIG. 9, it is shown that the verification failed in "2" and "3" in the evaluation order.

[0042] According to the second embodiment described above, the following operational effects can be obtained. (5) The automatic execution device 100A includes an evaluation unit 106 that evaluates the propriety of the operation definition data 220 based on the output of the component 300. Therefore, the user does not need to evaluate the calculation result of the component 300 by himself / herself, and can easily test the operation definition data 220.

[0043] (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 propriety of the operation definition data 220 based on the execution result of the query.

[0044] In each of the above-described embodiments and modifications, the configuration of the functional blocks is merely an example. Some of the functional configurations shown as separate functional blocks may be integrated, or the configuration represented by one functional block diagram may be divided into two or more functions. Also, a part of the functions of each functional block may be provided by other functional blocks.

[0045] In each of the above-described embodiments and modifications, the program is assumed to be stored in the ROM 42, but the program may be stored in a non-illustrated non-volatile storage device. Also, the automatic execution device 100 may include an input / output interface (not shown), and when necessary, the program may be read from another device via the input / output interface and a medium that can be used by the automatic execution device 100. Here, the medium refers to, for example, a storage medium detachable from the input / output interface, or a communication medium, that is, a network such as wired, wireless, or optical, or a carrier wave or digital signal propagating through the network. Also, part or all of the functions realized by the program may be realized by a hardware circuit or an FPGA.

[0046] Each of the above-described embodiments and modifications may be combined. Although various embodiments and modifications have been described above, the present invention is not limited to these contents. Other aspects conceivable within the scope of the technical idea of the present invention are also included in the scope of the present invention.

Explanation of Reference Numerals

[0047] 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

1. An automatic execution device that operates a component that reads parameters and pre-created operation definition data and operates, A scenario data acquisition unit that reads scenario data in which the parameters input to the component are defined, A parameter determination unit that determines the parameters input to the component based on the scenario data, A scenario execution unit that inputs the parameters determined by the parameter determination unit to the component based on the scenario data, and includes, The operation definition data is information indicating the use of the device in the manufacture of the product, The scenario data is information regarding the parameters input to the component, and includes at least information on the order in which the parameters are input, An automatic execution device further comprising an output unit that provides the output of the component or the calculation result using the output of the component to the user.

2. In the automatic execution device according to claim 1, The scenario data includes a plurality of processes in which the input order is determined, The component stores the calculation result of the first process in the database as the first process result, The scenario data includes information indicating the first process result stored in the database as the parameter for the second process after the first process. An automatic execution device.

3. In the automatic execution device according to claim 2, The scenario data includes an SQL statement for acquiring the first process result stored in the database, The parameter determination unit acquires the first process result from the database using the SQL statement. An automatic execution device.

4. In the automatic execution device according to claim 1, The scenario data includes the values of the parameters, The parameter determination unit uses the values of the parameters included in the scenario data. An automatic execution device.

5. In the automatic execution device according to claim 1, Further comprising an evaluation unit that evaluates the appropriateness of the operation definition data based on the output of the component, The output unit outputs the evaluation result of the evaluation unit. An automatic execution device.

6. In the automatic execution device according to claim 5, The component stores the calculation result in the database, The evaluation unit is an automatic execution device that reads evaluation data including a query that is a query to the database, and evaluates the appropriateness of the operation definition data based on the execution result of the query.

7. An automatic execution method executed by an automatic execution device that operates a component that reads parameters and operation definition data created in advance, the method comprising: a scenario data acquisition step of reading scenario data in which the parameters input to the component are defined; a parameter determination step of determining the parameters input to the component based on the scenario data; a scenario execution step of inputting the parameters determined in the parameter determination step to the component based on the scenario data, wherein the operation definition data is information indicating the use of a device in the manufacture of a product; the scenario data is information regarding the parameters input to the component, and includes at least information on the order in which the parameters are input; and an automatic execution method further including a provision step of providing the user with the output of the component or the calculation result using the output of the component.

Images