JP4907322B2 - Workflow generation apparatus, workflow generation method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a work flow preparation device which supports that a plurality of operators prepare cooperatively one work flow prepare. <P>SOLUTION: A flow preparation part 120 inputs outline tasks configuring an overall operation flow showing the flow of a whole operation based on the operation of an operator 811, and assigns executers to those input outline tasks. An operator having authority to detail the outline tasks based on the executers assigned to the outline tasks is determined, and a task preparation part 130 inputs detailed tasks acquired by detailing the outline tasks based on the operations of an operator 812 and an operator 813 having change authorities. <P>COPYRIGHT: (C)2008,JPO&amp;INPIT

Description

  The present invention relates to a workflow generation apparatus that supports creation of a workflow that models and manages a work flow.

2. Description of the Related Art Conventionally, work progress is managed using a workflow that models a work flow. In order to perform such business management, it is necessary to create a workflow in advance, and there is a workflow generation device that supports creation of a workflow.
JP-A-7-93395 JP-A-8-16639 JP-A-8-255075 Japanese Patent Laid-Open No. 10-11280 JP 2001-31527 A JP 2002-49883 A JP 2002-366589 A JP 2003-6234 A Japanese Patent Laid-Open No. 9-259157 Japanese Patent Laid-Open No. 2003-6250 Japanese Patent Laid-Open No. 2003-6251

Business management by workflow is effective, especially in a huge project, by specifying the role of each work and the information to be exchanged, and by sharing the specifications among the performers who perform the work, the work efficiency becomes high and effective. is there.
The conventional workflow generation apparatus assumes that a workflow creation person creates a workflow alone.
However, the more complex the work that is modeled by the workflow, the larger the workflow, making it difficult to create everything alone.
The person in charge of workflow creation is usually a person in a position that can overlook the flow of the entire work. However, such a person in charge of creating a workflow may not know the details of the work or the actual situation in the field.
As a result, the workflow does not reflect the actual work, and the work management by the workflow may be complicated, for example, in the actual site, a work different from the created workflow is performed. If such a situation is not fed back to the person in charge of workflow creation, the workflow that is different from the actual situation will be used.
Although it is possible for multiple workflow creators to collaborate to create workflows using a conventional workflow generator, if the intentions between the personnel are not unified, it is possible to create a contradictory workflow as a whole There is sex.
The present invention has been made, for example, in order to solve the above-described problems, and the workflow generation apparatus can support the creation of one huge workflow by cooperation of a plurality of workflow creators. The purpose is to.

A workflow generation device according to the present invention includes:
An input device for inputting information, a storage device for storing information, a processing device for processing information, an actor definition database storage unit, a general task input unit, a general task performer input unit, and a general task definition generation unit A task definition database storage unit, a detailed task input unit, a detailed task performer input unit, and a detailed task definition generation unit,
The actor definition database storage unit uses the storage device to store executor definition data that defines an executor that executes a task,
The general task input unit uses the input device to input a general task that constitutes an overall work flow representing the overall work flow,
The general task performer input unit executes the general task input by the general task input unit from the performers defined by the performer definition data stored in the actor definition database storage unit, using the input device. Enter the general task performer selected by the first operator as the performer,
The general task definition generator generates the general task based on the general task input by the general task input unit and the general task performer input by the general task performer input unit using the processing device. Generate summary task definition data to be defined,
The task definition database storage unit stores the general task definition data generated by the general task definition generation unit as task definition data for defining a task using the storage device,
The detailed task input unit uses the input device to input a detailed task in which a second operator has detailed the general task defined by the task definition data stored in the task definition database storage unit,
The detailed task executor input unit uses the input device, and the detailed task input by the detailed task input unit from the executors defined by the executor definition data stored in the actor definition database storage unit. Enter the detailed task executor selected by the second operator as the executor to execute
The detailed task definition generation unit is configured to use the processing device based on the detailed task input by the detailed task input unit and the detailed task performer input by the detailed task performer input unit. , Generate detailed task definition data that defines the above detailed task,
The task definition database storage unit further stores the detailed task definition data generated by the detailed task definition generation unit as task definition data using the storage device.

  According to the workflow generation device of the present invention, the general task created by the first operator and the executor thereof are input by the general task input unit and the general task executor input unit, and the second operator creates the general task. The detailed task input part and the detailed task performer input part input the detailed task to be executed and the executor thereof, and the general task definition generation part and the detailed task definition generation part generate task definition data. As a result, a plurality of operators can create a single workflow as a whole by creating a workflow in the range of their own responsibility.

Embodiment 1 FIG.
The first embodiment will be described with reference to FIGS.

FIG. 1 is a system configuration diagram showing an example of the overall configuration of a workflow generation system 800 in this embodiment.
The workflow generation system 800 is a system in which a plurality of operators 811 to 813 cooperate to generate one workflow.
For example, the operator 811 is in a position of summarizing the whole, and determines the flow of the entire work. The operator 812 is in a position to manage the site, and determines details of work on the site managed by the operator 812. The operator 813 is in a position to manage a site that is different from the operator 812, and determines details of work on the site managed by the operator 813.
In this way, a plurality of operators 811 to 813 determine work within a range that they are in charge of, and generate one workflow.
The workflow generation system 800 is an example of a workflow generation apparatus.

The workflow generation system 800 includes a server device 100 and a plurality of terminal devices 200.
The server device 100 includes an actor definition database storage unit 111, a task definition database storage unit 112, a flow definition database storage unit 113, an interface template database storage unit 114, a flow creation unit 120, a task creation unit 130, and an interface creation unit 140. Details of each block will be described later.
For example, one terminal device 200 is assigned to each of the operators 811 to 813, and the operators 811 to 813 input information or output information to the operators 811 to 813. The terminal device 200 manages who the operator is, for example, by authenticating the operators 811 to 813 with a password. This prevents the operator from performing operations outside his authority.
Based on the generated workflow, the workflow generation system 800 outputs an overall work flow diagram 710, a schematic task flow diagram 720, a detailed task flow diagram 730, a work definition document 740, an interface specification document 750, and the like. The output format may be displayed on, for example, a display device of the terminal device 200 or may be printed by a printer device.

FIG. 2 is a diagram showing an example of the external appearance of the server device 100 and the terminal device 200 in this embodiment.
The server device 100 and the terminal device 200 include a system unit 910, a display device 901 having a CRT (Cathode / Ray / Tube) or LCD (liquid crystal) display screen, a keyboard 902 (Key / Board: K / B), a mouse 903, Hardware resources such as an FDD 904 (Flexible / Disk / Drive), a compact disk device 905 (CDD), a printer device 906, and a scanner device 907 are provided, and these are connected by cables and signal lines.
The system unit 910 is a computer, and is connected to the facsimile machine 932 and the telephone 931 via a cable, and is connected to the Internet 940 via a local area network 942 (LAN) and a gateway 941.

FIG. 3 is a diagram illustrating an example of hardware resources of the server device 100 and the terminal device 200 according to this embodiment.
The server apparatus 100 and the terminal apparatus 200 include a CPU 911 (also referred to as a central processing unit, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, or a processor) that executes a program. The CPU 911 is connected to the ROM 913, the RAM 914, the communication device 915, the display device 901, the keyboard 902, the mouse 903, the FDD 904, the CDD 905, the printer device 906, the scanner device 907, and the magnetic disk device 920 via the bus 912, and the hardware. Control the device. Instead of the magnetic disk device 920, a storage device such as an optical disk device or a memory card read / write device may be used.
The RAM 914 is an example of a volatile memory. The storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of a storage device or a storage unit.
A communication device 915, a keyboard 902, a scanner device 907, an FDD 904, and the like are examples of an input unit and an input device.
Further, the communication device 915, the display device 901, the printer device 906, and the like are examples of an output unit and an output device.

The communication device 915 is connected to a facsimile machine 932, a telephone 931, a LAN 942, and the like. The communication device 915 is not limited to the LAN 942, and may be connected to the Internet 940, a WAN (wide area network) such as ISDN, or the like. When connected to a WAN such as the Internet 940 or ISDN, the gateway 941 is unnecessary.
The magnetic disk device 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924. The programs in the program group 923 are executed by the CPU 911, the operating system 921, and the window system 922.

The program group 923 stores programs that execute functions described as “˜units” in the description of the embodiments described below. The program is read and executed by the CPU 911.
The file group 924 includes information, data, signal values, variable values, and parameters that are described as “determination results of”, “calculation results of”, and “processing results of” in the description of the embodiments described below. Are stored as items of “˜file” and “˜database”. The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, Used for CPU operations such as calculation, calculation, processing, output, printing, and display. Information, data, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during the CPU operations of extraction, search, reference, comparison, operation, calculation, processing, output, printing, and display. Is remembered.
In addition, the arrows in the flowcharts described in the following description of the embodiments mainly indicate input / output of data and signals. The data and signal values are the RAM 914 memory, the FDD 904 flexible disk, the CDD 905 compact disk, and the magnetic field. Recording is performed on a recording medium such as a magnetic disk of the disk device 920, other optical disks, mini disks, and DVDs (Digital / Versatile / Disc). Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.

  In the description of the embodiments described below, what is described as “to part” may be “to circuit”, “to device”, and “to device”, and “to step” and “to”. “Procedure” and “˜Process” may be used. That is, what is described as “˜unit” may be realized by firmware stored in the ROM 913. Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware. Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD. The program is read by the CPU 911 and executed by the CPU 911. That is, the program causes the computer to function as “to part” described below. Alternatively, the procedure or method of “to part” described below is executed by a computer.

  Returning to FIG. 1, the functional blocks of the workflow generation system 800 will be described.

The actor definition database storage unit 111 stores performer definition data using a storage device such as the magnetic disk device 920.
The executor definition data is data that defines an executor that executes a task.
For example, in the case of a company organization, a person who executes a task is a “department” such as a material department or a sales department, a “department” that is a subordinate organization of the “department”, or an “employee” who is a member of the “department”. ”And so on. For example, if the task is “procure materials”, the performer is “materials department”. However, the “section” in charge may be different depending on the type of material, and the person in charge may be different depending on the supplier company of the procurement source. Therefore, if the task is defined in more detail, the performer may be “XX section” or “person in charge Δno × Buro”.
The actor definition database storage unit 111 stores performer definition data for a person who can be a task performer in a database format. A specific task executor is defined in task definition data described later. For example, in the task definition data, if the executor of the task is defined as “material department”, the executor definition data defines what organization the “material department” is.

The task definition database storage unit 112 stores task definition data using a storage device such as the magnetic disk device 920.
Task definition data is data that defines a task.
The definition of a task defines, for example, the work content of the task, the executor who executes the task, the format of information to be input by the task, and the format of information output by the task.
The work content of a task defines the content of work to be executed in the task, and is, for example, a sentence describing the work content in a natural language. Or when automating work and making a computer perform it, the program which described the process of work in the programming language may be sufficient.
An executor who executes a task is an executor who executes the specific task. The task definition data includes an identification name for identifying the executor, such as “executor: material department”. Although this alone does not reveal what the “material department” is, it is possible to know a detailed definition of the “material department” by referring to the executor definition data stored in the actor definition database storage section 111.
Information to be input by a task is information necessary for executing the task. For example, in the case of a “procure materials” task, information on how many materials to procure is necessary.
For example, in the “procure materials” task, a “purchase order” is input from another department in the company.
If there is a stock of the material described in the “Purchase”, the “Material Department” pays it to the department that ordered it. If there is no stock, procure materials from a business partner and deliver them to the department that ordered them.
The information output by a task is information indicating an execution result of executing the task, and is information necessary for executing the next task. For example, the “Materials Department” pays “Invoice” together with the procured materials to the department that has placed the order. In other words, the “procure materials” task outputs “invoice”.
In addition, in terms of the relationship between the “Material Department” and the business partner company, the “Material Department” can output “Purchase Order” and input “Invoice”.
Such “purchase orders” and “invoices” are usually formatted. This is because it is possible to avoid the risk of dropping items that must be described and to improve the efficiency of the work. This is the same whether the “purchase order” or “delivery note” is a paper document or electronic data. In addition, if the format is constant, the work can be automated using a computer.
The task definition data includes the definition of the format (format) of information input / output by the task. As a result, it is possible to ensure that information necessary for executing the task is reliably transmitted at the time of defining the task, so that the efficiency in actually executing the task is improved.
The task definition data also includes data indicating a task to be executed before executing the task and a task to be executed after executing the task.
For example, when there is another task that outputs information to be input by the task, the task can be executed only after the other task is executed. In this way, data indicating the order of task execution order is included in the task definition data.

The flow definition database storage unit 113 stores flow definition data using a storage device such as the magnetic disk device 920.
Flow definition data is data that defines the overall flow of work. The flow definition data is generated based on the task definition data. The task definition data includes data that indicates the task to be executed before execution of the task and the task to be executed after execution of the task, but this is limited to immediately before and after the task. I cannot grasp the flow. Therefore, by following the task definition data, flow definition data that can grasp the entire flow is generated and stored in the flow definition database storage unit 113.

The interface template database storage unit 114 stores interface template data using a storage device such as the magnetic disk device 920.
The interface template data is data that defines a template in the format of information input / output by a task. For example, the format of “Invoice” is defined in detail. The task definition data includes only an identification name for identifying an interface such as “input format: invoice (form 1)”, and the interface format database storage unit 114 stores the specific format for the task definition data. Refer to the template data.

The flow creation unit 120 generates an overall work flow based on the operation input by the terminal device 200.
The overall work flow represents a rough flow of the entire work.
The operation for generating the entire workflow is performed by, for example, an operator 811 who is in a position to summarize the entire workflow.
The overall work flow is composed of one or more general tasks. An outline task is a task that does not stipulate the details of work and is broadly grouped.
The operator 811 who is in a position of summarizing the whole usually does not know the details of the work contents in detail and leaves it to the site. This is because it is difficult to understand everything alone and the efficiency is low, such as when the organization is large.
For this reason, a rough flow of the entire work is constituted by a general task that does not define the work content so finely, and an overall work flow is generated.

  In addition, the flow creation unit 120 allocates the general tasks constituting the generated overall workflow to the performer based on the operation input by the terminal device 200. Here, the performer who allocates the general task is a high-level performer such as “part”. The operator 811 sets the site where the execution of the general task is entrusted as the general task performer.

The flow creation unit 120 uses a processing device such as the CPU 911 to generate general task definition data that defines a general task based on the input information.
The general task definition data generated by the flow creation unit 120 is stored as task definition data by the task definition database storage unit 112 using a storage device such as the magnetic disk device 920.

The task creation unit 130 details the general task based on the operation input by the terminal device 200.
The refinement of the summary task is to expand the summary task, which is a generally summarized task, into specific work (usually a plurality of tasks) (detailed task).
For example, the operator 812 and the operator 813 in the position of managing the site perform the operations for refining the overview task on the overview task allocated to the site managed by him / her.
This is because the operator 812 and the operator 813 are in a position to manage the site, and know in detail what kind of work should be performed in order to execute the general task.

The task creation unit 130 uses a processing device such as the CPU 911 to generate detailed task definition data that defines a detailed task based on the input information.
The detailed task definition data generated by the task creation unit 130 is stored as task definition data by the task definition database storage unit 112 using a storage device such as the magnetic disk device 920.

The interface creation unit 140 determines an interface for the detailed task based on the operation input by the terminal device 200.
The interface determination is to determine the format of information that is input or output by the task.
Since information required for the task differs depending on the specific work content of the task, the operation for determining the interface is performed by, for example, the operator 812 or the operator 813 who is in a position to manage the site.

The interface creation unit 140 uses a processing device such as the CPU 911 to generate interface definition data that defines an interface based on the input information.
The interface definition data generated by the interface creation unit 140 is stored as part of the detailed task definition data by the task definition database storage unit 112 using a storage device such as the magnetic disk device 920.

  In this way, the operators 811 to 813 each generate a workflow in a range that they are in charge of, thereby completing one huge workflow as a whole.

  The workflow generation system 800 outputs various flow diagrams and documents for a completed (or currently being created) workflow.

FIG. 4 is a diagram showing an example of the entire work flow diagram 710 output by the workflow generation system 800 in this embodiment.
Overall Workflow FIG. 710 is a diagram describing the overall workflow. For example, in this way, the overall flow of work is described in the form of a flowchart diagram.
For example, when the flow creation unit 120 creates the overall flow, the overall workflow diagram 710 (in the process of creation) is displayed on the screen of the terminal device 200 operated by the operator 811 to assist the operator 811 in the work.

FIG. 5 is a diagram showing an example of a schematic task flow diagram 720 output by the workflow generation system 800 in this embodiment.
General Task Flow FIG. 720 is a diagram in which the general task is classified for each performer and the work flow is described. For example, in this way, the work flow classified for each performer in the swimlane format is described.
In this example, “Organization A” to “Organization E” are performers who execute general tasks.
“Process 1: Overall work request” is a general task assigned to “Organization A”.
“Process 2: Overall work request” is a general task assigned to “Organization B”.
The general task may be executed by a plurality of performers. In that case, it is divided into areas for describing general tasks executed by each performer, such as “Process 4: Individual Work” and “Process 7: Work Result Report”. For this reason, one general task may be described in a plurality of parts.

FIG. 6 is a diagram showing an example of a detailed task flow diagram 730 output from the workflow generation system 800 according to this embodiment.
Detailed Task Flow FIG. 730 is a diagram describing the flow of work by classifying detailed tasks for each performer. For example, in this way, the work flow classified for each performer in the swimlane format is described.
In this example, “Organization A” to “Organization E” are performers who execute the refinement task.
“Organization C1” is a subordinate organization of “Organization C”, “Organization D1” and “Organization D2” are subordinate organizations of “Organization D”, and “Organization E1” is a subordinate organization of “Organization E”. The performer who performs the refinement task.
In this way, when the general task is detailed, the subordinate organization of the general task performer may be allocated as the detailed task performer, or the subordinate organization is not allocated and the general task performer is detailed as it is It may be a task executor.
For example, “Process 3” is refined into a refinement task “3-1” and a refinement task “3-2”, and the refinement task “3-2” is a subordinate organization of “Organization C”. It is assigned to a certain “organization C1”.
When one general task is allocated to a plurality of performers, even the same task may be different depending on the performer. For example, “Process 4” is assigned to “Organization D” and “Organization E”, but “Organization D” refines this into four refinement tasks, and “Organization E” creates three refinement tasks. It is detailed. In this example, in order to distinguish between them, “Process 4” assigned to “Organization D” is called “Process 4a”, and “Process 4” assigned to “Organization E” is called “Process 4b”. However, it is not necessary to change.
Further, as in the general task flow diagram 720 shown in the example of FIG. 5, a simple description of work performed in each task may be described.
In this example, since “Process 1”, “Process 2”, “Process 5”, and “Process 8” are not detailed, the general task is described as it is.

FIG. 7 is a diagram showing an example of a detailed work flow diagram 760 output from the workflow generation system 800 in this embodiment.
A detailed workflow diagram 760 is a type of the overall workflow diagram 710. The overall work flow diagram 710 shown in FIG. 4 is a diagram describing the flow of the entire work by the general task, whereas the detailed work flow diagram 760 describes the flow of the entire work by the detailed task. .
Further, in comparison with the detailed task flow diagram 730, the detailed task flow diagram 730 classifies and describes the detailed tasks for each performer, whereas the detailed work flow diagram 760 executes the detailed task. The whole is described as one flow without classifying each person.

FIG. 8 is an enlarged view of a part of another example of the detailed task flow diagram 730 output from the workflow generation system 800 according to this embodiment.
The detailed task flow diagram 730 shown in this example is obtained by adding the interface of the detailed task determined by the interface creation unit 140 to the detailed task flow diagram 730 shown in FIG.
In this example, the arrows connecting the quadrangle indicating the detailing task indicate the order of work and the flow of information. The rounded square at the tip drawn by the arrow pointing to the arrow indicates the format (interface) of the information. For example, the refinement task “3-1” outputs information in the format of “work instruction order ID: 00001 work name × ΔOO”, and the information is input by the refinement task “3-2”. .
If the detailed task flow diagram 730 describing all the interfaces is output, the figure becomes large. For example, when the detailed task flow diagram 730 is displayed on the screen of the terminal device 200, the mouse cursor is moved over the arrow. The interface of the information indicated by the arrow may be displayed only when the other interface is not displayed.

FIG. 9 is a diagram showing an example of a work definition list 770 output by the workflow generation system 800 in this embodiment.
The work definition list 770 is a diagram describing a list of general tasks executed by the executor and other executors who input and output information, focusing on one of the executors.
In this example, an ellipse written as “Organization C” in the center slightly upper left indicates that the work definition list 770 is for the executor “Organization C”. The ellipses written as “Organization A”, “Organization B”, “Organization D”, and “Organization E” on the right side are those who execute information exchange with “Organization C”. B, “Organization D”, and “Organization E”. In addition, a rectangle surrounded by a rounded rectangle below the ellipse labeled “Organization C” represents a general task executed by “Organization C”.

FIG. 10 is a diagram illustrating an example of a work definition document 740 output from the workflow generation system 800 according to this embodiment.
The work definition document 740 is a document that focuses on one of the performers and explains the contents of the task executed by the performer.
The work definition document 740 is generated from the task definition data stored in the task definition database storage unit 112.
In this example, the major items “1. Contract (XXΔ) individual work instruction” and “2. Work result council holding guidance” correspond to general tasks.
As the item name of the large item, for example, the name of the general task defined by the general task definition data is used.
Among the large items, the work outline (simple description of the work content) of the general task defined by the general task definition data is used for “(1) Work outline”.
Of the large items, the name of the detailed task that details the general task is used in the “(2) internal work item” portion. The detailed task is defined by detailed task definition data.
Of the large items, the work definition of the detailed task defined by the detailed task definition data (detailed description of the work content) is used in the part of “(3) Individual work definition”.
These sentences are included in the task definition data, and the workflow generation system 800 extracts necessary sentences from the task definition data and synthesizes them to generate a work definition document 740.

FIG. 11 is a diagram illustrating another example of the work definition document 740 output from the workflow generation system 800 according to this embodiment.
The work definition document 740 shown in this example omits the description of the work definition of the detailed task, and instead, what kind of interface exists with other performers is referred to as “(2) inter-organization interface”. Described in the item. In this example, the name of the interface is only described, but the definition of the interface (for example, the format of the document) may be described here.

FIG. 12 is a diagram showing an example of the interface specification 750 output from the workflow generation system 800 according to this embodiment.
The interface specification 750 is a document that describes the format of information exchanged between the detailed tasks executed by the executor (or its subordinate organization), focusing on two of the general task executors. .
The interface specification 750 is generated from the task definition data stored in the task definition database storage unit 112.
The interface specification 750 shown in this example describes the format of information exchanged between the executor “organization A” and the executor “organization C”.
The major items “1. Work result council holding guidance” and “2. Work completion report distribution” correspond to general tasks including a detailed task for outputting the information.
Among the major items, “(1) Organization C⇒Organization A” represents the direction of information. In this example, the executor “organization C” executes the general task “work result council holding guidance”, and the information output as a result is input by the task executed by the executor “organization A”. Yes.
Among the major items, “(2) Work contents” is the same as “(1) Work overview” in the work definition document 740, but in addition, the information format is also described.

  The workflow generation system 800 outputs the contents of the generated workflow as such a chart or document.

  Next, the functional block configuration of the workflow generation system 800 will be described in detail.

FIG. 13 is a detailed block diagram showing an example of the detailed block configuration of the flow creation unit 120 in this embodiment.
The flow creation unit 120 includes a general task input unit 121, a general task executor input unit 122, a general task definition generation unit 123, an overall workflow generation unit 124, an overall workflow output unit 125, an overall task flow generation unit 126, and an overall task. A flow output unit 127 is included.

The general task input unit 121 uses the input device such as the keyboard 902 and the mouse 903 of the terminal device 200 to input general tasks that constitute the entire work flow.
The general task input unit 121 outputs data representing the input general task using a processing device such as the CPU 911.

The general task performer input unit 122 inputs the general task performer using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200. The general task executor is an executor who executes the general task input by the general task input unit 121.
The general task performer input unit 122 is selected by the operator as the general task performer from among the performers defined by the performer definition data stored in the actor definition database storage unit 111 in advance as candidates for the general task performer. Enter the performer.

For example, the general task performer input unit 122 inputs the performer definition data stored in the actor definition database storage unit 111 using a processing device such as the CPU 911. The general task performer input unit 122 uses a display device 901 such as a CRT of the terminal device 200 to display a list of performers defined by the input performer definition data. The operator selects a general task performer from the displayed list of performers, and performs an operation such as double-clicking an input device such as a mouse 903. In the list of performers, all performers defined by the task definition data may be displayed, or performers excluding the subordinate organizations may be displayed.
The general task performer input unit 122 outputs data representing the input general task performer using a processing device such as the CPU 911.

The general task definition generation unit 123 inputs data representing the general task output from the general task input unit 121 using a processing device such as the CPU 911.
The general task definition generation unit 123 generates general task definition data based on the general task represented by the input data using a processing device such as the CPU 911. The general task definition data is data that defines a general task, and is a kind of task definition data.
The general task definition generation unit 123 outputs the generated general task definition data using a processing device such as the CPU 911.
The general task definition data output by the general task definition generation unit 123 is input by the task definition database storage unit 112 and stored as task definition data using a storage device such as the magnetic disk device 920.

The general task definition generation unit 123 inputs data representing the general task performer output from the general task performer input unit 122 using a processing device such as the CPU 911.
The general task definition generation unit 123 generates general task definition data based on the general task performer represented by the input data using a processing device such as the CPU 911.

For example, based on the general task input by the general task input unit 121, the general task definition generation unit 123 generates the general task definition data, and the task definition database storage unit 112 stores it. At this point, the general task definition data does not include data indicating the general task performer.
Next, the general task performer input unit 122 inputs the general task performer. The general task definition generation unit 123 inputs the general task definition data stored in the task definition database storage unit 112 using a processing device such as the CPU 911. The general task definition generation unit 123 generates general task definition data in which the general task performer is defined by adding data indicating the general task performer input by the general task performer input unit 122 to the general task definition data. To do. The general task definition generation unit 123 outputs the generated general task definition data using a processing device such as the CPU 911, and the task definition database storage unit 112 stores it using a storage device such as the magnetic disk device 920.

The overall workflow generation unit 124 inputs the task definition data stored in the task definition database storage unit 112 using a processing device such as the CPU 911.
The overall workflow generation unit 124 uses a processing device such as the CPU 911 to generate an overall workflow diagram 710 as shown in FIG. 4 based on the general task defined by the input task definition data.
The overall workflow generation unit 124 outputs data representing the generated overall workflow diagram 710 using a processing device such as the CPU 911.

The overall workflow output unit 125 inputs data representing the overall workflow diagram 710 output by the overall workflow generation unit 124 using a processing device such as the CPU 911.
The overall workflow output unit 125 outputs (displays / prints) an overall workflow diagram 710 represented by the input data using an output device such as a display device 901 such as a CRT of the terminal device 200 or a printer device 906.

The general task flow generation unit 126 inputs the task definition data stored in the task definition database storage unit 112 using a processing device such as the CPU 911.
The general task flow generation unit 126 generates a general task flow diagram 720 as illustrated in FIG. 5 based on the general task defined by the input task definition data, using a processing device such as the CPU 911.
The general task flow generation unit 126 outputs data representing the generated general task flow diagram 720 using a processing device such as the CPU 911.

The general task flow output unit 127 inputs data representing the general task flow diagram 720 output from the general task flow generation unit 126 using a processing device such as the CPU 911.
The general task flow output unit 127 outputs (displays / prints) the general task flow diagram 720 represented by the input data using an output device such as a display device 901 such as a CRT of the terminal device 200 and a printer device 906.

FIG. 14 is a detailed block diagram illustrating an example of a detailed block configuration of the task creation unit 130 in this embodiment.
The task creation unit 130 includes a detailed task input unit 131, a detailed task performer input unit 132, a detailed task definition generation unit 133, a detailed workflow generation unit 134, a detailed workflow output unit 135, and a detailed task flow generation unit 136. The detailed task flow output unit 137 is included.

The detailed task input unit 131 inputs a detailed task using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200. The detailed task input by the detailed task input unit 131 is a task in which the operator has detailed the general task defined by the task definition data stored in the task definition database storage unit 112.
The detailed task input unit 131 outputs data representing the input detailed task using a processing device such as the CPU 911.

The detailed task performer input unit 132 inputs a detailed task performer using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200. The detailed task executor is an executor who executes the detailed task input by the detailed task input unit 131.
The detailed task executor input unit 132 is an operator as a detailed task executor from among the performers defined by the executor definition data stored in the actor definition database storage unit 111 in advance as candidates for the detailed task executor. Enter the performer selected by.
The detailed task executor input unit 132 outputs data representing the input detailed task executor using a processing device such as the CPU 911.

The detailed task definition generation unit 133 inputs data representing the detailed task output from the detailed task input unit 131 using a processing device such as the CPU 911.
The detailed task definition generation unit 133 generates detailed task definition data based on the detailed task represented by the input data using a processing device such as the CPU 911. Detailed task definition data is data that defines a detailed task, and is a type of task definition data.

Further, the detailed task definition generation unit 133 inputs data representing the detailed task performer output from the detailed task performer input unit 132 using a processing device such as the CPU 911.
The detailed task definition generation unit 133 generates detailed task definition data based on the detailed task performer represented by the input data, using a processing device such as the CPU 911.

  The detailed task definition generation unit 133 outputs the detailed task definition data generated using the processing device such as the CPU 911. The detailed task definition data output by the detailed task definition generation unit 133 is a task definition database storage unit. 112 is input and stored as task definition data using a storage device such as the magnetic disk device 920.

The detailed workflow generation unit 134 inputs task definition data stored in the task definition database storage unit 112 using a processing device such as the CPU 911.
The detailed workflow generation unit 134 generates a detailed workflow diagram 760 as shown in FIG. 7 based on the detailed task defined by the input task definition data, using a processing device such as the CPU 911.
The detailed workflow generation unit 134 outputs data representing the generated detailed workflow diagram 760 using a processing device such as the CPU 911.

The detailed workflow output unit 135 inputs data representing the detailed workflow diagram 760 output by the detailed workflow generation unit 134 using a processing device such as the CPU 911.
The detailed workflow output unit 135 outputs (displays / prints) a detailed workflow diagram 760 represented by the input data, using an output device such as a display device 901 such as a CRT of the terminal device 200 or a printer device 906.

The detailed task flow generation unit 136 inputs the task definition data stored in the task definition database storage unit 112 using a processing device such as the CPU 911.
The detailed task flow generation unit 136 generates a detailed task flow diagram 730 as illustrated in FIG. 6 based on the detailed task defined by the input task definition data, using a processing device such as the CPU 911.
The detailed task flow generation unit 136 outputs data representing the generated detailed task flow diagram 730 using a processing device such as the CPU 911.

The detailed task flow output unit 137 inputs data representing the detailed task flow diagram 730 output from the detailed task flow generation unit 136 using a processing device such as the CPU 911.
The detailed task flow output unit 137 outputs (displays / prints) a detailed task flow diagram 730 represented by the input data using an output device such as a display device 901 such as a CRT of the terminal device 200 and a printer device 906.

FIG. 15 is a detailed block diagram showing an example of a detailed block configuration of the interface creation unit 140 in this embodiment.
The interface creation unit 140 includes an interface input unit 141, an interface definition generation unit 143, a detailed task flow generation unit 144, a detailed task flow output unit 145, a work definition document generation unit 146, a work definition document output unit 147, and an interface specification document generation unit. 148, and an interface specification document output unit 149.

The interface input unit 141 inputs an upstream interface and a downstream interface using an input device such as a keyboard 902 or a mouse 903 of the terminal device 200. The upstream interface represents the format of information input by the task. The downstream interface represents the format of information output by the task. Since the information output from the task becomes the input of the next task, the downstream interface of a certain task needs to match the upstream interface of the next task.
Therefore, the interface input unit 141 displays the CRT or the like of the terminal device 200 when the input upstream interface does not match the downstream interface of the previous task or when the input downstream interface does not match the upstream interface of the next task. A warning may be displayed on the device 901.
The interface input unit 141 outputs data representing the input upstream interface and downstream interface using a processing device such as the CPU 911.

The interface definition generation unit 143 inputs data representing the upstream interface and the downstream interface output from the interface input unit 141 using a processing device such as the CPU 911.
The interface definition generation unit 143 uses a processing device such as the CPU 911 to generate interface definition data based on the upstream interface and the downstream interface represented by the input data. The interface definition data is data that defines the format (interface) of information input / output by the detailed task defined by the task definition data stored in the task definition database storage unit 112, and is a kind of task definition data. The interface definition data may be part of the detailed task definition data.
The interface definition generation unit 143 outputs the generated interface definition data using a processing device such as the CPU 911. The interface definition data output by the interface definition generation unit 143 is input by the task definition database storage unit 112 and stored as task definition data using a storage device such as the magnetic disk device 920.
Note that if the downstream interface represented by the input data does not match the upstream interface of the next task, the interface definition generation unit 143 changes the task definition data of the next task using the processing device such as the CPU 911, and the interface May be matched.

  The detailed task flow generation unit 144 generates a detailed task flow diagram 730 from the task definition data stored in the task definition database storage unit 112, similarly to the detailed task flow generation unit 136 of the task creation unit 130. However, the detailed task flow diagram 730 generated by the detailed task flow generation unit 144 is different in that it includes information about the interface as shown in FIG.

The detailed task flow output unit 145 inputs data representing the detailed task flow diagram 730 output by the detailed task flow generation unit 144 using a processing device such as the CPU 911.
The detailed task flow output unit 145 outputs (displays / prints) the detailed task flow diagram 730 represented by the input data by using the display device 901 such as the CRT of the terminal device 200 and the output device such as the printer device 906.

The work definition document generation unit 146 inputs task definition data stored in the task definition database storage unit 112 using a processing device such as the CPU 911.
The work definition document generation unit 146 uses a processing device such as the CPU 911 to generate a work definition document 740 as illustrated in FIG. 10 or 11 based on the detailed task defined by the input task definition data.
The work definition document generation unit 146 outputs data representing the generated work definition document 740 using a processing device such as the CPU 911.

The work definition document output unit 147 inputs data representing the work definition document 740 output by the work definition document generation unit 146 using a processing device such as the CPU 911.
The work definition document output unit 147 outputs (displays / prints) a work definition document 740 represented by the input data using an output device such as a display device 901 such as a CRT of the terminal device 200 or a printer device 906.

The interface specification document generation unit 148 inputs the task definition data stored in the task definition database storage unit 112 using a processing device such as the CPU 911.
The interface specification document generation unit 148 generates an interface specification document 750 as shown in FIG. 12 based on the upstream interface and the downstream interface defined by the input task definition data, using a processing device such as the CPU 911.
The interface specification document generation unit 148 outputs data representing the generated interface specification document 750 using a processing device such as the CPU 911.

The interface specification document output unit 149 inputs data representing the interface specification document 750 output from the interface specification document generation unit 148 using a processing device such as the CPU 911.
The interface specification document output unit 149 outputs (displays / prints) an interface specification document 750 represented by the input data using an output device such as a display device 901 such as a CRT of the terminal device 200 or a printer device 906.

  Next, a procedure for generating a workflow using the workflow generation system 800 in this embodiment will be described.

