JP2018136636A - Information processing apparatus and information processing method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information processing apparatus that assists in reproducing business specifications from log information in an arbitrary form.SOLUTION: A control unit 11 of an information processing apparatus 1 comprises a setting file generation unit 111 and a standard log generation unit 112. The setting file generation unit generates a setting file 153 by processing a Web log 151 as an object of reproduction of business specifications by a business specification reproduction system according to a result of preprocessing of the Web log (for example, selection of essential information to be described in a standard log 155) and a layout of the standard log that log layout information 152 represents. The standard log generation unit closely examines an effective part of reproduction of business specifications by the business specification reproduction system, reads in a setting file, and converts a Web log which is included in the setting file and effective in reproduction of business specifications to generate a standard log.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an information processing apparatus and an information processing method.

  When migrating from the old system to the new system, system development (replacement development) is required for the replacement. In replacement development, a large proportion of the new system follows the specifications of the old system, and there are rare cases where an accurate document of the old system remains. In such a case, by analyzing the source of the old system, the specification of the old system is reproduced. However, even if the system level specification can be reproduced from the source, the business level specification can be reproduced. It is often difficult to reproduce (hereinafter sometimes referred to as business specifications). Therefore, in the past, business-level specifications are often reproduced by documents such as user interviews and procedure manuals. However, due to reasons such as user's subjectivity and maintenance of procedure manuals, I don't know the specifications.

  In view of such a problem, for example, in Patent Document 1, the procedure of acquiring a Web page, capturing a screen, extracting a link included in the page, and acquiring a linked page is started recursively from a specified URL. The page transition is automatically acquired by doing. Also, in Patent Document 2, an image log indicating the ID of a user who has instructed printing of a printer or a multifunction peripheral and an image of a printed document is accumulated, and an image log included in a log record group registered based on this information A set of log records belonging to the same individual task is obtained from the comparison between them, and the workflow corresponding to the individual task is estimated from the processing time of the similar image and attributes such as user information.

JP 2010-79342 A JP 2009-224958 A

By the way, when reproducing a business specification, it is assumed that data that is essential for reproducing the business specification is input to a computer that reproduces the business specification. In addition, log information generated by operating the system is in an arbitrary format that does not have a predetermined standard, and does not necessarily include data that is essential for reproducing business specifications. However, Patent Documents 1 and 2 neither describe nor suggest a method for acquiring data that is essential for reproducing business specifications, and thus it is difficult to reproduce business specifications from log information in an arbitrary format. Yes.
Therefore, the present invention has been made in view of such circumstances, and an object of the present invention is to support so that business specifications can be reproduced from log information in an arbitrary format.

In order to achieve the above object, the present invention provides:
An information processing apparatus that processes an operation log that records a user's business operations,
For each operation, specify the user who performed the operation, the date and time when the operation was performed, and the processing content by the operation,
Based on the identified user, date and time, and processing content, set a case that combines a plurality of operations executed as the processing content,
For each set item, a control unit that generates a standard log that associates the user who executed the item, a plurality of operations constituting the item, and the start date and time and end date and time of each of the items,
It is characterized by that.
The present invention also provides:
An information processing method in an information processing apparatus for processing an operation log recording a user's business operation,
A control unit of the information processing apparatus;
For each operation, identifying the user who performed the operation, the date and time when the operation was performed, and the processing content by the operation;
Based on the identified user, date and time, and processing content, setting a case that combines a plurality of operations executed as the processing content;
For each set item, a step of generating an operation log that associates the user who executed the item, a plurality of operations constituting the item, and the start date and time and end date and time of each of the items is executed. ,
It is characterized by that.
Other means will be described later.

  According to the present invention, it is possible to assist so that business specifications can be reproduced from log information in an arbitrary format.

It is a functional lineblock diagram of the information processor of this embodiment. It is a specific example of a web log. It is a specific example of a standard log. It is explanatory drawing of the production example 1 of a transition chain. It is explanatory drawing of the creation example 2 of a transition chain. It is explanatory drawing of the creation example 3 of a transition chain. It is explanatory drawing of the creation example 4 of a transition chain. It is a flowchart of a standard log generation process.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, exemplary embodiments of the invention will be described in detail with reference to the accompanying drawings.

