Reactive Blocks includes a built-in automatic verification tool that reveals mistakes and design flaws, and provides possible actions to fix them. To start the analyzing, select Analyze from the context menu.
An example of an analysis result is depicted in the following figure.
The result is shown in the Analysis view (1). If the analysis wondow is closed, to open it you may re-open the block or right-click the block and select Analyse from the context menu. To re-analyse the system, click refresh button in the upper right corner (5). There are two kinds of issue:
Clicking each error (2), warning or info will show an explanation on the problem (3) and some possible actions, if any, that you can take to fix it (4).
The analysis internally runs in two steps, an initial syntactical inspection and a subsequent deeper analysis. Some syntactical errors prevent the deep analysis to run. Therefore, it may happen that fixing an error reveals other issues, once you analyze again. The opposite, fixing an issue also removes other issues, is also possible.
Reactive Blocks generates executable code automatically from building blocks. In order to ensure correct implementation, it is important that all building blocks are consistent.
In the following we summarized what types of errors and warnings that are detected by the analyzer. For more information, just follow the links.
|The activity diagram contains an inconsistent construction.|
|Contract - related|
|Issues related to block contract.|