UML14 — (Minor) Activity diagram change recommendation

Summary: I know it"s late in the game, but in my use of activity diagrams for
modeling algorithms, a minor change has become apparent. Specifically, it
is possible to have objects "flow" from one activity state to another, but
it is not possible to show a persistent object which is modified by some
activity states and used by others. I therefore recommend the following change:

Activity states be able to depend on objects with stereotypes for <<use>>
and <<modify>>. In this case, control flow among the activity states must
be shown since the "data object" does not flow between activity states but
exists in an enclosing structural context.

No Data Available