WO2021214843A1 - Operation check assistance device, operation check assistance method, and operation check assistance program - Google Patents

Abstract

A program information acquisition unit (15) acquires an operation code, which is a source code of an operation program that reads an input value to operate. An inspection condition acquisition unit (16) acquires information regarding a target reaching part including a target reaching part of the operation code as an inspection condition. An inspection condition conversion unit (17) generates a determination formula for determining that the target reaching part included in the inspection condition acquired by the inspection condition acquisition unit is reached. An analysis unit (18) generates, using the determination formula generated by the inspection condition conversion unit, a generated value as the input value that is caused to reach the target reaching part.

Description

Operation check support device, operation check support method and operation check support program

This disclosure relates to an operation confirmation support device, an operation confirmation support method, and an operation confirmation support program.

During software development, the person in charge of checking the operation (hereinafter referred to as the person in charge) is inside the software that transitions according to the input value in order to check the operation of the software itself being developed or the operation of the device controlled by the software. The state may be transitioned to a specific state.
In such a case, the person in charge needs to determine the input value for transitioning the internal state of the software to a specific target state. Then, the person in charge confirms whether the internal state of the software can actually transition to a specific target state by inputting the determined input value into the software. Alternatively, the person in charge confirms whether the device controlled by the software can operate in response to the transition to the specific target state by realizing the transition to the specific target state.

As a specific example of such confirmation work at the time of software development, there is operation confirmation work of an embedded device such as an ECU (Electronic Control Unit) equipped with software. The software installed in the embedded device has an internal state that transitions by input to the software in order to realize complicated control, and the output of the software changes depending on the input and the internal state. In order to confirm the specific operation of such an embedded device, the person in charge may change the internal state of the software to a specific state. Therefore, the person in charge sets an internal state value representing the internal state of the software as a target as a value at which the internal state becomes a specific state based on the software specification information, and inputs it to the software retroactively from the set target. It is necessary to determine the input value to be input.

However, the person in charge of software development does not always know all the software specifications. In addition, even if the person in charge knows the software specifications, the person in charge must determine the input value to reach the target internal state value in consideration of the software specifications, which is necessary for operation check. It took a lot of man-hours to create the input value. In addition, the software installed in various systems or products has a large-scale complexity in software specifications by enhancing the functions in response to social demands. Along with this, the man-hours for the person in charge to manually create the input value are increasing.
In order to suppress the increase in man-hours related to creating input values in operation check during software development, the input values required for operation check are automatically calculated using formal verification technology that proves the properties of the system based on mathematics and logic. There is a method to generate with.

As an example of a method using such a formal verification technique, there is a method described in Patent Document 1. The method described in Patent Document 1 is a method of an inspection device that confirms the operation of a software operation program by using model checking, which is one of formal verification techniques. In the document, the inspection device is an input value sequence to the software or an input value sequence thereof, an internal state value of the software or an internal state value sequence to be a time series thereof, and an output value from the software or an output value to be a time series thereof. The inspection condition is the condition that the column must meet. Then, a SAT (Satisfiability Problem) solver is used to search for a solution of the input value string that satisfies the inspection condition, and if a solution of the input value string exists, the input value string, the internal state value string, and the output are the solutions. A method for outputting a value string is disclosed. The SAT solver is a known technique that, when a logical expression is acquired, searches for a solution whose true expression is true and outputs a solution that exists as a result of the search.

Japanese Unexamined Patent Publication No. 2019-083018

In the method of Patent Document 1, in order to obtain an input value for transitioning software to a specific target internal state, the person in charge needs to set an internal state value representing a specific target internal state as an inspection condition. .. That is, it is necessary for the person in charge to refer to the specification information about the internal state, select a specific target internal state as a setting target, and determine an internal state value representing the specific target internal state. .. Therefore, there is a problem that the man-hours for checking the operation increase due to the work of determining the internal state value.
In addition, it is necessary for the person in charge to manually create a logical expression in which the SAT solver can analyze the internal state value. Therefore, there is a problem that the man-hours for operation confirmation increase due to the work of creating a logical expression in which the SAT solver can analyze the internal state value.
In particular, in large-scale software and the like, the number of states that can be taken as internal states is large and complicated. In checking the operation of such software, it is difficult to select a specific internal state as a target, refer to specification information on the internal state, and determine an internal state value representing the specific internal state as the target. , The man-hours for operation check will increase significantly.

The main purpose of this disclosure is to reduce the man-hours for software operation check work.

The operation confirmation support device according to the present disclosure is
A program information acquisition unit that acquires the operation code, which is the source code of the operation program that operates by reading the input value,
An inspection condition acquisition unit that acquires information about a target arrival point including the target arrival point of the operation code as an inspection condition, and an inspection condition acquisition unit.
An inspection condition conversion unit that generates a determination formula for determining that the target reached point included in the inspection condition acquired by the inspection condition acquisition unit has been reached.
It is provided with an analysis unit that generates a generated value as the input value for reaching the target arrival point using the determination formula generated by the inspection condition conversion unit.

According to the present disclosure, in the operation confirmation work, the person in charge inputs the information about the target arrival point including the operation code and the target arrival point of the operation code, so that the analysis unit inputs the input value required for the operation confirmation work. Generate. Therefore, the man-hours for the software operation check work can be reduced.

The figure which shows the hardware configuration example of the operation confirmation support apparatus which concerns on Embodiment 1. FIG. The figure which shows the functional configuration example of the operation confirmation support apparatus which concerns on Embodiment 1. FIG. The flowchart which shows the processing operation of the operation confirmation support apparatus which concerns on Embodiment 1. The figure which shows the operation code which concerns on Embodiment 1. FIG. The figure which shows the marking method to the operation code which concerns on Embodiment 1. FIG. The figure which shows the inspection code which concerns on Embodiment 1. FIG. The figure which shows the input value which concerns on Embodiment 1 and the execution order of the confirmed software. The flowchart which shows the processing operation of the operation confirmation support apparatus which concerns on Embodiment 2. The figure which shows the operation code which concerns on Embodiment 2. The figure which shows the target arrival order conditional expression and the target arrival condition expression which concerns on Embodiment 2. The figure which shows the conditional inspection code which concerns on Embodiment 2. FIG. The figure which shows the functional configuration example of the operation confirmation support apparatus which concerns on Embodiment 3. FIG. The flowchart which shows the processing operation of the operation confirmation support apparatus which concerns on Embodiment 3. The figure which shows the operation code which concerns on Embodiment 3. The figure which shows the input value which concerns on Embodiment 3 and the execution order of the confirmed software.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In each figure, the same or corresponding parts are designated by the same reference numerals. In the description of the embodiment, the description will be omitted or simplified as appropriate for the same or corresponding parts.
The present disclosure is not limited to the embodiments described below, and various modifications can be made as necessary. For example, among the embodiments described below, two or more embodiments may be combined and implemented. Alternatively, of the embodiments described below, one embodiment or a combination of two or more embodiments may be partially implemented.
In the following description, the software whose operation is confirmed in the present disclosure is referred to as confirmed software. Then, the program of the confirmed software is shown as an operation program. In addition, the source code of the operation program is shown as the operation code.

Embodiment 1.
The present embodiment will be described with reference to FIGS. 1 to 7.
*** Explanation of configuration ***
A hardware configuration example of the operation confirmation support device 10 according to the present embodiment will be described with reference to FIG.
The operation confirmation support device 10 is a computer. The operation confirmation support device 10 includes a processor 11, and other hardware such as a memory 12, a communication device 13, and an input / output device 14. The processor 11 is connected to other hardware via a signal line and controls these other hardware.
The operation procedure of the operation confirmation support device 10 corresponds to the operation confirmation support method. Further, the program that realizes the operation of the operation confirmation support device 10 corresponds to the operation confirmation support program.

The processor 11 is an IC (Integrated Circuit) that performs processing. Specific examples of the processor 11 include a CPU (Central Processing Unit), a DSP (Digital Signal Processor), and the like.
The processor 11 executes a program that realizes the operation of the operation confirmation support device 10. The program that realizes the operation of the operation confirmation support device 10 is a program that realizes the functions of the program information acquisition unit 15, the inspection condition acquisition unit 16, the inspection condition conversion unit 17, the analysis unit 18, and the input value output unit 19, which will be described later. Is.

The memory 12 is a storage device. The memory 12 is, as a specific example, a RAM (Random Access Memory), a flash memory, or a combination thereof.
The memory 12 stores the program for realizing the operation of the operation confirmation support device 10, the operation code 30, and the specification information of the software to be confirmed. The software to be confirmed may be any kind of software, but in the present embodiment, the description will proceed assuming that it is embedded software.

