View source for OCEB2F 06 Business Process Modeling Skills

[[Category:Private]]
[[Category:OCEB2]]
==Module 6. Business Process Modeling Skills⌘==
<!--
===Uses of BPMN⌘===

There are three basic types of sub-models within an end-to-end BPMN model

*Private (internal)
*Internal to a specific organization
*Abstract (public)
*Represents the interactions between a private business process and another process participant
*Collaboration (global)
*Depicts the interactions between two or more business entities


===Abstract Processes⌘===

*Only those activities that are used to communicate outside the private business process, plus the appropriate flow control mechanisms are included in the abstract process
*Shows the private process as an empty pool

===Pools⌘===

*A pool is a '''participant''' in the process
*A participant can be a specific business entity (e.g. A company) or can be a more general business role (buyer, seller, etc...)
*Messages flowing into and out of a pool detail the content of the expected interface
*Graphically, a pool is '''a container for partitioning a process '''from other Pools, when modeling B2B
*Pools may not have any internal details ("Black Box")

===Composing Processes⌘===

*Proper BPMN syntax require all flow detail be sequenced
*There should be no gaps in the process among the flow details
*See Ad-hoc

===Designing B2B Processes⌘===

*A B2B business process involves two or more business partners. Each partner involves multiple "process participants" (Pools) to the table
*These are partner's back-office systems, e-business applications, employee interactions and other third-party elements
*The process systems deployed within, or extended toward each partner are responsible for the management of that partner's process participants.
*Thus, the BPMS can be seen as a gateway – a process-level firewall – connecting business partners that each have their own process management system or systems.

===Design of B2B Processes⌘===

*For collaborative commerce, the expression of a logically distributed process alone would not be sufficient.
*Even a single process with a centralized business design may need to be executed across a set of physically distributed systems, including systems owned by different companies.
*Because business partners normally interact with a large number of suppliers, customers and trading partners – hundreds or even thousands – companies often need to establish a common "interface process" in order to simplify the required technical integration '''at the network level'''

===Design of B2B Processes⌘===

*BPMN supports the concept of ''''public interfaces'''' and ''''private implementations''''. This is cover in the collaboration process type in the BPMN
*A deployed process usually instantiates the private implementation of a larger e-business process involving business partners.
*Partners participate by interacting through a '''public interface''', usually defined jointly by both sides.

===Collaboration Process⌘===
-->

===Advanced Events⌘===

====Terminate Event⌘====
:[[File:ClipCapIt-140901-131146.PNG]]
* This type of End indicates that all Activities in the Process should be immediately ended. 
* This includes all instances of multi-instances. 
* The Process is ended without compensation or event handling.
* Terminate end event in a sub-process ends only that sub-process (without ending parent process).

====Timer Events ⌘====
* Expresses a time gap in processing or a wait for a period of time.
* '''Start Timer''' – start on specific date (Monday at 9am, etc..) or a specific cycle (e.g., every Monday at 9am) 
* '''Intermediate Timer''' - a specific time-date or a specific cycle (e.g., every Monday at 9am)  
* If used in the main flow it acts as a delay mechanism
:[[File:TimerEvents.png]]

=====Timer Start Event⌘=====
[[File:TimerStartEvent.png]]
* Starts the Process on specific date (Monday at 9am, etc..) or a specific cycle (e.g., every Monday at 9am)

=====Timer Example 1⌘=====
[[File:BPMNTimerExampleEN.png]]

====Intermediate Boundary Events⌘====
[[File:BPMN_IntermediateEventExample.png]]

The process waits for a certain action to happen
* Can be attached to the boundary of an activity
** Message (arrives from a participant and triggers the Event)
** Timer (absolute date or cycle – e.g. Every Monday at 9 am) which tigers the event
** Error (only boundary of the activity)
** Signal (send to everyone)
=====Timer Example 2⌘=====
[[File:BPMNIntermediateTimerExample2EN.png]]

====Interrupting vs. Non-Interrupting⌘====
[[File:BPMNInterruptingVSNonInterrupting.png]]

====Signal Events⌘====
* A Signal is for general communication within and across Process levels, across Pools, and between Business Process Diagrams. 
* A BPMN Signal is similar to a signal flare that shot into the sky for anyone who might be interested to notice and then react. Thus, there is a source of the Signal, but no specific intended target.
:[[File:SignalEvents.png]]
=====Signal Event Example 1⌘=====
[[File:SignalExample.png]]
=====Signal Event Example 2⌘=====
[[File:SignalExample2.png]]

====Conditional Events ⌘====
* Is triggered when a condition such as "Temperature above 20°C" become true.
[[File:BPMNConditionalEvents.png]]

[[File:BPMNConditionalEventExampleEN.png]]

====Link Events⌘====
* A Link is a mechanism for connecting two sections of a Process.
* Link Events can be used to avoid long Sequence Flow lines.
* The use of Link Events is limited to a single Process level (i.e., they cannot link a parent Process with a Sub-Process or one pool to another pool).
* There can be multiple source Link Events, but there can only be one target Link Event.
* Link event must have name
[[File:LinkEvents.png]]

=====Link Events Example⌘=====
[[File:LinkEventsExample.png]]

=====Link Events as Off-Page Connector⌘=====
[[File:ClipCapIt-151001-142717.PNG]]

====Error Events⌘====

[[File:ErrorEvents.png]]
* An Error is generated when there is a critical problem in the processing of an Activity or when the execution of an Operation failed
*An '''Error''' indicates that a named Error should be generated.
*3 types of error events:
**Start '''Event Sub-Process''' Interrupting
**Intermediate '''Boundary''' Interrupting
**End
* Process can't wait for an error or rise an error in itermediate event (only in Boundary Intermediate)
* Process can't be instantiated using error event (only in Event Sub-Process)
=====Error Events Example 1⌘=====

