CN101694619A - Method for converting business process diagram into event driven bpel model - Google Patents

Abstract

The invention discloses a method for converting a business flow chart into an event-driven bpel model, which belongs to the field of information technology. The business flow chart is composed of a start activity, an end activity, multiple general activities representing specific tasks to be executed, and multiple logical structures connected through a number of directed connection lines according to the actual business logic, and the business flow chart is converted into event-driven According to the bpel model, the structured transformation is carried out first to obtain the structured business flow chart, and then the containerized transformation and serialized transformation are carried out; the container-level bpel text transformation is performed on the serialized business flow diagram, and each container is converted into a pair of bpel texts , and carry out the activity-level bpel code transformation, which is expressed in the bpel model as a pair of texts including a text header and a text tail, so far the transformation from the business flow chart to the event-driven bpel model is completed, so as to realize the simple modeling of the enterprise, Efficient execution of corporate workflow goals.

Description

Method of converting business flow chart into event-driven bpel model

technical field

The invention belongs to the field of information technology, in particular to a method for converting a business flowchart into an event-driven bpel model.

Background technique

Workflow technology is the key technology to realize enterprise business process automation, business process simulation, monitoring and so on. Business flow charts are widely used in various industries and play an indelible role in the actual business process management. However, the existing workflow business flow charts are relatively complicated, which is not conducive to popularization and use. The conversion between business flow chart and event-driven bpel model has always been the focus of business managers and scholars. The Bpel (Business Process Execution Language) language is easy for computer interpretation and execution, and has high operating efficiency, but there are deficiencies such as unintuitive model definition, too large model when describing the same function, and the need for users to have specialized computer knowledge.

Contents of the invention

The purpose of the present invention is to provide a method for converting a business flow diagram into an event-driven bpel model, wherein the business flow diagram consists of a start activity, an end activity, a plurality of general activities representing specific execution tasks, and a plurality of The logical structure is connected by several directed connection lines according to the actual business logic. The start activity indicates the start of the business, the end activity indicates the end of the business, and the directed connection line indicates the logical sequence of activities; if the activity or structure is connected to the starting point of the directed connection line , the directed link is called the output line of the activity or structure, otherwise it is called the input line, and the activity or structure is called the input activity or input structure of the directed link, otherwise it is the output activity; the business flow chart is converted into an event-driven The bpel model is divided into the following steps:

The first step is to perform structural transformation on the business flow chart to obtain a structured business flow chart. The transformation method is as follows: if an activity has multiple output lines, convert the output activities (or structures) of these multiple output lines into one Parallel structure; for the logical structure representing judgment, if it has an output line that turns forward, it is transformed into a loop structure, otherwise it is transformed into a selection structure; the parallel structure, loop structure and selection structure are all composed of a pair of structures Element composition;

The second step is to transform the structured business flow chart into a container to obtain a containerized business flow chart. The transformation method is as follows: convert the parallel structure into a parallel container, and use ParCon to represent the parallel container; convert the selection structure into a selection container, use IfCon Represents the selection container, converts each branch in the selection container into a selection sub-container, and uses IfcCon to represent the selection sub-container; transforms the loop structure into a loop container, and uses WhileCon to represent the loop container;

The third step is to serialize the business flow chart. In the second step, the containerized business flow chart is obtained, and all the activities or containers connected through the directed connection line are converted into a serial container, represented by SeqCon Serial container; convert all elements between the beginning and the end into a large serial container, named GlobalSeqCon;

The fourth step is to perform container-level bpel text transformation on the serialized business flow chart, and convert each container into a pair of bpel texts, which are called the text header and the text tail respectively, and convert the sub-activities (or The bpel text converted into sub-container) is placed between the pair of text converted into the container, and converted layer by layer according to this method, so as to convert the entire business flow chart into a bpel model. A pair of text converted into different types of containers is as follows Shown:

text content text header end of text serial container <bpel:sequence> </bpel:sequence> parallel container <bpel:flow> </bpel:flow> select container <bpel:if> </bpel:if> Loop container <bpel:while> </bpel:while>

The fifth step is to perform activity-level bpel code transformation on the serialized business flow chart. For the general activities in the business flow chart, the bpel code is executed in two steps: start task and submit task, so set a state for each activity Variable, the value range of the variable is "unstarted, to be started, started, submitted", and each activity is converted into two <bpel:while></bpel:while>, which are used to determine whether the task has been completed Started or submitted, if it has been started or submitted, it will jump out of the loop, otherwise it will continue to execute the loop, so as to realize the asynchronous waiting of the active task; at the same time, as the interface for the user to start and submit the task, define an event handler in the bpel model, the event A handle is represented in the bpel model as a pair of texts, where the head of the text is <bpel:EventHandle> and the tail of the text is </bpel:EventHandle>. Two event interfaces are defined for each activity between the text header and the text tail, one is the start task event interface, and the other is the submit task event interface, and each event interface is represented as a pair of text in the bpel model, where the text header It is <bpel:onEvent>, and the end of the text is </bpel:onEvent>. So far, the conversion from business flowchart to event-driven bpel model has been completed.

