Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| en:rule:single_process [2024-08-27 18:17] – Embedded diagram updated Anatoly Belaychuk | en:rule:single_process [2024-08-28 21:00] (current) – Anatoly Belaychuk | ||
|---|---|---|---|
| Line 333: | Line 333: | ||
| * Just as subprocesses should be placed at separate pages (diagrams), each process should be placed at a separate diagram when modeling collaboration. Communcating processes should be depicted as black boxes. | * Just as subprocesses should be placed at separate pages (diagrams), each process should be placed at a separate diagram when modeling collaboration. Communcating processes should be depicted as black boxes. | ||
| * If processes are connected by several message and/or data flows, they should be identified by names. Make sure that the same messages have the same labels. | * If processes are connected by several message and/or data flows, they should be identified by names. Make sure that the same messages have the same labels. | ||
| + | * Although BPMN spec allows dataflows connected to black box pools ([[#how to]], diagram below), not all BPMN modelers support this. | ||
| + | |||
| + | ===== Exceptions ===== | ||
| + | |||
| + | * It may be handy to depict several expanded processes on a single diagram for training/ | ||
| ===== See also ===== | ===== See also ===== | ||
