TYX
Home

Company Profile

Products

Support

News

Partners

PUG

Guestbook

Release Notes

Application Notes

Papers and Info

Problem Report

Y2K

FAQ


Release Notes

TYX TRD
Version 3.0.5
24 February 2006

1. Overview

This is a maintenance release of the TYX TRD System that corrects a few problems.

2. Detailed Description

2.1. Critical items

2.1.1. Security setting for macros in third-party applications

Microsoft Excel and Visio support the configuration of security features that impacts the ability to execute macros. The TRD System uses such macros to implement integration with Word, Excel and Visio. Consequently, these products have to be configured properly, to accept the execution of macros. Detailed instructions are provided in the Installation Guide.

2.1.2. Operating system and third-party software compatibility

Operating systems: this version was tested with Windows 2000 SP4 and Windows XP.

Microsoft Office: this version was tested with Visio 2003, Word XP, Word 2003, Excel XP and Excel 2003. The product is not compatible with earlier versions of Visio, Word and Excel.

Microsoft Visual SourceSafe: this version was tested with Visual SourceSafe 6.0a and Visual SourceSafe 6.0c.

2.2. Known Limitations

2.2.1. Duplicate Failure Mode Temporarily Created in Fault Editor

Adding Failure Modes to Component Types that have already been assigned to Components causes a warning message to be displayed, informing the user that these Failure Modes will not be automatically assigned to the Components of that Component Type. This message is correct. However, during the display of the message, a duplicate of the newly added Failure Mode appears in the grid. The duplicate disappears from the grid once the warning message is closed. It does not get saved in the TRD Project. This peculiarity does not affect the normal operation of the program.

2.2.2. Automatic Test Renumbering Feature Not Documented

The automatic test renumbering when moving Tests occurs only when the Performance Tests numbers are in ascending order. This behavior is by design. It is not documented in the Help System.

2.2.3. Horizontal limitation of the Test Strategy layout

For extremely large diagnostic branches, the drawing area expands horizontally causing an upper limitation of the zoom level. The upper zoom level starts to decrease below 100% for a test strategy layout having more than 187 diagnostic tests defined horizontally. The upper zoom level of 76% is reached for a number of 258 diagnostic tests defined horizontally. Below this zoom level the layout becomes hard to read, that is why the number of diagnostic tests defined horizontally for one performance test should not exceed 258.

2.2.4. Restrictions in deleting, moving and duplicating Test Blocks on multiple page layout

Because of the complexity of the Test Strategy layout and because the content of Test Blocks can be drawn on multiple pages, deleting, moving and duplicating entire Test Block branches (i.e. selected Test Blocks together with all the Tests and Replace actions that belong to it) is not allowed anymore. The same functionality can be obtained by deleting, moving or duplicating each Performance Test branch belonging to that Test Block.

2.3. Problem Reports

2.3.1. The release fixes several problems identified for release version 3.0.4:

  • Display of shapes connecting adjacent pages outside the drawing area
    Problem has been corrected, all shapes are drawn inside the drawing area. To enable this correction in existing TRD projects the Test Strategy layout must be re-drawn.
  • The shapes connecting adjacent pages were enabled for deleting, resizing, moving and rotating
    Problem has been corrected, these shapes are blocked for the above mentioned operations. To enable this correction in existing TRD projects, the Test Strategy layout must be re-drawn.
  • Text inside the decision blocks in generated flowcharts exceeds the size of the decision block
    Problem has been corrected.

2.3.2. The release provides improved speed for the following operations:

  • Deletion of Components and Faults in Fault Editor
  • Loading of table based editors
  • Propagating changes from the Data Explorer to the Fault table

 




| Home | Company Profile | Products | Support | News | Partners | User Groups | Guestbook |