&quot;Their stated goal was to no longer have to write any code in house, but rather nothing but UML&quot;<p>This goal was promoted heavily in the late &#x27;90s and early &#x27;00s.  Some tools could supposedly &quot;round-trip&quot; between UML and code, but I never saw that actually work.  As originally conceived, UML was supposed to foster communication and there are times when a UML diagram is the perfect means to communicate the intent.  I tend to use sequence diagrams and ER diagrams the most (yes - I know ER diagrams aren&#x27;t UML but they&#x27;re roughly analogous to class diagrams and what we&#x27;re usually trying to flesh out is the relationship between models).<p>As an aside, there were&#x2F;are graphical programming languages.  I wrote a couple of Windows and Mac utilities in ProGraph [1] during the &#x27;90s.  The ProGraph environment lives on as Marten [2] which I recently played with on Linux.  It&#x27;s not nearly as clean as I remember it being.<p>[1] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Prograph" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Prograph</a><p>[2] <a href="http:&#x2F;&#x2F;www.andescotia.com&#x2F;products&#x2F;marten&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.andescotia.com&#x2F;products&#x2F;marten&#x2F;</a>