CORE's rich framework of embedded static model diagnostics (to complement the dynamic validation provided by COREsim) consists of a model completeness checker, a model consistency checker, and a customer checker to implement project- or organization-specific rules. The Select Completeness Checker command (available from the Project menu on the Administrative Tools) allows the project to specify what level of completeness checks are currently desired.
Not all rules are valid on day one of a project. As the design matures, the completeness checks to identify key attributes and relationships which have yet to be specified should become more sophisticated and robust. With this in mind, for a project can specify one of four levels of completeness checks – from none to rich – tuning to the specific needs and stage in the project life cycle:
The levels are inclusive with each level including all checks defined at lower levels.
After selecting a completeness checker, you are prompted to either:
![]() |
The other components of the diagnostic framework - the consistency checks and the custom checks - are specified by a project administrator via the project property sheet. |
![]() |
What permissions are required to select the desired completeness checker? To specify the completeness checker for a project, your account must have administrator permission for that project. |