Products & Services Solutions Academia Support User Community Company

Learn more about Simulink Verification and Validation   

Using the Verification Manager

What Is the Verification Manager?

The Verification Manager is a graphical interface that appears in the Signal Builder dialog box. The tool allows you to manage from a central location all the Model Verification blocks in your model. The sections that follow describe how to access the Verification Manager for the purpose of enabling or disabling Model Verification blocks in a Simulink model.

Opening the Verification Manager

In this topic you create a Simulink model that you use to examine the Verification Manager in the following steps:

  1. Create the following example model in the Simulink software.

    Typically, a Signal Builder block provides test signals for an entire model from one location. The example model contains a Signal Builder block feeding five test signals to Model Verification blocks. Signals 1 through 4 are sent directly to Check Static Upper Bound Model Verification blocks. The fifth signal is sent to a subsystem that contains a Check Static Upper Bound verification block.

    Each Check Static Upper Bound verification block is set to assert for an upper bound of 1 (property Upper bound = 1). Blocks 1, 2, 3, and 5 appear crossed out because they are disabled (property Enable assert is cleared). Block 4 is enabled (property Enable assert is checked).

  2. Double-click the Signal Builder block in the preceding model to open its Signal Builder dialog box.

    The Signal Builder dialog box displays tabbed pages for three groups of signal values. Each group contains independent values for all five signals. However, only a subset of the signals is displayed for each group. For example, group1 displays signals 1 and 2. For more information on the Signal Builder block, see Working with Signal Groups in the Simulink documentation.

  3. In the Signal Builder dialog toolbar, select the Show Verification Settings tool .

    The Verification block settings pane and the Requirements pane appear as shown.

    By default, the Verification block settings pane lists all Model Verification blocks for the model, grouped by subsystem. The Requirements pane lists the requirements document links for the current signal group. See Managing Verification Requirements for details on adding requirement document links in the Signal Builder dialog box. For now, delete the Requirements pane in the next step.

  4. Just above the Verification block settings pane, select to close the Requirements pane.

    The example Verification block settings pane displays five Model Verification blocks. Four are in the top level of the model, and one is in a subsystem.

  5. Select the List Enabled Verifications tool in the Verification block settings toolbar.

    The Verification block settings pane now shows only the enabled Model Verification blocks for the current group, as shown.

  6. Select the Show Verification Block Hierarchy tool to list all Model Verification blocks for the current group again.

Enabling and Disabling Model Verification Blocks with the Verification Manager

In this section you use the Verification Manager to selectively enable and disable Model Verification blocks in group tests. In Opening the Verification Manager, you open the Verification Manager in the Signal Builder, as shown.

The Verification block settings pane in the preceding example lists the Model Verification blocks in the model. Each verification block has a preceding status node that indicates whether its assertion is enabled or disabled and whether that setting applies universally or to the active group. The preceding status node can be one of the following.

Node

Status

Verification block is disabled for this group. Click to enable for current group.

Verification block is enabled for the current group. Click to disable for current group.

Verification block is enabled for all test groups.

Use the Verification Manager to enable or disable model verification blocks in the test_signals model you created in Opening the Verification Manager, as follows:

  1. In the Verification Manager, click the empty check box next to the Check Static Upper Bound 2 node to enable it for the current group (group1).

    Enabling a disabled block in the Verification block settings pane leads to the following change in block appearance in the model.

    Because it is enabled in the current group, the Check Static Upper Bound 2 block gains an Override label and loses its cross-out. The meaning behind the change in appearance becomes clearer when another group is selected.

  2. In the Signal Builder dialog box, select the group2 tab and click the empty check box next to the Check Static Upper Bound 3 block to enable it for the current group (group2).

    The Check Static Upper Bound 3 block loses its cross to indicate that it is enabled for the current group. However, Check Static Upper Bound 2 gains a cross because it is enabled in another group, but not this one.

The change in appearance of the Check Static Upper Bound blocks in the preceding steps is exemplary of the change in appearance of every other Model Verification block except the Assertion block. The change in appearance of the Assertion block is summarized in the following table:

Assertion Block

Description

Enabled for all groups

Disabled in current group

Enabled in current group

Using Enabling and Disabling Tools in the Verification Manager

If you have many verification blocks, it is tedious to enable and disable blocks individually. For this reason, the Verification Manager lets you enable and disable blocks through selections from a context menu. These selections vary with the node as follows:

Node

Context Menu Selections

  • Contents enable for all groups

  • Contents enable by group

  • Contents group enable

  • Contents group disable

  • Block enable by group

  • Block enable for all groups

  • Block group enable

  • Block enable for all groups

  • Block group disable

As an example, assume that the following groups are defined in the Verification Manager for a model with five Model Verification blocks.

  1. Right-click the test_signals node and select Contents enable for all groups.

    Applying the Contents enable for all groups selection to the model node enables all contained Model Verification blocks, for all test groups, in all contained subsystems.

  2. Right-click test_signals and select Contents enable by group.

    Applying the Contents enable by group selection to the model node restores the previous individually enabled/disabled settings for each block in each group.

  3. Right-click test_signals and select Contents group enable.

    Applying Contents group enable to the test_signals model node in group1 individually enables all contained blocks for group1, but leaves the other groups untouched.

  4. Right-click test_signals and select Contents group disable.

    Applying Contents group disable to the test_signals model node in group1 individually disables all contained blocks for group1, but leaves the other groups untouched.

  5. Right-click Check Static Upper Bound 1 and select Block enable for all groups.

    Applying Block enable for all groups to the individual group1 block node for Check Static Upper Bound 1 in group1 enables this block for all groups.

  6. Right-click Check Static Upper Bound 1 and select Block enable by group.

    Applying Block enable by group to the individual group1 block node for Check Static Upper Bound 1 in group1 restores the previous individually enabled/disabled state to this block for all groups. This lets you enable or disable this node individually for each group.

  7. Right-click Check Static Upper Bound 1 and select Block group enable.

    Applying Block group enable to the individual group1 block node for Check Static Upper Bound 1 in group1 enables this block for this group only. This is equivalent to selecting the empty check box in group1 for this node.

  8. Right-click Check Static Upper Bound 1 and select Block group disable.

    Applying Block group disable to the individual block node for Check Static Upper Bound 1 in group1 disables this block for this group only. This is equivalent to clearing the check box for this node.

  


Related Products & Applications

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.

 © 1984-2009- The MathWorks, Inc.    -   Site Help   -   Patents   -   Trademarks   -   Privacy Policy   -   Preventing Piracy   -   RSS