JPH08180110A - Operation process defining method - Google Patents

Abstract

PURPOSE: To easily confirm the inspection result of the description state of node and flow information by describing operation process definition information in case or node units and inspecting the description information of operation process definition information corresponding to each case or node. CONSTITUTION: An operation definition tool consists of a business process description 1, work flow definition information setting 2, a work flow definition information check 3, an object connection check 4, icon display state alteration 6, a business process definition check 7, work flow definition script generation 8, an icon file 10, a business process definition file 11, etc. Then node icons, arrows which connect the node icons, and case icons flowing over the arrow are arranged. Attribute information corresponding to the icons is inputted and the degree of completion and connection relation of the attribute information corresponding to the icons arranged on a chart are inspected and according to the inspection result, the display state of the icons is changed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for defining a business process of a group business composed of a plurality of workers, and particularly applied to a business process defining method for describing a business flow by using a graphical interface. Regarding effective technology.

[0002]

2. Description of the Related Art In recent years, a workflow management system has been introduced for the purpose of increasing the productivity of white collars.

A workflow management system is a system for converting documents to be worked into electronic form, using a network,
It is intended to automate the business process consisting of a plurality of workers.

In a workflow management system, a business process definition tool that normally describes a business process, a workflow manager that manages the business process, a business client application that executes each business, and the like are provided. According to the information, the workflow manager circulates the documents (flow information) as the work target among the business clients and executes a series of business processes.

The work definition tools in the workflow management system as described above have been conventionally known, and these known work definition tools describe a flow of a series of business processes by using a graphical map. .

[0006] Specifically, one known work definition tool circulates the icons of nodes (activities), which are components that represent the steps of a work process prepared in advance, and the work route (business process). The business definition (business process definition) information composed of multiple activities is described by arranging the icon of the flow information (courier) to be created on the chart.

The graphical task definition information created by these task definition tools is converted into a data format (execution format) that can be interpreted by the workflow manager via a translator or the like.

[0008] The workflow manager uses the execution format data to move the cooler along the business route connecting the activities.

[0009]

In the conventional work definition tool, it is necessary not only to arrange the prepared icons on the chart but also to input the attribute information of the node corresponding to the arranged icon.

For example, for an icon representing a rendezvous that combines flow information (couriers) divided by parallel processing into one, it is necessary to set identification information or the like for uniquely determining the flow information.

In the conventionally known work definition tool, whether or not the attribute information of the node is correctly input is confirmed by designating the icon to be confirmed and selecting the input / reference menu of the attribute information of the node. It was realized by displaying the dialog screen for operating the attribute information and confirming its contents.

Therefore, in the conventionally known business definition tool, when confirming the attribute information of the icons arranged on the chart, (a) an operation of displaying the attribute information is executed for all the icons on the chart. Alternatively, (b) when translating the definition information for which definition has been completed into the execution format, the confirmation is performed by any method of confirming the entire business process.

However, the method (a) has a problem that the number of confirmation operations is as many as the number of icons arranged on the chart, which lowers the efficiency of business definition.

Further, in the above method (b), it is necessary to start the translator every time the setting status of the attribute information is confirmed. Since the translator targets the entire business process for checking, it takes time to perform the checking process. Therefore, it is difficult to obtain detailed information for each icon.

The present invention has been made to solve the above-mentioned problems of the prior art. An object of the present invention is to verify the setting status of attribute information corresponding to nodes and flow information in a business process definition method. The purpose is to provide a technology that can easily confirm the verification result.

The above and other objects and novel features of the present invention will become apparent from the description of this specification and the accompanying drawings.

[0017]

Of the inventions disclosed in the present application, a representative one will be briefly described below.
It is as follows.

(1) A document circulated among a plurality of workers is expressed as a case, a process of each worker and a process of controlling the flow of the document are expressed as nodes, and the nodes are connected by arrows so that a plurality of workers can be processed. Define a business process that shows a series of business flow realized by circulating documents between workers, manage the defined business process as business process definition information, and follow the flow of documents according to the business process definition information. In a business process definition method in a business process management system to be controlled, a first step of writing business process definition information in units of cases or nodes,
The second step of verifying the description state of the business process definition information corresponding to each case or node.

(2) In the means of (1) above, the first step is to arrange a node icon representing a node, an arrow connecting the node icons, and a case icon representing a case on the arrow. This is a step of inputting attribute information corresponding to each icon, and the second step includes a third step of verifying the setting status of the attribute information corresponding to each icon, and a display form of the icon according to the verified result. And a fourth step of changing.

(3) In the means of (2) above, as a method of changing the display form of the icon, the color arrangement of the elements forming the icon is changed.

(4) In the means of (2) above, as a method of changing the display form of the icon, the shape of the icon is changed.

(5) In the means of (2), the method of changing the display form of the icon is characterized by changing the shade of the color forming the icon.

(6) In the means (3) to (5), the second step displays a guidance related to the attribute information to be set according to the verification result.
Is further included.

(7) In the means (3) to (6), the third step has a step of verifying the setting status of the attribute information corresponding to the node and the connection relationship between the node and the arrow. The fourth step classifies the state of the node according to the setting status of the attribute information corresponding to the node and the combination of the connection relationship between the node and the arrow, and displays the node icon according to the classified state of the node. It is characterized by having a step of changing the form.

(8) In the means of (3) to (6), the third step includes a step of verifying the setting status of the attribute information corresponding to the node based on the status of the case arrangement in the node and arrow. And the fourth step has a step of changing the display form of the node icon according to the verification result.

(9) In the means of (1), the first step is a step of inputting the case, the attribute information about the case, the node, the attribute information about the node, and the arrow by text data, and the second step. Step has a sixth step of verifying the setting status of the attribute information corresponding to each case and node, and a seventh step of changing the display form of the text data corresponding to the case and node according to the verified result. Is characterized by.

(10) In the means of (9), as a method of changing the display form of the text data, the display color of the text data is changed.

(11) In the means of (9) or (10), the sixth step has a step of verifying the setting status of the attribute information corresponding to each node and the connection status of each node. The seventh step is to classify the state of the node according to the setting status of the attribute information corresponding to each node and the connection status combination of each node, and the text data corresponding to the node is classified according to the classified status of the node. It is characterized by having a step of changing the display form.

[0029]

According to the means (1) to (8) described above, in the method of defining a business process, a node icon, an arrow connecting the node icons, and a case icon flowing on the arrow are arranged and corresponding to each icon. Enter the attribute information, completeness of the attribute information corresponding to each icon arranged on the chart, verify the connection relationship of each icon, and display the state of the icons arranged on the chart according to the verified result, for example, It is changed by changing the color arrangement of the elements forming the icon, changing the shape of the icon, changing the shading of the color forming the icon, and the like.

Further, guidance related to the attribute information to be set according to the verified result is displayed.

As a result, the setting status of the attribute information corresponding to the icon can be easily confirmed, and the efficiency of the work definition work can be improved.

According to the means (9) to (11), in the method of defining a business process, a case, attribute information about a case, a node, attribute information about a node,
Also, an arrow is input by text data, the completion degree of the attribute information of the node and the case and the connection relationship between the node and the case are verified, and the display state of the text data corresponding to the node and the case is changed according to the verified result.

As a result, the setting status of the attribute information corresponding to the node and the case can be easily confirmed, and the efficiency of the work definition work can be improved.

[0034]

Embodiments of the present invention will be described below in detail with reference to the drawings.

In all the drawings for explaining the embodiments, parts having the same function are designated by the same reference numerals, and the repeated description thereof will be omitted.

[Embodiment 1] FIG. 1 is a block diagram showing an outline of a business definition tool for realizing a business process definition method which is an embodiment (first embodiment) of the present invention.

In FIG. 1, 1 is a business process description, 2 is workflow definition information setting, 3 is workflow definition information check, 4 is object connection check, 5
Is message generation, 6 is icon display state change, 7 is business process definition check, 8 is workflow definition script generation, 9 is display, 10 is icon file, 11 is business process definition file, 11-1
Is a definition information table, 11-2 icon display state management table, 12 is a business process definition rule, 13 is an object connection rule, and 14 is a workflow definition script.

In FIG. 1, business process description 1
Is composed of a business definition chart and a group of parts arranged on the chart.

The parts include a node icon representing a work step, a case icon representing flow data, and an arrow connecting the node icons.

The workflow definition information setting 2 displays a dialog for inputting attribute information corresponding to the icon arranged in the business process description 1, and stores the input attribute information in the definition information table 11-1.

In the workflow definition information check 3, the attribute information input in the workflow definition information setting 2 is checked, and the setting status is indicated by the icon display status management table 11-
Reflect on 2.

The object connection check 4 checks the connection state of the icons set in the business process description 1 and the workflow definition information setting 2 using the object connection rule 13, and the check result is the icon display state management table. 11-2, and an error message is generated and displayed in the message generation 5 depending on the type of rule violation.

The icon display state change 6 refers to the contents of the icon display state management table 11-2 and determines the display state of each icon.

The business process definition check 7 uses the business process definition rule 12 to check the contents of the business process definition file.

The workflow definition script generator 8 converts the contents of the definition information table 11-1 into the workflow definition script 14.

FIG. 2 is a block diagram showing a schematic configuration of a workflow management system equipped with the work definition tool shown in FIG.

In FIG. 2, reference numeral 21 is a workflow definition client that describes a business as a business process, and the business definition tool shown in FIG. 1 also operates on this workflow definition client 21.

22-1 to 22-3 are business clients that process the flow data that has been circulated.

Reference numeral 23 is a workflow manager, which uses the business process definition information defined by the workflow definition client 21 to execute the business client 22-
Circulate the flow data between 1 and 3.

An operation management client 24 monitors the progress of business processes and manages the entire workflow management system.

In the first embodiment, the business process definition information is provided in the form of a workflow definition script, and the workflow definition script is used after being converted into a form executable by the workflow manager.

The process of converting the workflow definition script into a format executable by the workflow manager may be executed by the workflow definition client 21 or the workflow manager 23.

FIG. 3 is a block diagram showing a schematic configuration of the workflow definition client 21 shown in FIG.

In FIG. 3, reference numeral 31 is a keyboard for inputting code data, and 32 is a pointing device (mouse) for inputting data using a mouse cursor.

Reference numeral 33 is a display for displaying code data and bitmap data, and 34 is a LAN adapter for connecting the workflow definition client 21 and the network.

Reference numeral 35 is a data file for storing information on the business process definition file and rules used for the check processing. The data file 35 is provided on the magnetic disk.

Reference numeral 36 is the workflow definition client 21.
It is a CPU that controls the whole.

Reference numeral 37 is a memory, which includes ROM 37-1 and R
It is composed of AM37-2.

Various programs for implementing the present invention are stored in the ROM 37-1, and the business definition tool shown in FIG. 1 is also stored in the ROM 37-1.

Various tables and data are stored in the RAM 37-2.

In this embodiment, the ROM and the RAM are separate blocks, but in the same memory R
It can also be realized by dividing the storage areas of the data stored in the OM and the data stored in the RAM.

Further, the business client 22- shown in FIG.
1 to 3, the workflow manager 23, and the operation management client 24 have the same schematic configuration as the workflow definition client 21.

In this workflow management system, information corresponding to one job is managed in units of business processes.

The information set in the business process description processing is stored in the definition information table 11-1 shown in FIG.

FIG. 4 shows the definition information table 11 shown in FIG.
It is a figure which shows an example of -1.

The definition information table 11-1 includes a business process ID 41, a business process name 42, a user key 43, a creator name 44, a creation date 45, a pointer 46 to the node attribute definition information table, and a case attribute definition information table. It is composed of a pointer 47 and the like.

The business process ID 41 is information for uniquely identifying the business process in the workflow management system, and the business process name 42 is
This is the name of the business process and is information used by the user to identify the business process.

The user key 43 is information representing a field name for storing information that uniquely identifies an instance of a business process when the instance is created.

The creator name 44 is a field that stores the name of the user who created the business process, and the creation date 45 is a field that stores the date and time when the business process was created.

The pointer 46 to the node attribute definition information table and the pointer 47 to the case attribute definition table are fields for storing pointers to the attribute definition information tables of nodes and cases related to the business process.

FIG. 5 is a diagram showing an example of a display screen of the work definition tool shown in FIG.

In FIG. 5, 60 is an icon menu,
Reference numerals 60-1 and 60-2 are node icons, and 60-3 is a case icon.

As the node icons 60-1 and 60-2, icons expressing division, broadcasting, waiting, collection, branching, processing, source, sink, etc. can be considered.

FIG. 6 shows an outline of the functions of the node icons 60-1 and 60-2 used in the first embodiment.

FIG. 7 is a flow chart showing the processing procedure of the business process description shown in FIG.

Next, the processing procedure of the business process description shown in FIG. 1 will be described with reference to FIGS.

In step 100, the node icon 60
When designating whether or not to perform the process of arranging -1 to 2 and arranging the node icons 60-1 and 60-2, in step 102, the arranging process of the node icons 60-1 and 60-2 is performed.

The placement processing of the node icons 60-1 and 60-2 is performed as shown in the screen example of the work definition tool of FIG.
This is performed by selecting an icon to be arranged on the chart from the icon menu 60 with the mouse 32 or the like and moving it to the position on the chart to be arranged.

At step 104, the process for the icon is selected.

The selectable processes include a process of inputting attribute information about the node icons 60-1 and 60-2, a process of connecting the arrow 61 to the node icons 60-1 and 60-2, a node icon 60-1 and the arrow 61, and the like. Is a deletion process and a change process.

In step 106, the node icon 60
The input processing of the attribute information regarding -1 and 2 is executed.

In the input process of the attribute information, the code data is input by operating the keyboard 31 and the mouse 32 using the dialog boxes corresponding to the node icons 60-1 and 60-2, and the input attribute is input. The information is
It is stored in the node attribute definition information table 70 shown in FIG.

In step 108, the process of connecting the arrow 61 to the node icons 60-1 and 60-2 arranged on the chart is executed.

At step 110, it is checked whether or not a new case is generated at the node which is the starting point of the arrow 61, and if a case is generated, the processing of steps 112 and 114 is executed.

At step 112, the case icon 60 is displayed.
-3 placement processing is executed.

The arranged case icon 60-3 can be displayed on all the nodes.

In this case, the case icons 60-3 are displayed only on the arrow 61 output from the source node and the arrow 61 output from the waiting node.

In step 114, the case icon 60
The input processing of the attribute information regarding -3 is executed.

In the process of inputting attribute information, the code data is input by operating the keyboard or the mouse using the dialog box corresponding to each case icon 60-3. 9 is stored in the case attribute definition information table 80.

In step 116, the node icon 60
-1 and 2 and the case icon 60-3, the arrow 61, and the like, delete processing and change processing are selected.

In step 118, the node icon 60
-1 to 2 and the case icon 60-3 and the arrow 61 are deleted.

When the icon is deleted, the attribute definition information corresponding to the icon is also deleted.

In step 120, the node icon 60
-1 and 2 and the change processing of the case icon 60-3, the arrow 61 and the like are executed.

Regarding the node icons 60-1 and 60-2,
It is possible to change the position in the chart and the content of the node attribute definition information corresponding to the icon.

At step 122, a check & display state changing process is executed.

The check & display state change process is a process of checking the setting status of the attribute information corresponding to the node icons 60-1 and 60-2, the case icon 60-3, etc., and changing the icon display mode according to this setting status. Is.

When the check & display state changing process in step 122 is completed, it is designated in step 124 whether or not the business process description is completed.

If not completed, steps 100 to 1
The processing of 24 is repeated.

At step 126, a business process definition check is executed.

At step 128, it is judged whether or not there is an error by various checks.

At step 130, an error message is generated, and the processing from step 100 onward is repeated.

At step 132, a process for generating a workflow definition script from the workflow definition information is executed.

FIG. 8 is a diagram showing an example of the node attribute definition information table 70-1 in which the attribute information input in the attribute information input process of step 106 shown in FIG. 7 is stored.

