JP2021149489A - Business visualization apparatus, business visualization method and program - Google Patents

Abstract

To highly efficiently acquire necessary parts of business specifications.SOLUTION: A business visualization apparatus includes a main key extraction section for extracting a position of a main key of an object table based on a table layout information, an event log generation section for extracting a history record of the table including the main key based on the position of the main key from update history information including a plurality of history records when a business process is implemented and generating an event log including the event record formed by associating the extracted history record and main key information representing a value of the main key, a divided log generation section for extracting an event record from the event log, in which processing type information represents a start of the processing, table identification information is the object table and the main key information is included, the main key information including the value of the business state of the object table representing the termination of the business, and generating divided event logs formed by collecting for every value of the business state, and business flow generation section generating a business flow based on the divided event logs for every value of the game states.SELECTED DRAWING: Figure 1

Description

The present invention relates to a business visualization device, a business visualization method, and a program.

In recent years, a technique for visualizing a business process by using a process mining technique has been known (see, for example, Patent Document 1). Such a technology for visualizing a business process is used for grasping business specifications by visualizing the business process based on the execution log of the business system.

Japanese Unexamined Patent Publication No. 2017-187953

However, with the above-mentioned technology for visualizing business processes, it is difficult to efficiently grasp the necessary parts of business specifications because the processing of a huge and complicated business system is visualized.

The present invention has been made to solve the above problems, and an object of the present invention is to provide a business visualization device, a business visualization method, and a program capable of efficiently grasping a necessary part of a business specification.

In order to solve the above problem, one aspect of the present invention is a primary key extraction unit that extracts a predetermined position of a primary key of a target table in the table based on table layout information that defines an array of tables. , Date and time information when a business process is executed, function identification information for identifying a function included in the business process, table identification information for identifying the table to be processed in the function, and a type of processing for the table. Based on the position of the primary key extracted by the primary key extraction unit from the update history information including a plurality of history records in which the processing type information indicating the above and the table information stored in the table are associated with each other, the primary key is selected. An event log generation unit that extracts the history record for the including table and generates an event log including an event record in which the extracted history record and the primary key information indicating the value of the primary key are associated with each other, and the event log generation unit. From the event log generated by, the processing type information indicates the start of processing, the table identification information is the target table, and the business status value of the target table indicates the end of business. A divided log generation unit that extracts the event record including the primary key information and generates a divided event log collected for each value of the business state, and a divided log generation unit generated by the divided log generation unit for each value of the business state. It is a business visualization device characterized by including a business flow generation unit that generates a business flow that visualizes the business process based on a divided event log.

Further, in one aspect of the present invention, in the above-mentioned business visualization device, the event log generated by the event log generation unit is used as the first event log, and the division log generation unit uses the first event log as the first event log. A start extraction unit that extracts the event record including the primary key information whose processing type information indicates the start of processing and generates a second event log summarizing the extracted event records, and the second event log. The target table extraction unit that extracts the event record whose table identification information indicates the target table and generates a third event log summarizing the extracted event records, and the target table that has been acquired in advance. From the table data, the primary key information included in the record in which the value of the business state indicates the end of the business is extracted, and the event records including the extracted primary key information are collected from the third event log. It is characterized by including an end extraction unit that generates the divided event log.

Further, one aspect of the present invention is the number of appearances of the function and the number of patterns of the immediately preceding function executed immediately before the function indicated by the function identification information included in the divided event log in the business visualization device. Based on the above, it is determined whether or not the function is a general-purpose function that can be executed regardless of the main flow of the business flow, and the divided event log includes the function identification information indicating the general-purpose function. The business flow generation unit includes a general-purpose function exclusion unit that excludes the event record, and the business flow generation unit is based on the divided event log in which the general-purpose function exclusion unit excludes the event record including the function identification information indicating the general-purpose function. The business flow is generated.

Further, one aspect of the present invention is that in the above-mentioned business visualization device, the general-purpose function exclusion unit is an index of the general-purpose function based on the number of appearances of the function and the number of patterns of the immediately preceding function. Is calculated, and when the calculated general-purpose degree is equal to or higher than a predetermined threshold value, the function is determined to be the general-purpose function.

Further, one aspect of the present invention is executed in the business visualization device after the specific function, which is the function related to the main flow of the business flow, is executed for each of the general-purpose functions by aggregating the divided event logs. It is characterized by including an appearance frequency generation unit that generates appearance frequency information indicating the appearance frequency.

Further, one aspect of the present invention is a primary key extraction step in which the primary key extraction unit extracts the position of the primary key of a predetermined target table in the table based on the table layout information that defines the arrangement of the tables. , The event log generation unit includes date and time information when the business process is executed, function identification information for identifying the function included in the business process, and table identification information for identifying the table to be processed in the function. At the position of the primary key extracted by the primary key extraction step from update history information including a plurality of history records in which processing type information indicating the type of processing for the table and table information stored in the table are associated with each other. Based on this, an event log generation step of extracting the history record for the table including the primary key and generating an event log including an event record in which the extracted history record is associated with the primary key information indicating the value of the primary key. Then, the divided log generation unit indicates that the processing type information starts processing from the event logs generated by the event log generation step, and the table identification information is the target table. A split log generation step that extracts the event record including the primary key information whose business status value of the target table indicates the end of business and generates a split event log summarized for each business status value, and a business. The flow generation unit is characterized by including a business flow generation step that generates a business flow that visualizes the business process based on the division event log for each value of the business state generated by the division log generation step. It is a business visualization method to be performed.

Further, one aspect of the present invention includes a primary key extraction step of extracting a predetermined primary key position of a target table in the table based on table layout information defining an array of tables, and a business process. Date and time information, function identification information for identifying the function included in the business process, table identification information for identifying the table to be processed in the function, and processing indicating the type of processing for the table. A table including the primary key based on the position of the primary key extracted by the primary key extraction step from update history information including a plurality of history records in which the type information and the table information stored in the table are associated with each other. An event log generation step that extracts the history record for and generates an event log including an event record in which the extracted history record and the primary key information indicating the value of the primary key are associated with each other, and an event log generation step that generates the event log. From the event log, the processing type information indicates the start of processing, the table identification information is the target table, and the business status value of the target table indicates the end of business. A split log generation step that extracts the event record including the primary key information and generates a split event log summarized for each business state value, and a split log generation step generated by the split log generation step for each business status value. This is a program for executing a business flow generation step that generates a business flow that visualizes the business process based on the divided event log.

According to the present invention, it is possible to efficiently grasp the necessary parts of the business specifications.

