Chapter 4
Part1
Handling complexity
1
Complex Gateway
2
AND OR XOR
3
proceeds
incoming
incoming
outgoing
ongoing
Gateways
4
AND
AND-Split  takes all
outgoing branches
AND-join  proceeds
when all incoming
branches have completed
Gateways
5
XOR-split  takes ONE
outgoing branch
XOR-join  proceeds
when ONE incoming
branch has completed
XOR
Condition 1
Condition 2
Gateways
6
OR-split  takes ONE/MORE
outgoing branches depending
on condition
OR-join  proceeds when all
ACTIVE incoming branches
have completed
OR
Condition 1
Condition 2
Gateways
7
A Complex Gateway allows the modeler to specify any
random rules needed to determine how to produce tokens
or process arriving tokens.
Complex gateway
Dead Path Elimination.
+
Business Rule
Complex Split
Complex Gateway
An example of the use of a complex gateway.
8
Complex Merge
Complex Gateway
Questionable usage of the complex merge gateway.
9
Complex Merge
Complex Gateway
A complex merge pattern solved with explicit merge points.
10
A complex merge pattern using a subprocess.
Complex Merge
Complex Gateway
11
12
The Error and Escalation events are similar in that they provide a way to stop
an ongoing subprocess and change the course or correct a situation.
Escalation event can also throw events and continue processing without
stopping the process or subprocess.
Escalation represent a planned condition created inside the process that must
be handled outside the normal flow
Error events always stop the branch of the subprocess that they are on.
Events And Error Handling
Error events & Escalation Events
Error Escalation
Events And Error Handling
Error events
13
14
Events And Error Handling
Escalation Events
15
Events And Error Handling
Escalation Events
16
Events And Error Handling
Escalation Events
17
Events And Error Handling
Basic exception handling flow.
18
Thank You

ch04-part1.pptx

Editor's Notes

  • #8 dead path elimination. asterisk
  • #9 A use case to declare an executive review of a product line requires a business process to check concurrently whether the product has high legal liabilities, is subject to frequent quality post-manufacture returns, and has unsatisfactory internal quality checks. The outcomes of these checks is to be evaluated so that as soon as two of these checks pass and the product doesn’t have any high liabilities, a clean product state is declared and the third check is aborted. تتطلب حالة الاستخدام للإعلان عن مراجعة تنفيذية لخط الإنتاج عملية تجارية للتحقق بشكل متزامن مما إذا كان المنتج لديه مسؤوليات قانونية عالية ، ويخضع لإرجاع جودة متكرر بعد التصنيع ، ولديه فحوصات جودة داخلية غير مرضية. يجب تقييم نتائج هذه الفحوصات بحيث بمجرد اجتياز اثنتين من هذه الفحوصات وعدم وجود أي مسؤوليات عالية للمنتج ، يتم الإعلان عن حالة المنتج النظيف وإلغاء الفحص الثالث.