This was also a point brought up in a recent talk [1] on software engineering, and what has happened since the "software crisis" was recognized in 1968.
The speaker, Mary Shaw, talks about Design Guidance, and how a decision chart is "a better organization of a body of design decision knowledge" [starts 27:40] and how we still, desperately, need something like that, and that there aren't any better ways to communicate such knowledge, that the speaker is aware of, than "this ancient chart."
(UML is mentioned later, but under the context that it is dying, which was probably a good thing.)
The speaker, Mary Shaw, talks about Design Guidance, and how a decision chart is "a better organization of a body of design decision knowledge" [starts 27:40] and how we still, desperately, need something like that, and that there aren't any better ways to communicate such knowledge, that the speaker is aware of, than "this ancient chart."
(UML is mentioned later, but under the context that it is dying, which was probably a good thing.)
[1] Progress Toward an Engineering Discipline of Software https://www.youtube.com/watch?v=lLnsi522LS8