JP2009122985A - System and program for sub-process execution - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a means for making a business process executable without edition of a target business process, when inserting a sub-process into an existing business process. <P>SOLUTION: A business process execution engine 100 executes a main process of a main 1. The main 1 is a main process that executes the sub-process of a sub 1 at the time of starting, and executes the sub-process of a sub 2 at the time of completion. The business process execution engine 100 stores a sub-process execution condition definition 201 having the definition of conditions to be executed by the sub 1 and the sub 2. The business process execution engine 100 refers to the sub-process execution condition definition, and executes the sub 1 and the sub 2 when executing the main 1. Accordingly, by reference to the sub-process execution condition definition 201, it is possible to execute the business process without edition of the main 1, the sub 1 and the sub 2 when inserting the sub 1 and the sub 2 into the existing main 1. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a sub-process execution system and a sub-process execution program that execute a main process and a sub-process associated with the main process.

Traditional business processes
(1) defined as a single process,
Or
(2) It is divided into main process definition and sub process definition, and it is explicitly defined to call sub process in main process definition.
The execution engine executed business processes based on this static information. On the other hand, in the following Patent Document 1, a process (sub-process) to be executed in each department is automatically determined in a process across departments, and the determination of the sub-process also includes received data. The technique of performing to and is disclosed.
JP-A-10-111888

In the conventional business process processing method,
(1) Even a similar process definition having a unique process different for each department needs to be created as a separate process definition.
(2) When common processing is put in, there is a problem that it is necessary to edit all target process definitions. FIG. 11 is a diagram for explaining a case where common processing is performed. Conventionally, when the “confirmation process 13” is to be included as a process common to the finals of the “quotation request process 11” and the “ordering process 12”, it is necessary to edit all of the target process definitions. .

  It is expected that the problem (1) can be solved by applying the technique of Patent Document 1 to these problems, but the problem (2) cannot be solved.

  The present invention is for solving the above problem (2), and when a common process is put into an existing business process, the business process is executed without editing the target business process. For the purpose.

The sub-process execution system of this invention is
An identifier indicating a sub-process executed as a part of the main process, a specific condition for specifying a target main process on which the sub-process is executed, and an execution timing of execution of the sub-process in the target main process, An execution condition definition storage for storing subprocess execution condition definitions that define the relationship
A process definition storage unit that stores a main process definition that is a file of the main process and a subprocess definition that is the file of the sub process and includes an identifier indicating the sub process;
Read the main process definition and the sub-process definition stored in the process definition storage unit,
The predetermined main process indicated by the predetermined main process definition is executed according to the designation from the read main process definition, and the sub-process execution stored in the execution condition definition storage unit is executed when the predetermined main process is executed. It is determined whether or not the predetermined main process corresponds to the target main process by referring to the specific condition of the condition definition. If it is determined that the predetermined main process corresponds to the target main process, the execution condition definition storage unit stores When the subprocess definition indicating the subprocess to be executed for the predetermined main process is searched from the read subprocess definition by referring to the identifier of the subprocess execution condition definition and hit by the search, The subprocess definition that was hit Characterized in that a sub-processing section that executes the execution timing of the subprocess is stored in the execution condition defined storage the sub-process execution condition definition.

  According to the present invention, it is possible to provide means for executing a business process without editing the target business process when a sub-process is added to an existing business process.