The beneficial effect of the invention is that the user can conveniently create the business flow chart of the enterprise, and the business flow chart can intuitively reflect the business-related processes of the enterprise such as operation, management, sales, logistics, and production. Compared with the enterprise business process modeling directly based on the bpel language, the invention requires less computer professional knowledge of users and has faster modeling speed. After the user establishes the business flow chart, the model conversion method of the present invention can be applied to generate a bpel model efficiently executed by the computer, thereby realizing the goal of simple modeling and efficient execution of the enterprise.

Description of drawings

Figure 1 is an example of a business flow chart for part design.

Fig. 2 is an example of the structural transformation diagram of the business flow chart of automobile chassis design, where c1- and -c1 form a parallel structure, c2- and -c2 form a selection structure, and c3- and -c3 form a loop structure.

Figure 3 is an example of a containerized transformation diagram of a business flow chart for automotive chassis design. Wherein, c1- and -c1 form a parallel structure, c2- and -c2 form a selection structure, and c3- and -c3 form a cyclic structure.

Figure 4 is an example of the serialization transformation diagram of the business flow chart of the automobile chassis design.

Figure 5 is an example of the bpel model of the car chassis design.

Detailed ways

The purpose of the present invention is to provide a method for converting a business flow chart into an event-driven bpel model. Figure 1 is an example of a part design business flow chart. The business flow chart consists of a start activity, an end activity, multiple general activities (the activities numbered 1-5 in Figure 1 represent specific tasks to be executed), and multiple logic The structure (the structure numbered 6 in Figure 1) is formed by connecting several directed connection lines according to the actual business logic, where the start activity indicates the start of the business, the end activity indicates the end of the business, and the directed connection lines indicate the logical order of the activities; If the activity (or structure) is connected to the starting point of the directed connection line, the directed connection line is called the output line of the activity (or structure), otherwise it is called the input line, and the activity (or structure) is called the input activity of the directed connection line (or structure), otherwise it is an output activity;

First, establish all the business-related processes of the enterprise, such as operation, management, sales, logistics, production, etc., as shown in Figure 2, which is a business flow chart of automobile chassis design. After establishing the business flow chart, follow the steps below to convert the business flow chart The model is converted to a bpel model:

The first step is to perform structural transformation on the business flow chart to obtain a structured business flow chart. The transformation method is as follows: if an activity has multiple output lines, convert the output activities (or structures) of these multiple output lines into one Parallel structure; for a logic structure representing a judgment, if it has an output line that turns forward, it is transformed into a loop structure, otherwise it is transformed into a selection structure; parallel structures, loop structures, and selection structures are all composed of a pair of structural elements ; Figure 2 shows an example of structural transformation of a business flow chart.

The second step is to transform the structured business flow chart into a container to obtain a containerized business flow chart. The transformation method is as follows: convert the parallel structure into a parallel container, and use ParCon to represent the parallel container; convert the selection structure into a selection container, use IfCon Represents the selection container, converts each branch in the selection container into a selection sub-container, and uses IfcCon to represent the selection sub-container; transforms the loop structure into a loop container, and uses WhileCon to represent the loop container. Figure 3 shows an example of containerized transformation of a structured business flow chart.

The third step is to serialize the business flow chart. In the second step, the containerized business flow chart is obtained, and all the activities (or containers) connected by directed connection lines are converted into a serial container to SeqCon represents a serial container; converts all elements between the start and end into a large serial container, named GlobalSeqCon. Figure 4 is an example of the serialization transformation of the business flow chart.

The fourth step is to perform container-level bpel text transformation on the serialized business flow chart, and convert each container into a pair of bpel texts, which are called the text header and the text tail respectively, and convert the sub-activities (or The bpel text converted into sub-container) is placed between the pair of text converted into the container, and converted layer by layer according to this method, so as to convert the entire business flow chart into a bpel model. A pair of text converted into different types of containers is as follows Shown:

text content text header end of text serial container <bpel:sequence> </bpel:sequence> parallel container <bpel:flow> </bpel:flow> select container <bpel:if> </bpel:if> Loop container <bpel:while> </bpel:while>

The fifth step is to perform activity-level bpel code transformation on the serialized business flow chart. For the general activities in the business flow chart, the bpel code is executed in two steps: start task and submit task, so set a state for each activity Variable, the value range of the variable is "unstarted, to be started, started, submitted", and each activity is converted into two <bpel:while></bpel:while>, which are used to determine whether the task has been completed Started or submitted, if it has been started or submitted, it will jump out of the loop, otherwise it will continue to execute the loop, so as to realize the asynchronous waiting of the active task; at the same time, as the interface for the user to start and submit the task, define an event handler in the bpel model, the event A handle is represented in the bpel model as a pair of texts, where the head text is <bpel:EventHandle> and the tail text is </bpel:EventHandle>. Two event interfaces are defined for each activity between the header text and the tail text, one is the start task event interface, and the other is the submission task event interface, each event interface is represented as a pair of text in the bpel model, where the header text It is <bpel:onEvent>, and the tail text is </bpel:onEvent>. So far, the conversion from business flowchart to event-driven bpel model has been completed.

