In the 1990's it was rather usual to hear rumors about CASE tools, which, starting from diagrams, would generate for the programmer the source code of a whole system. There were promises that it would be the future of system development, many times making codification unnecessary. Also, there were predictions that it would replace the human being in many situations.
As time went by, it became clear that many CASE tools that had proposed 'magic' or simply do all man's work had failed or hadn't reached the proposed result.
This is natural, for a great deal of codes generated only by diagrams can have as a result a "dirty" twisted code with unnecessary instructions which turns maintenance or customization extremely complex for the programmer. Besides, many times, the final result is not the one expected by the analyst or the one promised by the CASE tool.
So, in case you're thinking we are proposing this kind of magic or simply massive code generation with no criteria for the programmer, we are not. The objective is another.
The first action we take to minimize these problems was NOT create a tool that generates code from diagrams. To allow customization expected by each development team, we understand that the right is to generate code from templates that can be customized for any developer.
To understand other strategies of this project, view the page of Features, FAQ and Comparative on our web-site.

