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.
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.
As an ISO/IEC 19510:2013 standard and de-facto standard for business process modeling, the Business Process Model and Notation (hereinafter referred to as BPMN) defines a graphical notation for representing business processes in form of business process diagrams.
This post presents 10 key BPMN elements, which should be learned prior to creating your first business process diagrams. These 10 key BPMN elements represent a sub-set of the descriptive class of BPMN 2.0 elements.
With the release of BPMN 2.0.1 in 2013, the Business Process Model and Notation became an ISO/IEC 19510:2013 standard. This blog post explains why this is important.
The first article of the series “Supporting core BPM principles with BPMN 2.0”, presented business processes as organizational assets that are central to creating value for customers.
An introduction to BPMN Collaboration Diagrams. For complex collaborations more detail is needed, this information can be captured by Choreography Diagrams. Watch this is video guide to see how Choreography Diagrams can benefit you and your organization.
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.
In this article, we will firstly address how popular BPMN really is, by analyzing some of the existing studies. Secondly, we will define who uses the notation and thirdly, to what end.
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.