43 ms·
Flowcharts don't have state? Certainly some simple ones don't, but diagramming programs in flowcharts was not an uncommon method of presenting programs... well
by taeric 9y ago
Flowcharts don't have state? Certainly some simple ones don't, but diagramming programs in flowcharts was not an uncommon method of presenting programs... well, ever. Some of the introductory algorithms in Knuth's works use basic flowcharts. In some of his notes on computer languages, diagrams akin to what you are discussing were used by some smart people. So, don't take this as a criticism saying it is a bad idea.
More, this isn't to say these aren't worth looking at again. New and old things are always worth revisiting to see if something is different in the idea or the environment that we are in now.
That said, the UML world had several runs at diagrams that could do this. Activity diagrams being the more complicated ones, but what this is proposing seems to be the standard state machine diagrams.
It was not an unfounded (well, in my opinion) view that UML over complicated things. The problem appears to be that they were too complete in their modeling of the problems. And, these diagrams only really work in a "simple" sense if the viewers and the authors have a lot of shared context between them. The more of that context you put in the diagram, the more you will eventually remake UML's efforts. (Again, you will be in really smart company.)