JP7219396B2 - Classification program, classification method and classification device - Google Patents

Description

The present invention relates to a sorting program, a sorting method and a sorting apparatus.

In daily operation management of an information processing system, operations such as log collection and software update are repeatedly executed. At this time, in an information processing system, various hardware and software that are its components are related to each other. Therefore, the operation management is rarely completed with a single operation, and a plurality of operations including pre-processing and post-processing associated with the original operation are executed in a predetermined order. Therefore, in some cases, an operation procedure manual describing the order of execution of a plurality of operations and their specific contents is prepared, and daily operation management is performed according to the operation procedure manual.

It is a heavy burden to recreate a new operating procedure manual from scratch every time the components of the information processing system are changed. Therefore, a method for assisting creation of an operating procedure manual has been proposed.
For example, there has been proposed an operation procedure creation support system that assists in modifying an operation procedure manual in accordance with the information processing system after the configuration change when the configuration of the information processing system is changed. The proposed operation procedure creation support system extracts common procedures from various past operation procedure manuals and converts them into components, and also generates a configuration requirement tree that shows the correspondence relationship between the prerequisite system configuration and the procedure components. . The operation procedure creation support system evaluates the necessity of change for each procedure component included in the operation procedure manual before configuration change, and presents the procedure components to be replaced.

Also, for example, when comparing multiple existing operation manuals and extracting reusable common operation sequences, common operation sequence extraction that considers the similarity between unit operations described in different operation manuals A method is proposed. Further, for example, an evaluation method has been proposed in which keywords are extracted from a plurality of existing operating procedure manuals and the specificity of each operating procedure manual is evaluated based on the appearance frequency of the keywords. In addition, for example, an operation that automatically generates an information processing system operation manual by connecting a plurality of work manuals corresponding to a plurality of components included in an information processing system based on the relationships between the plurality of components. A procedure management method has been proposed.

JP 2013-127656 A JP 2016-167123 A JP 2017-49639 A JP 2017-162256 A

It is possible to extract descriptions of typical operation sequences from existing operation manuals, save the extracted descriptions of operation sequences as a library, and reuse the library to create future operation procedures. Conceivable. A typical operation sequence is, for example, an operation sequence commonly appearing in a plurality of existing operation manuals.

It is conceivable to automatically generate a library of operating procedures by analyzing a set of existing operating procedures. However, with automatic library generation, there is a problem that a library with low reusability may be generated because the range (granularity) of consecutive operations extracted from the existing operation manual is not appropriate. . For example, libraries that are too granular may contain non-essential operations, limiting reusability. In addition, a library with too small granularity does not include accompanying pre-processing and post-processing operations, so it may not be an appropriate procedure on its own, and the burden of creating operating procedures may not be reduced. be.

In one aspect, an object of the present invention is to provide a classification program, a classification method, and a classification apparatus that improve the reusability of a library of operating procedure manuals.

In one aspect, a sorting program is provided that causes a computer to perform processing. An operating procedure manual is obtained that includes explanations of a plurality of operations to be performed on an information processing system and that indicates the execution order of the plurality of operations. Based on the system configuration information indicating the plurality of objects included in the information processing system and the phrases included in the explanation of the operation manual, the object targeted by each of the plurality of operations among the plurality of objects is determined. For each two operations that are adjacent in the execution order indicated by the operating procedure, an evaluation value that indicates the strength of the connection between the two operations is calculated based on the relationship between the two objects determined for the two operations. calculate. By determining the division positions in the execution order based on the evaluation values, the explanations of the operations are classified into two or more groups.

Also, in one aspect, a computer-implemented method of classification is provided. Also, in one aspect, a classification device is provided that includes a storage unit and a processing unit.

In one aspect, the reusability of the library of runbooks is improved.

It is a figure explaining the example of the classification device of 1st Embodiment. It is a figure which shows the example of the information processing system of 2nd Embodiment. It is a block diagram which shows the hardware example of an operation management apparatus. 3 is a block diagram showing an example of functions of an operation management device; FIG. It is a figure which shows the 1st example of an operating procedure manual. It is a figure which shows the 2nd example of an operating procedure manual. It is a figure which shows the example of an operation manual. FIG. 10 is a diagram showing a first generation example of a library; FIG. 10 is a diagram showing a second generation example of a library; FIG. 4 is a diagram showing an example of system configuration information; FIG. 10 is a diagram showing an example of a component weight table; FIG. 10 is a diagram showing an example of an inter-operation weight table; FIG. FIG. 13 is a diagram illustrating a third generation example of a library; FIG. 14 is a diagram showing a fourth generation example of a library; FIG. 10 is a diagram showing an example of a library candidate table; 4 is a flow chart showing an example of a procedure for generating a library;

Hereinafter, this embodiment will be described with reference to the drawings.
[First embodiment]
A first embodiment will be described.

FIG. 1 is a diagram illustrating an example of a classification device according to the first embodiment.
The classification device 10 according to the first embodiment supports the creation of a library of operating procedure manuals used for operation management of an information processing system, and reduces the burden of creating operating procedure manuals. The classification device 10 can also be called an information processing device or a computer. The classification device 10 may be a client device operated by a user or a server device connected to a network.

The classification device 10 has a storage section 11 and a processing section 12 . The storage unit 11 may be a volatile semiconductor memory such as a RAM (Random Access Memory), or may be a non-volatile storage such as an HDD (Hard Disk Drive) or flash memory. The processing unit 12 is, for example, a processor such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), or a DSP (Digital Signal Processor). However, the processing unit 12 may include electronic circuits for specific purposes such as ASICs (Application Specific Integrated Circuits) and FPGAs (Field Programmable Gate Arrays). A collection of multiple processors is sometimes called a "multiprocessor" or simply a "processor."

The storage unit 11 stores one or more operating procedure manuals such as the operating procedure manual 13 . Each of the one or more operating procedure manuals includes explanations of a plurality of operations to be performed on the same information processing system that is the object of operation management. Also, one or more operation manuals each indicate the execution order of the plurality of operations.

An information processing system to be operated and managed includes various hardware components such as a server device and a disk drive, and various software components such as an operating system (OS) and middleware. A type of component can be referred to as a "class". A component instance, such as an individual physical server device or disk drive, can be referred to as an "object." For example, for the class of server device, there is a specific object assigned a specific host name and address.

