<p>This "activity" diagram was created online using the free software at <ahref="https://app.creately.com/diagram/4nGSj2FkKGg/edit">https://app.creately.com/</a>
<p>We also have a "<ahref="seq-wallet.html">sequence diagram</a> which shows clearly the sequence of wallet actions in a time-line.
<p>Both "activity" and "sequence" diagrams are part of the UML software specifiction system. We also have a "<ahref="trogclass-1.html">class</a>" diagram for troggle.
That page also defines the "essential", "specification" and "implementation" levels at which troggle is designed and maintained.
<p><em>"The Statechart diagram is one of the five UML diagrams used to model the dynamic nature of a system. They define different states of an object during its lifetime and these states are changed by events. Statechart diagrams are useful to model the reactive systems. Reactive systems can be defined as a system that responds to external or internal events.</em>
<p>They were devised by David Harel, Weizmann Instiutute, in his paper: <ahref="https://www.inf.ed.ac.uk/teaching/courses/seoc/2005_2006/resources/statecharts.pdf">Statecharts: A Visual Formalism For Complex Systems</a> Science of Computer Programming 8 (1987) 231-274.
Or for a quicker cheat-sheet, see <ahref="https://instadeq.com/blog/posts/paper-didnt-read-statecharts-a-visual-formalism-for-complex-systems/">Paper; Didn't Read - Statecharts</a>