JP5664050B2 - Information processing method, program, and apparatus - Google Patents

Description

  The present technology relates to a flow processing technology.

  There are various flows such as a flow representing a processing flow, a flow representing a state transition and a transition between events, and a business flow representing a business flow.

  Among them, for example, in business processes and reengineering, business flow analysis is attracting attention. For example, a technique for generating a business flow that is actually implemented using the business system by analyzing a record in a database that stores a processing result of the business system is known.

  There is also a technique for determining whether or not the process complies with business rules. In other words, an information processing system that checks a workflow constituted by a plurality of processes stores a conversion table in which the contents of the processes constituting the workflow and the properties of parameters assigned when the processes are performed are paired. Then, using this conversion table, specific workflow entity data is generated from the workflow instruction data in which the process instruction information and parameters constituting the workflow are paired. A check table is generated by extracting check items from a manual that describes items to be checked in the workflow. Based on this check table, the workflow generated above is checked. This conversion table is only data for generating one workflow from the workflow instruction data.

JP 2008-27072 A JP 2007-122651 A JP 2009-3879 A

  In a situation where a flow is generated from the business process result stored in the database as described above, there may be a case where a plurality of flows related from different viewpoints can be generated from the same data. There is a desire to analyze such a plurality of related flows while switching, but if the number of nodes included in the flow is enormous or the flow structure is complicated, the amount of data becomes too large There is a problem.

  Therefore, the objective of this technique is related with the technique for improving the efficiency of the resource used when hold | maintaining the data of several related flows as one side surface.

  This information processing method (A) estimates and converts the data amount of the conversion table for converting the first flow into the second flow related to the first flow and the data amount of the second flow itself. A step of storing the estimated value of the data amount of the table and the estimated value of the data amount of the second flow itself in the storage device; and (B) the estimated value of the data amount of the conversion table stored in the storage device is the second value. A conversion table generating step of generating the conversion table and storing it in a storage device when it is smaller than the estimated value of the data amount of the flow itself.

  Resources used when holding data of a plurality of related flows can be made efficient.