≪Configuration≫
As shown in FIG. 1, the information processing apparatus 1 according to the present embodiment is configured so that a business specification reproduction system disclosed in JP-A-2016-139178 (hereinafter referred to as a reference) has a business flow (information for creating a business specification). Is a device that outputs information used to generate (reproduce business specifications). In the present embodiment, description of the procedure itself for generating the business flow by the business specification reproduction system of the reference document is omitted. The information processing apparatus 1 is a computer that includes a control unit 11, a communication unit 12, an input unit 13, an output unit 14, and a storage unit 15.

The control unit 11 controls the entire processing executed by the information processing apparatus 1. The control unit 11 is, for example, a CPU (Central Processing Unit). The communication unit 12 functions as an interface for exchanging information with other computers via a network (not shown). The input unit 13 receives input of information from the operator. The input unit 13 is, for example, a keyboard or a pointing device. The output unit 14 outputs a processing result by the control unit 11. The output unit 14 is, for example, a display. The storage unit 15 stores a processing result by the control unit 11. The storage unit 15 is, for example, an HDD (Hard Disk Drive), a ROM (Read Only Memory), or a RAM (Random Access Memory).
Functions executed by the control unit 11 (described later) are realized by the control unit 11 executing the program read on the storage unit 15.

  The control unit 11 includes a setting file generation unit 111 and a standard log generation unit 112. The setting file generation unit 111 generates a setting file 153 to be described later. The standard log generation unit 112 generates a standard log 155 to be described later.

The storage unit 15 stores a Web log 151, log layout information 152, a setting file 153, a reproducible statistical result 154, and a standard log 155.
The Web log 151 is an operation log in which operations on the user's business are recorded by the user executing the business using the user terminal. The operation log is an access log stored in a Web server (not shown) accessed by the user terminal. The information processing apparatus 1 acquires an operation log from a Web server and stores it in the storage unit 15 as a Web log 151. Such a Web log 151 is not a log generated for the business specification reproduction system of the reference document, that is, a log having a format that can be immediately input to the business specification reproduction system.

  The log layout information 152 is information that defines the layout of the standard log 155 generated by the standard log generation unit 112. Layout modes are well known and will not be described in detail.

  The setting file 153 is a file to be read by the standard log generation unit 112 when the standard log generation unit 112 executes processing for generating the standard log 155. The setting file 153 is a file obtained by processing the Web log 151 according to the layout of the log layout information 152. The setting file 153 specifies essential information that is essential for the business specification reproduction system of the reference document to generate a business flow. In the present embodiment, the essential information includes (1) a matter ID of a matter executed on business, (2) a screen ID of a screen displayed on the user terminal when the matter is executed, and (3) execute the matter. The user who performs the operation for the case, (4) the start date and time of the operation for executing the case, and (5) the end date and time of the operation for executing the case. A case is a unique item that can specify one operation, and is equivalent to a combination of a plurality of operations (processing contents by operation). The case ID is a unique ID that can identify one operation. The screen ID is an ID of a screen displayed on the user terminal when the user executes one of a plurality of tasks constituting the matter, and has a function of identifying each of the tasks. The essential information is not limited to these five types. The designation of the essential information can be realized, for example, by an input from the operator of the information processing apparatus 1.

  The reproducible statistical result 154 is data obtained by tabulating the contents and the number of business operations performed in the operation recorded in the Web log 151. The business specified by the reproducible statistical result 154 is a business related to the business specification to be reproduced by the business specification reproduction system of the reference document. The reproducible statistical result 154 is generated together with the standard log 155 by the standard log generation unit 112.

  The standard log 155 is an operation log obtained by converting the Web log 151 so that it can be input to the business specification reproduction system of the reference document. The standard log 155 is an intermediate generation log, and is input information necessary for specifying business information. The standard log 155 includes essential information specified in the setting file 153 for each operation.

  As shown in FIG. 2, the Web log 151 expresses one operation on the user's business by one line and is described in a plurality of lines. In FIG. 2, only a part of the Web log 151 is shown. Each line of the Web log 151 includes an IP address (reference numeral 21), an access date (reference numeral 22), a request (reference numeral 23), a URL (reference numeral 24), and a referer (reference numeral 25).

  As shown in FIG. 3, the standard log 155 expresses one operation on the user's business by one line in a different form from the Web log 151, and is described collectively for a plurality of lines. Each line of the standard log 155 includes a user ID (reference numeral 31), a case ID (reference numeral 32), a screen ID (reference numeral 33), a start date and time (reference numeral 34), and an end date and time (reference numeral 35).

  When generating the standard log 155, the standard log generation unit 112 generates a user ID (reference numeral 31) using the IP address (reference numeral 21) of the web log 151. If the IP address (symbol 21) cannot be obtained from the web log 151, the standard log generation unit 112 uses the session ID (component of the referrer (symbol 25) in FIG. 2) to obtain the user ID (symbol 31). Can be generated.

  Further, the standard log generation unit 112 can group the operation groups that can be estimated to be performed on the same case for each operation (line) of the standard log 155 and attach the same case ID (reference numeral 32). . That is, different case IDs can be assigned to different operation groups, and the cases included in the standard log 155 can be demarcated. The referrer (reference numeral 25) can be a means of demarcation of a matter. A method for separating the cases will be described later with reference to FIGS.

  Further, the standard log generation unit 112 generates a screen ID (reference numeral 33) using the URL (reference numeral 24) of the web log 151. When the name of the URL (reference numeral 24) exists, the screen ID (reference numeral 33) can be written in Japanese as shown in FIG.

  In addition, the standard log generation unit 112 generates a start date (code 34) and an end date (code 35) using the access date (code 22) of the Web log 151. The start date and time (reference numeral 34) is the same as the date and time indicated by the access date and time (reference numeral 22). Since the date and time corresponding to the end date and time (reference numeral 35) are not originally recorded in the Web log 151, the end date and time (reference numeral 35) is set to the same date and time as the start date and time (reference numeral 34) for convenience.

  In addition, the code | symbol 36 in FIG. 3 is a column into which the value (example: applicant, approver) which shows the title of the user who performs each operation is input. When the post (role) of the user specified by the IP address in the web log 151 is known, the post can be entered in the column 36. When the post of the user specified by the IP address in the Web log 151 is not known, “unknown” is entered in the field of reference numeral 36 as shown in FIG. The information processing apparatus 1 can store, in the storage unit 15, a role correspondence table that associates a user with a job title for each user whose job title (role) is known. In addition, the setting file 153 may include a flag for determining whether or not to record the title of the user in the standard log 155 for a user who performs an operation for executing the matter.