Embodiment 1 FIG.
FIG. 1 is a diagram showing an example of the appearance of a business process execution system 1000 (sub-process execution system) that is a computer. In FIG. 1, a business process execution system 1000 includes a system unit 830, a display device 813 having a display screen of a CRT (Cathode / Ray / Tube) or LCD (liquid crystal), a keyboard 814 (Key / Board: K / B), a mouse. 815, FDD817 (Flexible Disk Drive), compact disk device 818 (CDD: Compact Disk Drive), printer device 819, and the like are provided with hardware resources, and these are connected by cables and signal lines.

  FIG. 2 is a diagram illustrating an example of hardware resources of the business process execution system 1000 according to the first embodiment. In FIG. 2, a business process execution system 1000 includes a CPU 810 (also referred to as a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, or a processor) that executes a program. The CPU 810 includes a ROM (Read Only Memory) 811, a RAM (Random Access Memory) 812, a display device 813, a keyboard 814, a mouse 815, a communication board 816, an FDD 817, a CDD 818, a printer device 819, and a magnetic disk device 820 via a bus 825. And control these hardware devices. Instead of the magnetic disk device 820, a storage device such as an optical disk device or a flash memory may be used.

  The RAM 812 is an example of a volatile memory. Storage media such as the ROM 811, the FDD 817, the CDD 818, and the magnetic disk device 820 are examples of nonvolatile memories. These are examples of a storage device or a storage unit, a storage unit, and a buffer. The communication board 816, the keyboard 814, the FDD 817, and the like are examples of an input unit and an input device. The communication board 816, the display device 813, the printer device 819, and the like are examples of an output unit and an output device.

  The communication board 816 is connected to a network (such as a LAN). The communication board 816 may be connected not only to the LAN but also to a WAN (wide area network) such as the Internet or ISDN.

  The magnetic disk device 820 stores an operating system 821 (OS), a window system 822, a program group 823, and a file group 824. The programs in the program group 823 are executed by the CPU 810, the operating system 821, and the window system 822.

  The program group 823 stores programs that execute the functions described as “to part” and “execution instance” in the description of the embodiment described below. The program is read and executed by the CPU 810.

  The file group 824 includes information described as “sub-process execution condition definition”, “main / sub-process definition”, “execution instance”, “determination result of”, “ Information described as “calculation result of”, “extraction result of”, “generation result of”, “processing result of”, data, signal values, variable values, parameters, etc. ~ "Database" is stored as each item. The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 810 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for CPU operations such as calculation, processing, output, printing, and display. Information, data, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during the CPU operations of extraction, search, reference, comparison, operation, calculation, processing, output, printing, and display. Is remembered.

  In the description of the embodiment described below, data and signal values are stored in the memory of RAM 812, the flexible disk of FDD 817, the compact disk of CDD 818, the magnetic disk of magnetic disk device 820, other optical disks, mini disks, DVDs (Digital). -It records on recording media, such as Versatile and Disk. Data and signals are transmitted on-line via the bus 825, signal lines, cables, and other transmission media.

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

  FIG. 3 shows a configuration block diagram of the business process execution system 1000 according to the first embodiment. The business process execution system 1000 includes a business process execution engine 100, a sub-process execution condition definition storage unit 200, a process definition storage unit 300, and a business APP 400 (hereinafter referred to as business APP (application)).

  The business process execution engine 100 includes a business application cooperation unit 111 (reception), a business application cooperation unit 112 (transmission), a process execution unit 120, and a sub-process processing unit 130. The business application cooperation unit 111 and the business application cooperation unit 112 are hereinafter referred to as a business APP cooperation unit 111 and a business APP cooperation unit 112.

  The sub-process processing unit 130 includes a process definition analysis unit 131, an execution instance 132, and a sub-process execution determination unit 133.

  The business process execution engine 100 and the business APP 400 may be connected via a network or may be connected on the same machine.

(Subprocess execution condition definition)
FIG. 4 shows an example of the subprocess execution condition definition 201 stored in the subprocess execution condition definition storage unit 200. The sub-process execution condition definition 201 will be described with reference to FIG. The sub-process execution condition definition 201 includes an identifier indicating a sub-process executed as a part of the main process, an extraction condition (specific condition) for extracting (specifying) a target main process that is a target on which the sub-process is executed, and Information defining the relationship with the execution timing of the execution of the sub-process in the target main process. In the sub-process execution condition definition 201 in FIG. 4, the identifier of the sub-process to be executed, the extraction condition of the target process (target main process) to be executed by this sub-process, and the sub-process execution timing indicated by the identifier A condition is defined.
(1) The “extraction condition” is the additional information (process definition name / main, sub, etc.) specified in the main / sub process definition (main process definition and sub process definition stored in the process definition storage unit) The conditions can be defined using the execution information generated during process execution (such as the user information that started the process / the contents of data passed from the business application). It is also possible to specify no condition.
(2) “Execution timing” can be specified at the start / end of a process or before or after execution of a specific process (eg, after the end of sub 1).

