Une image contenant texte, signe

Description générée automatiquement

Configuring Available Checks

 

Overview

The Model Checker is supplied with a predefined set of available checks, but this is configurable. Checks are organized into Model Check Sets (for example Systems Checks, Model Integrity Checks). Each set of checks is optional and may be enabled / disabled at project or package level. In addition, user-defined checks and check groups may be added and combined with any of the supplied checks. There are various ways to configure the checks presented in the UI and there is a priority order – that is if the higher-level property in use, then the lower level propert(ies) are ignored. The priority order is depicted below with the highest priority at the top:

 

Enabling / Disabling the Supplied Check Groups

The most basic option simply involves setting the following properties on the package / project:

A screenshot of a computer

Description automatically generated

If the checkbox for a Check Set is cleared then that set is not presented in the Model Checker user interface.

Providing an Explicit List Using the Power Pack Property

This property takes precedence over the basic properties described above and may be set at project / package level:

RhapsodyPowerPack.ModelChecker.ModelChecks

This property may be used by regular model-users to decide which Check Groups to show for a particular model / package. See Model Checks JAR Files below.

Providing an Explicit List Using the User Property

This property takes precedence over all the properties described above and may be set at project / package level:

RhapsodyPowerPackExtension.ModelChecker.ModelChecks

This property does not exist by default and must be added. It is intended for profile designers to supply their own set of available predefined checks by defining this property on a project-level stereotype or in a Property File. If this property is in use, then users of the model that desire to change the available checks for a specific package should override this property and not the power pack one above. 

Model Checks JAR Files

Both above ModelChecks properties work in the same way; they are a comma separated list of full paths to Model Check Sets. The supplied Model Check Sets are visible in the Rhapsody Power Pack profile:

A screenshot of a computer program

Description automatically generated

For example to include only the Systems and Model Integrity Check panels, set this property to RhapsodyPowerPack::ModelChecker::SystemChecks,RhapsodyPowerPack::ModelChecker::ModelIntegrityChecks

 

A user-supplied profile would typically include its own Model Check Sets and the Extension Explicit Model Checks property would contain full paths to those sets along with (optionally) any of those supplied by the Power Pack. Note that the order of the comma separated list determines the order of the check tabs presented in the Model Checker user interface.

Obtaining the Full Path

Full paths may be constructed manually or by using the Get Full Path helper.