The node attribute definition information table 70-1 is
Information such as a node number 701, a node name 702, a node type 703, a role name 704, and a business process procedure 705 is stored for each node.

The node number 701 is identification information for uniquely determining a node in a business process, and the node name 702 is a node name, which is information used by the user to identify the node.

The node type 703 is information indicating each node type, and in this embodiment, the source, sink, process,
It is classified into eight types: branching, waiting, collection, division, and broadcast.

The role name 704 is information for setting a role and a user corresponding to each node, and the role is composed of one or a plurality of users.

The business process procedure 705 is information describing the contents of processing to be executed by each node shown in FIG.

FIG. 9 is a diagram showing an example of the case attribute definition information table 70-2 in which the attribute information input in the attribute information input processing relating to the case icon 60-3 in step 114 shown in FIG. 7 is stored. .

The case attribute definition information table 70-2 is
Each case includes a case ID 710, a case name 711, a case attribute pointer 712, and the like.

The case ID 710 is information for uniquely identifying the case, the case name 711 is the name of the case, and is information used by the user to identify the case.

FIG. 10 is a diagram showing an example of a case attribute table storing case attributes.

The case attribute table 70-3 includes a case attribute name 720, a case attribute type 721, and a case attribute value 722.
Etc.

The case attribute name 720 represents the name of the case attribute and is information used by the user to identify the case attribute, and the case attribute type 721 defines the type of data set in the case attribute value. Information, for example,
There are character type, number type, date type, etc.

The case attribute value 722 is a field in which set data is stored.

Note that although access control is not managed in this embodiment, it is also possible to associate roles / users for each case attribute and manage operations (reference only, changeable, etc.) on case attribute values. To be

11 to 15 show Step 1 shown in FIG.
It is a flow chart which shows the detailed processing procedure of the check & display state change processing of 22.

A detailed processing procedure of the check & display state changing process will be described with reference to FIGS. 11 to 15.

In step 1200 shown in FIG. 11, object connection check processing is performed.

FIG. 12 shows the step 1200 shown in FIG.
5 is a flowchart showing a processing procedure of object connection check processing of FIG.

At step 1204 shown in FIG. 12, attribute value checking of individual nodes and cases is executed.

FIG. 13 shows step 1204 shown in FIG.
5 is a flowchart showing a processing procedure of attribute check processing for individual nodes and cases.

At step 1210 shown in FIG. 13, attribute information completeness check processing of nodes and cases is performed.

The node of step 1210 shown in FIG. 13,
The attribute information completeness check process of a case is a process of checking the setting status of the attribute information to be set in the node and the case and classifying the attribute information setting status of the node and the case.

In this processing, the attribute information setting status is set to “no setting information”, “setting information has error”, “partial setting of essential information”, “only essential information has been set”, “setting of essential information complete, In addition, the option information is also classified into seven states of "partial setting", "attribute information setting completed", and "other".

“No setting information” is a state in which no attribute information is set, and the node icons 60-1 and 60-2 and the case icon 60-3 that have just been transferred to the chart are displayed.
Is in this state.

"There is an error in the setting information" is a state in which there is an error in the set attribute information.

The "partial setting of essential information" is a status in which a part of the attribute information that must be set is set, and does not depend on the setting status of the option information.

“Only essential information has been set” is a state in which the setting of the attribute information that must be set is completed.

“Required information has been set and option information has been partially set” indicates that some of the attribute information that has to be set has been set and some of the attribute information that need not be set is set. It is in a state of being.

"Attribute information setting completed" is a state in which all attribute information has been correctly set and attribute information setting work has been completed.

FIG. 14 shows the step 1210 shown in FIG.
Is a flowchart showing a processing procedure of attribute information completeness check processing of the node and case.

In step 1300 shown in FIG. 14, it is checked whether or not the attribute information setting status is "no setting information". If it is not "no setting information", step 1300
If the process after step 302 is executed and there is “no setting information”, the attribute information setting status is set to 1 in step 1304.

At step 1302, it is verified whether or not there is an error in all the set attribute information.

In step 1306, it is checked whether or not the attribute information setting status is "error in setting information", and if it is not "error in setting information", the processing from step 1308 is executed, If there is an error in the setting information, the attribute information setting status is set to 2 in step 1310.

In step 1308, it is checked whether or not the attribute information setting status is "partial setting of essential information", and if it is not "partial setting of essential information", the processing from step 1312 onward is executed, If it is “partial setting of essential information”, the attribute information setting status is set to 3 in step 1314.

In step 1312, it is checked whether or not the attribute information setting status is "only essential information has been set". If it is not "only essential information has been set", the processing from step 1316 is executed, If “only essential information has been set”, the attribute information setting status is set to 4 in step 1318.

In step 1316, it is checked whether or not the attribute information setting status is "essential information setting complete, and optional information partially setting", and "essential information setting complete and optional information partially If it is not "setting", the processing from step 1320 is executed to "complete the setting of essential information and partially set optional information".
In step 1322, the attribute information setting status is set to 5.

In step 1320, it is checked whether or not the attribute information setting status is "attribute information setting completion". If it is "attribute information setting completion", in step 1324 the attribute information setting status is determined. 13 is set, and in the case of “setting of attribute information is completed”, a state other than the above is set in step 1326, the attribute information setting status is set to 7, and
The process returns to the individual node / case attribute check processing shown in.