FIG. 16 is a flowchart showing an example of a process flow of a workflow generation procedure for generating a workflow using the workflow generation system 800 according to this embodiment.
The workflow generation procedure includes an overall workflow creation process S11, a task allocation process S12, a task detailing process S13, and an interface defining process S14.

  In the overall workflow creation step S <b> 11, an operator 811 (a person who is in a position to summarize the entire workflow) creates an overall workflow using the workflow generation system 800. In the workflow generation system 800, the flow creation unit 120 supports the operator 811 by inputting the operation of the operator 811 and displaying the entire work flow diagram 710 being created.

  In the task allocation step S12, the operator 811 uses the workflow generation system 800 to allocate the general tasks constituting the overall workflow created in the overall workflow creation step S11 to the performer. The workflow generation system 800 supports the operator 811 by displaying a general task flow diagram 720 representing a result of assigning the general task to the performer by the flow creation unit 120 inputting the operation of the operator 811 and the like.

  In the task detailing step S <b> 13, the operator 812 and the operator 813 (who are in a position to manage each site) use the workflow generation system 800 to detail the general tasks assigned to each. In the workflow generation system 800, the task creation unit 130 inputs the operation of the operator 812 / operator 813 and displays a detailed task flow diagram 730 showing the result of refining the general task. Person 813 is supported.

  In the interface defining step S14, the operator 812 and the operator 813 define the upstream interface and the downstream interface of the detailed task in which the general task is detailed. In the workflow generation system 800, the interface creation unit 140 inputs the operations of the operator 812 and the operator 813, and displays a detailed task flow diagram 730 showing the result of defining the interface. To help. In addition, the interface creation unit 140 warns the operator 812 and the operator 813 when the downstream interface of the task and the upstream interface of the next task do not match, thereby causing an interface mismatch. prevent.

  As described above, the operators 811 to 813 cooperate to complete one workflow.

  Next, details of the workflow generation procedure will be described.

  The operator 811 logs in to the terminal device 200. The terminal device 200 authenticates the operator 811 and confirms that it has the authority to create the entire workflow. If the operator 811 does not have the authority to create the entire workflow, the following processing cannot be performed.

FIG. 17 is a diagram showing an example of an overall workflow creation screen displayed on the display device 901 such as a CRT of the terminal device 200 in the overall workflow creation step S11 in this embodiment.
In this example, the figure in the left square represents the parts that make up the overall workflow. The central graphic represents the overall work flow being created. The arrow slightly below the right represents a mouse cursor.
For example, the operator 811 operates the mouse 903 of the terminal device 200, moves the mouse cursor to the left part, and drags and drops the entire work flow.
An operation of the operator 811 is input by the general task input unit 121, and the general task definition generation unit 123 sequentially generates task definition data. Based on the task definition data, the overall workflow generation unit 124 generates an overall workflow diagram 710 representing the overall workflow being created. As shown in this figure, a display device 901 such as a CRT of the terminal device 200 is displayed. indicate.
In this way, the operator 811 completes the entire workflow, and at the same time, task definition data is generated.

  When the entire work flow is completed, the process proceeds to the task allocation step S12.

FIG. 18 is a diagram showing an example of a task allocation screen displayed on the display device 901 such as a CRT of the terminal device 200 in the task allocation step S12 in this embodiment.
The flowchart on the left is an overall workflow diagram 710 representing the overall workflow created in the overall workflow creation step S11.
The table on the right represents the performer performing the general task. The name of the executor is displayed at the top, and the general task executed by the executor is displayed below it. Immediately after the start of the task allocation step S12, since the general task is not allocated to the performer, the column below the performer is blank.

  For example, the operator 811 operates the mouse 903 of the terminal device 200, moves the mouse cursor to a square representing the general task in the overall workflow on the left side, and drags and drops the general task to execute the general task. Allocate people.

FIG. 19 is a diagram showing another example of a task allocation screen displayed on the display device 901 such as a CRT of the terminal device 200 in the task allocation step S12 in this embodiment.
FIG. 18 shows a screen immediately after the task allocation step S12 is started, whereas this diagram shows a screen in which the work is slightly advanced.
The flowchart on the left is an overall workflow diagram 710 generated by the overall workflow generation unit 124. The table on the right side is a schematic task flow diagram 720 generated by the general task flow generation unit 126.

  The operation of the operator 811 is input by the general task executor input unit 122, and the general task definition generation unit 123 sequentially generates task definition data. The general task flow generation unit 126 generates a general task flow diagram 720 (in an incomplete state) based on the task definition data, and a display device 901 such as a CRT of the terminal device 200 displays the general task flow diagram 720 as shown in FIG. .

Since it may be desired to add a general task at this stage, the overall workflow may be changed by an operation such as clicking the overall workflow diagram 710 on the left side.
In this case, the operation is input by the general task input unit 121, and the general task definition generation unit 123 changes the task definition data stored in the task definition database storage unit 112.
Alternatively, the entire work flow may be created on the task allocation screen from the beginning.

FIG. 20 is a diagram showing still another example of a task allocation screen displayed on the display device 901 such as a CRT of the terminal device 200 in the task allocation step S12 in this embodiment.
This figure shows a screen in a state where the work of the task allocation step S12 is completed and the general task flow diagram 720 is completed.
Thus, the operator 811 completes the general task flow diagram 720, and at the same time, task definition data in which the general task performer is defined is generated.

Next, it progresses to task detailed process S13.
The operator 812 and the operator 813 log in to their terminal devices 200, respectively. Each terminal device 200 authenticates the operator 812 and the operator 813, and confirms the authority ranges that can be operated by the operator 812 and the operator 813, respectively.

FIG. 21 is a diagram illustrating an example of a task detailing screen displayed on the display device 901 such as a CRT of the terminal device 200 in the task detailing step S13 in this embodiment.
This example is a screen displayed by the terminal device 200 of the operator 812. The operator 812 is the person in charge of the “system design section” and has the authority to refine the general tasks allocated to the “system design section”. For this reason, the subordinate performers of the “system design section” are displayed in detail.
The flowchart on the left side is a detailed workflow diagram 760 generated by the detailed workflow generation unit 134. Since none of the general tasks has been detailed yet at this stage, the detailed workflow diagram 760 is the same as the overall workflow diagram 710 of FIG.
The table on the right side is a detailed task flow diagram 730 generated by the detailed task flow generation unit 136. Again, since none of the general tasks has been detailed yet, it is the same as the detailed task flow diagram 730 in FIG. 19 except that the person executing the “system design section” has become more detailed.

The operator 812 refines the general task by performing an operation such as clicking a square representing the general task on the detailed task flow diagram 730. The detailed task input unit 131 inputs the operation of the operator 812.
In this example, the operator 812 is the person in charge of the “system design section” and has the authority to “detail the general task assigned to the system design section. Therefore, the operator 812 is assigned to the“ system design section ”. Clicking the square representing the general task allows the detailed work to be performed, but the detailed task input unit 131 performs the operation even if the square representing the general task assigned to another section is clicked. Not accepted.

In order to realize this, for example, an operator who has authority to change a task executed by the executor is defined in the executor definition data stored in the actor definition database storage unit 111. For example, the login name of the operator who has the authority to change the task executed by the executor is included in the executor definition data.
The detailed task input unit 131 inputs task definition data that defines the general task clicked by the operator 812 from the task definition data stored in the task definition database storage unit 112 using a processing device such as the CPU 911. The detailed task input unit 131 uses a processing device such as the CPU 911 to acquire a general task performer who executes the general task based on the input task definition data.
The refinement task input unit 131 uses a processing device such as the CPU 911 to input performer definition data that defines the acquired general task performer from the performer definition data stored in the actor definition database storage unit 111. The detailed task input unit 131 uses a processing device such as the CPU 911 to determine whether the operator 812 has the authority to change the general task based on the input performer definition data.
When it is determined that the operator 812 has the authority to change the general task, the detailed task input unit 131 accepts the operation of the operator 812 using a processing device such as the CPU 911 and performs task detailing processing. . When it is determined that the operator 812 does not have the authority to change the general task, the detailed task input unit 131 invalidates the operation of the operator 812 using a processing device such as the CPU 911 and the CRT of the terminal device 200. For example, a warning message is displayed on the display device 901 to notify the operator 812 that there is no change authority.

FIG. 22 is a diagram showing another example of the task detailing screen displayed on the display device 901 such as the CRT of the terminal device 200 in the task detailing step S13 in this embodiment.
This figure shows a screen in a state where the work of the task detailing step S13 has advanced a little. One of the general tasks executed by the “system design section” has been detailed to create two detailed tasks.
The detailing task input unit 131 inputs a detailing task based on the input operation of the operator 812. The detailed task definition generation unit 133 generates detailed task definition data based on the detailed task input by the detailed task input unit 131 using a processing device such as the CPU 911, and the task definition database storage unit 112 stores the detailed task definition data. To do. The detailed workflow generation unit 134 generates a detailed workflow diagram 760 based on the task definition data stored in the task definition database storage unit 112 using a processing device such as the CPU 911. The detailed task flow generation unit 136 generates a detailed task flow diagram 730 based on the task definition data stored in the task definition database storage unit 112 using a processing device such as the CPU 911. The generated detailed work flow diagram 760 and the detailed task flow diagram 730 are displayed by the detailed work flow output unit 135 and the detailed task flow output unit 137 using the display device 901 such as the CRT of the terminal device 200, and are shown in this figure. Screen.
The result of the refinement is reflected not only in the detailed task flow diagram 730 on the right side but also in the detailed workflow diagram 760 on the left side.

FIG. 23 is a diagram showing still another example of the task detailing screen displayed on the display device 901 such as the CRT of the terminal device 200 in the task detailing step S13 in this embodiment.
This figure shows a screen in a state where the work of the task detailing step S13 has further progressed. The two detailed tasks that have been refined by the “system design section” are assigned to the power supply system and the communication system, which are the subordinate performers.
The operation performed by the operator 812 to assign the performer who executes the detailed task to the detailed task is the same as the operation performed by the operator 811 in the task allocation step S12.
The operation of the operator 812 is input by the detailed task performer input unit 132, and the detailed task definition generation unit 133 generates detailed task definition data. In this example, the detailed task definition generation unit 133 determines that the detailed task performer is defined as “system design section” in the detailed task definition data as “power supply system” or “communication system”. Change to, and generate the modified detailed task definition data. The generated task definition data is stored as task definition data by the task definition database storage unit 112 using a storage device such as the magnetic disk device 920.
The detailed workflow generation unit 134 and the detailed task flow generation unit 136 generate a detailed workflow diagram 760 and a detailed task flow diagram 730 based on the task definition data stored in the task definition database storage unit 112, and output a detailed workflow. The unit 135 and the detailed task flow output unit 137 display using a display device 901 such as a CRT of the terminal device 200.
In this example, only the detailed task executor is changed, so the detailed task flow diagram 730 has changed, but the detailed work flow diagram 760 has not changed.
In this way, the operator 812 and the operator 813 refine the task.

Next, it progresses to interface prescription process S14.
For example, the operator 812 clicks an arrow connecting a square representing a task on the task detailing screen shown in FIG. 23, and selects a flow of information represented by the arrow. The interface input unit 141 displays a list of interfaces defined by the interface template data stored in the interface template database storage unit 114 using a display device 901 such as a CRT of the terminal device 200, and the operator 812 can display the list of interfaces. Select the format of the information.
The operation of the operator 812 is input by the interface input unit 141, and the interface definition generation unit 143 generates interface definition data. The generated interface definition data is stored as task definition data by the task definition database storage unit 112 using a storage device such as the magnetic disk device 920.
The detailed workflow generation unit 134 and the detailed task flow generation unit 136 generate a detailed workflow diagram 760 and a detailed task flow diagram 730 based on the task definition data stored in the task definition database storage unit 112, and output a detailed workflow. The unit 135 and the detailed task flow output unit 137 display using a display device 901 such as a CRT of the terminal device 200.
At this time, for example, when the interface is defined, the arrow color is green, when the interface is not defined, yellow, and when the interface is inconsistent, it is displayed red. It is good also as notifying whether it was completed.

  The workflow is completed as described above.

In addition, although said procedure was performed in order here, it does not necessarily need to be performed in order.
For example, before the overall workflow is completed in the overall workflow creation step S11, the completed general task may be allocated to the performer in the task allocation step S12 and the task detailing step S13 may be started. Further, after assigning the detailing task in the task detailing step S13, an operator having the authority to change the assigned detailing task may further refine the detailing task. In addition, before the task detailing is completed in the task detailing step S13, an interface may be defined in the interface defining step S14 for the completed detailing task for the time being.

The workflow generation system 800 (workflow generation apparatus) in this embodiment
An input device such as a keyboard 902 and a mouse 903 for inputting information, a storage device such as a magnetic disk device 920 for storing information, a processing device such as a CPU 911 for processing information, an actor definition database storage unit 111, and a general task Input unit 121, general task performer input unit 122, general task definition generation unit 123, task definition database storage unit 112, detailed task input unit 131, detailed task performer input unit 132, and detailed And a task definition generation unit 133.
The actor definition database storage unit 111 uses a storage device such as a magnetic disk device 920 to store executor definition data that defines an executor that executes a task.
The general task input unit 121 uses an input device such as a keyboard 902 or a mouse 903 to input general tasks constituting an overall work flow representing the overall work flow.
The general task performer input unit 122 is input by the general task input unit 121 from the performers defined by the performer definition data stored in the actor definition database storage unit 111 using an input device such as a keyboard 902 or a mouse 903. The general task executor selected by the first operator 811 is input as the executor who executes the general task.
The general task definition generation unit 123 uses a processing device such as the CPU 911 to execute the general task based on the general task input by the general task input unit 121 and the general task performer input by the general task performer input unit 122. The general task definition data for defining the task is generated.
The task definition database storage unit 112 stores the general task definition data generated by the general task definition generation unit 123 as task definition data for defining a task using a storage device such as a magnetic disk device 920. .
The detailed task input unit 131 uses the input device such as the keyboard 902 or the mouse 903, and the details of the general task defined by the task definition data stored in the task definition database storage unit 112 are detailed by the second operator 812. It is characterized by inputting a task.
The detailed task executor input unit 132 uses the input device such as the keyboard 902 and the mouse 903 to specify the detailed task input unit 131 from the performers defined by the executor definition data stored in the actor definition database storage unit 111. The detailed task executor selected by the second operator 812 is input as the executor to execute the detailed task input by the user.
The detailed task definition generation unit 133 uses a processing device such as the CPU 911 to convert the detailed task input by the detailed task input unit 131 and the detailed task performer input by the detailed task performer input unit 132. Based on this, detailed task definition data for defining a detailed task is generated.
The task definition database storage unit 112 further stores the detailed task definition data generated by the detailed task definition generation unit 133 as task definition data using a storage device such as a magnetic disk device 920. .

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, the general task created by the first operator 811 and its executor are represented by the general task input unit 121 and the general task performer input unit 122. The detailed task created by the second operator 812 and its executor are input by the detailed task input unit 131 and the detailed task executor input unit 132, and the general task definition generating unit 123 and the details are input. Since the generalized task definition generation unit 133 generates the task definition data, a plurality of operators can create a single workflow as a whole by creating a workflow in the range of their own responsibility.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The detailed task input unit 131 uses the input device such as the mouse 903 when the second operator 812 has the authority to change the task executed by the general task executor that executes the general task. Is input.

According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when the second operator 812 has the authority to change the task executed by the general task executor, the detailed task input unit Since the detailing task 131 inputs the detailed task, the authority range of each operator is clarified.
Also, by giving such authority to an operator who is familiar with the work actually performed by the general task executor, there is an effect that an effective workflow reflecting the substance can be generated.

The workflow generation system 800 (workflow generation apparatus) according to this embodiment further includes an interface input unit 141 and an interface definition generation unit 143.
The interface input unit 141 uses an input device such as a mouse 903, an upstream interface representing the format of information input by the detailed task defined by the task definition data stored in the task definition database storage unit 112, and the detailed task And a downstream interface representing a format of information to be output.
The interface definition generation unit 143 uses a processing device such as the CPU 911 to generate interface definition data that defines the format of information input and output by the refinement task based on the upstream interface and the downstream interface input by the interface input unit 141. It is characterized by generating.
The task definition database storage unit 112 further stores the interface definition data generated by the interface definition generation unit 143 as task definition data using a storage device such as a magnetic disk device 920.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, the interface definition generation unit 143 generates interface definition data that defines the format of information exchanged between the detailed tasks, and the task definition database Since the storage unit 112 stores it as task definition data, it is possible to easily check for lack of necessary information when executing a task, thereby improving work efficiency.

The workflow generation system 800 (workflow generation device) in this embodiment further includes an output device such as a display device 901 such as a CRT and a printer device 906 that outputs information, an overall workflow generation unit 124, and an overall workflow output. And a portion 125.
The overall workflow generation unit 124 uses a processing device such as the CPU 911 to describe an overall workflow diagram 710 describing the overall workflow based on the general task defined by the task definition data stored in the task definition database storage unit 112. Is generated.
The overall workflow output unit 125 outputs an overall workflow diagram generated by the overall workflow generation unit 124 using an output device such as a display device 901 such as a CRT or a printer device 906.

According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, since the overall workflow diagram generated by the overall workflow generation unit 124 is output, it is possible to easily grasp the overall workflow. There is an effect that the generated workflow can be effectively used.
Also, when the operator 811 is creating an overall workflow, the overall workflow generation unit 124 generates an overall workflow diagram 710 based on the task definition data generated so far, and displays it on a display device 901 such as a CRT. By displaying, there is an effect that the operator 811 can efficiently perform the work of creating the entire work flow.

The workflow generation system 800 (workflow generation device) in this embodiment further includes an output device such as a display device 901 such as a CRT and a printer device 906 that outputs information, a general taskflow generation unit 126, and a general taskflow output. Part 127.
The general task flow generation unit 126 is executed for each general task performer who executes the general task based on the general task defined by the task definition data stored in the task definition database storage unit 112 using a processing device such as the CPU 911. A general task flow diagram 720 describing the flow of work by classifying the work to be performed is generated.
The general task flow output unit 127 outputs the general task flow diagram 720 generated by the general task flow generation unit 126 using an output device such as a display device 901 such as a CRT or a printer device 906.

According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, the general task flow generation unit 126 generates and outputs the general task flow diagram 720 in which the general tasks are classified for each performer. There is an effect that can be effectively utilized.
Further, when the operator 811 assigns the performer to the general task, the general task flow generation unit 126 generates the general task flow diagram 720 based on the task definition data reflecting the result of the assignment so far, and the processing of the CPU 911 or the like By displaying on the apparatus, there is an effect that the operator 811 can efficiently perform the work of assigning the performer to the general task.

The workflow generation system 800 (workflow generation device) in this embodiment further includes an output device such as a display device 901 such as a CRT and a printer device 906 that outputs information, a detailed task flow generation unit 136, and a detailed task flow output. And a portion 137.
The detailed task flow generator 136 uses a processing device such as the CPU 911 to execute a detailed task based on the detailed task defined by the task definition data stored in the task definition database storage unit 112. A detailed task flow diagram 730 describing the flow of work is generated by classifying the work to be performed for each, and is characterized in that it is generated.
The detailed task flow output unit 137 outputs the detailed task flow diagram 730 generated by the detailed task flow generation unit 136 using an output device such as a display device 901 such as a CRT or a printer device 906.

According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, the detailed taskflow generation unit 136 generates and outputs a detailed taskflow diagram 730 in which detailed tasks are classified for each performer. There is an effect that the workflow can be used effectively.
Further, when the operator 812 details the general task, the detailed task flow generation unit 136 generates the detailed task flow diagram 730 based on the task definition data that has been detailed so far and reflects the result of assigning the performer. By displaying on a display device 901 such as a CRT, the operator 812 refines the general task and efficiently performs the work of assigning the performer.

The workflow generation system 800 (workflow generation device) in this embodiment further includes an output device such as a display device 901 such as a CRT and a printer device 906 that outputs information, a work definition document generation unit 146, and a work definition document output. And a portion 147.
The work definition document generation unit 146 uses a processing device such as the CPU 911 to perform details executed by a predetermined detailed task performer based on the detailed task defined by the task definition data stored in the task definition database storage unit 112. It is characterized in that a work definition document 740 describing a definition of a computerized task is generated.
The work definition document output unit 147 outputs the work definition document 740 generated by the work definition document generation unit 146 using an output device such as a display device 901 such as a CRT or a printer device 906.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, the work definition document generation unit 146 generates and outputs a work definition document 740 describing the definition of a task executed by a predetermined executor. The contents of the generated workflow can be thoroughly communicated to all. The work definition details the details of the work, so the practitioner will not misunderstand the meaning of the term and do the wrong work, and the administrator will understand the contents of the actual work well. The effect is that you can improve your work.

The workflow generation system 800 (workflow generation device) in this embodiment further includes an output device such as a display device 901 such as a CRT and a printer device 906 that outputs information, an interface specification document generation unit 148, and an interface specification document output And a portion 149.
The interface specification document generation unit 148 uses a processing device such as the CPU 911 to execute a predetermined detailed task executor based on the upstream interface and the downstream interface defined by the task definition data stored in the task definition database storage unit 112. An interface specification document 750 describing the format of information input by the detailed task to be executed and the format of information output by the detailed task is generated.
The interface specification document output unit 149 outputs the interface specification document 750 generated by the interface specification document generation unit 148 using a processing device such as a CPU 911.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, the interface specification document generation unit 148 generates and outputs an interface specification document 750 that defines an interface of a task executed by a predetermined executor. The format of information exchanged between tasks in the generated workflow can be made known to everyone. The format of the information is stipulated in detail in the interface specification document, so that it is possible to prevent the executioner from misinterpreting the meaning of the information and prevent necessary information from being transmitted, and to execute the work efficiently. There is an effect that can be done.

A workflow generation method in which the workflow generation system 800 (workflow generation apparatus) in this embodiment generates a workflow is as follows:
A workflow generation system 800 (workflow generation device) having an input device such as a keyboard 902 and a mouse 903 for inputting information, a storage device such as a magnetic disk device 920 for storing information, and a processing device such as a CPU 911 for processing information. Is a workflow generation method for generating a workflow, characterized by performing the following processing.
A storage device such as the magnetic disk device 920 stores executor definition data that defines the executor that executes the task.
Input devices such as a keyboard 902 and a mouse 903 input general tasks constituting the entire work flow representing the entire work flow.
The input device such as the keyboard 902 and the mouse 903 executes the general task input by the input device such as the keyboard 902 and the mouse 903 from the performers defined by the performer definition data stored in the storage device such as the magnetic disk device 920. The general task performer selected by the first operator 811 is input as the performer.
An outline in which a processing device such as a CPU 911 defines an outline task based on an outline task input by an input device such as a keyboard 902 or a mouse 903 and an outline task performer input by an input device such as a keyboard 902 or a mouse 903. Generate task definition data.
A storage device such as the magnetic disk device 920 stores general task definition data generated by a processing device such as the CPU 911 as task definition data for defining a task.
An input device such as a keyboard 902 or a mouse 903 inputs a detailed task in which the second operator 812 has refined a general task defined by task definition data stored in a storage device such as a magnetic disk device 920.
The refinement task input by the input device such as the keyboard 902 or the mouse 903 from the performers defined by the performer definition data stored in the storage device such as the magnetic disk device 920 is input by the input device such as the keyboard 902 or the mouse 903. The detailed task executor selected by the second operator 812 is input as the executor to be executed.
The processing device such as the CPU 911 performs the refinement task based on the refinement task input by the input device such as the keyboard 902 and the mouse 903 and the refinement task performer input by the input device such as the keyboard 902 and the mouse 903. Generate detailed task definition data to be defined.
A storage device such as the magnetic disk device 920 stores detailed task definition data generated by a processing device such as the CPU 911 as task definition data.

  According to the workflow generation method in this embodiment, the first operator 811 creates a general task, and the second operator 812 details the general task. By creating a workflow, there is an effect that one huge workflow can be generated as a whole.

  A workflow generation system 800 (workflow generation device) in this embodiment includes an input device such as a keyboard 902 and a mouse 903 for inputting information, a storage device such as a magnetic disk device 920 for storing information, and a CPU 911 for processing information. And a computer that causes a computer having a processing device such as a display device 901 such as a CRT that outputs information and an output device such as a printer device 906 to function as the workflow generation system 800 (workflow generation device) in this embodiment. It can be realized by executing.

  According to the program that causes a computer to function as the workflow generation system 800 (workflow generation device) in this embodiment, a plurality of operators create a workflow in their own area, thereby generating one huge workflow as a whole. The workflow generation system 800 (workflow generation apparatus) that can be realized is achieved.

Embodiment 2. FIG.
The second embodiment will be described with reference to FIGS.
Since the configuration, appearance, and hardware resources of the functional block of the workflow generation system 800 in this embodiment are the same as those of the workflow generation system 800 described in the first embodiment, description thereof is omitted here.

In the workflow generation system 800 according to the first embodiment, the operator 812 who performs the work of refining the outline task can only change within his authority range.
However, in some cases, it may be necessary to make changes that exceed your authority.
The workflow generation system 800 in this embodiment enables the operator 812 to make changes that exceed his authority range.

FIG. 24 is a detailed block diagram showing an example of a detailed block configuration of the task creation unit 130 in this embodiment.
Note that blocks common to the detailed blocks of the task creation unit 130 described in the first embodiment are denoted by the same reference numerals, and description thereof is omitted here.

  The task creation unit 130 includes a detailed task input unit 131, a detailed task executor input unit 132, an executor change authority determination unit 151, an executor change request notification unit 161, an executor change approval / disapproval input unit 171, and a detailed task definition. A generation unit 133, a detailed workflow generation unit 134, a detailed workflow output unit 135, a detailed taskflow generation unit 136, and a detailed taskflow output unit 137 are included.

The executor change authority determination unit 151 inputs data representing the detailed task executor output from the detailed task executor input unit 132 using a processing device such as the CPU 911.
The executor change authority determination unit 151 inputs executor definition data defining the input detailed task executor from the executor definition data stored in the actor definition database storage unit 111 using a processing device such as the CPU 911. .
The executor change authority determination unit 151 uses a processing device such as the CPU 911, and based on the input executor definition data, the operator who has input the detailed task executor by the detailed task executor input unit 132 is detailed. It is determined whether or not the task execution person has change authority to change the task to be executed.

  When the executor change authority determination unit 151 determines that the operator has change authority, the detailed task definition generation unit 133 generates detailed task definition data using a processing device such as the CPU 911.

When the executor change authority determination unit 151 determines that the operator has no change authority, the executor change request notification unit 161 uses a processing device such as the CPU 911 to notify another operator who has the change authority. To request approval of the change of the performer.
For example, another operator having change authority makes a determination based on the executor definition data input by the executor change authority determination unit 151.

The executor change request notifying unit 161 displays, for example, a message requesting approval of the executor's change using the display device 901 such as the CRT of the terminal device 200 of the operator having the change authority.
Alternatively, the executor change request notifying unit 161 transmits an e-mail requesting approval of the executor's change to an operator who has change authority, and the operator reads the e-mail so that the CRT A message may be displayed on the display device 901.

The executor change approval / disapproval input unit 171 uses an input device such as the keyboard 902 or the mouse 903 of the operator's terminal device 200 that has notified that the executor change request notification unit 161 requests the approval of the executor's change. Enter executor change acceptance / rejection information. The executor change approval / disapproval information is information indicating whether or not the operator who has notified that the executor change request notifying unit 161 requests the executor's change is approved.
The executor change approval / disapproval input unit 171 uses a processing device such as the CPU 911 to determine whether or not the input executor change approval / disapproval information indicates that the change is approved.

  When the executor change permission / denial input unit 171 determines that the change has been approved, the detailed task definition generation unit 133 generates detailed task definition data using a processing device such as the CPU 911.

  Next, the operation will be described.

FIG. 25 is a flowchart showing an example of a detailed task setting process in which the task creation unit 130 sets a detailed task in this embodiment.
The detailed task setting process includes a detailed task input step S21, a detailed task executor input step S22, an executor change authority determination step S23, an executor change request notification step S24, an executor change approval / disapproval input step S25, a detailed task. It has a definition generation step S26 and an executor change rejection notification step S27.

In the detailed task input step S21, the detailed task input unit 131 uses the input device such as the keyboard 902 or the mouse 903 of the terminal device 200 of the operator 812 to make the detailed task the detailed task detailed by the operator 812. Enter.
At this time, the detailed task input unit 131 determines whether or not the operator 812 has the authority to refine the general task, and inputs the detailed task if the authority is given.
The detailed task input unit 131 outputs data representing the input detailed task using a processing device such as the CPU 911.
The detailed task definition generation unit 133 inputs the data output from the detailed task input unit 131 using a processing device such as the CPU 911.
The detailed task definition generation unit 133 generates detailed task definition data based on the input data using a processing device such as the CPU 911.
At this time, a general task executor is provisionally set as the detailed task executor.
The detailed task definition generation unit 133 outputs the generated detailed task definition data using a processing device such as the CPU 911.
The task definition database storage unit 112 inputs the detailed task definition data output by the detailed task definition generation unit 133 using a processing device such as the CPU 911.
The task definition database storage unit 112 stores the input detailed task definition data using a storage device such as the magnetic disk device 920.

In the detailed task performer input step S <b> 22, the detailed task performer input unit 132 inputs the detailed task performer selected by the operator 812 using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200. To do.
At this time, a general task executor is set as the detailed task executor in the detailed task definition data. Accordingly, the operator 812 has the authority to change the detailing task. That is, the detailed task executor can be changed. Therefore, the detailing task performer input unit 132 inputs the detailing task performer selected (after change) by the operator 812.
The detailed task executor input unit 132 outputs data representing the input detailed task executor using a processing device such as the CPU 911.

In the executor change authority determining step S23, the executor change authority determining unit 151 inputs the data output by the detailed task executor input unit 132 in the detailed task executor input step S22 using a processing device such as the CPU 911. To do.
The executor change authority determination unit 151 uses a processing device such as the CPU 911 to execute executor definition data that defines the detailed task executor represented by the input data from the executor definition data stored in the actor definition database storage unit 111. Enter.
The executor change authority determination unit 151 determines whether the operator 812 has change authority based on the input executor definition data using a processing device such as the CPU 911.
If the executor change authority determination unit 151 determines that the user has change authority, the process proceeds to the detailed task definition generation step S26.
When the executor change authority determination unit 151 determines that the user does not have the change authority, the process proceeds to the executor change request notification process S24.

  When the detailed task performer input by the detailed task performer input unit 132 is a subordinate performer of the general task performer, the executor is changed within a range in which the operator 812 has change authority. In this case, there is no problem. However, when the refined task executor after the change is out of the authority range, it is necessary to negotiate with an operator having authority for the executor.

When the summary task is refined and divided into refinement tasks, there are cases in which work to be executed by other performers is included.
For example, it is assumed that there is a general task of “inspecting a purchase order and performing a predetermined work if there is no problem”. As this general task is refined, it becomes necessary to define the processing when there is a problem with the purchase order. If there is a problem with the purchase order, for example, a process of “inquiring the orderer and re-sending the correct purchase order” is performed. As a result, this general task includes an operation to be performed by the “ordering party” that “receives an inquiry from the ordering party and resends a correct purchase order”.
As described above, there are cases where it is desired to change the performer of the detailed task to an unauthorized performer.

In the executor change request notifying step S24, the executor change request notifying unit 161 uses the processing device such as the CPU 911 to input the same executor definition data input by the executor change authority determining unit 151.
The executor change request notifying unit 161 uses a processing device such as the CPU 911 to determine another operator having change authority to change a task executed by the detailed task executor based on the input executor definition data. To do. Here, it is assumed that the operator 813 has change authority.
The executor change request notifying unit 161 notifies the operator 813 that the change of the executor is requested using the display device 901 such as the CRT of the terminal device 200 of the operator 813.

  The operator 813 receives this notification and determines whether or not to approve the change of the executor. This is because if the executor is changed by the unilateral determination of the operator 812, the determination may not be appropriate. If the operator 813 determines that the change request of the performer is appropriate, the operator 813 approves the change.

In the executor change approval / disapproval input step S25, the executor change approval / disapproval input unit 171 inputs executor change approval / disapproval information using an input device such as the keyboard 902 and the mouse 903 of the terminal device 200 of the operator 813.
The executor change approval / disapproval input unit 171 determines whether the operator 813 has approved the change based on the input executor change approval / disapproval information using a processing device such as the CPU 911.
If the executor change approval / disapproval input unit 171 determines that the operator 813 has approved the change, the process proceeds to the detailed task definition generation step S26.
If the executor change consent rejection input unit 171 determines that the operator 813 has rejected the change, the process proceeds to the executor change rejection notification step S27.

In the detailed task definition generation step S26, the detailed task definition generation unit 133 inputs the detailed task definition data stored in the task definition database storage unit 112 in the detailed task input step S21 using a processing device such as the CPU 911. To do.
The detailed task definition generation unit 133 uses the processing device such as the CPU 911 to change the input detailed task definition data, and executes the detailed task performer in the detailed task performer input step S22. Detailed task definition data for the detailed task executor input by the operator input unit 132 is generated.
The detailed task definition generation unit 133 outputs the generated detailed task definition data using a processing device such as the CPU 911.
The task definition database storage unit 112 inputs the detailed task definition data output by the detailed task definition generation unit 133 using a processing device such as the CPU 911.
The task definition database storage unit 112 stores the input detailed task definition data using a processing device such as the CPU 911.
Thereafter, the detailed task setting process ends.

In the executor change refusal notification step S27, the detailed task executor input unit 132 uses the display device 901 such as a CRT of the terminal device 200 of the operator 812 to the operator 812, Notify that the change has been rejected.
Thereafter, the detailed task setting process ends.

Note that if the operator 813 waits for the executor's change to be approved or rejected, the work of the operator 812 cannot proceed, so the detailed task definition generation unit 133 does not wait for the change to be approved. (Tentative) detailed task definition data may be generated. In this case, the detailed task definition generation unit 133 includes data indicating that approval is awaited in the (temporary) detailed task definition data to be generated.
The task definition database storage unit 112 stores the input detailed task definition data separately as temporary task definition data when the input detailed task definition data includes data indicating that it is waiting for approval. Also keep the previous task definition data.
After that, if the change is approved, the task definition database storage unit 112 uses the processing device such as the CPU 911 to remove the temporary task definition data from the temporary task definition data as data indicating that the task is waiting for approval, and sets it as regular task definition data. Delete the task definition data before the change. On the contrary, if the change is rejected, the task definition database storage unit 112 deletes the temporary task definition data using a processing device such as the CPU 911.

  In this way, it is possible to change the detail task performer beyond the authority range of each operator.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The detailed task definition generating unit 133 executes the detailed task when the second operator 812 does not have the authority to change the task executed by the detailed task performer input by the detailed task performer input unit. When the third operator 813 having the authority to change the task executed by the user approves, detailed task definition data is generated using a processing device such as the CPU 911.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when the operator 812 attempts to change the detailed task executor beyond the authority range, the authority for the detailed task executor after the change is determined. When the detailed task definition generation unit 133 generates detailed task definition data upon receiving the approval of the operator 813 having the above, there is an effect that the executor can be changed beyond the authority range.

Embodiment 3 FIG.
Embodiment 3 will be described with reference to FIGS.
Since the configuration, appearance, and hardware resources of the functional block of the workflow generation system 800 in this embodiment are the same as those of the workflow generation system 800 described in the first embodiment, description thereof is omitted here.
In this embodiment, setting / changing of the interface will be described in detail.

