JP2006107141A - Process generation support device and method, and program and storage medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily obtain knowledge information required for processes in a system for easily and efficiently generating a process flow even in the state that a process order in a series of processes is not clear. <P>SOLUTION: The title included in the process is made to hold relation information with a knowledge file required for the title beforehand. Also, the process is made to hold attributes, the duplication processing of the process and the title is added, and the retrieval and preparation of a target desired process are facilitated. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a process generation support technique, and more particularly to a process generation support technique that can be suitably used to process a new process for which a process procedure has not been established.

  Conventional process generation will be described with reference to the drawings.

  FIG. 29 is a system block diagram illustrating an example of a block configuration of a system used for performing a conventional process generation.

  In FIG. 29, 301 is a title holding means, 302 is a flow holding means, 303 is a database, and 304 is a central processing unit.

  In the database 303, a title holding means 301 for storing and holding the name of the process to be performed and the contents corresponding to the process name (the contents of each process constituting the process and the title which is the name of each process); And a flow holding unit 302 that stores and holds “START title” that is the name of the beginning of the title (step) and “END title” that is the name of the last step. The central processing unit 304 can record the title name and the process contents having the title name in the title holding unit 301 based on the input information, and can extract the title name from the title holding unit 301. In addition, the title context can be recorded in the flow holding means 302 or extracted.

  FIG. 30 is a diagram for explaining an example of a process generation procedure. First, a title D is input as one title constituting the process via the central processing unit 304 (FIG. 30A). Next, another title is input and arranged along the processing procedure (flow). Here, the title B performed after the title D is input after the title D (FIG. 30B). Further, the title A constituting this process is input. At this time, since it is known that the title A is performed after the title B, the title A is input so as to be positioned after the title B (FIG. 30C). Note that the titles are not only arranged in the order in which they are performed, but are also connected by threads (lines) so that their order becomes clear.

  If it is known that the title F constituting this process is performed after the title D and before the title A, and the title B and the title F are different independent titles, the title F is the title D and the title A. The title D and the title A are respectively connected by a thread. Also, the title H performed after the title A is arranged after the title A as a title H by a thread (FIG. 30D).

As described above, in the above-described conventional technology, even when a new process is clearly specified, the titles of the flow parts already known in the process are connected in order from the top in the order, and as a whole Has generated a process. (For example, see Patent Document 1, Patent Document 2, and Patent Document 3)
JP 2001-134653 A JP-A-5-307555 Japanese Patent Laid-Open No. 08-264405

  However, in the conventional process generation method, when creating various process flows, the context of each title, which is a component, is determined, and the creator of the flow ensures that the entire process or part of the process is understood. It was a very difficult task to generate the desired flow unless you were a person. Also, at the time of creating the process flow, even if all the titles included in the process are known and the context of the title has been determined, it is necessary to review the process for some reason and change the flow. When this occurs, in addition to adding new titles or deleting existing titles, it has been necessary to perform complicated and error-prone operations such as changing the context and rearranging.

  Therefore, it is impossible for an input person who does not fully understand the process or the contents of the process with ambiguous procedures to represent the process as a flow, or a large amount of work is required to complete the process flow. It had been.

  On the other hand, when an expert who is familiar with the process generates the flow of the process, there is another problem. In general, knowledge is classified into knowledge that is described (recognized) in a document called formal knowledge and can be recognized and knowledge that is not described in a document called tacit knowledge. Tacit knowledge includes knowledge that can be formalized but only knowledgeable by an expert, or knowledge that is not formalized because the expert does not recognize it as knowledge. Therefore, the flow of a process created by a skilled person who has acquired a lot of tacit knowledge is often missing or omitted as it should be for the unskilled person, and the unskilled person executes the process. At that time, items and knowledge that are originally expressed in the flow and should be written are not described. As a result, the flow created by the skilled person is often difficult to use by the unskilled person as it is, and a lot of work and time are required for the correction and improvement, so that the flow is rarely used effectively.

  In addition, if the established process flow contains unnecessary or inappropriate titles, the appropriate process flow that removes them before executing the process in consideration of the processing conditions (prerequisites) is optional. Could not be generated. Hereinafter, in the present invention, the process thus changed (changed) is referred to as an “extraction process”.

  Furthermore, the process contents and knowledge (knowledge data) maintenance held in the title holding means in the database are modified after extracting the title by the central processing unit. Therefore, a process flow in which new knowledge and process contents are frequently changed requires a lot of work and time for maintenance.

  Therefore, the present invention has been made in view of the above-described problems, and an object thereof is to make it easier to create and change a process flow.

  In order to solve the above-described problems and achieve the object, a process generation support system according to the present invention is determined by a determination unit that determines the context of titles that are process names existing on a database, and the determination unit. Arranging means for rearranging the titles according to the context and arranging them on the display screen; Extracting means for extracting the titles according to the input condition to the database; Titles extracted by the extracting means on the display screen according to the context Relocation means for rearranging, selection means for selecting a title, associating means for associating the selected title with knowledge data existing in the knowledge database, and display for displaying the knowledge data on the display screen according to the associated information And means.

  In addition, the process generation support method according to the present invention includes a determination step for determining the context of a title that is a process name existing on a database, and rearranging the titles according to the context determined in the determination step on the display screen. Selecting the title, selecting the title in accordance with the input conditions to the database, extracting the title in accordance with the input conditions to the database, rearranging the title to be rearranged on the display screen according to the context, and selecting the title And an associating step for associating the selected title with the knowledge data existing on the knowledge database, and a displaying step for displaying the knowledge data on the display screen according to the associated information. .

  A program according to the present invention causes a computer to execute the process generation support method described above.

  A storage medium according to the present invention stores the above-described program in a computer-readable manner.

  According to the present invention, it is possible to create and change a process flow more easily.

  DESCRIPTION OF EMBODIMENTS Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the drawings.

  However, the technical scope of the present invention is not limited by the following description, and it goes without saying that modifications and combinations can be appropriately made within the scope of the gist of the present invention. In this embodiment, a process generation support system will be described as a specific example of creating an unclear process flow into a clear process flow.

