6-7 minutes<\/p>\n
Business Process Modeling Notation (BPMN) is a graphical representation for specifying business processes in a business process model. BPMN was developed by the Business Process Management Initiative in 2000. The aim was to standardize how processes were visually represented, and that aim has been carried on since 2004 by Object Management Group (OMG).<\/p>\n
The objective of BPMN is to support business process management for both technical users and business users by providing a notation that is intuitive to business users yet able to represent complex process semantics.<\/p>\n
A key element of BPMN is the choice of shapes and icons used for the graphical elements identified in this specification. The intent is to create a standard visual language that all process modelers will recognize and understand. The basic shapes of BPMN are very similar to flow diagrams, but instead of representing pure logical stages, they can also represent business-specific actions, like messaging other departments, and escalating issues.<\/p>\n
Activity An activity is a work that is performed within a business process. Event An event is something that happens during the course of a process. Gateway A gateway is used to control the divergence, and convergence of sequence flows in a process. Flow Two major flow elements are core to BPM:<\/p>\n
\u00b7 A sequence flow is used to show the order that activities will be performed in a process.<\/p>\n
\u00b7 A message flow is used to show the flow of messages between two participants of a process.<\/p>\n
An event is a common Business Process Model and Notation (BPMN) process modeling element that represents something that \u201chappens\u201d during the course of a process. In BPMN, events are expressed as circles. Events indicate when some event occurs at the start, end or during a process (as opposed to when some task or activity is performed):<\/p>\n
Simple BPMN Diagram Example<\/p>\n
A boundary event is an event shown on an activity boundary that can be triggered or thrown at any time while the associated task or activity is being performed. In other words, a boundary event is a type of intermediate event.<\/p>\n
In the example below, a Timer boundary event is shown. Some boundary events are time-based while others are based on a condition which must resolve to \u2018True\u2019 in order for that branch of the flow to proceed.<\/p>\n
Introduced in BPMN 2.0 is the concept of non-interrupting events. Interupting and non-interupting events are only relevant to intermediate events, especially boundary intermediate events. Boundary events can further be divided into two types: interrupting and non-interrupting, as a boundary events are associated with flow elements and can be configured to interrupt their usual behavior. They are illustrated with a solid line and a dashed line respectively.<\/p>\n
An interrupting event (solid line) is more common that a non-interrupting event(dashed line). As the name implies, once triggered, the current task stops and the flow of control continues along the new path.<\/p>\n
A non-Interrupting Timer Event attached at the boundary of the sub process A will not be interrupted. Sub process A will complete and the flow will continue on to subprocess B while a parallel flow will continue from the Non-Interrupting Timer Event onto the Handle Timeout sub process.<\/p>\n
In BPMN there are three types of events. Start Events, Intermediate Events, and End Events. All of these can be catching and throwing events.<\/p>\n","protected":false},"excerpt":{"rendered":"