In a business process, sub-processes have several use cases. Watch this short video guide to learn about the various types of BPMN Sub-Processes and how by utilising them you can benefit both you and your organization.
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.
Knowing when to show automation and IT on a process diagram is a tricky balance. Show too much, and stakeholders will 'turn off'. Yet...
This is past 1 of 'Managing Business Processes with BPMN: SWOT Analysis' where we take a look at the strengths and weaknesses of Managing Business Processes with BPMN. Next week we'll take a look at the Opportunities and Threats.
When modeling processes, it is very tempting to focus purely on the actors that undertake the relevant process tasks. Yet, processes often have a...
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.
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.
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.
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.
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.