Telelogic Statemate

Statemate 4.2 is now available. This release is focused on improvements to user workflow with interface enhancements, including additional modeling, analysis, performance and code generation improvements.

So let’s explore this new release, starting with the user workflow with interface enhancements:

  • Further Support for Large Models – Statemate Global Definition Sets (GDS) can often contain large amounts of data especially when working with large complex systems. In order to improve overall performance, a new option has being introduced to allow only “used elements” within the GDS to be loaded into the work area.
  • Enhanced Element Property Dialog – The property dialog has been redesigned to allow for enhanced ease-of-use. When the dialog window is resized, the fields within the dialog are also resized, making it easier to work within the window. The subroutine properties dialog user interface has also being changed to make it easier to use. Now when using the implementation tab, you can easily select the “selected implementation” simply by pushing the new select implementation button.
  • Optimized Workflow With New Default Value Field - Within the definition tab, there is now a new field called “default value”. This allows all textual elements within Statemate to have a default value. This benefits users by eliminating the need to set up defaults values using Test benches, optimizing the engineer’s workflow.
  • Improvements to Internal Editor With ‘Beautify” Support – The new internal text editor introduced to Statemate recently now has a new feature called “beautify”. This feature automatically formats and indents text for you, making documents easy to read.

Now let’s review some of the modeling improvements:

  • Flowcharts Now Supported as Subroutine Implementation – Flowcharts can now be defined as a subroutine implementation to give you even more choices in describing behavioral reuse within the model.
  • Long Description and Attributes for Transitions – To allow more readability within Statecharts, transitions can now include their own long descriptions and attributes.
  •  Enhanced Support for Default Values – As mentioned above, Statemate 4.2 now supports default value definitions within the properties for textual elements. Several new operators have been added to allow resetting of a single element or the entire scope back to their default value during simulation of the model.

    Statemate includes powerful Simulation capabilities. This new Statemate release builds on this foundation with several new exciting features:
  • New Quick Simulation Monitor – Users can now quickly build a simulation monitor for analysis of all Statemate textual elements within the scope of your simulation at the click of the mouse, a new feature that is surely going to be appreciated by many of our longtime Statemate users.
  • Improvements to Execution Trace – Building on a feature we introduced recently, simulation execution traces can now record truth table lines that were visited.

Finally, rounding off this release, we made several improvements to the code generation capabilities of Statemate, including providing compete support for MISRA C compliance.

Additional Resources