JP2003208500A - Business process definition display method, system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problems in a conventional method for differentially defining two or more business processes (BP) and operating them by a combination of main BP and sub BP in the simultaneous operation of the business processes that the diversification is remarkably limited by the competition of the sub BP, and the change of the main BP has an influence on all BP with the worst case where the BP cannot be operated. <P>SOLUTION: Succession of object orientation is applied to BP definition so that the change of a basic BP is automatically reflected to a derived BP. A changeable position/unchangeable position is designated in the definition of the basic BP and the derived BP, whereby the derivation can be performed while keeping the succeeded definition of BP at the minimum. Accordingly, the maintenance property of the BP definition and the understanding of the complicated BP definition can be facilitated. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a workflow system for realizing a workflow by a computer system, and more particularly to a workflow system suitable for reuse and maintenance of business process definition, a reuse support method therefor, and a program therefor. is there.

[0002]

2. Description of the Related Art A workflow system using a computer defines the order of each work, the person in charge, the work content, etc. for a series of works to be performed in a predetermined work order, and electronically sets the definition. It is a system for advancing work processing in order from one work to the next work according to.
A defined series of work is called a business process.
The business process definition data defines the work content, activity start conditions and end conditions, person in charge, etc. for each work node called an activity.

A business process is often defined hierarchically when, for example, a large work is divided into some middle works, and a middle work is divided into small works. For example, as described in Japanese Patent Application Laid-Open No. 11-316780, there is a technique in which a series of operations in an upper hierarchy is defined as a main business process and a series of operations in a lower hierarchy is separately defined as a sub-business process. This technology improved the maintainability of business processes and made it easier to understand complex and huge business processes.

[0004]

[Problems to be Solved by the Invention] When a workflow system is used in a business generally performed by an organization such as a company, a business process is performed between departments or departments / sections.
In many cases, a business process definition that is very similar is used between the person in charge and the person in charge. For example, the basic business process of the general affairs department is fixed, and each section in the department defines each business process by replacing or inserting some work with its own work.

In this case, even if the business process is sub-componentized to some extent as a sub-business process, the sub-business process required by each section is different.
It is easily expected that simultaneous operation will be impossible due to competition. In addition, it is expected that the requested work cannot be solved only by selecting the prepared sub-business process. For example, a large business process can be divided into several hierarchies, and since there can be only one criterion for making it into a sub-business process, the necessary changes belong to the main business process, or only one work is required. This is the case when a relatively large sub-business process is to be replaced because it wants to change.

[0006] The problem here is to enable a minimum necessary change to the business process definition and simultaneously operate a plurality of business processes that are slightly different from each other with relatively few resources.

[0007] In addition, for example, a change unique to each section is completed within that section, but if the business process definition of the general affairs department of Daigen is changed, the business process is changed and operated by each section. It is also an issue that changes are automatically reflected.

[0008]

In order to solve the above problems, in the workflow system of the present invention, the concept of object-oriented inheritance is applied to a business process so that the business process can be changed when the business process is changed. A method to automatically reflect the contents of changes to all derived business processes, a method to add a user's own procedure while keeping the rules held by the business process of the derivation source, and a changed object when changing the business process A means by which a definer of a business process specifies a changeable part and an impossible part is used.

Further, the present invention is a method for reading a business process definition in which a node defining a work is defined in order from a computer having a recording unit and displaying the business process definition, wherein the recording unit is the business process definition. Has the information in which the attribute information and the type information of the node included in are associated with each other, and the processing unit receives the instruction information for changing the business process definition from the user, and becomes the change target included in the instruction information for changing the business process definition. It is characterized in that the attribute information and the type information of the node are read from the recording unit, and the instruction information for changing the node to be changed is displayed on the screen based on the read attribute information and the type information.

[0010]

BEST MODE FOR CARRYING OUT THE INVENTION An embodiment of the present invention will be described in detail below with reference to the drawings. It should be noted that, hereinafter, the “business process” may be expressed as “BP” as necessary.

FIG. 1 is a block diagram showing a configuration example of a workflow system according to the present invention. The workflow system includes a work management server 1, a BP definition client 2 used by an administrator who defines a business process, a workflow client 3 used by an operator, and a network 10 connecting these devices.
The work management server 1 is a computer such as a server-dedicated machine or a personal computer, or a processing device.

