Interfaces. A well designed system will present simple interfaces with clear delineations of responsibility. All elements will be carefully named to minimize th

Interfaces. A well designed system will present simple interfaces with clear delineations of responsibility. All elements will be carefully named to minimize the potential for confusion or misuse. In such a system, diagrams become not only easy but semantically meaningful. Programmers use this to manage complexity, and in business domains laypeople should usually also be able to comprehend the chosen abstractions. To describe messages and related state transitions representing the function of a system over time, numbered arrows atop a block diagram can work well (essentially one visualization of a graph), but for more complex multi-component interfaces with a strong requirement for ordered messaging, message sequence charts are well received. https://www.mcternan.me.uk/mscgen/ https://www.mcternan.me.uk/mscgen/ There are two models of reality that I find to be the most useful ones, especially when writing programs. The first is functions, and the second is sequences of states. - Leslie Lamport .. via https://github.com/globalcitizen/taoup https://github.com/globalcitizen/taoup - see also https://en.wikipedia.org/wiki/State_machine https://en.wikipedia.org/wiki/State_machine - and you won't regret learning http://graphviz.org/ http://graphviz.org/