Differences

This shows you the differences between two versions of the page.

--- en:rule:do_not_save_on_gateways [2024-08-26 11:32] – [✔ How to] Anatoly Belaychuk
+++ en:rule:do_not_save_on_gateways [2024-11-27 16:44] (current) – [Do not save on gateways] Anatoly Belaychuk
@@ Line 1: / Line 1: @@
-====== 0-TBD Do not save on gateways ======
+====== Don't save on gateways ======
 {{tag>gateway}}
-{{en:underconstruction.png?nolink&200|}}
+Gateways make the diagram clear at first glance.
-Those willing to decrease the elements count make a diagram less readable.
 ===== ✔ How to =====
@@ Line 600: / Line 597: @@
 ===== Notes =====
-Put extra comments here (this section is optional)
+Some authors recommend using gateways when absolutely necessary only.
+They argue that reducing the number of elements makes a diagram more understandable.
+For example, Bruce Silver in his "Method and Style" book recommends implicit parallel split (saving diverging parallel gateway)
+and alternative routes join directly at the activity (saving converging exclusive gateway).
+Others, for the same reasons, recommend using conditional sequence flow (saving diverging exclusive gateway).
+These recommendations are doubtful: gateways shouldn't be considered as an useless ballast.
+They allow breaking a diagram into [[structured diagram|structural blocks]], thereby making the process logic explicit and easy to percieve.
 ===== Exceptions =====
@@ Line 729: / Line 732: @@
 ===== See also =====
-Reference similar rules here (this section is optional)
+  * [[structured_diagram]]
+  * [[explicit_parallel_split]]
+  * [[explicit_parallel_merge]]
+  * [[do_not_use_conditional_flows]]
+  * [[overlapped_flows]]
+  * [[alternative_paths]]
+  * [[time_flows_left_to_right]]
 ===== Author(s) =====
  --- //[[user:bell|Anatoly Belaychuk]] 2024-08-22 20:34//