The communication device 13 is an electronic circuit that executes information communication processing with a connection destination via a signal line. The communication device 13 includes a receiver that receives information input to the operation confirmation support device 10 and a transmitter that transmits information output from the operation confirmation support device 10. As a specific example, the communication device 13 is a communication chip or a NIC (Network Interface Card).

The input / output device 14 is an electronic circuit that executes information input / output processing. The input / output device 14 is connected to an input device used for input operation of input information input to the operation confirmation support device 10 or an external device such as a display for displaying output information output from the operation confirmation support device 10 on a screen. NS.
The input device is, for example, a mouse, a keyboard, a touch panel, or a combination of some or all of them. As a specific example, the display is an LCD (Liquid Crystal Display). The display may display the operation code 30 acquired by the program information acquisition unit 15 described later. Further, the display may display the input value output by the input value output unit 19 described later. The input value output by the input value output unit 19 is the same as the input value generated by the analysis unit 18 described later, and will be described below as the generated value 34.

The program that realizes the operation of the operation confirmation support device 10 is read from the memory 12 into the processor 11 and executed by the processor 11. In the memory 12, not only the program that realizes the operation of the operation confirmation support device 10 but also the OS (Operating System) is stored. The processor 11 executes a program that realizes the operation of the operation confirmation support device 10 while executing at least a part of the OS. A part or all of the program that realizes the operation of the operation confirmation support device 10 may be incorporated in the OS. When the processor 11 executes the OS, task management, memory management, file management, communication control, and the like are performed.
The program for realizing the operation of the operation confirmation support device 10, the operation code 30, the specification information of the software to be confirmed, and the OS may be stored in the auxiliary storage device. The auxiliary storage device is, for example, a hard disk, a flash memory, or a combination thereof. Auxiliary storage devices include SSD (registered trademark, Solid State Drive), SD (registered trademark, Secure Digital) memory card, CF (registered trademark, CompactFlash), NAND flash, flexible disk, optical disk, compact disk, and Blu-ray (registered). It may be a portable recording medium such as a (trademark) disc, a DVD (registered trademark, Digital Versaille Disk), or a combination thereof.

When the program and OS that realize the operation of the operation confirmation support device 10 are stored in the auxiliary storage device, they are loaded from the auxiliary storage device into the memory 12, read from the memory 12 into the processor 11, and executed by the processor 11. ..
The operation confirmation support device 10 may include a plurality of processors that replace the processor 11. These plurality of processors share the execution of the program that realizes the operation of the operation confirmation support device 10. Each processor is, as a specific example, a CPU.
The data, information, signal values, and variable values used, processed, or output by the program that realizes the operation of the operation confirmation support device 10 are at least the memory 12, the auxiliary storage device, or the register or cache memory in the processor 11. It is stored in either.

The program that realizes the operation of the operation confirmation support device 10 may be stored and provided in a computer-readable medium, may be stored in the storage medium and provided, or may be provided as a program product. A program product is not limited to a visual form, but is loaded with a computer-readable program. Further, the program that realizes the operation of the operation confirmation support device 10 may be provided via the network.

An example of the functional configuration of the operation confirmation support device 10 according to the present embodiment will be described with reference to FIG.
The operation confirmation support device 10 includes a program information acquisition unit 15, an inspection condition acquisition unit 16, an inspection condition conversion unit 17, an analysis unit 18, and an input value output unit 19.

The program information acquisition unit 15 acquires the operation code 30 from the memory 12 or from the connection destination via the communication device 13.

As the inspection condition 31, the inspection condition acquisition unit 16 provides information (hereinafter, referred to as target arrival location information) regarding the target arrival location including the target arrival location that is the target of the operation check in the operation code 30 acquired by the program information acquisition unit 15. get. The inspection condition 31 according to the present embodiment is input by the person in charge from the external device via the input / output device 14.
The inspection condition 31 includes at least one or more target arrival points. The target reaching location is a specific location in the operation code 30, and is a target location for operation confirmation. More specifically, the target arrival point is the line number of the operation code 30. Therefore, the target arrival location information is input as the line number of the operation code 30, and is acquired as the inspection condition 31 by the inspection condition acquisition unit 16. Further, the present invention is not limited to this, and the target arrival location information may be input by directly marking and designating the target arrival location on the operation code 30 displayed on the display via the input / output device 14.

The inspection condition conversion unit 17 generates a determination formula for determining that the target arrival point included in the inspection condition 31 has been reached, based on the inspection condition 31 acquired by the inspection condition acquisition unit 16.
In the present embodiment, the determination formula for determining that the target arrival point included in the inspection condition 31 has been reached is generated as a logical expression that can be analyzed by the analysis unit 18. The logical expression of this determination expression is a logical expression of the conditional expression indicating the condition to be satisfied when the line number of the operation code 30 indicating the target arrival point is reached, and is also referred to as the target arrival condition expression 32.
Further, the inspection condition conversion unit 17 adds a code used for the arrival determination using the target arrival location variable to the operation code 30 acquired by the program information acquisition unit 15 based on the inspection condition 31 acquired by the inspection condition acquisition unit 16. Generate the inspection code. Then, the inspection condition conversion unit 17 converts the inspection code into a logical expression that can be analyzed by the SAT solver of the analysis unit 18 to generate the logical expression 33 of the inspection code.
Therefore, the output of the inspection condition conversion unit 17 becomes the target achievement condition expression 32 and the logical expression 33 of the inspection code.

The analysis unit 18 searches for an input value to reach the target arrival point using the target arrival condition formula 32 generated by the inspection condition conversion unit 17, and generates a generated value 34 as an input value to reach the target arrival point. More specifically, the analysis unit 18 uses the SAT solver to solve the logical product of the target achievement condition formula 32 generated by the inspection condition conversion unit 17 and the logical formula 33 of the inspection code to reach the target arrival location. Search for the input value to be reached. Then, the analysis unit 18 generates a generated value 34 as an input value for reaching the target arrival point. Note that solving the logical product means finding an input value that satisfies the logical expression represented by the logical product, that is, the solution of the logical variable that makes the logical expression true.

The input value output unit 19 outputs the generated value 34 generated by the analysis unit 18. Further, the input value output unit 19 outputs a notification that the generated value 34 cannot be generated when the analysis unit 18 cannot generate the generated value 34 as a result of the search.

Further, the "units" of the program information acquisition unit 15, the inspection condition acquisition unit 16, the inspection condition conversion unit 17, the analysis unit 18, and the input value output unit 19 are "circuits" or "processes" or "procedures" or "processes". May be read as.
Further, the operation confirmation support device 10 may be realized by a processing circuit. The processing circuit is, for example, a logic IC (Integrated Circuit), a GA (Gate Array), an ASIC (Application Specific Integrated Circuit), or an FPGA (Field-Programmable Gate Array).
In this case, the program information acquisition unit 15, the inspection condition acquisition unit 16, the inspection condition conversion unit 17, the analysis unit 18, and the input value output unit 19 are each realized as a part of the processing circuit.
In this specification, the superordinate concept of the processor and the processing circuit is referred to as "processing circuit Lee".
That is, the processor and the processing circuit are specific examples of the "processing circuit Lee", respectively.
The program that realizes the operation of the operation confirmation support device 10 acquires program information by performing the procedures performed by the program information acquisition unit 15, the inspection condition acquisition unit 16, the inspection condition conversion unit 17, the analysis unit 18, and the input value output unit 19, respectively. It is a program to be executed by a computer as a procedure, an inspection condition acquisition procedure, an inspection condition conversion procedure, an analysis procedure, and an input value output procedure.

*** Explanation of operation ***
An operation example of the operation confirmation support device 10 according to the present embodiment will be described with reference to FIGS. 3 to 7.

First, an example of the processing operation of the operation confirmation support device 10 according to the present embodiment will be described with reference to the flowchart of FIG.

In step S101, the program information acquisition unit 15 acquires the operation code 30. Then, the process proceeds to step S102.

Next, in step S102, the inspection condition acquisition unit 16 acquires the target arrival location information of the operation code 30 from the external device via the input / output device 14 as the inspection condition 31. Then, the process proceeds to step S103.

Next, in step S103, the inspection condition conversion unit 17 defines a target arrival point variable based on the inspection condition 31 acquired by the inspection condition acquisition unit 16 in the process of step S102. The target arrival point variable is a variable used for the arrival determination for determining that the target arrival point has been reached. Then, the process proceeds to step S104.

