activity-diagram

Use fork/join or decision/merge nodes in an activity diagram for modelling user choices?

荒凉一梦 提交于 2019-12-08 13:29:47
问题 I was trying to use the activity diagram to model user interactions with a GUI, and came across the following question: whether to use decision/merge nodes or fork/join nodes in modelling different user choices. For example, a user can either change the settings of the program by clicking a button, or launch a process by clicking another button. It seemed to me using decision/merge nodes and a control arrow pointing back to the decision node is more natural, as the choices cannot be taken in

Join and Merge in activity diagram

我的梦境 提交于 2019-12-03 14:38:18
What is the difference between Join and Merge in Unified Modeling Language Activity Diagram. Give an example to understand more clearly. Join Node (see reference 1 ): Join node is a control node that has multiple incoming edges and one outgoing edge and is used to synchronize incoming concurrent flows . Join nodes are introduced to support parallelism in activities . Merge Node (see reference 2 ): Merge node is a control node that brings together multiple incoming alternate flows to accept single outgoing flow. There is no joining of tokens. Merge should not be used to synchronize concurrent

Difference between behavior of fork/join nodes toward tokens with other nodes of Activity diagrams

自闭症网瘾萝莉.ら 提交于 2019-12-02 05:11:28
As Thomas Kilian described here , normal behavior of nodes of Activity diagrams with tokens is: A node becomes active when at all of its incoming InformationFlow connectors a token has arrived. When the node finalizes it sends single tokens along all its outgoing InformationFlow connectors. But also he added: There are special nodes like fork and merge which behave a bit different I know that behavior of "merge" node differs because it becomes immediately active by receiving first token and accepts one among several alternate flows. But what is the difference between behavior of fork/join