[[File:BasicExceptionHandling.png]]
[[File:Ex02_BasicExceptionHandlingMerge.png]]

=====Error Events Example 2⌘=====

[[File:Ex03_ExceptionHandling.png]]

=====Error Events Example 3⌘=====
[[File:Ex04_ExceptionHandling.png]]

====Escalation Events⌘====

[[File:EscalationEvents.png]]
* An Escalation identifies a business situation that a Process might need to react to.
*In contrast to an Error, an Escalation by default is assumed to not abort the Activity to which the boundary Event is attached.

=====Escalation Example⌘=====
[[File:Escalation.png]]

===Task and Subprocesses⌘===

*Task
**A rounded rectangle (AKA roundtangle) showing the finest or atomic process step. It cannot be broken down to a finer level.
*Subprocess (collapsed)
**A roundtangle that can contain a series of other steps
*Subprocess (expanded)
**Shows all the subprocess activities
**May contain "-" sign

====Subprocesses⌘====
[[File:Figure10-27-expanded-sub-process-used-as-parallel-box.png|300px]]
*A Sub-process is a compound activity in that it has detail that is defined as a flow of other activities
*Expanded sub-process may be used as a mechanism for showing a group of parallel activities in more compact way
*Expanded sub-process does not need to include Start Event or an End Event and the sequence flow to/from these Events
====Subprocess Markers⌘====
[[File:Figure10-28-collapsed-sub-process-markers.png|800px]]
=====Ad-Hoc⌘=====
[[File:ClipCapIt-180607-164208.PNG]]
* Ad-Hoc Sub-Process contains a number of embedded inner activities and is intended to be executed with a more flexible ordering compared to the typical routing of processes
* It is possible to specify sequence flows between some of the contained activities.

=====Compensation⌘=====
[[File:Compensation.png]]
* '''Compensation''' is concerned with undoing steps that were already successfully completed, because their results and possibly side effects are no longer desired and need to be reversed. 
* If an Activity is still active, it cannot be compensated, but rather needs to be canceled.
* Compensation is performed by a compensation handler. A compensation handler performs the steps necessary to reverse the effects of an Activity.

=== Types of Tasks ⌘===
[[File:BPMNTypesOfTasks.png]]

==== Receive Task ⌘====
[[File:Figure10-15-receive-task-object.png|100px]]
* Waits for a Message to arrive from an external Participant
* Once the Message has been received, the Task is completed

[[File:Figure10-16-receive-task-object-that-instantiates-process.png|100px]]
* Starts the process
* MUST NOT have any incoming Sequence Flow
* Instantiate attribute MUST be set to true
==== Send Task ⌘====
[[File:BPMNSendTask.png|100px]]

* Sends a Message to an external Participant. 
* Once the Message has been sent, the Task is completed.

==== Service Task ⌘====

[[File:BPMNServiceTask.png |100px]]

* uses some sort of service, which could be a Web service or an automated application.

==== User Task ⌘====
[[File:Figure10-17-user-task-object.png|100px]]
* A typical “workflow” Task where a human performer performs the Task with the assistance of a software application 
* Examples:
** Phone operator updates customer record
** User changes his password

==== Manual Task ⌘====
[[File:Figure10-18-manual-task-object.png|100px]]
* Is expected to be performed without the aid of any business process execution engine or any application
* Example:
** A telephone technician installing a telephone at a customer location

==== Business Rule Task ⌘====

[[File:Figure10-19-business-rule-task-object.png|100px]]

* Provides a mechanism for the Process to provide input to a Business Rules Engine and to get the output of calculations that the Business Rules Engine might provide

==== Script Task ⌘====

[[File:Figure10-20-script-task-object.png|100px]]

* Is executed by a business process engine
* The modeler or implementer defines a script in a language that the engine can interpret
* When the Task is ready to start, the engine will execute the script
* When the script is completed, the Task will also be completed.

===Loops and multi-instance⌘===
==== Standard Loop ⌘====
[[File:LoopingActivity.png]]
*The Activity will loop as long as the boolean ''loopCondition'' is true
*The condition is evaluated for every loop iteration, and MAY be evaluated at the beginning or at the end of the iteration (''testBefore'' = true lub ''testBefore'' = false)
*In addition, a numeric cap can be optionally specified - ''loopMaximum''
*Loop activity instances are sequentially executed - one after another.
*Loop Activity is similar to DO WHILE loop.
==== Multi-Instance Activity⌘====

[[File:Element_multiple_instances_parallel.png|100px]] [[File:Figure10-48-activity-multi-instance-marker-for-parallel-instances.png|100px]] Multi-Instance parallel 

[[File:Element_multiple_instances_sequential.png|100px]] [[File:Figure10-49-activity-multi-instance-marker-for-sequential-instances.png|100px]] Multi-Instance sequential 
*The instances MAY execute in '''parallel''' or MAY be '''sequential'''.
*Multi-Instance Activites are used with collection of items
*Multi-Instance Activity is similar to FOR EACH loop

====Multi-Instance Activity Example⌘====

[[File:MultiInstanceActivityExample.png|600px]]

===Module 6. Questions⌘===
* What Types of Tasks are there in BPMN?
* What is the difference between Interrupting and Non-Interrupting event?
* What is the difference between Escalation and Error event?
* What is Link Event?
* What is Conditional Event?
* What is the difference between Signal and Message Event?