On the storage device connected to the work management server 1, the BP definition name table 11 and the node name table 1
2, a BP definition table 13, a differential BP definition link table 14, a BP definition inheritance relationship table 15, and a branch condition table 16 are stored. The BP definition name table 11 is B
The BP definition name corresponding to the P definition ID is stored. The node name table 12 includes a node ID of each node that constitutes a business process, a node name, an attribute indicating whether change is possible or not, a node type indicating a branch node or a general node, and a business process to which the node belongs. Identifier (BP
ID) is stored.

The BP definition table 13 stores transition destination node IDs corresponding to node IDs, which represent to which nodes each node belonging to the BP definition is connected. The differential BP definition link table 14 stores a link source node ID and a link destination node ID, which represent a connection relationship of nodes connected across the BP definition.

The BP definition inheritance relationship table 15 is a derived B that indicates which BP definition the BP definition inherited.
P's BP ID, derivation source basic BP ID, and derived BP
Stores the creator and registration date of.

The branch condition table 16 stores a node ID, a branch destination node ID, and a branch condition of a node whose node type registered in the node name table 12 is a branch. In the case of a node that joins after branching, there is no branching condition, and the branching source node ID is used instead of the branching destination node ID.
To store.

In FIG. 1, the communication control unit interposed between the workflow management program 4 and the network 10, the workflow management program 4 and the table 1 described above.
The illustration of the database management program interposed between 1, 12, 13, 14, 15, 16 is omitted.

A workflow management program 4 is stored and executed in the processing device of the work management server 1. The workflow management program 4 receives the business process definition information from the BP definition client 2, and receives the BP definition name table 11, node name table 12, BP definition table 13, differential BP definition link table 14, BP definition inheritance relationship table 15, and Register in the branch condition table 16. Further, in response to the inquiry from the BP definition client 2, the BP definition name table 11 and the node name table 1
2. BP definition table 13, differential BP definition link table 14, BP definition inheritance relationship table 15, and branch condition table 16 are taken out and transmitted to the BP definition client 2.

When the work of the workflow client 3 is completed, the workflow management program 4 controls the transition from the node currently being activated to the next node. The workflow management program 4 changes the node in the basic business process to the node in the derived business process when transiting to the next node in the same business process, and from the node in the derived business process to the node in the basic business process. Workflow control is performed when transitioning to.

The BP definition client 2 is a computer such as a personal computer or a processing device. A BP definition program 5 is stored and executed in the BP definition client 2.

The BP definition program 5 displays a screen for defining a business process on a display device via a graphical user interface (GUI) (not shown) to assist the administrator in defining the business process. Similarly, in the inheritance process of the business process, the definition of the derived BP that inherits the basic business process definition is supported. Further, the defined business process definition information is transmitted to the work management server 1 via a communication control unit (not shown), and the BP definition name table 11, node name table 12, BP definition table 13, differential BP definition link table 14, BP Request to register in the definition inheritance relationship table 15 and the branch condition table 16. Further, the business process information received from the work management server 1 via the communication control unit (not shown) is displayed on the display device.

The workflow client 3 is a computer such as a personal computer, and the workflow client program 6 is stored and executed in its processing device. The workflow client program 6 includes a business program, which is an application program such as slip processing, which is executed when a worker gives a work instruction from the workflow management program 4 via a communication control unit (not shown). The workflow client program 6 starts the business program when a work instruction is received from the workflow management program 4 via a communication control unit (not shown), monitors the progress of the business program, and manages the work when the instructed work ends. It is a program for notifying the server 1 of the end of work via a communication control unit (not shown). Illustration of a communication control unit interposed between the workflow client program 6 and the network 10 and a GUI interposed between the workflow client program 6 and the display device / input device are omitted.

The work flow management program 4 is stored in a computer-readable storage medium and is read into the main storage device of the work management server 1 via a drive device (not shown) connected to the work management server 1 or another computer. Is transmitted to the main storage device of the work management server 1 via the network drive and the drive unit of the work management server 1
Can be performed by The same applies to the BP definition program 5 and the workflow client program 6. In addition, the workflow management program 4,
The BP definition program 5 and the workflow client program 6 are collectively stored in one or two or more storage media, and read into the main storage devices of the work management server 1, the BP definition client 2 and the workflow client 3, respectively, or the program By transmission, it is possible to transmit to each computer and execute.