(First embodiment)
FIG. 2 is a system configuration diagram showing the configuration of the first embodiment of the process generation support system of the present invention.

  In FIG. 2, the process generation support system includes a display device 21, an input device 22, a main storage device 23, a central processing device 24, an external storage device 25, and a communication device 26. As shown in the figure, these devices are connected to each other so that they can communicate with each other.

  FIG. 3 is a system block diagram for explaining a block configuration of a system used to perform process generation according to the present embodiment. It has the same configuration as that of FIG. 29 used for the description of the conventional example, and the characteristic processing of this embodiment is executed in the central processing unit.

  In FIG. 3, 30 is a process holding unit, 31 is a title holding unit, 32 is a flow holding unit, 33 is a database, 34 is a knowledge database, 21 is a display device, and 24 is a central processing unit. Reference numeral 35 denotes an extraction process holding unit, 36 denotes a title holding unit for the extraction process, and 37 denotes a flow holding unit for the extraction process. The database 33 and the knowledge database 34 are held in the external storage device 25 shown in FIG.

  The database 33 includes a process holding unit 30 that stores and holds process names, classification information, creation information, update information, and access right information, and title names and contents corresponding to the respective process names by the process holding unit, A title holding unit 31 that stores and holds knowledge data, extraction conditions, creation information and update information, and a flow in which a title (START title) and an end title (END title) are associated and stored between titles. Holding part 32. Similarly, an extraction process holding unit 35 that stores and holds the name, classification information, creation information, update information, and access right information of the extraction process extracted and generated from the process according to the extraction conditions, and each extraction process by the extraction process holding unit The title holding unit 36 that stores and holds the title name, content, knowledge data, creation information, and update information corresponding to the name, and the start title (START title) and the end title (END title) are associated between the titles The flow holding unit 37 that is stored and held also exists in the database 33.

  Further, the knowledge database 34 has various knowledge files (for example, calculation tables, documents, images, etc.).

  The central processing unit 24 develops the information input from the input unit 22 shown in FIG. 2 on the main storage unit 23, performs various data processing to be described later, and stores the results in the database 33 with titles (each processing). Record the information related to the title and the knowledge file in the knowledge database, extract it from the database 33, hold the title order in the database 33, or extract it You can also. Furthermore, it is extracted from the knowledge database 34 based on the order of titles included in the process selected by the input device 22, the title and content selected by the input device 22, and the relationship information between the title and the knowledge file. The knowledge file can be displayed on the display device 21. This system can be used through the communication device 26 from devices other than the devices in which the database 33 and the knowledge database 34 exist.

  FIG. 4 is a diagram showing an example of a display screen used for inputting contents related to a process related to the present embodiment. This display screen is displayed on the display device 21 of FIG.

  In FIG. 4, as input items, 41 is a process name, 42 is a classification name as a process category, and 43 is access right information for setting edit authority of the process. Reference numerals 44 and 45 respectively denote process creation information and update information. In this embodiment, these items are input by the system. Therefore, the process creation information 44 and the update information 45 are items that are displayed on the display device 21 but cannot be input by the input device 22.

  FIG. 5 is a flowchart illustrating an example of processing in process generation according to the present embodiment.

  Referring to this figure, the processing in the present embodiment includes step S50 for determining whether a process is new after startup or whether the process already exists in the database, and if it is new in step S50, a process holding unit on the database ( Step S51 for generating a new process in FIG. 3:30), creation information input step S52 for inputting creation information of the new process and access information (for example, a user name) having access rights to the process creation user, and this new process Steps S53 and S54 for generating a title holding unit and a flow holding unit for storing a title and flow information included in the new process, and a process input screen for inputting a new process name / classification / access right for the process ( FIG. 4) is displayed at step S55 and step S55. With an update information input step S56 to update the process, and a step S57 of storing the process holding portion of the database by the input information that.

  If the process already exists in the database after the activation of this process, the process has step S58 for selecting the process, and the access right is obtained through step S59 for checking the access information stored in the process holding unit. For example, step S55 is processed as an input screen (FIG. 4) for editing already input information (process name / classification / access right).

  FIG. 6 is a diagram illustrating an example of a display screen used for inputting a title and contents related to the title according to the present embodiment.

  This display screen is displayed on the display device 21 of FIG. In FIG. 6, as input items, 61 is the title name, 62 is the title name as the title context information, 63 is the title content, 64 is the relationship information with the knowledge data related to the title, and 65 is the title extraction condition. It is. Reference numerals 66 and 67 denote title creation information and update information, respectively. In this embodiment, these items are input by the system. Accordingly, the title creation information 66 and the update information 67 are items that are displayed on the display device 21 but cannot be input by the input device 22. In the present embodiment, a hyperlink is exemplified as the relationship information with the knowledge data 64 related to the title. The hyperlink can be input by the input device 22, and a predetermined knowledge file can be extracted from the knowledge database 34 and displayed on the display device 21 by executing the hyperlink whose input has been completed. It is possible to confirm whether or not the relationship information to the desired knowledge file related to is correct.

  In this embodiment, in order to finally complete the process, at least information to be input includes a title name and a title name before or after the title. In FIG. 6, at least a title name 61 and a previous title name 62 preceding (preceding) the title name are input. The title content 63, the relationship information 64 with the knowledge data, and the extraction condition 65 are provided as necessary, and are not indispensable items for generating a process flow.

  If the title is an indispensable title in the process, for example, the condition “required” is input as an initial value, and it is found that the extraction condition 65 is a title that is necessary only under a specific condition. If so, enter that particular condition. Of course, if the extraction condition is not known at the time of creating the title, it may be input when it is found.

  The title name information input by the input device 22 on the title input screen is stored in the title storage unit 31 (FIG. 3) in the title storage step S74 in FIG. 7, and the previous title name information is stored in the flow in the flow storage step S78. Each is stored in the unit 32 (FIG. 3).

  When the previous title 62 is input, the central processing unit 24 records the context information between the pair of titles, that is, between the selected title and the previous title, in the flow holding unit 32. Although not shown, when a selected title and a subsequent title subsequent to the selected title are input, the context information between the selected title and the subsequent title is retained as described above. Since each title does not hold adjacent title information, there is no inconsistent context, and even if all the titles have not been determined in advance, only the titles whose context is known Enter it.

  In the process of creating a process, the title that precedes the title is often unclear. For this reason, in this embodiment, it is not necessary to input the previous title name 62 of the title in such a situation. This is because when the flow is visualized as will be described later in FIG. 1, the title is displayed so that the worker can easily identify the title without the following title, and the worker can connect the title while viewing the visualized flow. This is because it is possible to complete the process by generating the flow by inputting the previous title name 62 that precedes (previous) the title name again.

  FIG. 7 is a flowchart showing an example of processing in the flow control of the process of the present invention.

  Referring to this figure, in the processing according to the present embodiment, when a title is input after startup, it is determined whether the title is new or already exists in the database, and if it is new in step S71, it is stored on the database. A new title generation step S72 for generating a new title in the title holding unit, a creation information input step S721 for inputting creation information (FIG. 6: 66) of a newly created title, and an existing title in step S71, the title Title selection step S715 for selecting, title input step S73, title holding step S74 for holding the title input in step S73 in the title holding unit 31, and generation of connection information based on the held title information Connection information creation step to be performed The flow generation step S77 for generating a flow based on the title S62 and the title name 62 of the title held in step S75, and the flow generated in step S77 or step S714 described later are held in the flow holding unit 32. The flow holding step S78, the flow display step S79 for displaying the flow held in the flow holding unit 32, the flow displayed in step S79 is confirmed, and the input of the title is continued, or a desired extraction process is generated Whether to generate a test flow (a flow generated by deleting titles that do not satisfy the extraction condition from the process and rearranging the remaining titles) to determine whether or not to end the work Determination step S710 and the title extraction condition for acquiring the title extraction condition The input step S711, the title extraction step S712 for extracting a title that matches the specified extraction condition, the connection information creation step S713 for regenerating the connection information based on the extracted title context information, and the step S713 A test flow generation step S714 for generating a flow from the connection information.

  FIGS. 1-1 to 1-19 are diagrams for explaining in detail an example of the flow generation procedure of the process according to the present embodiment.

  When a title is input in the title input 1 (FIG. 1-1), the title is arranged on the flow as shown in the flow display 1 (FIG. 1-2). With the generation of a new title, title creation information is input by the system (FIG. 7: step S721). In this embodiment, date information is used as creation information. When the input of the title is completed, the title update information is similarly input (FIG. 7: Step S76).

  It is not necessary to pay attention to the context of the titles, and the titles can be input in any order without thinking (FIGS. 1-3). At that time, if the title is clearly known, the title shown in the flow display 3 (FIGS. 1-5) can be obtained by inputting the title as shown in the title input 2 (FIGS. 1-4). Thus, a partially connected flow is generated. This is an example of a display screen for inputting a title (FIGS. 6 and 1-1). Among the title names necessary for completing the process and the previous title name located before the title, the previous title name Indicates that you do not need to enter. In the process generation process, it is often impossible to determine the names of titles positioned before and after a certain title, which is a device for assisting process generation from such an ambiguous state.

  Next, assuming that a complete title can be input, a procedure for completing the flow by performing processes such as adding / deleting a title, inputting a context, etc. on the generated flow shown in the flow display 3 (FIGS. 1-5) Will be described. This flow connection process indicates that a flow can be generated from a part where the context of the part is known even if the entire flow is not known.

  A procedure for inputting the previous title to the title arranged on the flow will be described.

  When the title to be corrected is selected, the selected title is displayed on the flow so that it can be easily identified as shown in the display flow 4 (FIGS. 1-6). In this embodiment, a method of displaying the outline of the outer frame of the title thickly is used as an example. Not only is it possible to change the appearance such as line thickness from other titles, but the entire flow can also be moved so that the selected title is placed at a specific position on the display screen, such as the center or right center. Good.

  In the title input 3 (FIGS. 1-7), when the destination title (B) is input to the selected title D, the flow shown in the flow display 5 (FIGS. 1-8) is generated according to the input destination title information. The In this case, since the information of the title D stored in the title holding unit and the flow generation unit is updated, the title update information is changed by the system. In this embodiment, the date information is updated.

  Similarly, the title input 4 (FIG. 1-9) shows the input procedure of the title B and the extraction condition of the title B, and the flow display 6 (FIG. 1-10) is a flow generated by inputting this context information. The titles A-B-D and the title E-F are arranged in a connected state. In the flow display 7 (FIGS. 1 to 11), although not shown, the title E is input with the previous title (the title name is title B) and the title G is input with the title (the title name is title H). The generated flow is shown.

  The procedure for adding a new title is not shown because it is the same process as described above. However, when a new title C (first title name is title B) is input, the flow shown in the flow display 8 (FIG. 1-12) is changed. (The outer frame of title E is not yet bold at this point).

  A procedure for inputting knowledge data (relationship information with a knowledge file) to a title (title E) arranged on the flow will be described.

  When the title to be corrected is selected, the outline of the selected title E is displayed with a bold line as shown in the display flow 8 (FIG. 1-12). Next, knowledge data (for example, hyperlink) is input from the input screen of title E shown in title input 5 (FIGS. 1-13). When the input of the hyperlink is completed, a predetermined knowledge file is displayed on another screen by executing the hyperlink.

  When deleting a title on the flow, if the title to be deleted (title H) is selected, the outline of the selected title H is displayed with a bold line as shown in the flow display 9 (FIG. 1-14), and then the title is input. 6 (FIG. 1-15), when the deletion process is input from the input screen of title H, the selected title H is deleted from the flow, and from the context of the deleted title (by the connection information processing method described later) ) The system generates connection information between titles again, and the flow shown in the flow display 10 (FIG. 1-16) is generated.

  As described above, the flow display step S79 from the start of the flowchart (FIG. 7) and the title input 1 (FIG. 1-1) to the flow display 3 (FIG. 1-5) in the detailed description of the generation procedure of the process, the flow is displayed. It is possible to easily generate and visualize a flow by arranging a title only with the title name that has been conceived and the information before and after the title. In the flow determination step S710, the visualized flow (flow display 3 (FIG. 1-5)) is checked, and if correction is necessary, the process returns to step S71 in the flowchart (FIG. 7), and the process generation procedure is described in detail. From the flow display 4 (FIG. 1-6) to the flow display 9 (FIG. 1-14), operations such as connection of titles, addition of missing titles, deletion of surplus titles, and reconnection of flows are performed. For these operations, only the title name and the context information of the title need be input.