Each of the one or more operating procedure manuals includes a descriptive text describing specific work contents of a plurality of operations to be performed on the same or different objects. The descriptive text may be written in natural language and may include commands to be executed for a specific object. In addition, the description may include information such as the address, host name, and file path of the object as information specifying the target object. The series of operations described in the operating procedure manual includes not only the original operations to achieve the purpose of operation management, but also the operations that are to be executed accompanying the original operations such as pre-processing and post-processing. may be For example, operations include creating a directory, logging in to a server device, copying a log file, transferring a log file, stopping and restarting a server application, and changing OS and middleware settings.

For example, the operating procedure manual 13 includes descriptions of operations 13a, 13b, and 13c. The operation procedure manual 13 indicates that operations 13a, 13b, and 13c are executed in the order of operation 13a, operation 13b, and operation 13c in daily operation management. The explanation of operation 13a describes the work content for the server device having address a1. The explanation of operation 13b describes the work content for the server device with host name b2. The explanation of operation 13c describes the work content for the server apparatus related to file path b3.

The storage unit 11 also stores system configuration information 14 . The system configuration information 14 indicates a plurality of objects included in the information processing system to be operated and managed. System configuration information 14 may include information such as addresses, host names, file paths, etc. for each of the different objects belonging to a class. For example, system configuration information 14 includes information about objects 14a and 14b. The system configuration information 14 indicates that an address a1, a host name a2, a file path a3, etc. are associated with the object 14a. Further, the system configuration information 14 indicates that an address b1, a host name b2, a file path b3, etc. are associated with the object 14b.

Based on the words and phrases included in the explanation of the operating procedure and the system configuration information 14, the processing unit 12 selects objects targeted for each of the plurality of operations described in the operating procedure among the plurality of objects of the information processing system. judge. For example, the processing unit 12 extracts words and phrases that can identify objects such as addresses, host names, and file paths from the description of the operation manual, and searches the system configuration information 14 for objects corresponding to the extracted words and phrases.

For example, the processing unit 12 extracts the address a1 from the description of the operation 13a included in the operating procedure manual 13, and determines the object 14a corresponding to the address a1 to be the target of the operation 13a. Also, the processing unit 12 extracts the host name b2 from the explanation of the operation 13b included in the operating procedure manual 13, and determines the object 14b corresponding to the host name b2 as the target of the operation 13b. Also, the processing unit 12 extracts the file path b3 from the explanation of the operation 13c included in the operating procedure manual 13, and determines the object 14b corresponding to the file path b3 as the target of the operation 13c.

For each two operations that are adjacent in the execution order indicated by the operating procedure manual, the processing unit 12 determines the connection between the two operations based on the relationship between the two objects determined for the two operations. An evaluation value indicating strength is calculated. The evaluation value may be calculated such that the greater the strength of the connection between the two operations, the greater the evaluation value. For example, when the objects of two adjacent operations are the same, the processing unit 12 calculates the evaluation value so that the strength of the connection increases. In addition, when the objects of two adjacent operations are different, the processing unit 12 calculates the evaluation value so that the strength of the connection becomes small.

For example, the processing unit 12 calculates an evaluation value 15a for a pair of adjacent operations 13a and 13b. Since the object 14a corresponding to the operation 13a and the object 14b corresponding to the operation 13b are different, the evaluation value 15a may be calculated to be small. The processing unit 12 also calculates an evaluation value 15b for a pair of adjacent operations 13b and 13c. Since the object 14b corresponding to the operation 13b and the object 14b corresponding to the operation 13c are the same, the evaluation value 15b may be calculated to be large.

The processing unit 12 classifies the explanations of the series of operations into two or more groups by determining the division positions of the series of operations based on the calculated evaluation values. For example, the processing unit 12 determines to divide a set of operations whose calculated evaluation value is equal to or less than a threshold so that they do not belong to the same group. In addition, the processing unit 12 determines not to divide a set of operations whose calculated evaluation value exceeds the threshold so as to belong to the same group. The processing unit 12 may generate one library from descriptions of two or more operations belonging to the same group. It is possible to create a new operation manual by reusing the library. One library represents a sequence of operations with high reusability. For example, one library is a collection of original operations and operations that are likely to be executed along with them.

For example, the evaluation value 15a is below the threshold and the evaluation value 15b exceeds the threshold. Then, the processing unit 12 sets the division position between the operation 13a and the operation 13b, and does not set the division position between the operation 13b and the operation 13c. Then, the processing unit 12 creates a group 16a including the explanation of the operation 13a, and creates a group 16b including the explanations of the operations 13b and 13c. In this case, operation 13a and operations 13b and 13c belong to different libraries.

According to the classification device 10 of the first embodiment, the system configuration information 14 of the information processing system is referred to for each of the series of operations described in the operating procedure manual 13 to determine the target object. be. Then, based on the determined relationships between the objects, the strength of the coupling between adjacent operations is evaluated to determine split locations.

As a result, a library with appropriate granularity is generated from the existing operating procedure manual 13, and the reusability of the generated library is improved. For example, it is possible to reduce the possibility that reusable scenes are limited because the granularity is too large and non-essential operations are included. It also reduces the possibility that the particle size is too small to include the necessary pre- and post-treatments, making it difficult to use alone. As a result, it is possible to reduce the burden of creating a new operating procedure manual when changing the components of the information processing system.

[Second embodiment]
Next, a second embodiment will be described.
FIG. 2 is a diagram illustrating an example of an information processing system according to the second embodiment.

The information processing system of the second embodiment supports operation management that is routinely and repeatedly performed by the operator. The information processing system of the second embodiment includes electronic devices to be operated and managed, such as a business server 31, a file server 32, and a monitoring server 33. FIG. The information processing system of the second embodiment also includes an operation management device 100 used by an operator. The operation management apparatus 100 and electronic devices to be operated and managed are connected to a network 30 . The operation management device 100 corresponds to the classification device 10 of the first embodiment.

The business server 31 is a server computer that executes a server application such as a web server. The file server 32 is a server computer that stores file data using non-volatile storage and manages files using a file system. In the file system, directories are created in a hierarchical structure, directories are identified by directory paths, and files are identified by file paths. The monitoring server 33 is a server computer that monitors other electronic devices and detects abnormalities in other electronic devices.

Components to be operated and managed include these server computers, and may include other electronic devices such as communication devices. Also, the components subject to operation management may include hardware components such as disk drives provided in the server computer. Further, the components to be operated and managed may include software such as OS, middleware, and application software executed by these server computers.