FIG. 1 is a diagram for explaining a flow having an instance. FIG. 2 is a diagram illustrating an example of converting a flow using a conversion table. FIG. 3A is a diagram illustrating an example of a one-to-one event conversion unit of a conversion table. FIG. 3B is a diagram illustrating an example of a one-to-one transition conversion unit of the conversion table. FIG. 3C is a diagram illustrating an example of the transition conversion unit other than the one-to-one conversion table. FIG. 4 is a functional block diagram of the flow analysis apparatus according to the embodiment. FIG. 5 is a diagram illustrating a processing flow of preprocessing. FIG. 6A is an example of data stored in the analysis target data storage unit. FIG. 6B is a diagram illustrating an example of a temporary table. FIG. 7 is a diagram illustrating a processing flow of conversion table generation processing. FIG. 8 is a diagram showing a processing flow of conversion table generation processing. FIG. 9 is a diagram illustrating a processing flow of conversion table generation processing. FIG. 10 is a diagram showing a processing flow of a flow display scene. FIG. 11 is a diagram illustrating an example of data stored in the first flow storage unit. FIG. 12 is a diagram illustrating an example of a flowchart before conversion. FIG. 13 is a diagram illustrating an example of data stored in the second flow storage unit. FIG. 14 is a diagram illustrating an example of a flowchart after conversion. FIG. 15 is a diagram illustrating a processing flow of the flow conversion processing. FIG. 16 is a diagram illustrating an example of an initial state of intermediate Map data. FIG. 17 is a diagram illustrating an example of a one-to-one event conversion unit. FIG. 18 is a diagram illustrating an example of intermediate Map data in a state after processing the one-to-one event conversion unit. FIG. 19 is a diagram illustrating a processing flow of the flow conversion processing. FIG. 20 is a diagram illustrating an example of the one-to-one transition conversion unit. FIG. 21 is a diagram illustrating an example of intermediate Map data in a state after processing the one-to-one transition conversion unit. FIG. 22 is a diagram illustrating an example of a transition conversion unit other than one-to-one. FIG. 23 is a diagram illustrating an example of intermediate Map data in a state after processing a transition conversion unit other than one-to-one. FIG. 24 is a diagram illustrating a process flow of the flow conversion process. FIG. 25 is a diagram illustrating another example of the pre-conversion flow. FIG. 26 is a diagram illustrating an example of pre-conversion data for another example of the pre-conversion flow. FIG. 27 is a diagram illustrating another example of the post-conversion flow. FIG. 28 is a diagram illustrating an example of post-conversion data for another example of the post-conversion flow. FIG. 29 is a diagram illustrating another example of analysis target data. FIG. 30 is a diagram illustrating another example of the temporary table. FIG. 31A is a diagram illustrating another example of the one-to-one event conversion unit of the conversion table. FIG. 31B is a diagram illustrating another example of the one-to-one transition conversion unit of the conversion table. FIG. 31C is a diagram illustrating another example of the transition conversion unit other than the one-to-one conversion table. FIG. 32 is a diagram illustrating another example of the initial state of the intermediate map data. FIG. 33 is a diagram illustrating another example of the intermediate Map data in a state after processing the one-to-one event conversion unit. FIG. 34 is a diagram illustrating another example of the intermediate Map data in a state after processing the one-to-one transition conversion unit. FIG. 35 is a diagram illustrating another example of intermediate Map data in a state after processing a transition conversion unit other than one-to-one. FIG. 36 is a functional block diagram of a computer.

  Unlike the hand-drawn business flow, the business flow generated using the business system data as described in the section of the background art may be accompanied by statistical data indicating which part is executed how many times. In the present embodiment, such a flow is referred to as a “flow having an instance”. On the other hand, a flow that does not have information on the number of executions, such as a hand-drawn flow, is referred to as a “flow that does not have an instance” in the present embodiment. The flow having instances accurately indicates the actual state of the business, and by analyzing the flow, problems of the business can be found and can be improved.

  The main analysis target for business improvement performed in business processes and re-engineering is the business flow. However, there may be cases where new problems can be discovered by analyzing the flow from a viewpoint other than the business, such as the person who performed the business, the department, and the location where the business was performed. It is expected to improve the effect of business improvement by analysis. For example, even if there is no problem in the flow of work, it is useful for improving work efficiency if you can find problems such as when the work transfer efficiency between the persons in charge is bad or the flow of things on the work line is bad. .

  The original data of a flow having an instance is, for example, a database or log file in a business system, but the database in the business system includes not only the type of business but also various information such as the person in charge, department, location, etc. In many cases, it is desirable to use this to generate a flow for each viewpoint.

  FIG. 1 is a diagram illustrating an example of a flow for each viewpoint having an instance. FIG. 1B shows an example of a business system process record, and such data is acquired from a database record, log file, or the like. Here, the instance ID is an identifier for identifying a business process to be executed for one item (that is, an instance). When records with the same instance ID are arranged in order of processing time and a flow is generated using the “business” column, the result is as shown in FIG. The first node “Initial” and the last node “Final” are added separately. In FIG. 1A, two instances are superimposed. Therefore, the number of instances passing through the transition, that is, the number of times the transition is executed is shown in the transition between nodes (also referred to as events). In the example of FIG. 1A, the number of executions is “2” for the total number of instances “2” except that the transition between “inspection” and “repair” is the number of executions “1”. Yes. On the other hand, when a flow is generated using the “department” column, it is as shown in FIG.

  In the example of FIG. 1C, the correspondence between the business and the department, such as “part A” and “line 1”, is almost one-to-one. However, for “Part B”, the values of the corresponding department are two types, “Line 2” and “Line 4”, and as a result, the shape of the business flow and department flow changes depending on the appearance location. ing. In FIG. 1, the number of instances is two. Typically, the number of instances may reach several tens of thousands because the business results of several weeks to several months are analyzed as a flow. Then, there may be many portions where such a one-to-one relationship is not established. Furthermore, although two types of flows are shown in FIG. 1, more flows may be generated. Therefore, when a flow for each viewpoint having an instance is generated and held, there is a possibility that the amount of data becomes enormous.

  Therefore, a conversion table for converting from the first flow according to the first viewpoint to the flow according to the second viewpoint different from the first viewpoint is introduced. FIG. 2 shows an example of generating a post-conversion flow using a pre-conversion flow and a conversion table for a flow having instances. FIG. 2A shows “data before conversion” including transition and the number of executions as data for displaying the flow before conversion. In order to convert the pre-conversion data into “post-conversion data” that is data for generating the post-conversion flow shown in FIG. 2C, a “conversion table” shown in FIG. 2B is prepared. This conversion table includes information about the transition type after conversion and the number of executions for each transition before conversion. The post-conversion data includes information on the number of executions for each transition type.

  In the case of FIG. 2, the data amount of the conversion table exceeds the data amount of the converted data. Therefore, in this embodiment, the amount of data in the conversion table is estimated before the conversion table is generated, the amount of data in the converted table is also estimated, and the amount of data in the conversion table is estimated to be smaller than the amount of data in the converted data. If there is, a conversion table is generated and held. When the post-conversion flow is actually displayed, the post-conversion flow is generated using the pre-conversion flow and the conversion table data, and is output to a display device or the like. On the other hand, if the estimated value of the data amount of the converted data is less than or equal to the estimated value of the data amount of the conversion table, the converted data is generated and held. In this way, storage resources can be used efficiently.

  In the example of FIG. 2B, the data amount of the conversion table exceeds the data amount of the converted data, but the conversion table may not be in this format. For example, the C → D transition before the conversion and the c → d transition after the conversion have a one-to-one relationship before and after the conversion, and the number of executions “105” for the transition C → D in the conversion table. Information can be omitted. That is, the amount of data can be reduced by employing a conversion table other than the conversion table of FIG. However, even if the data amount of the conversion table is reduced, the data amount may be reduced if the pre-conversion data and the post-conversion data are held separately. Therefore, as described above, the data amount of the conversion table is estimated before the conversion table is generated, the data amount of the converted data is estimated, and the data with the smaller estimated value of the data amount is generated.

  In the following, a format as shown in FIGS. 3A to 3C is adopted as a more efficient conversion table. In this embodiment, three conversion tables are used. That is, the one-to-one event converter shown in FIG. 3A, the one-to-one transition converter shown in FIG. 3B, and the transition converter other than the one-to-one shown in FIG. 3C are used.

  The one-to-one event conversion unit is an event conversion table in which event types have a one-to-one correspondence before and after conversion, and an event name before conversion and an event name after conversion are registered in association with each other. Yes.

  The one-to-one transition conversion unit is a conversion table of transitions in which transition types have a one-to-one correspondence before and after conversion. The transition type before conversion and the transition type after conversion are registered in association with each other. The transition type is represented by a transition source event name and a transition destination event name. However, when both the transition source event name and the transition destination event name are registered in the one-to-one event conversion unit, the transition is not registered in the one-to-one transition conversion unit. In addition, when either the transition source event name or the transition destination event name is registered in the one-to-one transition conversion unit, a value is registered before the conversion, but is blank after the conversion.

  The transition conversion unit other than one-to-one is a conversion table of transitions whose transition types do not correspond one-to-one before and after conversion. It includes the transition type before conversion, the transition type after conversion, and the number of executions for each transition after conversion. Since the transitions targeted by this transition conversion unit are not one-to-one before and after conversion, a plurality of post-conversion transitions may correspond to one pre-conversion transition. For this reason, the number of executions is registered for each transition after conversion. When a one-to-one event is included, the data amount is reduced by leaving the converted part blank. Note that one post-conversion transition may correspond to multiple types of pre-conversion transitions, but the data structure for conversion is based on pre-conversion data. Conversion data of a plurality of pre-conversion transitions having the same transition is generated. In this case, the number of executions may be left blank.

  A flow analyzer used when such a conversion table is employed will be described with reference to FIGS.

  The flow analysis apparatus (FIG. 4) according to the present embodiment includes a preprocessing unit 100 and a display processing unit 300. The preprocessing unit 100 and the display processing unit 300 share some components, but a device having the preprocessing unit 100 and a device having the display processing unit 300 may be prepared separately. For example, a server or the like having the preprocessing unit 100 is connected to the network, and data used by the display processing unit 300 is read into a device having the display processing unit 300 and processed by the display processing unit 300 of the device. May be.

  The preprocessing unit 100 includes an analysis target data storage unit 101, a flow generation unit 102, an estimation processing unit 103, a data storage unit 104, a conversion table generation unit 105, a first flow storage unit 202, and a second flow. A storage unit 201 and a conversion table storage unit 203 are included.

  The flow generation unit 102 performs processing using the data stored in the analysis target data storage unit 101 and stores the processing result in the first flow storage unit 202 or the second flow storage unit 201. The flow generation unit 102 performs a process of generating a pre-conversion flow and a post-conversion flow, but the details of this process are the same as the processes disclosed in the documents listed in the background art column, so here in detail. Does not say. Further, the flow generation unit 102 stores data used in the estimation processing unit 103 in the data storage unit 104.

  The estimation processing unit 103 uses the data stored in the data storage unit 104 to store the data being processed in the data storage unit 104, and instructs the flow generation unit 102 to generate a flow after conversion. If not, an instruction is output to the conversion table generation unit 105.

  The conversion table generation unit 105 performs conversion table generation processing using data stored in the first flow storage unit 202 and the data storage unit 104, and stores the generated conversion table in the conversion table storage unit 203.

  The display processing unit 300 includes an input unit 301, a display switching unit 302, a flow conversion unit 303, a post-conversion flow storage unit 304, an output device 305 such as a display device or a printing device, and a first flow storage unit 202. The second flow storage unit 201 and the conversion table storage unit 203 are included.

  The input unit 301 outputs an instruction from the user to the display switching unit 302. When the pre-conversion flow is displayed, the display switching unit 302 generates the pre-conversion flow from the data stored in the first flow storage unit 202 and outputs the pre-conversion flow to the output device 305. Further, when displaying the converted flow, the display switching unit 302 converts the conversion stored in the second flow storage unit 201 according to the data storage state in the second flow storage unit 201 or the conversion table storage unit 203. The post-flow data is read out to generate a post-conversion flow and output to the output device 305, or the flow conversion unit 303 performs flow conversion processing, and the post-conversion flow stored in the post-conversion flow storage unit 304 is read out. Output to the output device 305. The flow conversion unit 303 generates a post-conversion flow using data stored in the conversion table storage unit 203 and the first flow storage unit 202 (in some cases, the second flow storage unit 201), and stores the post-conversion flow. Stored in the unit 304.

  Next, processing contents of the flow analysis apparatus shown in FIG. 4 will be described with reference to FIGS. First, the processing of the preprocessing unit 100 will be described with reference to FIGS.

  For example, first, the flow generation unit 102 generates a pre-conversion flow using data stored in the analysis target data storage unit 101, and stores the pre-conversion flow data in the first flow storage unit 202. In addition, the flow generation unit 102 generates a temporary table for estimating the amount of data used also in the estimation processing unit 103 and stores it in the data storage unit 104 (FIG. 5: step S1). The generation process of the pre-conversion flow is already known and will not be described in detail here.

  For example, when the analysis target data as shown in FIG. 6A is stored in the analysis target data storage unit 101, the contents of the temporary table stored in the data storage unit 104 are as shown in FIG. 6B. The analysis target data is acquired from the database or log file of the analysis target system. The event generation order for each instance is determined from the analysis target data shown in FIG. 6A, and the transition between events in the viewpoint before conversion is converted into the current_before (CB) column and the next_before (NB) column after the conversion. The transition between events is stored in the current_after (CA) column and the next_after (NA) column. For example, when processing the first and second records in FIG. 6A, for the transition from “component A” to “component B” in the business column, “part A” is registered in the CB column, “Part B” is registered in the NB column. On the other hand, regarding the transition from “Line 1” to “Line 2” in the department column, “Line 1” is registered in the CA column and “Line 2” is registered in the NA column. When the second and third records in FIG. 6A are processed, regarding the transition from “component B” to “assembly” in the business column, “component B” is registered in the CB column, and NB Register "Assembly" in the column. On the other hand, regarding the transition from “Line 2” to “Line 3” in the department column, “Line 2” is registered in the CA column and “Line 3” is registered in the NA column. Note that the end event is registered in the CB and CA columns.

  Next, the estimation processing unit 103 calculates a value of a predetermined parameter from the temporary table and stores it in the data storage unit 104 (step S3). The predetermined parameter is used for an estimated value calculation formula for the data amount of the conversion table and an estimated value calculation formula for the data amount of the post-conversion flow.