Also, the update information of the process that includes these titles is sequentially updated by the title update information that is updated when a title is newly created or modified (FIG. 5: step S56).
If all the extraction conditions for the titles that make up the process flow are "required", the extraction process flow generated based on this process is the same as the created process flow, so repeat the above procedure. A flow is created, and if it is determined in the flow determination step S710 that there is no problem with the created flow, the process generation is terminated.

  On the other hand, when there is an extraction condition unique to the title, the flow of the extraction process regenerated from the flow of this process is different from the flow of the original process. Therefore, if it is necessary to check the flow of the extraction process, an extraction test is performed according to the following procedure to check whether there is a problem in the created process flow.

  In title extraction condition input 1 (FIGS. 1-17), the extraction conditions input to all the titles constituting the process are displayed, and an arbitrary extraction condition is input (selected) as a test (title extraction condition input step S711). When the extraction condition information is input, a test flow is generated from the process flow and displayed by the title extraction step S712, the connection information creation step S713, and the test flow generation step S714 (FIG. 1-18).

  In the present embodiment, since the extraction condition 2 that is the extraction condition of the title B is not selected in the title extraction condition input 1 (FIG. 1-17), the title B is not extracted (deleted) from the process flow and remains. A test flow is generated from the title and its context information. Further, by selecting the title (title E), the outline of the selected title E is displayed with a bold line as shown in FIG. 1-18, and then the title display screen is displayed as shown in the test title display (FIG. 1-19). Is displayed. On the title display screen, the title cannot be corrected other than executing the hyperlink input as knowledge data to display the knowledge file.

  In this way, input of extraction conditions assumed when creating an extraction process and the flow display of the extraction process are repeated as an extraction test, and if there are problems or improvements in the generated test flow, the process returns to the start, and the process flow Create.

  FIG. 8 is a flowchart showing the detailed logic processing of connection information creation step S75 and step S713 in the present embodiment.

  Referring to this figure, the connection information creation step in the present embodiment includes step S81 for obtaining information of a designated process, step S82 for obtaining a title extraction condition from the designated process, and a designated extraction condition from the title holding unit. Step S83 for extracting a title that matches the title, Step S84 for extracting a flow in which both the START and END titles are extracted from the flow holding unit, and Step S85 for stacking the extracted title and flow Step S86 for extracting a flow whose END title is not to be extracted from the flow holding unit, Step S87 for stacking the extracted START title in the flow extracted in Step S86, and the flow holding unit Extract flows whose START titles are not subject to extraction Step S88, step S89 in which the extracted END title is stacked in the flow extracted in step S88, the START title stacked in step S87 and the END title stacked in step S89 are traced back from the END title. In step S810 for connecting and creating a flow, it is determined whether or not a processable title remains in the END title stacked in step S89, and if it remains, step S811 is repeatedly executed from step S810 and step S87. It is determined whether there is a stacked START title, and if it remains, step S812 is repeatedly executed from step S86, step S813 is deleted from the flow holding unit with the same START / END title, and the same START is issued from the flow holding unit. tight Step S814 for determining whether there are a plurality of titles, Step S815 for deleting a flow that eventually arrives at the same END title when a plurality of the same START titles exist, and a title not to be extracted from the flow holding unit The flow has START or END again, and if there is, step S816 is deleted.

  FIG. 9 is a diagram illustrating the logic details of the connection information creation unit in the present embodiment. The logic details of the connection information creation unit will be described with reference to the drawing.

  In FIG. 9A (extraction of titles from processes), for a plurality of processes A, the flow holding unit holds connection information of each title as shown in the figure. Here, the flow A whose START title is -1 indicates the head of the flow and indicates that there is no connection information that follows. Note that the display of the flow shown in the process A is a diagram for explanation, and such information does not exist on the holding unit. This flow display is generated from the flow holding unit by the flow display step S79 of the flow control device of FIG.

  Hereinafter, a detailed logic process for creating connection information will be described with reference to FIG.

  Titles A, C, and D are extracted from the above flow holding unit in step S83 for extracting titles that match the extraction conditions from the title holding unit in FIG. Next, in steps S84 in which both START / END processes match the title extracted by the extraction condition from the flow holding unit in FIG. 8, the flows of -1-A and AD are extracted.

  Next, a process for creating the extracted title connection will be described.

  9-2A and 9-2B (connection creation), titles A, C, D, F, and G are extracted from the flow in process B according to the title extraction conditions. At this time, the flow extracted in step S84 in FIG. 8 is only -1-A. Here, the flow of AB, BE, and B-H is extracted by step S86 which extracts the flow from which the END title is not extraction object from the flow holding part of FIG. Here, taking the flow of AB as an example, A is stacked in step S87 of stacking the START title of the extracted flow of FIG. Next, titles BC, BD, BE, and BH are extracted in step S88 for extracting a flow whose START title is not extracted from the flow holding unit in FIG. Here, the flow of title BC is taken as an example. Here, title C is stacked in step S89 of stacking the END title of the extracted flow in FIG. Next, the flow A-C is generated in step S810 of creating a flow by connecting the stacked START title and END title in FIG.

  Similarly, it is determined whether or not a processable title remains in the stacked END title in FIG. 8. If it remains, step S811 is repeatedly executed from step S810, and the presence or absence of the START title stacked in step S87 is determined. If so, the process is repeated until all the flows are processed in step S812 repeatedly executed from step S86. This is the data in the flow holding unit shown in the connection creation.

  Next, in step S813, the duplicate information is deleted from the flow generated in the steps so far, the flow having the same START / END title is deleted from the flow holding unit in FIG. 8, and the same START title is deleted from the flow holding unit. Step S814 for determining whether there are a plurality of records, Step S815 for deleting a flow that eventually reaches the same END title if there are a plurality of records, and deleting a flow that is not subject to extraction conditions from the flow holding unit Step S816 will be described.

  First, titles A, C, F, I, and H are extracted from the process D according to the extraction conditions in the section of FIG. At this time, in the flow holding unit, as shown in the flow holding unit of connection creation (FIGS. 9-2A and 9-2B), -1-A, AC, AC, -1-F, F- H, F-I, and I-H are generated. When this is displayed in the flow display step S79 of FIG. 7, there are two flows A-C, FI for the flow F-H, as in the flow holding unit of FIG. 9-3 (deletion of duplicate connection). , There will be another route called I-H. For this reason, an extra connection line indicated by a thick black line is displayed in the flow display. In order to delete this, the flow having the same START / END shown in the flow A-C is deleted in step S813 in which the flow having the same START / END title is deleted from the flow holding unit in FIG. Next, the flow is deleted in step S814 for determining whether there are a plurality of the same START titles and in step S815 for deleting a flow that eventually reaches the same END title when there are a plurality of the same START titles. As a result, excess connection information is deleted as shown in FIG. Finally, verification is performed in step S816 in which the START title starts from -1 and the START title or END title has a title not to be extracted. The above is the description of the connection information creation unit in the creation of the test flow of the extraction process that extracts the title from the designated process according to the extraction condition. New creation and deletion of the title in the process of creating the process (FIG. 7: Steps S71 to 710) The same processing is performed in the connection information creation step (FIG. 7: step S75) associated therewith.

  As described above, when the connection information creation unit of this embodiment is used, complicated flow control as shown in the figure can be easily processed. Accordingly, a new processing flow can be generated by simply combining titles extracted based on complicated conditions shown in the flow control (FIG. 7) in the present embodiment, and a new extraction process flow can be obtained.

  FIGS. 10-1 to 10-3B are diagrams for supplementarily explaining the detailed logic processing (FIG. 9) of the connection information creation steps S75 and 713 in the flow generation according to the present embodiment. The details of the logic for creating connection information will be described with reference to the figure.

  As shown in FIG. 10-1 (connection information storage), the connection information of the target process is extracted in the START process and the END process in addition to the information of the flow holding unit on the main storage device 23 as in step S84. It is stored in a data table with a target flag. The titles extracted at this time are A, C, D, F, and G. The data table may be in the external storage device 25.

  As shown in FIG. 10-2 (title extraction target, non-target identification addition), for records having the extracted titles A, C, D, F, and G as the START title and END title of the flow holding unit. , Each with an identification flag. At this time, a flag having a START title of -1 representing the head of the flow is unconditionally given a flag as an extraction target.

  Next, as shown in FIG. 10-3A (connection edit creation), the connection information creation unit shown in FIG. 8 processes the new connection information of AC, AD, AF, and AG. Each flow information is given. Next, in step S813 in FIG. 8, a flag 2 is assigned to a flow having the same START / END as a deletion target to eliminate duplication of the flow. Next, in steps S814 and 815 in FIG. 8, a flag 2 is assigned as a deletion target for a flow having the same START title and eventually reaching the same END title, and FIG. 10-3B (duplicate connection line deletion) The inconsistent connection line as shown in is selected for deletion. Next, in step S816 in FIG. 8, among the records in the flow holding unit, records other than the record whose START / END flags are both 1 are deleted, excess flow information is deleted, and connection information is created.

  FIG. 11 is a flowchart showing a detailed logic process for generating an extraction process according to the present embodiment, that is, a flow generation in which a process flow is modified.

  Referring to this figure, the extraction process generation and control method according to the present embodiment includes a specified process information acquisition step S110 for acquiring information of a specified process at the time of activation, and extraction conditions for titles constituting the specified process acquired in step S110. Title extraction condition display step S111 to be displayed, title extraction condition input step S112 for selecting an extraction condition from the title extraction conditions displayed in step S111, and a title that matches the input extraction condition from the title holding unit Extraction step S113, connection information creation step S114 for regenerating connection information based on the extracted title information, flow generation step S115 for generating a flow from the connection information generated in step S114, and holding in the flow holding unit Charted flow Having a flow display step S116, and the flow decision step S117 where the generated flow to determine whether it is appropriate to.

  Further, when an appropriate process is generated in step S117, a new extraction process generation step S118 for storing the process as a new extraction process in the extraction process holding unit of the database 33, and a title (extraction extracted in the new extraction process). Title holding unit generation step S119 and flow holding unit generation step S1110 for storing the generated title) in the title holding unit and the flow holding unit, an extraction process creation information input step S1111 for inputting creation information of a new extraction process, and a new An extraction process input step S1112 for displaying a screen (described later) for inputting the name of the extraction process and the like, and an extraction process update information input step S1113 for inputting update information of the extraction process based on the information input in step S1112.

  FIGS. 12-1 to 12-7 are diagrams illustrating the detailed logic of the extraction process generation in the present embodiment. The logic details of the extraction process generation method will be described with reference to the drawing.

  As shown in FIG. 12-1 (Title extraction condition input), an extraction condition for a newly created extraction process is input to a process that is an extraction source. In this case, it is assumed that the condition XX and the condition XZ are designated. As shown in FIG. 12-2 (after title extraction), title A and title C, title F, and title G that match the input extraction conditions are extracted.

  Flow information to be connected is created in the connection information creation step S114 of FIG. 11, and this is visualized by the flow generation step S115 and the flow display step S116 of FIG. 11 as shown in FIG. 12-3 (extraction process flow display). Display as.

  Next, it is determined whether or not the extraction process flow displayed in the flow determination step S117 is valid. If it is not valid, the process returns to FIG. 12-1 (title extraction condition input) again to correct the extraction conditions, and the same processing is performed. Is repeated to display the extraction process flow after the extraction condition is changed as shown in FIG. 12-4 (extraction condition change, extraction process flow redisplay).

  Next, it is determined again whether the flow of the extraction process generated in the flow determination step S117 is valid. If it is valid, the generation of the flow of the extraction process is finished. A new storage unit is generated in the extraction process holding means on the database 33 for the generated extraction process (FIG. 12-5). Similarly, extracted titles for the generated extraction process are stored in the title holding unit 36 and the flow holding unit 37 (FIG. 12-6). At this time, the creation and update information of the extracted title is an initial value (date information at the time of extraction in this example). The extraction process creation information is input as the same information as the extraction title creation information. Thereafter, an input screen for the extraction process (FIG. 13 to be described later) is displayed, and the extraction process update information (date information in this example) of the extraction process holding unit is updated by this input information (FIG. 11: Step S1113).

  FIG. 13 is a diagram illustrating an example of a display screen used for inputting contents related to the extraction process according to the present embodiment. This display screen is displayed on the display device 21 of FIG.

  In FIG. 13, reference numeral 131 denotes a process name, 132 denotes a classification name as a process category, and 133 denotes access right information for setting process editing authority. Reference numerals 134 and 135 respectively denote process creation information and update information. In this embodiment, these items are input by the system. Therefore, the process creation information 134 and the update information 135 are items that are displayed on the display device 21 but cannot be input by the input device 22.

  FIG. 14 is a flowchart showing a detailed logic process common to the flow generation step in this embodiment, that is, the flow generation step S77 at the time of process generation, the test flow generation step S714, and the flow generation step S115 at the time of extraction process generation.

  Referring to this figure, the flow generation step in the present embodiment is extracted as step S141 for obtaining information on the designated process, and step S142 for extracting the first flow having a START title value of −1 from the flow holding unit. Step S143 for stacking the END titles of the flow, Step S144 for extracting the flow having the titles stacked in Step S143 as the START title, and the X and Y values of the END titles of the extracted flows as X = (START Title X + 1), Y = (START title Y) Step S145, and if the extracted flow END title has already been placed, the X coordinate of the title calculated in step S145 and the placement The X coordinate of the title is compared, and the X coordinate of the placed title is calculated in step S145. If it is smaller than the X coordinate of the title, step S146 in which the X coordinate of the already placed title is set as the X coordinate in step S145, and another title has already been placed in the X coordinate and Y coordinate of the title calculated in step S145. In this case, step S147 in which the Y coordinate of other titles and all titles in the system is set to +1, step S148 in which the END titles in step S145 are stacked and arranged, and the title in step S148 as the START title Step S149 for determining the presence / absence, Step S1410 for determining the presence / absence of an unprocessed flow with the already arranged title as the START title, and the number of already arranged flows with the same START title as the flow extracted in Step S1410 Step S1411 stacking as In step S1412 in which the X and Y values of the END title of the flow extracted in step S1410 are X = (START title X + 1) and Y = (START title Y + L), respectively, and the START title has a value of −1. It has step S1413 which judges the presence or absence of a processing flow, and step S1414 which calculates the X and Y displacement amount based on the total number of titles.

  15-1 to 15-8 are schematic diagrams illustrating the flow display unit. The detailed logic processing of the flow display unit will be described with reference to the drawing.

  As shown in FIG. 15-1 (extraction of the head title), the head flow whose START title is -1 is extracted from the connection information in the flow holding unit 32, and the X coordinate and Y coordinate of the title A are respectively (1). , 1).

  Next, as shown in FIG. 15-2 (extraction and arrangement of records with the first title as the START title), the flow AB having the END title of the first flow as the START title is extracted.

  In step S145 of FIG. 14 (flow generation method flow logic details), the X displacement amount of title B is calculated as +1 and the Y displacement amount is calculated as 0. As a result, the X coordinate and Y coordinate of the title B are set to (2, 1), respectively. Since this title B does not overlap with other titles, it is stacked in step S148 in FIG.

  Next, in step S149 in FIG. 14, the flow BC having the title B as the START title is extracted. Therefore, in step S145, the X coordinate and Y coordinate of the title C are set to (3, 1), respectively.

  Thereafter, by repeating the same processing, as shown in FIG. 15-3 (repeating the above processing), the direct titles C, G, and H of the title B are arranged. Since there is no flow with the title H as the START title, it is determined in step S1410 in FIG. 14 whether or not there is a flow having the already placed titles (A, B, C, G) in the START title, and the processing starts from the top. Is done. Specifically, the flow A-E having the title A as START is extracted, and the number of arranged flows having A as the START title is stacked as L in step S1411. In this case, the arranged flow with A as the START title is only AB, and L is 1.

  In step S1412, the coordinates of the END title E in the flow A-E are calculated as (2, 2), and since the title E is not arranged, it is arranged in the coordinates in step S148. Next, an unprocessed flow EF with the title E as the START title is extracted in step S149, and the title F is arranged in (3, 2) in steps S145 and S148.

  Similarly, the unprocessed flow F-H having the title F as the START title is extracted in step S149, and the title H is calculated as (4, 2) in step S145. However, since the title H has already been arranged as (5, 1), the title F is connected to the title F in the arranged position from the comparison of X = 4 in step S145 and X = 5 by the arranged coordinates.

  In step S1410, the flow BD having the title B as the START title is extracted. The title D is calculated as coordinates (3, 2) from step S1411 by the existing arrangement flow B-C. However, since the title F is already arranged at the coordinates (3, 2), the Y coordinate of all the titles (titles E and F in this embodiment) of the system to which the title F belongs is incremented by “1” in step S147. To do. By this processing, duplication is avoided and title D is arranged in step S148.

  Subsequently, a flow DG with the title D as the START title is extracted in step S149, but since the title G has already been arranged, the X coordinate 4 of the title G and the X coordinate of the arranged title G in step S145 From the comparison of 4, the title G is connected to the title D with the arranged position.

  A determination is made as to whether an unprocessed flow having a START title value of -1 remains (step S1413 in FIG. 14), and if it remains, the processing from step S143 in FIG. 14 is repeated again.

  On the other hand, after extracting all the flows to be processed from the title flow holding unit shown in FIGS. 15-1 to 15-8, in step S 1414 of FIG. Based on the X and Y coordinate values and the display screen size of the display device 21, the arrangement position of each title is optimized. In this optimization process, not only correction of the arrangement position but also enlargement / reduction of the character size and the rectangle surrounding the character are performed.

  FIG. 16 is a diagram for explaining the processing flow of the extraction process when the title of the extraction process is updated.

  The process flow of the extraction process includes a step S160 of acquiring a designated extraction process, and a flow display step of displaying the process acquired in step S160 on the display device by the logic of the display unit described in FIGS. 15-1 to 15-8. In step S161, an executable title display step S162 for displaying a title executable in the extraction process as a target title, a step S163 for updating the executable title, and update information of the extraction process are input based on the update information in step S163. Step S164, step S165 for extracting a flow with the updated title as the START title, step S166 for determining the presence or absence of the extraction flow, and if there is an extracted flow, the status flag of the extraction flow is changed from “0” to “ Step S167 to change to “1” and extraction Step S168 for stacking the END title of the flow, step S169 for determining whether or not the status flags of all the flows having the stacked END title as the END title are “1”, and the status flags of all the flows by step S169. If it is “1”, the process includes step S1610 in which the title stacked in step S168 is set as an executable title, and step S1611 for determining whether there is an executable title in the extraction process.

  17-1 to 17-9 are diagrams for explaining in detail the processing flow of the extraction process described in FIG. The processing flow of the extraction process will be described with reference to the drawing.

  As shown in FIG. 17-1 (acquisition of designated extraction process), holding information and designation regarding the designated extraction process from the process holding unit 35, title holding unit 36 and flow holding unit 37 of the database 33 in step S160 of FIG. The title holding information and flow information included in the extraction process are stored in the main storage device 23. For the flow information, the flag is changed from “0” to “1” by updating the START title, and a data area for recording the flow status is added.

  In step S161 in FIG. 16, the flow of the extraction process shown in FIG. 17-2 (extraction process flow display) is displayed on the display device. At this time, the title A is displayed as an executable title so that it can be easily identified. In this embodiment, a method of displaying the outline of the outer frame of the title thickly is used as an example. Not only is it possible to change the appearance such as line thickness from other titles, but the entire flow can also be moved so that the selected title is placed at a specific position on the display screen, such as the center or right center. Good. An executable title means a title that can be executed logically / physically by processing (updating) a preceding title in the flow. Therefore, the title A whose START title is −1 (there is no preceding title) in the title flow holding unit is an executable title in the extraction process according to the present embodiment. When the title A is selected, a title name 171, title contents 172, knowledge data 173 and a button 174 for updating the title A that are input to the retained information of the title A are displayed. Also, the creation information 175 and update information 176 of the title A hold information displayed when the extraction process is generated and are displayed. The knowledge file 177 related to the title A is extracted from the knowledge database 34 and displayed by executing relation information (hyperlink in this example) displayed as the knowledge data 173. On the executable title display screen, the title cannot be corrected other than executing the hyperlink input as the knowledge data and displaying the knowledge file. When the title A and the knowledge file are referred to and the title A is completed (updated), the update button 174 is pressed.

  A process associated with the update of the title A as shown in FIG. 17-4 (a process associated with the update of the executable title) will be described.

  When the title A is updated, update information of the title A (date information: 2004/2/10 in the present embodiment) is input by the system (FIG. 16: step S163). With this information, the update information of the extraction process including title A is updated with the same information (2004/2/10) (FIG. 16: step S164). Also, the flow AB with the title A as the START title is extracted in steps S165 and 166 in FIG. 16, the status flag is changed to “1” in step S167, and the title B is stacked (step S168). Since all the status flags of the flow (only AB in this embodiment) with the title B as the END title in step S169 are “1”, the title B is set as an executable title in step S1610.

  Similarly, flows A-C and A-E are extracted in step S165, and titles C and E become executable titles. Since there are three flows as described above in which the title A is the START title in step S166, the presence or absence of an executable title is determined in step S1611 after these processes are completed, and the previous titles B, C, and E are executed. It is displayed on the display device as a possible title in step S162 (FIG. 17-5 Display of extraction process associated with update of executable title).

  Next, the case where the title C is updated among the executable titles will be exemplified.

  As shown in FIG. 17-6 (Process 2 associated with update of executable title), the update information of Title C is input and the update information of the extraction process is changed, which is the same as the update process of Title A described above. is there. Further, the flow CF having the title C as the START title is extracted in steps S165 and 166, the status flag is changed to “1” in step S167, and the title F is stacked (step S168). Next, it is determined whether or not the status flags of all flows having the title F stacked in step S169 as the END title are “1”, but the status flag of the flow E-F is “0” because the title E has not been updated. It is. Therefore, the process returns to step S165, and the process of extracting the flow with the title C as the START title is performed again, but there is no extractable flow in the flow holding information. Therefore, the presence / absence of a currently executable title (in this case, titles B and E) is determined in step S1611 and displayed (FIG. 17-7 Extraction process display 2 associated with update of executable title).

  When the processing described above is repeated and the final title in the extraction process flow is updated (FIG. 17-8 END processing 1), the final update information of the extraction process is input as shown in FIG. 17-9 (END processing 2). The Although not shown in the present embodiment, the extraction process holding information and the extraction process holding unit in the database 33 record whether the extraction process status flag is present and all the titles in the extraction process have been updated. May be.

  FIG. 18 is a diagram for explaining process duplication processing, which is one of the features of this embodiment.

  In the process duplication processing, step S180 for specifying and acquiring a process to be duplicated from the process holding unit 30 held in the database 33, and an area for storing the holding information of the new process by duplication in the process holding unit 30 are created. A new process generation step S181 to be performed, a creation information input step S182 for inputting creation information of a new process to be created by duplication, and an area for storing the title of the new process created in step S182. In order to input the title holding unit generation step S183, the flow holding unit creation step S184, and the name / classification of the new process created by duplication, a process input screen (FIG. 4) is displayed on the display device. Display process input step S185 Step S186 for copying the process holding information of the copy source acquired in Step S180 to the holding area created in Step S181; Steps S187 and 188 for initializing creation information and update information of a new process in the process of copying; Similarly, step S189 that duplicates the title holding information of the copy source to the title holding unit of the new process, steps S1810 and 1811 that initialize the creation information and update information of the new title in the process, and the flow holding unit of the copy source It has step S1812 which duplicates to the flow holding part of a new process, and update information input step S1813 which inputs the update information of a new process.

  FIG. 19 is a diagram for explaining title duplication processing in the present embodiment.

  The title duplication process is a process of duplicating a desired title in the same process in the process of creating a process flow. In this process, step S190 for designating and acquiring a title to be copied, a new title generating step S191 for creating an area for storing new title holding information by copying, and a title holding information for copying by step S190 are used. Step S192 for duplicating as new title holding information created in step S191, step S193 for initializing the creation and update information of the duplicated title, and duplication flow generation for duplicating the flow with the duplication source title as the END title Step S194 includes a flow holding step S195 for holding the flow information duplicated in Step S194, and a flow display step S196 for displaying the flow after the duplication processing on the display device.

  20-1 to 20-3 illustrate the title duplication process shown in FIG.

  As shown in FIG. 20-1 (selected title selection), the selected title (title C) is displayed so that it can be easily identified when the specified title is acquired in step S190 of FIG. In this embodiment, a method of displaying the outline of the outer frame of the title thickly is used as an example.

  As shown in FIG. 20-2 (duplication processing of title information), a storage area for new title holding information and flow information is generated in step S191, and in step S192, the title holding information of the source title (title C) is Stored as new title holding information. At this time, the name of the new title is uniquely input by the system with respect to the title name of the duplication source (in this embodiment, the duplication source name_Copy).

  In step S193, the creation and update information of the duplicated title (title C_Copy) is changed from the original value to the initial value (in this embodiment, the processing date / time information of the duplication process). In the duplicate flow generation unit in step S194, all the flows having the duplication source title as the END title (in this case, the flow A-C) are duplicated as a new title flow to the flow holding unit (A-C_Copy).

  In step S195, after storing the flow holding unit in step S194 on the database or the main storage device, a new title by duplication is displayed in the flow display in step S195 (FIG. 20-3: flow duplication processing). In this embodiment, in the generation of the duplicate flow in step S194, the example of duplicating the flow having the duplication source title as the END title has been described. However, the flow having the duplication source title as the START title (flow CF) is duplicated. Alternatively, all the flows including the duplication source title may be duplicated.

  As described above, according to the first embodiment, when the names of all titles in the series of process flows and the title name immediately before the title are input, the context of each title is automatically analyzed, A process generation system that determines and displays the placement position and connection line of each title in order from the part where the context was found, and extracts the titles included in the process according to the extraction conditions, and generates a flow with only the extracted titles It is a process support system equipped with a process generation system, which holds information related to knowledge data related to each title as holding information for each title, and can display and reference the knowledge data as necessary It was. In addition, creation information, update information, classification information, and access rights are added as process and extraction process holding information, and new information of each process can be updated by updating the titles included. Furthermore, an existing process can be selected and duplicated, or a desired title in the process can be duplicated.

  Therefore, the following effects are mentioned as the effects of the first embodiment.

  By adding associating information with knowledge data related to the title as the holding information of each title, it is possible to save time and effort to search and extract a desired knowledge in the knowledge database, and by using a communication device (network) It is possible to maintain a relationship with knowledge data on a plurality of connected knowledge databases. Also, by retaining only the association information, even if the knowledge file is edited / updated on each knowledge database, the latest knowledge file can be extracted from the title as long as the relationship information from the title does not change. Is possible. Therefore, the work and time required for the maintenance and update of the knowledge file can be reduced.

  By adding the name / classification / creation / update information and access rights as holding information of the process including the title and the extraction process, the user can easily select the desired process and the extraction process from the database. In addition, the access right can prevent inadvertent changes to the process and the title included in the process.

  When creating a new process similar to an existing process, using the process duplication processing according to this embodiment, after duplicating the existing process, only the title and title context (flow) different from the existing process can be corrected. A new process can be created, and the time required for creation can be shortened.

  Similarly, when a title similar to an existing title is newly created during creation of the process flow, the time required for creating the title can be shortened by using the title duplication processing according to the present embodiment.