FIG. 26 is a detailed block diagram showing an example of a detailed block of the interface creation unit 140 in this embodiment.
Note that blocks common to the detailed blocks of the interface creation unit 140 described in the first embodiment are denoted by the same reference numerals, and description thereof is omitted here.

  The interface creation unit 140 includes an interface input unit 141, an interface change authority determination unit 152, an interface inconsistency warning unit 181, an interface definition generation unit 143, a detailed task flow generation unit 144, a detailed task flow output unit 145, and a work definition document generation unit. 146, a work definition document output unit 147, an interface specification document generation unit 148, and an interface specification document output unit 149.

The interface change authority determination unit 152 inputs data representing the interface output from the interface input unit 141 using a processing device such as the CPU 911.
The interface change authority determination unit 152 obtains an upstream task and a downstream task using a processing device such as the CPU 911 based on the interface represented by the input data.
The two tasks are linked via information in the form that the interface represents. A task that outputs information is called an upstream task, and a task that inputs information is called a downstream task. Therefore, there is always an upstream task and a downstream task in one interface.

The interface change authority determination unit 152 inputs task definition data defining an upstream task from the task definition data stored in the task definition database storage unit 112 using a processing device such as the CPU 911.
The interface change authority determination unit 152 uses a processing device such as the CPU 911 to execute an upstream task executor defined by the input task definition data from the executor definition data stored in the actor definition database storage unit 111. Enter definition data.
The interface change authority determination unit 152 uses a processing device such as the CPU 911 to determine whether the operator 812 who has input the interface has the authority to change the upstream task based on the input executor definition data.

Similarly, the interface change authority determination unit 152 inputs task definition data defining a downstream task from the task definition data stored in the task definition database storage unit 112 using a processing device such as the CPU 911.
The interface change authority determination unit 152 uses a processing device such as the CPU 911 to execute the downstream task executor defined by the input task definition data from the executor definition data stored in the actor definition database storage unit 111. Enter definition data.
The interface change authority determination unit 152 determines whether the operator 812 who has input the interface has the authority to change the downstream task, based on the input executor definition data, using a processing device such as the CPU 911.

When the operator 812 has the authority to change the upstream task, the interface definition generation unit 143 generates interface definition data that defines the downstream interface of the upstream task using a processing device such as the CPU 911.
When the operator 812 has the authority to change the downstream task, the interface definition generation unit 143 generates interface definition data that defines the upstream interface of the downstream task using a processing device such as the CPU 911. .

There is no problem when the operator 812 has the authority to change both the upstream task and the downstream task, but if only one of the authority is changed, interface mismatch occurs. .
If neither change authority is given, the interface input unit 141 does not input an interface. This is realized by the same processing as that of the detailed task input unit 131 described in the second embodiment.

The interface inconsistency warning unit 181 uses the processing device such as the CPU 911 and the interface change authority determination unit 152 determines that the operator 812 has only the right to change either the upstream task or the downstream task. From the task definition data stored in the task definition database storage unit 112, task definition data defining an upstream task and task definition data defining a downstream task are input.
Note that the task definition data for which the operator 812 has change authority is updated with new interface definition data generated by the interface definition generation unit 143. The interface inconsistency warning unit 181 inputs the updated task definition data.

The interface inconsistency warning unit 181 determines whether the downstream interface of the upstream task and the upstream interface of the downstream task are consistent based on the input task definition data using a processing device such as the CPU 911.
This is because even if only one of them is updated, there may be a case where the originally inconsistent one is modified to be consistent.

When it is determined that the interface is inconsistent, the interface inconsistency warning unit 181 defines an upstream task performer from the performer definition data stored in the actor definition database storage unit 111 using a processing device such as the CPU 911. The executed person definition data and the executed person definition data defining the person executing the downstream task are input.
The interface inconsistency warning unit 181 uses a processing device such as the CPU 911 to operate an operator having change authority to change an upstream task and an operation having change authority to change a downstream task based on the input executor definition data. Discriminating the person. One of them is an operator 812 who inputs an interface. The other is an operator 813.
The interface inconsistency warning unit 181 uses the display device 901 such as the CRT of the terminal device 200 of the operator 812 and the operator 813 to warn the operator 812 and the operator 813 that the interface is inconsistent. To do.

As a result, when the operator 812 accidentally changes the interface, an error is noticed by the warning, and it is possible to take measures such as returning to the original state.
Also, if it is necessary to change the interface, the operator 813 notices that the interface has been changed by a warning, and the operator 813 modifies the interface of the task to which the change authority has been changed accordingly. The interface can be matched.

  Next, the operation will be described.

FIG. 27 is a flowchart showing an example of the flow of interface setting processing in which the interface creation unit 140 sets the task interface in this embodiment.
The interface setting process includes an interface input step S31, an interface change authority determination step S32, a first interface definition generation step S33, a second interface definition generation step S34, an interface inconsistency determination step S35, an interface inconsistency warning step S36, and an interface consistency notification. Step S37 is included.

In the interface input step S31, the interface input unit 141 inputs the interface selected by the operator 812 using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200 of the operator 812.
The interface input unit 141 outputs data representing the input interface using a processing device such as the CPU 911.

In the interface change authority determining step S32, the interface change authority determining unit 152 inputs data representing the interface output by the interface input unit 141 in the interface input step S31 using a processing device such as the CPU 911.
The interface change authority determining unit 152 uses a processing device such as the CPU 911 to determine the upstream task and the downstream task of the interface represented by the input data.
The interface change authority determination unit 152 uses a processing device such as the CPU 911 to perform task definition data that defines a determined upstream task and task definition that defines a downstream task from the task definition data stored in the task definition database storage unit 112. Enter the data.
The interface change authority determination unit 152 uses a processing device such as the CPU 911 to execute the executor definition data that defines the executor of the upstream task defined by the input task definition data from the executor definition data stored in the actor definition database storage unit 111. And executor definition data that defines the executor of the downstream task defined by the input task definition data.
The interface change authority determination unit 152 determines whether or not the operator 812 has the authority to change each of the upstream task and the downstream task based on the input executioner definition data using a processing device such as the CPU 911. To do.
If the operator 812 has the change authority to change both the upstream task and the downstream task, if the interface change authority determination unit 152 determines that the operation has changed, the process proceeds to the first interface definition generation step S33.
If the interface change authority determination unit 152 determines that the operator 812 has the change authority to change only one of the upstream task and the downstream task, the process proceeds to the second interface definition generation step S34.

In the first interface definition generation step S33, the interface definition generation unit 143 inputs data representing the interface output from the interface input unit 141 in the interface definition generation step S31 using a processing device such as the CPU 911.
The interface definition generation unit 143 uses a processing device such as the CPU 911 to generate interface definition data that defines the downstream interface of the upstream task and interface definition data that defines the upstream interface of the downstream task based on the input data. To do.
The interface definition generation unit 143 outputs the generated interface definition data using a processing device such as the CPU 911.
The task definition database storage unit 112 inputs the interface definition data output from the interface definition generation unit 143 using a processing device such as the CPU 911.
The task definition database storage unit 112 stores the input interface definition data using a storage device such as the magnetic disk device 920.
Thereafter, the interface setting process is terminated.

In the second interface definition generation step S34, the interface definition generation unit 143 inputs data representing the interface output from the interface input unit 141 in the interface definition generation step S31.
The interface definition generation unit 143 uses a processing device such as the CPU 911, based on input data, interface definition data that defines the downstream interface of the upstream task, and interface definition data that defines the upstream interface of the downstream task. The interface definition data for the task for which the operator 812 has change authority is generated.
The interface definition generation unit 143 outputs the generated interface definition data using a processing device such as the CPU 911.
The task definition database storage unit 112 inputs the interface definition data output from the interface definition generation unit 143 using a processing device such as the CPU 911.
The task definition database storage unit 112 stores the input interface definition data using a storage device such as the magnetic disk device 920.

In the interface inconsistency determining step S35, the interface inconsistency warning unit 181 uses task processing data such as the CPU 911, task definition data that defines an upstream task from the task definition data stored in the task definition database storage unit 112, and downstream Enter the task definition data that defines the task. The task definition data input by the interface mismatch warning unit 181 includes the interface definition data stored in the task definition database storage unit 112 in the second interface definition generation step.
The interface inconsistency warning unit 181 uses a processing device such as the CPU 911 to match the downstream interface of the upstream task with the upstream interface of the downstream task based on the upstream task and the downstream task defined by the input task definition data. It is determined whether or not.
When the interface mismatch warning unit 181 determines that the interface is mismatched, the process proceeds to the interface mismatch warning step S36.
When the interface mismatch warning unit 181 determines that the interface is matched, the process proceeds to the interface matching notification step S37.

In the interface inconsistency warning step S36, the interface inconsistency warning unit 181 uses a processing device such as the CPU 911 to execute an executor that defines the performer of the upstream task from the executor definition data stored in the actor definition database storage unit 111. Input definition data and executor definition data that defines the executor of the downstream task.
The interface inconsistency warning unit 181 uses a processing device such as the CPU 911 to operate an operator having change authority to change an upstream task and an operation having change authority to change a downstream task based on the input executor definition data. Discriminating the person.
The interface mismatch warning unit 181 uses a display device 901 such as a CRT to warn both the determined operators that the interface is mismatched.
Thereafter, the interface setting process is terminated.

In the interface consistency notification step S37, the interface inconsistency warning unit 181 uses a processing device such as the CPU 911 to execute an executor definition that defines the executor of the upstream task from the executor definition data stored in the actor definition database storage unit 111. Input data and executor definition data that defines the executor of the downstream task.
The interface inconsistency warning unit 181 uses a processing device such as the CPU 911 to operate an operator having change authority to change an upstream task and an operation having change authority to change a downstream task based on the input executor definition data. Discriminating the person.
The interface mismatch warning unit 181 uses a display device 901 such as a CRT to notify both identified operators that the interface is matched.

  Since only one of the interfaces was changed to make the interface consistent, it is considered that the interface was inconsistent before the change. Therefore, the interface mismatch warning unit 181 notifies the operator that the interface has been matched, and informs that it is no longer necessary to modify the interface. As a result, it is possible to prevent the operator from misunderstanding that the interface is still inconsistent and further correcting the matched interface to prevent inconsistency.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The interface input unit 141 uses an input device such as a keyboard 902 or a mouse 903 when the second operator 812 has the authority to change the task executed by the refinement task executor that executes the refinement task. And inputting an upstream interface and a downstream interface.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when the operator 812 does not have the authority to change the interface, the interface cannot be input. The effect is clear.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The interface mismatch warning unit 181 uses a processing device such as the CPU 911 to determine whether or not the interface is matched. When the interface mismatch is determined to be mismatched, the display device 901 (output device) such as a CRT is determined. ) Is used to warn the operator that the interface is inconsistent.

  According to the workflow generation system 800 in this embodiment, when the interface is inconsistent, the interface inconsistency warning unit 181 warns, so that the interface inconsistency can be easily found and a consistent workflow can be generated. There is an effect that can be.

Embodiment 4 FIG.
The fourth embodiment will be described with reference to FIGS.
Since the configuration, appearance, and hardware resources of the functional block of the workflow generation system 800 in this embodiment are the same as those of the workflow generation system 800 described in the first embodiment, description thereof is omitted here.

FIG. 28 is a detailed block diagram showing an example of a detailed block configuration of the interface creation unit 140 in this embodiment.
Note that blocks common to the detailed blocks of the interface creation unit 140 described in the third embodiment are denoted by the same reference numerals, and description thereof is omitted here.

  The interface creation unit 140 includes an interface input unit 141, an interface change authority determination unit 152, an interface change request notification unit 162, an interface change acceptance / rejection input unit 172, an interface definition generation unit 143, a detailed task flow generation unit 144, and a detailed task flow output unit. 145, a work definition document generation unit 146, a work definition document output unit 147, an interface specification document generation unit 148, and an interface specification document output unit 149.

  The interface change request notifying unit 162 displays a display device such as a CRT when the interface change authority determining unit 152 determines that the operator 812 has only one of the upstream task and the downstream task. 901 is used to notify the other operator who has the authority to change the other task to request the interface change approval.

The interface change approval / disapproval input unit 172 uses the input device such as the keyboard 902 and the mouse 903 of the terminal device 200 of the operator who has notified that the interface change request notification unit 162 requests the approval of the interface change. Enter information.
The interface change approval / disapproval information is information indicating whether or not the operator who has notified that the interface change request notifying unit 162 requests the approval of the interface change has approved the interface change.
The interface change approval / disapproval input unit 172 determines whether the input interface change approval / disapproval information represents change approval or change rejection using a processing device such as the CPU 911.

When the interface change authority determination unit 152 determines that the operator 812 has a change authority to change both the upstream task and the downstream task, the interface definition generation unit 143 defines an interface that defines the downstream interface of the upstream task. Definition data and interface definition data that defines an upstream interface of a downstream task are generated.
When the interface change authority determination unit 152 determines that the operator 812 has only one of the upstream task and the downstream task, the interface definition generation unit 143 determines that the interface change permission / inhibition input unit 172 Wait for input of interface change permission / inhibition information. When the interface change approval / disapproval input unit 172 determines that the change is approved, the interface definition data that defines the downstream interface of the upstream task and the interface definition data that defines the upstream interface of the downstream task are generated.
When the interface change approval / denial input unit 172 determines that the change is rejected, the interface definition generation unit 143 displays not only the interface definition data of the task for which the operator 812 does not have the change authority but also the interface definition data of the task having the change authority Is not generated.
This keeps the interface consistent.

FIG. 29 is a flowchart showing an example of the flow of interface setting processing in which the interface creation unit 140 sets an interface in this embodiment.
Note that steps common to the interface setting processing steps described in the third embodiment are denoted by the same reference numerals, and description thereof is omitted here.

  The interface setting process includes an interface input step S31, an interface change authority determination step S32, an interface change request notification step S38, an interface change acceptance / rejection input step S39, a first interface definition generation step S33, and an interface change rejection notification step S40.

  If the interface change authority determining unit 152 determines that the operator 812 has the change authority to change only one of the upstream task and the downstream task in the interface change authority determining step S32, the process proceeds to the interface change request notifying step S38. .

In the interface change request notifying step S38, the interface change request notifying unit 162 uses the display device 901 such as a CRT to request another operator having the authority to change the other task to approve the interface change. Notify you.
When the other operator determines that the interface change is appropriate, it approves the interface change.

In the interface change permission / inhibition input step S39, the interface change permission / inhibition input unit 172 inputs interface change permission / inhibition information using an input device such as a keyboard 902 or a mouse 903.
The interface change approval / disapproval input unit 172 uses a processing device such as the CPU 911 to determine whether another operator has approved the interface change.
When the interface change acceptance / rejection input unit 172 determines that another operator has approved the change of the interface, the process proceeds to the first interface definition generation step S33.
When the interface change acceptance / rejection input unit 172 determines that another operator has refused to change the interface, the process proceeds to the interface change rejection notification step S40.

In the interface change rejection notification step S40, the interface input unit 141 notifies the operator 812 that the interface change has been rejected using the display device 901 such as the CRT of the terminal device 200 of the operator 812. .
Thereafter, the interface setting process is terminated.

Note that if the other operator is waiting for the interface change to be approved or rejected, the operation of the operator 812 cannot proceed, so the interface definition generation unit 143 does not wait for the change to be approved (provisional). Interface definition data). In this case, the interface definition generation unit 143 includes data indicating that it is waiting for approval in the (temporary) interface definition data to be generated.
The task definition database storage unit 112 stores task definition data including the input interface definition data separately as temporary task definition data when the input interface definition data includes data indicating that it is waiting for approval. Also keep the detailed task definition data including the interface definition data before the change.
After that, if the change is approved, the task definition database storage unit 112 uses the processing device such as the CPU 911 to remove the temporary task definition data from the temporary task definition data as data indicating that the task is waiting for approval, and sets it as regular task definition data. Delete the task definition data before the change. On the contrary, if the change is rejected, the task definition database storage unit 112 deletes the temporary task definition data using a processing device such as the CPU 911.

  In this way, when an operator with change authority changes the interface between different tasks, the interface is changed after obtaining the approval of the operator with change authority of the other task, so temporarily, It is possible to prevent the occurrence of interface mismatch. Therefore, it is possible to prevent a situation in which it is determined that a workflow including an inconsistent interface has been mistakenly completed and the operation is started. Further, even if the details are corrected while the workflow is operated, inconsistency due to the correction timing does not occur.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The interface definition generation unit 143 is executed by another refinement task executor who executes another refinement task (downstream task) that inputs information output from the refinement task (upstream task) from the refinement task (upstream task). When the second operator 812 does not have the authority to change the task to be performed, or when the third operator having the authority to change the task executed by another detailed task performer approves, the processing of the CPU 911 or the like The interface definition data is generated using a device.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when the operator 812 does not have the authority to change the downstream task, the interface is obtained with the approval of another operator who has the authority to change the downstream task. Since the definition generation unit 143 generates the interface definition data, it is possible to prevent the interface from becoming inconsistent by correcting only one of the interfaces.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The interface definition generation unit 143 executes other detail task (upstream task) that outputs information input by the detail task (downstream task) to the detail task (downstream task). When the second operator 812 does not have the authority to change the task executed by the CPU, and when the third operator who has the authority to change the task executed by the other detailed task performer approves, the CPU 911 The interface definition data is generated using a processing device such as the above.

  According to the workflow generation system 800 (workflow generation device) in this embodiment, when the operator 812 does not have the authority to change the upstream task, the interface is obtained with the approval of another operator who has the authority to change the upstream task. Since the definition generation unit 143 generates the interface definition data, it is possible to prevent the interface from becoming inconsistent by correcting only one of the interfaces.

Embodiment 5 FIG.
The fifth embodiment will be described with reference to FIGS.
Since the appearance and hardware resources of the workflow generation system 800 in this embodiment are the same as those described in the first embodiment, description thereof is omitted here.

FIG. 30 is a block configuration diagram illustrating an example of a functional block configuration of the workflow generation system 800 according to this embodiment.
It should be noted that blocks common to the functional blocks of the workflow generation system 800 described in the first to fourth embodiments are denoted by the same reference numerals and description thereof is omitted here.

  The workflow generation system 800 includes an executor definition storage unit 311, a task definition storage unit 312, a task definition change input unit 320, a task definition change unit 330, a task definition change authority determination unit 350, a task definition change request notification unit 360, a task definition. A change acceptance / rejection input unit 370, an interface mismatch warning unit 181, a workflow diagram generation unit 380, and a workflow diagram output unit 390 are included.

  The executor definition storage unit 311 stores executor definition data using a storage device such as the magnetic disk device 920. The executor definition storage unit 311 is an example of an actor definition database storage unit.

FIG. 31 is a diagram illustrating an example of the performer definition data 510 stored in the performer definition storage unit 311 according to this embodiment.
The executor definition storage unit 311 stores a plurality of executor definition data 510.

  In the executor definition data 510, the “ID” column is an executor identifier. The executor identifier is data for the workflow generation system 800 to identify the executor. The executor identifier is used to indicate an executor who executes the task in the task definition data, for example.

  The “Name” column is an executor name. The executor name is the name of the executor. The executor name is data for the operator of the workflow generation system 800 to identify the executor. The executor name is used, for example, in order to display the executor who executes the task in the detailed task flow diagram. An executor name may be used as an executor identifier.

  The “BelongTo” column is an upper-level performer identifier. When a certain executor is a lower executor of another executor, the executor identifier of the higher executor is indicated. In this example, it is indicated that the performer “communication system” and the performer “power supply system” are subordinate performers of the “system design section”.

The “Change Authority ID” column is a change authority identifier. The change authority identifier indicates an operator who has the authority to change the contents of a task assigned to be executed by the executor. The change authority identifier is, for example, a login name of an operator having change authority.
Note that one operator may have change authority for a plurality of performers, or different operators may have change authority for performers below a certain performer.

  Further, the format of the performer definition data 510 may be, for example, an XML (Extensible Markup Language) format or a database format.

  Returning to FIG. 30, the description of the functional blocks of the workflow generation system 800 will be continued.

  The task definition storage unit 312 stores task definition data using a storage device such as the magnetic disk device 920. The task definition storage unit 312 is an example of a task definition database storage unit.

FIG. 32 is a diagram showing an example of task definition data 520 stored in the task definition storage unit 312 in this embodiment.
The task definition storage unit 312 stores a plurality of task definition data 520.

  In the task definition data 520, the “ID” column is task identification data. The task identification data is data for the workflow generation system 800 to identify a task. The task identification data is used, for example, to indicate a detailed task, an upstream task, a downstream task, etc. of the task in the task definition data.

  The “Work” column is task hierarchy data. The task hierarchy data indicates whether the task is a general task or a detailed task. For example, if the “Work” field is “Non”, a general task is indicated, and if “Yes”, a detailed task is indicated.

  The “Name” column is a task name. The task name is the name of the task. The task name is data for the operator of the workflow generation system 800 to identify the task. For example, the task name is used as a label of the task in the detailed task flow diagram, or as an item name of the task in the work definition document.

  The “Def” column is a task description. The task description is text data that describes the work content of the task. The task description is used, for example, by pasting it in the work content column in the work definition document.

  The “SubTask” column is detailed task data. The detailed task data is data indicating a detailed task in which the task is detailed. The detailed task data is task identification data of the detailed task. When there are a plurality of detailed tasks, a plurality of task identification data are arranged separated by “,”.

  The “BelongTo” column is general task data. The general task data is data indicating the original general task in the task definition data defining the detailed task, contrary to the detailed task data. The general task data is task identification data of the general task.

  The “UpperTask1” column is upstream task data. The upstream task data is data indicating the upstream task of the task. The upstream task here is another task that outputs information input by the task to the task. The upstream task data is task identification data of the upstream task. If the upstream task is a detailed task, the task identification data of the general task + “/” + the task identification data of the detailed task is used. When there are a plurality of upstream tasks, a plurality of columns such as an “UpperTask2” column, an “UpperTask3” column,... Are provided.

  The “UpperTask1_IFData” column is the upstream interface data. The upstream interface data is data indicating the format of information that the task inputs from the upstream task. The upstream interface data is, for example, the file name of a file that defines the information format. When there are a plurality of upstream tasks, a plurality of columns are provided such as an “UpperTask2_IFData” column, an “UpperTask3_IFData” column, and so on. In this case, the “UpperTask1_IFData” column indicates the format of information input from the upstream task indicated by the “UpperTask1” column. The “UpperTask2_IFData” column indicates the format of information input from the upstream task indicated by the “UpperTask2” column. As described above, the upstream task data and the upstream interface data correspond to each other.

  The “Lower Task 1” column is downstream task data. The downstream task data is data indicating the downstream task of the task. The downstream task here is another task that inputs information output from the task from the task. Downstream task data is task identification data of a downstream task. If the downstream task is a detailed task, the task identification data of the general task + “/” + the task identification data of the detailed task is used. Further, when there are a plurality of downstream tasks, a plurality of columns are provided such as a “Lower Task 2” column, a “Lower Task 3” column,.

  The “Lower Task 1_IFData” column is downstream interface data. The downstream interface data is data indicating the format of information that the task outputs to the downstream task. The downstream interface data is, for example, the file name of a file that defines the information format. When there are a plurality of downstream tasks, a plurality of columns are provided such as a “LowerTask2_IFData” column, a “LowerTask3_IFData” column, and so on. In this case, the “Lower Task 1_IFData” column indicates the format of information output to the downstream task indicated by the “Lower Task 1” column. The “LowerTask2_IFData” column indicates the format of information output to the downstream task indicated by the “LowerTask2” column. As described above, the downstream task data and the downstream interface data correspond to each other.

  The “Actor” column is task performer data. The task executor data is data indicating an executor who executes the task. The task executor data is an executor identifier of the executor.

  The “Subactor” column is performer data of the detailed task. This column indicates the performer of the detailed task when the performer of the detailed task that has refined the task is different from the performer of the task. If there are multiple performers of the refinement task, the performer identifiers of each performer are arranged separated by “,”.

  The “Change Authority” column is data for permission change permission / inhibition. The surrender permission changeability data means that even if the operator who has the authority to change the task executed by the person who executes the task does not have the authority to change the task executed by the person who executes the detailed task that details the task Indicates whether it can be changed without approval. For example, if the “Change Authority” column is “Yes”, it indicates that the change can be made without obtaining approval, and if it is “Non”, it indicates that the change authority needs to be approved. As a general rule, changes outside the change authority need to be approved by the change authority, but if you ask for approval in too much detail, the entire work may be delayed. The approval at the time of change is omitted.

  Returning to FIG. 30, the description of the functional blocks of the workflow generation system 800 will be continued.

The task definition change input unit 320 uses the input device such as the keyboard 902 or the mouse 903 of the terminal device 200 to input an operation on the workflow by the operator. The operation on the workflow input by the task definition change input unit 320 is, for example, detailing a task constituting the workflow or adding a task to the workflow. That is, this is an operation for instructing a change of task definition data for defining a task. The task definition change input unit 320 inputs task definition change instruction information indicating that the operator has instructed to change task definition data.
The task definition change input unit 320 includes a selected task input unit 321, a task detailing input unit 322, a task addition input unit 323, an executor change input unit 324, an upstream interface change input unit 325, and a downstream interface change input unit 326.

The selection task input unit 321 inputs a selection task using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200. The selected task is a task selected by the operator from the tasks constituting the workflow.
The operator, for example, a task that is to change the task definition in the detailed task flow diagram generated by the detailed task flow generation unit 144 and displayed on the display device 901 such as the CRT of the terminal device 200 by the detailed task flow output unit 145. Click on the rectangle that represents. The selected task input unit 321 inputs a task selected by the operator by inputting this operation.
The selected task input unit 321 may determine whether or not the operator has the authority to change the task selected by the operator, and may not select a task that does not have the authority to change.
The selected task input unit 321 outputs data indicating the selected task using a processing device such as the CPU 911. For example, the selected task input unit 321 outputs task identification data of the selected task.
The selected task input by the selected task input unit 321 is displayed so that it can be distinguished from other tasks, for example, by changing the color in the detailed task flow diagram generated by the detailed task flow generating unit 144. Notify that the task has been selected. Alternatively, possible operations for the task may be displayed in a menu format or the like.

The task detailing input unit 322 inputs task detailing instruction information using an input device such as the keyboard 902 and the mouse 903 of the terminal device 200. The task detailing instruction information is information indicating that the operator has instructed to refine the selected task input by the selected task input unit 321. The task detailing instruction information is an example of task definition change instruction information.
For example, the operator performs an operation of selecting “detail” from a menu displayed after performing an operation of selecting a task. The task detailing input unit 322 inputs task detailing instruction information by inputting this operation.

The task addition input unit 323 inputs task addition instruction information using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200. The task addition instruction information is information indicating that the operator has instructed to add a task after (downstream) the selected task input by the selected task input unit 321, for example. The position of the task to be added may be before (upstream) the selected task, or may be parallel to the selected task. The task addition instruction information is an example of task definition change instruction information. The task addition instruction information includes information indicating the position of the task to be added.
For example, the operator performs an operation of selecting “add” from a menu displayed after performing an operation of selecting a task. The task addition input unit 323 inputs task addition instruction information by inputting this operation.

The executor change input unit 324 inputs executor change instruction information using an input device such as the keyboard 902 and the mouse 903 of the terminal device 200. The executor change instruction information is information indicating that the operator has instructed to change the executor of the selected task input by the selected task input unit 321 to another executor. The executor change instruction information is an example of task definition change instruction information. The executor change instruction information includes information indicating the executor after the change.
The operator, for example, performs an operation of selecting a task and then dragging and dropping the selected task onto an area representing another executor in the detailed task flow diagram. The executor change input unit 324 inputs executor change instruction information by inputting this operation.

The upstream interface change input unit 325 inputs upstream interface change instruction information using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200. The upstream interface change instruction information is information indicating that the operator has instructed to change the format (upstream interface) of information input by the selected task input by the selected task input unit 321. The upstream interface change instruction information is an example of task definition change instruction information. The upstream interface change instruction information includes data indicating the changed upstream interface.
For example, the operator performs an operation of selecting “upstream interface change” from a menu displayed after performing an operation of selecting a task. The upstream interface change input unit 325 inputs this operation and displays a list of interfaces using a display device 901 such as a CRT of the terminal device 200. The operator performs an operation of selecting the changed upstream interface from the displayed list. The upstream interface change input unit 325 inputs upstream interface change instruction information by inputting this operation.

The downstream interface change input unit 326 inputs downstream interface change instruction information using an input device such as the keyboard 902 and the mouse 903 of the terminal device 200. The downstream interface change instruction information is information indicating that the operator has instructed to change the format (downstream interface) of the information output by the selected task input by the selected task input unit 321. The downstream interface change instruction information is an example of task definition change instruction information. The downstream interface change instruction information includes data indicating the changed downstream interface.
For example, the operator performs an operation of selecting “change downstream interface” from a menu displayed after performing an operation of selecting a task. The downstream interface change input unit 326 inputs this operation, and displays a list of interfaces using the display device 901 such as the CRT of the terminal device 200. The operator performs an operation of selecting the changed downstream interface from the displayed list. The downstream interface change input unit 326 inputs the downstream interface change instruction information by inputting this operation.

The task definition change authority determination unit 350 determines whether or not the content instructed by the operator based on the task definition change instruction information input by the task definition change input unit 320 is within the authority range of the operator.
The task definition change authority determination unit 350 includes an executor change authority determination unit 151 and an interface change authority determination unit 152.

For example, when the operator has the authority to change the general task, the operator has the authority to refine the general task. Therefore, when the task definition change instruction information input by the task definition change input unit 320 is task detailing instruction information, the task definition change authority determination unit 350 determines that the user has change authority.
In addition, when an operator has a change authority to change a task executed by an executor of a certain task, the operator has an authority to add a task executed by the same executor before and after the task. Therefore, even when the task definition change instruction information input by the task definition change input unit 320 is task addition instruction information, the task definition change authority determination unit 350 determines that the task has change authority.

On the other hand, when the task definition change instruction information input by the task definition change input unit 320 is the executor change instruction information, the operator has change authority to change the task executed by the executor before the change. Even if it does, it does not necessarily have the change authority which changes the task which the performer after a change performs.
Further, when the task definition change instruction information input by the task definition change input unit 320 is upstream interface change instruction information or downstream interface change instruction information, the operator has a change authority to change the upstream task or the downstream task. Not necessarily.

  Therefore, when the task definition change instruction information input by the task definition change input unit 320 is the executor change instruction information, the executor change authority determination unit 151 changes the task executed by the changed executor. It is determined whether or not the operator has.

  Further, the interface change authority determining unit 152 changes the upstream task or the downstream task when the task definition change instruction information input by the task definition change input unit 320 is the upstream interface change instruction information or the downstream interface change instruction information. It is determined whether or not the operator has authority.

The task definition change request notifying unit 360 uses the display device 901 such as the CRT of the terminal device 200 when the task definition change authority determining unit 350 determines that the operator does not have the change authority. Is notified that change approval is requested.
The task definition change request notification unit 360 includes an executor change request notification unit 161 and an interface change request notification unit 162.

  The executor change request notifying unit 161 determines the CRT of the terminal device 200 when the executor change authority determining unit 151 determines that the operator does not have change authority to change the task executed by the changed executor. The display device 901 is used to notify the other operator who has the change authority to change the task executed by the changed executor to request approval of the executor's change.

  The interface change request notification unit 162 displays the display device 901 such as the CRT of the terminal device 200 when the interface change authority determination unit 152 determines that the operator does not have change authority to change the upstream task or the downstream task. To notify other operators having change authority to change the upstream task or the downstream task that the approval of the interface change is requested.

The task definition change acceptance / rejection input unit 370 inputs task definition change acceptance / rejection information using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200. The task definition change approval / disapproval information is information indicating whether or not another operator who has notified the task definition change request notifying unit 360 of requesting approval of the change approves the change.
The task definition change approval / disapproval input unit 370 includes an executor change approval / disapproval input unit 171 and an interface change approval / disapproval input unit 172.

  The executor change approval / disapproval input unit 171 inputs executor change approval / disapproval information using an input device such as the keyboard 902 and the mouse 903 of the terminal device 200. The executor change approval / disapproval information is information indicating whether or not another operator notified by the executor change request notifying unit 161 to approve the change of the executor approves the change of the executor. . The executor change acceptance / rejection information is an example of task definition change acceptance / rejection information.

  The interface change permission / inhibition input unit 172 inputs interface change permission / inhibition information using an input device such as the keyboard 902 and the mouse 903 of the terminal device 200. The interface change approval / disapproval information is information indicating whether another operator who has notified the interface change request notifying unit 162 of requesting the interface change approval approves the interface change. The interface change acceptance / rejection information is an example of task definition change acceptance / rejection information.

Note that the task definition change approval / disapproval information may indicate “partially corrected and approved” instead of “approval” or “reject”.
In this case, for example, the task definition change request notifying unit 360 uses the display device 901 such as the CRT of the terminal device 200 to notify the operator who has input the task definition change instruction information of the partially modified content. To do. The task definition change acceptance / rejection input unit 370 inputs information indicating whether or not the operator who has input the task definition change instruction information approves the partially modified change content. Similarly, in this case, “Approve” after “Reject” may be indicated in addition to “Approve” and “Reject”.
In this way, the change is approved if an agreement is formed between them.

The task definition changing unit 330 changes the task definition data stored in the task definition storage unit 312 using a processing device such as the CPU 911.
There are two cases when the task definition changing unit 330 changes the task definition data.
One is a case where the task definition change authority determination unit 350 determines that the operator has the change authority.
The other is a case where the task definition change authority determining unit 350 determines that the operator has no change authority, and the task definition change approval / disapproval information input by the task definition change approval / disapproval input unit 370 indicates approval of the change.

  The task definition changing unit 330 includes a selected task definition acquiring unit 331, an upstream task definition acquiring unit 332, a downstream task definition acquiring unit 333, a general task definition acquiring unit 338, a selected task definition changing unit 341, an upstream task definition changing unit 342, and a downstream. A task definition changing unit 343, an executor changing unit 344, an upstream interface changing unit 345, a downstream interface changing unit 346, a new task definition generating unit 347, and a general task definition changing unit 348 are provided.

The selected task definition acquisition unit 331 inputs task definition data defining the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 using a processing device such as the CPU 911.
The selected task definition acquisition unit 331 outputs the input task definition data as selected task definition data using a processing device such as the CPU 911.

The upstream task definition acquisition unit 332 uses a processing device such as the CPU 911 to extract task definition data that defines the upstream task of the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312. input.
The upstream task definition acquisition unit 332 outputs the input task definition data as upstream task definition data using a processing device such as the CPU 911.
The upstream task definition acquisition unit 332 outputs the upstream task definition data, for example, when the task definition change instruction information input by the task definition change input unit 320 is upstream interface change instruction information.

The downstream task definition acquisition unit 333 uses a processing device such as the CPU 911 to extract task definition data that defines the downstream task of the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312. input.
The downstream task definition acquisition unit 333 outputs the input task definition data as downstream task definition data using a processing device such as the CPU 911.
The downstream task definition acquisition unit 333 outputs the downstream task definition data, for example, when the task definition change instruction information input by the task definition change input unit 320 is downstream interface change instruction information.

When the selected task input by the selected task input unit 321 is a refinement task, the general task definition acquisition unit 338 uses a processing device such as the CPU 911 to obtain details from the task definition data stored in the task definition storage unit 312. Enter the task data that defines the general task that is the original task.
The general task definition acquisition unit 338 outputs the input task definition data as general task definition data using a processing device such as the CPU 911.