The operation management device 100 is a client computer used by an operator who performs operation management of the information processing system. However, the operation management device 100 may be a server computer. Daily operation management includes collection of log files, analysis of log files, inspection of hardware components, software updates, and the like. The operation management apparatus 100 executes operations for operation management by, for example, transmitting commands to electronic devices.

The operation management device 100 executes a series of operations for achieving a specific purpose of operation management according to a pre-created operation procedure manual. The series of operations includes, in addition to essential operations, operations such as pre-processing and post-processing that are performed incidentally. The operation management device 100 displays the operation procedure manual, presents it to the operator, and executes the operation according to the input from the operator. However, the operation management device 100 may automatically execute a series of operations according to the operating procedure manual. In that case, the operating procedure manual is created in an automatically executable format.

In addition, the operation management device 100 analyzes existing operation manuals, extracts operation sequences that appear in common in a plurality of operation manuals, and generates a library of operation manuals. When the components of the information processing system are changed, the operation management device 100 combines the libraries according to the input from the operator to generate a new operating procedure manual adapted to the changed information processing system. However, the operation management apparatus 100 may automatically generate an operating procedure draft using the library from the changed information processing system and present it to the operator.

FIG. 3 is a block diagram showing an example of hardware of an operation management device.
The operation management device 100 has a CPU 101, a RAM 102, an HDD 103, an image signal processing section 104, an input signal processing section 105, a medium reader 106 and a communication interface 107 connected to a bus. The operation management device 100 corresponds to the classification device 10 of the first embodiment. A CPU 101 corresponds to the processing unit 12 of the first embodiment. A RAM 102 or HDD 103 corresponds to the storage unit 11 of the first embodiment.

The CPU 101 is a processor that executes program instructions. The CPU 101 loads at least part of the programs and data stored in the HDD 103 into the RAM 102 and executes the programs. Note that the CPU 101 may include a plurality of processor cores, and the operation management device 100 may include a plurality of processors. A collection of multiple processors is sometimes called a "multiprocessor" or simply a "processor."

The RAM 102 is a volatile semiconductor memory that temporarily stores programs executed by the CPU 101 and data used by the CPU 101 for calculation. Note that the operation management device 100 may be provided with a type of memory other than the RAM, and may be provided with a plurality of memories.

The HDD 103 is a nonvolatile storage that stores software programs such as an OS, middleware, and application software, and data. Note that the operation management apparatus 100 may include other types of storage such as flash memory and SSD (Solid State Drive), or may include multiple storages.

The image signal processing unit 104 outputs an image to the display 111 connected to the operation management apparatus 100 according to a command from the CPU 101 . As the display 111, any type of display such as a CRT (Cathode Ray Tube) display, a liquid crystal display (LCD: Liquid Crystal Display), an organic EL (OEL: Organic Electro-Luminescence) display, or the like can be used.

The input signal processing unit 105 receives input signals from the input device 112 connected to the operation management apparatus 100 . Input device 112 can be any type of input device, such as a mouse, touch panel, touchpad, keyboard, or the like. Also, multiple types of input devices may be connected to the operation management apparatus 100 .

The medium reader 106 is a reading device that reads programs and data recorded on the recording medium 113 . Examples of the recording medium 113 include magnetic disks such as flexible disks (FDs) and HDDs, optical disks such as CDs (Compact Discs) and DVDs (Digital Versatile Discs), magneto-optical disks (MOs), A semiconductor memory or the like can be used. The medium reader 106 stores programs and data read from the recording medium 113 in the RAM 102 or the HDD 103, for example.

The communication interface 107 is connected to the network 30 and communicates with other information processing apparatuses via the network 30 . The communication interface 107 may be a wired communication interface connected to a wired communication device such as a switch or router, or a wireless communication interface connected to a wireless communication device such as a base station or access point.

FIG. 4 is a block diagram illustrating an example of functions of an operation management device.
The operation management device 100 has an operating procedure manual storage unit 121 , an operation manual storage unit 122 , a configuration information storage unit 123 , a weight information storage unit 124 and a library storage unit 125 . These units are implemented using storage areas of the RAM 102 or HDD 103, for example. The operation management device 100 also has a library candidate generation unit 126 , a library generation unit 127 , an operation manual generation unit 128 and an operation execution unit 129 . These units are implemented using programs executed by the CPU 101, for example.

The operating procedure manual storage unit 121 stores a plurality of operating procedure manuals. One operating procedure manual corresponds to one purpose such as collecting log files or updating software, and describes a sequence of operations for achieving one purpose. Operating procedures are written in natural language and may include identification information of commands to be issued and objects to be targeted. Object identification information includes, for example, an IP (Internet Protocol) address, a host name, a directory path, a file path, and the like.

The operation manual storage unit 122 stores a plurality of operation manuals. One operation manual corresponds to one component class, such as a certain kind of OS or a certain kind of middleware, and describes executable operations for one component class. The operator's manual may include a description of the interfaces that a particular component class has, such as the commands that a particular component class can accept. Since the operation manual is a general description, it does not contain identification information of specific objects such as IP addresses and host names. An operating procedure manual may be created with reference to the operation manual. For example, commands are extracted from different operation manuals corresponding to different component classes, and an operating procedure manual is created by combining the extracted commands with the identification information of the objects to be operated and managed.

The configuration information storage unit 123 stores system configuration information indicating objects of components included in an information processing system to be operated and managed. A component class is a classification concept that indicates a type of hardware or a type of software. A component object, on the other hand, is a physical entity belonging to any class, such as an individual device, software installed on a particular device, or individual file data. The system configuration information associates objects included in the information processing system with identification information such as IP addresses, host names, directory paths, and file paths associated with the objects.

The weight information storage unit 124 stores weight information that is referred to when automatically generating a library from an existing operating procedure manual. The weight information is created in advance and stored in the weight information storage unit 124 . Details of the weight information will be described later.

The library storage unit 125 stores a library that is a reusable operating procedure manual component. A library is a typical set of operation sequences that appear in existing operation manuals, and is a set of meaningful operation sequences as components. By combining two or more libraries stored in the library storage unit 125, it is possible to create a new operating procedure manual for an information processing system whose components have been changed. Since the library shows appropriate combinations of operations and includes operational management know-how, it is possible to create operational procedure manuals without sufficient experience in component elements and operational management. The burden is reduced compared to creating a .