(Second Embodiment)
In the first embodiment, the relationship information with the knowledge file on the knowledge database is input as the title holding information. In the second embodiment, the knowledge file is stored in the desired knowledge database in the process of creating the title. At the same time, information related to the stored knowledge file is automatically input to the title as knowledge data. Further, in the first embodiment, the knowledge file displayed based on the knowledge data (relationship information with the knowledge file) from the title of the extraction process flow is only displayed, but in the second embodiment, It is configured to allow editing updates and additions to the displayed knowledge files.

  FIG. 21 is a diagram showing an example of a title input screen at the time of creating a process in the second embodiment.

  The title input screen shown in FIG. 21 has knowledge data 210 for displaying information related to the knowledge file and an execution button 211 for storing the knowledge file in the knowledge database.

  FIGS. 22-1 to 22-3 are diagrams for explaining processing when saving a knowledge file from the title input screen in FIG.

  As shown in FIG. 22-1 (selected title selection), a title (title D) to which knowledge data is added is selected, and an input screen for title D is displayed (file selection in FIG. 22-2). On the operation screen displayed by pressing the execution button (FIG. 21: 211), the current location of the knowledge file (for example, an external storage device) and a desired knowledge database (for example, database A) for storing the knowledge file are input. At this time, it is assumed that the external storage device and the knowledge database A are connected by a communication device (not shown). When the “execute” button in the figure is pressed, the knowledge file “AAA” is stored in the knowledge database A from the external storage device as shown in FIG. 22-3 (file storage), and the knowledge data of the title D is stored in the storage destination. Information related to the knowledge file “AAA” is automatically input by the system.

  FIG. 23A to FIG. 23D are diagrams illustrating processing for editing and updating and adding a knowledge file from the extraction process.

  For the process shown in FIG. 23-1 (process flow), an extraction process A that holds titles A, C, D, and E is generated by inputting extraction conditions (not shown). The executable title is updated in the same way as the processing flow (FIG. 16) of the extraction process described in the first embodiment, and the title D is executed as shown in FIG. 23-2 (extraction process flow A (knowledge file update)). When the possible title is reached, the title execution screen 231 in this embodiment is displayed. By executing the knowledge data (hyperlink in this embodiment) on the execution screen 231, the knowledge file 232 associated at the time of creating the process is displayed.

  The knowledge file display screen in this embodiment includes an update button 233 for editing and updating the displayed knowledge file. By depressing the update button 233, the history number 234 of the knowledge file is incremented. In this case, since there is no change in the relationship information between the title and the updated knowledge file, the title update information is not changed.

  Further, as shown in FIG. 23-3 (extraction process flow A (knowledge file addition)), a new knowledge file can be stored in the knowledge database from the executable title display screen in the present embodiment. The execution button shown as 235 in the figure inputs the current location of the knowledge file and the desired knowledge database on the operation screen 237 in the same manner as the knowledge file storage processing (FIGS. 22-1 to 22-3) described above. As a result, the knowledge file is stored in the knowledge database, and the relation information between the stored knowledge file and the title D is automatically input to the additional data column 236 of the title D by the system.

  FIG. 23-4 (extraction process flow B) shows a state in which the extraction process B is generated using the extraction conditions (not shown) from the process shown in FIG. 23-1 process flow again after the above processing. ing. On the execution screen of title D, the knowledge data added in FIG. 23-3 is displayed, and the history number 234 of the knowledge file updated in FIG. 23-2 is incremented and displayed.

  As described above, according to the second embodiment, in the process of creating a process, the knowledge file is stored in the desired knowledge database from the title input screen, and the same is possible from the executable title execution screen of the extraction process. The knowledge file can be stored in a desired knowledge database, and the knowledge file in the knowledge database can be edited and updated from the executable title execution screen of the extraction process, and the history information of the knowledge file can be updated. did.

  Therefore, the following effects are mentioned as the effects of the second embodiment.

  In the process of creating the process, the knowledge file required for the title is searched from the knowledge database, and the knowledge file is stored in the knowledge database for the first embodiment in which the location is input as the knowledge data on the title holding unit. However, since the system automatically inputs the location of the knowledge file, the time required for title creation can be shortened.

  Since the existing knowledge file can be edited and updated from the title of the extraction process, the knowledge file can be kept up-to-date. That is, a user who performs work or work according to the extraction process can complete the work / work while referring to the latest knowledge file.

  Since the knowledge file to be added to the title from the title of the extraction process can be stored in the knowledge database and the knowledge data can be added to the title of the extraction source, for example, multiple users can extract multiple extraction processes extracted from the same process By executing, each result can be added to the title. Accordingly, a user who newly executes an extraction process extracted from the process can perform work / business while referring to various past cases as a knowledge file, and can prevent errors and oversights.