It is a block diagram which shows an example of the business visualization apparatus by 1st Embodiment. It is a figure which shows the data example of the journal log in 1st Embodiment. It is a figure which shows an example of the table data of the target table in 1st Embodiment. It is a figure which shows the data example of the primary key layout storage part in 1st Embodiment. It is a figure which shows the data example of the event log in 1st Embodiment. It is a figure which shows an example of the extraction process of the position of the primary key in 1st Embodiment. It is a figure which shows an example of the event log generation processing in 1st Embodiment. It is a figure which shows an example of the extraction process of the record of CaseID including the start of the process of the target table in 1st Embodiment. It is a figure which shows an example of the extraction process of the record of the target table in 1st Embodiment. It is a figure which shows an example of the generation process of the division event log for every business status in 1st Embodiment. It is a figure which shows an example of the generation process of the business flow in 1st Embodiment. It is a flowchart which shows an example of the operation of the business visualization apparatus in 1st Embodiment. It is a block diagram which shows an example of the business visualization apparatus by 2nd Embodiment. It is a figure which shows an example of the distribution processing of a general-purpose function and a specific function in the 2nd Embodiment. It is a figure explaining an example of the general-purpose generation processing in 2nd Embodiment. It is a figure which shows an example of the exclusion process of a general-purpose function and the generation process of a business flow in the 2nd Embodiment. It is a figure which shows an example of the generation processing of the appearance frequency information in 2nd Embodiment. It is a flowchart which shows an example of the operation of the business visualization apparatus in 2nd Embodiment. It is a figure which shows the display example of the business flow and the appearance frequency information in 2nd Embodiment.

Hereinafter, the business visualization device, the business visualization method, and the program according to the embodiment of the present invention will be described with reference to the drawings.

[First Embodiment]
FIG. 1 is a block diagram showing an example of the business visualization device 1 according to the first embodiment.
As shown in FIG. 1, the business visualization device 1 generates a business flow by using the journal log, the table layout group, the target table name, and the table data of the target table as input data. The business visualization device 1 includes a storage unit 10 and a control unit 20.

Before explaining the details of the configuration of the business visualization device 1, first, the input data input to the business visualization device 1 will be described.
In the present embodiment, the journal log is a database update log recorded when a business process is executed, and is an example of update history information. Here, an example of journal log data will be described with reference to FIG.

FIG. 2 is a diagram showing an example of journal log data according to the present embodiment.
As shown in FIG. 2, the journal log is a record in which "date and time", "function ID", "table name", "CRUD", ..., "Updated table information" are associated with each other. Contains multiple (history records).

In FIG. 2, the “date and time” is an example of date and time information, and the “function ID” is an example of function identification information for identifying a function included in a business process. Further, the "table name" is an example of table identification information that identifies a table to be processed in the function. "CRUD" is an example of processing type information indicating the type of processing for a table, for example, "Insert" (addition), "Select" (extraction), "Update" (update), and "Delete" (delete). Shown. "Updated table information" is table information stored in the table, and indicates, for example, table information at the time of update.

For example, in the example shown in FIG. 2, the "date and time" of the first record of the journal log is "2020/03/10 10:00:00", the "function ID" is "function A", and so on. Indicates that the "table name" is "table A". Further, it is shown that "CRUD" of this record is "Insert" (additional) and "updated table information" is "1234abcddefghjkl ...".

The table layout group is an example of table layout information including a plurality of table layouts in which an array of tables is defined. The table layout includes, for example, item names, data types, number of bytes (data length), information on primary keys, etc. for each table.

The target table name is a table name indicating the target table for visualizing the business process, and is predetermined by being input from the outside of the business visualization device 1. The target table is a table having at least a business status and a primary key. Here, the business status is information indicating the business status such as completion, cancellation, and execution.
In this embodiment, an example in which the target table name is “table A” will be described. Further, in the present embodiment, the value of the primary key of "Table A" is used as CaseID.

The table data of the target table is, for example, data acquired on another day after the journal log is acquired. The table data shall include the primary key and business status of the target table. In the present embodiment, the table data of "table A" is used as the table data of the target table. Here, an example of table data of the target table will be described with reference to FIG.

FIG. 3 is a diagram showing an example of table data of the target table in the present embodiment.
The example shown in FIG. 3 is an example of the table data of "table A", in which "CaseID" (primary key value), "XX day" (date information), and "business status" are associated with each other. There is. In the "business status", "1" indicates completion and "9" indicates cancellation. In addition, "0" indicates that it is in progress (ongoing).
For example, the table data in which "CaseID" is "1234" indicates that the business process is completed on the date of "yyyymdd".

Returning to the description of FIG. 1, the storage unit 10 stores various information used by the business visualization device 1. The storage unit 10 includes, for example, a primary key layout storage unit 11, an event log storage unit 12, a Case ID storage unit 13, a split event log storage unit 14, and a business flow storage unit 15.

The primary key layout storage unit 11 stores information indicating the position of the primary key of the target table in each table, which is extracted from the table layout group which is the input data. Here, a data example of the primary key layout storage unit 11 will be described with reference to FIG.

FIG. 4 is a diagram showing a data example of the primary key layout storage unit 11 in the present embodiment.
As shown in FIG. 4, the primary key layout storage unit 11 stores the "table name", the "CaseID item position", and the "CaseID item length" in association with each other.
Here, "table name" indicates the table name of each table, and "CaseID item position" indicates the position (for example, the position from the beginning) of the primary key item of the target table ("table A"). There is. Further, "CaseID item length" indicates the data length of the primary key.

For example, in the example shown in FIG. 4, the "table name" is "table A", the "caseID item position" is "1" (1st byte), and the "caseID item length" is "4" (4 bytes). It shows that there is.
Further, the "table name" indicates that the "CaseID item position" in the "table B" is "6" (6th byte), and the "CaseID item length" is "4" (4 bytes).

Further, the "table name" is "Table C", the "CaseID item position" is "Null", the "CaseID item length" is "Null", and the primary key of the target table ("Table A"). Indicates that it does not exist in "Table C".

Returning to the description of FIG. 1, the event log storage unit 12 stores the event log generated by the event log generation unit 22, which will be described later, based on the journal log described above and the information stored in the primary key layout storage unit 11. Remember. The event log includes, for example, a plurality of event records in which a journal log record (history record) and a CaseID (an example of primary key information) which is a value of the primary key of the target table (“table A”) are associated with each other. Is done. Here, an example of event log data will be described with reference to FIG.

FIG. 5 is a diagram showing an example of event log data according to the present embodiment.
As shown in FIG. 5, the event log has a plurality of event records in which "date and time", "function ID", "table name", "CRUD", ..., "CaseID" are associated with each other. Includes.

