When modeling processes, it is very tempting to focus purely on the actors that undertake the relevant process tasks. Yet, processes often have a...
The terms ‘diagram’ and ‘model’ are often used interchangeably, yet there is actually an important difference between them. It can be useful to reflect on these differences when undertaking process analysis, management or improvement - and it can be particularly important when utilizing the BPMN approach to modelling.
In BPMN terminology a “Swimlane” represents both primary grouping BPMN elements - Pools and Lanes. But what are the common BPMN modeling mistakes encountered?
BPM defines four basic principles, which need to be followed, in order to successfully “taking care of processes”. In this article the first principle, “Processes are assets” is presented. In addition, the role of BPMN for supporting the first principle is investigated.
BPMN is a well-adopted process-modeling standard with good industrial support. Its major drawbacks are related to its complexity, which affects the end users as well BPMN tool vendors. This article provides a SWOT Analysis guide for any organization modeling and managing processes using the BPMN standard.
For two decades, the terms Business Process and Workflow co-exist. However, many professionals still misunderstood the terms and commonly think that a Business Process is just another term for a Workflow. This article will explain the commonalities and differences between both terms and terms related to their management and IT support.
BPMN Activities According to BPMN 2.0 specification, an activity represents “work that a company or organization performs using business processes.” In a BPMN process diagram, an...
Process approach is a common phrase, used in modern business. However, despite of its common use, there are many misconceptions around the phrase. This blog post tries to clarify the phrase as well the related concepts.
A quick introduction to BPMN Sub-Processes which includes hiding the complexity of a business process, and defining a contextual scope that can be used for data visibility, transactional scope, the handling of internal and external exceptions of events, or for compensation.
Graphically, a Flow is represented with an arrow between elements in a Process, Collaboration, or Choreography. BPMN 2.0 defines different kinds of Flows, which are explained in this article.