(Third embodiment)
In the third embodiment, termination information can be added to a title in the process creation process.

  FIG. 24 is a diagram showing a title input screen in the third embodiment.

  Whether the title is a terminal title can be determined by turning on / off the check box 241 shown in FIG. As described in detail in FIGS. 25A to 25C, the terminal title is a title provided so that the extraction process can be completed without executing the final title.

  The processing flow of the extraction process including the terminal title will be described in detail with reference to FIGS. 25-1 to 25-3 (processing flow of the extraction process including the terminal title).

  In order to distinguish a title having termination information from FIG. 24 from other titles, an area for storing termination information is provided in the title holding information on the main storage device 23. Remember that is a terminal title. The terminal type title E becomes an executable title, and when this is updated, a selection screen shown in FIG. 25-2 (extraction process end confirmation screen) is displayed on the display device. At this time, when “Yes” is selected and the extraction process is completed when the title E is updated, the update information of the subsequent title of the title E has the update information of the title E as shown in FIG. 25-3 (completion of the extraction process). At the same time, the update information of the extraction process is also input as the update information of the title E, and the extraction process is completed.

  As described above, according to the third embodiment, the extraction process is performed by updating the title in the extraction process by providing the terminal title with the terminal information added to the title holding information when the process is created. Can be completed on the way.

  Therefore, the following effects are mentioned as the effects of the third embodiment.

  When a user who performs work / work according to the extraction process finishes the extraction process halfway, it is unclear which work (title) should be completed and finished. For example, if the work / work according to the extraction process is terminated in the middle without being aware of the milestone (separation) of the work / work, the result / progress of the work / work by the user becomes unclear, and the subsequent work / work Cannot be taken over by anyone other than the user. Therefore, by arranging the terminal type titles in advance in the series of work / work, it is possible to prevent the extraction process from being completed on the way other than the terminal type titles, and the series of work / work is not delayed.