The selected task definition changing unit 341 inputs the selected task definition data output from the selected task definition acquiring unit 331 using a processing device such as the CPU 911.
The selected task definition changing unit 341 uses the processing device such as the CPU 911 to change the input selected task definition data based on the task definition change instruction information input by the task definition change input unit 320.
The selected task definition changing unit 341 outputs the changed selected task definition data as changed task definition data using a processing device such as the CPU 911.

The upstream task definition change unit 342 inputs the upstream task definition data output from the upstream task definition acquisition unit 332 using a processing device such as the CPU 911.
The upstream task definition changing unit 342 uses the processing device such as the CPU 911 to change the input upstream task definition data based on the task definition change instruction information input by the task definition change input unit 320.
The upstream task definition changing unit 342 outputs the changed upstream task definition data as changed task definition data using a processing device such as the CPU 911.

The downstream task definition change unit 343 inputs the downstream task definition data output from the downstream task definition acquisition unit 333 using a processing device such as the CPU 911.
The downstream task definition change unit 343 uses the processing device such as the CPU 911 to change the input downstream task definition data based on the task definition change instruction information input by the task definition change input unit 320.
The downstream task definition changing unit 343 outputs the changed downstream task definition data as changed task definition data using a processing device such as the CPU 911.

The executor change unit 344 outputs the selected task definition acquisition unit 331 when the task definition change instruction information input by the task definition change input unit 320 is the executor change instruction information using a processing device such as the CPU 911. Enter the selected task definition data.
The executor changing unit 344 changes task executor data in the selected selected task definition data based on the executor change instruction information using a processing device such as the CPU 911.
The executor changing unit 344 outputs the selected task definition data obtained by changing the task executor data as changed task definition data using a processing device such as the CPU 911.

The upstream interface change unit 345 outputs the selected task definition acquisition unit 331 when the task definition change instruction information input by the task definition change input unit 320 is the upstream interface change instruction information using a processing device such as the CPU 911. The selected task definition data and the upstream task definition data output by the upstream task definition acquisition unit 332 are input.
The upstream interface changing unit 345 uses the processing device such as the CPU 911 to change the upstream interface data in the selected selected task definition data based on the upstream interface change instruction information.
If the selected task definition data includes a plurality of upstream interface data, the upstream interface data corresponding to the upstream task data indicating the upstream task defined by the upstream task definition data is changed.
The upstream interface changing unit 345 uses a processing device such as the CPU 911 to change the downstream interface data in the input upstream task definition data based on the upstream interface change instruction information.
When the upstream task definition data includes a plurality of downstream interface data, the downstream interface data corresponding to the downstream task data indicating the selected task defined by the selected task definition data is changed.
The upstream interface changing unit 345 outputs the changed selected task definition data and the upstream task definition data as changed task definition data using a processing device such as the CPU 911.

The downstream interface change unit 346 outputs the selected task definition acquisition unit 331 when the task definition change instruction information input by the task definition change input unit 320 is the downstream interface change instruction information using a processing device such as the CPU 911. The selected task definition data and the downstream task definition data output by the downstream task definition acquisition unit 333 are input.
The downstream interface changing unit 346 uses the processing device such as the CPU 911 to change the downstream interface data in the selected selected task definition data based on the downstream interface change instruction information.
If the selected task definition data includes a plurality of downstream interface data, the downstream interface data corresponding to the downstream task data indicating the downstream task defined by the downstream task definition data is changed.
The downstream interface changing unit 346 uses the processing device such as the CPU 911 to change the upstream interface data in the input downstream task definition data based on the downstream interface change instruction information.
If the downstream task definition data includes a plurality of upstream interface data, the upstream interface data corresponding to the upstream task data indicating the selected task defined by the selected task definition data is changed.
The downstream interface changing unit 346 outputs the changed selected task definition data and downstream task definition data as changed task definition data using a processing device such as the CPU 911.

The new task definition generation unit 347 generates task definition data for defining a new task based on the task definition change instruction information input by the task definition change input unit 320 using a processing device such as the CPU 911, and creates a new task definition data. Use task definition data. .
For example, the new task definition generation unit 347 generates task identification data for identifying a new task by using a processing device such as the CPU 911 and sets it as new task identification data. The new task definition generation unit 347 generates task definition data including the generated new task identification data as task identification data using a processing device such as the CPU 911.
The new task definition generation unit 347 outputs the generated new task definition data as changed task definition data using a processing device such as the CPU 911.

The general task definition change unit 348 inputs the general task definition data output from the general task definition acquisition unit 338 using a processing device such as the CPU 911.
The general task definition change unit 348 changes the input general task definition data based on the task definition change instruction information input by the task definition change input unit 320 using a processing device such as the CPU 911.
The general task definition changing unit 348 outputs the changed general task definition data as changed task definition data using a processing device such as the CPU 911.

The task definition storage unit 312 receives the changed task definition data output from the task definition changing unit 330 using a processing device such as the CPU 911.
The task definition storage unit 312 stores the input changed task definition data as task definition data using a storage device such as the magnetic disk device 920.

The workflow diagram generation unit 380 generates a workflow diagram based on the task definition data stored in the task definition storage unit 312 and the ten ward company definition data stored in the executor definition storage unit 311 using a processing device such as the CPU 911. To do. A workflow diagram is a chart describing a workflow, such as an overall work flow diagram or a detailed task flow diagram.
The workflow diagram generation unit 380 includes an overall workflow generation unit 124, a general task flow generation unit 126, a detailed workflow generation unit 134, and a detailed task flow generation unit 144.

The workflow diagram generation unit 380 inputs task definition data stored in the task definition storage unit 312 and executor definition data stored in the executor definition storage unit 311 using a processing device such as the CPU 911.
The workflow diagram generation unit 380 uses a processing device such as the CPU 911 to generate a workflow diagram based on the input task definition data and executor definition data.
The workflow diagram generation unit 380 outputs data representing the generated workflow diagram using a processing device such as the CPU 911.

The workflow diagram output unit 390 outputs the workflow diagram generated by the workflow diagram generation unit 380 using an output device such as a display device 901 such as a CRT of the terminal device 200 or a printer device 906.
The workflow diagram output unit 390 includes an overall workflow output unit 125, a general task flow output unit 127, a detailed workflow output unit 135, and a detailed task flow output unit 145.

The workflow diagram output unit 390 inputs data representing the workflow diagram output by the workflow diagram generation unit 380 using a processing device such as the CPU 911.
The workflow diagram output unit 390 uses a display device 901 such as a CRT of the terminal device 200 and an output device such as the printer device 906 to output a workflow diagram represented by the input data.

  Next, the operation will be described.

FIG. 33 is a flowchart showing an example of a task detailing process in which the task definition changing unit 330 refines a task in this embodiment.
The task detailing process is a process when the task definition change instruction information input by the task definition change input unit 320 is task detailing instruction information.

  The task detailing process includes selected task definition acquisition step S41, upstream task definition acquisition step S42, downstream task definition acquisition step S43, new task definition generation step S44, selected task definition change step S45, upstream task definition change step S46, downstream task. It has a definition changing step S47 and a changed task definition storing step S48.

In the selected task definition acquisition step S41, the selected task definition acquisition unit 331 uses a processing device such as the CPU 911 to define the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312. Enter the selected task definition data.
The selected task definition acquisition unit 331 outputs the input selected task definition data using a processing device such as the CPU 911.

The task detailing input unit 322 inputs task detailing instruction information by inputting an operation of the operator 812 using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200.
The task detail input unit 322 outputs the input task detail instruction information using a processing device such as the CPU 911.

In the upstream task definition acquisition step S42, the upstream task definition acquisition unit 332 inputs the selected task definition data output by the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The upstream task definition acquisition unit 332 determines the upstream task of the selected task based on the upstream task data included in the input selected task definition data using a processing device such as the CPU 911.
The upstream task definition acquisition unit 332 inputs upstream task definition data that defines the determined upstream task from the task definition data stored in the task definition storage unit 312 using a processing device such as the CPU 911.
The upstream task definition acquisition unit 332 outputs the input upstream task definition data using a processing device such as the CPU 911.

In the downstream task definition acquisition step S43, the downstream task definition acquisition unit 333 inputs the selected task definition data output by the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The downstream task definition acquisition unit 333 determines a downstream task of the selected task based on the downstream task data included in the input selected task definition data using a processing device such as the CPU 911.
The downstream task definition acquisition unit 333 inputs downstream task definition data that defines the determined downstream task from the task definition data stored in the task definition storage unit 312 using a processing device such as the CPU 911.
The downstream task definition acquisition unit 333 outputs the input downstream task definition data using a processing device such as the CPU 911.

In the new task definition generation step S44, the new task definition generation unit 347 inputs the selected task definition data output from the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The new task definition generation unit 347 generates task identification data for identifying a new task by using a processing device such as the CPU 911 and sets it as new task identification data.
The new task definition generation unit 347 generates task definition data for defining a new task by using a processing device such as the CPU 911 and sets it as new task definition data.
The new task definition generation unit 347 outputs the generated new task identification data and the generated new task definition data using a processing device such as the CPU 911.

The new task definition data generated by the new task definition generation unit 347 includes the following data.
The task identification data included in the new task definition data is the generated new task identification data.
The upstream task data included in the new task definition data is the upstream task data included in the input selected task definition data.
The upstream interface data included in the new task definition data is the upstream interface data included in the input selected task definition data.
The downstream task data included in the new task definition data is downstream task data included in the input selected task definition data.
The downstream interface data included in the new task definition data is downstream interface data included in the input selected task definition data.
The task performer data included in the new task definition data is task performer data included in the input selected task definition data.

In the selected task definition changing step S45, the selected task definition changing unit 341 inputs the selected task definition data output from the selected task definition acquiring unit 331 in the selected task definition acquiring step S41 using a processing device such as the CPU 911.
The selected task definition changing unit 341 inputs new task identification data output by the new task definition generating unit 347 in the new task definition generating step S44 using a processing device such as the CPU 911.
The selected task definition changing unit 341 uses the processing device such as the CPU 911 to change the detailed task data in the input selection task definition data to include the input new task identification data.
The selected task definition changing unit 341 outputs the changed selected task definition data using a processing device such as the CPU 911.

In the upstream task definition changing step S46, the upstream task definition changing unit 342 inputs the upstream task definition data output by the upstream task definition acquiring unit 332 in the upstream task definition acquiring step S42 using a processing device such as the CPU 911.
The upstream task definition changing unit 342 inputs new task identification data output by the new task definition generating unit 347 in the new task definition generating step S44 using a processing device such as the CPU 911.
The upstream task definition changing unit 342 uses the processing device such as the CPU 911 to input the new task identification data that is the same as the task identification data of the selected task among the downstream task data included in the input upstream task definition data. Change to
The upstream task definition changing unit 342 outputs the changed upstream task definition data using a processing device such as the CPU 911.

In the downstream task definition changing step S47, the downstream task definition changing unit 343 inputs the downstream task definition data output by the downstream task definition acquiring unit 333 in the downstream task definition acquiring step S43 using a processing device such as the CPU 911.
The downstream task definition changing unit 343 inputs new task identification data output by the new task definition generating unit 347 in the new task definition generating step S44 using a processing device such as the CPU 911.
The downstream task definition changing unit 343 uses the processing device such as the CPU 911 to input new task identification data that is the same as the task identification data of the selected task among the upstream task data included in the input downstream task definition data. Change to data containing
The downstream task definition changing unit 343 outputs the changed downstream task definition data using a processing device such as the CPU 911.

In the changed task definition storage step S48, the task definition storage unit 312 inputs new task definition data output by the new task definition generation unit 347 in the new task definition generation step S44 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the selected task definition data output from the selected task definition changing unit 341 in the selected task definition changing step S45 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the upstream task definition data output by the upstream task definition change unit 342 in the upstream task definition change step S46 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the downstream task definition data output by the downstream task definition change unit 343 in the downstream task definition change step S47 using a processing device such as the CPU 911.
The task definition storage unit 312 stores input new task definition data, selected task definition data, upstream task definition data, and downstream task definition data using a storage device such as a magnetic disk device 920.

  Next, how the task definition data stored in the task definition storage unit 312 changes by the task detailing process described above will be described using a specific example.

FIG. 34 is a diagram showing an example of task definition data before being changed by the task detailing process in this embodiment.
It is assumed that the task definition storage unit 312 stores task definition data 521 to 523. Parts that are not necessary for the description are omitted.
An example of a display screen displayed on the display device 901 of the terminal device 200 based on the task definition data 521 to 523 is shown on the lower side. Among the display screens, the left side is a detailed workflow diagram 760 generated by the detailed workflow generation unit 134, and the right side is a detailed task flow diagram 730 generated by the detailed task flow generation unit 144.

  It is assumed that the operator 812 has a change authority for changing a task executed by the executor “Actor 2”. It is assumed that the operator 812 operates the keyboard 902 and the mouse 903 of the terminal device 200, selects the task “Process B”, and inputs an instruction for detailing the selected task “Process B”.

The selected task input unit 321 inputs the selected task “Process B” by inputting an operation of the operator 812 using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200.
The selected task input unit 321 outputs task identification data “TaskB” indicating the selected task “Processing B” using a processing device such as the CPU 911.

In the selected task definition acquisition step S41, the selected task definition acquisition unit 331 inputs the task identification data “TaskB” output from the selected task input unit 321 using a processing device such as the CPU 911.
The selected task definition acquisition unit 331 uses a processing device such as the CPU 911 to define task (processing B) that is indicated by the task identification data “TaskB” from the task definition data stored in the task definition storage unit 312. Enter 522.
The selected task definition acquisition unit 331 outputs the input task definition data 522 using a processing device such as the CPU 911.

In the upstream task definition acquisition step S42, the upstream task definition acquisition unit 332 inputs the task definition data 522 output by the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The upstream task definition acquisition unit 332 uses a processing device such as the CPU 911 to search the “UpperTask1” field from the input task definition data 522 and acquires the upstream task data “TaskA”. As a result, the upstream task definition acquisition unit 332 determines that the task identification data of the upstream task of the selected task “Process B” is “TaskA”.
If there are a plurality of upstream task data, it means that there are a plurality of upstream tasks of the selected task, and therefore all the upstream task data is acquired.
The upstream task definition acquisition unit 332 uses a processing device such as the CPU 911 to define task definition data that defines the task (processing A) indicated by the task identification data “TaskA” from the task definition data stored in the task definition storage unit 312. 521 is input.
The upstream task definition acquisition unit 332 outputs the input task definition data 521 using a processing device such as the CPU 911.

In the downstream task definition acquisition step S43, the downstream task definition acquisition unit 333 inputs the task definition data 522 output by the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The downstream task definition acquisition unit 333 uses a processing device such as the CPU 911 to search the “Lower Task 1” field from the input task definition data 522 and acquires the downstream task data “Task C”. Accordingly, the downstream task definition acquisition unit 333 determines that the task identification data of the downstream task of the selected task “Process B” is “TaskC”.
If there are a plurality of downstream task data, it means that there are a plurality of downstream tasks of the selected task, and therefore all the downstream task data is acquired.
The downstream task definition acquisition unit 333 uses a processing device such as the CPU 911 to define task (process C) that is defined by the task identification data “TaskC” from the task definition data stored in the task definition storage unit 312. 523 is entered.
The downstream task definition acquisition unit 333 outputs the input task definition data 523 using a processing device such as the CPU 911.

In the new task definition generation step S44, the new task definition generation unit 347 inputs the task definition data 522 output by the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The new task definition generation unit 347 inputs the task identification data “TaskB” output from the selected task input unit 321 using a processing device such as the CPU 911.
The new task definition generation unit 347 generates new task identification data for identifying a new task using a processing device such as the CPU 911. The new task identification data generated by the new task definition generation unit 347 may be anything as long as it is different from the task identification data included in the existing task definition data stored in the task definition storage unit 312. Here, it is assumed that new task identification data “TaskB1” is generated.

The new task definition generation unit 347 searches for the “UpperTask1” field from the input task definition data 522 using a processing device such as the CPU 911 and acquires the upstream task data “TaskA”. Similarly, the “UpperTask2” field, the “UpperTask3” field,... Are searched, and if there are a plurality of upstream task data, all are acquired.
The new task definition generation unit 347 searches for the “UpperTask1_IFData” field from the input task definition data 522 using a processing device such as the CPU 911 and acquires the upstream interface data “DataFile21”. Similarly, the “UpperTask2_IFData” column, the “UpperTask3_IFData” column,... Are searched, and if there are a plurality of upstream interface data, all are acquired.

The new task definition generation unit 347 searches for the “Lower Task 1” field from the input task definition data 522 using a processing device such as the CPU 911, and acquires the downstream task data “Task C”. Also search the “Lower Task 3” column... If there are a plurality of downstream task data, obtain all of them.
The new task definition generation unit 347 uses a processing device such as the CPU 911 to search the “Lower Task 1_IFData” field from the input task definition data 522 and obtain the downstream interface data “DataFile22”. Similarly, the “LowerTask2_IFData” column and the “LowerTask3_IFData” column are searched, and if there are a plurality of downstream interface data, all are acquired.

  The new task definition generation unit 347 searches for the “Actor” column from the input task definition data 522 using a processing device such as the CPU 911 and acquires task performer data “Actor2”.

The new task definition generation unit 347 generates new task definition data using a processing device such as the CPU 911.
The new task definition data generated by the new task definition generation unit 347 includes the generated new task identification data “TaskB1” as task identification data, and includes data “Yes” indicating a detailed task as task hierarchy data, The input task identification data “TaskB” is included as general task data, the acquired upstream task data “TaskA” is included as upstream task data, the acquired upstream interface data “DataFile21” is included as upstream interface data, and the acquired downstream task data “TaskC” is included as downstream task data, the acquired downstream interface data “DataFile22” is included as downstream interface data, and the acquired task performer data “Actor2” is defined as task performer data. Including.

  The new task definition generation unit 347 outputs the generated new task identification data “TaskB1” and the generated new task definition data using a processing device such as the CPU 911.

In the selected task definition changing step S45, the selected task definition changing unit 341 inputs the task definition data 522 output from the selected task definition acquiring unit 331 in the selected task definition acquiring step S41 using a processing device such as the CPU 911.
The selected task definition changing unit 341 inputs new task identification data “TaskB1” output by the new task definition generating unit 347 in the new task definition generating step S44 using a processing device such as the CPU 911.

  The selected task definition changing unit 341 searches for the “SubTask” field from the input task definition data 522 using a processing device such as the CPU 911. In this example, since the task definition data 522 does not include the “SubTask” field, the selected task definition changing unit 341 adds the “SubTask” field to the task definition data 522 and details the input new task identification data “TaskB1”. Added as generalized task data.

  The selected task definition changing unit 341 outputs the changed task definition data 522 using a processing device such as the CPU 911.

In the upstream task definition changing step S46, the upstream task definition changing unit 342 inputs the task definition data 521 output by the upstream task definition acquiring unit 332 in the upstream task definition acquiring step S42 using a processing device such as the CPU 911.
The upstream task definition changing unit 342 inputs the task identification data “TaskB” output from the selected task input unit 321 using a processing device such as the CPU 911.
The upstream task definition changing unit 342 inputs new task identification data “TaskB1” output by the new task definition generating unit 347 in the new task definition generating step S44 using a processing device such as the CPU 911.

The upstream task definition changing unit 342 uses a processing device such as the CPU 911 to search the “Lower Task 1” field from the input task definition data 521 and acquires the downstream task data “Task B”. Similarly, search the “Lower Task 2” column, the “Lower Task 3” column...
The upstream task definition changing unit 342 includes the input new task identification data “TaskB1” that matches the input task identification data “TaskB” among the acquired downstream task data using a processing device such as the CPU 911. Change to data. If there is downstream task data that does not match the input task identification data “TaskB”, the downstream task data is not changed.
In this example, the upstream task definition changing unit 342 changes the downstream task data “TaskB” in the “LowerTask1” column to “TaskB / TaskB1” using a processing device such as the CPU 911.

  The upstream task definition changing unit 342 outputs the changed task definition data 521 using a processing device such as the CPU 911.

In the downstream task definition changing step S47, the downstream task definition changing unit 343 inputs the task definition data 523 output by the downstream task definition acquiring unit 333 in the downstream task definition acquiring step S43 using a processing device such as the CPU 911.
The downstream task definition changing unit 343 inputs the task identification data “TaskB” output from the selected task input unit 321 using a processing device such as the CPU 911.
The downstream task definition changing unit 343 inputs new task identification data “TaskB1” output by the new task definition generating unit 347 in the new task definition generating step S44 using a processing device such as the CPU 911.

Using the processing device such as the CPU 911, the downstream task definition changing unit 343 searches the “UpperTask1” field from the input task definition data 523, and acquires the upstream task data “TaskB”. Similarly, the “UpperTask2” field, the “UpperTask3” field,... Are searched, and if there are a plurality of upstream task data, all are acquired.
The downstream task definition changing unit 343 includes the input new task identification data “TaskB1” that matches the input task identification data “TaskB” among the acquired upstream task data using a processing device such as the CPU 911. Change to data. If there is upstream task data that does not match the input task identification data “TaskB”, the upstream task data is not changed.
In this example, the downstream task definition changing unit 343 changes the upstream task data “TaskB” in the “UpperTask1” column to “TaskB / TaskB1” using a processing device such as the CPU 911.

  The downstream task definition changing unit 343 outputs the changed task definition data 523 using a processing device such as the CPU 911.

In the changed task definition storage step S48, the task definition storage unit 312 inputs new task definition data output by the new task definition generation unit 347 in the new task definition generation step S44 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the task definition data 522 output from the selected task definition changing unit 341 in the selected task definition changing step S45 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the task definition data 521 output from the upstream task definition change unit 342 in the upstream task definition change step S46 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the task definition data 523 output from the downstream task definition change unit 343 in the downstream task definition change step S47 using a processing device such as the CPU 911.
The task definition storage unit 312 stores input new task definition data, task definition data 522, task definition data 521, and task definition data 523 using a storage device such as a magnetic disk device 920.
When task definition data including the same task identification data as the task identification data included in the input task definition data is already stored, the task definition storage unit 312 uses the processing device such as the CPU 911 to store the old task definition data. Delete task definition data.

FIG. 35 is a diagram showing an example of task definition data changed by the task detailing process in this embodiment.
Note that the underline in the task definition data is a mark indicating a part changed from the task definition data in FIG. 34 and is not a part of the task definition data.

  The task definition storage unit 312 stores four task definition data after completion of the task detailing process described above. Among these, the task definition data 521a is the task definition data 521 changed by the upstream task definition changing unit 342. The task definition data 521 previously stored in the task definition storage unit 312 is deleted because the task definition data 521a and the task identification data are the same. The task definition data 522a is task definition data 522 changed by the upstream task definition changing unit 342. Again, the task definition data 522 stored in the task definition storage unit 312 has been deleted because the task definition data 522a and the task identification data are the same. The task definition data 523a is task definition data 523 changed by the downstream task definition changing unit 343. Similarly, the task definition data 523 previously stored in the task definition storage unit 312 is deleted because the task definition data 523a and the task identification data are the same. The task definition data 524 is new task definition data generated by the new task definition generation unit 347.

An example of a display screen displayed on the display device 901 of the terminal device 200 based on the task definition data is shown on the lower side.
Compared with FIG. 34, the task “Process B” has been detailed, and the detailed task “Process B <b> 1” has been shown by a graphic easy for the operator to understand.

  Next, the task addition process will be described.

FIG. 36 is a flowchart showing an example of a task addition process in which the task definition changing unit 330 adds a task in this embodiment.
The steps common to the task detailing process are denoted by the same reference numerals, and description thereof is omitted here.

  The task addition processing includes selected task definition acquisition step S41, downstream task definition acquisition step S43, new task definition generation step S51, selected task definition change step S52, downstream task definition change step S53, task hierarchy determination step S54, and general task definition acquisition. Step S55, general task definition changing step S56, changed task definition storing step S57, and interface mismatch warning step S58.

In the new task definition generation step S51, the new task definition generation unit 347 inputs the selected task definition data output from the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The new task definition generation unit 347 generates task identification data for identifying a new task by using a processing device such as the CPU 911 and sets it as new task identification data.
The new task definition generation unit 347 generates task definition data for defining a new task by using a processing device such as the CPU 911 and sets it as new task definition data.
The new task definition generation unit 347 outputs the generated new task identification data and the generated new task definition data using a processing device such as the CPU 911.

The new task definition data generated by the new task definition generation unit 347 includes the following data.
The task identification data is generated new task identification data.
The upstream task data is task identification data included in the selected selected task definition data.
The upstream interface data is data indicating that it is undefined.
Downstream task data and downstream interface data are downstream task data and downstream interface data included in the selected selection task definition data.
The task performer data is task performer data included in the selected selected task definition data.

In the selected task definition changing step S52, the selected task definition changing unit 341 inputs the selected task definition data output from the selected task definition acquiring unit 331 in the selected task definition acquiring step S41 using a processing device such as the CPU 911.
The selected task definition changing unit 341 inputs new task identification data output by the new task definition generating unit 347 in the new task definition generating step S51 using a processing device such as the CPU 911.
The selected task definition changing unit 341 uses the processing device such as the CPU 911 to change the downstream task data of the input selection task definition data to the input new task identification data.
The selected task definition changing unit 341 uses a processing device such as the CPU 911 to change the downstream interface data in the input selected task definition data to data indicating that it is undefined.
The selected task definition changing unit 341 outputs the changed selected task definition data using a processing device such as the CPU 911.

In the downstream task definition changing step S53, the downstream task definition changing unit 343 inputs the downstream task definition data output by the downstream task definition acquiring unit 333 in the downstream task definition acquiring step S43 using a processing device such as the CPU 911.
The downstream task definition changing unit 343 inputs new task identification data output by the new task definition generating unit 347 in the new task definition generating step S51 using a processing device such as the CPU 911.
The downstream task definition changing unit 343 uses the processing device such as the CPU 911 to input new task identification data that is the same as the task identification data of the selected task among the upstream task data included in the input downstream task definition data. Change to
The downstream task definition changing unit 343 outputs the changed downstream task definition data using a processing device such as the CPU 911.

In the task hierarchy determination step S54, the general task definition acquisition unit 338 inputs the selected task definition data output by the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to determine whether the selected task is the general task or the detailed task based on the task hierarchy data included in the input selection task definition data.
If it is determined that the selected task is a general task, the process proceeds to the changed task definition storage step S57.
If it is determined that the selected task is a detailed task, the process proceeds to the general task definition acquisition step S55.

In the general task definition acquisition step S55, the general task definition acquisition unit 338 uses a processing device such as the CPU 911 to execute the general task based on the general task data included in the selected task definition data input in the task hierarchy determination step S54. Determine.
The general task definition acquisition unit 338 inputs general task definition data that defines the determined general task from the task definition data stored in the task definition storage unit 312 using a processing device such as the CPU 911.
The general task definition acquisition unit 338 outputs the input general task definition data.

In the general task definition changing step S56, the general task definition changing unit 348 inputs the general task definition data output by the general task definition acquiring unit 338 in the general task definition acquiring step S55 using a processing device such as the CPU 911.
The general task definition changing unit 348 inputs new task identification data output by the new task definition generating unit 347 in the new task definition generating step S51 using a processing device such as the CPU 911.
The general task definition changing unit 348 changes the input general task definition data by using a processing device such as the CPU 911 and adds the input new task identification data to the detailed task data.
The general task definition changing unit 348 outputs the changed general task definition data using a processing device such as the CPU 911.

In the changed task definition storage step S57, the task definition storage unit 312 inputs new task definition data output by the new task definition generation unit 347 in the new task definition generation step S51 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the selected task definition data output from the selected task definition changing unit 341 in the selected task definition changing step S52 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the downstream task definition data output from the downstream task definition change unit 343 in the downstream task definition change step S53 using a processing device such as the CPU 911.
The task definition storage unit 312 inputs any general task definition data output by the general task definition change unit 348 in the general task definition change step S56 using a processing device such as the CPU 911.
The task definition storage unit 312 stores the input new task definition data, selected task definition data, and downstream task definition data (the approximate task definition data, if any) using a storage device such as the magnetic disk device 920.

In the interface inconsistency warning step S58, the interface inconsistency warning unit 181 uses the display device 901 such as the CRT of the terminal device 200 to display a message for warning of interface inconsistency.
By adding a new task, it becomes necessary to define an interface between the selected task and the added new task.
Normally, interface mismatch means a case where the downstream interface data of the upstream task does not match the upstream interface data of the downstream task. The interface inconsistency warning unit 181 determines interface inconsistency by determining whether or not both match, and displays a warning.
In this example, task definition data in which a new interface is undefined is generated. The downstream interface data of the selected task matches the upstream interface data of the added new task in that both are undefined. However, since the workflow cannot be put into operation if it is undefined, the interface inconsistency warning unit 181 also includes upstream interface data or downstream interface data indicating undefined in the task definition data. Displays a message warning that the interface is inconsistent.

  Next, how the task definition data stored in the task definition storage unit 312 changes as a result of the above task addition processing will be described using a specific example.

It is assumed that the task definition storage unit 312 stores the task definition data shown in FIG. 35 before performing the task addition process.
The operator 812 operates the keyboard 902 and the mouse 903 of the terminal device 200 to select the task “Process B1” and inputs an instruction to add a task to be executed after the execution of the selected task “Process B1”. And

The selected task input unit 321 inputs an operation of the operator 812 by using an input device such as a keyboard 902 or a mouse 903 of the terminal device 200 to input the selected task “Process B1”.
The selected task input unit 321 outputs task identification data “TaskB1” indicating the selected task “Processing B1” using a processing device such as the CPU 911.

The task addition input unit 323 inputs task addition instruction information by inputting an operation of the operator 812 using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200.
The task addition input unit 323 outputs the input task addition instruction information using a processing device such as the CPU 911.

In the selected task definition acquisition step S41, the selected task definition acquisition unit 331 inputs the task identification data “TaskB1” output from the selected task input unit 321 using a processing device such as the CPU 911.
The selected task definition acquisition unit 331 uses a processing device such as the CPU 911 to define the task (processing B1) indicated by the task identification data “TaskB1” from the task definition data stored in the task definition storage unit 312. Enter 524.
The selected task definition acquisition unit 331 outputs the input task definition data 524 using a processing device such as the CPU 911.

In the downstream task definition acquisition step S43, the downstream task definition acquisition unit 333 inputs the task definition data 524 output by the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The downstream task definition acquisition unit 333 uses a processing device such as the CPU 911 to search the “Lower Task 1” field from the input task definition data 524, and acquires the downstream task data “Task C”. Accordingly, the downstream task definition acquisition unit 333 determines that the task identification data of the downstream task of the selected task “Process B1” is “TaskC”.
If there are a plurality of downstream task data, it means that there are a plurality of downstream tasks of the selected task, and therefore all the downstream task data is acquired.
The downstream task definition acquisition unit 333 uses a processing device such as the CPU 911 to define task (process C) that is defined by the task identification data “TaskC” from the task definition data stored in the task definition storage unit 312. Enter 523a.
The downstream task definition acquisition unit 333 outputs the input task definition data 523a using a processing device such as the CPU 911.

In the new task definition generation step S51, the new task definition generation unit 347 inputs the task definition data 524 output from the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The new task definition generation unit 347 inputs the task identification data “TaskB1” output from the selected task input unit 321 using a processing device such as the CPU 911.

  The new task definition generation unit 347 generates new task identification data for identifying a new task using a processing device such as the CPU 911. The new task identification data generated by the new task definition generation unit 347 may be anything as long as it is different from the task identification data included in the existing task definition data stored in the task definition storage unit 312. Here, it is assumed that new task identification data “TaskB2” is generated.

The new task definition generation unit 347 uses a processing device such as the CPU 911 to search the “Work” field from the input task definition data 524 and acquires the task hierarchy data “Yes”.
Since the task hierarchy data is “Yes”, the new task definition generation unit 347 searches for the “BelongTo” field from the input task definition data 524 using a processing device such as the CPU 911 and acquires the general task data “TaskB”.

The new task definition generation unit 347 uses a processing device such as the CPU 911 to search the “Lower Task 1” column from the input task definition data 524, and acquires the downstream task data “Task C”. Similarly, search the “Lower Task 2” column, the “Lower Task 3” column...
Using a processing device such as the CPU 911, the new task definition generation unit 347 searches the “LowTask1_IFData” field from the input task definition data 524, and acquires the downstream interface data “DataFile22”. Similarly, the “Lower Task 2_IF Data” column, the “Lower Task 3_IF Data” column... Are searched, and if there are a plurality of downstream interface data, all are acquired.
The new task definition generation unit 347 uses a processing device such as the CPU 911 to search the “Actor” field from the input task definition data 524 and acquires the task performer data “Actor2”.

The new task definition generation unit 347 generates new task definition data using a processing device such as the CPU 911.
The new task definition data generated by the new task definition generation unit 347 includes the generated new task identification data “TaskB2” as task identification data, the acquired task hierarchy data “Yes” as task hierarchy data, and the acquired general task Data “TaskB” is included as general task data, input task identification data “TaskB1” is included as upstream task data, undefined data (for example, “undefined”) is included as upstream interface data, and acquired downstream The task data “TaskC” is included as downstream task data, the acquired downstream interface data “DataFile22” is included as downstream interface data, and the acquired task performer data “Actor2” is included as task performer data. .

  The new task definition generation unit 347 outputs the generated new task identification data “TaskB2” and the generated new task definition data using a processing device such as the CPU 911.

In the selected task definition changing step S52, the selected task definition changing unit 341 inputs the task definition data 524 output from the selected task definition acquiring unit 331 in the selected task definition acquiring step S41 using a processing device such as the CPU 911.
The selected task definition changing unit 341 inputs new task identification data output by the new task definition generating unit 347 in the new task definition generating step S51 using a processing device such as the CPU 911.

The selected task definition changing unit 341 uses a processing device such as the CPU 911 to search the “Lower Task 1” field from the input task definition data 524 and deletes the downstream task data. Similarly, the “Lower Task 2” column, the “Lower Task 3” column... Are searched, and if there are a plurality of downstream task data, all are deleted.
The selected task definition changing unit 341 uses a processing device such as the CPU 911 to search the “Lower Task 1_IFData” field from the input task definition data 524, and deletes the downstream interface data. Similarly, the “Lower Task 2_IF Data” column, the “Lower Task 3_IF Data” column... Are searched, and if there are a plurality of downstream interface data, all are deleted.
Using the processing device such as the CPU 911, the selected task definition changing unit 341 adds a “Lower Task 1” column to the input task definition data 524, and adds the input new task identification data “Task B2” as downstream task data.
Using the processing device such as the CPU 911, the selected task definition changing unit 341 adds a “LowTask1_IFData” column to the input task definition data 524, and adds data “undefined” indicating that it is undefined.

  The selected task definition changing unit 341 outputs the changed task definition data 524 using a processing device such as the CPU 911.

In the downstream task definition changing step S53, the downstream task definition changing unit 343 inputs the task definition data 523a output from the downstream task definition acquiring unit 333 in the downstream task definition acquiring step S43 using a processing device such as the CPU 911.
The downstream task definition changing unit 343 inputs the task identification data “TaskB1” output from the selected task input unit 321 using a processing device such as the CPU 911.
The downstream task definition changing unit 343 inputs new task identification data output by the new task definition generating unit 347 in the new task definition generating step S51 using a processing device such as the CPU 911.