The library candidate generating unit 126 analyzes the existing operating procedure manuals stored in the operating procedure manual storage unit 121, and extracts typical operation sequences that commonly appear in a plurality of operating procedure manuals. The library candidate generation unit 126 also refers to the operation manual stored in the operation manual storage unit 122 to estimate the class of the component targeted by each operation. The library candidate generation unit 126 may subdivide the operation sequence by determining the division position of the extracted operation sequence in consideration of the difference between the estimated classes. Subdivision adjusts the granularity of the operation sequence. The library candidate generation unit 126 outputs the operation sequence after granularity adjustment as a library candidate.

The library generation unit 127 further adjusts the granularity of the library candidates generated by the library candidate generation unit 126 by combining and subdividing the operation sequences to generate a library. In the granularity adjustment by the library generation unit 127, the system configuration information stored in the configuration information storage unit 123 and the weight information stored in the weight information storage unit 124 are referred to. Library generation unit 127 stores the generated library in library storage unit 125 . In the library, the concrete object identification information described in the existing operating procedure manual may be replaced with an abstract tag. For example, in the library, a specific IP address may be replaced with a tag indicating that the IP address of the target object should be described.

The operating procedure manual generating unit 128 generates a new operating procedure manual by combining the libraries stored in the library storage unit 125 when the components of the information processing system are changed. Selection of the library is made in response to input from the operator. Also, the identification information of the target object is input by the operator. However, based on the system configuration information of the changed information processing system, the operating procedure manual generation unit 128 may automatically or semi-automatically generate an operating procedure manual that conforms to the changed information processing system. . The operating procedure manual generation unit 128 stores the generated operating procedure manual in the operating procedure manual storage unit 121 .

The operation executing unit 129 selects one of the operating procedure manuals stored in the operating procedure manual storage unit 121 and displays it on the display 111 according to the input from the operator. The operation execution unit 129 executes a series of operations according to the selected operating procedure manual in response to input from the operator. For example, the operation executing unit 129 transmits a command to the target object. However, the operation procedure manual may be written in a format that can be automatically executed, and the operation execution unit 129 may automatically execute a series of operations according to the operation procedure manual. Automatic execution of a series of operations may be started in response to an input from an operator, or may be started according to a predetermined schedule.

Next, a problem in adopting the library candidate generated by the library candidate generation unit 126 as the library without adjusting the granularity by the library generation unit 127 will be described.
FIG. 5 is a diagram showing a first example of an operating procedure manual.

The operating procedure manual 131 is an example of an existing operating procedure manual stored in the operating procedure manual storage unit 121 . The operating procedure manual 131 is created by an operator with reference to an operation manual, for example. The operation procedure manual 131 is intended for Web server maintenance.

The operation procedure manual 131 describes four operations whose operation names are "login", "switch to root", "syslog confirmation", and "webserver startup suppression". These four operations are performed sequentially. First, "login" is executed, then "switch to root" is executed, then "syslog check" is executed, and then "webserver startup suppression" is executed.

"Login" is an operation of logging into a target server via a certain server. The work content of “login” includes a description in natural language, a login command, and an IP address of a transit server. "Switch to root" is an operation that changes the user authority to the root user. The work content of "switch to root" includes a description in natural language and a command for changing user authority.

"Check syslog" is an operation that retrieves an error message from a log file. In addition to the explanation in natural language, the command for message search is described in the work content of "check syslog". "Webserver startup suppression" is an operation for canceling automatic startup of a Web server, which is a server application. In addition to descriptions in natural language, the work content of "webserver activation suppression" includes a command for checking the activation state and a command for disabling the web server.

FIG. 6 is a diagram showing a second example of the operating procedure manual.
The operating procedure manual 132 is an example of an existing operating procedure manual stored in the operating procedure manual storage unit 121 . The operating procedure manual 132 is created by an operator with reference to an operation manual, for example. The operation procedure manual 132 aims at collecting log files.

The operating procedure manual 132 describes three operations whose operation names are "directory creation", "log collection" and "log transfer". These three operations are performed sequentially. First, "create directory" is executed, then "log collection" is executed, and then "log transfer" is executed.

"Create directory" is an operation for creating a directory in the management server. The work content of "directory creation" describes the IP address of the management server, the directory creation command, and the directory path in addition to the description in natural language.

"Log collection" is an operation to copy a log file held by an application server. In addition to descriptions in natural language, the work content of "log collection" includes the IP address of the application server and a file copy command. "Log transfer" is an operation to transfer the copied log file to the management server. In addition to descriptions in natural language, the work content of “log transfer” includes the IP address of the management server and a file transfer command using FTP (File Transfer Protocol).

FIG. 7 is a diagram showing an example of an operation manual.
The operation manual 133 is an example of an operation manual stored in the operation manual storage unit 122 . The operation manual 133 describes commands that can be accepted by the component class, operating system OS_L. The command description includes the description format of the command and the description format and meaning of options. The operation manual 133 includes descriptions of file copy commands, directory creation commands, and file transfer commands that can be accepted by the operating system OS_L.

FIG. 8 is a diagram showing a first generation example of a library.
The library candidate generation unit 126 extracts an operation sequence that appears in common in a plurality of operating procedure manuals stored in the operating procedure manual storage unit 121 . The operation sequence to be extracted is two or more continuous operations on the operating procedure manual. For example, the library candidate generation unit 126 extracts typical operation sequences appearing in a predetermined number or more of operating procedure manuals. The identity of operations is determined by the identity of operation names and work contents. Operations with a high degree of similarity are considered substantially identical operations. The operation sequence extracted here becomes a library candidate for the first stage.

The library candidate generation unit 126 refers to a plurality of operation manuals stored in the operation manual storage unit 122 and determines the class of the component corresponding to each operation included in the first stage library candidates. In the class determination, the library candidate generation unit 126 extracts commands from the work content of each operation, and specifies classes of components that can accept the extracted commands. As a result, for example, the type of OS and the type of middleware that process the command sent in the operation are specified.

Then, the library candidate generation unit 126 compares component classes between two adjacent operations in the same library candidate. The library candidate generating unit 126 determines not to divide a set of operations having the same component class, and determines to divide a set of operations having different component classes. The library candidate generation unit 126 further divides the operation sequence at the determined division positions, thereby subdividing the library candidates in the first stage. This adjusts the granularity of library candidates.

Here, a case is considered in which the second-stage library candidate generated by the library candidate generation unit 126 is adopted as the library. For example, from the operation procedure manual 132 described above, a library candidate 141 including "create directory", "collect log" and "transfer log" is generated. The component class targeted by "create directory" is determined to be OS_L from the commands included in the work content and the operation manual 133. FIG. The class of the component targeted by "log collection" is determined to be OS_L from the commands included in the work content and the operation manual 133. FIG. The class of the component targeted by “log transfer” is determined to be OS_L from the commands included in the work content and the operation manual 133 . The three operations of the library candidate 141 are not divided because the classes of target components are the same. Therefore, a library 151 is generated that includes "create directory", "collect log", and "transfer log".