Specifically, the following parameter values are calculated.
b: 1 to 1 event type
For each value of current_before, the number of types of the corresponding current_after value is calculated. The number of results of 1 is the number of 1 to 1 event types.
k: Average event name length
All types of values of current_before and current_after are acquired, and the average value of the character string length is the average event name length. It is counted that alphanumeric characters = 1 and kanji = 2.
g: Transition type including only one-to-one event One-to-one event is acquired in the counting process of b. Then, for all combinations of current_before and next_before, the number of ones that include only one-to-one events is counted among the corresponding combinations of current_after and next_after.
y: Number of transition types corresponding to one-to-one. For all combinations of current_before and next_before, calculation is performed by subtracting g from the number of corresponding current_after and next_after combinations of one.
n: Total number of event types before conversion
Count the number of all types of current_before values.
r: Number of transition species not corresponding to 1 to 1
For all combinations of current_before and next_before, the number of corresponding current_after and next_after combinations of 2 or more is counted.
x: Average number of divisions after conversion of transitions that do not correspond to 1 to 1
For all combinations of current_before and next_before, the average value of the number of combinations is calculated for the corresponding combinations of current_after and next_after.
l: Number of times storage capacity Although it depends on the maximum number of times assumed, it is usually fixed at about 4 bytes (Java int etc.)
m: Total number of event types after conversion
Number of all types of current_after values

  Then, the estimation processing unit 103 uses the parameter value stored in the data storage unit 104 and uses a pre-defined estimation value calculation formula to calculate the estimated value of the data amount in the conversion table and the post-conversion flow. Is calculated and stored in the data storage unit 104 (step S5).