In step 1212 shown in FIG. 13, it is checked whether there is a rule violation. If there is a rule violation, an error message is generated in step 1214, and the process returns to the object connection check process shown in FIG. To do.

In step 1206 shown in FIG. 12, the connection relation check process of the individual node and the arrow 61 is performed.

The connection relation check process of the individual node and the arrow 61 in step 1206 shown in FIG. 12 is a process for verifying the situation of the arrow 61 connected to the node, the connection relation with the adjacent node and the like.

FIG. 15 shows step 1206 shown in FIG.
5 is a flowchart showing a processing procedure of a connection relation check processing of the individual node and the arrow 61 of FIG.

In step 1230 shown in FIG. 15, the rule regarding the connection relation between the node and the arrow 61 is checked.

The rules regarding the connection relationship between the node and the arrow 61 are the object connection rules shown in FIGS.

The object connection rule shown in FIG.
The case-related object connection rule shown in FIG. 17 relates to the arrow 61, and the object connection rule shown in FIG.
The object connection rules shown in are for nodes.

Each object connection rule is associated with a rule group and a rule code.

The rule group is information for defining the handling when the rule is violated, and the rule code is information for uniquely identifying the rule.

In the present embodiment, the rule groups are not classified but are all classified into the same classification. However, when it is desired to classify the rules into levels, the rule groups may be used for classification.

In step 1232, it is checked whether or not there is a rule violation. If there is a rule violation, an error message is generated in step 1234, and the process returns to the object connection check process shown in FIG.

Whether or not the rule is violated is determined by referring to the level of the rule group in which the error has occurred.

In this embodiment, it is assumed that an error message is generated in response to an error for a rule whose rule group is "1".

When the connection checking process of the individual node and the arrow 61 in step 1206 shown in FIG. 12 is completed,
The process returns to the check & display state changing process shown in FIG.

When the object connection check process of step 1200 shown in FIG. 11 is completed, step 1202
Then, the result of the object connection check process is reflected in the display state of the icon.

Specifically, based on the contents of the icon display state management table generated and changed according to the result of the object connection check processing, the case icon 60-
3. Change the display state of the node icons 60-1 and 60-2.

FIG. 19 is a diagram showing an example of the icon display state management table 11-2.

The icon display state management table 11-2 shown in FIG. 19 relates to node icons, but the icon display state management table related to case icons can be similarly constructed.

The icon display state table 11-2 includes a node number 730, an attribute information setting state 731, an object connection state 732, a rule code list 733, an icon display mode 734 and the like.

The node number 730 is the same as that used in the node attribute definition information table 70-1 shown in FIG.

The attribute information setting status 731 is information obtained by the attribute information completeness check processing of the node and case in step 1204 shown in FIG. 13, and in the case of the first embodiment, there are seven states. .

The object connection status 732 is information reflecting the result of the object connection check processing in step 1200 shown in FIG. 11, and here, the number of object connection rules violating the rule of the node is one or more. The states are classified by.

The rule code list 733 stores a list of rule codes of object connection rules that the node violated as a result of the object connection check processing.

The icon display mode 734 is a state that is uniquely determined by the combination of the attribute information setting status and the object connection status. In the first embodiment, there are 14 statuses.

In the first embodiment, the state of the object connection status is classified according to the number of violated rules. However, the classification of the rule group of the object connection rule is detailed, and the detailed rule group is used for the object connection. A method of classifying the state of the situation is also conceivable.

20 and 21 are diagrams showing an example of the display form of the icon whose display state is changed based on the icon display mode 734 of the icon display state management table 11-2.

In this example, the classification of states is realized by changing the color arrangement of the elements forming the icons.

As a method of changing the display state, a method of changing the shape of the icon, the shading of the color, or the like can be considered.

22 to 26 are step 1 shown in FIG.
It is a flow chart which shows the detailed processing procedure of 26 business process definition check processing.

In step 1240 of FIG. 22, the node,
Execute the attribute value check process of the case.

FIG. 23 shows the step 1240 shown in FIG.
5 is a flowchart showing a processing procedure of attribute value check processing for the node and case.

At step 1250 shown in FIG. 23, a node to be subjected to the attribute value check processing is searched.

At step 1252, the rules regarding the attribute values of the node and the case are checked.

The rules relating to the attribute values of nodes and cases are the same as the rules used for checking the attribute values of individual nodes and cases.

In step 1254, it is checked whether or not there is a rule violation, and if there is a rule violation, an error message is generated in step 1256.

At step 1258, it is confirmed whether there is any unchecked node, and if there is any unchecked node,
The processing of steps 1250 to 1248 is repeated.

If there is no unchecked node, the process returns to the business process definition check process of FIG.

At step 1242 shown in FIG. 22, a connection relation check process between the node and the arrow 61 is executed.

The connection relation check process between the node and the arrow 61 is similar to the connection relation check process between the individual node and the arrow 61, and the situation of the arrow 61 connected to the node,
This is a process for verifying the connection relationship with an adjacent node.

FIG. 24 shows step 1242 shown in FIG.
Is a flowchart showing the processing procedure of the connection relation check processing between the node and the arrow 61.

In step 1260 shown in FIG. 24, a node to be the target of the connection relation check process between the node and the arrow 61 is searched.

In step 1262, the node and arrow 6
Check the rules for connection relationships in 1.

The rules regarding the connection relationship between the node and the arrow 61 are the same as the rules used in the connection relationship check processing between the individual node and the arrow 61, and among the object connection rules shown in FIGS.
It is classified into.