(Overview of operation)
The business APP 400 makes a processing request to the business process execution engine 100. The business process execution engine 100 performs processing described later in response to a processing request received from the business APP 400. As a result of the processing, a processing request is made to the business APP 400 (this may or may not be the same as the business application that made the processing request).

  The operation of the business process execution system 1000 will be described with reference to FIGS. 5 and 6 are sequence diagrams for explaining the operation of the business process execution system 1000. FIG. 7 is a diagram illustrating an example of a main process (definition name: main 1). FIG. 8 shows a subprocess (definition name: sub1) executed at the start. FIG. 9 shows a subprocess (definition name: sub2) to be executed at the end. FIG. 10 is a diagram conceptually showing this example.

  The sequence diagrams of FIGS. 5 and 6 show an example in which the sub-process of FIGS. 8 and 9 is applied to the main process of FIG. FIG. 4 shows the sub-process execution condition definition in this example.

(Initial processing)
FIG. 5 is a sequence showing the initial processing time in this example. At the time of initial processing, the process definition analysis unit 131 reads all the process definition files of the main / sub processes stored in the process definition storage unit 300 and changes the format for processing and holds it. Since the interface definition for linking with the business APP 400 is described in the process definition file, based on the interface definition, as shown in FIG. 5, "initialization 1.1", "initialization 1.1" .1 ”,“ Initialization 1.2 ”, and“ Initialization 1.2.1 ”, the business APP cooperation unit is initialized. Thereby, for example, an interface as a Web service is generated.

(Request processing)
Next, a description will be given with reference to FIG. FIG. 6 is a sequence showing processing when a request is transmitted from the business APP 400. In FIG. 6, “2: request” is a request corresponding to “waiting for reception (1)” in FIG. “3: Request” is a request corresponding to “Reception wait (2)” in FIG. Hereinafter, individual operations of the business APP cooperation unit 111 and the like in FIG. 6 will be described, and then the operation of FIG. 6 will be described.

(Business APP Linking Unit 111 (Reception))
The business APP linkage unit 111 receives a request from the business APP 400. This request includes an identifier designating the main process. In this example, as shown in FIG. 6, the identifier of “main 1” is included. The business APP linkage unit 111 transmits a request message obtained by converting the format of the received request (for internal processing) and a corresponding process definition identifier (main 1) to the process execution unit 120.

(Process execution unit 120)
The process execution unit 120 transmits the request received from the business APP cooperation unit 111 to the corresponding main 1 process definition analysis unit 131 based on the process definition identifier (main 1).

(Process definition analysis unit 131)
In the case of the first request of the process definition (main 1), the main 1 process definition analyzing unit 131 generates an execution instance. In the case of a request in the middle of process definition (for example, “3: request” corresponding to “waiting for reception (2)” in FIG. 7), the corresponding execution instance is searched and an execution request is transmitted.

(Execution instance 132)
When the execution instance 132 is generated, the execution instance 132 makes an inquiry to the sub-process execution determination unit 133, and if there is a sub-process corresponding to the sub-process execution condition definition 201, the execution instance 132 is executed. That is, when there is a corresponding subprocess, the subprocess execution determination unit 133 transmits an instance generation request to the process definition analysis unit 131 of the corresponding subprocess. In response to this request, the process definition analysis unit 131 generates an execution instance. Further, when an execution request is received, the execution instance receives information on a task to be executed next from the related process definition analysis unit 131 (for example, if it is waiting for reception in the initial state of FIG. 7 (1), “task 1 ”is applicable). The execution instance 132 updates the execution state of the process (initial, ~ after step execution, ~ wait, end, etc.) after execution, and makes an inquiry to the sub-process execution determination unit 133.

