Breakpoints are used to specify truth tables associated with activities and actions that are to be debugged. Truth tables are defined by a unique name (a unique instance name in the case of a generic) of the activity/action that they describe.
When a truth table is bound to an activity or action, then the assignments are made following the Rational Statemate step semantics. New values are only sensed at the next step. Writing to the same data-item twice flag a write/write racing condition. In the following example,
DATA_2
receives the previous value ofDATA_2
. If the truth table implements a subroutine such as in our previous example, then as soon as an assignment is made it is available to be used for this case.DATA_2
andDATA_3
receives the value of5
when the row is fired regardless of the previous value ofDATA_2
.To illustrate the simulation of an Action truth table, we use the following Activity Chart and the above Truth Table.
Click Edit. This allows you to edit the truth table.
Note: This is an Action truth table so there are no parameters as in the previous example. The column headings for the truth table should match the actual parameter names in the model. The behavior implemented in the following example is the same as in the previous example.