The ability to set classes and to make parent links from symbols to pages makes it easy to quickly build a model. However you can also build models without them being consistent.

For example you may have added diagrams or objects without setting their classes.

Model review provides the means to check and to a degree automatically make the model consistent

It is loaded through the menu >Model >Review in the main menu

Tabs select different type of review criteria.

Note - in general if you see a page number in Model Review you can double click it to open the diagram.

(See also Model Advisor)

Parent Class <> Child

Shows all objects whose class is different from that of it's child diagram. Generally you would not want that, although there may be exceptions. You can correct these by dragging a Child Class cell to a Parent class cell in the same Row and visa versa to change classes. You are prompted first. Or you can make all Parent Symbol Classes match their child pages with the All Parents to Child button

Not allowed in Page Class

Shows all objects whose class is not allowed on the class of diagram it is on, according to the Model Rules that you set in Configure Rules

Object Class <> Symbol Class

Shows all objects whose class is different from the class of the generic object. See Object Tags

Orphan Pages

Shows all diagrams that have no parent or jump links to them.

Page Links

Provides a means to see quickly what parent symbols each page.

Model Hierarchy

See Model Review Hierarchy

Non Included Parent Classes

Provides a way to find if there are parent objects with classes that do not populate the object and instance tables. Generally you would not want that, although there may be exceptions. You should you link a symbol to a page by a jump link if the link is not intended to produce objects and instances, for example to expand on an explanatory note.

Fix Connections

It is possible to change connection signals at one end only, so yuo may get the situation that the ends do not match. This will show such casesw and allow you to fix them.

Duplicate Tagnames

If tagnames for objects that are intended to produce objects and instances duplicated then it will not be possible to generate unique RealTags for them. This will quickly find the obvious case of having the same tag more than one on a diagram.

In addition, >Model >Highlight Duplicate Tagnames shows a red line to all objects with the same tagname as the one under the mouse. Only objects whose class creates instances are included.

Classes in their Parents

This will find structural errors such as having a Unit contain a Unit

Duplicate Tag in Parent

This will find cases where a tagname exists at a higher level in the hierarchy, wich may also prevent RealTag from being unique

Lost References

Some special objects such as Calculations, SetStates and Clones contain references to others. If you have deleted the original object then the special object will become invalid. Most times you are prompted before deleting objects that have references to them but sometimes this can happen. Lost references also checks all User Queries that are on diagram

Class Contents

This shows counts of the objects in each class, how many levels down the hierarchy they are and how many there are in each top level (ie the page where you started the review or the first page depending on what you chose) class. It is a useful view on the complexity of a model.

(Another view on complexity is provided as a standard Query)

Note - the counts as if all the links select the master. It does not depend on having run Database Build.