"Reverse Engineering" refers to the process of collecting information about your existing database and creating a new Model based on it.

"Reverse Engineer into Model" allows you to add objects from the database to an existing model.   You can also do this with the Database Compare feature, however, if you know what objects you want to add, this feature makes it easier and quicker.

ModelRight provides the ability to generate SQL DDL based on any Model changes. This can be very useful if you want a quick way to change the Database to reflect changes that you just made to your Model. You can do so without having to go through the Compare with Database process/wizard by using ModelRight's Generate Change Script feature:

Modeless Database Compare allows you to compare your Model with the Database as you design. You can keep the compare window open as you make changes to your Model. The mode-less compare window will automatically update to reflect your changes - so you can always have a view of how your Model differs from the database. You can import or export any differences without having to restart the compare process.

A Domain is simply an object that defines properties that other objects can "inherit". You can use Domains to classify your objects. For example, you might have lots of Columns in your Model that are some type of ID (Customer ID, Employee ID, etc...). Instead of having to assign common properties to them individually (a datatype of NUMBER, NOT NULL, etc..), you could create a Domain named “ID,” assign to it the common properties and then assign it to all of your ID Columns. That way you assure consistency of those properties across all of your ID Columns and you can easily change their properties simply by changing the ID Domain. So Domains provide an effective way to classify your objects, organize their properties, enforce consistency of property value and easily make changes across the class of objects.

Other products might define something like a Column Domain, but only ModelRight extends this capability to many more types of objects - like Tables, Relations, Indexes, Diagrams, Graphics, Tablespaces, Materialized Views, etc...

Whenever you make a change, ModelRight uses an internal "transaction" to contain the full impact of your change. When the transaction completes, it evaluates all of these changes and inserts an entry in this list so that you can see and report on the full impact of your change.

Simply select the object you want to edit and then change its properties in the Property Browser. Theres no need to constantly pop up dialogs to make changes. It's a common UI design that provides for better overall ease of use, but only ModelRight makes it available in a database design tool.

Of course ModelRight supports all the usual database objects like Table, View, Index, Constraint (PK, FK, UK). But ModelRight goes beyond the "least common denominator" approach taken by others and provides detailed, structured support for database specific features. It allows you to Generate, Reverse Engineer, and Compare objects like Materialized Views, Tablespaces, Clusters, Sequences, Packages, Procedures, Functions, Triggers, Synonyms, Schemas, Index-organized tables, Table and Index (Local and Global) Partitions and Subpartitions, Object/Structured Types and Tables, LOB storage options, REF columns, Function-based indexes, Fulltext Indexes, Filestreams, Computed/Virtual Columns, Collations, Character Sets, Engines, Logfile Groups, Databases, Tablespaces, Datafiles.