Why use EcoModeler as ECO UML modeling tool

  1. You can uninstall Together from Delphi 2006/2007. Removing Together (by also deleting the bpl files) will improve the responsiveness of your D2006 IDE, and make Delphi 2006/2007 startup speed increase.
  2. Increased reliability and stability. Check user feed back
  3. Users report a strong increase in productivity
  4. Eco State machines can be created for Delphi 2006/2007 Enterprise and Professional editions.
  5. A fully ECO customised GUI means that you are working with a UML tool that looks like it was made for ECO. Class derivation expressions, class default string representation, association embedding, association end delete actions, etc.
  6. Ability to build reusable models. Build a model, using BDS compile it as an assembly and use that dll (or model) as a building block in another model.
  7. The power of ModelMaker 9. Being based on ModelMaker 9 means that EcoModeler allows you to additionally create Use case diagrams, Robustness diagrams etc.
  8. You also have the refactoring tools, and method-override wizards. You may even model overloaded methods
  9. Full merging is supported from the model into a previously generated class. Modeled properties / methods which have renamed in the model will be renamed in your source. You can even add your own implementation properties / methods etc within your source file without risk.
  10. Regions added for auto hiding of ECO specific code, making your source more readable.
  11. Less autogenerated code. Each attribute/association only appears once in the source, the additional "protected _Attribute1" underscored protected properties are not generated because they are not needed. Exception: Attributes with HasUserCode - this is required by Eco.
  12. Neater code generation. EcoModeler generates more compact source code, including the addition of regions around ECO generated code.
  13. Better interface support. EcoModeler presents a time saving Interface Implementation Wizard whenever a class realizes an interface in the model. The advanced code-merge will also prevent any interface declarations added in code being lost when when the class's source code is regenerated.
  14. EcoModeler stores the entire model plus all diagrams in a single file. No need for a ModelSupport folder full of diagram files.
  15. EcoModeler is customizable. It is possible to add custom editors, or even additional tabs in existing editors. A comprehensive model API allows you to write plug-ins capable of manipulating your models in code.

Feedback from EcoModeler users