Here, "date and time", "function ID", "table name", "CRUD", ... Are the history records of the journal log, and "CaseID" is the target table ("table A". ") Indicates the value of the primary key. That is, in the event record of the event log, "CaseID" is added to the history record of the journal log.

For example, in the example shown in FIG. 5, the "date and time" is "2020/03/10 10:00:00", the "function ID" is "function A", and the "table name" is "table A". And "1234" of "CaseID" is added to the history record in which "CRUD" is "Insert" (additional).

Returning to the description of FIG. 1 again, the CaseID storage unit 13 stores a list of CaseIDs (primary key values) extracted from the event log. The CaseID storage unit 13 stores, for example, a list of "CaseIDs" in which "CRUD" is "Insert" in the event log.

The divided event log storage unit 14 stores the divided event log generated from the above-mentioned event log. The divided event log is an event log in which the event log is grouped according to the business status value and divided. In the split event log storage unit 14, the split log generation unit 23, which will be described later, determines that the business status value indicates the end of the business (for example, “1” (completed), “9” (cancelled), etc.) for each business status. Store the divided event log.

The business flow storage unit 15 stores the business flow generated by the business visualization device 1. Here, the business flow is, for example, a visualization of a business process such as BPMN (Business Process Model Notation), and stores the business flow generated for each business status by the business flow generation unit 24 described later.

The control unit 20 is, for example, a processor including a CPU (Central Processing Unit) and the like, and controls the business visualization device 1 in an integrated manner. The control unit 20 includes, for example, a primary key extraction unit 21, an event log generation unit 22, a division log generation unit 23, and a business flow generation unit 24.

The primary key extraction unit 21 extracts the position of the primary key of the target table (“table A”) in each table based on the table layout group (table layout information) which is the input data described above. Here, with reference to FIG. 6, the details of the process of extracting the position of the primary key of the target table (“table A”) in each table by the primary key extraction unit 21 will be described.

FIG. 6 is a diagram showing an example of the extraction process of the position of the primary key in the present embodiment.
FIG. 6A shows an example of the table layout group, and FIG. 6B shows information on the position of the primary key of the target table (“table A”) in each extracted table.
The primary key extraction unit 21 uses the primary key of "table A" as the Case ID, and sets the position of the primary key of "table A" as the "Case ID item position" and the "Case ID item length" from each table layout of the table layout group. Extract to generate a list of primary key positions as shown in FIG. 6 (b).

In the primary key extraction unit 21, for example, from the table layout TL1 of "table A" shown in FIG. 6A, the "CaseID item position" is "1" (1st byte) and the "CaseID item length" is "CaseID item length". It is extracted that it is 4 "(4 bytes), and is stored in the primary key layout storage unit 11 in association with" table A "of the" table name ". The primary key extraction unit 21 executes the same processing for each table to generate a list of primary key positions as shown in FIG. 6B, and stores the list in the primary key layout storage unit 11.

Returning to the description of FIG. 1, the event log generation unit 22 includes the primary key based on the position of the primary key extracted by the primary key extraction unit 21 from the journal log as shown in FIG. 2 which is the input data. Extract history records for the table. The event log generation unit 22 extracts a history record for the table including the primary key (CaseID) from the journal log based on the "CaseID item position" and "CaseID item length" of each table described above. The event log generation unit 22 associates the extracted history record with the CaseID (primary key information) indicating the value of the primary key to form an event record, and generates an event log including the event record. Here, the details of the event log generation process by the event log generation unit 22 will be described with reference to FIG. 7.

FIG. 7 is a diagram showing an example of the event log generation process in the present embodiment.
FIG. 7A shows the journal log L0, and FIG. 7B shows a list of the positions of the primary keys stored in the primary key layout storage unit 11.

For example, in "Table A", since the "CaseID item position" is "1" (1st byte) and the "CaseID item length" is "4" (4 bytes), the CaseID which is the value of the primary key is , "1234" of "1234abcdef ..." of "Updated table information". Therefore, the event log generation unit 22 extracts the history record whose "table name" is "table A" in the journal log L0, adds "1234" as the Case ID, and generates the event record.

Further, for example, in "Table B", the "CaseID item position" is "6" (6th byte) and the "CaseID item length" is "4" (4 bytes), so that it is the value of the primary key. The CaseID is "1234" of "abcde1234f ..." of "updated table information". Therefore, the event log generation unit 22 extracts the history record whose "table name" is "table B" in the journal log L0, adds "1234" as the CaseID, and generates the event record.

Further, for example, in "Table C", since "CaseID item position" and "CaseID item length" are "Null", the primary key of "Table A" does not exist. Therefore, the event log generation unit 22 excludes the history record of "table C" from the event log.
By processing in this way, the event log generation unit 22 generates the event log L1 (first event log) as shown in FIG. 7 (c), and the generated event log L1 is stored in the event log storage unit 12. Remember.

Returning to the description of FIG. 1 again, the split log generation unit 23 extracts event records satisfying the following extraction conditions from the event log L1 generated by the event log generation unit 22, and summarizes them for each business status value. Generate a split event log. Here, as for the extraction condition, "CRUD" (processing type information) indicates the start of processing (for example, "Insert"), and "table name" (table identification information) is the target table ("table A"). In addition, it is an event record including a CaseID in which the value of the business status of the target table (“table A”) indicates the end of business (for example, “1” (completed), “9” (cancelled), etc.). That is, the split log generation unit 23 extracts an event record for "table A" including a series of processes from the start to the end of the process from the event log L1 generated by the event log generation unit 22, and ends the event log L1. Generate a split event log for each type.

Further, the division log generation unit 23 stores the division event log collected for each business status value in the division event log storage unit 14.
Further, the divided log generation unit 23 includes a start extraction unit 231, a target table extraction unit 232, and an end extraction unit 233.

The start extraction unit 231 extracts from the event log L1 (first event log) an event record including a CaseID in which the above-mentioned "CRUD" indicates the start of processing (for example, "Insert"), and the extracted event. Generate an event log L2 (second event log) that summarizes the records. Here, with reference to FIG. 8, the case ID record extraction process including the start of the process by the start extraction unit 231 will be described.

FIG. 8 is a diagram showing an example of CaseID record extraction processing including the start of processing of the target table in the present embodiment.
FIG. 8A is an event log L1 (first event log) stored in the event log storage unit 12, and the start extraction unit 231 has an event record of the event log L1 in which “CRUD” is “Insert”. A certain event record is extracted, and the value of CaseID included in the event record is extracted as shown in FIG. 8 (b).

For example, in the event record of the first line of the event log L1 shown in FIG. 8A, “CRUD” is “Insert”, so that the start extraction unit 231 is “1234” which is the value of CaseID of the event record. Is extracted.
The start extraction unit 231 stores the list of CaseID values extracted in this way (FIG. 8B) in the CaseID storage unit 13.

Further, the start extraction unit 231 is shown in FIG. 8 (c) based on the event log L1 shown in FIG. 8 (a) and the list of Case ID values shown in FIG. 8 (b) stored in the Case ID storage unit 13. The event log L2 (second event log) as shown is generated.

For example, the start extraction unit 231 extracts all the event records including the value of CaseID shown in FIG. 8B from the event log L1, and collects the extracted event records into the event log L2 (second event log). Generate. That is, the start extraction unit 231 excludes the event record of CaseID that does not include "Insert" (there is no start) from the event log L1.

Returning to the description of FIG. 1 again, the target table extraction unit 232 extracted the event record whose table identification information indicates the target table from the event log L2 (second event log), and summarized the extracted event records. Generate event log L3 (third event log). That is, the target table extraction unit 232 extracts the event records corresponding to the target table “table A” and excludes the event records corresponding to the other tables. Here, with reference to FIG. 9, the process of extracting the records of the target table by the target table extraction unit 232 will be described.

FIG. 9 is a diagram showing an example of the record extraction process of the target table in the present embodiment.
FIG. 9A shows the event log L2 generated by the start extraction unit 231. The target table extraction unit 232 extracts the event record whose “table name” is “table A” from the event log L2. The extracted event records are put together to generate an event log L3 as shown in FIG. 9B. That is, the target table extraction unit 232 excludes event records other than "table A" from the event log L2.

Returning to the explanation of FIG. 1 again, the end extraction unit 233 sets the value of the business status from the table data of the target table (“table A”) acquired in advance to the end of the business (for example, “1” (completed)). , "9" (cancellation), etc.), and the Case ID included in the record is extracted. The end extraction unit 233 generates the divided event log L4 by collecting the event records including the extracted CaseID from the event log L3 (third event log) for each business status value. Here, with reference to FIG. 10, the process of generating the split event log for each business status by the end extraction unit 233 will be described.