<Method of separating the cases>
There are various methods for attaching a case ID (symbol 32) to a plurality of logs in the standard log 155 shown in FIG. 3 and separating the cases, and the concept of transition chain is introduced. The transition chain is a collection of one operation performed by the user. Examples of transition chains are one login to logout, one application / approval operation, or one based on a time difference. The transition chain has a function of grouping operation groups estimated to have been performed in the same case.

(Transition chain creation example 1)
A transition chain can be created using the referrer (reference numeral 25) shown in FIG. As shown in FIG. 4, a request source and a request (refer to reference numeral 23 in FIG. 2) are determined for each operation of the Web log 151 whose access date and time (see reference numeral 22 in FIG. 2) is ascending order. The case will be described. The request source is described in the referrer (see reference numeral 25 in FIG. 2) of the Web log 151. In this case, the procedure of tracing the previous operation log request from the last request source (indicated by an arrow in FIG. 4) is repeated, and the operation log that can be traced by dividing the matter by the operation log that cannot be traced. Set up one transition chain for the group. Thereafter, the above procedure is repeated for the last request source for which no transition chain is set.

  According to the above, the operation log that does not have a predetermined value at the request source (illustrated by “−” in FIG. 4) becomes the first operation log in the operation log group in which the transition chain is set, It becomes a landmark. According to FIG. 4, since the request source of the operation log on the third line is blank, it can be estimated from the operation log on the third line that an operation for a new case has started. Therefore, the case is divided by the operation log on the second line, and one transition chain is set for the operation log group on the first to second lines. As a result, as shown in FIG. 4, a case ID named “CHAIN1” is attached to the operation log group in the first and second lines.

Further, since the request source of the operation log on the 6th line is blank, it can be estimated from the operation log on the 6th line that an operation for a new case has started. Therefore, the case is divided by the operation log on the fifth line, and one transition chain is set for the operation log group on the third to fifth lines. As a result, as shown in FIG. 4, a case ID named “CHAIN2” is attached to the operation log group in the third to fifth lines. In the same manner, each time a case is divided, case IDs with names “CHAIN3” and “CHAIN4” are attached.
Note that the method of naming the project ID is arbitrary as long as it is unique.