The sixth step is to deploy the bpel model to the supporting bpel model engine (as shown in Figure 5), and the business process can be instantiated. After the instantiation, the enterprise can realize process automation and process monitoring.

Claims (2)

1. A method for converting a business flow diagram into an event-driven bpel model, characterized in that the business flow diagram is composed of a start activity, an end activity, a plurality of general activities and a plurality of logical structures representing concretely executed tasks through several Directed connection lines are connected according to the actual business logic, where the start activity indicates the start of the business, the end activity indicates the end of the business, and the directed connection line indicates the logical sequence of activities; if the activity or structure is connected to the starting point of the directed connection line, it is called a directed connection line. The connecting line is the output line of the activity or structure, otherwise it is called the input line, and the activity or structure is called the input activity or input structure of the directed connecting line, otherwise it is the output activity; the business flow chart is converted into an event-driven bpel model divided into The following steps: The first step is to perform structural transformation on the business flow chart to obtain a structured business flow chart; The second step is to transform the structured business flow chart into a container to obtain a containerized business flow chart; In the third step, the containerized business flow chart is obtained in the second step for serial transformation; The fourth step is to perform container-level bpel text transformation on the serialized business flow chart, and convert each container into a pair of bpel text; The fifth step is to perform activity-level bpel code transformation on the serialized business flow chart. For the general activities in the business flow chart, the bpel code is executed in two steps: start task and submit task, and convert each activity into a text header and the end of the text, which are used to judge whether the task has been started or submitted respectively. They are also used as the interface for users to start and submit tasks, as well as the start task event interface and submit task event interface. Each event interface is expressed in the bpel model as including text A pair of text at the head and the end of the text, so far the conversion from the business flow chart to the event-driven bpel model is completed. 2. according to claim 1 described business flow chart is converted into the method for event-driven bpel model, it is characterized in that, the concrete conversion method of above-mentioned each step is: The first step is to perform structural transformation on the business flow chart to obtain a structured business flow chart. The transformation method is as follows: if an activity has multiple output lines, convert the output activities or structures of these multiple output lines into a parallel structure ; For the logical structure representing judgment, if it has an output line that turns back forward, it is transformed into a loop structure, otherwise it is transformed into a selection structure; the parallel structure, loop structure and selection structure are all composed of a pair of structural elements ; The second step is to transform the structured business flow chart into a container to obtain a containerized business flow chart. The transformation method is as follows: convert the parallel structure into a parallel container, and use ParCon to represent the parallel container; convert the selection structure into a selection container, use IfCon Represents the selection container, converts each branch in the selection container into a selection sub-container, and uses fcCon to represent the selection sub-container; transforms the loop structure into a loop container, and uses WhileCon to represent the loop container; The third step is to serialize the business flow chart. In the second step, the containerized business flow chart is obtained, and all the activities or containers connected through the directed connection line are converted into a serial container, represented by SeqCon Serial container; convert all elements between the beginning and the end into a large serial container, named GlobalSeqCon; The fourth step is to perform container-level bpel text transformation on the serialized business flow chart, and convert each container into a pair of bpel texts, which are called the text header and the text tail respectively, and convert the sub-activities (or The bpel text converted into sub-container) is placed between the pair of text converted into the container, and converted layer by layer according to this method, so as to convert the entire business flow chart into a bpel model. A pair of text converted into different types of containers is as follows Shown: text content text header end of text serial container <bpel:sequence> </bpel:sequence> parallel container <bpel:flow> </bpel:flow> text content text header end of text select container <bpel:if> </bpel:if> Loop container <bpel:while> </bpel:while> The fifth step is to perform activity-level bpel code transformation on the serialized business flow chart. For the general activities in the business flow chart, the bpel code is executed in two steps: start task and submit task, so set a state for each activity Variable, the value range of the variable is "unstarted, to be started, started, submitted", and each activity is converted into two <bpel:while></bpel:while>, which are used to determine whether the task has been completed Started or submitted, if it has been started or submitted, it will jump out of the loop, otherwise it will continue to execute the loop, so as to realize the asynchronous waiting of the active task; at the same time, as the interface for the user to start and submit the task, define an event handler in the bpel model, the event A handle is represented in the bpel model as a pair of texts, where the head of the text is <bpel:EventHandle> and the tail of the text is </bpel:EventHandle>. Two event interfaces are defined for each activity between the text header and the text tail, one is the start task event interface, and the other is the submit task event interface, and each event interface is represented as a pair of text in the bpel model, where the text header It is <bpel:onEvent>, and the end of the text is </bpel:onEvent>. So far, the conversion from business flowchart to event-driven bpel model has been completed.

Images