Operation log analysis device and operation log analysis method

Abstract

An operation log analysis device according to an embodiment comprises an operation log acquisition unit, a reference table generation unit, a mapping unit, and a determination unit. The operation log acquisition unit acquires a first operation log in which a plurality of first operations that serve as references are recorded, and a second operation log in which a plurality of second operations that serve as targets are recorded. The reference table generation unit generates a reference table in which the presence of the plurality of first operations is recorded for each type of the plurality of first operations. The mapping unit maps the presence or the absence of the plurality of second operations to the reference table for each type of the plurality of first operations. The determination unit determines the presence or the absence of the plurality of second operations for each type of the plurality of first operations in the mapped reference table.

Description

Operation Log Analysis Device and Operation Log Analysis Method

[0001] The present invention relates to an operation log analysis device and an operation log analysis method.

[0002] In business analysis, there is a technique for analyzing a history (hereinafter referred to as "operation log") that records a plurality of operations performed by an operator. In this technique (i.e., task mining), the operations of an operator are decomposed into a plurality of tasks, and problems for each task (e.g., inefficient operations, bottlenecks, repetitive operations) are discovered. By this discovery, the behavior or business flow of the operator can be improved.

[0003] In the prior art, an operation log (hereinafter referred to as "reference log") that records a plurality of reference operations is compared with an operation log (hereinafter referred to as "target log") that records a plurality of target operations. By this comparison, it is possible to quantify, as a similarity, in which part of the target log an operation similar to the reference log appears (see, for example, Patent Document 1 and Patent Document 2).

[0004] International Publication No. 2020 / 250320 International Publication No. 2022 / 176333

[0005] However, in the prior art, it is not possible to determine which operation in the reference log corresponds to the part with a high similarity in the target log (i.e., the correspondence relationship). Furthermore, even when a part of the operations in the reference log is not included in the target log (i.e., there is an operation omission), a high similarity is calculated. As a result, it is not possible to determine the operation omission in the target log.

[0006] An object of the present invention is to determine the correspondence relationship of operations between a reference log and a target log.

[0007] The operation log analysis device according to the embodiment comprises an operation log acquisition unit, a reference table generation unit, a mapping unit, and a determination unit. The operation log acquisition unit acquires a first operation log recording a plurality of reference first operations and a second operation log recording a plurality of target second operations. The reference table generation unit generates a reference table recording the existence of each of the plurality of first operations. The mapping unit maps the existence or non-existence of each of the plurality of second operations to the reference table for each of the plurality of first operations. The determination unit determines the existence or non-existence of each of the plurality of second operations for each of the plurality of first operations in the mapped reference table.

[0008] According to the present invention, the correspondence between operations can be determined between a reference log and a target log.

[0009] Figure 1 is a diagram showing the functional configuration of the operation log analysis device. Figure 2 is a flowchart showing the operation of the operation log analysis device. Figure 3 is a diagram showing user screen operations. Figure 4 is a diagram showing operation logs for user screen operations. Figure 5 is a diagram showing a reference table. Figure 6 is a diagram showing a mapped reference table. Figure 7 is a diagram showing a graph of execution times for tasks. Figure 8 is a diagram showing a graph of execution times for tasks. Figure 9 is a diagram showing a status table for task execution status. Figure 10 is a diagram showing an overview of task execution status. Figure 11 is a diagram showing an animation of task execution status. Figure 12 is a diagram showing a reference table for another example. Figure 13 is a diagram showing a mapped reference table for another example. Figure 14 is a diagram showing a graph of execution times for tasks for another example. Figure 15 is a diagram showing the hardware configuration of the operation log analysis device.

[0010] The embodiments will be described below with reference to the drawings. Multiple parts assigned the same reference numeral will be considered identical, and redundant explanations will be omitted as appropriate.

[0011] Figure 1 shows the functional configuration of the operation log analysis device 1. The operation log analysis device 1 is a device that analyzes operation logs OL. The operation log analysis device 1 comprises an operation log acquisition unit 11, an operation log storage unit 12, an operation log selection unit 13, an operation association unit 14, a determination unit 15, and an output unit 16 as its respective functional units.

[0012] The operation log acquisition unit 11 is a means for acquiring the operation log OL. The operation log acquisition unit 11 acquires a first operation log (i.e., a reference log RL) which records a plurality of reference first operations. The operation log acquisition unit 11 acquires a second operation log (i.e., a target log TL) which records a plurality of target second operations. The operation log acquisition unit 11 may acquire the operation log OL from outside the operation log analysis device 1. The operation log acquisition unit 11 transmits the acquired operation log OL to the operation log storage unit 12.

