Design a Trace Table
Last updated
Last updated
To create a Trace Table, click Add in the trace table view. For an existing trace table, select the table and click Edit in the detail view.
The Trace Table Designer is displayed.
Use the buttons Add Column and Remove Column to add and remove columns. Columns are added and removed from the right.
Each column is of a designated Document Object Type. Furthermore, use the plus and minus buttons to add the attributes to be displayed for the Document Object Type. In the output view, each attribute is displayed in a separate column.
To run the Trace Table, you need to save it first. If the Trace Table has not been saved before, you will be prompted to add a (unique) name for the trace table. Click on the Save button then click Run. This will populate the output view with the column definitions. The sort order is based on the IDs in the left most column (the input set).
The input set specifies the Document Objects that make up the “root” of the Trace Table. These objects are used to populate the trace table’s left most column in ascending ID order. There are three different Trace table input set types:
From Database – all most current document objects of the selected type in the main project
Query – the Document Objects that are resulting from the selected query.
Customized – a hand-picked set of Document Object among the most current document objects of the selected type in the main project.
When editing a trace table, tick the checkbox Upward traces to define a Trace Table showing traces in the upward direction. Remember that Aligned Elements traces are unidirectional, pointing from a source to a target; using the upward trace table enables depiction in the reverse direction.
Tick the checkbox Advanced Mode to activate a multi-branch Trace Table.
When activating this mode, all columns to the right of the second column receive an additional number selection field for specifying the parent column. In the example above, the third column (the Use Case column) specifies the first column (the Requirement column) as the parent column.
In the output view, the second column shows specification tracing from the requirements in the first column, and the third column shows use cases tracing from requirements in the first column.
This can be particularly useful when compiling trace tables for Risk Items such as for Failuremodes or PHA which involves several Document Object Types.
Note! All Risk Factors (Severity, Probability, etc.) and Risk Reduction Factors (Probability Reduction, Severity Reduction, etc.) must be present in the table in order for RPN, NRPN, Thresholds, etc. to be correctly calculated.
Furthermore, the Advanced Mode also permits the use of Queries to populate the columns in order to restrict the search set of the Trace Table.
Use the button Delete in the detail view to delete the Trace Table.