However, "create directory" and "collect log" send commands to different server computers even if the types of OSs that can accept commands are the same. That is, even if the classes of the target components are the same, the objects of the target components are different. Also, "create directory" is an unnecessary operation when the directory to which the log files are to be transferred is already prepared, and cannot be said to be an essential operation associated with "collect log". Therefore, the generated library 151 is too granular, and the reusability of the library 151 is reduced.

FIG. 9 is a diagram showing a second generation example of the library.
Here, the operation manual describing the operations "monitoring suppression", "single user mode", "unmount", "drive check", "mount", "multi-user mode" and "monitoring suppression release" is Assume that it is stored in the storage unit 121 .

"Suspend monitoring" is an operation that suspends monitoring by monitoring software in order to suppress the generation of alerts during maintenance. "Single-user mode" is an operation to change the execution mode of the OS from multi-user mode to single-user mode in order to prevent the activation of other processes during maintenance. "Unmount" is an operation that separates the disk drive from the OS file system. A "drive check" is an operation that checks for physical failures in a disk drive.

"Mount" is an operation that connects a disk drive so that it can be recognized from the OS file system. "Multi-user mode" is an operation that returns the execution mode of the OS from single-user mode to multi-user mode. "Release monitoring suppression" is an operation for restarting monitoring by monitoring software. The original operation of this operation manual is "drive check". "Monitoring suppression" corresponds to pre-processing, and "Monitoring suppression release" corresponds to corresponding post-processing. "Single-user mode" corresponds to pre-processing, and "multi-user mode" corresponds to the corresponding post-processing. "Unmount" corresponds to pre-processing, and "mount" corresponds to its corresponding post-processing.

For example, the library candidate generation unit 126 generates library candidates 142 to 146 from this operating procedure manual. Library candidates 142-146 are first stage library candidates. Library candidate 142 includes "supervisory suppression". Library candidate 143 includes "Single User Mode". Library candidates 144 include "unmount", "drive check" and "mount". Library candidate 145 includes "multi-user mode". The library candidate 146 includes "Release Monitoring Suppression".

The library candidate generation unit 126 refers to the operation manuals stored in the operation manual storage unit 122 to determine the classes of components targeted by the operations of the library candidates 142 to 146 . The component class targeted by "monitoring suppression" is determined to be monitoring software. The class of the component targeted by the "single-user mode" is determined to be OS_L. The component class targeted by "unmount" is OS_L. It is judged as Disk. OS_L. Disk is control software that runs on the operating system OS_L. The class of the component targeted by "drive check" is determined to be OS_L. The component class targeted by "mount" is OS_L. It is judged as Disk. The class of components targeted by the "multi-user mode" is determined to be OS_L. The component class targeted by "Release Monitoring Suppression" is determined to be monitoring software.

"Unmount" and "drive check" included in the library candidate 144 target different component classes, and "drive check" and "mount" target different component classes. Therefore, library candidates 144 are divided into three. As a result, library candidate generator 126 generates libraries 152-158. Library 152 includes "monitoring suppression". Library 153 includes a "single-user mode". Library 154 contains "unmount". Library 155 includes "drive checks". Library 156 contains "mounts". Library 157 includes a "multi-user mode". The library 158 includes "Release Monitoring Suppression".

However, "single user mode" and "unmount" send commands to the same server computer even if the types of software that accept commands are different. That is, even if the class of the target component is different, the object of the target component is the same. The same applies to the relationship between "unmount" and "drive check", "drive check" and "mount", and "mount" and "multi-user mode".

Also, "single-user mode", "unmount", "mount" and "multi-user mode" are highly necessary operations that should be executed in conjunction with "drive check". Also, "monitoring suppression" and "monitoring suppression release" correspond to pre-processing and post-processing that should be executed in combination. Similarly, "single-user mode" and "multi-user mode" correspond to pre-processing and post-processing that should be performed in combination, and "unmount" and "mount" correspond to pre-processing and post-processing that should be performed in combination. Equivalent to. Therefore, the generated libraries 152-158 are too granular, and the reusability of the libraries 152-158 is reduced. If you ignore the alerts output by the monitoring software, it is possible to perform a "drive check" without stopping the monitoring software. .

In this way, the library candidates generated by the library candidate generation unit 126 may not have appropriate granularity because the division positions of the operation sequences are not appropriate. Therefore, the library generation unit 127 corrects the division position and adjusts the granularity of the library. As described below, the library generation unit 127 evaluates the degree of coupling for each two adjacent operations on the operating procedure manual. The library generation unit 127 decides to split at positions where the degree of connectivity is equal to or less than the threshold, and decides not to split at positions where the degree of connectivity exceeds the threshold.

FIG. 10 is a diagram showing an example of system configuration information.
The system configuration information 134 is stored in the configuration information storage section 123 . The system configuration information 134 is revised each time a component of the information processing system to be operated and managed is changed. The system configuration information 134 may be manually updated by the operator, or may be automatically updated by collecting information from the information processing system.

The system configuration information 134 registers object names and attributes for each of a plurality of objects included in the information processing system. An object name is a name that identifies an object that is a physical entity of a component. An attribute is identification information given to an object. Attributes that can be used include the host name of the server computer, the IP address of the server computer, a directory path indicating a directory on the file system, a file path indicating a file on the file system, and the like.

For example, a specific host name and a specific IP address are assigned to an object called A server belonging to a class called server computer. Also, a host name different from that of the A server and an IP address different from that of the A server are assigned to the object called B server belonging to the class of server computer.

FIG. 11 is a diagram showing an example of the inter-component weight table.
The inter-component weight table 135 is stored in the weight information storage unit 124 . The inter-component weight table 135 is used when modifying the degree of coupling between two adjacent operations from the class and object of the target component. The inter-component weight table 135 includes items for component 1, component 2, and weight. A component 1 indicates a condition that a component targeted by one of two adjacent operations should have. A component 2 indicates a condition that a component targeted by the other of the two adjacent operations should have. A weight is a value added to the degree of connectivity.

