Perform Completeness Checks

The Perform Completeness Checks command evaluates the completeness rules for the specified elements and updates the corresponding "updated" timestamp to reflect the last time the element was checked. Note that only the completeness checks are updated, not the consistency or custom checks (see the Perform All Diagnostics command for more information). This command can be applied at many different levels enabling fine-grained control.

For anything greater than a collection of elements, you will be prompted before the checks are run.

Checking at the Element Level

To perform completeness checks for one or more elements, select the desired elements from the element list in the project explorer. Right-click to access the pop-up menu and select the Perform Completeness Checks command from the Manage submenu.

Checking at the Folder Level

To perform completeness checks for all elements in a folder, select the desired folder from the project pane in the project explorer. Right-click to access the pop-up menu and select the Perform Completeness Checks command from the Manage submenu.

Checking at the folder level will check all elements included in the folder and all subfolders.

Checking at the Package Level

To perform completeness checks for all elements in a package, select the desired package from the project pane in the project explorer. Right-click to access the pop-up menu and select the Perform Completeness Checks command from the Manage submenu.

Checking at the package level will check all elements included in the package and all subpackages.

Checking at the Project Level

To perform completeness checks for all elements in a project, you may use the project explorer or the administrative tools. From the project explorer, select the Perform Completeness Checks command from the Manage submenu on the Project menu. From the administrative tools, select the project in the projects pane and select the Perform Completeness Checks command from the Manage submenu on the Project menu.

Tips and Tricks The completeness checks are designed to run in real-time as the model evolves. There are multiple optimizations in place to make this as streamlined and efficient as possible. In addition, the collection of completeness errors is always updated before it is displayed. The recommended strategy is to enable completeness checks to update automatically when an element is modified (this is set in the Model Assistant). Beyond this, it is appropriate to run the completeness checks after a CORE database import or before a major design review. In these circumstances, it may or may not make sense to perform all diagnostics.