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
Posted on:
BPMN Diagrams – Hit the Links With Intermediate Events
Drawing business process diagrams can be tricky. Just getting the layout on the page to look good can be tricky. Intermediate link events can be used to clean up diagrams. They can also be used to jump from a specified point in one process to a specific point in another process.
Business Process Modeling
Posted on:
BPMN Diagrams – Intermediate Rule Events
Business process modeling is rarely applied to simplistic processes. Real world business processes often embody complex decision making. Complex decisions imply choices of action. Rule intermediate events, in BPMN, are designed to express these hard ideas with easy to read diagrams.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Play Catch With Intermediate Errors
Business Processes might start out as easy-to-diagram simple processes. Over time, these processes get more complex, as they have to deal with real-world considerations and unanticipated situations. Things can go wrong. Classical flow diagramming gets complex when dealing with errors or exceptions in a process, while BPMN modeling keeps things simple.
Business Process Modeling / Requirements / Requirements gathering
Posted on:
BPMN Diagrams – Never Too Late For An Intermediate Timer Event
Business process modeling in the real world requires us to represent how processes deal with exceptions, delays and deadlines. Intermediate timer events can be used to model deadlines and the business processes for handling them. See an example of how to model a business process where two deadlines expire and the business responds.
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 – Undefined Intermediate Events
There are 9 different intermediate events in BPMN. One of them, called the none intermediate event, is “undefined” in that it doesn’t specify a distinct behavior. Unlike the other intermediate events, the none intermediate event has a single interpretation, and will only be used with a specific methodology.
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.