I'm going to say "no". In her example she mentions that the problem she's trying to solve is that flowcharts [1] need to be 3D to model multiple systems and com

I'm going to say "no". In her example she mentions that the problem she's trying to solve is that flowcharts [1] need to be 3D to model multiple systems and components operating in parallel, but that's just trying to push a single-system tool beyond it's usefulness. Trying to model multiple systems like that would lead to an explosion in the number of transitions very quickly. The closest we have nowadays to her "3D flowcharts" idea would be UML in general [2] and Orthogonal State Machines [3] in particular, but I think that what her problem really needed was better encapsulation and interfaces between systems. [1] https://en.wikipedia.org/wiki/Flowchart https://en.wikipedia.org/wiki/Flowchart [2] https://en.wikipedia.org/wiki/Unified_Modeling_Language https://en.wikipedia.org/wiki/Unified_Modeling_Language [3] https://en.wikipedia.org/wiki/UML_state_machine#Orthogonal_regions https://en.wikipedia.org/wiki/UML_state_machine#Orthogonal_r...