In step 1264, it is checked whether or not there is a rule violation, and if there is a rule violation, an error message is generated in step 1266.

At step 1268, it is confirmed whether or not there is an unchecked node, and if there is an unchecked node,
The processing of steps 1260 to 1268 is repeated.

If there is no unchecked node, the process returns to the business process definition check process of FIG.

At step 1244 shown in FIG. 22, the consistency check process for the case on the node / arrow 61 is executed.

The case consistency check process on the node / arrow 61 is a process for verifying the arrangement state of cases in the business process.

FIG. 25 shows step 1244 shown in FIG.
Is a flowchart showing the processing procedure of the consistency check processing for the case of the node on the arrow 61.

In step 1270 shown in FIG. 25, a node which is the target of the case consistency check processing is searched for.

In step 1272, the node, arrow 6
Check the rules for consistency of cases on 1.

As an example of the rule regarding the consistency of the cases on the node and the arrow 61, the rule group "2" in the business process definition rules shown in FIGS.
Some are classified into.

In step 1274, it is checked whether or not there is a rule violation, and if there is a rule violation, an error message is generated in step 1276.

At step 1278, it is confirmed whether or not there is an unchecked node, and if there is an unchecked node,
The processing of steps 1270 to 1278 is repeated.

If there is no unchecked node, the process returns to the business process definition check process of FIG.

In step 1246 shown in FIG. 22, flow legitimacy check processing is executed.

The flow correctness check process is a process for verifying the definition status of the entire business process such as the connection status of nodes.

FIG. 26 shows step 1246 shown in FIG.
5 is a flowchart showing a processing procedure of a validity check processing of the flow of FIG.

In step 1280 of FIG. 26, the rule regarding the legitimacy of the flow is checked.

As an example of the rule regarding the legitimacy of the flow, there is a rule classified into the rule group "3" among the business process definition rules shown in FIGS.

In step 1282, it is checked whether or not there is a rule violation. If there is a rule violation, an error message is generated in step 1284, and the process returns to the business process definition check processing of FIG.

In the first embodiment, the rule verified in the check & display state changing process is the object connection rule (rule classified into rule group "1"), but it is classified into rule group "2". It can also be realized as a rule for verifying a business process definition rule that

Regarding the setting status of the attribute information, the setting value of the attribute information of the other node connected by the arrow 61 is used to generate and set the attribute information of the node, or the settable candidate value is set. The attribute information can be changed by generating the attribute information.

[Second Embodiment] In the first embodiment, the method of changing the icon display mode according to the setting status of the attribute information corresponding to the icon has been described.

In this embodiment, a message corresponding to the setting status of the attribute information corresponding to the icon is displayed in association with the icon.

FIG. 29 is a block diagram showing an outline of a business definition tool for realizing a business process definition method which is another embodiment (second embodiment) of the present invention.

In FIG. 29, 201 is a business process description, 202 is workflow definition information setting, 203 is workflow definition information check, 204 is object connection check, 205 is message generation, 206 is icon display state change, and 207 is business process definition. Check, 208 is workflow definition script generation, 20
9 is a display, 210 is an icon file, 211
Is a business process definition file, 211-1 is a definition information table, 211-2 icon display state management table, 212 is a business process definition rule, 213 is an object connection rule, and 214 is a workflow definition script.

Further, reference numeral 215 is a guidance display, which generates a message related to the attribute information corresponding to the icon.

As the message to be generated, for example, a message for notifying unset essential information, a message for creating a list of attribute information to be set, and displaying the unset parts by classifying them into mandatory, optional, etc. Can be considered.

FIG. 30 is a diagram showing an example of the display screen of the work definition tool having the guidance display function of the second embodiment.

In the screen example shown in FIG. 30, guidance is displayed regarding node icons that violate the specified rule group.

The rule group used here is
This is shown in FIGS.

A method of displaying guidance for a designated node icon with a mouse cursor or a method of displaying guidance for all node icons on the chart is also conceivable.

[Embodiment 3] The above-mentioned Embodiments 1 and 2
Then, an example of a business definition tool that describes business processes by using graphical tools such as nodes and arrows was shown.

The third embodiment shows an example of a business definition tool for defining a business process by text data.

FIG. 31 is a block diagram showing an outline of a business definition tool for realizing a business process definition method which is another embodiment (third embodiment) of the present invention.

In FIG. 31, 301 is a business process description, 302 is workflow definition information setting, 303 is workflow definition information check, 304 is object connection check, 305 is message generation, 307 is business process definition check, and 308 is workflow definition script. Generation, 309 is a display, 311 is a business process definition file, 311-1 is a definition information table, 311-2 icon display state management table, 31
Reference numeral 2 is a business process definition rule, 313 is an object connection rule, and 314 is a workflow definition script.

Reference numeral 306 is a text display form change, which changes the display form of the text data according to the contents of the node display state management table 311-2.

FIG. 32 shows the node display state management table 3
It is a figure which shows an example of the 11-2 table.

The node display state management table 311-2 shown in FIG. 32 has the same contents as the icon display state management table. The node number 740, the attribute information setting status 741, the object connection status 742, and the rule code list. 743, a text display mode 744, and the like.

Text display state management table 311-2
Node number 740, attribute information setting status 741, object connection status 742, and rule code list 743 of
The content is the same as that of the icon display state management table 11-2.

The text display mode 744 is information whose value is determined by the contents of the attribute information setting status 741 and the object connection status 742, and manages the display status of the business process definition information corresponding to the node.

