3 ms·
So Harel did form a company - iLogix (https://en.wikipedia.org/wiki/I-Logix https://en.wikipedia.org/wiki/I-Logix), which developed "no code" visual tools using
by streetcat1 7y ago
So Harel did form a company - iLogix (https://en.wikipedia.org/wiki/I-Logix https://en.wikipedia.org/wiki/I-Logix), which developed "no code" visual tools using statecharts, mainly for embedded systems.
Also, in early 2000, there was a movement for "executable UML", (https://en.wikipedia.org/wiki/Executable_UML https://en.wikipedia.org/wiki/Executable_UML).
Which was based on state charts, and tried to be the first version of what is today known as "no code".
However, then agile came alone, and we went back to "code is the design", so those methods did not find commercial success.
- brucou 7y agoI find your thesis interesting (that agile ended the top-down design approach resulting from statecharts modeling). Do you have any references/links I can review to support it? It is true that agile seems antithetic to Big Design Up Front (http://www.agilemodeling.com/essays/bmuf.htm http://www.agilemodeling.com/essays/bmuf.htm). However the methods did seem to have found commercial success (in safety-critical software) albeit not in front-end programming. I believe instead that the drivers of adoption/rejection are specific to the success factors in specific industries. That or maybe front-end programming is driven more by trial and error (+ hype?) than by engineering.