(Transition chain creation example 2)
When a request (work) symbolizing a case delimiter is found in the Web log 151, a transition chain can be created. For example, when the user performs a login operation or an operation for displaying a portal screen, it can be estimated that the user has finished the work in progress. Therefore, a request such as a login or portal screen is registered in advance in the property file for the storage unit 15 or the standard log generation unit 112 as a request symbolizing a case delimiter.

  As shown in FIG. 5, a case will be described in which a request (see reference numeral 23 in FIG. 2) is determined for each operation of the Web log 151 whose ascending order of access date and time (see reference numeral 22 in FIG. 2). Requests symbolizing the case delimitation are “login” and “portal screen”, and are illustrated as delimitation conditions based on the screen name in FIG.

  According to FIG. 5, since the operation log request on the third line is “login”, it can be estimated from the operation log on the third line that an operation for a new case has started. Therefore, the case is divided by the operation log on the second line, and one transition chain is set for the operation log group on the first to second lines. As a result, as shown in FIG. 5, a case ID named “CHAIN1” is attached to the operation log group in the first and second lines.

  Further, since the operation log request on the sixth line is the “portal screen”, it can be estimated from the operation log on the sixth line that an operation for a new case has started. Therefore, the case is divided by the operation log on the fifth line, and one transition chain is set for the operation log group on the third to fifth lines. As a result, as shown in FIG. 5, the case ID named “CHAIN2” is attached to the operation log group in the third to fifth lines. In the same manner, each time a case is divided, case IDs with names “CHAIN3” and “CHAIN4” are attached.

(Transition chain creation example 3)
A transition chain can be created using a query in the Web log 151. The query is a parameter accompanying the request. Creation Example 3 can be used in conjunction with Creation Example 2. For example, when a value indicating a specific user is shown in the query, it can be estimated that the specific user has finished the work in progress. Therefore, a specific query that suggests a specific user or the like is registered in advance in the property file for the storage unit 15 or the standard log generation unit 112 as a query that symbolizes a case delimiter.

  As shown in FIG. 6, a case will be described in which a request (see reference numeral 23 in FIG. 2) is determined for each operation of the Web log 151 in which the downward direction on the page is the ascending order of access date and time (see reference numeral 22 in FIG. 2). When a query is attached to the request, “?” Is added after the request, and the query is input. The request symbolizing the case delimiter is “login” and “portal screen”. In FIG. 6, the request is illustrated as a delimiter condition based on the screen name. Also, the query symbolizing the case delimitation is “userA” (indicating user A) and “userB” (indicating user B), and are illustrated as delimitation conditions by accompanying information in FIG.

  According to FIG. 6, since the operation log request on the third line is “login” and the query is “id = userB” (query indicating the user B), the operation log on the third line relates to the user B. It can be estimated that an operation for a new case has started. For this reason, the case is divided by the operation log on the second line, and one transition chain is set for the operation log group related to user A on the first and second lines. As a result, as shown in FIG. 6, a case ID named “userA1” is attached to the operation log group related to user A in the first and second lines.

  Further, since the operation log request on the sixth line is the “portal screen”, it can be estimated from the operation log on the sixth line that an operation for a new case has started. For this reason, the case is divided by the operation log on the fifth line, and one transition chain is set for the operation log group related to the user B on the third to fifth lines. As a result, as shown in FIG. 6, a case ID named “userB2, CHAIN3” is assigned to the operation log group related to user B in the third to fifth lines. In the same manner, each time a case is divided, case IDs with names “CHAIN4” and “userB2” are attached.

