The latest on Modelio.

icon contribute

This question is quite hard to answer. Developers are often difficult to convince.

Despite some impressive results, the volume of code generated from a piece of model may not be indicative of the ROI : once a project is completed, how much value did you gain from a model-driven approach?

This question raises other questions. How does code generation scale up? How does it match any project specificities? How is it working in a continuously changing project?


The "Improve your Java development efficiency with Modelio and UML" white paper provides answers to this question. One of them is that productivity and ROI must be measured at the project scale (analysis, design, tests, ...) including maintenance. This may raise interest for modeling approaches, provided that model and code are maintained in synch during the project's lifecycle, using appropriate tool functionalities.

One other answer closely addresses developer concerns. Developers already get code generation from their favorite IDE such as Eclipse, but since the IDEs do not know the original model, they usually provide first shot generation obtained from code introspection, but cannot update the generated code. They are frequently in the unpleasant situation of having part of the generated code that is not up to date with regard to the manually captured code. Code generation that guarantees global consistency is a real advantage.

^ Back to Top