I wonder if you could use annotations to manage the visuals e.g http://drakon-editor.sourceforge.net/folder-night.png
You'd have an inline annotation to separate the code blocks and generate the visuals so you don't have to maintain/update two places.
Any tool that does that?
Flow charts get confusing after some complexity. Useless if you want to represent multiple actors + messages. Systems/sub-systems view.
There is a tendency to think of visual programming as an all or nothing. Either we have all text or all visual. As long as it is "Write once, update everywhere", visual tools can be useful in navigating new code bases, obtaining insights and quickly understanding a piece of code.
The problem though is they often require maitenance and get out of date with reality (even if it is comments/annotations)
I wonder if you could use annotations to manage the visuals e.g http://drakon-editor.sourceforge.net/folder-night.png You'd have an inline annotation to separate the code blocks and generate the visuals so you don't have to maintain/update two places. Any tool that does that?
Also, integrating different level of complexity using system 1,2,3 (from https://www.amazon.ca/Software-Requirements-3rd-Karl-Wiegers...) to represent user flow diagram in addition to flow charts.
Flow charts get confusing after some complexity. Useless if you want to represent multiple actors + messages. Systems/sub-systems view.
There is a tendency to think of visual programming as an all or nothing. Either we have all text or all visual. As long as it is "Write once, update everywhere", visual tools can be useful in navigating new code bases, obtaining insights and quickly understanding a piece of code.
The problem though is they often require maitenance and get out of date with reality (even if it is comments/annotations)