Statemate version 4.6.1.10 Release Notes

IBM Corporation
26 Nov, 2014

 

 

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

It is divided into the following sections:


Description

For information about IBM Rational Statemate see the Rational Statemate Support overview web page.

 

System requirements

To run Statemate 4.6.1.10 you need:

Operating System

Required Software

Supported Compilers

Hardware

Solaris 5.10

OpenWindows

Sun Studio 12 Update 1
GNAT Ada gcc 2.8.1

sun4u sparc SUNW,A70
1 GB RAM
Approximately 500Mb free
disk space

Windows XP SP3
Windows 7

MKS XServer 8.6
MKS Platform
Components 9.4

Microsoft Visual C++ 2008, 2010

Intel® Core™2CPU, 2 GHz
Minimum 1 GB, recommended 2 GB RAM
Approximately 600Mb free
disk space

 

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 9.3, 9.4, 9.5 (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 2003
  • GNAT ADA version 2.8.1 (Solaris)

 

Installing Statemate 4.6.1.10

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.

Download of electronic images

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 download information, please view the Rational Statemate 4.6.1.10 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.1

 

Fixed Defects in this release

For information about the APARs fixed in version 4.6.1.10 see the Fix List for Rational Statemate 4.6 page.

What's new in version 4.6.1.10

  • General Enhancements
    • Multi Value Attribute capability.

Statemate was enhanced to support Multi Value Attribute. This capability allows defining attributes in the Attribute Definition File as allowed to have multiple occurrences for a single element, with different values.
The format of attribute record in the Attribute Definition File includes now the multiplicity field:

#attr description:

    {

    #name:<Attribute name>

    #type:<Attribute type>

    #multiplicity: <yes/no>

    #value:<Default value>

    #legal values:<For enumerated type>

    #enforced: <yes/no>

    }

When multiplicity is set to ‘yes’, this attribute may appear multiple times for a single element.

Check-model will not report "Elements with non-unique attribute definitions" for multi-value attributes.

Multi-value attributes will be exported to DOORS as a concatenated string, when values are separated by semi-colons.

The 'Insert' button in the Attributes matrix was enhanced to support a Copy option for multi-value attribute. When the selected row is of a multi-value attribute, pressing 'Insert' will open a sub-menu,
New or Copy, and the new inserted attribute line will accordingly be created as new (empty) or copy of the selected attribute.

    • A new preference was added in the Databank Browser section "Preserve Attributes graphic data in chart-file".
      When it is set to 'Yes', it will works as before (default setting).
      When setting it to 'No', the 'attribute resources' section will not be included in the chart file.

 

  • Dataport/Dataimport Enhancements
    • New Dataport function was added, to retrieve description of use-case:
      char * stm_r_uc_description(stm_id st_id, int *status);
    • Three new Dataport functions were added, to retrieve occurrence Id's of Activities, Actors and Use-cases by name:
      stm_list stm_r_oac_name_of_oac(char *pattern, int *status);
      stm_list stm_r_oactor_name_of_oactor(char *pattern, int *status);
      stm_list srm_r_ouc_name_of_ouc(char *pattern, int *status);
    • New Dataport function was added, to allow saving a list of elements in the Workarea:
      int stm_list_save(char* list_name, char *desc, stm_list lst, stm_boolean force, int *status);
    • Two new Dataport functions were added, to retrieve note of relation, or relation by it's note:
      stm_list stm_r_note_of_relation(stm_list in_list, int *status);
      stm_list stm_r_relation_of_note(stm_list in_list, int *status);
    • New Dataport function was added, to retrieve Subroutines implemented by Procedural Flowchart:
      stm_list stm_r_sb_imp_procedural_fch_sb(stm_list in_list, int *status);
    • New Dataport function was added, to return Note of a Use-case diagram relation:
      char * stm_r_br_note_body(stm_id br_id, int *status);
    • New Dataimport function was added, to allow modification of Action:
      int stmModifyAction(STMContextHandle *handle, char* chart_name, char* action_name,
                   char* definition DEFAULT_VAL(=NULL),
                   char* short_description DEFAULT_VAL(=NULL),
                   char* long_description DEFAULT_VAL(=NULL),
                   int modify_mask DEFAULT_VAL(=0xFFFF));
    • New Dataimport functions were added, to support definition of enumerated value array indices:
      int stmCreateFieldEx(STMContextHandle *handle, char* chart_name, char* UserType_name,
                   char* field_name, stm_dt_structure_type structure,
                   stm_dt_data_type data_type,
                   char* array_lindex DEFAULT_VAL(=NULL),
                   char* array_rindex DEFAULT_VAL(=NULL),
                   char* array_of_type DEFAULT_VAL(=NULL),
                   char* user_type_name DEFAULT_VAL(=NULL),
                   char* short_description DEFAULT_VAL(=NULL),
                   char* long_description DEFAULT_VAL(=NULL));
      int stmCreateConditionEx(STMContextHandle *handle, char* chart_name,
                   char* condition_name, stm_co_structure_type structure,
                   stm_co_definition_type usage,
                   char* array_lindex DEFAULT_VAL(=NULL),
                   char* array_rindex DEFAULT_VAL(=NULL),
                   char* array_of_type DEFAULT_VAL(=NULL),
                   char* definition DEFAULT_VAL(=NULL),
                   char* short_description DEFAULT_VAL(=NULL),
                   char* long_description DEFAULT_VAL(=NULL));
      int stmCreateDataItemEx(STMContextHandle *handle, char* chart_name,
                   char* data_item_name,
                   stm_di_structure_type structure, stm_di_data_type data_type,
                   stm_di_definition_type usage,
                   char* array_lindex DEFAULT_VAL(=NULL),
                   char* array_rindex DEFAULT_VAL(=NULL),
                   char* array_of_type DEFAULT_VAL(=NULL),
                   char* definition DEFAULT_VAL(=NULL),
                   char* user_type_name DEFAULT_VAL(=NULL),
                   char* short_description DEFAULT_VAL(=NULL),
                   char* long_description DEFAULT_VAL(=NULL));
      int stmCreateUserTypeEx(STMContextHandle *handle, char* chart_name,
                   char* UserType_name,stm_dt_structure_type structure,
                   stm_dt_data_type data_type,
                   char* array_lindex DEFAULT_VAL(=NULL),
                   char* array_rindex DEFAULT_VAL(=NULL),
                   char* array_of_type DEFAULT_VAL(=NULL),
                   char* definition DEFAULT_VAL(=NULL),
                   char* user_type_name DEFAULT_VAL(=NULL),
                   char* short_description DEFAULT_VAL(=NULL),
                   char* long_description DEFAULT_VAL(=NULL));
      int stmCreateEventEx(STMContextHandle *handle, char* chart_name, char* event_name,
                   stm_ev_structure_type structure, stm_ev_definition_type usage,
                   char* array_lindex DEFAULT_VAL(=NULL),
                   char* array_rindex DEFAULT_VAL(=NULL),
                   char* array_of_type DEFAULT_VAL(=NULL),
                   char* definition DEFAULT_VAL(=NULL),
                   char* short_description DEFAULT_VAL(=NULL),
                   char* long_description DEFAULT_VAL(=NULL));
      int stmModifyDataItemUserTypeIndices(STMContextHandle *handle, char* chart_name,
                   char* data_item_name,
                   char* array_lindex DEFAULT_VAL(=NULL),
                   char* array_rindex DEFAULT_VAL(=NULL),
                   char* array_of_type DEFAULT_VAL(=NULL));
      int stmModifyConditionIndices(STMContextHandle *handle, char* chart_name,
                   char* condition_name,
                   char* array_lindex DEFAULT_VAL(=NULL),
                   char* array_rindex DEFAULT_VAL(=NULL),
                   char* array_of_type DEFAULT_VAL(=NULL));
      int stmModifyEventIndices(STMContextHandle *handle, char* chart_name,
                   char* event_name,
                   char* array_lindex DEFAULT_VAL(=NULL),
                   char* array_rindex DEFAULT_VAL(=NULL),
                   char* array_of_type DEFAULT_VAL(=NULL))
      ;
    • New Dataimport function was added, to allow setting the structure of local data items and subroutine parameters:
      int stmModifySubroutine(STMContextHandle *handle, char* chart_name,char* sbr_name,
                   stm_sb_definition_type sbr_type,
                   stm_sb_return_type sbr_ret_type,char* ret_usr_type_name,
                   stm_sb_select_implementation sbr_impl_type,
                   int params_num, stm_sb_param *sbr_params,
                   int globals_num, stm_sb_global *sbr_globals,
                   char* short_description DEFAULT_VAL(=NULL),
                   char* long_description DEFAULT_VAL(=NULL),
                   int modify_mask DEFAULT_VAL(=0xFFFF));
    • New Dataimport function was added, to allow changing the scope of Subroutines:
      int stmSubroutineChangeScope(STMContextHandle *handle,char* chart_name, char* subroutine_name,
                   char* new_chart_name);
    • New Dataimport function was added, to allow setting the data type of local data items and subroutine parameters:
      int stmModifySubroutine(STMContextHandle *handle, char* chart_name,char* sbr_name,
                   stm_sb_definition_type sbr_type,
                   stm_sb_return_type sbr_ret_type,char* ret_usr_type_name,
                   stm_sb_select_implementation sbr_impl_type,
                   int params_num, stm_sb_param *sbr_params,
                   int globals_num, stm_sb_global *sbr_globals,
                   char* short_description DEFAULT_VAL(=NULL),
                   char* long_description DEFAULT_VAL(=NULL),
                   int modify_mask DEFAULT_VAL(=0xFFFF));
    • New Dataimport function was added, to allow deletion of Generic chart parameter:
      int stmDeleteParameter(STMContextHandle *handle, char* chart_name,char* parameter_name);
    • Two new Dataimport functions were added, to create Truth-tables for Activities and Actions:
      int stmAddActionTruthTable(STMContextHandle *handle, char* chart_name, char* action_name,
                   stm_truth_table_rec *tt_rec);
      int stmAddActivityTruthTable(STMContextHandle *handle, char* chart_name, char* activity_name,
                   stm_truth_table_rec *tt_rec);

 


Contacting Support

IBM Rational Software Support Communities

  • Visit the Rational Support Resources site.
  • Visit the IBM Support Portal to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.
  • Visit developerWorks to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community.

Helpful Hints For Obtaining Technical Assistance:

Before you contact IBM Rational Software Support, gather the background information that you need to describe the problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:

  • What software versions were you running when the problem occurred?
  • Do you have logs, traces, or messages that are related to the problem?
  • Can you reproduce the problem? If so, what steps do you take to reproduce it?
  • Is there a workaround for the problem? If so, be prepared to describe the workaround.

If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support.

Follow IBM Rational Client Support on Twitter | Facebook | YouTube | devWorks Blog