In FIG. 1, the work management server 1 and BP
Definition client 2 and workflow client 3
Are shown as one each, but this is one of the embodiments, and a plurality of units can be used for each. It is also possible that the BP definition client 2 and the workflow client 3 have various tables stored in the storage device of the work management server 1.

FIG. 2 is a diagram showing the data structure of the BP definition name table 11. Each record of the BP definition table 11 is composed of a BP ID 21 and a BP name 22. B
The PID 21 is an identifier assigned by the workflow management program 4 for uniquely identifying the business process (BP). The BP name 22 is the name of the business process that the administrator gives when defining the business process, and corresponds to the BP ID 21. The BP ID 21 or the BP name 22 can be referred to as the business process identifier.

FIG. 3 is a diagram showing the data structure of the node name table 12. Each record of the node name table 12 is composed of a node ID 31, a node name 32, an attribute 33, a node type 34 and a BP ID 35. Node I
D31 is an identifier assigned to uniquely identify a node that constitutes a business process. The node name 32 is a name given to a node when an administrator defines a business process, and corresponds to the node ID 31.
The attribute 33 is an attribute given to a node by an administrator when defining a business process, and private represents unmodifiable and public represents modifiable. Node type 34
Indicates whether it is a general node or a special node such as a branch node. In the case of a branch node, the branch condition table 16 stores information about the branch. The BP ID 35 is the ID of the business process in which the node is defined. The BP ID is registered in the BP definition name table 11.

FIG. 4 is a diagram showing the data structure of the BP definition table 13. Consider the business process definition as a set of nodes that has information on transition destination nodes. Each record of the BP definition table 13 includes a node ID 41 and a transition destination node ID 42. The node ID 41 is
Node ID 31 registered in the node name table 13
Is an ID that uniquely identifies a node that constitutes a business process. Transition destination node 42
Is the ID of the node to which the node indicated by the node ID 41 transits. If the transition destination node ID 42 is "-", it indicates the end of the business process or does not transit to a node in the same business process. When the same ID exists in the same column for both the node ID 41 and the node ID 42, it indicates that the node is a branch node.

FIG. 5 shows the differential BP definition link table 14
It is a figure which shows the data structure of. BP definition table 13
Is a table for registering transition information of nodes within the same business process, whereas the differential BP definition link table 14 is a table for registering transition information between nodes across business processes. Each record of the differential BP definition link table 14 has a link source node ID 5
1 and a link destination node ID 52. The link source node ID 51 is an ID indicating a node defined in the business process of the transition source. The link destination node ID 52 is an ID indicating a node defined in the business process of the transition destination. Link source node I
Both D51 and the link destination node ID 52 correspond to the node ID 31 registered in the node name table 12.

FIG. 6 is a diagram showing the data structure of the BP definition inheritance relationship table 15. Each record of the BP definition inheritance relationship table 15 has a BP ID 61 and a basic BP ID.
62, creator 63 and registration date 64. BP
The ID 61 is an ID indicating a derived BP generated by inheriting the BP. The basic BP ID 62 has an ID of BP ID
It is an ID indicating a basic BP (derivation source BP or inheritance source BP) of the BP 61. When "-" is designated, it indicates that the BP ID 61 is a BP that is not inherited from any BP. Creator 63 is derived B
The name of the creator of P. Registration date 64 is 11, 12, 1
This is the date on which the derivative BP has been registered in the various tables 3, 14, 15 and 16.

FIG. 7 is a diagram showing a data structure of the branch condition table 16. Each record of the branch condition table 16 includes a node ID 71, a branch destination / source node ID 72, and a branch condition 73. The node ID 71 is an ID indicating a branch node. The branch destination / source node ID 72 is
It is an ID indicating a branch destination node or a branch source node of the node whose ID is the node ID 71. When the branch condition 73 is other than "-", the branch destination / source node ID 72 is designated with an ID indicating the branch destination node. In case of "-",
An ID indicating the branch source node is designated. Branch condition 73
Is the branching condition of the branching node whose ID is the node ID 71. If "-" is specified, the ID is the node ID
The branch node 71 is a branch end node instead of a branch start node.

