Statemate version 4.6 Release Notes

IBM Corporation
01 June, 2009

 

 

© Copyright IBM Corporation 1989, 2009
U.S. Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

This file contains last-minute product information and updates to Statemate 4.6

It is divided into the following sections:

For the latest news and information on Rational Statemate, visit the Web site at http://www.ibm.com/software/rational/support/.

System requirements

To run Statemate 4.6 you need:

  • One of the following operating systems installed on your computer:
    • Sparc Solaris 2.8/2.9/2.10 with the following Windowing systems:
      • CDE
      • OpenWindows: 3
      • Motif
    • Windows XP SP2 with one of the following X-Servers Installed:
      • X-Vision
      • MKS X/Server
  • The system requirements for Windows:

The recommended memory (RAM) for Windows is 256 MB.
When working with large models on Windows platforms, you should allow more memory to enhance tool performance.
When working with models that contain 200 or more charts and 2500 or more dictionary elements (textual elements), allow at least 1 GB of physical memory.

For additional information on system requirements, including recommended configurations, visit the Rational Support Web site at: http://www.ibm.com/software/awdtools/statemate/sysreqs

At the time of writing, the third party products tested with <productname> n.n are:

 

Compatible products

  • Adobe Acrobat Reader 6.0 or newer
  • CANoe V3.0
  • ClearCase V3.1.1
  • Continuous 4.5
  • DOORS 8.1 (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 97/2000
  • GNAT ADA version 2.8.1 (Solaris)

 

Installing Statemate 4.6

Changes in Statemate 4.6 for Windows:

o        The default installation directory for Statemate 4.6 has changed to
C:\IBM\Rational\Statemate

o        The MKS Toolkit (NutCracker) for Statemate 4.6 was upgraded to version 9.2 and its default installation directory is:
C:\Program files\Common Files\IBM\Rational\Shared\MKS Toolkit
If a previous version of MKS Toolkit is installed, the installation of version 9.2 will overwrite it.

o        The installation directory of the Statemate 4.6 Stmlockman service has changed to:
C:\Program files\Common Files\IBM\Rational\Shared\Stmlockman

o        The MKS X/Server delivered with Statemate 4.6 was upgraded to version 8.5 (previous MKS X/Server versions can still be used).

o        The default 'Start' menu link to Statemate 4.6  is:
All Programs->IBM Rational->IBM Rational Statemate 4.6->Statemate 4.6

o        The default 'Start' menu link to Statemate 4.6 Documentation is:
All Programs->IBM Rational->IBM Rational Documentation->IBM Rational Statemate 4.6

o        The Statemate 4.6 desktop icon has changed to comply with the Rational product family icons, and is named "IBM Rational Statemate 4.6".

Before installing, it is recommended that you check in and unlock all configuration items in all workareas.
For more information, see the Statemate Administrator’s Guide and Statemate Installation Guide, found on the CD.


Obtaining a license for Statemate

Statemate uses Telelogic Lifecycle Solutions licensing. - hidden
For more details about obtaining a license, please see “TLS_licensing_guide”. - hidden
The file can be found on the distribution CD, under “license_server_windows_1.3” - hidden
directory for Windows, and under “license_server_1.3” directory for Solaris. – hidden
For details about obtaining a license, please refer to Statemate customer support.


What's new in version 4.6

  • Workflow Enhancements
    • Main Window View
      • The Elements matrixes in the 'Charts' and 'Search' tabs were enhanced to allow the display of Statechart transitions.
        Showing the Transitions is optional.
        In the 'Charts' tab the display of transitions is controlled by a check-box in the 'Elements Matrix' tab of the 'View Filter'.
        In the 'Search' tab, 'Transition' was added to the 'Type' selection list of the 'Graphical' tab.

    • Field Properties form
      • The Element Properties dialog was enhanced, to allow opening of multiple record-field dialogs, and support cut/copy/paste operations between them.
        The "Properties" button in the record dialog which opens the field-properties, was replaced by a menu-button with 3 options:
        'Properties'
        'Properties in a New Window'
        'Properties in Separate Window'
        These options are available from the right side of the ‘Properties’ button, opening a pop-up menu.Default action of this  button is the first menu option - 'Properties'

        To support cut/copy/paste of complete record-field information, the following options were added to the right-click pop-up menu in the record fields matrix:
        Cut/Copy/Paste (String): execute the operation only on the field information included  in the matrix
        Cut/Copy/Paste (Element): execute the operation on all field properties data

    • Panel Update during Rename
      • The tool was enhanced to support update of panel bindings during rename of textual elements. This behavior is controlled by a new Properties preference "Update panel bindings upon element rename", with 3 optional values:
        'Never': Do not update panel bindings during 'Rename'
        'Always': Always update panel bindings during 'Rename'
        'Only unique': Update panel bindings only if the renamed element name is unique
        Default value of the preference is 'Never'

    • Quick Workarea Cleanup
      • A new menu entry was added in the 'Charts' tab : "Edit->Delete all Charts/GDS's", to allow quick deletion of all charts & GDS's from the workarea, while reducing database size to minimum.

    • Preserving Chart version after Import
      • The import operation was enhanced to allow preservation of a locked chart's version when overwriting it with an "imported" chart of the same name.
        The “overwrite” confirmation dialog now offers a check-box to preserve current version, or import the chart as 'New'.

    • Diff/Merge chart
      • The tool was enhanced to support integration with external tool, to do a textual diff/merge between a chart in the Workarea and the latest chart-version found in the Databank.
      • The merge result (chart) will be saved as a new version of the chart in the data-bank
      • A new menu entry was added to the charts/files tab:
        Configuration->Diff/Merge chart with latest version.

      • The external diff/merge tool is defined using a new preference in the preferences ‘General’ section: ‘DiffMerge tool Command Line’.
        • The value of this preference should be a full path to 3-way-DiffMerge tool which will expect to following format:
          <script-name> <input-file-1> <input-file-2> <output-file>

    • Box Name Text Orientation
      • In both Activity-charts and Statecharts graphics editors, a new option was added to the pop-up  menu of box names: "Flip Horizontal/Vertical Name".
        This option will modify the text orientation of selected box names.

    • Router Properties
      • The 'Transparency' field was removed from Routers property form

  • CheckModel Enhancements
    • (C1141) 'else' Transitions with priority
      • New CheckModel test was added to report an error when a prioritized transition is labeled 'else'
    • (C13013) Activities defined as Task in a generic scope
      • New CheckModel test was added to report a 'Design' error for generic activities defined as 'Task'
    • (C5029, C3029, C1029, C18029, C7110) Subroutines that are used incorrectly
      • The default behavior of the CheckModel test for "Subroutines that are used incorrectly" was changed, to report errors when the chart with the erroneous usage is in the profile scope, not only if the definition chart of the Subroutine is explicitly included in the scope.

  • GBA Enhancements
    • The GBA was enhanced to animate the hierarchy of ancestor instances of a current state, in addition to the current 'leaf' states.

  • Dataport / DataImport / Documentor Enhancements
    • New Documentor API
      • New Function : STM_R_SB_GLOBAL_DATA_MODE(IN sb : SUBROUTINE, IN sp: SUBROUTINE_PARAMETER, OUT st: INTEGER): INTEGER;
        New Documentor function was added to support retrieval of Subroutine global parameters mode.

    • New Dataport API
      • stm_exit_graphic_editor
        stm_boolean stm_exit_graphic_editor(stm_id id, int *status)
        A new Dataport API was added which sends a message to an open Statemate-session to close a graphic-editor.

        Function Parameters:
        • id - Element id
        • status - (out parameter) - can return the following:
                    – stm_success
                    – stm_error_in_open_socket_to_statemate

    • New DataImport API
      • stmDeleteBindParameter
        int stmDeleteBindParameter(STMContextHandle *handle, char* chart_name,
                                  char* instance_box_name,char* formal_parameter_name);
        A new DataImport API was added to allow deletion of generic parameter bindings.


  • MicroC Enhancements
    • Generate inline Set/Get functions for each Generic Instance
      • The Statemate MicroC Code generator was enhanced to allow generation of Get/Set function for Inlined Generic's elements separately for each instance using the OSDT.
        With this capability each instance will generated its set of Get/Set functions for the generic's elements.
        To use this new capability a proper definition should be set to the Get/Set API's and to enable them in the OSDT.
        The enhanced API's are:
        * Get Function Declare()
        * Get Function Define()
        * Get Array Element Function Declare()
        * Get Array Element Function Define()
        * Set Function Declare()
        * Set Function Define()
        * Set Array Element Function Declare()
        * Set Array Element Function Define()

        A reference definition is available in the MAILOOP_SC and MAINLOOP_SC_EXT OSI's.
        To update your OSI simply copy the definition from the relevant API and enable it.

        For example, the definition of the API "Set Function Define" in MAINLOOP_SC is:

        ?<begin>$<ResideInInlinedGenericInstance>  ?<==> yes ?<?>@<for>@<InstancesList>@<begin>$<returntype>
        $<nameid>?<begin>$<genChartName>?<!=>?<?>_$<genChartName>?<:>?<end>_CB_$<InstancesList>($<argType> $<argName>)
        {?<begin>$<tstDrvInst>?<!=>?<?>
        $<tstDrvInst>?<:>?<end>
        $<$<InstancesList>CodeBody>}

        @<end>?<:>$<returntype>
        $<nameid>?<begin>$<genChartName>?<!=>?<?>_$<genChartName>?<:>?<end>_CB($<argType> $<argName>?<begin>$<genArgType>?<!=> ?<&&> $<genArgName> ?<!=>?<?>, $<genArgType> $<genArgName>?<:>?<end>)
        {?<begin>$<tstDrvInst>?<!=>?<?>
        $<tstDrvInst>?<:>
        ?<end>$<setElemCode>}

        ?<end>

  • Statemate Autosar Generator (SAG) Enhancements

 

    • Enhance Support of Data Types
      • A single Boolean type will be defined in the XML for all Conditions and another single Boolean type will be defined for all Events.
      • SAG supports automatic linkage to external type for to Data-Elements that answer the following requirements:
        • Have no specific minimum or maximum values.
        • Have the Design Attribute “C Data Type” set to a value.
        • In order to map the value of C Data Type to an AUTOSAR type, it must be written within the body of one of the API’s at the OS Definition Tool->API Definition->AUTOSAR Types  API’s.
      • SAG supports elements of type record and array on Software Component Interface.

 

    • Enhance Support of External Ports and Interfaces
      • The user may use an external Interface to type a Port, by setting an interface reference to the design-attribute External Interface Reference, available for Info-Flows (for S-R Interface) and Subroutines (C-S Interface). In this case, the Interface will not be defined in the XMl, and the port will refer to the provided reference.

 

    • Enhance support of timeouts
      • SAG allows the user to define the Defining Minimum and Maximum values for the CounterTime variable, using the dialog options->Set Timer Configuration.

 

    • Support of Calibration Interfaces
      • SAG supports using AUTOSAR calPrmInterfaces, by choosing the value “CalPrm Access” for the “Data Exchange Behavior” column.

 

    • Support Mode Declaration Groups
      • Mode Declaration Group will be implemented by SAG using an enumerated User Defined Type with Design-Attribute “Mode Declaration Group” set to “yes”, and having a data item of this type flowing on a certain info flow.
      • An input data will be accessed via the RTE API Rte_Mode_...() and output via the API Rte_Switch_...()
      • The XML will include definitions of ModeDeclarationGroup and ModeDeclaration. In addition, it will define ModeSwitchPoint and ModeSwitchComSpec for output data.

    • Support of Data Elements both as Inputs and Outputs
      • SAG will automatically identify Data Elements that are used both as inputs, i.e. on incoming info-flow representing an AUTOSAR Required-Port, and as outputs, i.e. on outgoing info-flow representing an AUTOSAR Provided-Port.
      • Input access of such Data Elements will be implemented regularly, meaning via a Sender-Receiver Interface using the appropriate RTE API’s.
      • Output Access of such Data Elements will be implemented using an operation named Write<DataName>, on a Client-Server Interface typing a dedicated Required-Port.
        All such operations will be gathered into a single Port and a single Interface. The Port’s name may be customized using the OSDT API: Code Style->Type Naming Style->Implicit (Generated) R-Port Name.

 

 

Contacting Support

Please visit our Telelogic support overview site at: http://www.ibm.com/software/rational/support/telelogic/
You will find a one-sheet reference guide about how to best contact support in your geography.

 

Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send written license inquiries to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send written inquiries to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions. Therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Intellectual Property Dept. for Rational Software
IBM Corporation
1 Rogers Street
Cambridge, Massachusetts 02142
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copy and Trademark information at www.ibm.com/legal/copytrade.html.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office

UNIX is a registered trademark of The Open Group in the United States and other countries.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Other company, product or service names may be trademarks or service marks of others.