The downstream task definition changing unit 343 uses a processing device such as the CPU 911 to search the “UpperTask1” field from the input task definition data 523a, and acquires the upstream task data “TaskB / TaskB1”. Similarly, the “UpperTask2” field, the “UpperTask3” field,... Are searched, and if there are a plurality of upstream task data, all are acquired.
The downstream task definition changing unit 343 changes the portion of the acquired upstream task data that matches the input task identification data “TaskB1” to the input new task identification data “TaskB2”. The upstream task data that does not match the input task identification data “TaskB1” is not changed.
In this example, the downstream task definition changing unit 343 changes the upstream task data “TaskB / TaskB1” in the “UpperTask1” column to “TaskB / TaskB2” using a processing device such as the CPU 911.

  The downstream task definition changing unit 343 outputs the changed task definition data 523a using a processing device such as the CPU 911.

In the task hierarchy determination step S54, the general task definition acquisition unit 338 inputs the task definition data 524 output by the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to search the “Work” field from the input task definition data 524 and acquires the task hierarchy data “Yes”.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to determine whether the selected task is a general task or a detailed task based on the acquired task hierarchy data. In this example, since the acquired task hierarchy data is “Yes”, the general task definition acquisition unit 338 determines that the selected task is a detailed task, and proceeds to the general task definition acquisition step S55.

In the general task definition acquisition step S55, the general task definition acquisition unit 338 uses a processing device such as the CPU 911 to search the “BelongTo” field from the task definition data 524 input in the task hierarchy determination step S54 and search for the general task data “TaskB”. Is obtained.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to define a task (processing B) indicated by the acquired general task data “TaskB” from the task definition data stored in the task definition storage unit 312. Definition data 522a is acquired.

  The general task definition acquisition unit 338 outputs the acquired task definition data 522a using a processing device such as the CPU 911.

In the general task definition changing step S56, the general task definition changing unit 348 inputs the task definition data 522a output by the general task definition acquiring unit 338 in the general task definition acquiring step S55 using a processing device such as the CPU 911.
The general task definition changing unit 348 inputs the new task identification data “TaskB2” output from the new task definition generating unit 347 in the new task definition generating step S51 using a processing device such as the CPU 911.

The general task definition changing unit 348 uses a processing device such as the CPU 911 to search the “SubTask” field from the input task definition data 522a, and acquires the detailed task data “TaskB1”.
The general task definition changing unit 348 changes the “SubTask” field of the task definition data 522a using a processing device such as the CPU 911, and adds the input new task identification data “TaskB2” to the detailed task data.
The general task definition changing unit 348 outputs the changed task definition data 522a using a processing device such as the CPU 911.

In the changed task definition storage step S57, the task definition storage unit 312 inputs new task definition data output by the new task definition generation unit 347 in the new task definition generation step S51 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the task definition data 524 output from the selected task definition changing unit 341 in the selected task definition changing step S52 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the task definition data 523a output from the downstream task definition changing unit 343 in the downstream task definition changing step S53 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the task definition data 522a output by the general task definition change unit 348 in the general task definition change step S56 using a processing device such as the CPU 911.
The task definition storage unit 312 stores input new task definition data, task definition data 524, task definition data 523a, and task definition data 522a using a storage device such as a magnetic disk device 920.
As with the task detailing process, when task definition data including the same task identification data as the task identification data included in the input task definition data has already been stored, the task definition storage unit 312 includes the CPU 911 and the like. Delete old task definition data using the processing unit.

FIG. 37 is a diagram showing an example of task definition data changed by the task addition processing in this embodiment.
Note that the underline in the task definition data is a mark indicating a part changed from the task definition data in FIG. 35 and is not a part of the task definition data.

  The task definition data stored in the task definition storage unit 312 is further increased by one to five. Among these, the task definition data 521a is not changed. The task definition data 522b is task definition data 522a changed by the general task definition changing unit 348. The task definition data 523b is task definition data 523a changed by the downstream task definition changing unit 343. The task definition data 524b is task definition data 524 changed by the selected task definition changing unit 341. The task definition data 525 is new task definition data generated by the new task definition generation unit 347. The old task definition data 522a, task definition data 523a, and task definition data 524 have been deleted.

An example of a display screen displayed on the display device 901 of the terminal device 200 based on the task definition data is shown on the lower side.
Compared with FIG. 35, the fact that the task “Process B2” is added after the task “Process B1” is shown by a graphic that is easy for the operator to understand.
Note that a thick box rectangle “IF undefined” is a warning displayed by the interface mismatch warning unit 181.

FIG. 38 is a flowchart showing another example of the flow of task addition processing in which the task definition changing unit 330 adds a task in the embodiment.
In addition, about the process which is common in the already demonstrated process, the same code | symbol is attached | subjected and description is abbreviate | omitted here.

  The task addition processing includes selected task definition acquisition step S41, upstream task definition acquisition step S42, downstream task definition acquisition step S43, new task definition generation step S61, upstream task definition change step S62, downstream task definition change step S63, task hierarchy determination Step S54, general task definition acquisition step S55, general task definition change step S56, and change task definition storage step S67.

In the new task definition generation step S61, the new task definition generation unit 347 inputs the selected task definition data output from the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The new task definition generation unit 347 generates task identification data for identifying a new task by using a processing device such as the CPU 911 and sets it as new task identification data.
The new task definition generation unit 347 generates task definition data for defining a new task by using a processing device such as the CPU 911 and sets it as new task definition data.
The new task definition generation unit 347 outputs the generated new task identification data and the generated new task definition data using a processing device such as the CPU 911.

The new task definition data generated by the new task definition generation unit 347 includes the following data.
The task identification data is generated new task identification data.
The upstream task data is upstream task data included in the selected selection task definition data.
The upstream interface data is upstream interface data included in the input selected task definition data.
The downstream task data is downstream task data included in the input selected task definition data.
The downstream interface data is downstream interface data included in the input selected task definition data.
The task performer data is task performer data included in the selected selected task definition data.

In the upstream task definition changing step S62, the upstream task definition changing unit 342 inputs the upstream task definition data output by the upstream task definition acquiring unit 332 in the upstream task definition acquiring step S42 using a processing device such as the CPU 911.
The upstream task definition changing unit 342 inputs new task identification data output by the new task definition generating unit 347 in the new task definition generating step S61 using a processing device such as the CPU 911.
The upstream task definition changing unit 342 uses the processing device such as the CPU 911 to add the input new task identification data to the downstream task data included in the input upstream task definition data.
Using the processing device such as the CPU 911, the upstream task definition changing unit 342 uses the downstream interface data included in the input upstream task definition data as the downstream interface data corresponding to the added downstream task data (new task identification data). The same data as the downstream interface data corresponding to the downstream task data indicating the selected task is added.
The upstream task definition changing unit 342 outputs the changed upstream task definition data using a processing device such as the CPU 911.

In the downstream task definition changing step S63, the downstream task definition changing unit 343 inputs the downstream task definition data output by the downstream task definition acquiring unit 333 in the downstream task definition acquiring step S43 using a processing device such as the CPU 911.
The downstream task definition changing unit 343 inputs new task identification data output by the new task definition generating unit 347 in the new task definition generating step S61 using a processing device such as the CPU 911.
The downstream task definition changing unit 343 uses the processing device such as the CPU 911 to add the input new task identification data to the upstream task data included in the input downstream task definition data.
Using the processing device such as the CPU 911, the downstream task definition changing unit 343 uses the upstream interface data included in the input downstream task definition data as upstream interface data corresponding to the added upstream task data (new task identification data). The same data as the upstream interface data corresponding to the upstream task data indicating the selected task is added.
The downstream task definition changing unit 343 outputs the changed downstream task definition data using a processing device such as the CPU 911.

In the changed task definition storage step S67, the task definition storage unit 312 inputs new task definition data output by the new task definition generation unit 347 in the new task definition generation step S61 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the upstream task definition data output by the upstream task definition change unit 342 in the upstream task definition change step S62 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the downstream task definition data output by the downstream task definition change unit 343 in the downstream task definition change step S63 using a processing device such as the CPU 911.
The task definition storage unit 312 inputs any general task definition data output by the general task definition change unit 348 in the general task definition change step S56 using a processing device such as the CPU 911.
The task definition storage unit 312 stores the input new task definition data, upstream task definition data, and downstream task definition data (if any, general task definition data) using a storage device such as the magnetic disk device 920.

  Next, how the task definition data stored in the task definition storage unit 312 changes as a result of the above task addition processing will be described using a specific example.

It is assumed that the task definition storage unit 312 stores the task definition data shown in FIG. 37 before performing the task addition process.
The operator 812 operates the keyboard 902 and the mouse 903 of the terminal device 200 to select the task “Process B1”, and inputs an instruction to add a task to be executed in parallel with the selected task “Process B1”. Shall.

The selected task input unit 321 inputs an operation of the operator 812 by using an input device such as a keyboard 902 or a mouse 903 of the terminal device 200 to input the selected task “Process B1”.
The selected task input unit 321 outputs task identification data “TaskB1” indicating the selected task “Processing B1” using a processing device such as the CPU 911.

The task addition input unit 323 inputs task addition instruction information by inputting an operation of the operator 812 using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200.
The task addition input unit 323 outputs the input task addition instruction information using a processing device such as the CPU 911.

In the selected task definition acquisition step S41, the selected task definition acquisition unit 331 inputs the task identification data “TaskB1” output from the selected task input unit 321 using a processing device such as the CPU 911.
The selected task definition acquisition unit 331 uses a processing device such as the CPU 911 to define a task (processing B1) indicated by the task identification data “TaskB1” from the task definition storage unit 312 stored in the task definition storage unit 312. Data 524b is input.
The selected task definition acquisition unit 331 outputs the input task definition data 524b using a processing device such as the CPU 911.

In the upstream task definition acquisition step S42, the upstream task definition acquisition unit 332 inputs the task definition data 524b output from the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
Using the processing device such as the CPU 911, the upstream task definition acquisition unit 332 searches the “UpperTask1” field from the input task definition data 524b, and acquires the upstream task data “TaskA”. Similarly, the “UpperTask2” field, the “UpperTask3” field,... Are searched, and if there are a plurality of upstream task data, all are acquired.
The upstream task definition acquisition unit 332 uses a processing device such as the CPU 911 to define a task (processing A) indicated by the acquired upstream task data “TaskA” from the task definition data stored in the task definition storage unit 312. The definition data 521a is input.
The upstream task definition acquisition unit 332 outputs the input task definition data 521a using a processing device such as the CPU 911.

In the downstream task definition acquisition step S43, the downstream task definition acquisition unit 333 inputs the task definition data 524b output by the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The downstream task definition acquisition unit 333 uses a processing device such as the CPU 911 to search the “Lower Task 1” field from the input task definition data 524b, and acquires the downstream task data “Task B2”. Similarly, the “Lower Task 2” column, the “Lower Task 3” column... Are searched, and if there are a plurality of pieces of downstream task data, all are acquired.
The downstream task definition acquisition unit 333 uses a processing device such as the CPU 911 to define task (process C) that is defined by the task identification data “TaskC” from the task definition data stored in the task definition storage unit 312. Enter 523a.
The downstream task definition acquisition unit 333 outputs the input task definition data 523a using a processing device such as the CPU 911.

  In the new task definition generation step S61, the new task definition generation unit 347 inputs the task definition data 524b output from the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.

The new task definition generation unit 347 generates new task identification data for identifying a new task using a processing device such as the CPU 911. The new task identification data generated by the new task definition generation unit 347 may be anything as long as it is different from the task identification data included in the existing task definition data stored in the task definition storage unit 312. Here, it is assumed that new task identification data “TaskB3” is generated.
The new task definition generation unit 347 uses a processing device such as the CPU 911 to search the “ID” field from the input task definition data 524b, and changes the task identification data to the generated new task identification data “TaskB3”.

  The new task definition generation unit 347 outputs the generated new task identification data “TaskB3” and the changed task definition data 524b using a processing device such as the CPU 911.

In the upstream task definition changing step S62, the upstream task definition changing unit 342 inputs the task definition data 521a output from the upstream task definition acquiring unit 332 in the upstream task definition acquiring step S42 using a processing device such as the CPU 911.
The upstream task definition changing unit 342 inputs the task identification data “TaskB1” output from the selected task input unit 321 using a processing device such as the CPU 911.
The upstream task definition changing unit 342 inputs new task identification data “TaskB3” output by the new task definition generating unit 347 in the new task definition generating step S61 using a processing device such as the CPU 911.

The upstream task definition changing unit 342 uses a processing device such as the CPU 911 to search the “Lower Task 1” field from the input task definition data 521a, and acquires the downstream task data “Task B / Task B1”. Similarly, the “Lower Task 2” column, the “Lower Task 3” column... Are searched, and if there are a plurality of pieces of downstream task data, all are acquired.
The upstream task definition changing unit 342 adds downstream task data to the input task definition data 521a using a processing device such as the CPU 911. In this example, since there is only one acquired downstream task data, the upstream task definition changing unit 342 adds the “Lower Task 2” column, and adds the input new task identification data “Task B3” as the downstream task data.

Using the processing device such as the CPU 911, the upstream task definition changing unit 342 determines from the acquired downstream task data that there is a portion that matches the input task identification data “TaskB1”. In this example, there is a portion where the downstream task data “TaskB / TaskB1” in the “LowerTask1” column matches the task identification data “TaskB1”.
The upstream task definition changing unit 342 acquires downstream interface data corresponding to the determined downstream task data from the input task definition data 521a using a processing device such as the CPU 911. In this example, the upstream task definition changing unit 342 searches the “LowerTask1_IFData” field and acquires the downstream interface data “DataFile21”.

  The upstream task definition changing unit 342 uses the processing device such as the CPU 911 to add the acquired downstream interface data “DataFile21” as the downstream interface data corresponding to the added downstream task data. That is, the upstream task definition changing unit 342 uses a processing device such as the CPU 911 to add the “Lower Task 2_IFData” column to the input task definition data 521a and add the downstream interface data “DataFile21”.

  The upstream task definition changing unit 342 outputs the changed task definition data 521a using a processing device such as the CPU 911.

In the downstream task definition changing step S63, the downstream task definition changing unit 343 inputs the task definition data 525 output by the downstream task definition acquiring unit 333 in the downstream task definition acquiring step S43 using a processing device such as the CPU 911.
The downstream task definition changing unit 343 inputs the task identification data “TaskB1” output from the selected task input unit 321 using a processing device such as the CPU 911.
The downstream task definition changing unit 343 inputs new task identification data “TaskB3” output from the new task definition generating unit 347 in the new task definition generating step S61 using a processing device such as the CPU 911.

Using the processing device such as the CPU 911, the downstream task definition changing unit 343 searches the “UpperTask1” field from the input task definition data 525, and acquires the upstream task data “TaskB1”. Similarly, the “UpperTask2” field, the “UpperTask3” field,... Are searched, and if there are a plurality of upstream task data, all are acquired.
The downstream task definition changing unit 343 adds upstream task data to the input task definition data 525 using a processing device such as the CPU 911. In this example, since the acquired upstream task data is only one, the upstream task definition changing unit 342 adds the “UpperTask2” column and adds the input new task identification data “TaskB3” as the upstream task data.

The downstream task definition changing unit 343 determines, using a processing device such as the CPU 911, from the acquired upstream task data that there is a part that matches the input task identification data “TaskB1”. In this example, the upstream task data “TaskB1” in the “UpperTask1” column matches the task identification data “TaskB1”.
The downstream task definition changing unit 343 acquires upstream interface data corresponding to the determined upstream task data from the input task definition data 525 using a processing device such as the CPU 911. In this example, the downstream task definition changing unit 343 searches the “UpperTask1_IFData” field, and acquires the upstream interface data “undefined”.

  The downstream task definition changing unit 343 uses the processing device such as the CPU 911 to add the acquired upstream interface data “undefined” as the upstream interface data corresponding to the added upstream task data. That is, the downstream task definition changing unit 343 adds the “UpperTask2_IFData” column to the input task definition data 525 and adds the upstream interface data “undefined” using a processing device such as the CPU 911.

  The downstream task definition changing unit 343 outputs the changed task definition data 525 using a processing device such as the CPU 911.

In the task hierarchy determination step S54, the general task definition acquisition unit 338 inputs the task definition data 524b output from the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to search the “Work” field from the input task definition data 524b and acquires the task hierarchy data “Yes”.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to determine whether the selected task is a general task or a detailed task based on the acquired task hierarchy data. In this example, since the acquired task hierarchy data is “Yes”, the general task definition acquisition unit 338 determines that the selected task is a detailed task, and proceeds to the general task definition acquisition step S55.

In the general task definition acquisition step S55, the general task definition acquisition unit 338 uses a processing device such as the CPU 911 to search the “BelongTo” field from the task definition data 524b input in the task hierarchy determination step S54 and search for the general task data “TaskB”. Is obtained.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to define a task (processing B) indicated by the acquired general task data “TaskB” from the task definition data stored in the task definition storage unit 312. Definition data 522b is acquired.

  The general task definition acquisition unit 338 outputs the acquired task definition data 522b using a processing device such as the CPU 911.

In the general task definition change step S56, the general task definition change unit 348 inputs the task definition data 522b output from the general task definition acquisition unit 338 in the general task definition acquisition step S55 using a processing device such as the CPU 911.
The general task definition changing unit 348 inputs new task identification data “TaskB3” output from the new task definition generating unit 347 in the new task definition generating step S61 using a processing device such as the CPU 911.

The general task definition changing unit 348 uses a processing device such as the CPU 911 to search the “SubTask” column from the input task definition data 522b, and obtains detailed task data “TaskB1, TaskB2”.
The general task definition changing unit 348 changes the “SubTask” field of the task definition data 522b by using a processing device such as the CPU 911, and adds the input new task identification data “TaskB3” to the detailed task data.
The general task definition changing unit 348 outputs the changed task definition data 522b using a processing device such as the CPU 911.

In the changed task definition storage step S57, the task definition storage unit 312 receives the task definition data 524b output from the new task definition generation unit 347 in the new task definition generation step S61 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the task definition data 521a output from the upstream task definition change unit 342 in the upstream task definition change step S62 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the task definition data 525 output by the downstream task definition change unit 343 in the downstream task definition change step S63 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the task definition data 522b output from the general task definition change unit 348 in the general task definition change step S56 using a processing device such as the CPU 911.
The task definition storage unit 312 stores input task definition data 524b, task definition data 521a, task definition data 525, and task definition data 522b using a storage device such as a magnetic disk device 920.
When task definition data including the same task identification data as the task identification data included in the input task definition data is already stored, the task definition storage unit 312 uses the processing device such as the CPU 911 to store the old task definition data. Delete task definition data.

FIG. 39 is a diagram showing an example of task definition data changed by the task addition process in this embodiment.
Note that the underline in the task definition data is a mark indicating a part changed from the task definition data in FIG. 37 and is not a part of the task definition data.

  The task definition data stored in the task definition storage unit 312 is further increased by one to six. Among these, the task definition data 521c is the task definition data 521a changed by the upstream task definition changing unit 342. The task definition data 522c is task definition data 522b changed by the general task definition changing unit 348. The task definition data 523b and the task definition data 524b are not changed. The task definition data 525c is task definition data 525 changed by the downstream task definition changing unit 343. The task definition data 526 is task definition data 524b changed by the new task definition generation unit 347. The old task definition data 521a, task definition data 522b, and task definition data 525 have been deleted. On the other hand, since the task definition data 524b and the task definition data 526 have different task identification data, the task definition storage unit 312 determines that the task definition data is different, and does not delete the task definition data 524b.

An example of a display screen displayed on the display device 901 of the terminal device 200 based on the task definition data is shown on the lower side.
Compared with FIG. 37, the number of tasks “Process B1” is increased to two, and a task that is executed in parallel is added by a graphic that is easy for the operator to understand.
Note that a thick box rectangle “IF undefined” is a warning displayed by the interface mismatch warning unit 181.

  Unlike the task addition process (serial addition) described with reference to FIG. 36, the task addition process (parallel addition) described with reference to FIG. 38 does not always cause interface inconsistency. Does not have. However, when the task definition data stored in the task definition storage unit 312 is changed, the interface inconsistency warning unit 181 uses a processing device such as the CPU 911 to check whether an interface inconsistency has occurred due to the change. As a result of the inspection, when an interface mismatch or undefined is found, the interface mismatch warning unit 181 displays a warning using the display device 901 such as the CRT of the terminal device 200.

  Next, the executor change process will be described.

FIG. 40 is a flowchart showing an example of a flow of an executor changing process in which the task definition changing unit 330 changes the executor of the task in this embodiment.
In addition, about the process which is common in the already demonstrated process, the same code | symbol is attached | subjected and description is abbreviate | omitted here.

  The executor change process includes a selected task definition acquisition step S41, a selected task definition change step S71, a task hierarchy determination step S54, a general task definition acquisition step S55, a general task definition change step S76, and a changed task definition storage step S77.

In the task executor changing step S71, the executor changing unit 344 inputs the selected task definition data output from the selected task definition acquiring unit 331 in the selected task definition acquiring step S41 using a processing device such as the CPU 911.
The executor change unit 344 inputs the executor change instruction information output by the task definition change input unit 320 using a processing device such as the CPU 911.
The executor changing unit 344 uses a processing device such as the CPU 911 to acquire an executor identifier indicating the changed executor based on the input executor change instruction information.
The executor changing unit 344 changes the task executor data in the selected selected task definition data to the acquired executor identifier using a processing device such as the CPU 911.
The executor changing unit 344 outputs the acquired executor identifier and the changed selected task definition data using a processing device such as the CPU 911.

In the general task definition changing step S76, the general task definition changing unit 348 inputs the general task definition data output by the general task definition acquiring unit 338 in the general task definition acquiring step S55 using a processing device such as the CPU 911.
The general task definition changing unit 348 inputs the executor identifier output by the executor changing unit 344 in the task executor changing step S71 using a processing device such as the CPU 911.
The general task definition changing unit 348 uses a processing device such as the CPU 911 to acquire task executor data and detailed task executor data included in the input general task definition data.
The general task definition changing unit 348 uses a processing device such as the CPU 911 to determine whether the input executor identifier is included in either the acquired task executor data or the detailed task executor data. To do.
When it is determined that the input executor identifier is not included in either the acquired task executor data or the detailed task executor data, the general task definition changing unit 348 uses a processing device such as the CPU 911. Then, in the input general task definition data, the detailed task execution person data is changed to include the input execution person identifier.
The general task definition changing unit 348 outputs the changed general task definition data using a processing device such as the CPU 911.

In the changed task definition storage step S77, the task definition storage unit 312 uses the processing device such as the CPU 911 to input the selected task definition data output by the executor change unit 344 in the task executor change step S71.
The task definition storage unit 312 inputs any general task definition data output from the general task definition change unit 348 in the general task definition change step S76 using a processing device such as the CPU 911.
The task definition storage unit 312 uses a storage device such as the magnetic disk device 920 to store the input selected task definition data and, if any, general task definition data.

  Next, how the task definition data stored in the task definition storage unit 312 changes due to the above-described performer change process will be described using a specific example.

It is assumed that the task definition storage unit 312 stores the task definition data shown in FIG. 39 before executing the executor change process.
The operator 812 operates the keyboard 902 and the mouse 903 of the terminal device 200 to select the task “Process B1” (right side), and designates the performer of the selected task “Process B1” (right side) as the performer “Actor3”. ”Is entered.
Note that the operator 812 does not have the authority to change the task executed by the executor “Actor3”, and the operator 813 has the authority to change the task executed by the executor “Actor3”. To do.

The selected task input unit 321 inputs an operation of the operator 812 by using an input device such as a keyboard 902 or a mouse 903 of the terminal device 200 to input the selected task “Process B1” (right side).
The selected task input unit 321 outputs task identification data “TaskB3” indicating the selected task “Process B1” (right side) using a processing device such as the CPU 911.

The executor change input unit 324 inputs executor change instruction information by inputting the operation of the operator 812 using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200.
The executor change input unit 324 outputs the input executor change instruction information using a processing device such as the CPU 911.
The executor change instruction information includes an executor identifier “Actor3” indicating the executor after the change.

The executor change authority determination unit 151 inputs the executor change instruction information output by the executor change input unit 324 using a processing device such as the CPU 911.
The executor change authority determining unit 151 uses a processing device such as the CPU 911 to acquire an executor identifier “Actor3” indicating the executor after the change from the input executor change instruction information.
The executor change authority determination unit 151 uses a processing device such as the CPU 911 to define the executor indicated by the acquired executor identifier “Actor3” from the executor definition data stored in the executor definition storage unit 311. Enter definition data.
The executor change authority determination unit 151 uses a processing device such as the CPU 911 to perform an operation having change authority to change a task executed by the executor indicated by the executor identifier “Actor3” based on the input executor definition data. Determine who is. In this example, the executor change authority determination unit 151 determines that the operator having the change authority is the operator 813.
The executor change authority determination unit 151 determines whether the operator 812 who has input the executor change instruction information has the change authority based on the determined operator using a processing device such as the CPU 911. In this example, the executor change authority determination unit 151 determines that the operator 812 has no change authority.
The executor change authority determination unit 151 outputs data indicating the determination result and data indicating the determined operator 813 using a processing device such as the CPU 911.

The executor change request notifying unit 161 inputs data indicating the determination result output from the executor change authority determining unit 151 and data indicating the operator 813 using a processing device such as the CPU 911.
Since the executor change authority determining unit 151 determines that the operator 812 has no change authority, the executor change request notifying unit 161 uses the processing device such as the CPU 911 to execute the execution output from the executor change input unit 324. Enter person change instruction information.
The executor change request notifying unit 161 uses a processing device such as the CPU 911 to generate a message requesting the operator 813 to approve the executor's change based on the input executor change instruction information.
The executor change request notifying unit 161 requests the operator 813 to approve the change of the executor by displaying the generated message using the display device 901 such as the CRT of the terminal device 200 of the operator 813. Notify you.

  The operator 813 looks at the displayed message and determines whether to approve the change of the performer. In this example, it shall be approved. The operator 813 operates the keyboard 902 and the mouse 903 of the terminal device 200 to input that the change is approved.

The executor change approval / disapproval input unit 171 inputs executor change approval / disapproval information indicating approval of change by inputting an operation of the operator 813 using an input device such as a keyboard 902 or a mouse 903 of the terminal device 200. .
The executor change approval / disapproval input unit 171 uses the processing device such as the CPU 911 to output the input executor change approval / disapproval information.

The task definition changing unit 330 inputs the executor change approval / disapproval information output by the executor change approval / disapproval input unit 171 using a processing device such as the CPU 911.
Since the input executor change approval / disapproval information indicates the approval of the change, the task definition changing unit 330 starts the executor change process using a processing device such as the CPU 911.

In the selected task definition acquisition step S41, the selected task definition acquisition unit 331 inputs the task identification data “TaskB3” output from the selected task input unit 321 using a processing device such as the CPU 911.
The selected task definition acquisition unit 331 uses a processing device such as the CPU 911 to define the task (right processing B1) indicated by the input task identification data “TaskB3” from the task definition data stored in the task definition storage unit 312. The task definition data 526 to be input is input.
The selected task definition acquisition unit 331 outputs the input task definition data 526 using a processing device such as the CPU 911.

In the task executor changing step S71, the executor changing unit 344 inputs the task definition data 526 output by the selected task definition acquiring unit 331 in the selected task definition acquiring step S41 using a processing device such as the CPU 911.
The executor change unit 344 inputs the executor change instruction information output by the executor change input unit 324 using a processing device such as the CPU 911.

The executor changing unit 344 acquires an executor identifier “Actor3” indicating the changed executor from the input executor change instruction information using a processing device such as the CPU 911.
The executor changing unit 344 uses a processing device such as the CPU 911 to search the “Actor” field from the input task definition data 526 and changes the task executor data to the acquired executor identifier.

  The executor changing unit 344 outputs the changed task definition data 526 using a processing device such as the CPU 911.

In the task hierarchy determination step S54, the general task definition acquisition unit 338 inputs the task definition data 526 output by the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The general task definition acquisition unit 338 searches for the “Work” field from the input task definition data 526 using a processing device such as the CPU 911 and acquires the task hierarchy data “Yes”.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to determine whether the selected task is a general task or a detailed task based on the acquired task hierarchy data. In this example, since the acquired task hierarchy data is “Yes”, the general task definition acquisition unit 338 determines that the selected task is a detailed task, and proceeds to the general task definition acquisition step S55.

In the general task definition acquisition step S55, the general task definition acquisition unit 338 uses a processing device such as the CPU 911 to search the “BelongTo” field from the task definition data 526 input in the task hierarchy determination step S54 and search for the general task data “ "TaskB" is acquired.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to define a task (processing B) indicated by the acquired general task data “TaskB” from the task definition data stored in the task definition storage unit 312. The definition data 522c is input.
The general task definition acquisition unit 338 outputs the input task definition data 522c using a processing device such as the CPU 911.

In the general task definition changing step S76, the general task definition changing unit 348 inputs the task definition data 522c output by the general task definition acquiring unit 338 in the general task definition acquiring step S55 using a processing device such as the CPU 911.
The general task definition changing unit 348 inputs the executor change instruction information output by the executor change input unit 324 using a processing device such as the CPU 911.
The general task definition changing unit 348 uses a processing device such as the CPU 911 to acquire an executor identifier “Actor3” indicating the executor after the change from the input executor change instruction information.
The general task definition changing unit 348 uses a processing device such as the CPU 911 to search the “Actor” column from the input task definition data 522c, and obtains task performer data “Actor2”.
The general task definition changing unit 348 uses a processing device such as the CPU 911 to search the “Subactor” field from the input task definition data 522c, and acquires detailed task performer data. In this example, since the task definition data 522c does not include the “Subactor” column, the general task definition change unit 348 acquires empty detailed task performer data.
The general task definition changing unit 348 uses the processing device such as the CPU 911 to determine whether the acquired executor identifier “Actor3” is included in either the acquired task executor data or the detailed task executor data. Determine. In this example, since the task performer data is “Actor2” and the detailed task performer data is empty, the general task definition changing unit 348 determines that it is not included.
The general task definition changing unit 348 determines that the acquired executor identifier “Actor3” is not included in the acquired task executor data or the detailed task executor data, and thus uses a processing device such as the CPU 911. The executor identifier “Actor3” is added as detailed task executor data. In this example, since the task definition data 522c does not include the “Subactor” column, the general task definition changing unit 348 adds a “Subactor” column to the task definition data 522c by using a processing device such as the CPU 911 to be detailed. An executor identifier “Actor3” is added as task executor data.

  The general task definition changing unit 348 outputs the changed task definition data 522c using a processing device such as the CPU 911.

In the changed task definition storage step S78, the task definition storage unit 312 inputs the task definition data 526 output by the executor changing unit 344 in the task executor changing step S71 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the task definition data 522c output from the general task definition change unit 348 in the general task definition change step S76 using a processing device such as the CPU 911.
The task definition storage unit 312 stores input task definition data 526 and task definition data 522c using a storage device such as a magnetic disk device 920.
If the task definition storage unit 312 has already stored task definition data including the same task identification data as the task identification data included in the input task definition data, the task definition storage unit 312 uses the processing device such as the CPU 911 to store the old task definition data. Delete task definition data.

FIG. 41 is a diagram showing an example of task definition data changed by the executor changing process in this embodiment.
Note that the underline in the task definition data is a mark indicating a part changed from the task definition data in FIG. 39 and is not a part of the task definition data.

  The task definition data stored in the task definition storage unit 312 remains six. Among these, task definition data 521c, task definition data 523b, task definition data 524b, and task definition data 525c are not changed. The task definition data 522d is task definition data 522c changed by the general task definition changing unit 348. The task definition data 526d is task definition data 526 changed by the executor changing unit 344. The old task definition data 522c and task definition data 526 have been deleted.

An example of a display screen displayed on the display device 901 of the terminal device 200 based on the task definition data is shown on the lower side.
Compared to FIG. 39, it is indicated by a graphic that the operator can easily understand that the executor of the task “Process B1” (right side) is changed to “Actor3”.
Note that a thick box rectangle “IF undefined” is a warning displayed by the interface mismatch warning unit 181.

  Next, the upstream interface change process will be described.

FIG. 42 is a flowchart showing an example of the flow of an upstream interface change process in which the task definition changing unit 330 changes the upstream interface of a task in this embodiment.
In addition, about the process which is common in the already demonstrated process, the same code | symbol is attached | subjected and description is abbreviate | omitted here.

  The upstream interface change process includes a selected task definition acquisition step S41, an upstream task definition acquisition step S42, a selected task upstream interface change step S81, an upstream task downstream interface change step S82, a task hierarchy determination step S54, a general task definition acquisition step S55, an upstream Task hierarchy determination steps S83 and S93, general task identity determination step S84, upstream general task definition acquisition steps S85 and S95, upstream general task downstream change steps S86 and S96, general task upstream change step S87, and changed task definition storage step S88. .

In the selected task upstream changing step S81, the upstream interface changing unit 345 inputs the selected task definition data output from the selected task definition acquiring unit 331 in the selected task definition acquiring step S41 using a processing device such as the CPU 911.
The upstream interface change unit 345 inputs the upstream interface change instruction information output from the upstream interface change input unit 325 using a processing device such as the CPU 911.
The upstream interface changing unit 345 uses a processing device such as the CPU 911 to determine the upstream task that is the other party whose interface is to be changed from the input upstream interface change instruction information.
The upstream interface change unit 345 uses a processing device such as the CPU 911 to acquire interface data indicating the changed upstream interface from the input upstream interface change instruction information.
The upstream interface changing unit 345 uses the processing device such as the CPU 911 to change the upstream interface data corresponding to the upstream task data indicating the determined upstream task among the input selected task definition data to the acquired interface data.
The upstream interface changing unit 345 outputs the changed selected task definition data using a processing device such as the CPU 911.

In the upstream task downstream change step S82, the upstream interface change unit 345 uses the processing device such as the CPU 911 to change the selected task upstream from the upstream task definition data output by the upstream task definition acquisition unit 332 in the upstream task definition acquisition step S42. The upstream task definition data that defines the upstream task determined in step S81 is input.
The upstream interface changing unit 345 uses a processing device such as the CPU 911 to obtain the downstream interface data corresponding to the downstream task data indicating the selected task from the input upstream task definition data in the selected task upstream changing step S81. Change to data.
The upstream interface changing unit 345 outputs the changed upstream task definition data using a processing device such as the CPU 911.

In the task hierarchy determination step S54, when the general task definition acquisition unit 338 determines that the selected task is a detailed task, the process proceeds to the general task definition acquisition step S55.
When it is determined that the task is a general task, the process proceeds to the upstream task hierarchy determination step S93.

In the upstream task hierarchy determination steps S83 and S93, the general task definition acquisition unit 338 inputs the upstream task definition data output by the upstream task definition change unit 342 in the upstream task downstream change step S82 using a processing device such as the CPU 911. .
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to determine whether the upstream task is a general task or a detailed task based on the task hierarchy data included in the input upstream task definition data.

When it is determined in the upstream task hierarchy determination step S83 that the upstream task is a general task, the process proceeds to the general task upstream change step S87.
If it is determined in the upstream task hierarchy determination step S83 that the upstream task is a detailed task, the process proceeds to the general task identity determination step S84.

If it is determined in the upstream task hierarchy determination step S93 that the upstream task is a general task, the process proceeds to the changed task definition storage step S88.
When it is determined in the upstream task hierarchy determination step S93 that the upstream task is a detailed task, the process proceeds to the upstream general task definition acquisition step.

In the general task identity determination step S84, the general task definition acquisition unit 338 uses the processing device such as the CPU 911 to execute the upstream task based on the general task data included in the upstream task definition data input in the upstream task hierarchy determination step S83. Determine the general task.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to determine whether the general task of the determined upstream task is the same as the general task (of the selected task) determined in the general task definition acquisition step S55. To do.
When it is determined that the general task of the upstream task and the general task of the selected task are the same, the process proceeds to the changed task definition storage step S88.
If it is determined that the general task of the upstream task is different from the general task of the selected task, the process proceeds to the upstream general task definition acquisition step S85.

