I worked on at least one project that used ObjecTime, a predecessor to UML. You <i>were</i> coding in it, in a very ship-in-a-bottle way. The article completely ignores how state machine patterns are done in UML, which ( IMO ) is where you start to see some gain. This being said, just doing state machines in a non-OO way isn&#x27;t exactly rocket surgery.<p>It was tolerable.  But changes were a bit expensive, and we kept a reference machine for builds, which was not very nice. The environment was hard to replicate - behind the scenes was a sandbox of Smalltalk and that was sort of ugly.<p>We did a port to Rose, but Rose was not, frankly, as capable.<p>What&#x27;s funny-peculiar  is - as described in your experience - the whole idea of &quot;architects that can&#x27;t code.&quot; At the very least there&#x27;s apparently no market for tools to enable that.