Trace Tables

To import a Trace table definition, download and unzip the extension file, go to Main Menu -> Traces -> Import and select the unzipped xml extension file. The Trace Table Designer will open with the imported Trace Table definition. To run the trace table, click Refresh. Note! You have to define the input set (all Document Objects  of the particular root type in the current / master database are used by default). Note that you have to explicitly save and name Trace Table definition to use it again. The Trace Table is saved under its root type.

Issue analysis on Test Cases

This Trace Table shows the traces from Executed Test Cases to Issues. For the best effect, use the Failed Test Case Query as input set to single out Issues from failed Test Cases.

Impact analysis of failed Test Cases

This upward (or reverse) Trace Table starts with Executed Test Cases and traces upwards to Test Cases, Specifications, and finally Requirements. To display the impact of failed test cases, use the Failed Test Case Query as an input set.

Failuremodes, Hazards and Mitigations

This is a typical Risk Trace Table displaying Failuremodes, with traces to Hazards including effects, causes, probability, severity, and visibility. Furthermore, the calculated Risk Priority Number, tracing mitigations with their risk reductions and risk type including the updated Risk Priority Number for each mitigation are also displayed.

Reqs to Specs to Tests to Test Results

This Trace Table displays the traces from Requirements to Specifications on to Test Cases and finally their subsequent Test Results. A regular end-to-end trace table.