Next, in step S104, the inspection condition conversion unit 17 uses the code used for the arrival determination using the target arrival location variable based on the inspection condition 31 acquired by the inspection condition acquisition unit 16 in the process of step S102 as the operation code 30. Generate the inspection code added to.
The inspection code is the code indicated by the arithmetic expression of the target arrival point variable in one of the lines before and after the target arrival point line, which is always executed when the target arrival point line is reached in the operation code 30. Is inserted.
Then, the inspection condition conversion unit 17 converts the inspection code into a logical expression that can be analyzed by the SAT solver of the analysis unit 18 to generate the logical expression 33 of the inspection code. Then, the process proceeds to step S105.

Next, in step S105, the inspection condition conversion unit 17 generates a target arrival condition expression 32 used for the arrival determination using the target arrival location variable based on the inspection condition 31 acquired in the process of step S102. The target arrival condition expression 32 generated by the inspection condition conversion unit 17 is a condition satisfied by the target arrival location variable when the line in which the code used for the arrival determination using the target arrival location variable included in the inspection code is inserted is executed. Is a conditional expression shown by a logical expression. Then, the process proceeds to step S106.
Since there is no dependency between the process of step S105 and the process of step S104, the operation confirmation support device 10 may be executed by changing the execution order or in parallel.

Next, in step S106, the analysis unit 18 searches for an input value to reach the target arrival point by solving the logical product of the logical expression 33 of the inspection code and the target arrival condition expression 32 using the SAT solver. ..
When there is an input value that is a solution of the logical product, the analysis unit 18 generates a generated value 34 as an input value for reaching the target arrival point. Then, the process proceeds to step S107.
On the other hand, when the input value which is the solution of the logical product does not exist, the analysis unit 18 does not generate the generated value 34 and notifies the input value output unit 19 that the generated value 34 could not be generated. Then, the process proceeds to step S108.

Next, in step S107, the input value output unit 19 outputs the generated value 34 generated by the analysis unit 18 in step S106 to the external device via the input / output device 14.

Next, in step S108, the input value output unit 19 indicates that in step S106, the analysis unit 18 does not have a solution of the logical product of the logical expression 33 of the inspection code and the target achievement condition expression 32, and the generated value 34 cannot be generated. Output a notification. By outputting this notification, the input value output unit 19 notifies the person in charge that the transition to the specific internal state indicated at the target arrival point is an operation that cannot occur in the confirmed software.

A more detailed operation example of the operation confirmation support device 10 according to the present embodiment will be described with reference to a specific example of the operation code 30 shown in FIG.
Specifically, in the following example, in order to confirm the operation of the confirmed software generated by the operation code 30 shown in FIG. 4 in the SLEEP mode, the operation confirmation support device 10 sets the internal state of the confirmed software to the SLEEP mode. The operation of generating the generated value 34 to be transitioned to will be described.
The number string at the left end of FIG. 4 indicates the line number of the operation code 30.
The operation code 30 of this example has a mode variable mode representing the operation mode which is the internal state of the software to be confirmed, two input variables Demo_I_x and Demo_I_y for substituting the input value, and an output variable Demo_O for substituting the output value. ..

In step S101 of FIG. 3, the program information acquisition unit 15 acquires the operation code 30 shown in FIG. Then, the process proceeds to step S102.
In this example, the operation code 30 is only one file in which one function main is described, but the operation code 30 is not limited to this, and may be a plurality of functions or a set of a plurality of files.

In step S102 of FIG. 3, the inspection condition acquisition unit 16 acquires the target arrival location information in the operation code 30 as the inspection condition 31. Then, the process proceeds to step S103.
In this example, the target arrival point in the operation code 30 is the 26th line of the operation code 30 shown in FIG. 4, which corresponds to the “internal state of the confirmed software whose operation mode has changed to the SLEEP mode”.
Therefore, in this example, the person in charge directly inputs the information "26th line of the operation code 30" to the inspection condition acquisition unit 16 via the input / output device 14 as the target arrival location information.
However, the method of inputting the target arrival point information is not limited to this, and as shown in FIG. 5, a method of visually marking the target arrival point on the operation code 30 displayed on the display via the input / output device 14, etc. Any method may be used as long as it is a method of designating and inputting a specific part in the operation code 30.

In step S103 of FIG. 3, the inspection condition conversion unit 17 defines one target arrival point variable reach based on one inspection condition 31 of “26th line of the operation code 30”. Then, the process proceeds to step S104.
The initial value of the target arrival point variable reach defined here is 0.

In step S104 of FIG. 3, the inspection condition conversion unit 17 is based on the inspection condition 31 of "the 26th line of the operation code 30", and as shown in FIG. Generate the inspection code added by inserting the code of reach ++;).
Further, the inspection condition conversion unit 17 converts the inspection code into a logical expression that can be analyzed by the SAT solver, and generates the logical expression 33 of the inspection code. Then, the process proceeds to step S105.

In step S105 of FIG. 3, the inspection condition conversion unit 17 sets the target arrival condition expression 32 to be satisfied when the target arrival point is reached, based on the target arrival point variable reach defined based on the inspection condition 31, “reach>. 0 "is generated. Then, the process proceeds to step S106.

In step S106 of FIG. 3, the analysis unit 18 solves the logical product of the logical expression 33 of the inspection code and the target achievement condition expression 32 using the SAT solver. Then, the analysis unit 18 searches for the input values to be assigned to the input variables Demo_I_x and Demo_I_y by the time the execution process of the confirmed software reaches the 26th line of the operation code 30 which is the target arrival point. Then, the analysis unit 18 generates a generated value 34 as an input value for reaching the target arrival point.
In this example, the execution process of the confirmed software reaches the 27th line of the inspection code in which reach ++; is inserted, and the target arrival location is a solution that makes "reach>0", which is the target achievement conditional expression 32, true. There is an input value to reach. Therefore, the generated value 34 is generated as an input value for reaching the target arrival point. Therefore, the process proceeds to step S107.

In step S107 of FIG. 3, the input value output unit 19 outputs the generated value 34 generated in the process of step S106.

FIG. 7 shows the generated value 34 generated in this example and the execution order of the confirmed software until the target arrival point is reached.
The table at the lower right of FIG. 7 shows the input values assigned to the input variables Demo_I_x and Demo_I_y in each of the three execution cycles of the confirmed software as inputs to the confirmed software.
Specifically, the input values assigned to the input variables Demo_I_x and Demo_I_y in the first cycle are 10 and 3. The input values assigned to the input variables Demo_I_x and Demo_I_y in the second cycle are 90 and 3. Further, the input values assigned to the input variables Demo_I_x and Demo_I_y in the third cycle are both xx and yy indicating arbitrary values.

The table on the upper right of FIG. 7 shows the values of the output variable Demo_O and the value of the mode variable mode before and after the input values are assigned to the input variables Demo_I_x and Demo_I_y.
Specifically, at the start of the first cycle, the output variable Demo_O has no value, and the mode variable mode is START. When 10 and 3 are assigned to the input variables Demo_I_x and Demo_I_y, the processing of the 8th and 9th lines of the operation code 30 is executed, 100 is assigned to the output variable Demo_O, and RUN is assigned to the mode variable mode. Then, at the end of the first cycle, the output variable Demo_O becomes 100, and the mode variable mode becomes RUN.
At the start of the second cycle, the output variable Demo_O is 100 and the mode variable mode is RUN. When 90 and 3 are assigned to the input variables Demo_I_x and Demo_I_y, the processing of the 21st and 22nd lines of the operation code 30 is executed, 50 is assigned to the output variable Demo_O, and SLEEP is assigned to the mode variable mode. Then, at the end of the first cycle, the output variable Demo_O becomes 50, and the mode variable mode becomes SLEEP.
At the start of the third cycle, the output variable Demo_O is 50 and the mode variable mode is SLEEP. Regardless of which value is assigned to the input variables Demo_I_x and Demo_I_y, the execution process of the confirmed software reaches the 26th line of the operation code 30 indicating the target arrival point of this example.

In this example, the input values to the input variables Demo_I_x and Demo_I_y shown in the lower right table of FIG. 7 are 10 and 3 in the first cycle, 90 and 3 in the second cycle, and arbitrary values in the third cycle, respectively. The generated value 34 is output as an input value for three cycles.
As described above, in the present embodiment, the generated value 34 to be generated is not limited to one cycle, and may be generated as an input value string for a plurality of cycles.

