We’re here to help you

Menu

Using the Watch Window

Introduction

In Dezyne sequence diagrams are used to follow an execution path through the models. Sequence diagrams are displayed on verification check failure, behaviour simulation and on execution path analysis.

The Watch Window provides an alternative and more detailed view on such an execution path. For each step in the path it shows the values of all state variables of the models involved.

Graphical Representation

The watch window is displayed under Watch in the Simulation perspective. For any step in the execution path it shows in table format the following data:

  • in a grey bar, a named section for the selected component, for each provided interface, and for each required interface

  • for each section a list of all state variables and their actual values
    image

Each section can be collapsed by pressing the '-' character in front of the section name. The '-' changes into a '+' character, allowing to expand the section again.
image

Navigation

The watch window shows the state in one particular step in the program execution path. You can use the navigation buttons at the top of the watch window to navigate through the path. The button functionality is as follows:

  • step to first: go to the very first step

  • forward step over: go to the next step that points in the same component or interface as the current one

  • forward step into: go to the next step; that step might lead to one of the other models involved in the program execution

  • backward step into: go to the previous step; that step might lead to one of the other models involved in the program execution

  • backward step over: go to the previous step that points in the same component or interface as the current one

  • step to last: go to the very last step

Buttons are grayed out if they do not lead to new steps.

When stepping leads to changes in the value of some variables, these values are displayed in red.

Navigation in the watch window and in the sequence diagram are kept synchronized: a change in either one is reflected in the other. Any change will highlight the place in the model editor where the respective behaviour is specified.

If you have questions that weren’t answered by this Guide,
let our support team help you out.

Enjoy this article? Don't forget to share.
google-site-verification:google656c7703ab521151.html