For example, the inter-component weight table 135 includes records in which component 1 is "OS_L (object1)", component 2 is "OS_L (object2)", and the weight is -0.5. This record means that the degree of coupling is lowered by 0.5 when the OS types of the command transmission destinations are both OS_L, but the server computers that are the physical entities of the command transmission destinations are different. Even if the component classes are the same, if the component objects are different, the degree of coupling between operations is often reduced.

Also, for example, the inter-component weight table 135 includes records in which the component 1 is “OS_L (object1)”, the component 2 is “OS_L (object1)”, and the weight is +1.0. This record means that the degree of coupling is increased by 1.0 when the types of OSs of command transmission destinations are both OS_L and the server computer, which is the physical entity of the command transmission destination, is the same. If the classes of the components are the same and the objects of the components are also the same, the degree of coupling between operations is often high.

Also, for example, the inter-component weight table 135 includes records in which component 1 is “OS_L(object1)”, component 2 is “OS_L(object1).Disk”, and the weight is +0.5. This record indicates that the software types of the command transmission destination are OS_L and OS_L. If the disk and the server computer, which is the physical entity of the command transmission destination, are the same, it means that the degree of coupling is increased by 0.5. The reason why the degree of coupling is high is that it can be said that the commands are highly related to each other.

Further, for example, the component weight table 135 includes records in which the component 1 is “class 1”, the component 2 is “class 2”, and the weight is −0.5. This record applies when the conditions of the records above it do not apply. This record means that the degree of coupling is reduced by 0.5 when the component classes are different. In general, when the component classes are different, the degree of coupling between operations is often low.

FIG. 12 is a diagram showing an example of the inter-operation weight table.
The inter-operation weight table 136 is stored in the weight information storage unit 124 . The inter-operation weight table 136 is used when correcting the degree of coupling between two adjacent operations based on the relationship between pre-processing and post-processing. The inter-operation weight table 136 includes entries for pre-processing, post-processing and weight. A keyword for specifying an operation to be executed as preprocessing is registered in the preprocessing item. Keywords for specifying operations to be executed as post-processing corresponding to pre-processing are registered in the post-processing item. A weight is a positive value that is added to the degree of connectivity. Information on a plurality of combinations of pre-processing and post-processing is registered in the inter-operation weight table 136 .

The library generating unit 127 searches for preprocessing keywords from the operation names and work details described in the operating procedure manual, and detects operations corresponding to preprocessing. The library generation unit 127 also searches for post-processing keywords from the operation names and work details described in the operating procedure manual, and detects operations corresponding to post-processing. When a pre-processing operation and a post-processing operation having a corresponding relationship are detected, the library generating unit 127 increases the degree of coupling in the interval from pre-processing to post-processing. That is, the library generation unit 127 adds weight to the degree of coupling for each set of two adjacent operations existing between the pre-processing and the post-processing to make it difficult to split.

FIG. 13 is a diagram showing a third generation example of the library.
Here, it is assumed that the library generation unit 127 further performs granularity adjustment on the processing result of the library candidate generation unit 126 in FIG. The library candidate 161 corresponds to the library 151 in FIG. The library candidate 161 includes three operations of "create directory", "collect log" and "transfer log".

The library generation unit 127 refers to the system configuration information 134 stored in the configuration information storage unit 123, extracts object identification information from the work content of each operation, and determines a target object. For example, the library generation unit 127 determines that the target object is the A server from the IP address included in the work content of "directory generation". Also, the library generation unit 127 determines that the target object is the B server from the IP address included in the work content of "log collection". Also, the library generation unit 127 determines that the target object is the B server from the IP address included in the work content of "log transfer".

Also, the library generation unit 127 sets an initial value of the degree of coupling for a pair of two adjacent operations on the operating procedure manual. The initial value of the degree of coupling is set to 1.0 for a set of operations classified into the same library candidate by the library candidate generation unit 126 . The initial value of the degree of coupling is set to 0 for sets of operations classified into different library candidates by the library candidate generation unit 126 . Therefore, the library generation unit 127 sets the initial value of the degree of coupling between "directory generation" and "log collection" to 1.0. Also, the library generation unit 127 sets the initial value of the degree of coupling between “log collection” and “log transfer” to 1.0.

The library generation unit 127 corrects the degree of coupling based on the inter-component weight table 135 and the inter-operation weight table 136 stored in the weight information storage unit 124 . Since library candidate 161 does not include a set of operations corresponding to pre-processing and operations corresponding to post-processing, only inter-component weight table 135 is applied here.

As for the set of "create directory" and "collect logs", the class of the component targeted by the former is OS_L, and the object of the component targeted by the former is the A server. The component class targeted by the latter is OS_L, and the component object targeted by the latter is the B server. Since the classes are both OS_L and the objects are different, the degree of coupling between "create directory" and "collect log" is reduced by 0.5.

Regarding the set of "log collection" and "log transfer", the class of the component targeted by the former is OS_L, and the object of the component targeted by the former is the B server. The component class targeted by the latter is OS_L, and the component object targeted by the latter is the B server. Since both classes are OS_L and the objects are the same, the degree of coupling between "log collection" and "log transfer" increases by 1.0.

The library generation unit 127 compares the degree of coupling with a predetermined threshold for each pair of adjacent operations, and determines to divide when the degree of coupling is equal to or less than the threshold, and does not divide when the degree of coupling exceeds the threshold. to do). Here, the threshold of the degree of coupling is set to 0.5. Then, since the coupling degree of "directory generation" and "log collection" is 0.5, the library generation unit 127 determines to divide "directory generation" and "log collection". Since the degree of coupling between "log collection" and "log transfer" is 2.0, the library generation unit 127 determines not to separate (combine) "log collection" and "log transfer". Thereby, the granularity of the library candidate 161 is adjusted and the libraries 171 and 172 are generated. Library 171 includes "Create Directory". Library 172 includes "log collection" and "log transfer".

FIG. 14 is a diagram showing a fourth generation example of the library.
Here, it is considered that the library generation unit 127 further performs granularity adjustment on the processing result of the library candidate generation unit 126 in FIG. Library candidates 162-168 correspond to libraries 152-158 in FIG. Library candidate 162 includes "supervisory suppression". Library candidate 163 includes "Single User Mode". Library candidate 164 includes "unmount". Library candidates 165 include "drive check". Library candidates 166 include "mount". Library candidate 167 includes "multi-user mode". The library candidate 168 includes "Release Monitoring Suppression".