[0013] The operation log storage unit 12 is a means for storing operation logs OL. The operation log storage unit 12 may also be a database. The operation log storage unit 12 stores the operation logs OL acquired by the operation log acquisition unit 11. The operation log storage unit 12 transmits the operation logs OL selected by the operation log selection unit 13 to the operation log selection unit 13.

[0014] The operation log selection unit 13 is a means for selecting operation logs OL. The operation log selection unit 13 selects two operation logs OL to be compared (i.e., the reference log RL and the target log TL) from among the multiple operation logs OL stored in the operation log storage unit 12. The operation log selection unit 13 transmits the two selected operation logs OL to the operation association unit 14.

[0015] For example, the operation log selection unit 13 selects the veteran worker's operation log OL as the reference log RL and the new worker's operation log OL as the target log TL. By comparing the two selected operation logs OL, it is possible to confirm whether the new worker performed the operations and executed the work without any omissions, just like the veteran worker.

[0016] The operation association unit 14 is a means for performing operation association. The operation association unit 14 associates operations in the reference log RL with operations in the target log TL. The operation association unit 14 includes a reference table generation unit 14A and a mapping unit 14B.

[0017] The reference table generation unit 14A is a means for generating the reference table RT. The reference table generation unit 14A generates a reference table RT that records the existence of multiple first operations for each type of multiple first operations in the reference log RL. The reference table generation unit 14A transmits the generated reference table RT to the mapping unit 14B.

[0018] The mapping unit 14B is a means for performing mapping. The mapping unit 14B maps the presence or absence of multiple second operations in the target log TL for each type of multiple first operations in the reference log RL to the reference table RT. The mapping unit 14B may also map the time (i.e., execution time) when the multiple second operations were performed for each type of multiple first operations to the reference table RT. The mapping unit 14B transmits the mapped reference table RTM to the determination unit 15.

[0019] The determination unit 15 is a means for performing a determination. The determination unit 15 determines, in the mapped reference table RTM, the existence or non-existence of multiple second operations in the target log TL for each type of multiple first operations in the reference log RL. The determination unit 15 may determine that a task related to the multiple first operations has been performed if the existence of multiple second operations is mapped to multiple first operations. The determination unit 15 may also determine that a task related to the multiple first operations has been performed if each of the execution times in which the multiple second operations were performed falls within a predetermined time range. The determination unit 15 transmits the determination result RU to the output unit 16.

[0020] The output unit 16 is a means for performing output. The output unit 16 converts the judgment result RU into a predetermined data format and outputs it. The output unit 16 may convert the judgment result RU into a displayable data format (e.g., image data, video data). The output unit 16 may also cause an output device (e.g., a display device) to output the judgment result RU.

[0021] Figure 2 is a flowchart showing the operation of the operation log analysis device 1. Through steps S1 to S7, the operation log analysis device 1 determines the correspondence between operations between the reference log RL and the target log TL.

[0022] (Step S1) First, the operation log acquisition unit 11 acquires the reference log RL and the target log TL. For example, the operation log acquisition unit 11 acquires operation information related to operations (e.g., clicks, key inputs) performed by a user (e.g., an operator) on the terminal screen. The operation log acquisition unit 11 acquires the operation log OL by associating the operation information with each type of operation. The operation log OL is used as the reference log RL or the target log TL (see Figures 3 and 4).

[0023] (Step S2) Next, the operation log acquisition unit 11 stores the reference log RL and target log TL acquired in step S1 in the operation log storage unit 12. Steps S1 and S2 may be repeated. As a result, the operation log storage unit 12 stores a large number of operation logs OL.

[0024] (Step S3) Next, the operation log selection unit 13 selects a reference log RL and a target log TL to be compared from the multiple operation logs OL saved in step S2. For example, the operation log selection unit 13 selects an arbitrary reference log RL and a target log TL from the operation log storage unit 12 in response to an operation entered by the user through an input device. At this time, a list of operation logs OL stored in the operation log storage unit 12 may be displayed on the screen of the user's terminal. The user may select an arbitrary operation log OL from the displayed list.

[0025] (Step S4) Next, the reference table generation unit 14A generates a reference table RT from the reference log RL selected in step S3. For example, the reference table generation unit 14A sets a flag (e.g., 1) indicating the existence of an operation for each type of operation in the reference log RL. The reference table generation unit 14A may repeat a similar operation for each task in the reference log RL. The reference table generation unit 14A may also set a flag (e.g., 0) indicating the absence of an operation. In this way, the reference table generation unit 14A generates the reference table RT by modeling the reference log RL in a format that can be compared for each task and each operation (see Figure 5).

