One danger of using a precise language like BPMN to describe business processes is that you can precisely get yourself into trouble. Deadlock (in BPMN) is a condition used to describe a process that can’t be completed. By designing (or describing) the wrong business process, you can create a process that never finishes.
Business Process Modeling
Posted on:
BPMN Compensation Event Correction
One of our readers (thank you!) pointed out that another blogger was critiqueing one of our earlier business process modeling notation (BPMN) diagrams. Turns out we made a couple mistakes. Here’s a more detailed look at the compensation end event.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Wait For An Intermediate Timer Event
Business process modeling requires us to model behaviors of people and organizations. Those behaviors often involve waiting. Prescribed delays, or waiting for a specific time or date is what we can represent with an intermediate timer event in the sequence flow of a BPMN diagram. This article shows an example of how to model this delay in a business process.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Boundary Intermediate Message Events
Intermediate message events can be placed on an activity boundary in BPMN. This use represents a form of exception handling for a task or sub-process, in response to an incoming message. This is a very different behavior than the ones we previously described, which show how to use intermediate message events in the course of the normal sequence flow of a business process.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – How To Use End Events (Part 2)
This is part two of a two part article. The first part is “How To Use End Events (Part 1)”. End events describe how a process ends. Often, the end of one process can initiate other behaviors within a business process. Like death and taxes, every business process has an end. Sometimes more than one.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – How To Use End Events (Part 1)
End events describe how a process ends. Often, the end of one process can initiate other behaviors within a business process. Like death and taxes, every business process has an end. Sometimes more than one.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Go With The Flow
BPMN Diagrams document business processes. Those processes have a flow to them, and that flow can branch and merge. It has a beginning and an end. Flow happens from the perspective of a single organization or person – but multiple people can talk to each other. Learn how to diagram flow and messaging in this article.