In the third embodiment, the business process definition information (business process definition script) represented by the text data describes the attribute information for each node, and the part of the business process definition script corresponding to the node is described. Each time, the display form of the text data is changed.

As a method of changing the display form of the text data, a method of changing the display color of the text data can be considered.

FIG. 33 is a diagram showing an example of a business process definition script.

The script shown in FIG. 33 is composed of reserved words and attribute information to be set, and text data enclosed in parentheses serves as a unit of business process definition information.

Reserved words in this script are represented by a character string with # added at the beginning. The attribute information to be set is the same information as the contents of the definition information table shown in FIG.

FIG. 34 is a diagram showing an example of a display screen of the work definition tool of the third embodiment.

The display screen shown in FIG. 34 displays not only the text data of each node or case but also the icon in the first embodiment for easy understanding.

Although the present invention has been specifically described based on the embodiments, it is needless to say that the present invention is not limited to the embodiments and various modifications can be made without departing from the scope of the invention.

[0230]

The effects obtained by the typical ones of the inventions disclosed in the present application will be briefly described as follows.

(1) According to the present invention, a node icon,
Arrange the arrows that connect between the node icons, the case icons that flow on the arrows, enter the attribute information corresponding to each icon, and complete the attribute information corresponding to each icon placed on the chart, and By verifying the connection relationship and changing the display state of the icon placed on the chart according to the verification result, it becomes possible to easily check the setting status of the attribute information corresponding to the icon, and It is possible to improve efficiency.

(2) According to the present invention, the case, the attribute information about the case, the node, the attribute information about the node, and the arrow are input by text data, and the completeness of the attribute information of the node and the case, the node and the case are input. Since the connection status of is verified and the display state of the text data corresponding to the node and case is changed according to the verification result, it is possible to easily check the setting status of the attribute information corresponding to the node and case. It is possible to improve the efficiency of work definition work.

[Brief description of drawings]

FIG. 1 is a block diagram showing an outline of a business definition tool that implements a business process definition method that is an embodiment (first embodiment) of the present invention.

FIG. 2 is a block diagram showing a schematic configuration of a workflow management system in which the business definition tool shown in FIG. 1 is installed.

FIG. 3 is a workflow definition client 21 shown in FIG.
3 is a block diagram showing a schematic configuration of FIG.

4 is a diagram showing an example of a definition information table 11-1 shown in FIG.

FIG. 5 is a diagram showing an example of a display screen of a work definition tool according to the first embodiment.

FIG. 6 is a node icon 60-1 used in the first embodiment.
It is a figure which shows the outline | summary of the function of -2.

7 is a flowchart showing a processing procedure of the business process description shown in FIG.

FIG. 8 is a diagram showing an example of a node attribute definition information table 70-1.

FIG. 9 is a diagram showing an example of a case attribute definition information table 70-2.

FIG. 10 is a case attribute table 7 storing case attributes.
It is a figure which shows an example of 0-3.

FIG. 11 is a flowchart showing a detailed processing procedure of the check & display state change processing of step 122 shown in FIG. 7.

12 is a flowchart showing a processing procedure of object connection check processing in step 1200 shown in FIG.

13 is a flowchart showing a processing procedure of attribute check processing for individual nodes and cases in step 1204 shown in FIG.

FIG. 14 is a flowchart showing a processing procedure of attribute information completeness check processing of the node and case of step 1210 shown in FIG. 13;

15 is a flowchart showing a processing procedure of a connection relation check processing of an individual node and an arrow 61 in step 1206 shown in FIG.

FIG. 16 is a diagram showing an object connection rule regarding a case.

FIG. 17 is a diagram showing an object connection rule regarding arrows.

FIG. 18 is a diagram showing an object connection rule relating to a node.

FIG. 19 is a diagram showing an example of an icon display state management table 11-2.

FIG. 20 is a diagram showing an example of a display form of an icon whose display state is changed.

FIG. 21 is a diagram showing an example of a display form of an icon whose display state is changed.

22 is a flowchart showing a detailed processing procedure of the business process definition check processing in step 126 shown in FIG.

FIG. 23 is a flowchart showing the processing procedure of the attribute value check processing of the node / case of step 1240 shown in FIG. 22;

FIG. 24 is a flowchart showing a processing procedure of connection relationship check processing between the node and the arrow 61 in step 1242 shown in FIG. 22;

FIG. 25 is a flowchart showing the processing procedure of the consistency check processing of the case on the arrow 61 in the node of step 1244 shown in FIG. 22;

FIG. 26 is a flowchart showing a processing procedure of validity check processing of the flow of step 1246 shown in FIG. 22.

FIG. 27 is a diagram showing an example of a business process definition rule.

FIG. 28 is a diagram showing an example of a business process definition rule.

FIG. 29 is a block diagram showing an outline of a business definition tool that realizes a business process definition method that is another embodiment (second embodiment) of the present invention.

FIG. 30 is a diagram showing an example of a display screen of a work definition tool according to the second embodiment.

FIG. 31 is a block diagram showing an outline of a business definition tool for realizing a business process definition method which is another embodiment (third embodiment) of the present invention.

FIG. 32 is a node display state management table 3 shown in FIG. 31.
It is a figure which shows an example of the 11-2 table.

FIG. 33 is a diagram showing an example of a business process definition script.

FIG. 34 is a diagram showing an example of a display screen of a work definition tool according to the third embodiment.