(Sub-process execution determination unit 133)
Upon receiving an inquiry from the execution instance, the sub-process execution determination unit 133 determines which process definition (main process, target department = material, target person = general employee) and execution state (initialization, after step execution, When the received message information is received and compared with the sub-process execution condition definition 201, the sub-process execution condition definition 201 is satisfied, and the executable timing matches the execution state of the current execution instance. The process definition analysis unit is requested to execute the subprocess.

(2, 2.1)
In FIG. 6, a case where the business APP cooperation unit 111 receives “2: request (main 1)” will be described. Upon receiving “2: request (main 1)”, the business APP cooperation unit 111 processes a request message obtained by converting the format of the received request (for internal processing) and the corresponding process definition identifier (the main 1). It transmits to the execution part 120.

(2.1.1)
Upon receipt of “request (main 1)”, the process execution unit 120 transmits this request to the corresponding “main 1” process definition analysis unit 131 based on the identifier (main 1) of the process definition.

(2.1.1.1)
Since the received request is the first request of “main 1”, the process definition analysis unit 131 generates an execution instance of “main process 1” in FIG.

(2.1.1.1.1)
Since the execution instance 132 is at the time of generation, it makes an inquiry to the sub-process execution determination unit 133, and if there is a sub-process corresponding to the sub-process execution condition definition 201, the execution instance 132 is executed.

(2.1.1.1.1.1)
When receiving an inquiry, if there is a corresponding subprocess, the subprocess execution determining unit 133 transmits an instance generation request to the process definition analyzing unit 131 of the corresponding subprocess. In this example, the sub-process execution determination unit 133 transmits a request to the sub-process definition analysis unit 131.

(2.1.1.1.1.1.1)
The corresponding process definition analysis unit 131 generates an execution instance in response to this request. In this example, the sub-1 process definition analysis unit 131 generates an execution instance of the subprocess 1.

(2.1.1.1.1.1.2)
The sub-1 process definition analyzing unit 131 transmits an execution request to the generated sub-1 execution instance. When the execution instance 132 of sub 1 receives the execution request, it executes “notification of completion mail” of FIG.

(2.1.1.2)
When “completion mail notification” is executed, the process definition analyzing unit 131 of the main 1 transmits an “execution request” to the execution instance of the main 1.

(2.1.1.2.1)
When the “execution request” is received, the execution instance 132 of the main 1 executes the task 1 (in this case, the order form creation in FIG. 7 corresponds), updates the execution state after execution, for example, in this case , “After task 1 execution” is updated, and an inquiry is transmitted to the sub-process execution determination unit 133. The sub-process execution determination unit 133 does not respond to the inquiry because “after task 1 execution” is not defined in the execution timing of the sub-process execution condition definition 201.

  The above is the processing operation for “2: request”.

(3 / 3.1)
Next, the processing operation for “3: request” will be described. In FIG. 6, a case where the business APP cooperation unit 111 receives “3: request (main 1)” (corresponding to reception waiting (2) in FIG. 7) will be described. Upon receiving “3: request (main 1)”, the business APP cooperation unit 111 receives a request message obtained by converting the format of the received request (for internal processing) and a corresponding process definition identifier (the main 1). Request (main 1) "is transmitted to the process execution unit 120 (3.1).

(3.1.1)
Upon receiving “request (main 1)”, the process execution unit 120 transmits this request to the corresponding “main 1” process definition analysis unit 131 based on the identifier (main 1) of the process definition.

(3.1.1.1)
Since the received “request (main 1)” in this case is a request in the middle of the process definition, the process definition analyzing unit 131 searches for a corresponding execution instance and transmits an “execution request”.

(4.)
When the “execution request” is received, the execution instance 132 of the main 1 receives information on a task to be executed next from the related process definition analysis unit 131 (in this example, the order execution (task 2) in FIG. 7). Acquire and execute order (task 2). After executing task 2, the execution instance 132 updates the process execution state (initial, ~ after step execution, ~ wait, end, etc.), and makes an inquiry to the sub-process execution determination unit 133. In this example, after the execution of the order (task 2) is executed, the execution state of the process is “finished”.

(4.1)
When receiving an inquiry, if there is a corresponding subprocess, the subprocess execution determining unit 133 transmits an instance generation request to the process definition analyzing unit 131 of the corresponding subprocess. As shown in the sub-process execution condition definition 201 in FIG. 4, the condition for executing the sub-process 2 is “execution timing = when finished”. Accordingly, the sub-process execution determination unit 133 transmits a sub-2 instance generation request to the sub-2 process definition analysis unit 131.

(4.1.1)
The corresponding sub-2 process definition analyzing unit 131 generates a sub-2 execution instance in response to this request.

(4.1.2)
The sub-2 process definition analyzing unit 131 transmits an execution request to the generated sub-2 execution instance. Upon receipt of the execution request, the sub-2 execution instance 132 executes “waiting for section manager approval” in FIG. This completes the process.

  With the business process execution system 1000 according to the first embodiment described above, when a subprocess is added to an existing business process, the business process can be executed without editing the target business process.

1 is a diagram illustrating an example of an appearance of a business process execution system 1000 according to a first embodiment. The hardware configuration of the business process execution system 1000 of Embodiment 1. FIG. 1 is a block diagram of a business process execution system 1000 according to Embodiment 1. FIG. FIG. 3 is a diagram illustrating a sub-process execution condition definition 201 according to the first embodiment. FIG. 3 is a sequence diagram of initial processing of the business process execution system 1000 according to the first embodiment. FIG. 3 is a sequence diagram when a request is received by the business process execution system 1000 according to the first embodiment. 4 is an example of a main process according to the first embodiment. An example of the sub-process 1 of the first embodiment. An example of the sub-process 2 of the first embodiment. FIG. 3 is a conceptual diagram of a processing operation according to the first embodiment. The figure which shows a prior art.

Explanation of symbols

  11 Quotation Request Process, 12 Ordering Process, 13 Confirmation Process, 100 Business Process Execution Engine, 111 Business APP Coordination Unit, 112 Business APP Coordination Unit, 120 Process Execution Unit, 130 Sub-Process Processing Unit, 131 Process Definition Analysis Unit, 132 Execution instance, 133 sub-process execution determination unit, 200 sub-process execution condition definition storage unit, 201 sub-process execution condition definition, 300 process definition storage unit, 400 business APP, 1000 business process execution system.

Claims (3)

An identifier indicating a sub-process executed as a part of the main process, a specific condition for specifying a target main process on which the sub-process is executed, and an execution timing of execution of the sub-process in the target main process, An execution condition definition storage for storing subprocess execution condition definitions that define the relationship
A process definition storage unit that stores a main process definition that is a file of the main process and a subprocess definition that is the file of the sub process and includes an identifier indicating the sub process;
Read the main process definition and the sub-process definition stored in the process definition storage unit,
Executing the predetermined main process indicated by the predetermined main process definition according to the specification from the read main process definition, and executing the sub-process stored in the execution condition definition storage unit when executing the predetermined main process It is determined whether or not the predetermined main process corresponds to the target main process by referring to the specific condition of the condition definition, and if it is determined that the predetermined main process corresponds to the target main process, the execution condition definition storage unit stores the determination result. When the subprocess definition indicating the subprocess to be executed for the predetermined main process is searched from the read subprocess definition by referring to the identifier of the subprocess execution condition definition and hit by the search, The subprocess definition hit Subprocess execution system, characterized in that a sub-processing section that executes in the sub-process execution timings of the execution condition definition the subprocess is stored in the execution condition definition storage unit. The sub-process processing unit
When executing the predetermined main process, the execution state is updated for each execution unit of the predetermined main process, and each time the execution state is updated, the sub process execution condition definition stored in the execution condition definition storage unit is updated. It is determined whether the predetermined main process corresponds to the target main process by referring to the specific condition, and if it is determined that the predetermined main process corresponds to the target main process, the sub-process stored in the execution condition definition storage unit By referring to the identifier of the execution condition definition, the subprocess definition indicating the subprocess to be executed for the predetermined main process is searched from the read subprocess definition. Defined in the subprocess execution condition definition stored in the condition definition storage 2. The sub-process execution according to claim 1, wherein the execution timing and the updated execution state are compared, and the sub-process indicated by the hit sub-process definition is executed if they are identical by the comparison. system. An identifier indicating a sub-process executed as a part of the main process, a specific condition for specifying a target main process on which the sub-process is executed, and an execution timing of execution of the sub-process in the target main process, Processing to store the subprocess execution condition definition that defines the relationship between
A process for storing a main process definition that is a file of the main process and a sub-process definition that is the file of the sub-process and includes an identifier indicating the sub-process;
The stored main process definition and the sub-process definition are read, the predetermined main process indicated by the predetermined main process definition is executed according to the designation from the read main process definition, and the predetermined main process is executed. When determining whether the predetermined main process corresponds to the target main process by referring to the specific condition of the sub-process execution condition definition, and determining that the predetermined main process corresponds to the target main process, By referring to the identifier of the execution condition definition, the subprocess definition indicating the subprocess to be executed with respect to the predetermined main process is searched from the read subprocess definition. Indicates the subprocess definition Subprocess execution program for causing to execute a process for performing serial subprocess defined timing to the subprocess execution conditions defined in the computer.

Images