Appendix B  Revision History

Different versions of Reactis are labeled as shown in Figure B.1 and described below.

---

Figure B.1: Version labels begin with a “V” and include three parts: a year, a major release number, and a patch release number. The parts are numbers separated by decimal points. By convention, trailing zeros are omitted.

---

Major Releases.

A new version of Reactis is released at the start of each year and labeled by a “V” followed by the four-digit year, for example V2003. Each label for an intra-year release includes a suffix consisting of a decimal point followed by a major release number; for example V2003.1, V2003.2, etc. will label the releases during 2003 that follow V2003.

Beta Releases.

RSI often makes beta releases available to customers interested in evaluating the newest features of Reactis. Beta releases do not undergo as much testing as major releases do. By convention, beta releases have odd numbered major release numbers. For example, V2003.1, V2003.3, V2003.5, ... denote beta releases.

Patch Releases.

Both stable and beta releases may be “patched.” The label for a patch release is constructed by extending the label for the major release to be patched with a suffix that includes a second decimal point and a patch release number. Some examples clarify the scheme:

V2003.1.2	denotes	the second patch release for V2003.1
V2003.0.1	denotes	the first patch release for V2003

B.1  Patches for Current Stable Release

Patches to Reactis are posted to the Reactive Systems website every two to three weeks. To view a summary recent changes, please view the archives of the Reactis Patches mailing list available at:

B.2  V2007 (31 October 2007)

In addition to numerous quality enhancements, the following features were added since V2006.2

B.2.1  Reactis for C Plugin

Reactis for C Plugin integrates seamlessly with Reactis to offer white-box testing and validation of the C-code portions of models (S-Functions and calls to C from Stateflow). Together Reactis and Reactis for C Plugin automate the generation of test data from, and validation of models constructed with Simulink, Stateflow, and C code.

B.2.2  Newly-Supported Simulink features

1. Support MATLAB R2007a and R2007b models.
2. Support conditional input branch execution in Simulink.
3. Observe the setting "Propagate execution context across subsystem boundary" for enabled and triggered subsystems.
4. Support Simulink Model Reference blocks.
5. Support Simulink Rate Transition blocks.

B.2.3  Other Improvements

1. A Japanese version of Reactis is now available.
2. When a coverage metric is disabled in the Tester launch dialog, Tester no longer tracks coverage for the metric.
3. A new setting allows the user to specify a subfolder where Reactis generated files (.rsi, .rst, .mwi, .rsp) will be stored.
4. All Tester parameters and the currently used RSI file can automatically be saved to a separate RTP file. The stored RSI file can later be extracted via File -> Extract Info File and the Tester parameters can be loaded in the Tester lauch dialog. This allows for easy exact reproduction of a Tester run.
5. Reactis now offers the option to automatically check for updates once per day.
6. Reactis now allows the output of a diagram-based Validator objective to be wired to the input of another objective.
7. A capability has been added to the Reactis License Manager to specify a date format for use in CSV log files.
8. New API functions rsSetParameter and rsGetParameter allow the retrieval and modification of global Reactis parameters (those set in Reactis' settings dialog).
9. Reactis may now run as a regular user without elevated privileges on Windows 2000/XP/Vista.
10. When exporting test suites to .m format for import into Simulink, the test data may now include structures and arrays. The same data types are now supported for export to .mat and .m formats.
11. Reactis now stores Simulator coverage highlighting settings as well as breakpoints in the .rsp file associated with a model, causing them to be retained from one invocation of Reactis to the next.
12. New View -> Expand Tree and View -> Collapse Tree menu items offer a quick way to expand or collapse all nodes of the tree in the hierarchy panel.

B.3  Previous Major Release Dates

V2006.2 (6 November 2006)

V2006 (25 January 2006)

V2005 (18 May 2005)

V2004.2 (17 December 2004)

V2004 (3 March 2004)

V2003.2 (16 October 2003)

V2003 (4 February 2003)

V2002 (3 June 2002)