(Transition chain creation example 4)
A transition chain can be created using the access date and time (reference numeral 22) shown in FIG. If the access date / time of the target operation log is significantly different from the access date / time of the previous operation log, the matter ends with the previous operation log, and a new matter starts from the target operation log. Can be estimated. Therefore, a threshold value for the time difference between adjacent access dates is registered in advance in the property file for the storage unit 15 or the standard log generation unit 112.

  As shown in FIG. 7, the screen name (refer to reference numeral 23 in FIG. 2) is equivalent to the screen name (see reference numeral 23 in FIG. 2) for each operation of the Web log 151 in the ascending order of the access date and time (simply “date and time” in FIG. 7). Hereinafter, a case where accompanying information (query)) is defined will be described. The threshold value for the time difference between adjacent access dates and times is, for example, 30 minutes, and is illustrated as a delimiter condition based on the time difference in FIG.

  According to FIG. 7, the time difference between the operation log date and time (2016/07 / 20_10: 05) on the 6th line and the operation log date and time (2016/07 / 20_11: 10) on the 7th line is 30 minutes or more. Therefore, it can be estimated from the operation log on the seventh line that an operation for a new case has started. Therefore, the case is divided by the operation log on the sixth line, and one transition chain is set for the operation log group on the first to sixth lines. As a result, as shown in FIG. 7, the case ID named “CHAIN1” is attached to the operation log group in the first to sixth lines.

  In addition, since the time difference between the operation log date and time on the 12th line (2016/07 / 20_11: 15) and the operation log date and time on the 13th line (2016/07 / 21_10: 30) is 30 minutes or more, 13 From the operation log on the line, it can be estimated that an operation for a new case has started. For this reason, the case is divided by the operation log on the 12th line, and one transition chain is set for the operation log group on the 7th to 12th lines. As a result, as shown in FIG. 7, a case ID named “CHAIN2” is attached to the operation log group in the first to sixth lines. In the same manner, the cases are separated by time difference, and the case ID named “CHAIN3” is attached.

  The standard log generation unit 112 generates the standard log 155 (see FIG. 3) according to the above-described creation examples 1 to 4. At that time, since individual cases are specified, the standard log generation unit 112 outputs the contents and the number of operations related to the specified cases as a reproducible statistical result 154.

<< Process >>
As shown in FIG. 8, the standard log generation process for the information processing apparatus 1 to convert the Web log 151 and generate the standard log 155 is as follows.
First, the information processing apparatus 1 performs pre-processing of the Web log 151 that is the target of the business specification reproduction by the business specification reproduction system of the reference document (step S1). Specifically, essential information to be described in the standard log 155 is selected. Further, the work on the job is associated with the screen ID (or URL) of the screen displayed on the user terminal when the work is performed. When the user's title is recorded in the standard log 155, a role correspondence table that associates the user with the title is stored in the storage unit 15. In addition, the Web log 151 is finely edited as a design item so that the standard log 155 can be input to the business specification reproduction system of the reference document.

  Next, the information processing apparatus 1 uses the setting file generation unit 111 to process the Web log 151 according to the layout of the standard log 155 indicated by the log layout information 152 and the result of the pre-processing in step S1 to generate the setting file 153. Generate (step S2).

  Next, the information processing apparatus 1 uses the standard log generation unit 112 to identify an effective part of the business specification reproduction by the business specification reproduction system of the reference document from the Web log 151 (step S3). Specifically, image data, CSS (Cascading Style Sheets) data, and other noise information included in the setting file 153 are deleted. As a result, the Web log 151 included in the setting file 153 becomes a Web log 151 effective for reproducing business specifications. Further, the standard log generation unit 112 analyzes the Web log 151 effective for reproducing the business specification and outputs a reproducible statistical result 154.

Next, the information processing apparatus 1 causes the standard log generation unit 112 to read the setting file 153, converts the Web log 151 included in the setting file 153, which is effective for reproducing business specifications, and generates the standard log 155 (step S1). S4). Specifically, the standard log generation unit 112 extracts a value corresponding to essential information from each operation log in the Web log 151. Further, the standard log generation unit 112 edits the extracted value so as to be a value (see FIG. 3) that can be input to the business specification reproduction system of the reference document. Further, the standard log generation unit 112 attaches the case ID to the edited operation log according to the transition chain creation examples 1 to 4 (FIGS. 4 to 7) already described.
This completes the standard log generation process.

According to the present embodiment, an operation log that is not generated for the business specification reproduction system of the reference document can be reliably converted into a standard log 155 that can be input to the business specification reproduction system.
Therefore, it is possible to support so that business specifications can be reproduced from log information in an arbitrary format.

  In addition, when setting multiple projects from multiple operations included in the operation log, multiple types of methods can be prepared to separate the cases, and by selecting the appropriate method, the business specifications by the business specification replay system Can improve the reproduction accuracy.

  Further, when the operation log is the Web log 151, it is possible to assist so that the business specification can be reproduced regardless of the format of the Web log 151.