[0026] (Step S5) Next, the mapping unit 14B maps the operation information of the target log TL selected in step S3 to the reference table RT generated in step S4. For example, the mapping unit 14B maps a flag (e.g., 1, 0) indicating the presence or absence of an operation in the target log TL for each type of operation in the reference table RT. The mapping unit 14B may also map the execution time of the operation in the target log TL for each type of operation in the reference table RT (see Figure 6).

[0027] (Step S6) Next, the determination unit 15 determines the correspondence of operations in the reference table RTM mapped in step S5. For example, the determination unit 15 determines whether the operation exists or does not exist in the target log TL for each type of operation in the reference table RTM. The determination unit 15 focuses on operations in the reference table RTM for which a flag "1" indicating the existence of the operation in the reference log RL is set. The determination unit 15 determines whether or not a flag "1" indicating the existence of the operation in the target log TL is mapped to the said operation. If it is mapped (YES), the determination unit 15 determines that the operation has been executed. If it is not mapped (NO), the determination unit 15 determines that the operation has not been executed (i.e., there is an operation omission) (see Figure 6).

[0028] The determination unit 15 may determine whether the existence of multiple operations in the target log TL is mapped to multiple operations in the reference log RL. If it is mapped (YES), the determination unit 15 may determine that the task related to the multiple operations in the reference log RL has been executed. If it is not mapped (NO), the determination unit 15 may determine that the task has not been executed.

[0029] The determination unit 15 may determine whether each execution time of an operation in the target log TL falls within a predetermined time range (e.g., 1 hour). If each execution time falls within the predetermined time range (YES), the determination unit 15 may determine that tasks related to multiple operations in the reference log RL have been executed. If at least one execution time falls outside the predetermined time range (NO), the determination unit 15 may determine that the task has not been executed (see Figures 7 and 8).

[0030] (Step S7) Finally, the output unit 16 outputs the judgment result RU obtained in step S6. For example, the output unit 16 outputs the task execution status as the judgment result RU in a predetermined data format (e.g., image data, video data) (see Figures 9, 10, and 11).

[0031] Figure 3 shows a user's screen operations. For example, to set up an arbitrary tool, the user performs three tasks (Task 1, Task 2, Task 3) in sequence on the terminal screen, performing a total of 15 operations (Operation 1 to Operation 15) in sequence. Each of the 15 operations is a click on a button, a change in a value in a select box, etc.

[0032] In Task 1, the user performs operations 1 through 5 on screen A and operations 6 through 8 on screen B to configure app A. In Task 2, the user performs operations 9 through 10 on screen C and operations 11 through 13 on screen D to configure app B. In Task 3, the user performs operations 14 through 15 on screen E to configure browser C.

[0033] Figure 4 shows the operation log OL1 for user screen operations. Operation log OL1 records operation information for each type of operation (also called operation ID). For example, the operation information includes the following: time, application information, screen information, URL (Uniform Resource Locator), operation location, operation command, operation position, and input value. The time is the time the operation was performed. The application information is the application used for the operation. The screen information is the screen on which the operation was performed. The URL is the address of that screen. The operation location is the location where the operation was performed. The operation command is the content of the operation. The operation position is the location (especially the coordinates) where the operation was performed. The input value is the value entered during the operation. The operation information may also include a captured image of the screen during the operation.

[0034] Figure 5 shows the reference table RT1. The reference table RT1 records the presence ("1") or absence ("0") of each of the 15 operations (operations 1 to 15) in the operation log OL1 for each task. The same task may include operations on multiple different screens (e.g., screen A and screen B of task 1). In this case, the reference table RT1 may divide one task into multiple subtasks. Alternatively, the reference table RT1 may record the presence or absence of operations for each screen.

[0035] The reference table RT1 records five tasks (T1A, T1B, T2A, T2B, T3). Task T1A corresponds to operations 1 to 5 in Task 1. Task T1B corresponds to operations 6 to 8 in Task 1. Task T2A corresponds to operations 9 to 10 in Task 2. Task T2B corresponds to operations 11 to 13 in Task 2. Task T3 corresponds to operations 14 to 15 in Task 3.

