While the internals of ECO are complex, using it is very easy. The classes of the problem domain such as Customers and Invoices are defined in a Class Model.

ECO will then generate the database schema, the code for the domain classes, and the information for mapping the classes to the database tables.

And better yet, when you change your model, ECO will merge the changes into your code, and update your database schema while preserving your precious data. A feature we refer to as Database Evolution.

However, far from being a mere code generator and Object-Relational mapper, ECO provides extensive framework support for the domain objects at runtime, including databinding, querying, and UnDo/Redo operations. In addition the model itself is available at runtime, so that concepts in the model that do no translate directly into code are still available for ECO, as well as for the developer.

So the goal of ECO is not only to create the code and database from the model, but also to make the ECO objects efficient building blocks for your application, eliminating a lot of rote programming. Our company name CapableObjects, alludes to this fact.

Listen & watch the Framework Argument Presentation to get an overview on what we do for You and how You will benefit from using ECO in your existing and new software projects.

There is more information about ECO on our old site. We are working on migrating it.

• ECO IV Overview
• Maintaining your business classes and relationships as UML diagrams.
• UML state diagram execution.
• In-memory transactions.
• Multiple undo/redo support.
• OCL expression evaluation.
• Quick application prototyping.
• Multi-user synchronization.
• Automatic creation and modification of your database schema.
• Custom mapping to existing databases via XML mapping information.
• Support for updating multiple databases.
• Reusing business classes (UML packages) across multiple applications.