By inputting the generated value 34 generated as described above into the confirmed software in each execution cycle and executing it, the execution process of the confirmed software reaches the 26th line of the operation code 30 in the third cycle. The internal state transitions to SLEEP mode. Therefore, it is possible to check the operation in the SLEEP mode.
In this example, the case where the inspection condition acquisition unit 16 acquires the target arrival point information including one target arrival point as the inspection condition 31 has been described, but the present invention is not limited to this, and the target arrival point including a plurality of target arrival points is not limited to the above. Information may be acquired as inspection condition 31. As a specific example, the inspection condition acquisition unit 16 acquires two line numbers of the operation code 30 indicating two target arrival points as the inspection condition 31, such as "11th line and 26th line of the operation code 30". You may.
Then, the operation confirmation support device 10 may generate a generation value 34 that reaches both target arrival points of these two target arrival points, that is, the 11th line and the 26th line of the operation code 30.
Further, when the operation confirmation support device 10 cannot generate the generated value 34 that reaches both target arrival points of the two target arrival points, the operation confirmation support device 10 is made to reach both target arrival points of the two target arrival points. It may be notified that the generated value 34 could not be generated.
Further, when the operation confirmation support device 10 cannot generate the generated value 34 that reaches both of the two target arrival points and can generate the generated value 34 that reaches only one of the target arrival points, 2 It may be notified that the generated value 34 that reaches both target arrival points of one target arrival point could not be generated and that only one of the target arrival points can be reached.

*** Explanation of the effect of the embodiment ***
As described above, in the present embodiment, the person in charge does not need to refer to the specification information regarding the internal state of the software to be confirmed, but simply specifies the target arrival point (line 26 in the above example) in the operation code 30. A specific internal state that is the target of operation confirmation can be input as the inspection condition 31. Then, the operation confirmation support device 10 can generate a generated value 34 to reach the target arrival point by using the inspection condition 31.
Therefore, in the above example, the person in charge internally checks the operation of the confirmed software that transitions the internal state to the specific state shown in the 26th line, or confirms the operation of the device controlled by the confirmed software in the specific state. The work of determining the state value becomes unnecessary. Therefore, the man-hours required for operation check can be reduced.

Further, the inspection condition conversion unit 17 generates a target arrival condition expression 32 (reach> 0) using the target arrival location variable (reach) based on the inspection condition 31 “26th line of the operation code 30”. ..
Therefore, it is not necessary for the person in charge to manually create a logical expression that can be analyzed by the SAT solver used by the analysis unit 18. Therefore, in addition to reducing the man-hours required for operation check, it is possible for the person in charge to check the operation even if he / she does not have mathematical knowledge.
In addition, by notifying that the generated value 34 cannot be generated, the person in charge informs that the state transition to the state indicated by the target arrival point input as the inspection condition 31 is an operation that cannot occur in the confirmed software. You can check.
Therefore, it is possible to indicate that the behavior of the confirmed software may not be implemented according to the specifications.

On the other hand, as compared with the present embodiment, in the method of Patent Document 1, the person in charge refers to the specification information of the software to be confirmed, extracts a variable representing the internal state targeted for operation confirmation, and the variable is It is necessary to set the internal state value to be satisfied. Furthermore, since the work of describing this internal state value in a logical expression that can be analyzed by the SAT solver is required, the person in charge needs mathematical knowledge.

In order to clarify the effect, as a specific example, a generated value 34 for transitioning the internal state of the confirmed software generated by the operation code 30 shown in FIG. 4 to the SLEEP mode is created by using the method of Patent Document 1. This case will be described.
First, the person in charge refers to the specification information of the software to be confirmed, and the SLEEP mode, which is the target of the operation check, is a specific state in the operation mode representing the internal state, and the operation mode is represented by the value of the mode variable mode. You need to understand that.
Next, the person in charge needs to determine the value of the mode variable mode representing the SLEEP mode from the specification information of the software to be confirmed.
Further, it is necessary to convert the mode variable mode representing the SLEEP mode determined in this way into a logical expression that can be analyzed by the SAT solver.
The operation code 30 in FIG. 4 is only one file in which one function main is described, but when the software to be confirmed is large-scale and complicated, the internal state values targeted for operation confirmation are many and complicated, so the operation is performed. Confirmation man-hours will increase significantly.

*** Other configurations ***
<Modification example 1>
In the first embodiment, the program information acquisition unit 15 has described an example of acquiring the operation code 30. However, the program information acquisition unit 15 acquires the AST program created by AST (Abstract Syntax Tree) including the node or branch as the operation program, converts it into the AST code which is the source code of the AST program, and converts the operation code 30. You may get the AST code as.
In the first modification, the person in charge directly inputs the information regarding the node or branch indicating the target arrival location to the inspection condition acquisition unit 16 via the input / output device 14 as the target arrival location information. Further, the method of inputting the target arrival location information is not limited to this, and a method of visually designating and inputting the nodes or branches included in the AST displayed on the display via the input / output device 14 may be used. ..
When the AST code is acquired in step S101 of FIG. 3, in step S102 of FIG. 3, the inspection condition acquisition unit 16 sets the information about the node or branch indicating the target arrival location as the inspection condition 31 and uses the input / output device 14 as the inspection condition 31. It may be obtained from an external device. Then, in step S104 of FIG. 3, the inspection condition conversion unit 17 extracts the line number of the code corresponding to the node or branch indicating the target arrival point from the operation code 30 based on the inspection condition 31, and determines the inspection code. The formula 33 may be generated. Then, in step S105 of FIG. 3, the target arrival conditional expression 32 that is satisfied when the line number of the code corresponding to the node or branch indicating the target arrival location in the operation code 30 is reached may be generated.

<Modification 2>
As a modification 2, the program information acquisition unit 15 acquires a state transition program created in a state transition diagram including a node or an edge as an operation program, converts it into a state transition code which is a source code of the state transition program, and converts it into a state transition code. The state transition code may be acquired as the operation code 30.
In the second modification, the person in charge directly inputs the information regarding the node or edge indicating the target arrival location to the inspection condition acquisition unit 16 via the input / output device 14 as the target arrival location information. Further, the method of inputting the target arrival location information is not limited to this, and is a method of visually designating and inputting a node or an edge in the state transition diagram displayed on the display via the input / output device 14. May be good.
When the state transition code is acquired in step S101 of FIG. 3, in step S102 of FIG. 3, the inspection condition acquisition unit 16 sets the input / output device 14 as the inspection condition 31 with the information regarding the node or edge indicating the target arrival point as the inspection condition 31. It may be obtained from an external device via. Then, in step S104 of FIG. 3, the inspection condition conversion unit 17 extracts the line number of the code corresponding to the node or edge indicating the target arrival point from the operation code 30 based on the inspection condition 31, and determines the inspection code. The formula 33 may be generated. Then, in step S105 of FIG. 3, the target arrival conditional expression 32 that is satisfied when the line number of the code corresponding to the node or edge indicating the target arrival location in the operation code 30 is reached may be generated.

Embodiment 2.
The present embodiment will be described with reference to FIGS. 8 to 11.
In the present embodiment, an example will be described in which the inspection condition 31 includes a plurality of target arrival points and the arrival order of the plurality of target arrival points.
In this embodiment, the difference from the first embodiment will be mainly described.
The matters not explained below are the same as those in the first embodiment.

*** Explanation of configuration ***
Since the hardware configuration of the operation confirmation support device 10 according to the present embodiment is the same as the configuration of the first embodiment shown in FIG. 1, the description thereof will be omitted.
The inspection condition conversion unit 17 according to the present embodiment generates the target achievement condition formula 32 and the inspection code as in the first embodiment, and then performs a conditional inspection based on the inspection code and the inspection condition 31. Generate code for.
Then, the inspection condition conversion unit 17 converts the conditional inspection code into a logical expression that can be analyzed by the SAT solver of the analysis unit 18 to generate a logical expression of the conditional inspection code.
Therefore, the output of the inspection condition conversion unit 17 becomes a logical expression of the target achievement condition expression 32 and the conditional inspection code.

*** Explanation of operation ***
First, an example of the processing operation of the operation confirmation support device 10 according to the present embodiment will be described with reference to the flowchart of FIG. The same operations as those in the first embodiment are designated by the same numbers, and the description thereof will be omitted.
After the completion of step S101, in step S202, the inspection condition acquisition unit 16 acquires the target arrival location information of the operation code 30 from the external device via the input / output device 14 as the inspection condition 31. Then, the process proceeds to step S203.
The inspection condition 31 acquired by the inspection condition acquisition unit 16 includes a plurality of target arrival points and an order of arrival of the plurality of target arrival points (hereinafter, referred to as a target arrival order).

Next, in step S203, the inspection condition conversion unit 17 has the same number of plurality of target arrival points included in the inspection condition 31 based on the inspection condition 31 acquired by the inspection condition acquisition unit 16 in the process of step S202. Define the target reach variable. Then, the process proceeds to step S204.

Next, in step S204, the inspection condition conversion unit 17 operates a code used for arrival determination using a plurality of target arrival location variables based on the inspection condition 31 acquired by the inspection condition acquisition unit 16 in the process of step S202. Generate the inspection code added to the code 30. Then, the process proceeds to step S205.
In the operation code 30, a code used for arrival determination using a plurality of target arrival point variables is added to a line that is always executed when each line of a plurality of target arrival points is reached. That is, the inspection code includes the code used for the arrival determination indicated by the calculation formula of each target arrival point variable in one of the lines before and after each line of the plurality of target arrival points in the operation code 30. It will be the one that was inserted.

