This series of articles is dedicated to the explanation of common BPMN 2.0 terms, where this article will explain the terms Fork, Join, Branch and Merge as defined in the BPMN 2.0 specification.
This is the concluding part of our 'Managing Business Processes with BPMN: SWOT Analysis'. Here we take a look at the Opportunities and Threats of Managing Business Processes with BPMN.
BPMN specification defines an Activity as “Work that a company or organization performs using business processes”. But what are the common mistakes and how do you avoid making them?
In BPMN terminology a “Swimlane” represents both primary grouping BPMN elements - Pools and Lanes. But what are the common BPMN modeling mistakes encountered?
Business process modeling is a process of transforming actual business processes into models. The question, which occurs is, whether modeling is worth the spent time and money?
Commonly, it is misunderstood that IT has a direct influence on business value. Instead, the business processes are those that have direct impact on creating business value (see the first BPM principle), where IT just supports or automates those business processes.
We understand the term “asset” as any item of economic value owned by an individual or organization, especially that which could be converted into money. In this blog we take a look at how in BPMN Business Processes can be considered Organizational Assets too.
An event is a common BPMN process modeling element, which represents something that “happens” during the course of a process. But what are the common mistakes made and how do you avoid them?
Swimlanes are one of the five basic categories of BPMN elements and act as a container for partitioning a set of activities from other activities. BPMN 2.0 defines two different types of Swimlanes: Pools and Lanes.
There are many BPMN diagrams based on previous versions. This article shows how to visually assess the version and the approximate version and age of a BPMN diagram.