FIG. 8 is a diagram showing a data example of a business process inheritance screen displayed on the display device of the BP definition client 2. In order to perform the inheritance, the basic BP is called by an operator's instruction via a file menu (not shown). Reference numeral 801 indicates the start of the business process, and 806 indicates the end of the business process.

Numerals 803, 804, and 805 are icons indicating normal work nodes, which are called general nodes. 802
Is a general node, but is a derived B created by inheritance
It is an icon indicating a BP that is not used in P.

Reference numerals 807, 808, 809, and 810 are general nodes, but are icons indicating nodes added later by inheritance.

Reference numerals 811 and 812 denote icons indicating branch nodes. The branch condition of the node is set via a drop-down list (not shown).

The registration menu 813 shows a screen for verifying the consistency of the business process and registering the derived BP. The consistency verification 814 is an instruction for checking whether there is a portion where the node cannot be connected due to a change in the basic BP or an incorrect inheritance. The derived BP registration 815 is
It is an instruction for registering the derived BP in various tables of 11, 12, 13, 14, 15 and 16.

FIG. 9 is a diagram in which a part of FIG. 8 is extracted in order to avoid the complexity and to illustrate a modification example at the time of inheritance. The private 901 is an identifier indicating that the node cannot be changed at the time of inheritance. public
Reference numeral 903 is an identifier indicating that the node can be changed at the time of inheritance. 902 is an icon indicating a general node changed by inheritance. This is public.
This is a node that can be changed so that the identifier 903 is designated. 904 and 905 are icons indicating nodes added by inheritance. This 90
With the addition of 4,905, 902 is 90 in the derived BP.
4,905.

FIG. 10 shows a derived BP by inheriting the basic BP.
5 is a flowchart showing a flow of processing for creating a.
After authenticating the operator of the BP definition client 2, the BP definition program 5 displays the BP inheritance screen on the display device (step 101). Operator wants to inherit B
The BP definition program 5 is instructed to call P as the basic BP, and the BP definition program 5 configures the basic BP (step 102). The BP definition program 5 determines whether the configuration of the basic BP has failed (step 10).
3). If it fails, the BP is inconsistent, and the operator corrects the inconsistent portion, and then the process returns to step 102 (step 104).

If the basic BP is successfully constructed, the basic B
P is displayed on the BP inheritance screen displayed on the display screen of the BP definition client 2 (step 10).
5). The operator attaches an icon showing a node required for the derived BP to the screen, connects the nodes with an arrow, and inputs necessary information through a drop-down list (not shown), so that the basic BP and the derived BP are connected. Difference BP which is the difference
Is created (step 106). After creating the differential BP, the BP definition program 5 is instructed through the consistency verification 88 to verify the consistency and determine whether or not the result is inconsistency (step 107).

If there is a mismatch, the operator corrects the mismatch and returns to step 106 (step 108). If there is no inconsistent part, the operator registers the derived BP 89
To the BP definition program 5 via the
Registered in various tables 1, 12, 13, 14, 15, and 16 (at this time, the operator is registered in the BP definition inheritance relationship table 15 as the creator 63) (step 10
9). It is determined whether the operator has selected "end", and if not, step 110 is repeated and the operator selects "end".
When is selected, the BP derivation is completed (step 11).
0).

FIG. 11 shows derived BPs 11, 12, 13,
It is a flow chart which shows a flow of processing registered into various tables of 14, 15, and 16. BP definition program 5
Starts the registration process according to the operator's instruction to register the derived BP, and assigns the BP ID to the derived BP (step 11).
1). The operator inputs the BP name, and the BP definition program 5 receives the information (step 112). The BP definition program 5 registers the BP ID and the BP name of the derived BP in the BP definition name table 11 as a set (step 11).
3). The BP definition program 5 registers the information of the node newly created at the time of creating the derived BP in the node name table 12 (step 114). The BP definition program 5 registers the transition information of the nodes forming the derived BP in the BP definition table 13 (step 115).

The BP definition program 5 searches the node name table 12 and registers the combination of the newly created node and the node belonging to the basic BP in the differential BP definition link table 14 (step 116). The BP definition program 5 searches the node name table 12 to find a branch node, and registers necessary information in the branch condition table 16 (step 117). BP definition program 5
Registers the BP inheritance relationship in the BP definition inheritance relationship table 15, registers the operator of the BP definition client 2 as the BP definition creator 63, and registers the current date (step 118).