Next, in step S205, the inspection condition conversion unit 17 uses a plurality of target arrival point variables defined in the process of step S203 based on the inspection condition 31 acquired by the inspection condition acquisition unit 16 in the process of step S202. Generate a target arrival order conditional expression. Then, the process proceeds to step S206.
The target arrival order conditional expression is a target arrival point variable or a condition that the target arrival point variable satisfies when the code used for the arrival determination is executed by reaching each of a plurality of target arrival points according to the target arrival order. It is an expression described by logical product using the denial of the target arrival point variable. The number of target arrival order conditional expressions is the same as the number of a plurality of target arrival points.

Next, in step S206, the inspection condition conversion unit 17 generates a conditional inspection code in which the target arrival order conditional expression is added to the inspection code. Then, the inspection condition conversion unit 17 converts the conditional inspection code into a logical expression that can be analyzed by the SAT solver of the analysis unit 18 to generate a logical expression of the conditional inspection code. Then, the process proceeds to step S207.
The conditional inspection code generated by the inspection condition conversion unit 17 is a target in the line after each line in which the code used for the arrival determination indicated by the calculation formula of the target arrival point variable in the inspection code is inserted. The arrival order conditional expression is inserted.

Next, in step S207, the inspection condition conversion unit 17 generates the target arrival condition expression 32 using the target arrival order conditional expression generated in the process of step S205. Then, the process proceeds to step S208.
The target achievement condition expression 32 generated by the inspection condition conversion unit 17 is for inspecting that the target arrival points in the conditional inspection code are reached according to the target arrival order and all the target arrival order conditional expressions are true. It is a conditional expression of. Therefore, the target arrival condition expression 32 is composed of the logical product of the target arrival order conditional expression.
Since there is no dependency between the process of step S207 and the process of step S206, the software to be confirmed may be executed by changing the execution order or in parallel.

Next, in step S208, the analysis unit 18 searches for an input value to reach the target arrival point by solving the logical product of the logical expression of the conditional inspection code and the target arrival condition expression 32 using the SAT solver. do.
When there is an input value that is a solution of the logical product, the analysis unit 18 generates a generated value 34 as an input value for reaching the target arrival point. Then, the process proceeds to step S107.
On the other hand, when the input value which is the solution of the logical product does not exist, the analysis unit 18 does not generate the generated value 34 and notifies the input value output unit 19 that the generated value 34 could not be generated. Then, the process proceeds to step S108.
Since steps S107 and S108 are as described above, description thereof will be omitted.

A more detailed operation example of the operation confirmation support device 10 according to the present embodiment will be described with reference to a specific example of the operation code 30 shown in FIG.
Specifically, in the following example, the person in charge confirms the operation that "starting from the START mode, the operation mode changes in the order of the RUN mode, the STOP mode, the SLEEP mode, the ReSTART mode, and the END mode".
In order to confirm this operation, the person in charge specifies and inputs five target arrival points and the target arrival order in the operation code 30 as inspection conditions 31, so that the operation confirmation support device 10 reaches the five target arrival points. An example of generating the generated value 34 to be reached in order will be described.
The leftmost circle in FIG. 9 indicates the target arrival point. Further, the numbers 1 to 5 described in the leftmost circle of FIG. 9 indicate the target arrival order.
That is, in the example of FIG. 9, it is shown that five target arrival points are designated in the operation code 30. The target arrival order is as follows: target arrival point 1 (10th line), target arrival point 2 (21st line), target arrival point 3 (33rd line), target arrival point 4 (56th line), target arrival point. It shows that the order is 5 (79th line).

In step S101 of FIG. 8, the program information acquisition unit 15 acquires the operation code 30 shown in FIG. Then, the process proceeds to step S202.
In this example, the operation code 30 is only one file in which one function main is described, but the operation code 30 is not limited to this, and may be a plurality of functions or a set of a plurality of files.

In step S202 of FIG. 8, the inspection condition acquisition unit 16 acquires the target arrival location information in the operation code 30 as the inspection condition 31. Then, the process proceeds to step S203.
The inspection condition 31 acquired by the inspection condition acquisition unit 16 includes a plurality of target arrival points and a target arrival order which is an arrival order of the plurality of target arrival points.
The goals of the operation check of this example are shown in (1) to (6) below.
(1) The operation mode, which is the internal state of the software to be confirmed, shifts to the RUN mode.
(2) The operation mode shifts to the STOP mode.
(3) The operation mode shifts to the SLEEP mode.
(4) The operation mode shifts to the Reset mode.
(5) The operation mode shifts to the END mode.
(6) The operation mode starts from the START mode and changes in the order of the RUN mode, the STOP mode, the SLEEP mode, the ReSTART mode, and the END mode.
Therefore, the plurality of target arrival points that satisfy the inspection condition 31 correspond to the transition of the internal state of the confirmed software in each of (1) to (5), that is, the 10th line, the 21st line, and the 33rd line of the operation code 30. The eyes, the 56th line, and the 79th line.
The target arrival order, which is the inspection condition 31, is the 21st line, the 33rd line, and the 56th line in order from the 10th line of the operation code 30, which corresponds to the transition order of the internal state of the confirmed software in (6). , 79th line.
Therefore, in this example, the person in charge directly informs the inspection condition acquisition unit 16 via the input / output device 14 “10th line, 21st line, 33rd line, 56th line, 79th line of the operation code 30”. Information indicating a plurality of target arrival points is input as target arrival point information. In addition, the person in charge inputs information indicating the target arrival order of "first the 10th line, then the 21st line, the 33rd line, the 56th line, and the 79th line" as the target arrival location information.
However, the method of inputting the target arrival point information is not limited to this, and as shown in FIG. 9, a plurality of target arrival points and the target arrival order are directly displayed on the operation code 30 displayed on the display via the input / output device 14. Any method may be used as long as it is a method of designating and inputting a specific place and an order in the operation code 30, such as visually marking.

In step S203 of FIG. 8, the inspection condition conversion unit 17 is based on the inspection condition 31 of "10th line, 21st line, 33rd line, 56th line, 79th line of the operation code 30", and these five Define five target arrival point variables corresponding to the target arrival point. Specifically, the inspection condition conversion unit 17 defines reach1, reach2, reach3, reach4, and reach5 as target arrival location variables. Then, the process proceeds to step S204.

In step S204 of FIG. 8, the inspection condition conversion unit 17 is based on the inspection condition 31 that the target arrival location is "10th line, 21st line, 33rd line, 56th line, 79th line of the operation code 30". , The inspection code is generated by inserting the code used for the arrival determination indicated by the calculation formula of each target arrival point variable into the operation code 30.
Specifically, the inspection condition conversion unit 17 has "reach1 ++;" on the 11th line, "reach2 ++;" on the 22nd line, "reach3 ++;" on the 34th line, "reach4 ++;" on the 57th line, and 80th line. An operation code 30 is inserted into the eye to generate an inspection code. Then, the process proceeds to step S205.

In step S205 of FIG. 8, the inspection condition conversion unit 17 defines five target arrival order conditional expressions as shown in FIG. 10 based on the target arrival order acquired as the inspection condition 31. Specifically, the inspection condition conversion unit 17 defines condition1, condition2, condition3, condition4, and condition5 as the target arrival order conditional expression. Then, the process proceeds to step S206.
The target arrival order conditional expression of this example is a condition satisfied by the five target arrival point variables when the five target arrival points of the operation code 30 are reached according to the target arrival order and the code used for the arrival determination is executed. Is an expression that describes. Further, the target arrival order conditional expression is an expression described by a logical product using the target arrival point variable or the negation of the target arrival point variable.

In step S206 of FIG. 8, as shown in FIG. 11, the inspection condition conversion unit 17 generates a conditional inspection code in which the target arrival order conditional expression is added to the inspection code.
Specifically, the inspection condition conversion unit 17 inserts condition1 on the 12th line, condition2 on the 25th line, condition3 on the 39th line, condition4 on the 64th line, and condition5 on the 89th line, and the conditional inspection code. To generate. Further, the inspection condition conversion unit 17 converts the conditional inspection code into a logical expression that can be analyzed by the SAT solver of the analysis unit 18 to generate a logical expression of the conditional inspection code. Then, the process proceeds to step S207.

