Information Technology Reference
In-Depth Information
Next, the
<bpmn2:endEvent>
tag is defined. It represents the end of our business pro-
cess.
Finally, we find all the sequence flows; they join all the activities in a sequence. Note that
each
sequenceFlow
element specifies its
id
,
sourceRef
, and
targetRef
values.
So far, we have a very basic XML representation of our activities. Now, it's not just a dia-
gram. We have a formalized description of the activities that we have included in our pro-
cess and that can be used by technical people to add all the details needed to execute this
process.
Once we reach this state, a business analyst can start adding information about data that
will flow throughout the activities. Technical roles will be in charge of adding the inform-
ation about the external systems that will be contacted.
Version 2 of this process will include an
XOR Exclusive Diverging gateway
that will be
in charge of analyzing whether a compilation was successful. If not, a notification will be
sent to the developer that created the code and an
XOR Exclusive Converging gateway
will create a new User task to develop the required code, as shown in the following dia-
gram:
The following XML snippet from the
chapter-03/BPMN2-scenarios/src/
main/resources/sprintManagement-V1.bpmn2
file shows:
<bpmn2:exclusiveGateway id="_8" name="Compile OK?"
gatewayDirection="Diverging">
<bpmn2:incoming>_4_8</bpmn2:incoming>
<bpmn2:outgoing>_8_5</bpmn2:outgoing>
<bpmn2:outgoing>_8_9</bpmn2:outgoing>
</bpmn2:exclusiveGateway>
<bpmn2:exclusiveGateway id="_7" name=""
gatewayDirection="Converging">
<bpmn2:incoming>_9_7</bpmn2:incoming>
<bpmn2:incoming>_2_7</bpmn2:incoming>
