Information Technology Reference
In-Depth Information
successful or not. Based on the evaluation from the compilation activity, we will continue
with the happy path if the path of execution has no errors or exceptions, and produces the
expected successful output. If errors are found, it will send a notification to the developer
that corrections need to be made, go back to the other exclusive gateway (the one that
converges) and continue into the same path two steps behind. We need to evaluate wheth-
er this gateway will add unnecessary complexity to our model or whether it will help us to
better reflect what is happening. Once again, we need to be able to decouple how we are
representing the business scenario and the technical implications that our model will have
when we want to run it. We will see that these kinds of exceptional paths can also be
solved technically without adding more flow objects to our business processes diagram.
We need to find the right balance between the technical decisions and what the process
diagram represents for the business scenario.
A third option for our business process could be the following:
This third option includes three intermediate catching events. Two of them are boundary
events (they're attached to the border of an activity to capture such events from inside the
activity) and are error boundary events. They change the way the process was working by
going through the notification path if the compilation or the deployment throws an error.