In step S207 of FIG. 8, the inspection condition conversion unit 17 indicates a condition to be satisfied when the five target arrival points in the conditional inspection code are reached according to the target arrival order by using the target arrival order conditional expression. The target achievement conditional expression 32 is generated. Then, the process proceeds to step S208.
As shown in FIG. 10, the target achievement condition expression 32 of this example is condition1 && condition2 && condition3 && condition4 && condition5.

In step S208 of FIG. 8, the analysis unit 18 solves the logical product of the logical expression of the conditional inspection code and the target arrival condition expression 32 by using the SAT solver, so that the five target arrival points are arranged in the target arrival order. Search for the input value to reach. Then, the analysis unit 18 generates a generated value 34 as an input value for reaching the five target arrival points in the target arrival order.
In the present embodiment, the generated value 34 to be generated is not limited to one cycle, and may be generated as an input value string for a plurality of cycles.
In this example, there are input values for reaching five target arrival points in the target arrival order, which is a solution that makes the logical product of the logical expression of the conditional inspection code and the target achievement condition expression 32 true. Therefore, the generated value 34 is generated as an input value for reaching the five target arrival points in the target arrival order. Then, the process proceeds to step S107.

In step S107 of FIG. 8, the input value output unit 19 outputs the generated value 34 generated in the process of step S208.

By inputting the generated value 34 generated as described above into the confirmed software at each cycle and executing the execution, the execution process of the confirmed software can reach the target arrival point in the target arrival order. Specifically, the execution process of the confirmed software goes to "10th line, 21st line, 33rd line, 56th line, 79th line of the operation code 30", first the 10th line, and then 21 lines. The eyes, the 33rd line, the 56th line, and the 79th line can be reached in this order.
As a result, it is possible to confirm the operation that "starting from the START mode, the operation modes are changed in the order of the RUN mode, the STOP mode, the SLEEP mode, the ReSTART mode, and the END mode".

*** Explanation of the effect of the embodiment ***
As described above, in the present embodiment, the person in charge does not refer to the specification information regarding the internal state of the software to be confirmed, the plurality of target arrival points in the operation code 30, and the targets of the plurality of target arrival points. Enter by specifying the arrival order. Then, only by the person in charge specifying in this way, it is possible to input a plurality of internal states that are targets for operation confirmation and their transition order as the inspection condition 31. Then, the operation confirmation support device 10 can generate the generated value 34 as an input value for transitioning a plurality of internal states according to the acquired transition order by using the inspection condition 31.
Therefore, in the above example, the internal states are changed to a plurality of states (10th line, 21st line, 33rd line, 56th line, 79th line) in a specific order (first 10th line, then 21st line, and so on. In the operation check of transitioning in the order of the 33rd line, the 56th line, and the 79th line), the work of determining the internal state value becomes unnecessary. Therefore, the man-hours required for operation check can be reduced.

Further, the inspection condition conversion unit 17 generates the target achievement condition expression 32 based on the inspection condition 31.
Therefore, it is not necessary for the person in charge to manually create a logical expression that can be analyzed by the SAT solver used by the analysis unit 18. Therefore, in addition to reducing the man-hours required for operation check, it is possible for the person in charge to check the operation even if he / she does not have mathematical knowledge.

*** Other configurations ***
<Modification example 1>
In the second embodiment, the program information acquisition unit 15 has described an example of acquiring the operation code 30. However, the program information acquisition unit 15 acquires the AST program created by AST including the node or branch as the operation program, converts it into the AST code which is the source code of the AST program, and acquires the AST code as the operation code 30. You may.
In the first modification, the person in charge directly informs the inspection condition acquisition unit 16 via the input / output device 14 the information regarding the node, the branch, or the combination of the node and the branch, which indicates the plurality of target arrival points. Enter as information. Further, the person in charge directly inputs the target arrival order of the plurality of target arrival points indicated by the nodes or branches into the inspection condition acquisition unit 16 via the input / output device 14 as the target arrival point information.
The method of inputting the target arrival location information is not limited to this, and may be a method of visually designating and inputting the nodes or branches included in the AST displayed on the display via the input / output device 14. .. Further, the method of inputting the target arrival location information may be a method of inputting the target arrival order by designating the nodes or branches included in the AST displayed by the input / output device 14 in order.
When the AST code is acquired in step S101 of FIG. 8, in step S202 of FIG. 8, the inspection condition acquisition unit 16 inspects the node, the branch, or the information regarding the combination of the node and the branch indicating the target arrival point. As the number 31, it may be acquired from an external device via the input / output device 14. Then, in step S204 of FIG. 8, the inspection condition conversion unit 17 extracts the line number of the code corresponding to the node or branch indicating the target arrival point from the operation code 30 based on the inspection condition 31, and inputs the inspection code. It may be generated. Then, in step S205 of FIG. 8, the inspection condition conversion unit 17 extracts the target arrival order of reaching the line number of each code corresponding to the node or branch indicating the plurality of target arrival points based on the inspection condition 31. A target arrival order conditional expression may be generated. Then, in step S207 of FIG. 8, the target arrival condition expression that is satisfied when the line numbers of the codes corresponding to the nodes or branches indicating the plurality of target arrival points in the operation code 30 are reached in the order of the target arrival order. 32 may be generated.

<Modification 2>
As a modification 2, the program information acquisition unit 15 acquires a state transition program created in a state transition diagram including a node or an edge as an operation program, converts it into a state transition code which is a source code of the state transition program, and converts it into a state transition code. The state transition code may be acquired as the operation code 30.
In the second modification, the person in charge directly informs the inspection condition acquisition unit 16 via the input / output device 14 the information regarding the node, the edge, or the combination of the node and the edge, which indicates the plurality of target arrival points. Enter as information. Further, the person in charge directly inputs the target arrival order of the plurality of target arrival points indicated by the nodes or edges to the inspection condition acquisition unit 16 via the input / output device 14 as the target arrival point information.
The method of inputting the target arrival location information is not limited to this, and is a method of visually designating and inputting the nodes or edges included in the state transition diagram displayed on the display via the input / output device 14. May be good. Further, the method of inputting the target arrival location information may be a method of inputting the target arrival order by designating the nodes or edges included in the state transition diagram displayed by the input / output device 14 in order.
When the state transition code is acquired in step S101 of FIG. 8, in step S202 of FIG. 8, the inspection condition acquisition unit 16 inspects the node, the edge, or the information regarding the combination of the node and the edge indicating the target arrival point. As condition 31, it may be acquired from an external device via the input / output device 14. Then, in step S204 of FIG. 8, the inspection condition conversion unit 17 extracts the line number of the code corresponding to the node or edge indicating the target arrival point from the operation code 30 based on the inspection condition 31, and obtains the inspection code. It may be generated. Then, in step S205 of FIG. 8, the inspection condition conversion unit 17 extracts the target arrival order of reaching the line numbers of the respective codes corresponding to the nodes or edges indicating the plurality of target arrival points based on the inspection condition 31. A target arrival order conditional expression may be generated. Then, in step S207 of FIG. 8, the target arrival condition expression that is satisfied when the line numbers of the codes corresponding to the nodes or edges indicating the plurality of target arrival points in the operation code 30 are reached in the order of the target arrival order. 32 may be generated.

Embodiment 3.
The present embodiment will be described with reference to FIGS. 12 to 14.
In the present embodiment, the operation of the generated value 34, which is an input value such that the execution process of the confirmed software reaches the target arrival point and the output value output from the confirmed software becomes a specific value, is confirmed. An example generated by the support device 10 will be described.
In this embodiment, the difference from the first embodiment will be mainly described.
The matters not explained below are the same as those in the first embodiment.

*** Explanation of configuration ***
The functional configuration of the operation confirmation support device 10 according to the present embodiment will be described with reference to FIG. The same components as those in the first embodiment shown in FIG. 2 are designated by the same numbers, and the description thereof will be omitted.
In the present embodiment, the operation confirmation support device 10 newly includes an input / output condition acquisition unit 20.
The input / output condition acquisition unit 20 sets the input / output condition 35 as a condition relating to at least one of the input value indicated by the input variable and the output value indicated by the output variable included in the operation code 30 acquired by the program information acquisition unit 15. Is obtained from an external device via the input / output device 14.
The input / output condition 35 is a condition that defines the input / output value condition of the software to be confirmed, and is specifically a range or a specific value.
The program that realizes the operation of the operation confirmation support device 10 is the input / output variable condition input procedure that realizes the function of the input / output condition acquisition unit 20 in the program that realizes the operation of the operation confirmation support device 10 of the first embodiment. Is added.

*** Explanation of operation ***
An operation example of the operation confirmation support device 10 according to the present embodiment will be described with reference to FIGS. 13 to 15.

First, with reference to the flowchart of FIG. 13, an example of the processing operation of the operation confirmation support device 10 according to the present embodiment is shown.
The same operations as those in the first embodiment are designated by the same numbers, and the description thereof will be omitted.