FIG. 10 is a diagram showing an example of a split event log generation process for each business status in the present embodiment.
FIG. 10A shows the event log L3 (third event log) generated by the target table extraction unit 232, and FIG. 10B shows the table data TD1 of the input data “table A”. .. The end extraction unit 233 creates a divided event log L4 (L4-1, L4-2, ...) As shown in FIG. 10C based on the event log L3 (third event log) and the table data TD1. Generate.

The end extraction unit 233 extracts, for example, the value of "CaseID" (for example, "1234") corresponding to "1" (completion) in the "business status" in the table data TD1. The end extraction unit 233 extracts and summarizes the event records corresponding to the value "1234" of the "CaseID" from the event log L3, and divides the event log into "1" (completed). Generate event log L4-1.

Further, the end extraction unit 233 extracts, for example, the value of "CaseID" (for example, "5678") corresponding to "9" (cancellation) in the "business status" in the table data TD1. The end extraction unit 233 extracts and summarizes the event records corresponding to the value "5678" of the "CaseID" from the event log L3, and divides the event log into "9" (cancelled). Generate event log L4-1.

Further, the end extraction unit 233 stores the generated divided event log L4 (L4-1, L4-2, ...) In the divided event log storage unit 14. For example, the end extraction unit 233 stores the extracted event record in the divided event log storage unit 14 in association with the “business status” (see FIG. 10C).

Returning to the description of FIG. 1 again, the business flow generation unit 24 is based on the division event log L4 (L4-1, L4-2, ...) For each business status value generated by the division log generation unit 23. , Generate a business flow that visualizes the business process. The business flow generation unit 24 uses, for example, an existing process mining technique to generate a business flow such as BPMN for each value of the business status. Here, with reference to FIG. 11, the details of the business flow generation process by the business flow generation unit 24 will be described.

FIG. 11 is a diagram showing an example of a business flow generation process in the present embodiment.
FIG. 11A shows a division event log L4 (L4-1, L4-2, ...) Generated by the division log generation unit 23 (end extraction unit 233), and FIG. 11B shows a business flow. The business flow FL1, the business flow FL2, ... Generated by the generation unit 24 are shown.

For example, the end extraction unit 233 acquires the division event log L4-1 whose business status is “1” (completed) from the division event log storage unit 14, and obtains the business flow FL1 from the acquired division event log L4-1. Generate. Further, for example, the end extraction unit 233 acquires the division event log L4-2 whose business status is “9” (cancelled) from the division event log storage unit 14, and the business flow from the acquired division event log L4-2. Generate FL2.

The end extraction unit 233 stores the generated business flow FL1, business flow FL2, ... In the business flow storage unit 15.

Next, the operation of the business visualization device 1 according to the present embodiment will be described with reference to the drawings.
FIG. 12 is a flowchart showing an example of the operation of the business visualization device 1 according to the present embodiment.

As shown in FIG. 12, the business visualization device 1 first extracts the position of the primary key of the target table in each table based on the table layout group (step S101). As shown in FIG. 6, for example, the primary key extraction unit 21 of the business visualization device 1 sets the position of the primary key of “Table A” in each table from the table layout group as “CaseID item position” and “CaseID item length”. To generate a list of primary key positions as shown in FIG. 6 (b). The primary key extraction unit 21 stores a list of generated primary key positions in the primary key layout storage unit 11.

Next, the business visualization device 1 generates the event log L1 from the journal log and the position of the primary key of each table (step S102). As shown in FIG. 7, the event log generation unit 22 of the business visualization device 1 is based on a list of the journal log L0 which is input data and the position of the primary key stored in the primary key layout storage unit 11 (FIG. 7). Generate the event log L1 as shown in c). For example, the event log generation unit 22 extracts the history record of each table in the journal log L0, adds the value of the primary key of each table as CaseID, and generates an event record. The event log generation unit 22 collectively generates an event log L1 by collecting the generated event records, and stores the event log L1 in the event log storage unit 12.

Next, the business visualization device 1 extracts a CaseID in which "CRUD" includes "Insert", extracts an event record including the CaseID from the event log L1, and generates an event log L2 (step S103). As shown in FIG. 8, the start extraction unit 231 of the business visualization device 1 extracts the event record in which "CRUD" is "Insert" from the event records of the event log L1 stored in the event log storage unit 12. The value of CaseID included in the event record is extracted as shown in FIG. 8B. The start extraction unit 231 extracts all the event records including the value of CaseID shown in FIG. 8B from the event log L1, and generates the event log L2 in which the extracted event records are put together.

Next, the business visualization device 1 extracts a record for the target table from the event log L2 and generates the event log L3 (step S104). As shown in FIG. 9, the target table extraction unit 232 of the business visualization device 1 extracts and summarizes the event records corresponding to the target table “table A” from the event log L2 to generate the event log L3. do.

Next, the business visualization device 1 extracts the Case ID indicating the end of the business status from the table data of the target table, divides the event log L3 for each business status and Case ID, and generates the divided event log L4 (step S105). ). As shown in FIG. 10, the end extraction unit 233 of the business visualization device 1 divides the event log L3 for each “business status” and Case ID in the table data TD1, and divides the event log L4 (L4-1, L4-2). , ...) is generated. The business visualization device 1 stores the generated split event log L4 (L4-1, L4-2, ...) In the split event log storage unit 14.

Next, the business visualization device 1 generates a business flow from the split event log L4 (step S106). As shown in FIG. 11, the business flow generation unit 24 of the business visualization device 1 generates business flows (FL1, FL2, ...) From the divided event logs L4 (L4-1, L4-2, ...). do. The business flow generation unit 24 stores the generated business flow (FL1, FL2, ...) In the business flow storage unit 15. After the process of step S106, the business visualization device 1 ends the process.

The business visualization device 1 outputs a business flow (FL1, FL2, ...) Stored by the business flow storage unit 15 to a display device (not shown) such as a liquid crystal display, and generates a business flow (FL1). , FL2, ...) Is displayed on the display device.