In this embodiment, the following estimated value calculation formula is adopted.
Conversion table: 2bk + 2yk (1 + ((n−b) / n)) + r (2k + 2kx ((n−b) / n) + xl)
Flow after conversion: (2k + 1) (g + (rx + y) (m / n))

  This estimated value calculation formula is calculated on the assumption that the number of event types and the average character string length of event types can be easily obtained using a temporary table, and can be calculated using relatively few types of easily obtained parameters. Yes. Therefore, a completely accurate data amount cannot be calculated, and another equation may be introduced to estimate a more accurate data amount. Alternatively, it is also possible to introduce a formula for simplifying the estimation more simply and reducing the processing load for calculating the parameter value.

  Then, the estimation processing unit 103 compares the estimated value of the data amount of the conversion table calculated in step S75 with the estimated value of the data amount of the converted flow, and the estimated value of the data amount of the conversion table is more It is determined whether it is small (step S7). When the estimated value of the data amount of the conversion table cannot be said to be smaller, that is, when the estimated value of the data amount of the converted flow is less than or equal to the estimated value of the data amount of the conversion table, the estimation processing unit 103 The flow generation unit 102 is instructed to generate a post-flow (step S11). Then, the process proceeds to step S13. The flow generation unit 102 generates a post-conversion flow using the temporary table stored in the data storage unit 104 or the data stored in the analysis target data storage unit 101, and converts the converted flow data into the first data. 2 stored in the flow storage unit 201. The specific processing content is the same as the pre-conversion flow and is a known method, and thus detailed description thereof is omitted.

  On the other hand, when the estimated value of the data amount of the conversion table is smaller, the estimation processing unit 103 instructs the conversion table generation unit 105 to generate a conversion table (step S9). The processing of the conversion table generation unit 105 will be described in detail later. Then, the process ends.

  After the generation of the post-conversion flow is completed, the flow generation unit 102 discards the temporary table stored in the data storage unit 104 (step S13).

  In this way, data with a smaller estimated value of the data amount is generated, so that a resource called a data storage area can be used effectively.

  Next, processing contents of the conversion table generating unit 105 will be described with reference to FIGS. The conversion table generation unit 105 acquires a temporary table from the data storage unit 104 (step S21). Next, the conversion table generating unit 105 extracts the type of the CB (current_before) value from the temporary table and stores it in a storage device such as a main memory (step S23). For example, a list of CB value types is generated.

  And the conversion table production | generation part 105 specifies one unprocessed CB value (step S25). The conversion table generating unit 105 specifies the type of CA (current_after) value corresponding to the specified CB value in the temporary table and counts the number of types (step S27). As a result, it is possible to specify whether the event is a one-to-one event. Therefore, the conversion table generation unit 105 determines whether the type of CA value corresponding to the specified CB value is 1 (step S29). When the type of CA value corresponding to the specified CB value is not 1, the process proceeds to step S33. On the other hand, when the type of CA value corresponding to the specified CB value is 1, the conversion table generation unit 105 is specified as the pre-conversion value in the one-to-one event conversion unit in the conversion table storage unit 203. A CB value is set, and a corresponding CA value is set as the converted value of the one-to-one event conversion unit in the one-to-one event conversion unit (step S31). Then, control goes to a step S33.

  In step S33, the conversion table generation unit 105 determines whether there is an unprocessed CB value among the types of CB values extracted in step S23 (step S33). If there is an unprocessed CB value, the process returns to step S25. On the other hand, when there is no unprocessed CB value, the processing shifts to the processing in FIG. This completes the one-to-one event conversion unit.

  Shifting to the description of the processing in FIG. 8, the conversion table generation unit 105 extracts a combination type (that is, a transition type) of the CB value and the NB (next_before) value in the temporary table, and stores, for example, a storage device such as a main memory. (Step S35). For example, a list of combinations of CB values and NB values is generated.

  And the conversion table production | generation part 105 specifies one unprocessed combination among the extracted combinations (step S37). Thereafter, the conversion table generating unit 105 checks whether both the CB value and the NB value included in the specified combination have been registered in the one-to-one event conversion unit (step S39). Accordingly, it is determined whether or not this combination is registered in the one-to-one transition converter or a transition converter other than one-to-one. If both the CB value and the NB value included in the identified combination are already registered in the one-to-one event conversion unit (step S41: Yes route), the conversion table generation unit 105 does nothing about the identified combination. Return to step S37. Since the one-to-one event conversion unit can handle it, it is not registered in other conversion units.

  On the other hand, when not registered (step S41: No route), the conversion table generating unit 105 extracts the combination of the CA value and the NA value corresponding to the identified combination from the temporary table (step S43). The appearance frequency is counted for each type of combination of CA value and NA value. The processing shifts to the processing in FIG.

  Shifting to the description of the processing in FIG. 9, the conversion table generating unit 105 determines whether there is only one type of combination of the CA value and the NA value extracted in step S43 (step S45). If only one type of combination of CA value and NA value is extracted, it indicates that there is a one-to-one correspondence between transition types before and after conversion. Therefore, the conversion table generation unit 105 registers the specified combination (CB value and NB value) as the value before conversion of the one-to-one transition conversion unit in the conversion table storage unit 203, and as the value after conversion, Corresponding combinations (CA value and NA value) are registered (step S47). Then, control goes to a step S51.

  On the other hand, if there are two or more combinations extracted in step S43, the conversion table generation unit 105 uses the transition conversion unit other than the one-to-one combination in the conversion table storage unit 203 as the combination specified as the value before conversion. (CB value and NB value) are registered, the corresponding combination (CA value and NA value) is registered as the converted value, and the appearance frequency counted in step S43 is registered as the number of executions (step S49). ). For the corresponding combinations, all the types of combinations extracted in step S43 are registered, and the appearance frequency is registered as the number of executions for that type. In this way, data is registered in transition conversion units other than one-to-one.

  In step S51, the conversion table generation unit 105 confirms whether either the CA value or the NA value included in the corresponding combination extracted in step S43 has been registered in the one-to-one event conversion unit. If applicable, the corresponding part is changed to a blank (step S51). As a result, the amount of data can be reduced.

  Thereafter, the conversion table generating unit 105 determines whether there is an unprocessed combination among the combinations of the CB value and the NB value extracted in step S35 (step S53). If there is an unprocessed combination, the process returns to step S37 via the terminal C. On the other hand, when all the combinations extracted in step S35 have been processed, the conversion table generating unit 105 discards the temporary table stored in the data storage unit 104 (step S55) and returns to the original process. .

  As a result, a conversion table estimated to have a small amount of data is generated and stored in the conversion table storage unit 203.

  In the example described above, an example in which there is one type of pre-conversion flow and one type of post-conversion flow is shown, but there may be a plurality of pre-conversion flows and post-conversion flows.

  Next, with reference to FIGS. 10 to 24, a scene in which data generated by the above-described processing is used will be described.

  For example, when receiving an instruction from the user via the input unit 301, the display switching unit 302 reads the data of the flow before conversion from the first flow storage unit 202, converts it to a flow diagram, and then outputs the output device 305 such as a display device. (FIG. 10: Step S61). In the following description, it is assumed that the first flow storage unit 202 stores data as shown in FIG. Since the transitions are arranged in the order of appearance, a flow diagram can be generated by connecting them as they are. In the case of data as shown in FIG. 11, the flow diagram output from the output device 305 such as a display device in step S61 is data as shown in FIG.

  And the input part 301 receives a viewpoint switching instruction | indication from a user (step S63). Then, the input unit 301 outputs data (for example, “department”) indicating the viewpoint after switching to the display switching unit 302. Then, the display switching unit 302 confirms whether or not the flow data regarding the viewpoint after switching (that is, after conversion) is held in the first flow storage unit 202 or the second flow storage unit 201 (step S65). Regarding this determination, it may be confirmed whether the conversion table storage section 203 holds a conversion table from the viewpoint before switching (that is, before conversion) to the viewpoint after switching (that is, after conversion).

  When the flow data regarding the viewpoint after switching is held, the display switching unit 302 reads out the corresponding flow data from the first flow storage unit 202 or the second flow storage unit 201, and flows from the flow data. A diagram is generated and output to the output device 305 (step S67). Then, control goes to a step S73.

  For example, if data as shown in FIG. 13 is held in the second flow storage unit 201 and this is flow data regarding the viewpoint after switching, a flow diagram as shown in FIG. 14 is generated and a display device or the like is generated. Output to. As a result, the user can immediately confirm the flow regarding the viewpoint after switching. In some cases, flow diagrams before and after switching may be displayed side by side.

  On the other hand, when the flow data regarding the viewpoint after switching is not held in the first flow storage unit 202 and the second flow storage unit 201, the display switching unit 302 causes the flow conversion unit 303 to switch the viewpoint before switching and after switching. A flow conversion instruction including the above viewpoint is output, and the flow conversion unit 303 performs a flow conversion process according to the flow conversion instruction (step S69). This flow conversion process will be described with reference to FIGS.

  For example, the flow conversion unit 303 reads the flow data before the viewpoint switching (FIG. 11) from the first flow storage unit 202, and reads the conversion table data from the conversion table storage unit 203 (FIG. 15: Step S81). For example, the conversion table storage unit 203 stores data as shown in FIGS. 3A to 3C.

  Then, the flow conversion unit 303 generates intermediate Map data from the flow data before viewpoint switching (that is, before conversion) and stores it in a storage device such as a main memory (step S83).

  The intermediate Map data is a Map object that can store a key (Key) and a value (Value) corresponding to the key (Key). For example, Java (registered trademark) java.util.HashMap can be used. In such intermediate Map data, an object in which the transition type of the flow data before viewpoint switching is set to Key and the number of executions and Map (transition type after viewpoint switching) is set to Value is stored. As shown in FIG. 16, for Key, the transition type before the viewpoint switching (transition type before conversion) in FIG. 11 is registered as it is. On the other hand, for the number of executions in Value, the number of executions of each transition type before viewpoint switching is registered as it is. Map in Value is empty.

  Next, the flow conversion unit 303 identifies one unprocessed pre-conversion event in the one-to-one event conversion unit included in the conversion table (step S85). Then, the flow conversion unit 303 searches for the key of the intermediate map data using the identified pre-conversion event, and converts the key of the value-side Map corresponding to the hit key to the post-conversion corresponding to the one-to-one event conversion unit. An event is registered (step S87). FIG. 17 shows the one-to-one event conversion unit again. For example, if Event-B is specified in step S85, the key of the intermediate map data in FIG. Since it appears at the transition of the line, the corresponding post-conversion event “Event-b” is registered in the corresponding Map key on the Value side. When such a process is performed for the three pre-conversion events registered in the one-to-one event conversion unit in FIG. 17, the intermediate Map data in FIG. 16 changes as shown in FIG. As can be seen from FIG. 18, the Map key on the Value side is divided into two so that the preceding event (that is, the transition source event) and the subsequent event (that is, the transition destination event) can be registered. In addition, the number of executions on the Value side is set to Value when a value is registered in the Key in the Map on the Value side.

  Returning to the description of the processing in FIG. 15, the flow conversion unit 303 determines whether all the pre-conversion events have been processed in the one-to-one event conversion unit (step S <b> 89). If there is an unprocessed pre-conversion event, the process returns to step S85. On the other hand, when all the pre-conversion events have been processed in the one-to-one event conversion unit, the processing shifts to the processing in FIG.

  Shifting to the description of the processing in FIG. 19, the flow conversion unit 303 identifies one unprocessed pre-conversion transition in the one-to-one transition conversion unit (step S <b> 91). Then, the flow conversion unit 303 searches for the key of the intermediate map data in the specified pre-conversion transition, and converts the value in the Map on the Value side corresponding to the hit key to the post-conversion corresponding to the one-to-one transition conversion unit. A transition is registered (step S93). FIG. 20 shows the one-to-one transition conversion unit again. For example, if a transition including Event-A and Event-C is specified, the transition of the second row corresponds to the key of the intermediate map data in FIG. . Accordingly, the preceding event “Event-a2” of the corresponding post-conversion transition is registered in the Key of the corresponding Map on the Value side. The subsequent event of the transition after conversion in the one-to-one transition converter is unregistered, but this indicates that the one-to-one event converter can handle it, and has already been registered. However, if both the preceding event and the subsequent event of the post-conversion transition are registered in the one-to-one transition conversion unit, both are registered in the Key in the Map on the corresponding Value side. If such a process is performed for two pre-conversion transitions registered in the one-to-one transition conversion unit in FIG. 20, the intermediate Map data in FIG. 18 is converted as shown in FIG. Although not applicable in the case of FIG. 18, when a post-conversion transition is newly registered in the key on the Value side Map in this step, the number of executions on the Value side is registered in the Value on the Value side Map.

  Then, the flow conversion unit 303 determines whether all pre-conversion transitions in the one-to-one transition conversion unit have been processed (step S95). If there is an unprocessed pre-conversion transition, the process returns to step S91. On the other hand, when all pre-conversion transitions in the one-to-one transition conversion unit have been processed, the flow conversion unit 303 identifies one unprocessed pre-conversion transition in a transition conversion unit other than one-to-one (step S97). ). Then, the flow conversion unit 303 searches for the key of the intermediate map data in the specified pre-conversion transition, and registers the corresponding post-conversion transition in the key of the value-side map corresponding to the hit key (step S99). ). FIG. 22 shows a transition conversion unit other than one-to-one again. For example, if a transition including Event-A and Event-B is specified, the transition of the first row is changed in the key of the intermediate map data in FIG. Applicable. Accordingly, the preceding events “Event-a2” and “Event-a2” of the corresponding post-conversion transition are registered in the Key of the corresponding Map on the Value side. The subsequent event of the transition after conversion in the transition conversion unit other than one-to-one is unregistered, but this indicates that the one-to-one event conversion unit can handle it, and it has already been registered in the intermediate map data. . However, if both the preceding event and the subsequent event of the post-conversion transition are registered in a transition conversion unit other than one-to-one, both are registered in the Key in the Map on the corresponding Value side. If such a process is performed for two pre-conversion transitions registered in a transition conversion unit other than one-to-one in FIG. 22, the intermediate Map data in FIG. 21 is converted as shown in FIG. For the post-conversion transition registered in this step, the number of executions in the transition conversion unit other than one-to-one is registered as it is in the Value in the Map on the Value side.

  Returning to the description of the processing in FIG. 19, the flow conversion unit 303 determines whether all pre-conversion transitions of the transition conversion unit other than one-to-one have been processed (step S <b> 101). If there is an unprocessed pre-conversion transition, the process returns to step S97. On the other hand, when all the pre-conversion transitions of the transition conversion unit other than one-to-one are processed, the process proceeds to the process of FIG.

  24, the flow conversion unit 303 generates post-conversion flow data from the Map on the Value side of the intermediate Map data, and stores it in the post-conversion flow storage unit 304 (step S103). In the Map on the Value side of the intermediate Map data shown in FIG. 23, the same data as the flow data after conversion (after viewpoint switching) shown in FIG. 13 is generated, so the data from the Value side of the intermediate Map data Is stored in the post-conversion flow storage unit 304. Note that the Key on the Value side indicates the transition type, and the Value indicates the number of executions. When there are a plurality of keys of the same type, the respective times are totaled and integrated into one record. Then, the flow conversion unit 303 discards the intermediate map data stored in the storage device such as the main memory (step S105). Then, the process returns to the original process.

  Returning to the description of the processing in FIG. 10, the display switching unit 302 generates a flow diagram from the flow data after conversion (after viewpoint switching) stored in the post-conversion flow storage unit 304 and outputs the flow diagram to the output device 305. (Step S71). Thereby, for example, the flowchart shown in FIG. 14 is displayed.

  Then, after step S67 or step S71, the display switching unit 302 determines whether the user has instructed to end the process via the input unit 301 (step S73). If the end of the process is not instructed, there is a possibility of further instructing switching of viewpoints, and the process returns to step S63. On the other hand, when the end of the process is instructed, the process ends according to the instruction.

  An instruction to return to the flow before conversion (that is, before viewpoint switching) may be input, or there may be an instruction to switch to the third viewpoint.

  By performing the processing as described above, a converted flow can be generated even when a conversion table is adopted. If the converted flow is stored as it is, it can be immediately presented to the user. In this way, it is possible to present a flow of a plurality of viewpoints by switching viewpoints while effectively using the resource of the storage area.

  When three or more flows are handled, the most efficient pattern is estimated as to which one is selected as the pre-conversion flow and the remaining flow is held in the conversion table or itself. For example, when the first to third flows exist, the first flow is selected as the pre-conversion flow, and the second flow and the third flow are both converted into the conversion table. Is held in the conversion table and the third flow is held by itself, the second flow is held by itself and the third flow is held in the conversion table, the second and third flows are The most efficient pattern is selected based on the total estimated amount of data for each pattern, such as when it is held by itself.

  For example, consider a case where a flow before conversion as shown in FIG. 25 (flow data is FIG. 26) is converted into a flow after conversion as shown in FIG. 27 (flow data is FIG. 28). For example, it is assumed that data to be analyzed as shown in FIG. 29 (part of all 324 instances) is obtained, and the temporary table is obtained in the form shown in FIG.

  Using the estimated value calculation formula described above, the method for generating the conversion table is about 336 bytes, and the method for holding the converted flow data is about 406 bytes. Assuming that the method for holding the flow data after conversion is 100%, the method for generating the conversion table requires only about 83% of the data amount, and the capacity can be saved by about 17%. Also, compare the estimation result with the actual capacity. First, in the conversion tables of FIGS. 31A to 31C, the character string data is counted as 1 byte for each alphanumeric character, the kanji character is counted as 2 bytes per character, and the execution frequency data is set as 4 bytes as Java int. When counted, the total conversion table is 340 bytes, and the difference from the estimated 336 bytes is 4 bytes. FIG. 28 shows the post-conversion flow data. If this is counted according to the same rules as those in the conversion table, it is 412 bytes, and the difference from the estimated 406 bytes is 6 bytes. Therefore, it can be determined that the estimation error is small and practical.

  In this way, it is understood that the conversion table is more advantageous, and the conversion table generation unit 105 performs the conversion table generation processing described with reference to FIGS. 7 to 9, and performs the one-to-one event conversion unit illustrated in FIG. A one-to-one transition converter shown in FIG. 31B and a transition converter other than the one-to-one shown in FIG. 31C are generated and stored in the conversion table storage unit 203. Although the data amount of the transition conversion unit other than one-to-one is large, there is an effect of the one-to-one event conversion unit and a relatively large number of blanks are generated.

  Next, when the flow conversion unit 303 performs the flow conversion process, initial intermediate map data as shown in FIG. 32 is generated. Next, when the one-to-one event conversion unit is processed, intermediate Map data as shown in FIG. 33 is generated. Further, when the one-to-one transition conversion unit is processed, intermediate Map data as shown in FIG. 34 is generated. Further, when the transition conversion unit other than one-to-one is processed, intermediate Map data as shown in FIG. 35 is generated. In the transition conversion unit other than one-to-one, since a plurality of rows are associated with one row before conversion after conversion, an existing row of Map on the Value side of the intermediate Map data is changed to a transition other than one-to-one. Copy so that the number of lines after conversion in the conversion part is the same. The reason for copying is that the conversion result of the one-to-one event may be included in the existing line. Then, the converted value of the transition conversion unit other than one-to-one is stored in the Key and Value portions on the Value side of the intermediate Map data. FIG. 35 shows that substantially the same data as the converted flow data shown in FIG. 28 is obtained.

  Although the embodiment of the present technology has been described above, the present technology is not limited to this. The embodiment described above can also be applied to flows other than business flows.

  Furthermore, the functional block diagram described above is merely an example, and may not match the actual program module configuration. As long as the result does not change for the processing flow, it is possible to change the processing order or to execute in parallel. Furthermore, the data holding method described above is merely an example, and data may be held in other formats.

  A conversion table of another format may be adopted for the conversion table. Further, other formulas may be adopted for the estimated value calculation formula.

  The flow analysis apparatus described above is a computer apparatus, and as shown in FIG. 36, a memory 2501, a CPU 2503, a hard disk drive (HDD) 2505, a display control unit 2507 connected to the display device 2509, and a removable device. A drive device 2513 for the disk 2511, an input device 2515, and a communication control unit 2517 for connecting to a network are connected by a bus 2519. An operating system (OS) and an application program for executing the processing in this embodiment are stored in the HDD 2505, and are read from the HDD 2505 to the memory 2501 when executed by the CPU 2503. The CPU 2503 controls the display control unit 2507, the communication control unit 2517, and the drive device 2513 according to the processing content of the application program, and performs a predetermined operation. Further, data in the middle of processing is mainly stored in the memory 2501, but may be stored in the HDD 2505. In an embodiment of the present technology, an application program for performing the above-described processing is stored in a computer-readable removable disk 2511 and distributed, and installed from the drive device 2513 to the HDD 2505. In some cases, the HDD 2505 may be installed via a network such as the Internet and the communication control unit 2517. Such a computer apparatus realizes various functions as described above by organically cooperating hardware such as the CPU 2503 and the memory 2501 described above and programs such as the OS and application programs. .

  The above-described embodiment can be summarized as follows.

  In the information processing method according to the present embodiment, (A) the data amount of the conversion table for converting the first flow into the second flow related to the first flow and the data amount of the second flow itself Storing the estimated value of the data amount of the conversion table and the estimated value of the data amount of the second flow itself in the storage device, and (B) the data amount of the conversion table stored in the storage device When the estimated value is smaller than the estimated value of the data amount of the second flow itself, a conversion table generating step of generating the conversion table and storing it in the storage device is included.

  In this way, the storage resource used when holding a plurality of related flows can be made more efficient.

  Note that in the information processing method according to the present embodiment, (C) the step of displaying the first flow and (D) the instruction to display the second flow are received from the user, the first flow is stored in the storage device. A step of confirming whether a conversion table for converting the data into the second flow is stored or whether the data of the second flow is stored, and (E) the second flow from the first flow to the storage device When the conversion table for converting to the second flow data is stored or when the second flow data is not stored, the conversion table is read from the storage device, and the first flow data is read by the conversion table. You may make it further include the 2nd flow production | generation step which produces | generates a 2nd flow by converting into 2 flows, and the step which displays the (F) produced | generated 2nd flow.

  In this way, flows with different viewpoints can be presented using the conversion table. If the flow is a business flow, the term event may be appropriate, but it is generally called a node.

  In the conversion table described above, (a) a node type pair in which the relationship between the node type appearing in the first flow and the node type appearing in the second flow is a one-to-one relationship is registered. 1 table, (b) the transition type from the first node to the second node appearing in the first flow, and the transition from the third node to the fourth node appearing in the second flow A second table for registering a pair of transition types having a one-to-one relationship with the species, and (c) registering a correspondence relationship of transition types other than the pair of transition types specified in the first table and the second table The third table may be included.

  With such a table configuration, the data amount of the conversion table can be further reduced.

  Further, in the second table and the third table, the node type derived from the first table may be registered as empty. The data amount of the conversion table can be further reduced.

  Further, the conversion table described above may include the three tables described above. Further, in the second flow generation step described above, the second flow is generated by applying to the first flow in the order of the first table, the second table, and the third table. Also good. The second flow can be generated efficiently.

  In addition, the conversion table generation step described above arranges the attribute values of the first attribute used in the record stored in the database (B1) and used as the first flow node in time series for each case. The second flow obtained by arranging the attribute values of the second attribute included in the same record and used as the nodes of the second flow for each item in the first flow instance obtained by Storing each transition in the instance in the temporary table in association with the record from which the node is extracted; and (B2) appearing in the first flow and the node type appearing in the first flow from the temporary table. Extracting a pair of node types having a one-to-one relationship with the node type to be registered in the first table, and (B3) tempo From the table, the first transition type from the first node to the second node appearing in the first flow, and the third transition from the third node to the fourth node appearing in the second flow. A step of extracting a pair of transition types having a one-to-one relationship with the two transition types and registering them in the second table; and (B3) a first node appearing in the first flow from the temporary table If there is a one-to-many relationship between the transition type from the first node to the second node and the transition type from the third node to the fourth node that appears in the second flow, The correspondence relationship may include a step of registering in the third table. A conversion table can be generated efficiently.

  It is possible to create a program for causing a computer to carry out the processing described above, such as a flexible disk, an optical disk such as a CD-ROM, a magneto-optical disk, and a semiconductor memory (for example, ROM). Or a computer-readable storage medium such as a hard disk or a storage device. Note that data being processed is temporarily stored in a storage device such as a RAM.

  The following supplementary notes are further disclosed with respect to the embodiments including the above examples.