In step S301, the program information acquisition unit 15 acquires the operation code 30. Further, when the program information acquisition unit 15 acquires the operation code 30, the program information acquisition unit 15 analyzes the operation code 30, and is an input value input to the confirmed software or an input value output from the confirmed software. Extract the input / output variables to which the output value is assigned. Then, the process proceeds to step S102.

Since step S102 is the same as that described in the first embodiment, the description thereof will be omitted.

After the processing of step S102 is completed, in step S302, the input / output condition acquisition unit 20 acquires the input / output condition 35 that defines the input / output value conditions of the software to be confirmed.
The input / output condition 35 is a range or a value, and indicates a condition to be satisfied by the input / output variable extracted in the process of step S301. Then, the process proceeds to step S303.

In step S303, the inspection condition conversion unit 17 is at least one of an input variable inspection expression and an output variable inspection expression as an expression for inspecting the value of the input / output variable based on the input / output condition 35 acquired in the process of step S302. Generate one. Then, the inspection condition conversion unit 17 inserts and adds an expression for inspecting the value of the input / output variable into the operation code 30. Then, the process proceeds to step S103.
The code in which the expression for checking the value of the input / output variable is inserted in the operation code 30 is used as the operation code 30 in the processes after step S103.
Since steps S103 and subsequent steps are as described above, the description thereof will be omitted.

As described above, in the present embodiment, the person in charge inputs the conditions related to the input / output values of the confirmed software assuming the usage environment, so that the operation of the confirmed software can be confirmed in the assumed usage environment. can.

A more detailed operation example of the operation confirmation support device 10 according to the present embodiment will be described with reference to a specific example of the operation code 30 shown in FIG.
Specifically, in the following example, in order to confirm the operation of the confirmed software generated by the operation code 30 shown in FIG. 14 in the RUN mode, the generated values satisfying the following conditions (1) and (2). The operation of generating 34 will be described.
(1) The internal state of the confirmed software transitions to the RUN mode.
(2) The value of the output variable Demo_O to which the output value of the confirmed software is substituted is 300.
The operation code 30 of this example has a mode variable mode representing the operation mode which is the internal state of the software to be confirmed, two input variables Demo_I_x and Demo_I_y for substituting the input value, and an output variable Demo_O for substituting the output value. ..

In step S301 of FIG. 13, the program information acquisition unit 15 acquires the operation code 30 shown in FIG. After that, the program information acquisition unit 15 analyzes the acquired operation code 30 and extracts input / output variables. Then, the process proceeds to step S102.
In this example, the input variables Demo_I_x and Demo_I_y and the output variable Demo_O are extracted by the program information acquisition unit 15.

In step S102 of FIG. 13, the inspection condition acquisition unit 16 acquires the target arrival location information in the operation code 30 as the inspection condition 31. Then, the process proceeds to step S302.
In this example, the target arrival point in the operation code 30 is the 19th line of the operation code 30 shown in FIG. 14, which corresponds to the “internal state of the confirmed software whose operation mode has changed to the RUN mode”.

In step S302 of FIG. 13, the input / output condition acquisition unit 20 acquires the input / output condition 35 that defines the input / output value conditions of the software to be confirmed. Then, the process proceeds to step S303.
In the operation check in this example, since the condition that "the value of the output variable is 300" is satisfied, this input / output condition 35 is the condition of the output variable "Demo_O = 300".

In step S303 of FIG. 13, the inspection condition conversion unit 17 generates an output variable inspection expression as an expression for inspecting the value of the output variable based on the input / output condition 35 acquired in the process of S302 in the operation code 30. .. Then, the inspection condition conversion unit 17 inserts the generated output variable inspection formula into the operation code 30. As a specific example, the output variable inspection formula is inserted as an assert statement. Then, the process proceeds to step S103.

In step S103 of FIG. 13, the inspection condition conversion unit 17 defines one target arrival point variable reach based on one inspection condition 31 of "the 19th line of the operation code 30". Then, the process proceeds to step S104.

In step S104 of FIG. 13, the inspection condition conversion unit 17 inserts the code of the calculation formula (reach ++;) of the target arrival location variable on the 20th line based on the inspection condition 31 of "19th line of the operation code 30". And generate the added inspection code.
Further, the inspection condition conversion unit 17 converts the inspection code into a logical expression that can be analyzed by the SAT solver, and generates the logical expression 33 of the inspection code. Then, the process proceeds to step S105.

In step S105 of FIG. 13, the inspection condition conversion unit 17 uses the target arrival point variable reach defined based on the inspection condition 31 to satisfy the target arrival condition expression 32 (reach> 0) when the target arrival point is reached. ) Is generated. Then, the process proceeds to step S106.

In step S106 of FIG. 13, the analysis unit 18 satisfies the input / output condition 35 by solving the logical product of the logical expression 33 of the inspection code and the target arrival condition expression 32 using the SAT solver, and also satisfies the target arrival point. Search for the input value to reach. Then, the analysis unit 18 generates the generated value 34 as an input value that satisfies the input / output condition 35 and reaches the target arrival point. Specifically, the analysis unit 18 inputs the input values assigned to the input variables Demo_I_x and Demo_I_y, which reach the 19th line of the operation code 30 which is the target arrival point and the value of the output variable Demo_O is 300. Explore. Then, the analysis unit 18 generates the generated value 34 as an input value that satisfies the input / output condition 35 and reaches the target arrival point.
In this example, there is an input value that reaches the 20th line of the inspection code in which reach ++; is inserted and is a solution that makes "reach>0", which is the target achievement conditional expression 32, true. Therefore, the generated value 34 is generated as an input value that satisfies the input / output condition 35 of "Demo_O = 300" and reaches the 19th line of the operation code 30. Therefore, the process proceeds to step S107.

In step S107 of FIG. 13, the input value output unit 19 outputs the generated value 34 generated in the process of step S106.
FIG. 15 shows the generated value 34 generated in this example and the execution order of the confirmed software until the target arrival point is reached.

The lower right table of FIG. 15 shows the input values assigned to the input variables Demo_I_x and Demo_I_y in each of the three execution cycles of the confirmed software as inputs to the confirmed software.
Specifically, the input values assigned to the input variables Demo_I_x and Demo_I_y in the first cycle are 10 and 3. The input values assigned to the input variables Demo_I_x and Demo_I_y in the second cycle are also 10 and 3. The input values assigned to the input variables Demo_I_x and Demo_I_y in the third cycle are also 10 and 3.

The table on the upper right of FIG. 15 shows the values of the output variable Demo_O and the value of the mode variable mode before and after the assignment of the input values to the input variables Demo_I_x and Demo_I_y.
Specifically, at the start of the first cycle, the output variable Demo_O has no value, and the mode variable mode is START. When 10 and 3 are assigned to the input variables Demo_I_x and Demo_I_y, the processing of the 8th and 9th lines of the operation code 30 is executed, 100 is assigned to the output variable Demo_O, and RUN is assigned to the mode variable mode. Then, at the end of the first cycle, the output variable Demo_O becomes 100, and the mode variable mode becomes RUN.
At the start of the second cycle, the output variable Demo_O is 100 and the mode variable mode is RUN. When 10 and 3 are assigned to the input variables Demo_I_x and Demo_I_y, the processing of the 18th and 19th lines of the operation code 30 is executed, Demo_O + 100 is assigned to the output variable Demo_O, and RUN is assigned to the mode variable mode. Then, at the end of the first cycle, the output variable Demo_O becomes 200, and the mode variable mode becomes RUN.
At the start of the third cycle, the output variable Demo_O is 200 and the mode variable mode is RUN. When 10 and 3 are assigned to the input variables Demo_I_x and Demo_I_y, the processing of the 18th and 19th lines of the operation code 30 is executed, Demo_O + 100 is assigned to the output variable Demo_O, and RUN is assigned to the mode variable mode. Then, at the end of the first cycle, the output variable Demo_O becomes 300, and the mode variable mode becomes RUN.
Therefore, at the end of the third cycle, the execution process of the confirmed software reaches the 19th line of the operation code 30 indicating the target arrival location of this example, and the input / output condition 35 “Demo_O = 300” is satisfied. Is done.

In this example, as shown in the lower right table of FIG. 7, the input values to the input variables Demo_I_x and Demo_I_y are 10 and 3 in the first cycle, 10 and 3 in the second cycle, and 10 in the third cycle. The generated value 34 is output as an input value for three cycles of 3.
As described above, in the present embodiment, the generated value 34 is not limited to one cycle, and may be generated as an input value string for a plurality of cycles.