[Explanation of symbols]

1,201,301 ... Business process description, 2,20
2, 302 ... Workflow definition information setting, 3, 203,
303 ... Workflow definition information check, 4,204,
304 ... Object connection check, 5, 205, 30
5 ... Message generation, 6, 206 ... Icon display state change, 7, 207, 307 ... Business process definition check, 8, 208, 308 ... Workflow definition script generation, 9, 209, 309 ... Display, 10, 21
0 ... Icon file, 11, 211, 311 ... Business process definition file, 11-1, 211-1, 31
1-1 ... Definition information table, 11-2, 211-2, 3
11-2 ... Icon display state management table, 12, 21
2,312 ... Business process definition rule, 13,21
3, 323 ... Object connection rule, 14, 214,
314 ... Workflow definition script, 21 ... Workflow definition client, 223-1 ... Business client, 23 ... Workflow manager, 24 ... Operation management client, 31 ... Keyboard, 32 ... Pointing device (mouse), 33 ... Display, 34 ... LA
N adapter, 35 ... Data file, 36 ... CPU, 3
7 ... memory, 37-1, ... ROM, 37-2 ... RAM, 7
0-1 ... Node attribute definition information table, 70-2 ... Case attribute definition information table, 70-3 ... Case attribute table, 215 ... Guidance display, 306 ... Text display form change.

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Hirofumi Kondo 1099 No. Ozenji, Aso-ku, Kawasaki-shi, Kanagawa Ltd. System Development Laboratory, Hitachi, Ltd. Hitachi, Ltd. System Development Laboratory (72) Inventor Atsushi Nitta 1099, Ozenji Temple, Aso-ku, Kawasaki City, Kanagawa Stock Company Hitachi System Development Laboratory

Claims (14)

[Claims] 1. A case in which a document circulated among a plurality of workers is expressed as a case, a process of each worker and a process for controlling the flow of the document are expressed as nodes, and the nodes are connected by arrows to perform a plurality of works. Define a business process that shows a series of business flow realized by circulating documents between persons, manage the defined business process as business process definition information, and control the flow of documents according to the business process definition information. In the business process definition method in the business process management system, the first step of writing business process definition information in units of cases or nodes and the second step of verifying the description state of the business process definition information corresponding to each case or node A method for defining a business process, comprising: 2. At least "nodes that divide a plurality of cases and distribute them to a plurality of nodes", "broadcast nodes that duplicate a case and distribute it to a plurality of arrows", as nodes constituting the business process. "Waiting node that correlates multiple cases and distributes them as a set", "Collection node that integrates multiple cases and distributes as one case",
The business process definition method according to claim 1, further comprising a "branch node that selects and distributes only one arrow from a plurality of arrows". 3. In the first step, a node icon representing a node, an arrow connecting the node icons, a case icon representing a case are arranged on the arrow, and attribute information corresponding to each icon is input. The second step has a third step of verifying the setting status of the attribute information corresponding to each icon, and a fourth step of changing the display form of the icon according to the verified result. The business process definition method according to claim 1 or 2, characterized in that. 4. The method for defining a business process according to claim 3, wherein as a method of changing the display form of the icon, the color arrangement of the elements forming the icon is changed. 5. The method for defining a business process according to claim 3, wherein a shape of the icon is changed as a method of changing the display form of the icon. 6. The method for defining a business process according to claim 3, wherein, as a method of changing the display form of the icon, the shade of the color forming the icon is changed. 7. The method according to claim 3, wherein the second step further includes a fifth step of displaying a guidance related to attribute information to be set according to the verification result. The business process definition method described in paragraph 1. 8. The third step includes the step of verifying the setting status of the attribute information corresponding to the node and the connection relationship between the node and the arrow, and the fourth step corresponds to the node. The method further includes a step of classifying the states of the nodes according to the setting status of the attribute information and the combination of connection relationships between the nodes and the arrows, and changing the display form of the node icon according to the states of the classified nodes. The business process definition method according to any one of claims 3 to 7. 9. The attribute information setting status of the node is at least “no setting information”, “error in setting information”, “partial setting of essential information”, “only essential information has been set”, “essential information 9. The business process defining method according to claim 8, wherein the setting is completed and the option information is partially set "and" setting of attribute information is completed ". 10. The third step includes a step of verifying a setting status of attribute information corresponding to the node according to a layout status of cases in nodes and arrows, and a result of the verification in the fourth step. 8. The business process definition method according to claim 3, further comprising the step of changing the display form of the node icon in accordance with the method. 11. The attribute information of another node connected by an arrow is used to generate and set the attribute information of the node, or to generate a settable candidate value. The business process definition method according to any one of claims 3 to 10. 12. The first step comprises the case,
A step of inputting attribute information about a case, a node, attribute information about a node, and an arrow by text data, and the second step includes a sixth step of verifying the setting status of the attribute information corresponding to each case and node. The seventh step of changing the display form of the text data corresponding to the case and the node according to the verified result, and the business process defining method according to claim 1 or 2. 13. The business process definition method according to claim 12, wherein a display color of the text data is changed as a method of changing the display form of the text data. 14. The sixth step has a step of verifying a setting status of attribute information corresponding to each node and a connection status of each node, and the seventh step comprises:
The node status is classified according to the setting status of the attribute information corresponding to each node and the connection status combination of each node,
14. The business process definition method according to claim 12, further comprising a step of changing a display form of text data corresponding to the node according to a state of the classified node.