In the upstream general task definition acquisition steps S85 and S95, the general task definition acquisition unit 338 uses the processing device such as the CPU 911 to convert the general task data included in the upstream task definition data input in the upstream task hierarchy determination steps S83 and S93. Based on this, the general task of the upstream task is determined.
The general task definition acquisition unit 338 inputs task definition data that defines the determined general task from the task definition data stored in the task definition storage unit 312 using a processing device such as the CPU 911.
The general task definition acquisition unit 338 outputs the input task definition data as upstream general task definition data using a processing device such as the CPU 911.

In the upstream general task downstream changing steps S86 and S96, the general task definition changing unit 348 uses the processing device such as the CPU 911 and the upstream general task output by the general task definition acquiring unit 338 in the upstream general task definition acquiring steps S85 and S95. Enter definition data.
The general task definition changing unit 348 inputs the upstream interface change instruction information output from the upstream interface change input unit 325 using a processing device such as the CPU 911.
The general task definition changing unit 348 uses a processing device such as the CPU 911 to acquire interface data indicating the changed upstream interface from the input upstream interface change instruction information.
The general task definition changing unit 348 uses the processing device such as the CPU 911 to change the downstream interface data corresponding to the downstream task data indicating the selected task among the input upstream general task definition data to the acquired interface data.
The general task definition changing unit 348 outputs the changed upstream general task definition data using a processing device such as the CPU 911.

In the general task upstream change step S87, the general task definition change unit 348 inputs the general task definition data output by the general task definition acquisition unit 338 in the general task definition acquisition step S55 using a processing device such as the CPU 911.
The general task definition changing unit 348 uses a processing device such as the CPU 911 to, among the input general task definition data, the upstream interface data corresponding to the upstream task data indicating the upstream task, and the interface data indicating the changed upstream interface. Change to
The general task definition changing unit 348 outputs the changed general task definition data using a processing device such as the CPU 911.

In the changed task definition storage step S88, the task definition storage unit 312 inputs the selected task definition data output from the upstream interface change unit 345 in the selected task upstream change step S81 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the upstream task definition data output from the upstream interface change unit 345 in the upstream task downstream change step S82 using a processing device such as the CPU 911.
The task definition storage unit 312 inputs the upstream general task definition data output by the general task definition change unit 348 in the upstream general task downstream change steps S86 and S96 using a processing device such as the CPU 911, if any.
The task definition storage unit 312 inputs the general task definition data output from the general task definition change unit 348 in the general task upstream change step S87 using a processing device such as the CPU 911, if any.
The task definition storage unit 312 uses the storage device such as the magnetic disk device 920 to input the selected selection task definition data and the upstream task definition data (if any, the upstream general task definition data and the general task definition data). Remember.

  Next, how the task definition data stored in the task definition storage unit 312 changes due to the above-described upstream interface change process will be described using a specific example.

It is assumed that the task definition storage unit 312 stores the task definition data shown in FIG. 41 before the upstream interface change process.
The operator 812 operates the keyboard 902 and the mouse 903 of the terminal device 200 to select the task “Process B2”, and the executor “Actor3” of the upstream interfaces of the selected task “Process B2” executes. It is assumed that an instruction to change the upstream interface having the task “Process B1” as an upstream task to an interface defined by the interface template data of the file name “DataFile23” is input.
Instead of selecting a task first, the interface to be changed may be directly selected by clicking an arrow on the screen.

The selected task input unit 321 inputs an operation of the operator 812 by using an input device such as a keyboard 902 or a mouse 903 of the terminal device 200 to input the selected task “Process B2”.
The selected task input unit 321 outputs task identification data “TaskB2” indicating the selected task “Processing B2” using a processing device such as the CPU 911.

The upstream interface change input unit 325 inputs the upstream interface change instruction information by inputting the operation of the operator 812 using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200.
The upstream interface change input unit 325 outputs the input upstream interface change instruction information using a processing device such as the CPU 911.
The upstream interface change instruction information includes the task identification data “TaskB3” (hereinafter referred to as “changed upstream task data”) indicating the upstream task (“Actor3”) “Process B1” that is the partner whose interface is to be changed, and the change. Interface data “DataFile 23” (hereinafter referred to as “changed interface data”) indicating a later upstream interface is included.

The interface change authority determination unit 152 inputs the upstream interface change instruction information output from the upstream interface change input unit 325 using a processing device such as the CPU 911.
The interface change authority determination unit 152 acquires the changed upstream task data “TaskB3” from the input interface change instruction information using a processing device such as the CPU 911.
The interface change authority determination unit 152 uses a processing device such as the CPU 911 to define task definition data 525c that defines the task indicated by the changed upstream task data “TaskB3” acquired from the task definition data stored in the task definition storage unit 312. Enter.
The interface change authority determining unit 152 uses a processing device such as the CPU 911 to search the “Actor” field from the input task definition data 525 c and obtain task executor data “Actor 3”.
The interface change authority determination unit 152 uses a processing device such as the CPU 911 to define an executor indicated by the acquired task executor data “Actor3” from the executor definition data stored in the executor definition storage unit 311. Enter definition data.
The interface change authority determination unit 152 uses a processing device such as the CPU 911 to perform an operation having a change authority to change a task executed by the executor indicated by the task executor data “Actor3” based on the input executor definition data. Determine who is. In this example, the interface change authority determining unit 152 determines that the operator having the change authority is the operator 813.
The interface change authority determination unit 152 uses a processing device such as the CPU 911 to determine whether the operator 812 who has input the interface change instruction information has change authority based on the determined operator. In this example, the interface change authority determination unit 152 determines that the operator 812 has no change authority.
The interface change authority determination unit 152 outputs data indicating the determination result and data indicating the determined operator 813 using a processing device such as the CPU 911.

The interface change request notification unit 162 inputs data indicating the determination result output by the interface change authority determination unit 152 and data indicating the operator 813 using a processing device such as the CPU 911.
Since the interface change authority determining unit 152 determines that the operator 812 does not have the change authority, the interface change request notifying unit 162 uses the processing device such as the CPU 911 to change the upstream interface change output by the upstream interface change input unit 325. Enter instruction information.
The interface change request notification unit 162 uses a processing device such as the CPU 911 to generate a message requesting the operator 813 to approve interface change based on the input upstream interface change instruction information.
The interface change request notification unit 162 displays the generated message using the display device 901 such as the CRT of the terminal device 200 of the operator 813, thereby requesting the operator 813 to approve the interface change. To be notified.

  The operator 813 looks at the displayed message and determines whether to approve the interface change. In this example, it shall be approved. The operator 813 operates the keyboard 902 and the mouse 903 of the terminal device 200 to input that the change is approved.

The interface change approval / disapproval input unit 172 inputs interface change approval / disapproval information indicating the cause of the change by inputting the operation of the operator 813 using an input device such as the keyboard 902 or the mouse 903 of the terminal device 200.
The interface change approval / disapproval input unit 172 outputs the input interface change approval / disapproval information using a processing device such as the CPU 911.

The task definition changing unit 330 inputs the interface change acceptance / rejection information output from the interface change acceptance / rejection input unit 172 using a processing device such as the CPU 911.
The task definition changing unit 330 starts the upstream interface changing process by using a processing device such as the CPU 911 because the input interface change permission / denial information indicates approval of the change.

In the selected task definition acquisition step S41, the selected task definition acquisition unit 331 inputs the task identification data “TaskB2” output from the selected task input unit 321 using a processing device such as the CPU 911.
Using the processing device such as the CPU 911, the selected task definition acquisition unit 331 generates task definition data 525c that defines a task indicated by the input task identification data “TaskB2” from the task definition data stored in the task definition storage unit 312. input.
The selected task definition acquisition unit 331 outputs the input task definition data 525c using a processing device such as the CPU 911.

In the upstream task definition acquisition step S42, the upstream task definition acquisition unit 332 inputs the task definition data 525c output from the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
Using the processing device such as the CPU 911, the upstream task definition acquisition unit 332 searches the “UpperTask1” field from the input task definition data 525c, and acquires the upstream task data “TaskB1”. Similarly, the upstream task definition acquisition unit 332 searches the “UpperTask2” field from the task definition data 525c, and acquires the upstream task data “TaskB3”.
The upstream task definition acquisition unit 332 uses a processing device such as the CPU 911 and task definition data 524b for defining a task indicated by the acquired upstream task data “TaskB1” from the task definition data stored in the task definition storage unit 312. Then, the task definition data 526d defining the task indicated by the acquired upstream task data “TaskB3” is input.

  The upstream task definition acquisition unit 332 inputs upstream interface change instruction information using a processing device such as the CPU 911, acquires the changed upstream task data “TaskB3”, and defines the task indicated by “TaskB3”. Task definition data 526d may be input.

  The upstream task definition acquisition unit 332 outputs the input task definition data 524b and task definition data 526d using a processing device such as the CPU 911.

In the selected task upstream changing step S81, the upstream interface changing unit 345 inputs the task definition data 525c output from the selected task definition acquiring unit 331 in the selected task definition acquiring step S41 using a processing device such as the CPU 911.
The upstream interface change unit 345 inputs the upstream interface change instruction information output from the upstream interface change input unit 325 using a processing device such as the CPU 911.
The upstream interface changing unit 345 acquires the changed upstream task data “TaskB3” and the changed interface data “DataFile23” from the input upstream interface change instruction information using a processing device such as the CPU 911.

The upstream interface changing unit 345 searches for the “UpperTask1” field from the input task definition data 525c using a processing device such as the CPU 911, and acquires the upstream task data “TaskB1”. Similarly, the upstream interface changing unit 345 searches the “UpperTask2” field from the task definition data 525c, and acquires the upstream task data “TaskB3”.
The upstream interface changing unit 345 uses a processing device such as the CPU 911 to search the acquired upstream task data for a match with the changed upstream task data “TaskB3”. In this example, the upstream task data in the “UpperTask2” column matches.
The upstream interface changing unit 345 searches for and changes the upstream interface data corresponding to the matched upstream task data from the input task definition data 525c using a processing device such as the CPU 911. In this example, the upstream interface change unit 345 searches the “UpperTask2_IFData” field from the task definition data 525c, and changes the upstream interface data to the acquired changed interface data “DataFile23”.

  The upstream interface changing unit 345 outputs the changed task definition data 525c using a processing device such as the CPU 911.

In the upstream task downstream change step S82, the upstream interface change unit 345 uses a processing device such as the CPU 911, from among the task definition data 524b and 526d output by the upstream task definition acquisition unit 332 in the upstream task definition acquisition step S42. The task definition data 526d for defining the task indicated by the changed upstream task data “TaskB3” acquired in the selected task upstream changing step S81 is input.
The upstream interface changing unit 345 inputs the task identification data “TaskB2” output from the selected task input unit 321 using a processing device such as the CPU 911.

The upstream interface changing unit 345 uses a processing device such as the CPU 911 to search the “Lower Task 1” field from the input task definition data 526d and obtain the downstream task data “Task B2”. Similarly, the “Lower Task 2” column, the “Lower Task 3” column... Are searched, and if there are a plurality of pieces of downstream task data, all are acquired.
The upstream interface changing unit 345 uses a processing device such as the CPU 911 to search the acquired downstream task data for a match with the input task identification data “TaskB2”.
The upstream interface change unit 345 searches for and changes the downstream interface data corresponding to the matched downstream task data from the input task definition data 526d using a processing device such as the CPU 911. In this example, the upstream interface changing unit 345 searches the “LowerTask1_IFData” field from the task definition data 526d, and changes the downstream interface data to the changed interface data “DataFile23” acquired in the selected task upstream changing step S81.

  The upstream interface changing unit 345 outputs the changed task definition data 526d using a processing device such as the CPU 911.

In the task hierarchy determination step S54, the general task definition acquisition unit 338 inputs the task definition data 525c output from the selection task definition acquisition unit 331 in the selection task definition acquisition step S41 using a processing device such as the CPU 911.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to search the “Work” column from the input task definition data 525c, and acquires the task hierarchy data “Yes”.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to determine whether the selected task is a general task or a detailed task based on the acquired task hierarchy data. In this example, since the acquired task hierarchy data is “Yes”, the general task definition acquisition unit 338 determines that the selected task is a detailed task, and proceeds to the general task definition acquisition step S55.

In the general task definition acquisition step S55, the general task definition acquisition unit 338 uses a processing device such as the CPU 911 to search the “BelongTo” field from the task definition data 525c input in the task hierarchy determination step S54 and search for the general task data “ "TaskB" is acquired.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to extract task definition data 522d that defines a task indicated by the acquired general task data “TaskB” from the task definition data stored in the task definition storage unit 312. input.
The general task definition acquisition unit 338 outputs the input task definition data 522d using a processing device such as the CPU 911.

In the upstream task hierarchy determination step S83, the general task definition acquisition unit 338 inputs the task definition data 526d output from the upstream interface change unit 345 in the upstream task downstream change step S82 using a processing device such as the CPU 911.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to search the “Work” field from the input task definition data 526d and acquires the task hierarchy data “Yes”.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to determine whether the upstream task is a general task or a detailed task based on the acquired task hierarchy data. In this example, since the acquired task hierarchy data is “Yes”, the general task definition acquisition unit 338 determines that the upstream task is a detailed task, and proceeds to the general task identity determination step S84.

In the general task identity determination step S84, the general task definition acquisition unit 338 uses a processing device such as the CPU 911 to search the “BelongTo” field from the task definition data 526d input in the upstream task hierarchy determination step S84, and acquires the general task data. Obtain “TaskB”.
The general task definition acquisition unit 338 compares the acquired general task data “TaskB” with the general task data “TaskB” acquired in the general task definition acquisition step S55 by using a processing device such as the CPU 911 and determines whether they match. Determine whether or not. In this example, since they match, the process proceeds to the changed task definition storage step S88.

When the general task of the selected task is different from the general task of the upstream task, the interface to be changed is an interface between the general tasks, so the interface of the general task needs to be changed.
On the other hand, when the general task of the selected task and the general task of the upstream task are the same, the interface to be changed is an interface inside the general task, and therefore it is not necessary to change the interface of the general task.

In the changed task definition storage step S88, the task definition storage unit 312 receives the task definition data 525c output from the upstream interface change unit 345 in the selected task upstream change step S81 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the task definition data 526d output from the upstream interface change unit 345 in the upstream task downstream change step S82 using a processing device such as the CPU 911.
The task definition storage unit 312 stores input task definition data 525c and task definition data 526d using a storage device such as a magnetic disk device 920.
If the task definition storage unit 312 has already stored task definition data including the same task identification data as the task identification data included in the input task definition data, the task definition storage unit 312 uses the processing device such as the CPU 911 to store the old task definition data. Delete task definition data.

FIG. 43 is a diagram showing an example of task definition data changed by the upstream interface change process in this embodiment.
Note that the underline in the task definition data is a mark indicating a part changed from the task definition data in FIG. 41 and is not a part of the task definition data.

  The task definition data stored in the task definition storage unit 312 remains six. Among these, task definition data 521c, task definition data 522d, task definition data 523b, and task definition data 525b are not changed. The task definition data 525e is task definition data 525c changed by the upstream interface changing unit 345. The task definition data 526e is task definition data 526d changed by the upstream interface changing unit 345. The old task definition data 525c and task definition data 526d have been deleted.

An example of a display screen displayed on the display device 901 of the terminal device 200 based on the task definition data is shown on the lower side.
In this example, details of the interface are not displayed, but compared with FIG. 41, the warning “IF undefined” on the right side disappears, indicating that the interface is defined.

  Next, the downstream interface change process will be described.

FIG. 44 is a flowchart showing an example of the flow of the downstream interface change process in which the task definition changing unit 330 changes the downstream interface of the task in this embodiment.
In addition, about the process which is common in the already demonstrated process, the same code | symbol is attached | subjected and description is abbreviate | omitted here.

Downstream interface change processing includes selected task definition acquisition step S41, downstream task definition acquisition step S43, selected task downstream change step T81, downstream task upstream change step T82, task hierarchy determination step S54, general task definition acquisition step S55, downstream task hierarchy. It has determination steps T83 and T93, general task identical determination step T84, downstream general task definition acquisition steps T85 and T95, downstream general task upstream change steps T86 and T96, general task downstream change step T87, and changed task definition storage step T88.
Each process of the downstream interface change process is the same as each process of the upstream interface change process except that “upstream” and “downstream” are reversed, and thus the detailed description of the process is omitted. .

  Next, how the task definition data stored in the task definition storage unit 312 changes by the downstream interface change process will be described using a specific example.

It is assumed that the task definition storage unit 312 stores the task definition data shown in FIG. 43 before the upstream interface change process.
The operator 812 operates the keyboard 902 and the mouse 903 of the terminal device 200 to select the task “Process B2”, and sets the downstream interface of the selected task “Process B2” as the interface template data of the file name “DataFile24”. It is assumed that an instruction to change to the specified interface has been input.

  The description of the processing similar to the specific example of the upstream interface change processing described above is omitted, and only the processing flow is greatly different will be described.

In the downstream task hierarchy determination step T83, the general task definition acquisition unit 338 inputs the task definition data 523b output by the downstream interface change unit 346 in the downstream task upstream change step T82 using a processing device such as the CPU 911.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to search the “Work” column from the input task definition data 523b and acquires the task hierarchy data “Non”.
The general task definition acquisition unit 338 uses a processing device such as the CPU 911 to determine whether the downstream task is a general task or a detailed task based on the acquired task hierarchy data. In this example, since the acquired task hierarchy data is “Non”, the general task definition acquisition unit 338 determines that the downstream task is the general task, and proceeds to the general task downstream change step T87.

In the general task downstream change step T87, the general task definition change unit 348 inputs the task definition data 522d output by the general task definition acquisition unit 338 in the general task definition acquisition step S55 using a processing device such as the CPU 911.
The general task definition change unit 348 inputs the downstream interface change instruction information output from the downstream interface change input unit 326 using a processing device such as the CPU 911.
The general task definition changing unit 348 acquires the changed downstream task data “TaskC” and the changed interface data “DataFile24” from the input downstream interface change instruction information using a processing device such as the CPU 911.

The general task definition changing unit 348 uses a processing device such as the CPU 911 to search the “Lower Task 1” field from the input task definition data 522d, and acquires the downstream task data “Task C”. Similarly, the “Lower Task 2” column, the “Lower Task 3” column... Are searched, and if there are a plurality of pieces of downstream task data, all are acquired.
The general task definition changing unit 348 uses a processing device such as the CPU 911 to search the acquired downstream task data for a match with the changed downstream task data “TaskC”.
The general task definition changing unit 348 uses a processing device such as the CPU 911 to search and change the downstream interface data corresponding to the matched downstream task data from the input task definition data 522d. In this example, the general task definition changing unit 348 searches the “LowerTask1_IFData” field from the task definition data 522d, and changes the downstream interface data to the acquired changed interface data “DataFile24”.

  The general task definition changing unit 348 outputs the changed task definition data 522d using a processing device such as the CPU 911.

In the changed task definition storage step T88, the task definition storage unit 312 receives the task definition data 525e output from the downstream interface change unit 346 in the selected task downstream change step T81 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the task definition data 523b output from the downstream interface change unit 346 in the downstream task upstream change step T82 using a processing device such as the CPU 911.
The task definition storage unit 312 receives the task definition data 522d output by the general task definition change unit 348 in the general task downstream change step T87 using a processing device such as the CPU 911.
The task definition storage unit 312 stores input task definition data 525e, task definition data 523b, and task definition data 522d using a storage device such as a magnetic disk device 920.
If the task definition storage unit 312 has already stored task definition data including the same task identification data as the task identification data included in the input task definition data, the task definition storage unit 312 uses the processing device such as the CPU 911 to store the old task definition data. Delete task definition data.

FIG. 45 is a diagram showing an example of task definition data changed by the downstream interface changing process in this embodiment.
Note that the underline in the task definition data is a mark indicating a part changed from the task definition data in FIG. 43 and is not a part of the task definition data.

  The task definition data stored in the task definition storage unit 312 remains six. Among these, the task definition data 521c, the task definition data 524b, and the task definition data 526e are not changed. The task definition data 522f is task definition data 522d changed by the general task definition changing unit 348. The task definition data 523f is task definition data 523b changed by the downstream interface changing unit 346. The task definition data 525f is task definition data 525e changed by the downstream interface changing unit 346. The old task definition data 522d, task definition data 523b, and task definition data 525e are deleted.

An example of a display screen displayed on the display device 901 of the terminal device 200 based on the task definition data is shown on the lower side.
In this example, since the details of the interface are not displayed, the display does not change from the display screen shown in FIG.

  Next, a workflow creation work flow using the workflow generation system 800 in this embodiment will be described.

FIG. 46 is a flowchart showing an example of a workflow creation work flow using the workflow generation system 800 in this embodiment.
The workflow creation work includes a main flow creation process T11, a task distribution process T12, a task detailing process T13, an input / output definition process T14, a detailed task determination process T15, and a detailed task storage process T16.

In the main flow creation step T11, an operator 811 (an operator having the authority to manage the whole) uses the workflow generation system 800 to create an overall workflow.
The operator 811 inputs general tasks that constitute the entire work flow. Further, the operator 811 may roughly define the general task interface at this point.
The operation of the operator 811 is input by the task definition change input unit 320, the task definition change unit 330 generates task definition data, and the task definition storage unit 312 stores it.

In the task allocation step T12, the operator 811 uses the workflow generation system 800 to allocate the general task input in the main flow creation step T11 to the performer.
The operator 811 inputs an executor who executes the general task.
The operation of the operator 811 is input by the task definition change input unit 320 (executor change input unit 324), the task definition change unit 330 (executor change unit 344) changes the task definition data, and the task definition storage unit 312 memorizes.

In the task detailing step T13, the operator 812 / operator 813 uses the workflow generation system 800 to detail the general tasks allocated to the performers managed by the operator 812 / operator 813.
The operator 812 / operator 813 adds a detailing task or changes an executor.
The operation of the operator 812 / operator 813 is input by the task definition change input unit 320, the task definition change unit 330 changes the task definition data, and is stored in the task definition storage unit 312.
When there is a change exceeding the change authority, the task definition storage unit 312 stores the provisional temporary task definition data. When storing the task definition storage unit 312 as temporary provisional task definition data, the task definition storage unit 312 keeps old task definition data without deleting it.

In the input / output definition process T14, the operator 812 / operator 813 uses the workflow generation system 800 to input the interface of the detailed task assigned to the performer managed by each.
The operations of the operator 812 / operator 813 are input by the task definition change input unit 320 (upstream interface change input unit 325 / downstream interface change input unit 326), and the task definition change unit 330 (upstream interface change unit 345 / downstream interface). The change unit 346) changes the task definition data, and the task definition storage unit 312 stores it.
Similarly, when there is a change exceeding the change authority, the task definition storage unit 312 stores temporary provisional task definition data.

In the detailed task determination step T15, the operator 812 / operator 813 uses the workflow generation system 800 to know a change made by another operator. When a change by another operator is involved in the change authority of the operator, the operator 812 / operator 813 inputs whether to approve or reject the change.
The operation of the operator 812 / operator 813 is input by the task definition change permission / inhibition input unit 370.

  In the detailed task storage step T16, the task definition storage unit 312 stores the change based on the approval / rejection input in the detailed task determination step T15. That is, when the change is approved, the task definition storage unit 312 confirms provisional temporary task definition data and deletes old task definition data. If the change is rejected, the temporary provisional task definition data is deleted.

  The above processing is repeated to complete one workflow.

  When the workflow is completed, the task definition data stored in the task definition storage unit 312 is used to output a workflow diagram and a work definition document, and the workflow management apparatus manages the actual work.

In this way, a plurality of operators can create workflows with their respective authority ranges, and as a result, one huge workflow can be created with no contradiction as a whole.
Since each operator makes a change within his authority range, even if another operator makes a change before the change of one operator is confirmed, it is possible to prevent the workflow from being inconsistent.
Since the authority range of each operator is determined based on the task performer, the authority range of the operator can be determined in accordance with the actual organization configuration.

  Further, the task is changed by taking over the old task definition data stored in the task definition storage unit 312 and changing / adding a part of the old task definition data, so that the data once inputted can be used effectively.

The workflow generation system 800 (workflow generation apparatus) in this embodiment
An input device such as a keyboard 902 and a mouse 903 for inputting information, a storage device such as a magnetic disk device 920 for storing information, a processing device such as a CPU 911 for processing information, and a display device 901 such as a CRT for outputting information. And an output device such as a printer device 906, a task definition storage unit 312, a task definition change input unit 320, a task definition change authority determination unit 350, a task definition change request notification unit 360, and a task definition change approval / disapproval input unit 370. And a task definition changing unit 330.
The task definition storage unit 312 stores task definition data that defines a task using a storage device such as a magnetic disk device 920.
The task definition change input unit 320 inputs task definition change instruction information indicating that the operator has instructed to change the task definition data stored in the task definition storage unit 312 using an input device such as a keyboard 902 or a mouse 903. It is characterized by doing.
The task definition change authority determination unit 350 uses a processing device such as the CPU 911 to allow the operator who has instructed the task definition change instruction information input by the task definition change input unit 320 to input the task definition data. It is characterized in that it is determined whether or not the user has a change authority to change.
The task definition change request notification unit 360 uses an output device such as a display device 901 such as a CRT or a printer device 906 when the task definition change authority determination unit 350 determines that the operator does not have the change authority. , Notifying other operators having the authority to change the task definition data to request approval of the change of the task definition data.
The task definition change approval / disapproval input unit 370 uses an input device such as a keyboard 902 or a mouse 903 to determine whether another operator notified by the task definition change request notification unit 360 approves the change of the task definition data. The task definition change approval / disapproval information is input.
When the task definition change approval / disapproval information input by the task definition change approval / disapproval input unit 370 indicates that another operator approves the change of the task definition data, the task definition change unit 330 displays a processing device such as the CPU 911. The task definition data is generated based on the task definition change instruction information input by the task definition change input unit 320 and used as changed task definition data.
The task definition storage unit 312 further stores the changed task definition data generated by the task definition change unit 330 as task definition data using a storage device such as the magnetic disk device 920.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, a plurality of operators create a workflow by changing task definition data within their own authority range, and the operator exceeds the authority range. When the change is instructed, the task definition changing unit 330 changes the task definition data with the approval of the operator having the change authority, so that a plurality of operators cooperate to generate one huge workflow. There is an effect that can be.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The task definition storage unit 312 uses a storage device such as a magnetic disk device 920 to store data including task executor data indicating an executor executing the task as task definition data.
The task definition change input unit 320 includes a selected task input unit 321 and an executor change input unit 324.
The selected task input unit 321 inputs a task selected by the operator from tasks defined by the task definition data stored in the task definition storage unit 312 as a selected task, using an input device such as a keyboard 902 or a mouse 903. It is characterized by.
The executor change input unit 324 uses an input device such as a keyboard 902 or a mouse 903 to change the executor who executes the selected task input by the selected task input unit 321 as task definition change instruction information. It is characterized in that executor change instruction information indicating the instruction is input.
The task definition change authority determination unit 350 (executor change authority determination unit 151) uses a processing device such as the CPU 911 to execute the changed executor instructed by the executor change instruction information input by the executor change input unit 324. When the operator has the authority to change the task executed by the operator, it is determined that the operator has the authority to change.
The task definition change unit 330 includes a selected task definition acquisition unit 331 and an executor change unit 344.
The selected task definition acquisition unit 331 uses a processing device such as the CPU 911 to define a task definition that defines the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as selected task definition data. It is characterized by acquiring data.
The executor change unit 344 indicates that the task definition change approval / disapproval information input by the task definition change approval / disapproval input unit 370 (executor change approval / disapproval input unit 171) indicates that the other operator approves the change of the executor. The executor change input unit 324 inputs task executor data included in the selected task definition data acquired by the selected task definition acquisition unit 331 as changed task definition data using a processing device such as the CPU 911. The task definition data changed to the task executor data indicating the executor after the change instructed by the change instruction information is generated.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, the change authority of the operator is determined based on the task performer, and the change is performed when the task performer is changed to an executer outside the authority range. With the approval of another operator who has the change authority for the task of the subsequent performer, the executer change unit 344 changes the task definition data, so that it is possible to distribute the authority corresponding to the actual organizational structure, There is an effect that a plurality of operators can cooperate to create one huge workflow.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The task definition storage unit 312 uses a storage device such as the magnetic disk device 920, and as an upstream interface that represents a format in which an upstream task that outputs information input by the task to the task is output as task definition data. Data including data and downstream interface data representing a format in which the task outputs information is stored for a downstream task that inputs information output from the task from the task.
The task definition change input unit 320 includes a selected task input unit 321 and an upstream interface change input unit 325.
The selected task input unit 321 inputs a task selected by the operator from tasks defined by the task definition data stored in the task definition storage unit 312 as a selected task, using an input device such as a keyboard 902 or a mouse 903. It is characterized by.
The upstream interface change input unit 325 uses the input device such as the keyboard 902 or the mouse 903 to change the format in which the selected task input by the selected task input unit 321 inputs information as task definition change instruction information. Upstream interface change instruction information indicating that the instruction is issued is input.
The task definition change authority determining unit 350 (interface change authority determining unit 152) has the authority to change the upstream task of the selected task input by the selected task input unit 321 using a processing device such as the CPU 911. In this case, it is determined that the operator has change authority.
The task definition change unit 330 includes a selected task definition acquisition unit 331, an upstream task definition acquisition unit 332, and an upstream interface change unit 345.
The selected task definition acquisition unit 331 uses a processing device such as the CPU 911 to define a task definition that defines the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as selected task definition data. It is characterized by acquiring data.
The upstream task definition acquisition unit 332 uses a processing device such as the CPU 911 to obtain the upstream task of the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as upstream task definition data. It is characterized by acquiring task definition data to be defined.
The upstream interface change unit 345, when the task definition change approval / disapproval information input by the task definition change approval / disapproval input unit 370 (interface change approval / disapproval input unit 172) indicates that the other operator approves the format change. Using the processing device such as the CPU 911, the upstream interface change instruction information input by the upstream interface change input unit 325 includes the upstream interface data included in the selected task definition data acquired by the selected task definition acquisition unit 331 as the changed task definition data. The upstream interface change input unit 325 inputs the task definition data changed to the upstream interface data representing the format designated by the above and the downstream interface data included in the upstream task definition data acquired by the upstream task definition acquisition unit 332 Change And generating the task definition data changed on the downstream interface data representing the format indicated by the shown information.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when an operator instructs to change the interface between a downstream task having change authority and an upstream task not having change authority, the upstream task Since the upstream interface changing unit 345 changes the task definition data with the approval of another operator having the change authority, the occurrence of interface inconsistency can be prevented, and a plurality of operators cooperate, There is an effect that a workflow without contradiction can be created.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The task definition storage unit 312 uses a storage device such as the magnetic disk device 920, and as an upstream interface that represents a format in which an upstream task that outputs information input by the task to the task is output as task definition data. Data including data and downstream interface data representing a format in which the task outputs information is stored for a downstream task that inputs information output from the task from the task.
The task definition change input unit 320 includes a selected task input unit 321 and a downstream interface change input unit 326.
The selected task input unit 321 inputs a task selected by the operator from tasks defined by the task definition data stored in the task definition storage unit 312 as a selected task, using an input device such as a keyboard 902 or a mouse 903. It is characterized by.
The downstream interface change input unit 326 uses an input device such as a keyboard 902 or a mouse 903 to change the format in which the selected task input by the selected task input unit 321 outputs information as task definition change instruction information. Downstream interface change instruction information indicating that an instruction is issued is input.
The task definition change authority determining unit 350 (interface change authority determining unit 152) has the authority of the above operator to change the downstream task of the selected task input by the selected task input unit 321 using a processing device such as the CPU 911. In this case, it is determined that the operator has change authority.
The task definition change unit 330 includes a selected task definition acquisition unit 331, a downstream task definition acquisition unit 333, and a downstream interface change unit 346.
The selected task definition acquisition unit 331 uses a processing device such as the CPU 911 to define a task definition that defines the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as selected task definition data. It is characterized by acquiring data.
The downstream task definition acquisition unit 333 uses a processing device such as the CPU 911 to obtain the downstream task of the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as the downstream task definition data. It is characterized by acquiring task definition data to be defined.
The downstream interface changing unit 346, when the task definition change acceptance / rejection information input by the task definition change acceptance / rejection input unit 370 (interface change acceptance / rejection input unit 172) indicates that the other operator approves the change of the format Downstream interface change instruction information that the downstream interface change input unit 326 has input downstream interface data included in the selected task definition data acquired by the selected task definition acquisition unit 331 as changed task definition data using a processing device such as the CPU 911. The downstream interface change input unit 326 inputs the task definition data changed to the downstream interface data representing the format designated by the above and the upstream interface data included in the downstream task definition data acquired by the downstream task definition acquisition unit 333 Change And generating the task definition data changed upstream interface data representing an instruction format by shown information.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when an operator instructs to change the interface between an upstream task having change authority and a downstream task not having change authority, the downstream task Since the downstream interface changing unit 346 changes the task definition data with the approval of another operator who has the change authority, the occurrence of interface inconsistency can be prevented, and a plurality of operators cooperate, There is an effect that a workflow without contradiction can be created.

The workflow generation system 800 (workflow generation apparatus) in this embodiment further includes an interface inconsistency warning unit 181.
The task definition storage unit 312 uses a storage device such as the magnetic disk device 920, and as an upstream interface that represents a format in which an upstream task that outputs information input by the task to the task is output as task definition data. Data including data and downstream interface data representing a format in which the task outputs information is stored for a downstream task that inputs information output from the task from the task.
The interface inconsistency warning unit 181 is included in the format represented by the upstream interface data included in the task definition data stored in the task definition storage unit and the task definition data that defines the upstream task of the task defined by the task definition data. When the format represented by the downstream interface data does not match, an output device such as a display device 901 such as a CRT or a printer device 906 is used to warn the operator that the interface is inconsistent. And

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when an interface mismatch occurs, the interface mismatch warning unit 181 gives a warning, so that an interface mismatch can be easily found. This is advantageous in that a plurality of operators can cooperate to create a consistent workflow.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
If the upstream interface data included in the task definition data stored in the task definition storage unit indicates that the interface is undefined, the interface inconsistency warning unit 181 displays a display device 901 such as a CRT, a printer device 906, or the like. The output device is used to warn the operator that the interface is undefined.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when the interface is undefined, the interface inconsistency warning unit 181 gives a warning, so that it is possible to easily find the interface leakage. This is advantageous in that a plurality of operators can cooperate to create a consistent workflow.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The interface inconsistency warning unit 181 uses an output device such as a display device 901 such as a CRT or a printer device 906 to warn an operator who has the authority to change the task definition data.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, an interface inconsistency warning unit is provided to an operator having change authority to change a task having an inconsistent interface among a plurality of operators. Since 181 warns, the operator who receives the warning can modify the interface to make the interface consistent.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The interface inconsistency warning unit 181 uses a display device 901 such as a CRT and an output device such as a printer device 906 to warn an operator who has the authority to change task definition data that defines an upstream task of the task. It is characterized by doing.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, an interface is not provided to an operator having change authority to change an upstream task that is a partner of an inconsistent interface among a plurality of operators. Since the matching warning unit 181 gives a warning, there is an effect that the operator who has received the warning can modify the interface of the upstream task to match the interface.