FIG. 12 is a flow chart showing the flow of processing for forming a BP. The BP definition program 5 starts the BP configuration processing in response to the operator's instruction to call the BP, and sets the BP to be configured as the BP (step 121). The BP definition program 5 searches the BP definition inheritance relation table 15, finds the highest basic BP following the BP, and sets this as the BP (step 12).
2). The BP definition program 5 searches the differential BP definition link table 14 and the BP definition table 13 and performs node generation and connection of the BP according to the node transition information (step 123). The BP definition program 5 determines whether or not there is an inconsistent portion in the consistency verification (step 124). If there is inconsistency in the connection of the nodes, the process ends as a configuration failure (step 125).

If there is no inconsistency, it is judged whether the BP is a BP to be constructed (step 126). If the BP is the BP to be configured, the process ends as it is, and if not, the BP definition inheritance relationship table 15 is searched and the B
Find a derivative BP of P and use it as the BP, step 1
Return to step 23 (step 127).

FIG. 13 is a diagram showing an example of data on the BP edit screen displayed on the display device of the BP definition client 2 and an example of BP inconsistency. The identifiers and icons shown in common with FIG. 8 represent common identifiers and icons in FIGS. 8 and 13. The BP that edits
It is called and displayed on the BP edit screen according to an operator's instruction via a file menu (not shown). Since the BP is constructed in the process of being called, if there is an inconsistent portion, the BP definition program 5 shows that portion by an "x" mark. It should be noted that any other method may be used as long as it can be displayed with a symbol, a character, a figure, or the like indicating that it is inconsistent. Reference numerals 1303, 1304, and 1305 indicate locations where the mismatch actually occurs. The operator uses the on-screen operations such as pasting various icons, deleting icons, connecting arrows, etc.
Is edited and re-registered via the registration menu 813.

The cause of the inconsistency of the BP in FIG. 13 is 1
That is, the branch nodes 811 and 812, which were in the section indicated by the arrows 301 and 1302, were deleted. Difference node 8
07, 808, 809, and 810 include branch node 811 or branch node 812 in the transition destination or transition source node, except for 807 closest to the start node 801, so that they can be connected at the locations indicated by 1301 and 1302. Disappear.

FIG. 14 is a flowchart showing the processing flow of the consistency verification procedure. The BP definition program 5
Consistency verification is started in accordance with an instruction from the operator or the BP definition program 5 itself, and it is determined whether or not one of the currently generated nodes is pointed to (step 141). In the case of the pointed node, the BP definition program 5 determines whether the node pointed to by the node has been generated, and if not, step 1
If it has been generated, the process proceeds to step 144 (step 142). If the node is not pointed to from anywhere, the BP definition program 5 saves the location of the node using a save function (not shown), and returns to step 141 (step 143).

The BP definition program 5 determines whether all the nodes in the BP have been examined, and if so, the process ends (step 144). Select next node, step 14
Return to 1 (step 145).

As described above, by applying the concept of object-oriented inheritance to a business process,
The changes in the basic business process can be automatically reflected, and the inconsistencies caused thereby can be corrected by editing by the operator. Further, the changeable / unchangeable designation at the time of defining a business process is used at the time of defining a derived BP and enables inheritance by making the most of the basic BP. This solves the problem of the present invention that the maintenance property is improved.

What has been described here is one of the embodiments.
For example, tables 11, 12, 13, 14, 15, and 16
By using the to illustrate the inheritance relationship of the BP definition and the connection relationship of the nodes, it is possible to easily understand the complicated BP definition.

The program for implementing the present invention may be installed in a computer for use, may be stored in a recording medium accessible via a network for use, or may be read by a computer. It may be stored in a recording medium or may be in another form.

As described above, according to this embodiment, by applying the object-oriented concept of inheritance to a business process, the contents of the change are automatically reflected in all business processes derived from the business process. , It is possible to add a user's own procedure while keeping the rules held by the business process of the derivation origin, and allowing the definer of the business process to specify the changeable part and the impossible part. It can improve the maintainability of and facilitate understanding of complex and huge business processes.