[0036] Figure 6 shows the mapped reference table RTM1. For multiple operations in the target log TL, the reference table RTM1 records the presence ("1") or absence ("0") of the operation and the execution time of the operation for each task. The reference table RTM1 may also record the presence or absence of multiple operations in the reference log RL for each task.

[0037] For each of the five operations (operations 1 to 5) in task T1A, the existence value "1" for each operation in the target log TL is mapped. Therefore, the determination unit 15 determines that task T1A was executed. The determination unit 15 may also determine whether task T1A was executed based on the execution time of the mapped operations (see Figure 7).

[0038] The existence of the operations in the target log TL is mapped to the three operations (operations 6 to 8) in task T1B. Therefore, the determination unit 15 determines that task T1B has been executed.

[0039] Two operations (operations 9 and 10) in task T2A are mapped to the existence of operations "1" in the target log TL. Therefore, the determination unit 15 determines that task T2A was executed. The determination unit 15 may also determine whether task T2A was executed based on the execution time of the mapped operations (see Figure 8).

[0040] For the three operations (operations 11 to 13) in task T2B, the absence of operations ("0") in the target log TL is mapped. Therefore, the determination unit 15 determines that task T2B has not been executed.

[0041] For the two operations in task T3 (operations 14 and 15), the presence ("1") and non-existence ("0") of the operations in the target log TL are mapped, respectively. Therefore, the determination unit 15 determines that task T3 has not been executed. The determination unit 15 may also determine that operation 14 has been executed and operation 15 has not been executed.

[0042] Figure 7 shows graph G1A of the execution times for task T1A. Graph G1A shows the execution times for each type of operation (operations 1 to 5) in the reference table RTM1 along the time axis. Graph G1A records multiple execution times for each type of operation.

[0043] For example, the determination unit 15 determines whether five operations have been executed within one hour. The determination unit 15 extracts the latest execution time (e.g., 2024 / 12 / 05 12:xx) from each of the five operations. The determination unit 15 determines that each of the extracted latest execution times is within one hour (YES). That is, the determination unit 15 determines that the five operations have been executed continuously in time, and determines that the task T1A related to the five operations has been executed.

[0044] FIG. 8 is a diagram showing a graph G2A of execution times for task T2A. The graph G2A shows the execution times for each type of operation for two operations (operation 9 to operation 10) in the reference table RTM1 along the time axis. The graph G2A records one execution time for each type of operation.

[0045] For example, the determination unit 15 determines whether two operations have been executed within one hour. The determination unit 15 extracts the latest execution time (e.g., 2024 / 12 / 05 9:xx, 2024 / 12 / 05 15:xx) from each of the two operations. The determination unit 15 determines that each of the extracted latest execution times is not within one hour (NO). That is, the determination unit 15 determines that the two operations have not been executed continuously in time, and determines that the task T2A related to the two operations has not been executed.

[0046] As described above, the determination unit 15 determines whether a task related to a plurality of operations has been executed based on the continuity of the execution times of the plurality of operations. The determination unit 15 can prevent erroneously determining that a task has been executed due to accidentally gathered temporally discontinuous operations.

[0047] FIG. 9 is a diagram showing a situation table ST for the execution status of a task. The situation table ST displays the character "executed" indicating that the task has been executed and the character "not executed" indicating that the task has not been executed. Each of the two characters is surrounded by a dashed box. The dashed box is arranged for the corresponding task.

[0048] The status table ST colors the fields (or cells) corresponding to the executed operations and does not color the fields (or cells) corresponding to the unexecuted operations. By referring to the status table ST, the user can immediately understand the executed tasks (or operations) and the unexecuted tasks (or operations).

[0049] In Case 1, five tasks (T1A, T1B, T2A, T2B, T3) are executed. In Case 2, two tasks (T1A, T2A) are executed and three tasks (T1B, T2B, T3) are not executed. In Case 3, three tasks (T1A, T2A, T2B) are executed and two tasks (T1B, T3) are not executed. In Case 3-t1 and Case 3-t2, two tasks (T2A, T2B) are executed and three tasks (T1A, T1B, T3) are not executed. In Case 3-t3, three tasks (T1A, T2A, T2B) are executed and two tasks (T1B, T3) are not executed. In Case 4, five tasks (T1A, T1B, T2A, T2B, T3) are not executed.

[0050] In Case 3-t1, Operations 1 to 2 of the unexecuted task T1A are executed and Operations 3 to 5 are not executed. In Case 3-t2, Operations 3 to 5 of the unexecuted task T1A are executed and Operations 1 to 2 are not executed. Thus, the user can understand some of the operations executed in the unexecuted tasks.