The workflow generation system 800 (workflow generation apparatus) in this embodiment further includes an interface inconsistency warning unit 181.
The task definition storage unit 312 uses a storage device such as the magnetic disk device 920, and as an upstream interface that represents a format in which an upstream task that outputs information input by the task to the task is output as task definition data. Data including data and downstream interface data representing a format in which the task outputs information is stored for a downstream task that inputs information output from the task from the task.
The interface inconsistency warning unit 181 is included in the task definition data that defines the downstream interface data included in the task definition data stored in the task definition storage unit and the downstream task of the task defined by the task definition data. When the format represented by the upstream interface data does not match, an output device such as a display device 901 such as a CRT or a printer device 906 is used to warn the operator that the interface is inconsistent. And

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when an interface mismatch occurs, the interface mismatch warning unit 181 gives a warning, so that an interface mismatch can be easily found. This is advantageous in that a plurality of operators can cooperate to create a consistent workflow.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
When the downstream interface data included in the task definition data stored in the task definition storage unit indicates that the interface is undefined, the interface inconsistency warning unit 181 displays a display device 901 such as a CRT, a printer device 906, or the like. The output device is used to warn the operator that the interface is undefined.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when the interface is undefined, the interface inconsistency warning unit 181 gives a warning, so that it is possible to easily find the interface leakage. This is advantageous in that a plurality of operators can cooperate to create a consistent workflow.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The interface inconsistency warning unit 181 uses an output device such as a display device 901 such as a CRT or a printer device 906 to warn an operator who has the authority to change the task definition data.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, an interface inconsistency warning unit is provided to an operator having change authority to change a task having an inconsistent interface among a plurality of operators. Since 181 warns, the operator who receives the warning can modify the interface to make the interface consistent.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The interface inconsistency warning unit 181 uses an output device such as a display device 901 such as a CRT or an output device such as a printer device 906 to warn an operator who has a change authority to change task definition data that defines a task downstream of the task. It is characterized by doing.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, an interface is not provided to an operator who has change authority to change a downstream task that is a partner of an inconsistent interface among a plurality of operators. Since the matching warning unit 181 gives a warning, there is an effect that the operator who has received the warning can modify the interface of the downstream task to match the interface.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The task definition storage unit 312 uses a storage device such as the magnetic disk device 920, as task definition data, task identification data that identifies the task, detailed task data that indicates a detailed task that details the task, The upstream interface data representing the format in which the upstream task that outputs the information input by the task outputs the information, and the downstream task that receives the information output from the task from the task. Storing data including downstream interface data representing a format for outputting information.
The task definition change input unit 320 includes a selected task input unit 321 and a task detailing input unit 322.
The selected task input unit 321 inputs a task selected by the operator from tasks defined by the task definition data stored in the task definition storage unit 312 as a selected task, using an input device such as a keyboard 902 or a mouse 903. It is characterized by.
The task detailing input unit 322 uses the input device such as the keyboard 902 or the mouse 903 to indicate that the operator has instructed the detailing of the selected task input by the selected task input unit 321 as task definition change instruction information. The task detailing instruction information to be expressed is input.
The task definition changing unit 330 includes a selected task definition acquiring unit 331, a new task definition generating unit 347, and a selected task definition changing unit 341.
The selected task definition acquisition unit 331 uses a processing device such as the CPU 911 to define a task definition that defines the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as selected task definition data. It is characterized by acquiring data.
The new task definition generation unit 347 generates task identification data for identifying a new task as new task identification data using a processing device such as the CPU 911, and uses the processing device such as CPU 911 as changed task definition data. The generated new task identification data is included as task identification data, the upstream interface data included in the selected task definition data acquired by the selected task definition acquisition unit 331 is included as upstream interface data, and the selection acquired by the selected task definition acquisition unit 331 Task definition data including downstream interface data included in task definition data as downstream interface data is generated.
The selected task definition changing unit 341 uses the processing device such as the CPU 911 to change the selected task definition data acquired by the selected task definition acquiring unit 331 as the changed task definition data, and the new task definition generating unit 347 generates the changed task definition data. Task definition data including new task identification data as detailed task data is generated.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, another operator who is familiar with the work content defines the details of the work based on the task in which the operator has roughly defined the work. In this case, the original task is left and a detailed task in which the task is detailed is generated, so that both parties can communicate with each other and input data can be used effectively. Further, since the detailed task takes over the interface of the original task, inconsistency of the interface does not occur, and a workflow with no contradiction can be created.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The task definition storage unit 312 uses a storage device such as a magnetic disk device 920, and as a task definition data, the task definition storage unit 312 indicates a general task indicating the general task when the task is a detailed task that is a detailed task. Data including data is stored.
The new task definition generation unit 347 further includes task identification data included in the selected task definition data acquired by the selected task definition acquisition unit 331 as the changed task definition data, using the processing device such as the CPU 911, as approximate task data. It is characterized by generating task definition data.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when a certain task is detailed, the task definition data defining the detailed task includes the general task data indicating the original task. It is possible to easily determine the hierarchical relationship of tasks, and to produce a workflow with no contradiction.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The task definition storage unit 312 uses a storage device such as the magnetic disk device 920, and further includes, as task definition data, upstream task data indicating an upstream task of the task and downstream task data indicating a downstream task of the task. The data to be stored is stored.
The new task definition generation unit 347 includes the upstream task data included in the selected task definition data acquired by the selected task definition acquisition unit 331 as the changed task definition data using the processing device such as the CPU 911, and is selected. Task definition data including downstream task data included in selected task definition data acquired by the task definition acquisition unit 331 as downstream task data is generated.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, the task that has refined the task takes over the upstream task and the downstream task of the original task. There is an effect that a workflow can be created.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The task definition storage unit 312 uses a storage device such as the magnetic disk device 920, and further includes, as task definition data, upstream task data indicating an upstream task of the task and downstream task data indicating a downstream task of the task. The data to be stored is stored.
The task definition changing unit 330 further includes an upstream task definition acquiring unit 332, a downstream task definition acquiring unit 333, an upstream task definition changing unit 342, and a downstream task definition changing unit 343.
The upstream task definition acquisition unit 332 uses a processing device such as the CPU 911 to obtain the upstream task of the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as upstream task definition data. It is characterized by acquiring task definition data to be defined.
The downstream task definition acquisition unit 333 uses a processing device such as the CPU 911 to obtain the downstream task of the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as the downstream task definition data. It is characterized by acquiring task definition data to be defined.
The upstream task definition changing unit 342 uses a processing device such as the CPU 911 to select selected task definition acquisition unit 331 among the downstream task data included in the upstream task definition data acquired by the upstream task definition acquisition unit 332 as changed task definition data. The task definition data, which is the same as the task identification data included in the selected task definition data acquired by the above, is changed to data including the new task identification data generated by the new task definition generation unit 347, is generated.
The downstream task definition changing unit 343 uses a processing device such as the CPU 911 to select selected task definition acquisition unit 331 among the upstream task data included in the downstream task definition data acquired by the downstream task definition acquisition unit 333 as changed task definition data. The task definition data, which is the same as the task identification data included in the selected task definition data acquired by the above, is changed to data including the new task identification data generated by the new task definition generation unit 347, is generated.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when a task is detailed, the task definition data that defines the upstream task and the downstream task of the original task is changed to start from the upstream task. Since the downstream task seen and the upstream task seen from the downstream task are detailed tasks, the connection between tasks can be taken over, interface inconsistency does not occur, and a consistent workflow can be created There is an effect.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The task definition storage unit 312 uses a storage device such as a magnetic disk device 920, as task definition data, an upstream task that outputs task identification data for identifying the task and information input by the task to the task. Upstream interface data representing a format in which information is output; downstream interface data representing a format in which the task outputs information with respect to a downstream task that receives information output from the task; and upstream of the task Data including upstream task data indicating a task and downstream task data indicating a downstream task of the task is stored.
The task definition change input unit 320 includes a selected task input unit 321 and a task addition input unit 323.
The selected task input unit 321 inputs a task selected by the operator from tasks defined by the task definition data stored in the task definition storage unit 312 as a selected task, using an input device such as a keyboard 902 or a mouse 903. It is characterized by.
The task addition input unit 323 uses the input device such as the keyboard 902 and the mouse 903 to add other tasks to be executed after execution of the selected task input by the selected task input unit 321 as task definition change instruction information. The task addition instruction information indicating that the person has instructed is input.
The task definition changing unit 330 includes a selected task definition acquiring unit 331, a downstream task definition acquiring unit 333, a new task definition generating unit 347, a selected task definition changing unit 341, and a downstream task definition changing unit 343. Features.
The selected task definition acquisition unit 331 uses a processing device such as the CPU 911 to define a task definition that defines the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as selected task definition data. It is characterized by acquiring data.
The downstream task definition acquisition unit 333 uses a processing device such as the CPU 911 to obtain the downstream task of the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as the downstream task definition data. It is characterized by acquiring task definition data to be defined.
The new task definition generation unit 347 generates task identification data for identifying a new task as new task identification data using a processing device such as the CPU 911, and uses the processing device such as CPU 911 as changed task definition data. , Including the generated new task identification data as task identification data, the downstream interface data included in the selected task definition data acquired by the selected task definition acquisition unit 331 as downstream interface data, and the selection acquired by the selection task definition acquisition unit 331 Task definition data including task identification data included in the task definition data as upstream task data and downstream task data included in the selected task definition data acquired by the selected task definition acquisition unit 331 as downstream task data is generated. And
The selected task definition changing unit 341 uses a processing device such as the CPU 911 to convert the downstream task data included in the selected task definition data acquired by the selected task definition acquiring unit 331 as the new task definition generating unit 347 as changed task definition data. The task definition data changed to the new task identification data generated by is generated.
The downstream task definition changing unit 343 uses a processing device such as the CPU 911 to select selected task definition acquisition unit 331 among the upstream task data included in the downstream task definition data acquired by the downstream task definition acquisition unit 333 as changed task definition data. The task definition data, which is the same as the task identification data included in the selected task definition data acquired by, is changed to the new task identification data generated by the new task definition generation unit 347, is generated.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when adding a task to be executed after execution of a task, the downstream interface of the added new task takes over the downstream interface of the original task. There is an effect that an inconsistent interface does not occur and a consistent workflow can be created.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The new task definition generation unit 347 uses a processing device such as the CPU 911 to generate task definition data that further includes upstream interface data indicating that the interface is undefined as changed task definition data.
The selected task definition changing unit 341 uses a processing device such as the CPU 911 to generate task definition data in which downstream interface data is changed to downstream interface data indicating that the interface is undefined as changed task definition data. It is characterized by.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, since the interface between the original task and the added task is undefined, the operator needs to specify the interface. It is possible to notify, and there is an effect that a workflow without contradiction can be created.

  Note that the original downstream interface may be left as it is, instead of making the interface undefined.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The new task definition generation unit 347 further includes, as upstream interface data, downstream interface data included in the selected task definition data acquired by the selected task definition acquisition unit 331 as changed task definition data using a processing device such as the CPU 911. It is characterized by generating definition data.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, since the upstream interface of the added task is consistent with the downstream interface of the original task, it is not necessary to change the interface of the added task. In this case, there is no need to input an interface, so that the amount of work for the operator can be reduced and a consistent workflow can be created.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The task definition storage unit 312 uses a storage device such as a magnetic disk device 920, as task definition data, an upstream task that outputs task identification data for identifying the task and information input by the task to the task. Upstream interface data representing a format in which information is output; downstream interface data representing a format in which the task outputs information with respect to a downstream task that receives information output from the task; and upstream of the task Data including upstream task data indicating a task and downstream task data indicating a downstream task of the task is stored.
The task definition change input unit 320 includes a selected task input unit 321 and a task addition input unit 323.
The selected task input unit 321 inputs a task selected by the operator from tasks defined by the task definition data stored in the task definition storage unit 312 as a selected task, using an input device such as a keyboard 902 or a mouse 903. It is characterized by.
The task addition input unit 323 adds other tasks to be executed in parallel with the selected task input by the selected task input unit 321 as task definition change instruction information using an input device such as the keyboard 902 or the mouse 903. Task addition instruction information indicating that the operator has instructed is input.
The task definition change unit 330 includes a selected task definition acquisition unit 331, an upstream task definition acquisition unit 332, a downstream task definition acquisition unit 333, a new task definition generation unit 347, an upstream task definition change unit 342, and a downstream task definition. And a change unit 343.
The selected task definition acquisition unit 331 uses a processing device such as the CPU 911 to define a task definition that defines the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as selected task definition data. It is characterized by acquiring data.
The upstream task definition acquisition unit 332 uses a processing device such as the CPU 911 to obtain the upstream task of the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as upstream task definition data. It is characterized by acquiring task definition data to be defined.
The downstream task definition acquisition unit 333 uses a processing device such as the CPU 911 to obtain the downstream task of the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as the downstream task definition data. It is characterized by acquiring task definition data to be defined.
The new task definition generation unit 347 generates task identification data for identifying a new task as new task identification data using a processing device such as the CPU 911, and uses the processing device such as CPU 911 as changed task definition data. The generated new task identification data is included as task identification data, the upstream interface data included in the selected task definition data acquired by the selected task definition acquisition unit 331 is included as upstream interface data, and the selection acquired by the selected task definition acquisition unit 331 The downstream interface data included in the task definition data is included as downstream interface data, the upstream task data included in the selected task definition data acquired by the selected task definition acquisition unit 331 is included as upstream task data, and the selected task definition acquisition unit 331 acquires Shi And generating a task definition data including downstream task data contained in the selected task definition data as the downstream task data.
Using the processing device such as the CPU 911, the upstream task definition changing unit 342 converts the downstream task data included in the upstream task definition data acquired by the upstream task definition acquiring unit 332 as the changed task definition data, as a new task definition generating unit 347. The task definition data changed to the downstream task data including the new task identification data generated by is generated.
The downstream task definition changing unit 343 uses the processing device such as the CPU 911 to convert the upstream task data included in the downstream task definition data acquired by the downstream task definition acquiring unit 333 as the changed task definition data, as a new task definition generating unit 347. The task definition data changed to the upstream task data including the new task identification data generated by is generated.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when adding a task to be executed in parallel with a task, the interface of the added new task is the same as the interface of the original task. There is no need to change the downstream interface of the upstream task and the upstream interface of the downstream task, interface inconsistency does not occur, and a consistent workflow can be created.

  The time for executing the task to be added is not limited to the time after the execution of the selected task or in parallel with the execution of the selected task, but may be at another time. For example, it may be before execution of the selected task. The processing in this case is the same as the processing described above except that “upstream” and “downstream” are reversed.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The task definition storage unit 312 uses a storage device such as a magnetic disk device 920, as task definition data, an upstream task that outputs task identification data for identifying the task and information input by the task to the task. Upstream interface data representing a format in which information is output; downstream interface data representing a format in which the task outputs information with respect to a downstream task that receives information output from the task; and upstream of the task Data including upstream task data indicating a task and downstream task data indicating a downstream task of the task is stored.
The task definition change input unit 320 includes a selected task input unit 321 and a task addition input unit 323.
The selected task input unit 321 inputs a task selected by the operator from tasks defined by the task definition data stored in the task definition storage unit 312 as a selected task, using an input device such as a keyboard 902 or a mouse 903. It is characterized by.
The task addition input unit 323 uses the input device such as the keyboard 902 and the mouse 903 to add other tasks to be executed before execution of the selected task input by the selected task input unit 321 as task definition change instruction information. Task addition instruction information indicating that the operator has instructed is input.
The task definition changing unit 330 includes a selected task definition acquiring unit 331, an upstream task definition acquiring unit 332, a new task definition generating unit 347, a selected task definition changing unit 341, and an upstream task definition changing unit 342. Features.
The selected task definition acquisition unit 331 uses a processing device such as the CPU 911 to define a task definition that defines the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as selected task definition data. It is characterized by acquiring data.
The upstream task definition acquisition unit 332 uses a processing device such as the CPU 911 to obtain the upstream task of the selected task input by the selected task input unit 321 from the task definition data stored in the task definition storage unit 312 as upstream task definition data. It is characterized by acquiring task definition data to be defined.
The new task definition generation unit 347 generates task identification data for identifying a new task as new task identification data using a processing device such as the CPU 911, and uses the processing device such as CPU 911 as changed task definition data. The generated new task identification data is included as task identification data, the upstream interface data included in the selected task definition data acquired by the selected task definition acquisition unit 331 is included as upstream interface data, and the selection acquired by the selected task definition acquisition unit 331 Task definition data including task identification data included in the task definition data as downstream task data and upstream task data included in the selected task definition data acquired by the selected task definition acquisition unit 331 as upstream task data is generated. And
The selected task definition changing unit 341 uses the processing device such as the CPU 911 to convert the upstream task data included in the selected task definition data acquired by the selected task definition acquiring unit 331 as the new task definition generating unit 347 as changed task definition data. The task definition data changed to the new task identification data generated by is generated.
The upstream task definition changing unit 342 uses a processing device such as the CPU 911 to select selected task definition acquisition unit 331 among the downstream task data included in the upstream task definition data acquired by the upstream task definition acquisition unit 332 as changed task definition data. The task definition data, which is the same as the task identification data included in the selected task definition data acquired by, is changed to the new task identification data generated by the new task definition generation unit 347, is generated.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when adding a task to be executed before executing a task, the upstream interface of the added new task takes over the upstream interface of the original task. There is an effect that an inconsistent interface does not occur and a workflow without contradiction can be created.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The new task definition generation unit 347 uses a processing device such as the CPU 911 to generate task definition data further including downstream interface data indicating that the interface is undefined as changed task definition data.
The selected task definition changing unit 341 uses a processing device such as the CPU 911 to generate task definition data in which the upstream interface data is changed to upstream interface data indicating that the interface is undefined as changed task definition data. It is characterized by.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, since the interface between the original task and the added task is undefined, the operator needs to specify the interface. It is possible to notify, and there is an effect that a workflow without contradiction can be created.

  Note that the original upstream interface may be left as it is, instead of making the interface undefined.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The new task definition generation unit 347 uses a processing device such as the CPU 911 to further include, as changed task definition data, upstream interface data included in the selected task definition data acquired by the selected task definition acquisition unit 331 as downstream interface data. It is characterized by generating definition data.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, since the downstream interface of the added task is consistent with the upstream interface of the original task, there is no need to change the interface of the added task. In this case, there is no need to input an interface, so that the amount of work for the operator can be reduced and a consistent workflow can be created.

The workflow generation system 800 (workflow generation apparatus) in this embodiment is characterized by the following points.
The task definition storage unit 312 uses a storage device such as a magnetic disk device 920 as task definition data, and further includes detailed task data indicating a detailed task in which the above task is detailed, and the above task details the general task. Data including general task data indicating the general task is stored in the case of a detailed refinement task.
The task definition change unit 330 further includes a general task definition acquisition unit 338 and a general task definition change unit 348.
When the selected task input by the selected task input unit 321 is a detailed task obtained by refining the general task, the general task definition acquisition unit 338 uses a processing device such as the CPU 911 as a general task definition data as a task definition data. Task definition data that defines the general task is acquired from the task definition data stored in the storage unit 312.
The general task definition change unit 348 uses the processing device such as the CPU 911 to generate detailed task data included in the general task definition data acquired by the general task definition acquisition unit 338 as changed task definition data. The task definition data changed to data including the new task identification data generated by 347 is generated.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, when a detailed task is selected and a task is added, details of the same general task as the original detailed task are added to the new task. Therefore, the general task can be refined into a plurality of tasks.

The workflow generation system 800 (workflow generation apparatus) in this embodiment further includes an executor definition storage unit 311.
The executor definition storage unit 311 uses a storage device such as the magnetic disk device 920 to execute executor identification data (executor identifier) for identifying the executor as executor definition data for defining an executor that executes a task. And change authority data (change authority identifier) indicating an operator having change authority to change a task executed by the performer.
The task definition change authority determination unit 350 uses a processing device such as the CPU 911 to change from the performer definition data stored in the performer definition storage unit 311 according to the task definition change instruction information input by the task definition change input unit 320. Executer definition data that defines an executor that executes a task defined by the specified task definition data is acquired, and the change authority data included in the acquired executor definition data indicates by using a processing device such as the CPU 911. Based on the operator, it is determined whether or not the operator who has instructed to change the task definition data based on the task definition change instruction information has a change authority.

  According to the workflow generation system 800 (workflow generation apparatus) in this embodiment, task change authority is allocated to operators based on the performer who executes the task. There is an effect that the operator who is familiar with the contents of the work performed by the performer can change the task.

A workflow generation method in which the workflow generation system 800 (workflow generation apparatus) in this embodiment generates a workflow is as follows:
An input device such as a keyboard 902 and a mouse 903 for inputting information, a storage device such as a magnetic disk device 920 for storing information, a processing device such as a CPU 911 for processing information, and a display device 901 such as a CRT for outputting information. A workflow generation system 800 (workflow generation device) having an output device such as a printer device 906 generates a workflow and performs the following processing.
A storage device such as the magnetic disk device 920 stores task definition data that defines a task.
An input device such as a keyboard 902 or a mouse 903 inputs task definition change instruction information indicating that an operator has instructed to change task definition data stored in a storage device such as a magnetic disk device 920.
Whether the processing device such as the CPU 911 has an authority to change the task definition data when the operator who has instructed to change the task definition data based on the task definition change instruction information input by the input device such as the keyboard 902 or the mouse 903 Determine whether.
When it is determined that the operator does not have the change authority, the output device such as the display device 901 such as the CRT or the printer device 906 gives the task to the other operator who has the authority to change the task definition data. Notify that the change of definition data is required to be approved.
Task definition change indicating whether an input device such as a keyboard 902 or a mouse 903 approves the change of the task definition data by another operator notified by an output device such as a display device 901 such as a CRT or a printer device 906 Enter acceptance / rejection information.
When the task definition change approval / disapproval information input by the input device such as the keyboard 902 or the mouse 903 indicates that another operator approves the change of the task definition data, the processing device such as the CPU 911 causes the keyboard 902 or the mouse. Task definition data is generated based on task definition change instruction information input by an input device such as 903, and is used as changed task definition data.
A storage device such as the magnetic disk device 920 stores changed task definition data generated by a processing device such as the CPU 911 as task definition data.

  According to the workflow generation method in this embodiment, when a plurality of operators create a workflow by changing task definition data within their own authority range, and the operator instructs a change that exceeds the authority range. Since the processing device such as the CPU 911 changes the task definition data with the approval of the operator who has the change authority, it is possible to generate a huge workflow in cooperation with a plurality of operators. Play.

  A workflow generation system 800 (workflow generation device) in this embodiment includes an input device such as a keyboard 902 and a mouse 903 for inputting information, a storage device such as a magnetic disk device 920 for storing information, and a CPU 911 for processing information. And a computer that causes a computer having a processing device such as a display device 901 such as a CRT that outputs information and an output device such as a printer device 906 to function as the workflow generation system 800 (workflow generation device) in this embodiment. It can be realized by executing.

  According to the program that causes a computer to function as the workflow generation system 800 (workflow generation device) in this embodiment, a plurality of operators can create and operate a workflow by changing task definition data within their own authority range. When the administrator instructs a change exceeding the authority range, the task definition changing unit 330 changes the task definition data with the approval of the operator having the change authority. There is an effect that a workflow generation system 800 (workflow generation device) capable of generating a huge workflow can be realized.

1 is a system configuration diagram illustrating an example of an overall configuration of a workflow generation system 800 according to Embodiment 1. FIG. FIG. 3 is a diagram showing an example of the appearance of a server device 100 and a terminal device 200 in the first embodiment. FIG. 3 is a diagram illustrating an example of hardware resources of the server device 100 and the terminal device 200 according to the first embodiment. FIG. 7 shows an example of an overall work flow diagram 710 output by the workflow generation system 800 according to the first embodiment. FIG. 7 shows an example of a schematic task flow diagram 720 output by the workflow generation system 800 in the first embodiment. FIG. 7 shows an example of a detailed task flow diagram 730 output by the workflow generation system 800 according to the first embodiment. FIG. 7 shows an example of a detailed work flow diagram 760 output by the workflow generation system 800 according to the first embodiment. FIG. 7 is an enlarged view of a part of another example of a detailed task flow diagram 730 output by the workflow generation system 800 according to the first embodiment. 6 is a diagram showing an example of a work definition list 770 output by the workflow generation system 800 according to Embodiment 1. FIG. FIG. 6 is a diagram showing an example of a work definition document 740 output from the workflow generation system 800 according to the first embodiment. FIG. 10 is a diagram illustrating another example of the work definition document 740 output from the workflow generation system 800 according to the first embodiment. 6 is a diagram showing an example of an interface specification document 750 output by the workflow generation system 800 according to Embodiment 1. FIG. FIG. 3 is a detailed block diagram illustrating an example of a detailed block configuration of a flow creation unit 120 according to the first embodiment. FIG. 3 is a detailed block diagram illustrating an example of a detailed block configuration of a task creation unit 130 according to the first embodiment. FIG. 3 is a detailed block diagram illustrating an example of a detailed block configuration of an interface creation unit 140 according to the first embodiment. FIG. 6 is a flowchart showing an example of a process flow of a workflow generation procedure for generating a workflow using the workflow generation system 800 according to the first embodiment. The figure which shows an example of the whole work flow preparation screen which the display apparatuses 901, such as CRT of the terminal device 200, display in the whole work flow preparation process S11 in Embodiment 1. FIG. The figure which shows an example of the task allocation screen which the display apparatuses 901, such as CRT of the terminal device 200, display in task allocation process S12 in Embodiment 1. FIG. The figure which shows another example of the task allocation screen which the display apparatuses 901, such as CRT of the terminal device 200, display in task allocation process S12 in Embodiment 1. FIG. The figure which shows another example of the task allocation screen which the display apparatuses 901, such as CRT of the terminal device 200, display in task allocation process S12 in Embodiment 1. FIG. The figure which shows an example of the task detailed screen displayed on display apparatuses 901, such as CRT of the terminal device 200, in task detailed process S13 in Embodiment 1. FIG. The figure which shows another example of the task detailed screen which the display apparatuses 901, such as CRT of the terminal device 200, display in task detailed process S13 in Embodiment 1. FIG. The figure which shows another example of the task detailed screen displayed on display apparatuses 901, such as CRT of the terminal device 200, in task detailed process S13 in Embodiment 1. FIG. FIG. 4 is a detailed block diagram illustrating an example of a detailed block configuration of a task creation unit 130 according to the second embodiment. The flowchart figure which shows an example of the flow of the detailed task setting process in which the task creation part 130 in Embodiment 2 sets a detailed task. FIG. 10 is a detailed block diagram illustrating an example of a detailed block of an interface creation unit 140 according to Embodiment 3. The flowchart figure which shows an example of the flow of the interface setting process in which the interface preparation part 140 in Embodiment 3 sets the interface of a task. FIG. 10 is a detailed block diagram illustrating an example of a detailed block configuration of an interface creation unit 140 according to a fourth embodiment. The flowchart figure which shows an example of the flow of the interface setting process in which the interface preparation part 140 in Embodiment 4 sets an interface. FIG. 16 is a block configuration diagram illustrating an example of a functional block configuration of a workflow generation system 800 according to a fifth embodiment. FIG. 18 is a diagram illustrating an example of performer definition data 510 stored in the performer definition storage unit 311 according to the fifth embodiment. FIG. 20 is a diagram illustrating an example of task definition data 520 stored in a task definition storage unit 312 according to the fifth embodiment. FIG. 18 is a flowchart showing an example of a task detailing process in which a task definition changing unit 330 details a task in the fifth embodiment. FIG. 20 is a diagram showing an example of task definition data before being changed by the task detailing process in the fifth embodiment. FIG. 20 is a diagram showing an example of task definition data changed by task detailing processing in the fifth embodiment. FIG. 18 is a flowchart showing an example of a task addition process in which a task definition changing unit 330 adds a task in the fifth embodiment. FIG. 20 is a diagram illustrating an example of task definition data changed by task addition processing in the fifth embodiment. The flowchart figure which shows another example of the flow of the task addition process in which the task definition change part 330 in the form of Embodiment 5 adds a task. FIG. 20 is a diagram illustrating an example of task definition data changed by task addition processing in the fifth embodiment. FIG. 20 is a flowchart illustrating an example of a flow of an executor change process in which a task definition changing unit 330 in the fifth embodiment changes an executor of a task. FIG. 20 is a diagram illustrating an example of task definition data changed by an executor change process in the fifth embodiment. FIG. 25 is a flowchart showing an example of an upstream interface change process flow in which the task definition changing unit 330 changes the upstream interface of a task in the fifth embodiment. FIG. 18 is a diagram illustrating an example of task definition data changed by upstream interface change processing according to the fifth embodiment. FIG. 25 is a flowchart showing an example of a flow of downstream interface change processing in which the task definition changing unit 330 in the fifth embodiment changes the downstream interface of a task. FIG. 20 shows an example of task definition data changed by downstream interface change processing in the fifth embodiment. FIG. 20 is a flowchart showing an example of a workflow creation work flow using the workflow generation system 800 according to the fifth embodiment.

Explanation of symbols

  100 server device, 111 actor definition database storage unit, 112 task definition database storage unit, 113 flow definition database storage unit, 114 interface template database storage unit, 120 flow creation unit, 121 general task input unit, 122 general task performer input unit 123 General task definition generation unit 124 General work flow generation unit 125 General work flow output unit 126 General task flow generation unit 127 General task flow output unit 130 Task creation unit 131 Detailed task input unit 132 Details Task execution input unit, 133 detailed task definition generation unit, 134 detailed workflow generation unit, 135 detailed workflow output unit, 136, 144 detailed task flow generation unit, 137, 145 detailed task flow output unit, 140 Interface creation unit, 141 interface input unit, 143 interface definition generation unit, 146 work definition document generation unit, 147 work definition document output unit, 148 interface specification document generation unit, 149 interface specification document output unit, 151 executor change authority determination unit 152 Interface change authority determination unit, 161 executor change request notification unit, 162 interface change request notification unit, 171 executor change approval / disapproval input unit, 172 interface change approval / disapproval input unit, 181 interface inconsistency warning unit, 200 terminal device, 311 Executor definition storage unit, 312 Task definition storage unit, 320 Task definition change input unit, 321 Selected task input unit, 322 Task detailing input unit, 323 Task addition input unit, 324 Executor change input unit, 325 Upstream interface Additional input unit, 326 Downstream interface change input unit, 330 Task definition change unit, 331 Selected task definition acquisition unit, 332 Upstream task definition acquisition unit, 333 Downstream task definition acquisition unit, 338 General task definition acquisition unit, 341 Change selected task definition Part, 342 upstream task definition change part, 343 downstream task definition change part, 344 performer change part, 345 upstream interface change part, 346 downstream interface change part, 347 new task definition generation part, 348 general task definition change part, 350 task Definition change authority determination unit, 360 Task definition change request notification unit, 370 Task definition change acceptance / rejection input unit, 380 Workflow diagram generation unit, 390 Workflow diagram output unit, 510 Executor definition data, 520-526 Task definition data, 710 Overall work Flow diagram 720, general task flow diagram, 730 detailed task flow diagram, 740 work definition document, 750 interface specification, 760 detailed work flow diagram, 770 work definition list, 800 workflow generation system, 811-813 operator, 901 display device, 902 Keyboard, 903 mouse, 904 FDD, 905 CDD, 906 printer device, 907 scanner device, 910 system unit, 911 CPU, 912 bus, 913 ROM, 914 RAM, 915 communication device, 920 magnetic disk device, 921 OS, 922 window system , 923 program group, 924 file group, 931 telephone, 932 facsimile machine, 940 Internet, 941 gateway, 942 LAN.

Claims (24)