(Appendix 1)
Estimating the data amount of the conversion table for converting the first flow into the second flow related to the first flow and the data amount of the second flow itself, and the estimated value of the data amount of the conversion table Storing an estimated value of the data amount of the second flow itself in a storage device;
If the estimated value of the data amount of the conversion table stored in the storage device is smaller than the estimated value of the data amount of the second flow itself, the conversion table is generated and stored in the storage device A conversion table generation step;
An information processing method executed by a computer.

(Appendix 2)
Displaying the first flow;
When an instruction to display the second flow is received from a user, a conversion table for converting the first flow into the second flow is stored in the storage device, or data of the second flow To check if is stored,
If the conversion table for converting the first flow to the second flow is stored in the storage device or if the data of the second flow is not stored, the conversion table is stored in the storage device. A second flow generation step of generating the second flow by reading from the device and converting the data of the first flow into the second flow by the conversion table;
Displaying the generated second flow;
The information processing method according to appendix 1, further comprising:

(Appendix 3)
The conversion table is
A first table for registering a pair of node types having a one-to-one relationship between a node type appearing in the first flow and a node type appearing in the second flow;
The relationship between the transition type from the first node to the second node that appears in the first flow and the transition type from the third node to the fourth node that appears in the second flow is as follows: A second table for registering pairs of transition types having a one-to-one relationship;
A third table for registering correspondences of transition types other than the pair of transition types specified in the first table and the second table;
The information processing method according to supplementary note 1 or 2 including:

(Appendix 4)
The information processing method according to claim 3, wherein in the second table and the third table, the node type derived from the first table is registered as empty.

(Appendix 5)
The conversion table is
A first table for registering a pair of node types having a one-to-one relationship between a node type appearing in the first flow and a node type appearing in the second flow;
The relationship between the transition type from the first node to the second node that appears in the first flow and the transition type from the third node to the fourth node that appears in the second flow is as follows: A second table for registering pairs of transition types having a one-to-one relationship;
A third table for registering correspondences of transition types other than the pair of transition types specified in the first table and the second table;
Including
In the second flow generation step, the second flow is generated by applying to the first flow in the order of the first table, the second table, and the third table. Information processing method.

(Appendix 6)
The conversion table generation step includes:
Each transition in the first flow instance obtained by arranging the attribute values of the first attribute included in the record stored in the database and used as a node of the first flow in time series for each case; Each transition in the second flow instance obtained by arranging the attribute values of the second attribute included in the same record and used as the node of the second flow for each case is extracted from the source of the node Storing them in a temporary table in association with the records of
A node type pair in which the relationship between the node type appearing in the first flow and the node type appearing in the second flow is a one-to-one relationship is extracted from the temporary table and registered in the first table. And steps to
From the temporary table, the first transition type from the first node to the second node that appears in the first flow, and the third node to the fourth node that appears in the second flow. Extracting a pair of transition types having a one-to-one relationship with the second transition type and registering them in the second table;
From the temporary table, a transition type appearing in the first flow from the first node to the second node, and a transition appearing in the second flow from the third node to the fourth node. If the relationship with the species is one-to-many, registering the correspondence with the transition species in the third table;
The information processing method of supplementary note 3 including this.