(Fourth embodiment)
In the fourth embodiment, in the process of generating an extraction process from a process, it is possible to set whether or not to display an executable title on the extraction process flow so as to be distinguishable from other titles.

  FIG. 26 is a diagram showing extraction process generation processing in the fourth embodiment.

  Although it is substantially equivalent to the extraction process generation process in the first embodiment (FIG. 11), the process in the fourth embodiment is a step S261 for determining whether or not to specify an executable title in the generated extraction process flow. If it is specified, an executable title display is recorded in the extraction process holding information in step S262. If not specified, the executable title non-display is recorded in the same manner in step S263.

  FIG. 28 is a diagram illustrating an example of an extraction process holding unit on the database 33 according to the fourth embodiment.

  By recording “1” and “0” in the executable title display area, the display / non-display setting of the executable title is recorded. FIG. 27 is an input screen serving as an extraction process input unit 260 for performing display / non-display setting of executable titles in the present embodiment when generating an extraction process. By setting the setting check box 271 to ON or OFF, such setting is performed. Do.

  The effects of the fourth embodiment include the following effects.

By not allowing an executable title to be specified and enabling all titles on the extraction process to be updated, the processing time required for the extraction process (FIG. 16) exemplified in the first embodiment is shortened. For example, if the number of titles included in the extraction process flow is small, there are few branches in the extraction process flow, and the listability is good, the work / work is performed according to the extraction process flow even if the executable title is not specified by the system. can do. In this case, the work / work time can be further shortened by omitting the system processing time required to clearly indicate the executable title. As described above, the present invention is not limited to the above-described embodiment, and will be described. Needless to say, the screen content is not limited to this. The present invention can be appropriately modified and combined within the scope of the gist of the present invention.

  Another object of the present invention is to supply a storage medium (or recording medium) on which a program code of software that realizes the functions of the above-described embodiments is recorded to a system or apparatus, and to perform computer (or CPU or MPU) of the system or apparatus. Needless to say, this is also achieved by reading and executing the program code stored in the storage medium.

  In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the storage medium storing the program code constitutes the present invention. Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an operating system (OS) running on the computer based on the instruction of the program code. It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the actual processing and the processing is included.

  Further, after the program code read from the storage medium is written in a memory provided in a function expansion card inserted into the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. It goes without saying that the CPU or the like provided in the card or the function expansion unit performs part or all of the actual processing, and the functions of the above-described embodiments are realized by the processing. When the present invention is applied to the storage medium, the storage medium stores program codes corresponding to the flowcharts described above.