The library generation unit 127 refers to the system configuration information 134 stored in the configuration information storage unit 123 to determine the object targeted by each operation. The object "monitoring suppression" is omitted as it is self-explanatory since there is only one monitoring software. The object in "single-user mode" is the A-server. The "unmounted" object is the A server. The "drive check" object is the A server. The "mount" object is the A server. The object in "multi-user mode" is the A server. Since there is only one piece of monitoring software, the object "Release Monitoring Inhibition" is omitted as it is self-explanatory.

Also, the library generation unit 127 sets an initial value of the degree of coupling for a pair of two adjacent operations on the operating procedure manual. Since the operations of the library candidates 162 to 168 belong to different library candidates, the initial values of the degrees of binding are all zero.

Next, the library generation unit 127 corrects the degree of coupling based on the inter-component weight table 135 stored in the weight information storage unit 124 . The coupling between "supervisory suppression" and "single-user mode" is reduced by 0.5 due to the different component classes. The degree of coupling between "single-user mode" and "unmount" depends on component classes OS_L and OS_L. Since it is a Disk and the object is the same, it increases by 0.5. The coupling degrees of "unmount" and "drive check", "drive check" and "mount", and "mount" and "multi-user mode" are similarly increased by 0.5. The degree of coupling between "multi-user mode" and "unsupervised suppression" is reduced by 0.5 due to the different component classes.

Next, the library generation unit 127 corrects the degree of coupling based on the inter-operation weight table 136 stored in the weight information storage unit 124 . "Unmount" and "mount" are related to pre-processing and post-processing. Therefore, the degree of coupling between "unmount" and "drive check" and the degree of coupling between "drive check" and "mount" are increased by 0.5. Also, "single-user mode" and "multi-user mode" are related to pre-processing and post-processing. For this reason, the degree of coupling between "single-user mode" and "unmount", the degree of coupling between "unmount" and "drive check", the degree of coupling between "drive check" and "mount", the degree of coupling between "mount" and "multi-user mode" Coupling is increased by 0.5. Also, "monitoring suppression" and "monitoring suppression release" are related to pre-processing and post-processing. Therefore, each degree of coupling in the interval from "monitoring suppression" to "monitoring suppression cancellation" is increased by 1.0.

Then, the library generation unit 127 compares the degree of coupling with a predetermined threshold value for each pair of adjacent operations, and determines whether to divide (not combine) or not to divide (combine). Since the degree of coupling between "monitoring inhibition" and "single-user mode" is 0.5, it is decided to divide (not combine). Since the coupling degree of "single-user mode" and "unmount" is 2.0, it is determined not to divide (combine). Since the coupling degree of "unmount" and "drive check" is 2.5, it is determined not to split (combine). Since the coupling degree of "drive check" and "mount" is 2.5, it is determined not to divide (combine). Since the coupling degree of "mount" and "multi-user mode" is 2.0, it is determined not to divide (combine). Since the coupling degree of "multi-user mode" and "monitoring inhibition release" is 0.5, it is decided to divide (not combine).

As a result, the libraries 173-175 are generated by adjusting the granularity of the library candidates 162-168. Library 173 includes "supervisory suppression". Library 174 includes "single-user mode", "unmount", "drive check", "mount" and "multi-user mode". The library 175 includes "Release Monitoring Suppression".

FIG. 15 is a diagram showing an example of a library candidate table.
In converting the library candidates 162 to 168 into the libraries 173 to 175, the library generation unit 127 generates a library candidate table 137 for calculating the coupling degree. The library candidate table 137 includes items of class, object, operation, coupling degree and weight. In the library candidate table 137, a plurality of operations described in the operating procedure are registered in order of execution.

The library generation unit 127 registers the operation name in the operation item of the library candidate table 137 . The library generation unit 127 also registers the class name of the component (the name of the component type) in the class item of the library candidate table 137 . The library generation unit 127 registers an initial value of 1.0 or 0 in the degree of binding field of the library candidate table 137 based on the result of classification by the library candidate generation unit 126 . In the example of FIG. 15, the degree of connection between the operation and the next operation is registered in the item of degree of connection included in the record corresponding to an operation.

Next, when the library generating unit 127 determines the object targeted by each operation, it registers the object name in the object field of the library candidate table 137 . The library generator 127 selects a weight from the inter-component weight table 135 based on the combination of the class and the object for each two adjacent operations, and adds the selected weight to the coupling degree item of the library candidate table 137. .

Next, the library generation unit 127 detects a set of pre-processing and post-processing, and selects a weight corresponding to the detected set of pre-processing and post-processing from the inter-operation weight table 136 . The library generation unit 127 registers the selected weight in the weight item of the library candidate table 137 . At this time, the selected weight is registered for each record from the record indicating the operation corresponding to the pre-processing to the record immediately before the record indicating the operation corresponding to the post-processing. When two or more pairs of pre-processing and post-processing are detected, the library generation unit 127 performs the above registration processing for each detected pair.

Then, the library generation unit 127 performs an aggregation process of adding the weight registered in the weight item of the library candidate table 137 to the degree of coupling item. When two or more weights are registered for one operation, the two or more weights are all added to the degree of coupling item. As a result, the final coupling degree is calculated in the coupling degree item.

Next, a processing procedure for library generation will be described.
FIG. 16 is a flow chart showing an example of a library generation procedure.
(S10) The library candidate generation unit 126 extracts a typical operation string that appears in two or more operation manuals from a plurality of existing operation manuals stored in the operation manual storage unit 121. FIG. For example, the library candidate generation unit 126 extracts common operation sequences appearing in a predetermined number or more of operating procedure manuals.

(S11) The library candidate generation unit 126 refers to the operation manual for each component class (type of component) stored in the operation manual storage unit 122, and extracts each operation included in the operation sequence extracted in step S10. Determines the class of the target component. For example, the library candidate generation unit 126 extracts a command from the work content of each operation and searches for a class of components that can accept the command.

(S12) The library candidate generation unit 126 divides the operation sequence extracted in step S10 based on the component class determined in step S11. For example, the library candidate generation unit 126 compares the classes of two adjacent operations, determines not to divide at positions where the classes are the same, and determines to divide at positions where the classes are different.

(S13) The library generation unit 127 sets an initial value of the coupling degree for each two adjacent operations in the operation sequence extracted in step S10. For example, the initial value is set to 0 for the set of operations determined to be divided in step S12, and set to 1.0 for the set of operations determined not to be divided.

(S14) The library generation unit 127 refers to the system configuration information 134 stored in the configuration information storage unit 123, and determines the object of the component targeted by each operation included in the operation sequence extracted in step S10. do. For example, the library generation unit 127 extracts identification information such as an IP address, a host name, and a file path from the work content of each operation, and searches for an object to which the identification information is assigned.