(Appendix 7)
Estimating the data amount of the conversion table for converting the first flow into the second flow related to the first flow and the data amount of the second flow itself, and the estimated value of the data amount of the conversion table Storing an estimated value of the data amount of the second flow itself in a storage device;
If the estimated value of the data amount of the conversion table stored in the storage device is smaller than the estimated value of the data amount of the second flow itself, the conversion table is generated and stored in the storage device A conversion table generation step;
A program that causes a computer to execute.

(Appendix 8)
Estimating the data amount of the conversion table for converting the first flow into the second flow related to the first flow and the data amount of the second flow itself, and the estimated value of the data amount of the conversion table And an estimation processing unit that stores an estimated value of the data amount of the second flow itself in a storage device;
If the estimated value of the data amount of the conversion table stored in the storage device is smaller than the estimated value of the data amount of the second flow itself, the conversion table is generated and stored in the storage device A conversion table generator,
An information processing apparatus.

101 Analysis target data storage unit 102 Flow generation unit
DESCRIPTION OF SYMBOLS 103 Estimation processing part 104 Data storage part 105 Conversion table production | generation part 201 2nd flow storage part 202 1st flow storage part 203 Conversion table storage part
DESCRIPTION OF SYMBOLS 301 Input part 302 Display switching part 303 Flow conversion part 304 After-conversion flow storage part 305 Output device