[0051] FIG. 10 is a diagram showing an overview OV of the execution status of tasks. The overview OV colors the operations executed on five screens (Screens A to E) and does not color the unexecuted operations. By referring to the overview OV, the user can immediately understand the operations executed and the unexecuted operations on each screen.

[0052] In Overview OV1 shown in Figure 10(A), 15 operations (operations 1 to 15) are performed. In Overview OV2 shown in Figure 10(B), 8 operations (operations 1 to 5, operations 9 to 10, operation 14) are performed across three screens (screens A, C, and E). On the other hand, 7 operations (operations 6 to 8, operations 11 to 13, operation 15) are not performed across three screens (screens B, D, and E). Overviews OV1 and OV2 correspond to Case 1 and Case 2, respectively (see Figure 9).

[0053] Figure 11 shows an animation AN representing the task execution status. The animation AN displays multiple operations performed on five screens (screens A to E) in sequence. The multiple operations may be displayed in sequence over time, or in response to user actions. By referring to the animation AN, the user can understand the multiple operations performed on each screen in sequence.

[0054] In animation AN1 shown in Figure 11(A), two operations (operations 14 and 15) on screen E are displayed in sequence. In the first scene, it is shown, along with an explanatory text, that "AAA" has been entered at a predetermined position on the screen as operation 14. In the next scene, it is shown, along with an explanatory text, that "BBB" has been entered at a different position on the screen as operation 15. Animation AN1 corresponds to Example 1 (see Figure 9).

[0055] In animation AN2 shown in Figure 11(B), one operation (operation 14) on screen E is displayed. The details of operation 14 are shown in a manner similar to animation AN1. Since the next operation 15 has not been performed, the next scene is not displayed. Animation AN2 corresponds to Example 2 (see Figure 9).

[0056] According to the embodiment described above, the operation log analysis device 1 can determine the correspondence between operations between the reference log RL and the target log TL. As a result, the operation log analysis device 1 can determine whether or not the target log TL sufficiently contains the multiple operations that constitute the reference log RL (i.e., whether or not there are any missing operations).

[0057] (Another example) Figure 12 shows a reference table RT2 relating to an alternative example. The reference table RT2 records the presence ("1") or absence ("0") of each task for 15 operations (operations 1 to 15) in the operation log OL1. In the reference table RT2, multiple tasks (e.g., T5 and T7) include the same operation (e.g., operation 1, operation 3).

[0058] The reference table RT2 records four tasks (T5, T6, T7, T8). Task T5 corresponds to operations 1 to 5. Task T6 corresponds to operations 6 to 8. Task T7 corresponds to operations 1, 3, and 9 to 10. Task T8 corresponds to operations 11 to 13. The three tasks T5, T6, and T8 are similar to the three tasks T1A, T1B, and T2B, respectively (see Figure 5).

[0059] Figure 13 shows a mapped reference table RTM2 in another example. For multiple operations in the target log TL, the reference table RTM2 records the existence ("1") or non-existence ("0") of the operation and the execution time of the operation for each task.

[0060] The existence of each operation ("1") in the target log TL is mapped to the five operations (operations 1 to 5) in task T5. Therefore, the determination unit 15 determines that task T5 has been executed. The determination unit 15 may also determine that task T5 has been executed in the same way as task T1A (see Figure 7).

[0061] For the four operations in task T7 (operations 1, 3, 9, and 10), the existence value "1" for each operation in the target log TL is mapped. Therefore, the determination unit 15 determines that task T7 was executed. The determination unit 15 may also determine whether task T7 was executed based on the execution time of the mapped operations (see Figure 14).

[0062] Figure 14 shows graph G7 of the execution times for task T7 in a different example. Graph G7 shows the execution times for each type of operation (operation 1, operation 3, operation 9, operation 10) in the reference table RTM2 along the time axis.

[0063] For example, the determination unit 15 determines whether the four operations were performed within one hour. The determination unit 15 sets a one-hour time range for the execution time. The determination unit 15 moves the time range along the time axis and determines whether the execution times of the four operations are included within the time range. The determination unit 15 determines that the execution times of the four operations are included within the time range in the vicinity of the execution time (2024 / 12 / 05 8:00) (YES). In other words, the determination unit 15 determines that the four operations were performed consecutively in time and that task T7 related to the four operations was performed.

[0064] As described above, the determination unit 15 determines whether or not a task has been executed for each task. The determination unit 15 can prevent incorrectly determining that a task has been executed based on the execution history of operations related to another task.