(S15) The library generating unit 127 generates the inter-component weight table 135 stored in the weight information storage unit 124 based on the class of the component determined in step S11 and the object of the component determined in step S14. Search for The library generation unit 127 searches the inter-element weight table 135 for the conditions of the elements possessed by two adjacent operations on the operation sequence extracted in step S10, and selects weights. The library generation unit 127 adds the selected weight to the coupling degree.

(S16) The library generation unit 127 searches for a combination of pre-processing and post-processing registered in the inter-operation weight table 136 stored in the weight information storage unit 124 from among the operation strings extracted in step S10. . Pre-processing operations and post-processing operations are searched by matching operation names, work contents, and keywords.

(S17) The library generator 127 identifies a set of adjacent operations existing between the pre-processing operation and the post-processing operation searched in step S16. In addition, the library generation unit 127 selects weights corresponding to the corresponding set of pre-processing and post-processing from the inter-operation weight table 136 . The library generation unit 127 adds the selected weight to the coupling degree of each identified pair of adjacent operations.

(S18) The library generating unit 127 compares the calculated degree of coupling with a predetermined threshold value for each two adjacent operations on the operation sequence extracted in step S10, and detects division positions. The library generation unit 127 determines to divide (not combine) the operation sequence at positions where the degree of combination is equal to or less than the threshold. Also, the library generation unit 127 determines not to divide (combine) the operation sequence at a position where the degree of coupling exceeds the threshold.

(S19) The library generation unit 127 reconfigures the operation sequence of step S12 so that the operation sequence is divided at the division position detected in step S18 and is not divided at other positions. The library generation unit 127 generates one library from one operation sequence after reconfiguration, and stores the generated library in the library storage unit 125 . In one library, operation names and work contents of operations belonging to one operation sequence after division are described in order of execution.

According to the operation management device 100 of the second embodiment, the degree of connection between adjacent operations is evaluated for common operation sequences extracted from a plurality of existing operation procedure manuals, and the operation sequence is evaluated based on the degree of connection. is divided. The degree of coupling is calculated in consideration of the class of components targeted by operations and the identity of objects. Also, the degree of coupling is calculated in consideration of the correspondence between pre-processing and post-processing.

As a result, an operation sequence with appropriate granularity is automatically generated as a library, improving the reusability of the library. For example, from the viewpoint of the identity of the component objects, other operations that are less relevant to the original operation can be deleted from the library, and the versatility of the library can be improved. In addition, other operations that are closely related to the original operation can be included in the same library. can be easily reused. In addition, it is possible to prevent division of corresponding operations such as pre-processing and post-processing, so that the generated library can be an independently meaningful operation sequence. As a result, it is possible to reduce the burden of creating a new operating procedure manual when changing the components of the information processing system.

10 classification device 11 storage unit 12 processing unit 13 operation procedure manual 13a, 13b, 13c operation 14 system configuration information 14a, 14b object 15a, 15b evaluation value 16a, 16b group

Claims (6)

to the computer,
Acquiring an operating procedure manual including a description of a plurality of operations to be performed on an information processing system and indicating an execution order of the plurality of operations;
Objects targeted by each of the plurality of operations among the plurality of objects based on system configuration information indicating the plurality of objects included in the information processing system and phrases included in the explanation of the operating procedure manual judge,
For each two operations adjacent in the execution order indicated by the operating procedure manual, the strength of coupling between the two operations is determined based on the identity of the determined objects corresponding to the two operations. Calculate the evaluation value shown,
Based on correspondence information including a first keyword indicating pre-processing and a second keyword indicating post-processing corresponding to the pre-processing, and phrases included in the operating procedure manual, detecting from among a first operation indicative of the pre-processing and a second operation indicative of the post-processing;
modifying the evaluation value according to whether the two operations belong to the section from the first operation to the second operation;
Classifying the explanations of the plurality of operations into two or more groups by determining division positions in the execution order based on the corrected evaluation values;
The sorting program that causes the processing to take place. causing the computer to further execute a process of generating a library based on the descriptions of the operations classified into the same group;
A classification program according to claim 1. In calculating the evaluation value, when the determined objects are the same, the evaluation value is calculated so that the strength of the connection is greater than when the determined objects are different.
A classification program according to claim 1. In modifying the evaluation value, the coupling between the two operations is stronger when the two operations belong to the interval than when the two operations do not belong to the interval. modify the rating value,
A classification program according to claim 1 . the computer
Acquiring an operating procedure manual including a description of a plurality of operations to be performed on an information processing system and indicating an execution order of the plurality of operations;
Objects targeted by each of the plurality of operations among the plurality of objects based on system configuration information indicating the plurality of objects included in the information processing system and phrases included in the explanation of the operating procedure manual judge,
For each two operations adjacent in the execution order indicated by the operating procedure manual, the strength of coupling between the two operations is determined based on the identity of the determined objects corresponding to the two operations. Calculate the evaluation value shown,
Based on correspondence information including a first keyword indicating pre-processing and a second keyword indicating post-processing corresponding to the pre-processing, and phrases included in the operating procedure manual, detecting from among a first operation indicative of the pre-processing and a second operation indicative of the post-processing;
modifying the evaluation value according to whether the two operations belong to the section from the first operation to the second operation;
Classifying the explanations of the plurality of operations into two or more groups by determining division positions in the execution order based on the corrected evaluation values;
Classification method. a storage unit for storing an operating procedure manual including explanatory texts of a plurality of operations to be performed on an information processing system and indicating an order of execution of the plurality of operations;
Objects targeted by each of the plurality of operations among the plurality of objects based on system configuration information indicating the plurality of objects included in the information processing system and phrases included in the explanation of the operating procedure manual determining, for each two operations adjacent in the execution order indicated by the operating procedure manual, based on the determined identity of the objects corresponding to the two operations, determining the connection between the two operations; An evaluation value indicating strength is calculated, correspondence information including a first keyword indicating preprocessing and a second keyword indicating postprocessing corresponding to the preprocessing, and phrases included in the explanation text of the operating procedure manual and detecting a first operation indicating the pre-processing and a second operation indicating the post-processing from the plurality of operations, wherein the two operations are selected from the first operation to the second operation. Descriptive text of the plurality of operations by correcting the evaluation value according to whether or not it belongs to the section up to the operation, and determining the division position in the execution order based on the corrected evaluation value. into two or more groups; and
A classifier having a

Images