As described above, the business visualization device 1 according to the present embodiment includes a primary key extraction unit 21, an event log generation unit 22, a division log generation unit 23, and a business flow generation unit 24. The primary key extraction unit 21 determines the position of the primary key of a predetermined target table (for example, “table A”) in each table based on the table layout information (for example, table layout group) that defines the array of tables. Extract. The event log generation unit 22 extracts a history record for the table including the primary key from the journal log L0 (update history information) based on the position of the primary key extracted by the primary key extraction unit 21, and sets the extracted history record. An event log L1 including an event record associated with a CaseID (primary key information) indicating the value of the primary key is generated. Here, the journal log includes a plurality of history records, and the history record includes date and time information when the business process is executed, a function ID (function identification information) for identifying a function included in the business process, and a function. The table name (table identification information) that identifies the table to be processed, the CRUD (processing type information) that indicates the type of processing for the table, and the table information stored in the table (for example, the updated table information) are associated with each other. There is. In the split log generation unit 23, CRUD indicates the start of processing (for example, “Insert”) from the event log L1 generated by the event log generation unit 22, and the table name is the target table (“table A”). Further, an event record including a CaseID whose business status (business status) value of the target table indicates the end of business (for example, "1" (completed), "9" (cancelled), etc.) is extracted. Generate the split event log L4 organized for each business status value. The business flow generation unit 24 generates a business flow that visualizes the business process based on the division event log L4 for each business status value generated by the division log generation unit 23.

As a result, the business visualization device 1 according to the present embodiment extracts the log including the process from the start to the end of the processing for the target table from the journal log, and generates a business flow for each value of the business status (business status). .. Therefore, the business visualization device 1 according to the present embodiment can exclude unnecessary parts that complicate the business flow and make the necessary parts of the business specifications into the business flow. Therefore, the business visualization device 1 according to the present embodiment can efficiently grasp the necessary parts of the business specifications.

Further, in the present embodiment, the event log generated by the event log generation unit 22 is set as the event log L1 (first event log), and the division log generation unit 23 includes the start extraction unit 231 and the target table extraction unit 232, and ends. It is provided with an extraction unit 233. The start extraction unit 231 extracts an event record including Case ID indicating the start of processing from the event log L1 (first event log), and the event log L2 (second event) that summarizes the extracted event records. Log) is generated. The target table extraction unit 232 extracts an event record whose table name indicates the target table (“table A”) from the event log L2 (second event log), and collects the extracted event records in the event log L3 (). 3rd event log) is generated. From the table data (for example, table data TD1) of the target table acquired in advance, the end extraction unit 233 sets the value of the business status to the end of the business (for example, "1" (completed), "9" (cancelled), etc. ) Is extracted, and the event records including the extracted CaseID are collectively generated from the event log L3 (third event log) to generate the divided event log L4.
As a result, the business visualization device 1 according to the present embodiment can efficiently extract the necessary parts of the business specifications from the event log L1 and exclude other unnecessary parts.

Further, the business visualization method according to the present embodiment includes a primary key extraction step, an event log generation step, a split log generation step, and a business flow generation step. In the primary key extraction step, the primary key extraction unit 21 defines a predetermined table (for example, “table A”) in each table based on the table layout information (for example, table layout group) that defines the array of tables. Extract the position of the primary key of. In the event log generation step, the event log generation unit 22 extracts a history record for the table including the primary key from the journal log L0 (update history information) based on the position of the primary key extracted by the primary key extraction step. , Generates an event log L1 including an event record in which the extracted history record and a CaseID (primary key information) indicating the value of the primary key are associated with each other. In the split log generation step, the split log generation unit 23 indicates that CRUD indicates the start of processing (for example, “Insert”) from the event log L1 generated by the event log generation step, and the table name is the target table. (“Table A”), and further includes a CaseID in which the value of the business status (business status) of the target table indicates the end of the business (for example, “1” (completed), “9” (cancelled), etc.). The event record is extracted, and the divided event log L4 summarized for each business status value is generated. In the business flow generation step, the business flow generation unit 24 generates a business flow that visualizes the business process based on the division event log L4 for each business status value generated by the division log generation step.
As a result, the business visualization method according to the present embodiment has the same effect as the business visualization device 1 described above, and can efficiently grasp the necessary parts of the business specifications.

[Second Embodiment]
Next, the business visualization device 1a according to the second embodiment will be described with reference to the drawings.
The business visualization device 1a according to the second embodiment divides each function into a general-purpose function and a specific function, excludes the general-purpose function from the above-mentioned divided event log L4, and generates information on the appearance frequency of the general-purpose function. Is added, which is different from the first embodiment.

In this embodiment, the general-purpose function is a function that can be executed regardless of the main flow of the business flow. For example, a function that can be executed at an arbitrary timing by pressing a special key such as a function key. Is. For example, a general-purpose function in a financial lending business is a function that can be executed at an arbitrary timing regardless of the main flow of the business flow, such as a function of changing loan conditions. The general-purpose function is, for example, a function that can be excluded in order to grasp the business specifications.
In addition, the specific function is a function related to the main flow of the business flow, and is a function required for grasping the business specifications.

FIG. 13 is a block diagram showing an example of the business visualization device 1a according to the second embodiment.
As shown in FIG. 13, the business visualization device 1a generates business flow and appearance frequency information by using the journal log, the table layout group, the target table name, and the table data of the target table as input data. The business visualization device 1a includes a storage unit 10a and a control unit 20a.
In FIG. 13, the same reference numerals are given to the same configurations as those in FIG. 1, and the description thereof will be omitted.

The storage unit 10a stores various information used by the business visualization device 1a. The storage unit 10a includes, for example, a main key layout storage unit 11, an event log storage unit 12, a Case ID storage unit 13, a split event log storage unit 14, a business flow storage unit 15, an analysis result storage unit 16, and the analysis result storage unit 16. It is provided with an appearance frequency information storage unit 17.

The analysis result storage unit 16 stores the analysis result of analyzing the divided event log L4 in order to sort the general-purpose function and the specific function, which will be described later, and to generate the appearance frequency information. Details of the analysis results will be described later.
The appearance frequency information storage unit 17 stores the appearance frequency information of the general-purpose function.

The control unit 20a is, for example, a processor including a CPU and the like, and controls the business visualization device 1a in an integrated manner. The control unit 20a includes, for example, a primary key extraction unit 21, an event log generation unit 22, a division log generation unit 23, a business flow generation unit 24, a general-purpose function exclusion unit 25, and an appearance frequency generation unit 26. ing.

The general-purpose function exclusion unit 25 performs the function indicated by the function ID (function identification information) included in the split event log L4 based on the number of occurrences of the function and the number of patterns of the immediately preceding function executed immediately before. It is determined whether or not the event record is, and the event record including the function ID indicating the general-purpose function is excluded from the split event log L4. The general-purpose function exclusion unit 25 calculates, for example, the general-purpose function, which is an index of the general-purpose function, based on the number of appearances of the function and the number of patterns of the immediately preceding function, and the calculated general-purpose degree is equal to or higher than a predetermined threshold value. In addition, the function is determined to be a general-purpose function. Here, with reference to FIGS. 14 and 15, the determination of the general-purpose function by the general-purpose function exclusion unit 25 and the distribution processing of the general-purpose function will be described.