Claims (8)

The estimated value of the data amount of the conversion table for converting the first flow into the second flow related to the first flow is the average of the similarity of the flow shape before and after the conversion and the character string length of the node name. calculated based on the second flow data of estimated values of itself, is calculated based on the average string length of transient species numbers and node names of the flow, the data amount of the estimated value of the conversion table Storing an estimated value of the data amount of the second flow itself in a storage device;
If the estimated value of the data amount of the conversion table stored in the storage device is smaller than the estimated value of the data amount of the second flow itself, the conversion table is generated and stored in the storage device A conversion table generation step;
An information processing method executed by a computer. Displaying the first flow;
When an instruction to display the second flow is received from a user, a conversion table for converting the first flow into the second flow is stored in the storage device, or data of the second flow To check if is stored,
If the conversion table for converting the first flow to the second flow is stored in the storage device or if the data of the second flow is not stored, the conversion table is stored in the storage device. A second flow generation step of generating the second flow by reading from the device and converting the data of the first flow into the second flow by the conversion table;
Displaying the generated second flow;
The information processing method according to claim 1, further comprising: The conversion table is
A first table for registering a pair of node types having a one-to-one relationship between a node type appearing in the first flow and a node type appearing in the second flow;
The relationship between the transition type from the first node to the second node that appears in the first flow and the transition type from the third node to the fourth node that appears in the second flow is as follows: A second table for registering pairs of transition types having a one-to-one relationship;
A third table for registering correspondences of transition types other than the pair of transition types specified in the first table and the second table;
The information processing method according to claim 1 or 2, comprising: 4. The information processing method according to claim 3, wherein in the second table and the third table, the node type derived from the first table is registered as empty. The conversion table is
A first table for registering a pair of node types having a one-to-one relationship between a node type appearing in the first flow and a node type appearing in the second flow;
The relationship between the transition type from the first node to the second node that appears in the first flow and the transition type from the third node to the fourth node that appears in the second flow is as follows: A second table for registering pairs of transition types having a one-to-one relationship;
A third table for registering correspondences of transition types other than the pair of transition types specified in the first table and the second table;
Including
3. The second flow generation step generates the second flow by applying to the first flow in the order of the first table, the second table, and the third table. The information processing method described. The conversion table generation step includes:
Each transition in the first flow instance obtained by arranging the attribute values of the first attribute included in the record stored in the database and used as a node of the first flow in time series for each case; Each transition in the second flow instance obtained by arranging the attribute values of the second attribute included in the same record and used as the node of the second flow for each case is extracted from the source of the node Storing them in a temporary table in association with the records of
A node type pair in which the relationship between the node type appearing in the first flow and the node type appearing in the second flow is a one-to-one relationship is extracted from the temporary table and registered in the first table. And steps to
From the temporary table, the first transition type from the first node to the second node that appears in the first flow, and the third node to the fourth node that appears in the second flow. Extracting a pair of transition types having a one-to-one relationship with the second transition type and registering them in the second table;
From the temporary table, a transition type appearing in the first flow from the first node to the second node, and a transition appearing in the second flow from the third node to the fourth node. If the relationship with the species is one-to-many, registering the correspondence with the transition species in the third table;
The information processing method according to claim 3, comprising: The estimated value of the data amount of the conversion table for converting the first flow into the second flow related to the first flow is the average of the similarity of the flow shape before and after the conversion and the character string length of the node name. calculated based on the second flow data of estimated values of itself, is calculated based on the average string length of transient species numbers and node names of the flow, the data amount of the estimated value of the conversion table Storing an estimated value of the data amount of the second flow itself in a storage device;
If the estimated value of the data amount of the conversion table stored in the storage device is smaller than the estimated value of the data amount of the second flow itself, the conversion table is generated and stored in the storage device A conversion table generation step;
A program that causes a computer to execute. The estimated value of the data amount of the conversion table for converting the first flow into the second flow related to the first flow is the average of the similarity of the flow shape before and after the conversion and the character string length of the node name. calculated based on the second flow data of estimated values of itself, is calculated based on the average string length of transient species numbers and node names of the flow, the data amount of the estimated value of the conversion table And an estimation processing unit that stores an estimated value of the data amount of the second flow itself in a storage device;
If the estimated value of the data amount of the conversion table stored in the storage device is smaller than the estimated value of the data amount of the second flow itself, the conversion table is generated and stored in the storage device A conversion table generator,
An information processing apparatus.

Images