July 23, 2009
Dear Reactis User:
We are pleased to announce the availability of Reactis V2009.2. The new version includes a host of new features and enhancements since the previous major release in January 2009.
Multi-Block MC/DC enables the aggregation of multiple Simulink Logical Operator blocks into a single unit for the purposes of Decision, Condition, and MC/DC coverage tracking. For example, consider the following model fragment:
Under the traditional definition of MC/DC coverage in Simulink, this fragment would include three separate decisions:
each with its own conditions and MC/DC targets. When Multi-Block MC/DC is enabled, these three operators are combined into a single decision:
Multi-Block MC/DC may be enabled or disabled from the General tab of the Reactis Settings Dialog. When disabled the traditional definition of MC/DC for Simulink is used (one decision per Logical Operator block).
Hovering over a Logical Operator block will show arrows indicating the group that the block belongs to. If no arrows appear then the block is not part of any group.
Clicking on a signal line in Reactis now highlights the signal in yellow. This feature makes it easy to trace a signal back to the point where it was generated and forwards to the point where it is consumed (used by a block to compute a new value). The highlighting flows through (backwards and forwards) the following blocks that do not modify a signal value: Inport, Outport, Subsystem, From, Goto, DataStoreWrite, DataStoreRead. Highlighting can be removed by clicking in open space.
After clicking the "up" arrow (or pressing F2) to display the parent of the currently displayed subsystem, Reactis now highlights the subsystem that was previously visible. This can be helpful when navigating large models.
A new tab lists all Validator objectives (assertions, user-defined targets, and virtual sources) that have been added to a model. For each objective, the listing provides the objective's status (disabled, enabled, covered, not covered, violated, ok), name, and location in the model. For any objective, you may double-click on the objective in the list to display it in the main panel or right-click to edit the objective. Also, the list can be used to revive "orphaned" objectives (those that are invisible because the name of the system in which they reside has changed).
Reactis now supports the following:
foo(&(a[3]))
and foo(&b.x)
are now supported
if foo is an external C function called from Stateflow.
Simulink.Parameter
object is used as a configuration
variable, the value of the objects’ “DataType” property
is shown in the DataType column of Reactis’ configuration variable list.
Previously, such configuration variables did show up as type “double”.You may download the patches or full installers from the Reactis User Pages.
Best Regards,
The Reactis Team