![]() ![]() ![]() 2Īgain, you could have modeled the implicit join explicitly, too. However, here one might decide that the implicit join contributes to readability. You could have modeled the implicit join happening at this task with an exclusive joining gateway. Instead, use link events to connect points which are not on the same page or screen anymore. The reader will lose any sense of what such lines actually mean. This order will often also lead to a minimum of crossing lines.Īvoid very long (multi page) sequence flows, especially when flowing against the reading direction. Often, you will find a "natural" order of pools reflecting the order of first involvement of parties in the end-to-end process. Oftentimes, removing lanes can improve readability! Rearrange the order of pools in a collaboration diagram to avoid message flows crossing pools as much as possible. Rearrange the order of lanes and paths to make your sequence flows more readable. The same applies to incoming flows on the right of a symbol.Īvoid flows crossing each other and flows crossing many pools or lanes, wherever possible. However, this would have decreased readability, because the flow connection violates the reading direction. The author could have attached the sequence flow, leaving this task on its left. However, by consciously choosing to partly overlap those flows, this model becomes less cluttered, therefore less confusing and easier to read. The author could have made the five (!) sequence flows leading into the end event visible by separating them. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |