Ahnboyoung: /* Types of Sub-Processes */

2013-06-25T18:06:05Z

Types of Sub-Processes

New page

{{Cat|NobleProg BPMN Certification Level 1|02.1}}
[[Category:Private]]

== BPMN Activity Basics ==
=== An Activity ===
* is work that is performed within a Business Process
* can be atomic or non-atomic (compound)
* represent points in a Process flow where work is performed
* is executable element of a BPMN Process

=== Activities Type ===
* '''Task'''
** an atomic Activity within a Process flow
** is used when the work in the Process cannot be broken down to a finer level of detail
** an end-user or applications are used to perform the Task when it is executed
* '''Sub-Process'''
* '''Call Activity'''
** allows the inclusion of re-usable Tasks and Processes in the diagram

== Types of Tasks ==
{| class="wikitable"
|-
! Type !! Icon !! Explanation
|-
| 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
|-
| Receive start task
| [[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
|-
| 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
* The task is scheduled through a task list manager of some sort
Examples:
* Phone operator updates customer record
* User changing their 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
Examples:
* 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.
|-
|
|
|

|-
|}

{{PB}}

=== Receive, Manual and User tasks examples ===
<signavio>6e1d79cfa53a41d78b47ab613f14129a:67083c7a248419752b0c77271654b27bf4e5f57942a606758b3f3fbf2586d6_a2bb4b4b5f6914b96f6c9e8f34d6d734437b8a5ebab45d47e83a7adf9814c_66ba2dfbb8dc66af5bff544825da16e0ff8cf88b31435d7616a0ec37ced</signavio>

=== Business Rule and Script Tasks examples ===
<signavio>7012c6d14d2e41e88ee6390957e99d8b:752f4136d15ccd7313c58fec0402a7fefcdf8af6ff5317762663da0c52_53baf13f7975287d87d1abceded4d58b4285747f9345374d62a47bea99a29_aa50b48e909325d4140a5eb729a81f0122c7a97de8b2e9eea96363aa724e44</signavio>

 
 

=== Business Rule vs Gateways ===
<signavio>c29d1ba87d2b4e02afe7f40539f7143c:ec6332ffbef268e9a8d67dcfd3825679ac953dae8a9bd8a8865a122e38ba710_cbb990e49f514b532fe663e9423773806ef05676f33edb742482e646f439274_5cdd8ff8edc81b1f8aa27b1385112c44557557919369ee598b2dbbc7e5a494e</signavio>

{{PB}}

== Sub-process Markers ==
* A Sub-Process is an Activity whose internal details have been modeled using Activities, Gateways, Events, and Sequence Flows
* A Sub-Process is a graphical object within a Process, but it also can be “opened up” to show a lower-level Process

 

== Types of Sub-Processes ==
=== Collapsed ===
[[File:Figure10-25-sub-process-object-collapsed.png|120px]]

=== Expanded ===
[[File:Figure10-26-sub-process-object-expanded.png|400px]]

[[File:Figure10-27-expanded-sub-process-used-as-parallel-box.png| 400px]]

 
 

== Sub-process Markers ==
Makers can be combined.

[[File:Figure10-28-collapsed-sub-process-markers.png|650px]]

Activities - Revision history

Ahnboyoung: /* Types of Sub-Processes */