A process ends when there are no role instances with something to do … assuming of course that they cannot be revived into activity by an external event that they are waiting on.
|Tutor:||I hope you can see now why a RAD is not a flowchart.|
|Pupil:||Well, a flowchart — and, I guess, all the variations on the theme that I—ve seen being used — represents a simple, single, sequential flow of activity, a single thread with no possibility of multiple concurrent activity. A swim-lane diagram typically does no more than show the single thread trundling between roles. Even if we allow a thread to divide we aren—t getting the true concurrency that happens in the world.|
|Tutor:||Exactly. It is ...|