FIG. 14 is a diagram showing an example of a distribution process between a general-purpose function and a specific function in the present embodiment.
FIG. 14A shows the division event log L4 generated by the division log generation unit 23, and the general-purpose function exclusion unit 25 sorts (sorts) the division event log L4 by Case ID and date / time in chronological order by Case ID. ) Is performed, and the split event log L4 is analyzed. Based on the analysis result, the general-purpose function exclusion unit 25 divides each function into either a general-purpose function or a specific function, as shown in FIG. 14 (b). Further, the general-purpose function exclusion unit 25 adds the distribution result shown in FIG. 14B to the division event log L4 shown in FIG. 14A to generate the division event log L5 shown in FIG. 14C. do. The general-purpose function exclusion unit 25 generates a split event log L5 for each split event log L4.

Further, FIG. 15 is a diagram illustrating an example of a general-purpose generation process according to the present embodiment.
FIG. 15A shows a split event log L4 sorted in chronological order by CaseID, and the general-purpose function exclusion unit 25 displays a split event log L4 sorted in chronological order by CaseID in FIG. 15B. As shown in, the analysis is performed based on the number of appearances (number of appearances) of each function and the number of patterns. The general-purpose function exclusion unit 25 totals the numbers of all the function IDs that appear for each function that exists immediately before. The general-purpose function exclusion unit 25 stores the analysis results shown in FIGS. 15A and 15B in the analysis result storage unit 16.

For example, in the example shown in FIG. 15B, when "function A" is executed, the number of occurrences in which "function A" is executed immediately before is "4", and "function B" is executed immediately before. It shows that the number of appearances to be made is "6". In this case, the number of appearances on the horizontal axis is "10", and the number of patterns is "2".

Further, the general-purpose function exclusion unit 25 generates a tabulation table as shown in FIG. 15 (c) from the front-back analysis table shown in FIG. 15 (b). The general-purpose function exclusion unit 25 includes the number of appearances of each function ID in the summary table, the number of patterns on the vertical axis (number of patterns (vertical)) and the number of patterns on the horizontal axis (patterns) in the front-back analysis table shown in FIG. Based on the number (horizontal)), the versatility is calculated by the following formula (1).

Versatility = (LOG (number of appearances)) x number of patterns (total)
= (LOG (number of appearances)) x (number of patterns (vertical) + number of patterns (horizontal)) ... (1)

For example, in the example shown in FIG. 15 (c), the versatility of "function A" is "2.3 x 5" according to the above formula (1).
The general-purpose function exclusion unit 25 determines that the general-purpose function is a general-purpose function when the general-purpose degree calculated above is equal to or greater than a predetermined threshold value (general-purpose degree ≥ predetermined threshold value). Further, the general-purpose function exclusion unit 25 determines that the general-purpose function is a specific function when the general-purpose degree calculated above is less than a predetermined threshold value (general-purpose degree <predetermined threshold value).

Further, the predetermined threshold value is, for example, a value obtained by multiplying the average value of the general-purpose degree by the user setting coefficient N (average value of the general-purpose degree × N). Here, the average value of the general-purpose degree is the average value of the general-purpose degree in all the functions included in the split event log L4, and the user setting coefficient N is a coefficient value set by the user.
In this way, the general-purpose function exclusion unit 25 determines whether each function is a general-purpose function or a specific function.

Further, as shown in FIG. 16, the general-purpose function exclusion unit 25 excludes the event record including the function ID indicating the general-purpose function from the split event log L5 to generate the split event log L6.

FIG. 16 is a diagram showing an example of a general-purpose function exclusion process and a business flow generation process in the present embodiment.
FIG. 16A shows the split event log L5 to which the “function type” which is the determination result of the general-purpose function is added. The general-purpose function exclusion unit 25 excludes the event record whose "function type" is "general-purpose function" from the split event log L5, and leaves the event record whose "function type" is "specific function" in FIG. 16 (Fig. 16). The split event log L6 as shown in b) is generated. The general-purpose function exclusion unit 25 generates the split event log L6 for each business status value. Further, the general-purpose function exclusion unit 25 stores the generated split event log L6 in the split event log storage unit 14.

Further, in the present embodiment, the business flow generation unit 24 generates a business flow based on the divided event log L6 in which the general-purpose function exclusion unit 25 excludes the event record including the function ID indicating the general-purpose function. That is, the business flow generation unit 24 generates the business flow FL3 as shown in FIG. 16 (c).

Returning to the description of FIG. 13, the appearance frequency generation unit 26 aggregates the above-mentioned divided event log L5 and generates appearance frequency information indicating the appearance frequency executed after the specific function for each general-purpose function. Here, with reference to FIG. 17, the details of the appearance frequency information generation process by the appearance frequency generation unit 26 will be described.

FIG. 17 is a diagram showing an example of the generation processing of the appearance frequency information in the present embodiment.
FIG. 17A shows the above-mentioned divided event log L5, and the appearance frequency generation unit 26 immediately before the function IDs of all the general-purpose functions appearing from the divided event log L5 sorted in chronological order for each Case ID. The number of appearances is totaled for each specific function that exists in. The appearance frequency generation unit 26 generates an appearance frequency analysis result as shown in FIG. 17 (b).

For example, in the example shown in FIG. 17B, the general-purpose function "function B" has "4" at the beginning and "6" after "function A". It shows that. It also indicates that the total number of occurrences of "function B" is "10".

Further, the appearance frequency generation unit 26 totals the number of Case IDs in which each function ID of the general-purpose function appears and the total number of Case IDs as shown in FIG. 17C from the divided event log L5. The appearance frequency generation unit 26 stores the analysis results (aggregation results) shown in FIGS. 17 (b) and 17 (c) in the analysis result storage unit 16.
For example, in the example shown in FIG. 17C, the number of CaseIDs of the general-purpose function “Function B” is “3”, and the total number of CaseIDs is “10”.

The appearance frequency generation unit 26 generates the appearance frequency information as shown in FIG. 17 (d) from the aggregation results shown in FIGS. 17 (b) and 17 (c). The appearance frequency generation unit 26 includes "total number of Case IDs", "total number of appearances", "total number of executions", "number of Case IDs in which functions appear", and "total number" for each specific function as appearance frequency information. And generate "average number of executions".

Here, the "total number of CaseIDs" is the total number of CaseIDs aggregated in FIG. 17B, and the "total number" of the "total number of appearances" is the total number of appearances aggregated in FIG. 17A. , "Number of Case IDs in which a function appears", and the appearance frequency generation unit 26 calculate the "average number of executions" of "total number of appearances" by the following formula (2).

Average number of executions = total number of appearances / total number of CaseIDs ... (2)

Further, the "total number" for each specific function is the number of appearances of the function IDs of each general-purpose function for each specific function aggregated according to FIG. 17A, and the appearance frequency generation unit 26 is the "average execution" for each specific function. The number of times is calculated by the following formula (2).

