Description
For information about IBM Rational Statemate see the Rational
Statemate Support overview web page.
System requirements
For information about the hardware and
software requirements for Rational Statemate, see the Statemate Installation Guide in the IBM
Rational Information Center
At the time of writing, the third
party products tested with <productname> n.n are:
- <third
party product> or reference to documentation including this information
- <third party product>
Compatible products
- Adobe Acrobat Reader 6.0 or newer
- CANoe V3.0
- ClearCase V3.1.1
- Continuous 4.5
- DOORS 8.1, 9.1, 9.2 (Windows Systems)
- dSPACE (models 1102 & 1103)
- dSPACE ControlDesk
1.2 P2
- FlexNet v 11.5.0.0
- FrameMaker 7.0
- PVCS Version Manager v6.7.00 (Build 894)
- QNX V6.3.2
- VxWorks: 5.4 (Tornado 2.0)
- Word 2000/2003
- GNAT ADA version 2.8.1 (Solaris)
Installation Instructions
For information on installing, see the
Statemate Administrator’s Guide and Statemate Installation
Guide, found on the Rational
Information Center
Download of electronic images
For
download information, please view the Rational Statemate
4.6.0.2 Download page.
The
installation packages are available for download at IBM Fix Central:
Select these filters:
- Product Group: Rational
- Product: IBM Rational Statemate
- Installed version: 4.6
Fixed Defects
in this release
For information about the APARs
fixed in version 4.6.0.1 see the Fix List for
Rational Statemate 4.6 page :
What's new in version 4.6.0.2
- Plugin Management enhancement
- The tool was enhanced to
support environment variable setting for defining additional plugin directory:
SET STM_PLUGINS_DIR=<plugin directory>
Statemate will search both the <STM_ROOT>\plugin
and the directory pointed by STM_PLUGINS_DIR (if set) for plugin txt files.
- Doors Enhancement
- GUI Enhancement of the Statemate DOORS
Bridge
- A new selection button was added to the DOORS
interface profile editor, to control deletion of obsolete chart shadows
from the DOORS module. The possible options are:
1. None: don’t delete any chart shadows from DOORS
2. Explicitly confirm: popup a dialog to confirm deletion for
each chart shadow that does not exist in the Statemate Workarea. The dialog options are Yes/Yes to
All/No/No to All/Abort.
3. Detached from scope: delete from DOORS the chart shadows which
they, or their DOORS ancestors,
are no longer connected to the
model tree in the Statemate workarea.Workarea
Management – hidden for this version
- MicroC Enhancements
- A fix was implemented in the MicroC Code-Generator to correctly handle AND-State
exiting reactions.
This change can be avoided by environment variable setting:
SET STM_AVOID_AND_ST_CHECK=ON
- Statemate AUTOSAR Generator
(SAG) Enhancements
- Enhance Support of Client
Server Interface
- The SAG I/O Window contains a new tab called
“Client/Server”, in which the user may define Provided/Required ports with
their corresponding Client-Server Interfaces and their contained
Operations with their attributes.
- The user may select an externally defined
Client-Server Interface from a predefined list defined in a
configuration file. The file name is controlled by a new MicroC Code Generator preference "SAG
Configuration File".
- SAG generates an appropriate code, including
the API call to invoke an Operation on the Client side, and the
Operation implementation on the Server side. In addition, SAG generates
the corresponding Ports and Interfaces definitions in the ARXML file, as
well as the Synchronous Server Call Points for the accessing Runnable Entity on the Client side and a Runnable Entity with a referencing Operation Invoked
Event on the server side.
- Dataport Enhancements
- New Dataport
APIs
- A new set of API functions
was added to the Dataport library, to support
relations in use-case diagrams.
These functions are similar to the corresponding basic a-flow-line (ba) queries:
- stm_list stm_r_br_defined_in_ch(stm_list in_list, int *status)
Retrieve ids of all relations defined in the input list charts
- stm_relation_type stm_r_br_type(stm_id br_id, int *status)
Retrieve the type of a relation
- stm_id stm_r_br_chart(stm_id br_id, int *status)
Retrieve the chart id in which a relation is defined
- stm_br_all_ptr stm_r_br_all(stm_id br_id,int *status)
Retrieve the stm_br_all data structure
populated with the relation's data
- stm_br_text_ptr stm_r_br_text(stm_id br_id,int *status)
Retrieve the stm_br_text data
structure populated with the relation's data
- stm_br_graphic_ptr stm_r_br_graphic(stm_id br_id, int *status)
Retrieve the stm_br_graphic data
structure populated with the relation's data
- stm_list stm_r_br_enter_uc(stm_list in_list,int
*status)
Retrieve ids of all relations entering the use-cases in the
input list
- stm_list stm_r_br_enter_actor(stm_list in_list,int
*status)
Retrieve ids of all relations entering the actors in the input
list
- stm_list stm_r_br_exit_from_uc(stm_list in_list,int *status)
Retrieve ids of all relations exiting the use-cases in the input
list
- stm_list stm_r_br_exit_from_actor(stm_list in_list,int
*status)
Retrieve ids of all relations exiting the actors in the input
list
- stm_list stm_r_oactor_of_actor(stm_list in_list,int
*status)
Retrieve ids of all occurrences of actors in the input list
- stm_list stm_r_ouc_of_uc(stm_list in_list,int
*status)
Retrieve ids of all occurrences of use-cases in the input list
- stm_id stm_r_oactor(stm_id oa_id,int *status)
Retrieve id of the actor that corresponds to the actor
occurrence
- stm_id stm_r_ouc(stm_id oa_id,int *status)
Retrieve id of the use-case that corresponds to the use-case
occurrence
Feature 1 – hidden for this version
- Feature
2 – hidden for this version
- Workflow
Enhancements
IBM Rational Software Support
For support information, please visit the Rational Support
overview site.
You will find a one-sheet reference guide about how to best contact support in
your geography.