As described above, the process generation support systems of the first to fourth embodiments have the following effects.
(1) The creation of a flow according to the above-described embodiment is performed by means for repeatedly performing a process of inputting a title, inputting a context relationship between titles, and rearranging the title arrangement according to the context information. In other words, the minimum information necessary for creating a flow is the title and the information before and after the title. When this information is input to the system, the title is arranged by the means according to the above embodiment, and the process is created by repeating this. Is done. The created process is also changed in the same manner. On the other hand, the title holds only the relationship information with the related knowledge data. In other words, the knowledge data held in the desired database can be maintained and updated independently of this process generation support system, and this process generation support system relates the latest and updated knowledge data to the title. It can be displayed based on information. As a result, according to the above-described embodiment, it is possible to reduce the work and time required to create and change a flow and to maintain and update knowledge data.
(2) By providing classification information, creation and update information for various processes in the database, the target process can be easily accessed, and the process and the process are comprehensively included by the access rights provided for the process. It is possible to prevent inadvertent changes to the titles made.
(3) When creating a process, the process can be performed more easily by duplicating and changing a similar process existing in the database. Further, by initializing the creation / update information of the duplicated process, the duplicated process can be handled as a newly created process.

It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure explaining the outline of a process generation process. It is a figure which shows schematic structure of embodiment of the information processing system of this invention. It is a system block diagram which shows schematic structure of embodiment of the information processing system of this invention. It is a figure which shows the example of UI (user interface) screen as a process input part. It is a flowchart which shows the outline | summary of a process production | generation process. It is a figure which shows the example of UI screen as a title input part. It is a flowchart which shows the outline | summary of a process flow production | generation process. It is a flowchart which shows the detail of a connection information creation process. It is a figure for illustrating the logic of connection information creation processing. It is a figure for illustrating the logic of connection information creation processing. It is a figure for illustrating the logic of connection information creation processing. It is a figure for illustrating the logic of connection information creation processing. It is a figure for showing the specific example of a connection information creation process, and supplementarily explaining the logic of a process. It is a figure for showing the specific example of a connection information creation process, and supplementarily explaining the logic of a process. It is a figure for showing the specific example of a connection information creation process, and supplementarily explaining the logic of a process. It is a figure for showing the specific example of a connection information creation process, and supplementarily explaining the logic of a process. It is a flowchart which shows the outline | summary of an extraction process production | generation process. It is a figure for showing supplementary explanation and showing an example of extraction process generation processing logic. It is a figure for showing supplementary explanation and showing an example of extraction process generation processing logic. It is a figure for showing supplementary explanation and showing an example of extraction process generation processing logic. It is a figure for showing supplementary explanation and showing an example of extraction process generation processing logic. It is a figure for showing supplementary explanation and showing an example of extraction process generation processing logic. It is a figure for showing supplementary explanation and showing an example of extraction process generation processing logic. It is a figure for showing supplementary explanation and showing an example of extraction process generation processing logic. It is a figure which shows the example of UI screen as an extraction process input part. It is a flowchart which shows the arrangement | positioning process of a title. It is a figure for demonstrating the specific example of the arrangement | positioning process of a title. It is a figure for demonstrating the specific example of the arrangement | positioning process of a title. It is a figure for demonstrating the specific example of the arrangement | positioning process of a title. It is a figure for demonstrating the specific example of the arrangement | positioning process of a title. It is a figure for demonstrating the specific example of the arrangement | positioning process of a title. It is a figure for demonstrating the specific example of the arrangement | positioning process of a title. It is a figure for demonstrating the specific example of the arrangement | positioning process of a title. It is a figure for demonstrating the specific example of the arrangement | positioning process of a title. It is a flowchart which shows the process of the extraction process accompanying a title update process. It is a figure explaining the specific example of an extraction process process accompanying a title update process. It is a figure explaining the specific example of an extraction process process accompanying a title update process. It is a figure explaining the specific example of an extraction process process accompanying a title update process. It is a figure explaining the specific example of an extraction process process accompanying a title update process. It is a figure explaining the specific example of an extraction process process accompanying a title update process. It is a figure explaining the specific example of an extraction process process accompanying a title update process. It is a figure explaining the specific example of an extraction process process accompanying a title update process. It is a figure explaining the specific example of an extraction process process accompanying a title update process. It is a figure explaining the specific example of an extraction process process accompanying a title update process. It is a flowchart explaining the duplication process of the process in 1st Embodiment. 6 is a flowchart illustrating title duplication processing according to the first embodiment. It is a figure explaining the specific example of the title duplication process in 1st Embodiment. It is a figure explaining the specific example of the title duplication process in 1st Embodiment. It is a figure explaining the specific example of the title duplication process in 1st Embodiment. It is a figure which shows the example of UI screen as a title input part in 2nd Embodiment. It is a figure which shows the specific example of the knowledge file preservation | save process from the process in 2nd Embodiment. It is a figure which shows the specific example of the knowledge file preservation | save process from the process in 2nd Embodiment. It is a figure which shows the specific example of the knowledge file preservation | save process from the process in 2nd Embodiment. It is a figure which shows the specific example of the knowledge file preservation | save process from the extraction process in 2nd Embodiment. It is a figure which shows the specific example of the knowledge file preservation | save process from the extraction process in 2nd Embodiment. It is a figure which shows the specific example of the knowledge file preservation | save process from the extraction process in 2nd Embodiment. It is a figure which shows the specific example of the knowledge file preservation | save process from the extraction process in 2nd Embodiment. It is a figure which shows the example of UI screen as a title input part in 3rd Embodiment. It is a figure explaining the specific example of the process of the extraction process in 3rd Embodiment. It is a figure explaining the specific example of the process of the extraction process in 3rd Embodiment. It is a figure explaining the specific example of the process of the extraction process in 3rd Embodiment. It is a flowchart which shows the outline | summary of the extraction process production | generation process in 4th Embodiment. It is a figure which shows the example of UI screen as an extraction process input part in 4th Embodiment. It is a figure which shows the specific example of the extraction process holding | maintenance means in 4th Embodiment. It is a system block diagram which shows schematic structure of the conventional information processing system. It is a figure which shows the outline | summary of the conventional process flow production | generation process.