By inputting the generated value 34 generated as described above into the confirmed software in each cycle and executing the execution, the execution process is made to reach the 19th line of the operation code 30 which is the target arrival point in the third cycle. Moreover, the value of the output variable Demo_O can be set to 300.

In this example, the case where the input / output condition acquisition unit 20 acquires the condition related to the output value of the output variable Demo_O = 300 as the input / output condition 35 has been described. However, the present invention is not limited to this, and the input / output condition acquisition unit 20 may acquire a specific input value as the input / output condition 35, or may acquire the range of the input / output value as the input / output condition 35.

*** Explanation of the effect of the embodiment ***
As described above, when the person in charge inputs the input / output condition 35 regarding the input / output value of the confirmed software, the generation of the generated value 34 that causes the input / output value that cannot be taken in the usage environment of the confirmed software is excluded. be able to.
As a result, the person in charge can exclude the execution of unnecessary processing operations that are not expected in the environment in which the software to be confirmed is used, and execute the operation confirmation. Therefore, the man-hours required for operation check can be reduced.

<Modification example 1>
In the third embodiment, the program information acquisition unit 15 has described an example of acquiring the operation code 30. However, the program information acquisition unit 15 acquires the AST program created by AST (Abstract Syntax Tree) including the node or branch as the operation program, converts it into the AST code which is the source code of the AST program, and converts the operation code 30. You may get the AST code as.
In the first modification, the person in charge directly inputs the information regarding the node or branch indicating the target arrival location to the inspection condition acquisition unit 16 via the input / output device 14 as the target arrival location information. Further, the method of inputting the target arrival location information is not limited to this, and a method of visually designating and inputting the nodes or branches included in the AST displayed on the display via the input / output device 14 may be used. ..
When the AST code is acquired in step S301 of FIG. 13, in step S102 of FIG. 13, the inspection condition acquisition unit 16 sets the information about the node or branch indicating the target arrival location as the inspection condition 31 and uses the input / output device 14 as the inspection condition 31. It may be obtained from an external device. Then, in step S104 of FIG. 13, the inspection condition conversion unit 17 extracts the line number of the code corresponding to the node or branch indicating the target arrival point from the operation code 30 based on the inspection condition 31, and determines the inspection code. The formula 33 may be generated. Then, in step S105 of FIG. 13, the target arrival conditional expression 32 that is satisfied when the line number of the code corresponding to the node or branch indicating the target arrival location in the operation code 30 is reached may be generated.

<Modification 2>
As a modification 2, the program information acquisition unit 15 acquires a state transition program created in a state transition diagram including a node or an edge as an operation program, converts it into a state transition code which is a source code of the state transition program, and converts it into a state transition code. The state transition code may be acquired as the operation code 30.
In the second modification, the person in charge directly inputs the information regarding the node or edge indicating the target arrival location to the inspection condition acquisition unit 16 via the input / output device 14 as the target arrival location information. Further, the method of inputting the target arrival location information is not limited to this, and is a method of visually designating and inputting the nodes or edges included in the state transition diagram displayed on the display via the input / output device 14. May be good.
When the state transition code is acquired in step S301 of FIG. 13, in step S102 of FIG. 13, the inspection condition acquisition unit 16 sets the input / output device 14 as the inspection condition 31 with the information regarding the node or edge indicating the target arrival point as the inspection condition 31. It may be obtained from an external device via.
Then, in step S104 of FIG. 13, the inspection condition conversion unit 17 extracts the line number of the code corresponding to the node or edge indicating the target arrival point from the operation code 30 based on the inspection condition 31, and determines the inspection code. The formula 33 may be generated. Then, in step S105 of FIG. 13, the target arrival conditional expression 32 that is satisfied when the line number of the code corresponding to the node or edge indicating the target arrival location in the operation code 30 is reached may be generated.

10 operation check support device, 11 processor, 12 memory, 13 communication device, 14 input / output device, 15 program information acquisition unit, 16 inspection condition acquisition unit, 17 inspection condition conversion unit, 18 analysis unit, 19 input value output unit, 20 Input / output condition acquisition unit, 30 operation code, 31 inspection condition, 32 target achievement condition formula, 33 inspection code logical formula, 34 generated value, 35 input / output condition.

Claims (10)

1. A program information acquisition unit that acquires the operation code, which is the source code of the operation program that operates by reading the input value,
   An inspection condition acquisition unit that acquires information about a target arrival point including the target arrival point of the operation code as an inspection condition, and an inspection condition acquisition unit.
   An inspection condition conversion unit that generates a determination formula for determining that the target reached point included in the inspection condition acquired by the inspection condition acquisition unit has been reached.
   An operation confirmation support device including an analysis unit that generates a generated value as an input value for reaching the target arrival point using the determination formula generated by the inspection condition conversion unit.
2. The inspection condition conversion unit
   As the determination formula, a logical expression used for determining the arrival at the target arrival point is generated, a code used for determining the arrival at the target arrival point is added to the operation code to create an inspection code, and the inspection code is used. Convert to a logical expression to generate the logical expression of the inspection code,
   The analysis unit
   The operation check according to claim 1, wherein the input value that satisfies the logical product of the determination formula and the logical formula of the inspection code is searched for, and the generated value is generated as the input value to reach the target arrival point. Support device.
3. The inspection condition acquisition unit
   The line number of the operation code indicating the target arrival point is acquired as the inspection condition, and the line number is acquired.
   The inspection condition conversion unit
   The operation confirmation support device according to claim 1 or 2, wherein as the determination expression, a target arrival condition expression that is satisfied when the line number of the operation code indicating the target arrival location is reached is generated.
4. The inspection condition acquisition unit
   The line numbers of the operation code indicating the plurality of target arrival points and the target arrival order, which is the arrival order of the plurality of target arrival points, are acquired as the inspection conditions.
   The inspection condition conversion unit
   As the determination formula, any one of claims 1 to 3 that generates a target arrival condition expression that is satisfied when the line numbers of the operation codes indicating the plurality of target arrival locations are reached in the target arrival order. The operation confirmation support device according to item 1.
5. The operation check support device is further equipped.
   It is provided with an input / output condition acquisition unit that acquires an input / output condition that is a range or value of at least one of the input value and the output value output by the operation program.
   The analysis unit
   Any one of claims 1 to 4, which uses the determination formula generated by the inspection condition conversion unit to generate a generated value as the input value that satisfies the input / output conditions and reaches the target arrival point. The operation confirmation support device according to item 1.
6. The analysis unit
   The operation confirmation support device according to any one of claims 1 to 5, which notifies that the input value for reaching the target arrival point could not be generated.
7. The program information acquisition unit
   An AST program created by an AST (Abstract Syntax Tree) including a node or a branch as the operation program is acquired, the AST program is converted into an AST code which is a source code of the AST program, and the AST code is converted into the operation. Get as code,
   The inspection condition acquisition unit
   The node or branch indicating the target arrival point is acquired as the inspection condition, and the inspection condition is acquired.
   The inspection condition conversion unit
   The line number of the operation code corresponding to the node or branch of the inspection condition is extracted.
   The operation confirmation support device according to any one of claims 1 to 6, which generates a target achievement condition expression that is satisfied when the line number of the operation code is reached as the determination expression.
8. The program information acquisition unit
   The state transition program created in the state transition diagram including the node or edge is acquired as the operation program, the state transition program is converted into the state transition code which is the source code of the state transition program, and the state transition code is converted into the state transition code. Obtained as the above operation code
   The inspection condition acquisition unit
   The node or edge indicating the target arrival point is acquired as the inspection condition, and the inspection condition is acquired.
   The inspection condition conversion unit
   The line number of the operation code corresponding to the node or edge of the inspection condition is extracted, and the line number is extracted.
   The operation confirmation support device according to any one of claims 1 to 6, which generates a target achievement condition expression that is satisfied when the line number of the operation code is reached as the determination expression.
9. The computer
   Get the operation code which is the source code of the operation program that operates by reading the input value.
   Obtain information about the target arrival point including the target arrival point of the operation code as an inspection condition, and obtain the information.
   A determination formula for determining that the target reached point included in the inspection conditions has been reached is generated.
   An operation confirmation support method for generating a generated value as the input value for reaching the target arrival point using the determination formula.
10. Program information acquisition process to acquire the operation code which is the source code of the operation program that reads the input value and operates,
    The inspection condition acquisition process for acquiring information about the target arrival point including the target arrival point of the operation code as an inspection condition, and
    An inspection condition conversion process for generating a determination formula for determining that a target reached point included in the inspection condition acquired by the inspection condition acquisition process has been reached, and an inspection condition conversion process.
    An operation confirmation support program for causing a computer to execute an analysis process for generating a generated value as an input value for reaching the target arrival point using the determination formula generated by the inspection condition conversion process.

Images