Completeness Checker

GENESYS's rich framework of embedded static model diagnostics (to complement the dynamic validation provided by the embedded Simulator) consists of a model Completeness Checker and a Design Integrity Checker to implement project- or organization-specific rules. The specific rules are contained within a script and are modifiable for your individual projects.

 

 

The Select Script command (available from the Project Properties page) 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 you 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:

 

• Level 1: Fundamental attributes and relationships
• Level 2: Intermediate checks
• Level 3: Detailed checks

 

The levels are inclusive with each level including all checks defined at lower levels.

 

To perform no consistency checks (this setting is recommended only for those projects that do not wish to leverage any automated support in ensuring project and model completeness by bypassing all rules), simply delete the script from the property sheet by selecting the Clear Script  button next to the Completeness Checker field. 

 

NOTE:

The other component of the diagnostic framework - the Design Integrity Checker - is specified by a Project Administrator on the project property sheet.

 

NOTE:

What permissions are required to select the desired Completeness Checker? To specify the Completeness Checker for a project, your account must have full permissions for that project.