Explanation of symbols

DESCRIPTION OF SYMBOLS 21 Display apparatus 22 Input apparatus 23 Main memory 24 Central processing unit 25 External storage 30 Process holding part 31 Title holding part 32 Flow holding part 35 Extraction process holding part 36 Extraction process title holding part 37 Extraction process flow holding part 34 Knowledge database

Claims (10)

A decision means for deciding the context of the title which is a process name existing in the database;
Arranging means for rearranging the titles according to the context determined by the determining means and arranging them on the display screen;
Extraction means for extracting titles according to the input conditions to the database;
Rearrangement means for rearranging the title extracted by the extraction means on the display screen according to the context;
An association means for selecting a title and associating the selected title with knowledge data existing on the knowledge database;
Display means for displaying knowledge data on the display screen in accordance with associated information;
A process generation support system comprising:   2. The process generation support system according to claim 1, further comprising storage means for newly storing knowledge data on a knowledge database while associating with the selected title.   Update storage means for updating and storing the displayed knowledge data in the knowledge database according to the information related to the selected title, and storage means for storing history information of the knowledge data held in the knowledge database. The process generation support system according to claim 1, wherein:   Generation means for generating a process that includes the arranged title and an extraction process that includes the extracted and rearranged title, access right determining means for determining access rights to the process and the extraction process, and title creation information And setting means for setting update information, generation means for generating creation and update information of processes and extraction processes that include corresponding titles based on the title creation information and update information, and classification of processes and extraction processes 2. The process generation support system according to claim 1, further comprising classification information setting means for setting information.   Duplicating means for duplicating the title and process, first initial information setting means for setting the access right and creation information of the duplicated process as predetermined initial information, and updated information of the duplicated title and process as predetermined initial information A second initial information setting means for information; and a relation information generating means for generating relation information between the duplicated title and knowledge data based on connection information between the duplication source title and knowledge data. The process generation support system according to claim 1.   End information generating means for generating a title having end information of the process, and end information determining means for determining end information of the extraction process including the title when the title having end information included in the extraction process is updated. The process generation support system according to claim 4, further comprising:   In order to clearly indicate the title of interest included in the extraction process, the image processing apparatus further includes a determination unit that determines the title of interest, and an output unit that displays the determined title of interest on the display screen in a manner that distinguishes the determined title of interest from the non-target title. The process generation support system according to claim 4, wherein the output unit is stopped in accordance with process output information. A determination step for determining the context of the title, which is a process name existing on the database;
An arrangement step of arranging the titles on the display screen by rearranging the titles according to the context determined in the determination step;
An extraction process for extracting titles according to the input conditions to the database;
A rearrangement step of rearranging only the title extracted in the extraction step on the display screen according to the context;
An association step of selecting a title and associating the selected title with knowledge data existing in the knowledge database;
A display step of displaying knowledge data on the display screen according to the associated information;
A process generation support method comprising:   A program causing a computer to execute the process generation support method according to claim 8.   A storage medium storing the program according to claim 9 in a computer-readable manner.

Images