Average number of executions = total number for each specific function / number of CaseIDs in which the function appears ... (3)

Next, the operation of the business visualization device 1a according to the present embodiment will be described with reference to the drawings.
FIG. 18 is a flowchart showing an example of the operation of the business visualization device 1a according to the present embodiment.

In FIG. 18, the processes from step S201 to step S205 are the same as the processes from step S101 to step S105 shown in FIG. 12, so the description thereof will be omitted.

In step S206, the business visualization device 1a sorts the divided event log L4 by Case ID and date / time, and totals the number of appearances and the number of patterns for all function IDs. That is, the general-purpose function exclusion unit 25 of the business visualization device 1a aggregates the number of appearances and the number of patterns as shown in FIG. 15 described above.

Next, the general-purpose function exclusion unit 25 calculates the general-purpose degree based on the aggregation result (the number of appearances and the number of patterns), and divides the general-purpose function into a general-purpose function or a specific function according to the general-purpose degree (step S207). The general-purpose function exclusion unit 25 calculates the general-purpose degree by, for example, the above-mentioned equation (1), and divides it into a general-purpose function or a specific function according to whether or not the general-purpose degree is equal to or higher than a predetermined threshold value (FIG. 14). (See split event log L5).

Next, the general-purpose function exclusion unit 25 excludes the general-purpose function from the split event log L5 (step S208). For example, as shown in FIG. 16 described above, the general-purpose function exclusion unit 25 generates a divided event log L6 excluding the general-purpose function from the divided event log L5 divided into the general-purpose function and the specific function.

Next, as shown in FIG. 16, the business flow generation unit 24 of the business visualization device 1a generates the business flow FL3 from the divided event log L5 (step S209). The business flow generation unit 24 stores the generated business flow FL3 in the business flow storage unit 15.

Next, the appearance frequency generation unit 26 of the business visualization device 1a aggregates the divided event logs L5 and generates appearance frequency information of each general-purpose function (step S210). The appearance frequency generation unit 26 generates appearance frequency information from the divided event log L5, which is divided into general-purpose functions and specific functions, as shown in FIG. 17 (see FIG. 17 (d)). Further, the appearance frequency generation unit 26 stores the generated appearance frequency information in the appearance frequency information storage unit 17. After the process of step S210, the business visualization device 1a ends the process.

The business visualization device 1a outputs the business flow stored in the business flow storage unit 15 to, for example, a display device (not shown) such as a liquid crystal display, and displays the generated business flow on the display device. Further, the business visualization device 1a may output the appearance frequency information stored in the appearance frequency information storage unit 17 to a display device (not shown) and display it on the display device.

Note that FIG. 19 is a diagram showing a display example of business flow and appearance frequency information in the present embodiment.
FIG. 19A is a display example of a business flow (for example, BPMN, etc.). In the example shown in FIG. 19A, the business flow after excluding the general-purpose function is shown.

Further, FIG. 19B shows a display example of the appearance frequency information. In the example shown in FIG. 19B, the appearance frequency information is displayed in a format that matches the layout of the BPMN of the business flow shown in FIG. 19A, which makes it easier to grasp the appearance frequency information of the general-purpose function. There is.

As described above, the business visualization device 1a according to the present embodiment includes the general-purpose function exclusion unit 25. The general-purpose function exclusion unit 25 sets the function indicated by the function ID included in the split event log L4 into the main flow of the business flow based on the number of occurrences of the function and the number of patterns of the immediately preceding function executed immediately before. It is determined whether or not the function is a general-purpose function that can be executed regardless, and the event record including the function ID indicating the general-purpose function is excluded from the divided event log L4 (L5). The business flow generation unit 24 generates a business flow based on the divided event log L4 (L6) in which the general-purpose function exclusion unit 25 excludes the event record including the function identification information indicating the general-purpose function.

Since the general-purpose function can be executed regardless of the main flow of the business flow, it is executed at an arbitrary timing, which is a factor that complicates the business flow. Since the business visualization device 1a according to the present embodiment generates the business flow by excluding this general-purpose function, it is possible to more efficiently grasp the necessary part of the business specifications.

Further, in the present embodiment, the general-purpose function exclusion unit 25 calculates the general-purpose degree, which is an index of the general-purpose function, based on the number of appearances of the function and the number of patterns of the immediately preceding function, and the calculated general-purpose degree is predetermined. When it is equal to or more than the threshold value, the function is determined to be a general-purpose function.
As a result, the business visualization device 1a according to the present embodiment can appropriately determine the general-purpose function by a simple means.

Further, the business visualization device 1a according to the present embodiment aggregates the divided event logs L4, and for each general-purpose function, the appearance frequency indicating the appearance frequency executed after the specific function which is a function related to the main flow of the business flow. The appearance frequency generation unit 26 for generating information is provided.
As a result, the business visualization device 1a according to the present embodiment can grasp the influence of the general-purpose function, for example, and can more efficiently grasp the necessary part of the business specification.

The present invention is not limited to each of the above embodiments, and can be modified without departing from the spirit of the present invention.
For example, in each of the above embodiments, the execution order of each process of the divided log generation unit 23 (processes of the start extraction unit 231 and the target table extraction unit 232 and the end extraction unit 233) is limited to each of the above embodiments. The execution order may be changed instead of the one.

Further, in each of the above embodiments, the configuration in which the business visualization device 1 (1a) does not have a display unit has been described, but the present invention is not limited to this, and the business visualization device 1 (1a) has a built-in display unit. You may try to do it.

Further, in each of the above embodiments, the business visualization device 1 (1a) has described an example of acquiring input data from the outside, but the present invention is not limited to this, and for example, the input data is input to the storage unit 10 (10a). The data may be stored in advance.

Further, in each of the above embodiments, an example in which the business visualization device 1 (1a) includes the storage unit 10 (10a) has been described, but the present invention is not limited to this, and a part of the storage unit 10 (10a) or a part of the storage unit 10 (10a) or The whole may be provided outside the business visualization device 1 (1a). Further, in this case, the storage unit 10 (10a) may be, for example, a storage server device that can be connected via a network.

Further, in each of the above embodiments, the business visualization device 1 (1a) has been described as an example of one device, but the present invention is not limited to this, and the business visualization device 1 (1a) may be composed of a plurality of devices. A part of the functions of the control unit 20 (20a) may be provided externally.

Further, in each of the above embodiments, an example of using a journal log as an example of update history information has been described, but the present invention is not limited to this, and for example, another update log such as a DB update log may be used. good.

Each configuration included in the above-mentioned business visualization device 1 (1a) has a computer system inside. Then, a program for realizing the functions of each configuration included in the above-mentioned business visualization device 1 (1a) is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into the computer system. By executing the processing, the processing in each configuration provided in the business visualization device 1 (1a) described above may be performed. Here, "loading and executing a program recorded on a recording medium into a computer system" includes installing the program in the computer system. The term "computer system" as used herein includes hardware such as an OS and peripheral devices.
Further, the "computer system" may include a plurality of computer devices connected via a network including a communication line such as the Internet, WAN, LAN, and a dedicated line. Further, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, or a storage device such as a hard disk built in a computer system. As described above, the recording medium in which the program is stored may be a non-transient recording medium such as a CD-ROM.

The recording medium also includes an internal or external recording medium that can be accessed from the distribution server to distribute the program. Even if the program is divided into a plurality of parts, downloaded at different timings, and then combined with each configuration provided in the business visualization device 1 (1a), or the distribution server that distributes each of the divided programs is different. good. Furthermore, a "computer-readable recording medium" is a volatile memory (RAM) inside a computer system that serves as a server or client when a program is transmitted via a network, and holds the program for a certain period of time. It shall also include things. Further, the above program may be for realizing a part of the above-mentioned functions. Further, it may be a so-called difference file (difference program) that can realize the above-mentioned function in combination with a program already recorded in the computer system.

Further, a part or all of the above-mentioned functions may be realized as an integrated circuit such as LSI (Large Scale Integration). Each of the above-mentioned functions may be made into a processor individually, or a part or all of them may be integrated into a processor. Further, the method of making an integrated circuit is not limited to the LSI, and may be realized by a dedicated circuit or a general-purpose processor. Further, when an integrated circuit technology that replaces an LSI appears due to advances in semiconductor technology, an integrated circuit based on this technology may be used.

1, 1a Business visualization device 10, 10a Storage unit 11 Primary key layout storage unit 12 Event log storage unit 13 CaseID storage unit 14 Divided event log storage unit 15 Business flow storage unit 16 Analysis result storage unit 17 Occurrence frequency information storage unit 20, 20a Control unit 21 Primary key extraction unit 22 Event log generation unit 23 Divided log generation unit 24 Business flow generation unit 25 General-purpose function exclusion unit 26 Occurrence frequency generation unit 231 Start extraction unit 232 Target table extraction unit 233 End extraction unit L0 Journal log L1 , L2, L3 Event log L4, L4-1, L4-2, L5, L6 Split event log FL1, FL2, FL3 Business flow TL1 Table layout TD1 Table data

Claims (7)

Based on the table layout information that defines the array of tables, the primary key extraction unit that extracts the position of the primary key of the predetermined target table in each table, and the primary key extraction unit.
The date and time information when the business process is executed, the function identification information for identifying the function included in the business process, the table identification information for identifying the table to be processed in the function, and the type of processing for the table. The primary key is included based on the position of the primary key extracted by the primary key extraction unit from the update history information including a plurality of history records in which the indicated processing type information and the table information stored in the table are associated with each other. An event log generation unit that extracts the history record for the table and generates an event log including an event record in which the extracted history record and the primary key information indicating the value of the primary key are associated with each other.
From the event log generated by the event log generation unit, the processing type information indicates the start of processing, the table identification information is the target table, and the business status value of the target table is A split log generation unit that extracts the event record including the primary key information indicating the end of the business and generates a split event log summarized for each value of the business status.
A business visualization device including a business flow generation unit that generates a business flow that visualizes the business process based on a division event log for each value of the business state generated by the division log generation unit. The event log generated by the event log generation unit is used as the first event log.
The divided log generation unit
From the first event log, the event record including the primary key information whose processing type information indicates the start of processing is extracted, and the start extraction for generating the second event log summarizing the extracted event records is generated. Department and
A target table extraction unit that extracts the event record whose table identification information indicates the target table from the second event log and generates a third event log that summarizes the extracted event records.
The primary key information included in the record in which the value of the business state indicates the end of the business is extracted from the table data of the target table acquired in advance, and the extracted primary key is extracted from the third event log. The business visualization device according to claim 1, further comprising an end extraction unit that collectively generates the divided event log by collecting the event records including information. The function indicated by the function identification information included in the divided event log is executed regardless of the main flow of the business flow based on the number of occurrences of the function and the number of patterns of the immediately preceding function executed immediately before. It is provided with a general-purpose function exclusion unit that determines whether or not the general-purpose function is a possible general-purpose function and excludes the event record including the function identification information indicating the general-purpose function from the divided event log.
The business flow generation unit is characterized in that the general-purpose function exclusion unit generates the business flow based on the divided event log excluding the event record including the function identification information indicating the general-purpose function. The business visualization device according to claim 1 or 2. The general-purpose function exclusion unit calculates the general-purpose degree, which is an index of the general-purpose function, based on the number of appearances of the function and the number of patterns of the immediately preceding function, and the calculated general-purpose degree is equal to or higher than a predetermined threshold value. The business visualization device according to claim 3, wherein the function is determined to be the general-purpose function. An appearance frequency generation unit that aggregates the divided event logs and generates appearance frequency information indicating the appearance frequency to be executed after the specific function, which is the function related to the main flow of the business flow, for each general-purpose function. The business visualization device according to claim 3 or 4, wherein the business visualization device is provided. A primary key extraction step in which the primary key extraction unit extracts the position of the primary key of a predetermined target table in each of the tables based on the table layout information that defines the array of tables.
The event log generation unit includes date and time information when a business process is executed, function identification information for identifying a function included in the business process, table identification information for identifying the table to be processed in the function, and the above. Based on the position of the primary key extracted by the primary key extraction step from the update history information including a plurality of history records in which the processing type information indicating the processing type for the table and the table information stored in the table are associated with each other. An event log generation step of extracting the history record for the table including the primary key and generating an event log including an event record in which the extracted history record is associated with the primary key information indicating the value of the primary key. ,
From the event log generated by the event log generation step, the split log generation unit indicates that the processing type information starts processing, the table identification information is the target table, and further, the target. A split log generation step that extracts the event record containing the primary key information whose business status value in the table indicates the end of business and generates a split event log summarized for each business status value.
The business flow generation unit is characterized by including a business flow generation step that generates a business flow that visualizes the business process based on the division event log for each value of the business state generated by the division log generation step. Business visualization method. On the computer
Based on the table layout information that defines the array of tables, the primary key extraction step that extracts the position of the primary key of the predetermined target table in each table, and the primary key extraction step.
The date and time information when the business process is executed, the function identification information for identifying the function included in the business process, the table identification information for identifying the table to be processed in the function, and the type of processing for the table. Based on the position of the primary key extracted by the primary key extraction step from the update history information including a plurality of history records in which the indicated processing type information and the table information stored in the table are associated with each other, the primary key is selected. An event log generation step that extracts the history record for the including table and generates an event log including an event record in which the extracted history record and the primary key information indicating the value of the primary key are associated with each other.
From the event log generated by the event log generation step, the processing type information indicates the start of processing, the table identification information is the target table, and the business state value of the target table. Is a split log generation step that extracts the event record including the primary key information indicating the end of the business and generates a split event log summarized for each value of the business status.
A program for executing a business flow generation step that generates a business flow that visualizes the business process based on the divided event log for each value of the business state generated by the divided log generation step.

Images