[0051]

As described above, according to the present invention, the contents of the change are reflected in the business process derived from a certain business process, and the procedure unique to the user is maintained while observing the rule held by the business process of the derivation source. Can be added, and the definer of the business process can specify the changeable part and the unchangeable part, so that the variability and maintenance of the business process definition can be improved.

[Brief description of drawings]

FIG. 1 is a configuration diagram of a workflow system according to an embodiment.

FIG. 2 is a data configuration diagram of a BP definition name table 11 according to the embodiment.

FIG. 3 is a data configuration diagram of a node name table 12 according to the embodiment.

FIG. 4 is a data configuration diagram of a BP definition table 13 according to the embodiment.

FIG. 5 is a data configuration diagram of a differential BP definition link table 14 of the embodiment.

FIG. 6 is a data configuration diagram of a BP definition inheritance relationship table 15 according to the embodiment.

FIG. 7 is a data configuration diagram of a branch condition table 16 of the embodiment.

FIG. 8 is a diagram showing a data example of a business process inheritance screen for defining a derived BP.

FIG. 9 is a diagram showing a part of FIG. 8 for illustrating a modification example when inheriting.

FIG. 10 is a flowchart showing a flow of processing for creating a derived BP by inheriting a basic BP.

FIG. 11 is a flowchart showing a flow of processing of registering a derived BP in various tables of 11, 12, 13, 14, 15, and 16.

FIG. 12 is a flowchart showing the flow of processing that constitutes a BP.

FIG. 13 is a diagram showing an example of data on a BP edit screen and an example of BP mismatch.

FIG. 14 is a flowchart showing a processing flow of a consistency verification procedure.

[Explanation of symbols]

1 Work management server 2 BP definition client 3 Workflow client 4 Workflow management program 5 BP definition program 6 Workflow client program 11 BP definition name table 12 node name table 13 BP definition table 14 Difference BP definition link table 15 BP definition inheritance relationship table 16 Branch condition table

Claims (7)

[Claims] 1. A method for reading a business process definition consisting of a node defining a work stored in a recording unit of a computer and displaying the business process definition by a processing unit, wherein the recording unit is included in the business process definition. Information that associates the attribute information and the type information of the node to be processed, the processing unit receives the instruction information for changing the business process definition, and the processing unit of the node corresponding to the information of the node included in the received instruction information. Attribute information and type information are read from the recording unit, and based on the read attribute information and type information, information about a node included in the instruction information is displayed on a screen to display a business process definition. Method. 2. The information about the node includes at least one of attribute information of the node, type information of the node, information indicating a transition source of the node, and information indicating a transition destination of the node. A method for displaying the business process definition described in 1. 3. The attribute information includes information indicating whether a node is changeable or not changeable.
How to display the described business process definition. 4. The method for displaying a business process definition according to claim 1, wherein the type information includes information indicating whether the node is a general node or a special node. 5. The received instruction information, the read attribute information and type information when displaying information about a node included in the instruction information on a screen based on the read attribute information and type information. 2. When there is an inconsistent part, the inconsistent part is displayed with a code indicating that it is inconsistent, and the business process definition is displayed. how to. 6. A system for reading out a business process definition in which a node defining a work is defined in order from a computer having a recording unit and displaying the business process definition by a processing unit, the attribute of the node included in the business process definition. A recording unit that stores information in which information and type information are associated with each other, accepts instruction information for changing the business process definition, and attribute information and type information of a node corresponding to the node information included in the accepted instruction information. And a processing unit for displaying information regarding a node included in the instruction information on a screen based on the read attribute information and type information. system. 7. A program for reading a business process definition including information of a node defining a work from a computer having a recording unit and displaying the business process definition by a processing unit, the node being used when the business process definition is changed. Accepting change instruction information including an identifier, reading out information in which the node identifier, the node attribute information, and the node identifier stored in advance in the recording unit are associated with each other, and the accepted change instruction information and the change instruction When the attribute information of the node corresponding to the node identifier included in the information and the type information of the node are compared, and as a result of the comparison, there is a part where at least either the attribute information of the node or the type information of the node is inconsistent. Is displayed with a symbol indicating that the information related to the node where the inconsistency has occurred is inconsistent. A program that displays the business process definition characterized by