An input device for inputting information, a storage device for storing information, a processing device for processing information, an actor definition database storage unit, a general task input unit, a general task performer input unit, and a general task definition generation unit A task definition database storage unit, a detailed task input unit, a detailed task performer input unit, a detailed task definition generation unit, an interface input unit, and an interface definition generation unit ,
The actor definition database storage unit uses the storage device to store executor definition data that defines an executor that executes a task,
The general task input unit uses the input device to input a general task that constitutes an overall work flow representing the overall work flow,
The general task performer input unit executes the general task input by the general task input unit from the performers defined by the performer definition data stored in the actor definition database storage unit, using the input device. Enter the general task performer selected by the first operator as the performer,
The general task definition generator generates the general task based on the general task input by the general task input unit and the general task performer input by the general task performer input unit using the processing device. Generate summary task definition data to be defined,
The task definition database storage unit stores the general task definition data generated by the general task definition generation unit as task definition data for defining a task using the storage device,
The detailed task input unit uses the input device to input a detailed task in which a second operator has detailed the general task defined by the task definition data stored in the task definition database storage unit,
The detailed task executor input unit uses the input device, and the detailed task input by the detailed task input unit from the executors defined by the executor definition data stored in the actor definition database storage unit. Enter the detailed task executor selected by the second operator as the executor to execute
The detailed task definition generation unit is configured to use the processing device based on the detailed task input by the detailed task input unit and the detailed task performer input by the detailed task performer input unit. , Generate detailed task definition data that defines the above detailed task,
The task definition database storage unit further stores the detailed task definition data generated by the detailed task definition generation unit as task definition data using the storage device ,
The interface input unit uses the input device to output an upstream interface representing a format of information input by the refinement task defined by the task definition data stored in the task definition database storage unit, and the refinement task outputs Enter the downstream interface representing the format of the information,
The interface definition generation unit generates interface definition data that defines the format of information input and output by the detailed task based on the upstream interface and the downstream interface input by the interface input unit, using the processing device. And
The task definition database storage unit further stores the interface definition data generated by the interface definition generation unit as task definition data using the storage device,
The second operator has the authority to change a task executed by another refinement task executor that executes another refinement task that inputs information output by the refinement task. If not, the interface definition data is generated using the processing device when a third operator who has the authority to change the task executed by the other detailed task performer approves. Workflow generation device. An input device for inputting information, a storage device for storing information, a processing device for processing information, an actor definition database storage unit, a general task input unit, a general task performer input unit, and a general task definition generation unit A task definition database storage unit, a detailed task input unit, a detailed task performer input unit, a detailed task definition generation unit, an interface input unit, and an interface definition generation unit ,
The actor definition database storage unit uses the storage device to store executor definition data that defines an executor that executes a task,
The general task input unit uses the input device to input a general task that constitutes an overall work flow representing the overall work flow,
The general task performer input unit executes the general task input by the general task input unit from the performers defined by the performer definition data stored in the actor definition database storage unit, using the input device. Enter the general task performer selected by the first operator as the performer,
The general task definition generator generates the general task based on the general task input by the general task input unit and the general task performer input by the general task performer input unit using the processing device. Generate summary task definition data to be defined,
The task definition database storage unit stores the general task definition data generated by the general task definition generation unit as task definition data for defining a task using the storage device,
The detailed task input unit uses the input device to input a detailed task in which a second operator has detailed the general task defined by the task definition data stored in the task definition database storage unit,
The detailed task executor input unit uses the input device, and the detailed task input by the detailed task input unit from the executors defined by the executor definition data stored in the actor definition database storage unit. Enter the detailed task executor selected by the second operator as the executor to execute
The detailed task definition generation unit is configured to use the processing device based on the detailed task input by the detailed task input unit and the detailed task performer input by the detailed task performer input unit. , Generate detailed task definition data that defines the above detailed task,
The task definition database storage unit further stores the detailed task definition data generated by the detailed task definition generation unit as task definition data using the storage device ,
The interface input unit uses the input device to output an upstream interface representing a format of information input by the refinement task defined by the task definition data stored in the task definition database storage unit, and the refinement task outputs Enter the downstream interface representing the format of the information,
The interface definition generation unit generates interface definition data that defines the format of information input and output by the detailed task based on the upstream interface and the downstream interface input by the interface input unit, using the processing device. And
The task definition database storage unit further stores the interface definition data generated by the interface definition generation unit as task definition data using the storage device,
The second operator has the authority to change a task executed by another refinement task executor that executes another refinement task that outputs information input by the refinement task. If not, the interface definition data is generated using the processing device when a third operator who has the authority to change the task executed by the other detailed task performer approves. Workflow generation device. An input device for inputting operations by a plurality of operators, a storage device for storing information, a processing device for processing information, an actor definition database storage unit, a task definition database storage unit, a detailed task input unit, A detailed task definition generation unit,
The actor definition database storage unit is executor definition data that defines an executor that executes a task using the storage device, and changes a task assigned to the executor among the plurality of operators. Storing performer-defined data including data indicating an operator having authority to
The task definition database storage unit stores task definition data including data indicating task performers assigned to execute the task, the task definition data defining a task using the storage device.
The detailed task input unit inputs an operation by any one of the plurality of operators using the input device, and stores the task stored in the task definition database storage unit using the processing device. based on the definition data, acquires the task execution who run assigned the task, the actor definition database storage unit based on the execution user-defined data stored, modify the tasks assigned to the task performer Gets the operator having the authority, based on the acquired operator, determines whether there is a permission to modify the tasks to the operator who inputs the operation, the task the operator who inputs the operation When it is determined that the user has the right to change the task, the operator who has input the above operation uses the input device to input a detailed task that details the task ,
The detailed task definition generation unit generates task definition data that defines the detailed task based on the detailed task input by the detailed task input unit using the processing device ,
The task definition database storage unit, using the storage device, the details of the task, the details of the task definition generator workflow generator you and to store task definition data generated is. The workflow generation device includes an output device that outputs information to the plurality of operators, a detailed task performer input unit, an executor change authority determination unit, an executor change request notification unit, and an executor change And a consent input part,
The detailed task executor input unit uses the input device to input a detailed task executor to which an operator who inputs the operation assigns execution of the detailed task input by the detailed task input unit. ,
The executor change authority determining unit uses the processing device to provide the detailed task executor input by the detailed task executor input unit based on the executor definition data stored in the actor definition database storage unit. An operator who has the authority to change the assigned task is acquired, and based on the acquired operator, it is determined whether the operator who has input the operation has the authority to change the task,
When the executor change authority determining unit determines that the operator who has input the operation does not have authority to change the task, the executioner change request notifying unit uses the output device to perform the detailed task. Notifying the operator who has the authority to change the task assigned to the executor to request approval to make the detail task performer the detail task performer,
The executor change approval / disapproval input unit uses the input device to input whether the operator who notified the request by the executor change request notification unit has approved the request,
The details of the task definition generating unit, when the invoker change authorization determination unit if there is a permission to modify the tasks to the operator who inputs the operation is determined, and, the performer change request notification unit requests When the executor change approval / disapproval input unit inputs that the notified operator approves the request , the detailed task is used as a task executor assigned to execute the detailed task using the processing device. 4. The workflow generation apparatus according to claim 3 , wherein task definition data including data indicating a detailed task executor input by an executor input unit is generated. An input device for inputting operations by a plurality of operators, an output device for outputting information to the plurality of operators, a storage device for storing information, a processing device for processing information, and a task definition database storage unit A refinement task input unit, an interface input unit, an interface change authority determination unit, an interface change request notification unit, an interface change acceptance / rejection input unit, and an interface definition generation unit,
The task definition database storage unit stores task definition data including task definition data that defines a task using the storage device and includes interface definition data that defines a format of information input by the task. Remember about each,
The detailed task input unit uses the input device to input a task selected by any one of the plurality of operators from the plurality of tasks, and uses the processing device to When it is determined whether the operator who has selected the task has the authority to change the task, and when the operator who has selected the task has the authority to change the task, the input device is used. , The operator who selected the above task inputs a detailed task that details the above task,
The interface input unit inputs the format of information input by the detailed task input by the detailed task input unit specified by the operator who has selected the task using the input device,
The interface change authority determination unit determines whether the operator who has selected the task has an authority to change an upstream task that outputs information input by the task, using the processing device,
The interface change request notifying unit changes the upstream task using the output device when the interface change authority determining unit determines that the operator who has selected the task does not have the authority to change the upstream task. To the operator having the authority to perform the request to approve the format of the information output by the upstream task to the format input by the interface input unit,
The interface change approval / disapproval input unit uses the input device to input whether the operator who notified the request from the interface change request notification unit has approved the request,
The interface definition generating unit, when the interface change authorization determination unit if there is a permission to modify the upstream task in the operator selected the task is determined, and, the interface change request notification unit has notified the request When the interface change approval / disapproval input unit inputs that the operator has approved the request, the format input by the interface input unit is used as the format of information input by the detailing task using the processing device. It generates interface definition data representing,
The task definition database storage unit, using the storage device, the details of the task, workflow generator you and to store task definition data including interface definition data the interface definition generator has generated. An input device for inputting operations by a plurality of operators, an output device for outputting information to the plurality of operators, a storage device for storing information, a processing device for processing information, and a task definition database storage unit A refinement task input unit, an interface input unit, an interface change authority determination unit, an interface definition generation unit, and an interface inconsistency warning unit,
The task definition database storage unit is task definition data that defines a task using the storage device, and includes interface definition data that defines a format of information input by the task and a format of information output by the task Task definition data including, for each of a plurality of tasks,
The detailed task input unit uses the input device to input a task selected by any one of the plurality of operators from the plurality of tasks, and uses the processing device to When it is determined whether the operator who has selected the task has the authority to change the task, and when the operator who has selected the task has the authority to change the task, the input device is used. , The operator who selected the above task enters a detail task that details the above task,
The interface input unit inputs the format of information input by the detailed task input by the detailed task input unit specified by the operator who has selected the task using the input device,
The interface change authority determination unit determines whether the operator who has selected the task has an authority to change an upstream task that outputs information input by the task, using the processing device,
The interface definition generation unit generates interface definition data representing a format input by the interface input unit as a format of information input by the detailing task using the processing device,
The task definition database storage unit stores task definition data including the interface definition data generated by the interface definition generation unit for the detailed task using the storage device,
The interface inconsistency warning unit uses the processing device to store the task definition database when the interface change authority determination unit determines that the operator who has selected the task does not have authority to change the upstream task. Based on a plurality of task definition data stored by the department, it is determined whether the format of the information output by the upstream task matches the format of the information input by the detailed task, and the upstream task outputs When it is determined that the format of the information to be performed and the format of the information input by the detailing task do not match, using the output device, the operator having the authority to change the upstream task A workflow generation device that warns that there is a discrepancy between the format of the information output by the upstream task and the format of the information input by the detailed task. . The workflow generation device has an actor definition database storage unit,
The actor definition database storage unit is executor definition data that defines an executor that executes a task using the storage device, and changes a task assigned to the executor among the plurality of operators. Storing performer-defined data including data indicating an operator having authority to
The task definition data stored by the task definition database storage unit includes data indicating a task performer assigned to execute the task,
The detailed task input unit inputs task definition data for the input task from the plurality of task definition data stored in the task definition database storage unit using the processing device, and the input task definition data based on, acquires the task execution who run assigned the task, based on the performer definition data in which the actor definition database storage unit and stored by, the permission to change the tasks assigned to the task performer Determine whether the operator who has selected the task has the authority to change the task based on the acquired operator ,
The interface modification rights determination unit, using the processing device, from among the plurality of task definition data which the task definition database storage unit is stored, and enter a task definition data for said upstream task, the input task definition data Authority to acquire the task performer assigned to execute the upstream task based on the above, and to change the task assigned to the task performer based on the performer definition data stored in the actor definition database storage unit Gets the operator having, based on the acquired operator, claim 5 or claim, characterized in that to determine whether there is a permission to modify the upstream task in the operator selected the task 6. The workflow generation device according to 6 . An input device for inputting operations by a plurality of operators, an output device for outputting information to the plurality of operators, a storage device for storing information, a processing device for processing information, and a task definition database storage unit A refinement task input unit, an interface input unit, an interface change authority determination unit, an interface change request notification unit, an interface change acceptance / rejection input unit, and an interface definition generation unit,
The task definition database storage unit stores task definition data including task definition data that defines a task using the storage device and includes interface definition data that defines a format of information output by the task. Remember about each,
The detailed task input unit uses the input device to input a task selected by any one of the plurality of operators from the plurality of tasks, and uses the processing device to When it is determined whether the operator who has selected the task has the authority to change the task, and when the operator who has selected the task has the authority to change the task, the input device is used. , The operator who selected the above task inputs a detailed task that details the above task,
The interface input unit uses the input device to input a format of information output by the detailed task input by the detailed task input unit, instructed by an operator who has selected the task,
The interface change authority determination unit determines whether the operator who has selected the task has the authority to change a downstream task that inputs information output by the task, using the processing device,
The interface change request notifying unit changes the downstream task using the output device when the interface change authority determining unit determines that the operator who has selected the task does not have the authority to change the downstream task. To the operator having the authority to perform the request to approve the format of the information input by the downstream task to the format input by the interface input unit,
The interface change approval / disapproval input unit uses the input device to input whether the operator who notified the request from the interface change request notification unit has approved the request,
The interface definition generating unit, when the interface change authorization determination unit if there is a permission to modify the downstream task to the operator selecting the task is determined, and, the interface change request notification unit has notified the request When the interface change approval / disapproval input unit inputs that the operator has approved the request, the format input by the interface input unit is used as the format of the information output by the detailing task using the processing device. It generates interface definition data representing,
The task definition database storage unit, using the storage device, the details of the task, workflow generator you and to store task definition data including interface definition data the interface definition generator has generated. An input device for inputting operations by a plurality of operators, an output device for outputting information to the plurality of operators, a storage device for storing information, a processing device for processing information, and a task definition database storage unit A refinement task input unit, an interface input unit, an interface change authority determination unit, an interface definition generation unit, and an interface inconsistency warning unit,
The task definition database storage unit is task definition data that defines a task using the storage device, and includes interface definition data that defines a format of information input by the task and a format of information output by the task Task definition data including, for each of a plurality of tasks,
The detailed task input unit uses the input device to input a task selected by any one of the plurality of operators from the plurality of tasks, and uses the processing device to When it is determined whether the operator who has selected the task has the authority to change the task, and when the operator who has selected the task has the authority to change the task, the input device is used. , The operator who selected the above task enters a detail task that details the above task,
The interface input unit uses the input device to input a format of information output by the detailed task input by the detailed task input unit, instructed by an operator who has selected the task,
The interface change authority determination unit determines whether the operator who has selected the task has the authority to change a downstream task that inputs information output by the task, using the processing device,
The interface definition generation unit generates interface definition data representing a format input by the interface input unit as a format of information output by the detailing task using the processing device,
The task definition database storage unit stores task definition data including the interface definition data generated by the interface definition generation unit for the detailed task using the storage device,
The interface inconsistency warning unit uses the processing device to store the task definition database when the interface change authority determination unit determines that the operator who has selected the task does not have the authority to change the downstream task. Based on a plurality of task definition data stored by the department, it is determined whether the format of the information output by the detailed task matches the format of the information input by the downstream task, and the detailed task When it is determined that the format of the information to be output and the format of the information input by the downstream task are not consistent with each other, the operator having the authority to change the downstream task using the output device A workflow generation device that warns that there is a discrepancy between the format of the information output by the detailed task and the format of the information input by the downstream task. . The workflow generation device has an actor definition database storage unit,
The actor definition database storage unit is executor definition data that defines an executor that executes a task using the storage device, and changes a task assigned to the executor among the plurality of operators. Storing performer-defined data including data indicating an operator having authority to
The task definition data stored by the task definition database storage unit includes data indicating a task performer assigned to execute the task,
The detailed task input unit inputs task definition data for the input task from the plurality of task definition data stored in the task definition database storage unit using the processing device, and the input task definition data based on, acquires the task execution who run assigned the task, based on the performer definition data in which the actor definition database storage unit and stored by, the permission to change the tasks assigned to the task performer Determine whether the operator who has selected the task has the authority to change the task based on the acquired operator ,
The interface change authority determination unit inputs task definition data for the downstream task from among a plurality of task definition data stored in the task definition database storage unit using the processing device, and the input task definition data Authority to acquire the task performer who is assigned to execute the downstream task based on the above, and to change the task assigned to the task performer based on the performer definition data stored in the actor definition database storage unit Gets the operator having, based on the acquired operator, claim 8 or claim, characterized in that to determine whether there is a permission to change the downstream task to the operator selecting the task 10. The workflow generation device according to 9 . Terminal device operated by a plurality of operators, a storage device for storing information, a processing device for processing information, an executor definition storage unit , a task definition storage unit, a selected task input unit, and a selected task definition acquisition has a section, the task definition change permission determination unit, and a task definition change input section, and a task definition change unit,
The executor definition storage unit is executor definition data for defining an executor using the storage device, and a change authority indicating an operator who has an authority to change a task definition assigned to the executor Stores performer definition data including performer data for each of a plurality of performers,
The task definition storage unit is task definition data that defines a task using the storage device, and includes task definition data including task performer data indicating an performer assigned to execute the task . Remember for each task ,
The selected task input unit, by using the terminal device, from among the plurality of tasks, enter the selected task to one of the operator among the plurality of operator selected,
The selected task definition acquisition unit uses the processing device to determine the selected task from a plurality of task definition data stored in the task definition storage unit based on the selected task input by the selected task input unit. Get task definition data for
The task definition change authority determination unit is an executor assigned to execute the selected task based on task executor data included in the task definition data acquired by the selected task definition acquisition unit using the processing device. Based on the determined executor, the executor definition data for the executor is acquired from the plurality of executor definition data stored in the executor definition storage unit, and the acquired executor definition data is acquired The operator having the authority to change the definition of the task assigned to the performer is determined based on the change authority data included in the operator, and the operator who has selected the selected task is determined based on the determined operator. Determine whether you have the authority to change the definition of the selected task,
The task definition change input unit, when the task definition change permission determination unit if there is authority to change the definition of the selected task to the operator selecting the selected task is determined, using the terminal device , Input an instruction to change the definition of the selected task by the operator who selected the selected task,
The task definition change unit, using the processing device, based on the varying Sarayubi indicate that the task definition change input unit inputs, change the task definition data in which the selected task definition acquisition unit has acquired,
The task definition storage unit, using the storage device, the task definition data which the task definition change unit is changed, the workflow generating apparatus and to store the task definition data for the selected task. The workflow generation device includes an executor change input unit, an executor change authority determination unit, an executor change request notification unit, an executor change consent rejection input unit, and an executor change unit .
The executor change input unit, when the task definition change permission determination unit if there is a right to change the definition of the selected task to the operator selecting the selected task is determined, using the above terminal device, the operator who selects the selection task is instructed to enter the performer of the changed for changing the executor assigned to the selected task,
The executor change authority determination unit uses the processing device to determine a plurality of executor definition data stored in the executor definition storage unit based on the changed executor input by the executor change input unit . Among them, acquire the performer definition data for the performer after the change , and define the task assigned to the performer after the change based on the change authority data included in the acquired performer definition data. Determine who has the authority to change , and based on the determined operator, whether the operator who has selected the selected task has the authority to change the definition of the task assigned to the changed performer Determine whether
The performer change request notification unit, when the invoker's changing authority judging unit and is not authorized to change the definition of tasks assigned to performers after the change is determined by the operator selecting the selected task , by using the terminal device, the operator to have the authority to change the definition of tasks assigned to performers after the change, performer after the change performers assigned to the selected task To request approval to change
The practitioner changing yes or no input unit, by using the terminal device, the operator having the authority to change the definition of tasks assigned to performers after the change, the invoker's assigned to the selected task Enter whether or not you approved the change to the performer after the change ,
The executor changing unit determines that the operator who has selected the selected task has the authority to change the definition of the task assigned to the changed executor, and the executor changing authority determining unit determines , and operator having the authority to change the definition of tasks assigned to performers after the change, the execution that a performer assigned to the selected task approved the changes to the running person after the change who when a change yes or no input unit inputs, using the processing device, the task executor data included in the task definition data the selected task definition acquisition unit has acquired the task of indicating the performer of the variable Sarago Generate task definition data changed to performer data ,
12. The workflow according to claim 11 , wherein the task definition storage unit stores the task definition data generated by the executor changing unit as task definition data for the selected task using the storage device. Generator. A terminal device operated by a plurality of operators, a storage device that stores information, a processing device that processes information, a task definition storage unit, a selected task input unit, a selected task definition acquisition unit, and a task definition change authority A determination unit, an upstream interface change input unit, an upstream task definition acquisition unit, an interface change authority determination unit, an interface change request notification unit, an interface change approval / disapproval input unit, and an upstream interface change unit;
The task definition storage unit, using the storage device, meet the task definition data defining a task, the task definition data including upstream interface data representing the type of information the task is input, for each of a plurality of tasks Remember ,
The selection task input unit uses the terminal device to input a selection task selected by any one of the plurality of operators from the plurality of tasks ,
The selected task definition acquisition unit, using the processing device, based on the selected task to the selected task input section inputs, from among a plurality of task definition data which the task definition storage unit stores, for the selected task get the task definition data,
The task definition change authority determination unit determines whether the operator who has selected the selected task has the authority to change the definition of the selected task, using the processing device,
The upstream interface change input unit uses the terminal device when the task definition change authority determination unit determines that the operator who has selected the selected task has the authority to change the definition of the selected task. Enter the changed format instructed by the operator who selected the selected task to change the format of the information entered by the selected task,
The upstream task definition acquisition unit, using the processing device, from among the plurality of task definition data which the task definition storage unit and stored by the task definition data for upstream task to output information which the selected task is entered Acquired,
The interface change authority determination unit determines whether the operator who has selected the selected task has the authority to change the definition of the upstream task, using the processing device,
The interface change request notifying unit uses the terminal device when the interface change authority determining unit determines that the operator who has selected the selected task does not have the authority to change the definition of the upstream task. Notify the operator who has the authority to change the task definition to request approval to change the format of the information output by the upstream task to the format after the change input by the upstream interface change input unit. And
The interface change approval / disapproval input unit uses the terminal device to allow an operator having the authority to change the definition of the upstream task to change the format of information output by the upstream task to the changed format. Enter whether or not approved
The upstream interface changing unit has an authority to change the definition of the upstream task when the interface change authority determining unit determines that the operator who has selected the selected task has the authority to change the definition of the upstream task. the operator has is the case where that information in a form that the upstream task outputs approved the changed format after the change entered the interface changes yes or no input unit, using the processing device, the the upstream interface data selection task definition acquisition unit is included in the acquired task definition data, and generates a task definition data changed upstream interface data representing the format after the change,
The task definition storage unit, using the storage device, the task definition data which the upstream interface change portion is generated, the workflow generator you and to store the task definition data for the selected task. A terminal device operated by a plurality of operators, a storage device that stores information, a processing device that processes information, a task definition storage unit, a selected task input unit, a selected task definition acquisition unit, and a task definition change authority It includes a determination unit, and an upstream interface change input unit, an upstream task definition acquiring unit, and an interface change authorization determining unit, and an upstream interface changing unit, and an interface mismatch warning unit,
The task definition storage unit, using the storage device, meet the task definition data defining a task represents an upstream interface data representing the type of information the task is input, the format of the information that the task output Task definition data including downstream interface data is stored for each of a plurality of tasks ,
The selection task input unit uses the terminal device to input a selection task selected by any one of the plurality of operators from the plurality of tasks,
The selected task definition acquisition unit uses the processing device to determine the selected task from a plurality of task definition data stored in the task definition storage unit based on the selected task input by the selected task input unit. Get task definition data for
The task definition change authority determination unit determines whether the operator who has selected the selected task has the authority to change the definition of the selected task, using the processing device,
The upstream interface change input unit uses the terminal device when the task definition change authority determination unit determines that the operator who has selected the selected task has the authority to change the definition of the selected task. Enter the changed format instructed by the operator who selected the selected task to change the format of the information entered by the selected task,
The upstream task definition acquisition unit uses the processing device to obtain task definition data for an upstream task that outputs information input by the selected task from among a plurality of task definition data stored in the task definition storage unit. Acquired,
The interface change authority determination unit determines whether the operator who has selected the selected task has the authority to change the definition of the upstream task, using the processing device,
The upstream interface change unit uses the processing device to send upstream interface data included in the task definition data acquired by the selected task definition acquisition unit to the upstream format indicating the changed format input by the upstream interface change input unit. Generate task definition data changed to interface data,
The task definition storage unit stores the task definition data generated by the upstream interface change unit using the storage device as task definition data for the selected task,
The interface inconsistency warning unit uses the processing device to determine the format of information output from the upstream task and the information input from the selected task based on a plurality of task definition data stored in the task definition storage unit . determined format and are whether are aligned, when the format type and information that the selected task input information which the upstream task output is determined not Tei aligned, using the terminal device And warning the operator having the authority to change the definition of the upstream task that the format of the information output by the upstream task is inconsistent with the format of the information input by the selected task. and to that workflow generating device. The workflow generation device includes an executor definition storage unit,
The executor definition storage unit is executor definition data for defining an executor using the storage device, and a change authority indicating an operator who has an authority to change a task definition assigned to the executor Stores performer definition data including performer data for each of a plurality of performers,
The task definition data stored by the task definition storage unit includes task executor data indicating an executor assigned to execute the task,
The task definition change authority determination unit is an executor assigned to execute the selected task based on task executor data included in the task definition data acquired by the selected task definition acquisition unit using the processing device. Based on the determined executor, the executor definition data for the executor is acquired from the plurality of executor definition data stored in the executor definition storage unit, and the acquired executor definition data is acquired. The operator having the authority to change the definition of the task assigned to the performer is determined based on the change authority data included in the operator, and the operator who has selected the selected task is determined based on the determined operator. Determine whether you have the authority to change the definition of the selected task,
The interface change authority determination unit uses the processing device to determine an executor assigned to execute the upstream task based on task executor data included in the task definition data acquired by the upstream task definition acquisition unit. Based on the determined executor, the executor definition data stored in the executor definition storage unit is acquired from the executor definition data for the executor, and the acquired executor definition data is obtained. An operator having authority to change the definition of the task assigned to the executor is determined based on the included change authority data, and the operator who has selected the selected task is determined based on the determined operator. 15. The workflow generation apparatus according to claim 13, wherein it is determined whether or not there is an authority to change the definition of the upstream task. A terminal device operated by a plurality of operators, a storage device that stores information, a processing device that processes information, a task definition storage unit, a selected task input unit, a selected task definition acquisition unit, and a task definition change authority A determination unit, a downstream interface change input unit, a downstream task definition acquisition unit, an interface change authority determination unit, an interface change request notification unit, an interface change approval / disapproval input unit, and a downstream interface change unit;
The task definition storage unit, using the storage device, meet the task definition data defining a task, the task definition data including downstream interface data representing the type of information to force out the task, each of the plurality of tasks Remember about
The selected task input unit, by using the terminal device, from among the plurality of tasks, enter the selected task to one of the operator among the plurality of operator selected,
The selected task definition acquisition unit, using the processing device, based on the selected task to the selected task input section inputs, from among a plurality of task definition data which the task definition storage unit stores, for the selected task get the task definition data,
The task definition change authority determination unit determines whether the operator who has selected the selected task has the authority to change the definition of the selected task, using the processing device,
The downstream interface change input unit uses the terminal device when the task definition change authority determining unit determines that the operator who has selected the selected task has the authority to change the definition of the selected task. Enter the changed format that changes the format of the information output by the selected task, instructed by the operator who selected the selected task,
The downstream task definition acquisition unit, using the processing device, from among the plurality of task definition data which the task definition storage unit and stored by the task definition data for downstream task of inputting information the selected task output Acquired,
The interface change authority determination unit determines whether the operator who has selected the selected task has the authority to change the definition of the downstream task, using the processing device,
The interface change request notifying unit uses the terminal device when the interface change authority determining unit determines that the operator who has selected the selected task does not have the authority to change the definition of the downstream task. Notify the operator who has the authority to change the task definition to request approval to change the format of the information input by the downstream task to the format after the change input by the downstream interface change input unit. And
The interface change approval / disapproval input unit uses the terminal device to allow an operator having the authority to change the definition of the downstream task to change the format of information input by the downstream task to the changed format. Enter whether or not approved
The downstream interface changing unit has an authority to change the definition of the downstream task when the interface change authority determining unit determines that the operator who has selected the selected task has the authority to change the definition of the downstream task. the operator has is the case where that information in a form that the downstream task enters approved the changed format after the change entered the interface changes yes or no input unit, using the processing device, the The task definition data obtained by changing the downstream interface data included in the task definition data acquired by the selected task definition acquisition unit into the downstream interface data representing the format after the change is generated ,
The task definition storage unit stores task definition data generated by the downstream interface changing unit as task definition data for the selected task, using the storage device. A terminal device operated by a plurality of operators, a storage device that stores information, a processing device that processes information, a task definition storage unit, a selected task input unit, a selected task definition acquisition unit, and a task definition change authority includes a determination unit, and the downstream interface change input section, a downstream task definition acquiring unit, and an interface change authorization determining unit, and the downstream interface changing unit, and an interface mismatch warning unit,
The task definition storage unit, using the storage device, meet the task definition data defining a task represents an upstream interface data representing the type of information the task is input, the format of the information that the task output Task definition data including downstream interface data is stored for each of a plurality of tasks ,
The selection task input unit uses the terminal device to input a selection task selected by any one of the plurality of operators from the plurality of tasks,
The selected task definition acquisition unit uses the processing device to determine the selected task from a plurality of task definition data stored in the task definition storage unit based on the selected task input by the selected task input unit. Get task definition data for
The task definition change authority determination unit determines whether the operator who has selected the selected task has the authority to change the definition of the selected task, using the processing device,
The downstream interface change input unit uses the terminal device when the task definition change authority determining unit determines that the operator who has selected the selected task has the authority to change the definition of the selected task. Enter the changed format that changes the format of the information output by the selected task, instructed by the operator who selected the selected task,
The downstream task definition acquisition unit uses the processing device to obtain task definition data for a downstream task that inputs information output from the selected task from among a plurality of task definition data stored in the task definition storage unit. Acquired,
The interface change authority determination unit determines whether the operator who has selected the selected task has the authority to change the definition of the downstream task, using the processing device,
The downstream interface changing unit uses the processing device, and the downstream interface data included in the task definition data acquired by the selected task definition acquiring unit is a downstream indicating the changed format input by the downstream interface change input unit Generate task definition data changed to interface data,
The task definition storage unit stores the task definition data generated by the downstream interface changing unit using the storage device as task definition data for the selected task,
The interface inconsistency warning unit uses the processing device to determine the format of information output from the selected task and the information input from the downstream task based on a plurality of task definition data stored in the task definition storage unit . format and it is determined whether or not aligned, when the format of the information format and the downstream task of information which the selected task is output is input is determined not Tei aligned, using the terminal device The operator having the authority to change the definition of the downstream task is warned that the format of the information output by the selected task is inconsistent with the format of the information input by the downstream task. and to that workflow generating device. The workflow generation device includes an executor definition storage unit,
The executor definition storage unit is executor definition data for defining an executor using the storage device, and a change authority indicating an operator who has an authority to change a task definition assigned to the executor Stores performer definition data including performer data for each of a plurality of performers,
The task definition data stored by the task definition storage unit includes task executor data indicating an executor assigned to execute the task,
The task definition change authority determination unit is an executor assigned to execute the selected task based on task executor data included in the task definition data acquired by the selected task definition acquisition unit using the processing device. Based on the determined executor, the executor definition data for the executor is acquired from the plurality of executor definition data stored in the executor definition storage unit, and the acquired executor definition data is acquired. The operator having the authority to change the definition of the task assigned to the performer is determined based on the change authority data included in the operator, and the operator who has selected the selected task is determined based on the determined operator. Determine whether you have the authority to change the definition of the selected task,
The interface change authority determination unit uses the processing device to determine an executor assigned to execute the downstream task based on task executor data included in the task definition data acquired by the downstream task definition acquisition unit. Based on the determined executor, the executor definition data stored in the executor definition storage unit is acquired from the executor definition data for the executor, and the acquired executor definition data is obtained. An operator having authority to change the definition of the task assigned to the executor is determined based on the included change authority data, and the operator who has selected the selected task is determined based on the determined operator. 18. The workflow generation apparatus according to claim 16, wherein it is determined whether or not there is an authority to change a definition of a downstream task. In a workflow generation method in which a workflow generation device having an input device that inputs operations by a plurality of operators, a storage device that stores information, and a processing device that processes information generates a workflow,
The storage device is executor definition data for defining an executor who executes a task, and data indicating an operator having authority to change a task assigned to the executor among the plurality of operators. storing the performer definition data including,
It said storage device, meet the task definition data defining a task, stores the task definition data including data indicating a task execution who run assigned the task,
The input device inputs an operation by any one of the plurality of operators,
Based on the task definition data stored in the storage device , the processing device acquires a task performer assigned to execute the task,
The processing device acquires an operator having authority to change a task assigned to the task performer based on the performer definition data stored in the storage device ,
Based on the acquired operator, the processing device determines whether the operator who has input the operation has the authority to change the task ,
When it is determined that the operator who inputs the operation has the authority to change the task, the input device inputs a detailed task in which the operator who inputs the operation has refined the task ,
It said processing device, based on the refinement tasks the input device is input, generates a task definition data defining the details of the task,
Said storage device, said about the details of the task, workflow generation method characterized by storing task definition data which the processor has generated. A workflow generation device having an input device that inputs operations by a plurality of operators, an output device that outputs information to the plurality of operators, a storage device that stores information, and a processing device that processes information In the workflow generation method for generating a workflow ,
Said storage device, meet the task definition data defining a task, the task definition data including interface definition data defining the format of the information that the task is input, and stores for each of a plurality of tasks,
The input device inputs a task selected from the plurality of tasks by any one of the plurality of operators,
The processing device determines whether the operator who has selected the task has the authority to change the task,
When it is determined that the operator who has selected the task has the authority to change the task , the input device inputs a detailed task in which the operator who has selected the task has refined the task ,
The input device inputs the format of information input by the refinement task input by the input device, instructed by the operator who has selected the task ,
The processing device determines whether the operator who has selected the task has the authority to change the upstream task that outputs information input by the task,
When the processing device determines that the operator who has selected the task does not have the authority to change the upstream task, the output device sends the upstream task to the operator who has the authority to change the upstream task. Informs that it requests to approve the format of the information output by the input device .
The input device inputs whether the operator to whom the output device has notified the request has approved the request,
When the processing device determines that the operator who has selected the task has the authority to change the upstream task , and the input device confirms that the operator who has notified the request from the output device has approved the request. If you type, the processing device, as the type of information the details of the task is input, and generates an interface definition data representing the format of the input device is input,
Said storage device, said about the details of the task, workflow generation method characterized by storing task definition data including interface definition data which the processor has generated. A workflow generation device having an input device that inputs operations by a plurality of operators, an output device that outputs information to the plurality of operators, a storage device that stores information, and a processing device that processes information In the workflow generation method for generating a workflow ,
Said storage device, meet the task definition data defining a task, the task definition data including interface definition data defining the format of the information format and the task of information the task input and output, a plurality of tasks Remember about each ,
The input device inputs a task selected from the plurality of tasks by any one of the plurality of operators,
The processing device determines whether the operator who has selected the task has the authority to change the task,
When it is determined that the operator who has selected the task has the authority to change the task , the input device inputs a detailed task in which the operator who has selected the task has refined the task ,
The input device inputs the format of information input by the refinement task input by the input device , instructed by the operator who has selected the task ,
The processing device determines whether the operator who has selected the task has the authority to change the upstream task that outputs information input by the task,
The processing device, and the type of information the details of the task is input, and generates an interface definition data representing the format of the input device is input,
It said storage device is attached to the refinement tasks, storing task definition data including interface definition data which the processor has generated,
When the processing device determines that the operator who has selected the task does not have the authority to change the upstream task, the processing device determines that the upstream task is based on a plurality of task definition data stored in the storage device. Determines whether the format of the information output by and the format of the information input by the detailed task are consistent,
When it is determined that the format of the information output by the upstream task does not match the format of the information input by the detailed task, the output device provides an operator with authority to change the upstream task. A workflow generation method that warns that there is a mismatch between the format of information output by the upstream task and the format of information input by the detailed task . A workflow generation device having an input device that inputs operations by a plurality of operators, an output device that outputs information to the plurality of operators, a storage device that stores information, and a processing device that processes information In the workflow generation method for generating a workflow ,
Said storage device, meet the task definition data defining a task, the task definition data including interface definition data defining the format of the information that the task is output, and stores for each of a plurality of tasks,
The input device inputs a task selected from the plurality of tasks by any one of the plurality of operators,
The processing device determines whether the operator who has selected the task has the authority to change the task,
When it is determined that the operator who has selected the task has the authority to change the task , the input device inputs a detailed task in which the operator who has selected the task has refined the task ,
The input device inputs the format of information output by the detailed task input by the input device, instructed by the operator who has selected the task ,
The processing device determines whether the operator who has selected the task has the authority to change the downstream task that inputs the information output by the task,
When the processing device determines that the operator who has selected the task does not have the authority to change the downstream task, the output device sends the downstream task to the operator who has the authority to change the downstream task. Informs that it requests to approve the format of the information input by the input device .
The input device inputs whether the operator to whom the output device has notified the request has approved the request,
When the processing device determines that the operator who has selected the task has the authority to change the downstream task , and the input device confirms that the operator who has notified the request from the output device has approved the request. If you type, the processing device, as the type of information the details of the task is output, to generate an interface definition data representing the format of the input device is input,
Said storage device, said about the details of the task, workflow generation method characterized by storing task definition data including interface definition data which the processor has generated. A workflow generation device having an input device that inputs operations by a plurality of operators, an output device that outputs information to the plurality of operators, a storage device that stores information, and a processing device that processes information In the workflow generation method for generating a workflow ,
Said storage device, meet the task definition data defining a task, the task definition data including interface definition data defining the format of the information format and the task of information the task input and output, a plurality of tasks Remember about each ,
The input device inputs a task selected from the plurality of tasks by any one of the plurality of operators,
The processing device determines whether the operator who has selected the task has the authority to change the task,
When it is determined that the operator who has selected the task has the authority to change the task , the input device inputs a detailed task in which the operator who has selected the task has refined the task ,
The input device inputs the format of information output by the detailed task input by the input device , instructed by the operator who has selected the task ,
The processing device determines whether the operator who has selected the task has the authority to change the downstream task that inputs the information output by the task,
The processing device, and the type of information the details of the task is output, to generate an interface definition data representing the format of the input device is input,
It said storage device is attached to the refinement tasks, storing task definition data including interface definition data which the processor has generated,
When the processing device determines that the operator who has selected the task does not have authority to change the downstream task, the processing device performs the detailed processing based on a plurality of task definition data stored in the storage device. Determine whether the format of the information output by the task matches the format of the information input by the downstream task,
When it is determined that the format of the information output by the detailed task does not match the format of the information input by the downstream task, the output device provides an operator with authority to change the downstream task. A workflow generation method that warns that the format of information output by the detailed task and the format of information input by the downstream task are inconsistent . By computer executes, as a workflow generator according to any one of claims 1 to 18, the computer program characterized that you the computer functions.

Images