(Modification)
The present invention is not limited to the above-described embodiment, and can be modified without departing from the spirit of the present invention. For example, there are the following (a) and (b).
(A): The operation log processed by the information processing apparatus 1 of the present embodiment may be the Web log described in the present embodiment, or may be an operation log recorded on another type of recording medium. Good. In the case of a Web log, the Apache (registered trademark) access log described in this embodiment may be used, or another type of access log may be used. The information processing apparatus 1 according to the present embodiment can process not only the operation log but also a log output from an application. That is, the information processing apparatus 1 can process a business log including these logs. Due to the performance of the application or the loss of the business log, some or all of the essential information described in this embodiment may not be included in the business log. In this case, data including part or all of the essential information can be input from outside and included in the business log.
(B): Among operations recorded in the operation log, operations that do not practically constitute execution of work may be excluded. For example, in FIG. 5, a case consisting of a request group (first and second lines) with a case ID “CHAIN1” is simply logged out immediately after logging in on the login screen, and eventually logged in. The user is not performing any work. In this case, the information processing apparatus 1 may perform processing so that the case ID is not attached to the request group on the first and second rows. Specifically, the case exclusion list is stored in the storage unit 15 of the information processing apparatus 1, and an operation group to be excluded (for example, a request group including login and logout immediately after login) is registered in the case exclusion list. That's fine. Thereby, since the excluded case is not recorded in the standard log 155 and is not input to the business specification reproduction system of the reference document, the accuracy of reproduction of the business specification by the business specification reproduction system can be improved. .

In addition, it is possible to realize a technique in which various techniques described in this embodiment are appropriately combined.
The software described in this embodiment can be realized as hardware, and the hardware can also be realized as software.
In addition, hardware, software, flowcharts, and the like can be changed as appropriate without departing from the spirit of the present invention.

DESCRIPTION OF SYMBOLS 1 Information processing apparatus 11 Control part 12 Communication part 13 Input part 14 Output part 15 Storage part 111 Setting file generation part 112 Standard log generation part 151 Web log 152 Log layout information 153 Setting file 154 Reproducible statistical result 155 Standard log

Claims (10)

An information processing apparatus that processes an operation log that records a user's business operations,
For each operation, specify the user who performed the operation, the date and time when the operation was performed, and the processing content by the operation,
Based on the identified user, date and time, and processing content, set a case that combines a plurality of operations executed as the processing content,
For each set item, a control unit that generates an operation log that associates the user who executed the item, a plurality of operations that configure the item, and the start date and time and end date and time of each of the items,
An information processing apparatus characterized by that. The controller is
One matter is set by combining a plurality of operations that can be changed by following the access destination described in the processing content.
The information processing apparatus according to claim 1. The work that symbolizes the separation of the case is registered in advance as a separation work,
The controller is
One matter is set by combining a plurality of operations executed after the first separation operation as the separation operation is executed until the second separation operation as the separation operation is executed.
The information processing apparatus according to claim 1. The controller is
When the interval between the date and time when the first work executed as the processing content is executed and the date and time when the second work executed after the first work is executed exceeds a predetermined time, Consider the end of the first work as the end of the case including the first work, and set one case.
The information processing apparatus according to claim 1. The operation log processed by the information processing apparatus is a Web log.
The information processing apparatus according to claim 1, wherein the information processing apparatus is an information processing apparatus. An information processing method in an information processing apparatus for processing an operation log recording a user's business operation,
A control unit of the information processing apparatus;
For each operation, identifying the user who performed the operation, the date and time when the operation was performed, and the processing content by the operation;
Based on the identified user, date and time, and processing content, setting a case that combines a plurality of operations executed as the processing content;
For each set item, a step of generating an operation log that associates the user who executed the item, a plurality of operations constituting the item, and the start date and time and end date and time of each of the items is executed. ,
An information processing method characterized by the above. The controller is
One matter is set by combining a plurality of operations that can be changed by following the access destination described in the processing content.
The information processing method according to claim 6. The work that symbolizes the separation of the case is registered in advance as a separation work,
The controller is
One matter is set by combining a plurality of operations executed after the first separation operation as the separation operation is executed until the second separation operation as the separation operation is executed.
The information processing method according to claim 6. The controller is
When the interval between the date and time when the first work executed as the processing content is executed and the date and time when the second work executed after the first work is executed exceeds a predetermined time, Consider the end of the first work as the end of the case including the first work, and set one case.
The information processing method according to claim 6. The operation log processed by the information processing apparatus is a Web log.
The information processing method according to any one of claims 6 to 9, wherein the information processing method is used.

Images