[0065] Figure 15 shows the hardware configuration of the operation log analysis device 1. The operation log analysis device 1 comprises a CPU 101, RAM 102, ROM 103, storage 104, display device 105, input device 106, and communication device 107 as its components. Each component is connected to the others via an internal bus so as to be able to communicate with each other. The operation log analysis device 1 may include at least one of each component.

[0066] The CPU 101 is a processor that executes various processes according to a program. The CPU 101 uses a predetermined area of ​​the RAM 102 as a working area. The CPU 101 realizes each processing unit (e.g., operation log acquisition unit 11, operation log selection unit 13, operation association unit 14, reference table generation unit 14A, mapping unit 14B, determination unit 15, output unit 16) by reading and executing each program stored in the ROM 103 or storage 104. Each processing unit may be realized by a dedicated hardware circuit (e.g., ASIC). The CPU 101 is an example of a processing unit.

[0067] RAM 102 is a memory that stores various types of data in a rewritable format. RAM 102 is an SDRAM (Synchronous Dynamic Random Access Memory), etc. ROM 103 is a memory that stores various types of data in a non-rewritable format. Storage 104 is various types of storage media. Storage 104 may also be a drive device that writes or reads various types of data to or from the storage media. Storage 104 may write or read various types of data to or from the storage media in accordance with control by the CPU 101. RAM 102, ROM 103, or storage 104 are examples of storage units (e.g., operation log storage unit 12).

[0068] The display device 105 is a device that displays various images. The display device 105 is an LCD (Liquid Crystal Display), etc. The display device 105 displays various images based on display signals from the CPU 101. The display device 105 is an example of a display unit (e.g., output unit 16).

[0069] The input device 106 is a device that receives various input operations from the user. The input device 106 is a mouse, keyboard, etc. The input device 106 receives the operations entered by the user as instruction signals and transmits the received instruction signals to the CPU 101. The input device 106 is an example of an input unit.

[0070] The communication device 107 is a device that communicates with external devices via a network in accordance with the control of the CPU 101. The communication device 107 is an example of a communication unit.

[0071] Each embodiment of the present invention is presented as an example and does not limit the scope of the invention. Each embodiment can be carried out in various forms without departing from the spirit of the invention. Each embodiment may be combined with one another, in which case the combined effects can be obtained. Each embodiment includes a plurality of components, and various inventions can be obtained by various combinations of the plurality of components. Each embodiment or each combination of components is included within the scope of the invention.

[0072] 1... Operation log analysis device, 11... Operation log acquisition unit, 12... Operation log storage unit, 13... Operation log selection unit, 14... Operation association unit, 14A... Reference table generation unit, 14B... Mapping unit, 15... Judgment unit, 16... Output unit, 101... CPU, 102... RAM, 103... ROM, 104... Storage, 105... Display device, 106... Input device, 107... Communication device, AN... Animation, G... Graph, OL... Operation log, OV... Overview, RL... Reference log, RT... Reference table, RU... Judgment result, ST... Status table, T... Task, TL... Target log

Claims

1. An operation log analysis device comprising: an operation log acquisition unit that acquires a first operation log recording a plurality of standard first operations and a second operation log recording a plurality of target second operations; a standard table generation unit that generates a standard table recording the existence of the plurality of first operations for each type of the plurality of first operations; a mapping unit that maps the existence or non-existence of the plurality of second operations for each type of the plurality of first operations to the standard table; and a determination unit that determines the existence or non-existence of the plurality of second operations for each type of the plurality of first operations in the mapped standard table.

2. The operation log analysis device according to claim 1, wherein the determination unit determines that a task relating to the plurality of first operations has been performed if the existence of the plurality of second operations is mapped to the plurality of first operations.

3. The operation log analysis device according to claim 1, wherein the mapping unit maps the execution times of the plurality of second operations to the reference table for each type of the plurality of first operations, and the determination unit determines that a task related to the plurality of first operations has been executed if the existence of the plurality of second operations is mapped to the plurality of first operations and each of the execution times is within a predetermined time range.

4. An operation log analysis method comprising: a computer acquiring a first operation log recording a plurality of reference first operations and a second operation log recording a plurality of target second operations; generating a reference table for each type of plurality of first operations that records the existence of the plurality of first operations; mapping the existence or non-existence of the plurality of second operations for each type of plurality of first operations to the reference table; and determining the existence or non-existence of the plurality of second operations for each type of plurality of first operations in the mapped reference table.

Images