Release notes

N release (NM5 1.1.1951)

Improved Polarion Adapter

The Polarion adapter is now able to understend the attributes of links between workitems. It is possible to read only relevant links (see example below) and to define custom evaluations based on these attributes, e.g. to create a query which lists all „branchedFrom” workItems together with their origin.

include link if (
	// only consider "verifies" relations 
	valueOf(role) == "verfifies"

The help provides a detailed description of the Polarion link type .

„Suspect” marker for Integrity Adapter is now configurable

Just in case you changed the default name of the suspect marker field in PTC Integrity: By configuration, YT can cope with it.

server ""
port 7001
fields for {
	// Define the field name for suspect links count
	suspect count "Name of customized fieldSuspect Count"

Usability Improvements

Better support when analyzing Query Results.

For YT Queries, it was possible to select an artifact or a link between two artifacts by a simple click in the results table.
This feature now also works for aggregation queries (e.g. count the number of failings tests per requirements).

We added a Reset Button to the YT Configuration Editor

You can now easily reset your unsaved changes in the YT Configuration Editor by a simple button click.

Better guidance if configured YT Configuration file does not exist

In some cases, YT was too eager to guess the users expectations regarding the active YT Configuration. For instance, if a user set the preference holding the active configuration to a non-existing file, YT created this file for the user. This lead to confusions.
Now, YT better observes the users behavior and will never create an empty configuration file „under the hood”.

Preview on upcoming features

YT Web based snapshot viewer

Imagine you can explore the traceability status of your project which had just been calculated in the last night with your browser.
In the „N”-Release, we built the foundation for a web-based snapshots viewer. Here are two screenshots of our showcase:

Updated implementation of adapter specific licenses

With the „O” Release (scheduled for Apr. 27th, 2020), we will update the implementation of our license management to better honor adapter-specific licenses.
For existing customers only an update of the license file will be necessary.

Bug Fixes

The DOORS adapter showed unexpected behavior when filtering Enum values with „not equals”.

We made our DOORS adapter more robust when filtering objects based on Enumeration values.

include objects if(
	// true if 
	// - multiValuedEnumAttribute = "A,B,D"
	// - multiValuedEnumAttribute = <not set>
	valueOf("multiValuedEnumAttribute") != "C"

N release, milestone 3 (NM3 1.1.1947)

We introduced private queries

When specifying more sophisticated queries to analyze your trace data, you might want to utilize sub-queries which are aggregated by a master query.
For the user, the only relevant query is actually the master query. We added a new keyword private as a flag for sub-queries.
Private queries won’t be presented to the user in order to execute them. In addition, they produce no output in batch/command line mode.

Private Queries

Improved navigation to PTC Integrity items

With YT, one can navigate to PTC items either in the „native” PTC client application or the web application.
For users who chose the „native” PTC client as navigation target, YT showed the items in standalone mode, i.e. without context. Now, YT opens the items „within their context/container” (e.g. a document).

Improved documentation of regular expressions for PDF / Text / Word Adapter

We utilizes regular expressions for data extraction rules. Imagine a text structure such as

REQ 001 lorem ipsum
REQ 002 some really long text
        covering multiple lines
REQ 003 more lorem ipsum

and you want to specify an extraction rule such „from REQ until next REQ”
As several users requested exactly this from our support team, we documented how to do just that .

Bug Fixes

No PTC Integrity login needed when viewing a snapshot

If a snapshot contained requirements (or other itemis) from PTC Integrity, YT asked for the login credentials during the load of the snapshot.
Since the login is not necessary, we removed this question.

N release, milestone 2 (NM2 1.1.1943)

Unified logging for individual data accesses, artifact types, and link types

YT now reports adapter-specific information on a more detailed level, according to the individual definitions in the current YT configuration. It also reports some additional information on YT start and on extraction of traceability data into CSV files (in batch mode). Furthermore, the log messages are now reported by specific loggers depending on which area they belong to.

In more detail, the following information is logged now:

Logger com.yakindu.traceability.formalized.setup

  • On YT start or reload: YT lists all Eclipse projects in the workspace in the form "YT found project name" or „YT found no projects”, respectively.

Logger com.yakindu.traceability.formalized.dataaccess

  • For each data access:
    • When a new resource (e.g., a file) is found: "DataAccess name found resource resource-name"
    • If the data access defines a file pattern and no file is found for that pattern when YT loads: "DataAccess name found no file for pattern pattern"
    • When a file has been changed and re-read: "File path has been updated"

Logger com.yakindu.traceability.formalized.artifacttype

  • For each artifact type, whenever the artifacts of that type have been loaded or updated:

Updated artifact type name
No of changed artifacts: number
(further adapter-specific lines in the form " caption: number")
(adapter-specific lines in the form " caption: measurement ms")

Logger com.yakindu.traceability.formalized.linktype

  • For each link type, whenever the links of that type have been loaded or updated:

Updated links of type name
No of links: number
(further adapter-specific lines in the form " caption: number")
(adapter-specific lines in the form " caption: measurement ms")

Logger com.yakindu.traceability.formalized.dataextract

  • Whenever traceability data is exported into CSV files:
    • For linked artifacts: " number linked artifacts exported in measurement ms."
    • For linkable artifacts: " number linkable artifacts of type exported in measurement ms."
    • For links: " number links of type exported in measurement ms."

Logger com.yakindu.traceability.formalized.queryextract

  • Whenever query results are exported into CSV files: " number result rows of query name exported in measurement ms."

Note that there are currently some limitations:

  • The number of linked artifacts is currently not yet exported separately for each type.
  • PTC and Native File adapters do not yet report link-related information.

Bug Fixes

The text editor adapter saved modified files when creating links by drag-and-drop

When you modified a text file that contains artifacts, it needs to be saved before creating text editor links. In certain rare situations, YT auto-saved text files when creating a link by drag-and-drop. This was not intended, because it might save changes that you didn’t actually intend to keep. YT now enforces manual saving of modified files also in this situation.

The query function „tracesFromTo” did not work for cycles

Execution of queries with the query function „tracesFromTo” could lead to errors when the traceability model contained cycles. This should work now.

N release, milestone 1 (NM1 1.1.1939)

Sophisticated distinction of validations

We moved several parts of our Suspicious Links validation into a separate validation, the Model Consistency validation. The reason for this step is that these parts of the validation are often much faster to execute. Thus, splitting them apart from the more expensive parts has the advantage that they can be executed in situations where not much time is available, while a complete validation is not necessary.

Now the Suspicious Links validation only checks whether the links have been changed, which can take very long for some adapters. While the Model Consistency validation contains by far more checks, they typically don’t require that much effort.

New validation menu

You might have noticed that these two validations had been separate before and have been merged into the Suspicious Links validation in LM1 for usability reasons. In order to keep the improved usability, we added a new menu option to execute all three validations that are related to links. These are the validations for Suspicious Links, Model Consistency, and Duplicate Links.

Improved usability for report creation

When generating reports based on the traceability model, you usually want the model to be consistent, such that you can trust the results that are contained in the report. For this reason, it is advisable to execute at least some of our validations. However, you might have to wait very long for the validation results, before you can start the report generation. Also, you might just forget to execute the validations at all.

New report wizard

To improve this situation, we extended the report wizard with the option to select the validations that should be executed before generating the report. If the validation produced any errors or warnings, a dialog will ask you whether or not the report should be created anyway. Otherwise, report generation will start immediately after the validation.

We also made two minor improvements to the usability of our report generation. First, customers noticed that the button for selecting parameter values in the report wizard was hard to find. So we made it more visible. Second, there is now a progress indication for the report generation, which is visible in Eclipse’s task bar and in the Progress view.

Improvements of the YT Explorer

When artifacts are linked to themselves (which is rather unusual), they are now decorated with a special icon. This icon is visible in both the YT Explorer and in the YT Overview. In the screenshot below, you can see this new decoration next to the artifact „SW-QTS: ASIL A”.

Decoration for self-linked artifacts

You can disable/enable this icon and other decorations in the Eclipse preferences ( General → Appearance → Label Decorations).

Improvements of the query language

We extended the query function traceMatrixFor to support access to attributes (including custom attributes) of the artifacts contained in the traces that have been found by the function. This works even if you access more than one artifact at once. In this case, the attribute values of all artifacts will be combined to a comma-separated list that is stored in a string.

If these attributes are also objects with attributes, you can access those as well. This applies recursively. The above-mentioned comma-separated list will then contain the values of the final attributes that are accessed in this way. For example, A.attr1.attr2 will result in a list that contains the values of attr2. If A, attr1, and attr2 each contain a single value, the final list will consist only of one attribute value. Note that not only can A be a set of artifacts, but also attr1 and attr2.

Bug Fixes

Fixed a bug regarding the string function "match"

When used in the attribute mapping adapter, the match function returned the original string if the regular expression did not match. For other adapters, match returned an empty string in the same case. This is according to the keyword’s description in the help. We corrected the function’s evaluation in the attribute mapping adapter to behave like in all other adapters.

Fixed a bug that could lead to bogus name change errors

We fixed a corner case where a QuickFix for a suspicious link issue could result in a name change error when there was actually no name change.

M release (MM5 1.1.1934)

YT Plus – We want to involve our users in the definition of upcoming features of YAKINDU Traceability

We want to provide more features which are beneficial for you – and we want to provide these benefits in the form of YT Plus features. In this post, you may read more about YT Plus .

To be most helpful to you, we are really interested in your needs and wishes. Therefore, we now offer a preview on the first YT Plus features, namely:

YT Project Summary

The YT Project Summary provides an overview of your project’s artifacts, coverage metrics, as well as even navigation to any work product within your project.

For those of you who know this view already from a prior milestone release and know the YT Configuration Overview: We eventually named it Project Summary. The name is a better fit.

YT Search

With the YT Search, you search the work items (such as requirements, test cases, model elements, software units, …) in a google-like manner.

Improvements of the DOORS NG adapter

Credentials are stored in secure store

You no longer must provide the DOORS NG credentials in the form of plain text as part of the YT configuration. Instead, YT now prompts you on first access for the credentials and stores them in the so-called secure store.

DOORS NG prompt

If you run YT in command line mode, you also may provide the credentials as Java System properties


Improved Artifact Type configuration

The filtering of artifacts in Artifact Type Config in addition to == and !=, now supports the
keywords in, !in, contains, and !contains. Multiple constraints can be added separated by

DOORS NG configuration

In addition, custom attributes can now be filtered like any other attributes by specifying them in double
quotes with any of the constraint keywords. The keyword customField has been removed. For your convenience, the content assist of the configuration editor now retrieves the list of attributes of DOORS NG’s meta model and suggests them once triggered by CTRL+SPACE.

M release, milestone 3 (MM3 1.1.1930)

Improved Configuration Overview

The Configuration Overview displays artifact types associated with disabled data accesses with a dashed border. If a link type has a disabled data access, it is represented by a dashed arrow. A click on the artifact count bubble opens the artifact search.

Configuration Overview with big bubble and artifact types with disabled data access

Better proposals in Search view

Proposals in the Search view have been improved. In order to fix possible misspellings, they now contain also words that are similar to the one that was typed.

Mistyped search correction

Multiple conditions in Attribute Mapping

For links mapped by Attribute Mapping, it is now possible to define multiple constraints to match both involved artifacts. Think about two artifacts in the same file which reference each other by an ID. Up to now, you had to define an attribute in each of the two involved artifact types that combined the ID and the resource in a single string. Now you can separately reference the ID and the resource.

Test view for regular expressions

A new view for testing regular expressions has been added and is available via hyperlink in the configuration where a regular expression is expected. Just press Ctrl and click on the String to open the view, pre-filled with the current expression.

Regular expression tester view

Bug fixes

Snapshots support nearly all Unicode characters

After some adapters extracted rarely used Unicode characters for artifacts, the snapshot creation failed. Except some control characters, all are now supported for snapshots also. Another fix removed an error when a snapshot with an empty parameter value was loaded.

YT_Snapshot_Viewer.bat fixed

The YT_Snapshot_Viewer.bat has been fixed to support also paths with braces and other special characters in the path and file name.

M release, milestone 2 (MM2 1.1.1926)

Link Coverage in Configuration Overview

We extended our new Configuration Overview (a YT Plus feature) to show coverage indicators on link types that display the coverage percentages and visualize them as colored bars.

Configuration Overview with coverage indicators

Coverage is computed for each link type for both directions. Since every arrow represents one link type, there are two bars on each of them. The bar closer to a given artifact type shows which percentage of its artifacts is linked to at least one artifact of the other artifact type that is involved in the given link type.

Configuration Overview with details about coverage

You can see the actual numbers of linked versus total artifacts for a link type by clicking on the arrow representing it. In this example, three of the eleven „Software architecture” artifacts are linked to a „Software integration test specification”, resulting in a coverage of 27%.

Adapter improvements

Xtext adapter can read artifacts from the index

To improve the performance of our Xtext adapter in certain usage scenarios, we added the option to read artifacts directly from the Xtext index, instead of always parsing the actual files. However, the adapter up to now only supported rule-based filtering of artifacts, for which the Xtext index does not provide enough information. Therefore, we extended the configuration language to also support filtering artifacts by their EClass (i.e., their type).

DOORS performance tuning

We found some ways to improve the performance of our DOORS adapter.

Bug Fixes

In some cases, the DOORS adapter did not find all links in the specified baseline.

M release, milestone 1 (MM1 1.1.1922)

Configuration Overview

As latest YT Plus feature, we added a new interactive Configuration Overview.

Side note: The YT Plus approach comprises some experimental preview/early access features. If you are curious, you are welcome to try them out – so is your feedback. You can activate the new features in the YT preferences.

Adapter improvements

Load DOORS data from cache – even if DOORS is not available

In situations where you already extracted DOORS data before and your DOORS client is not available, YT loads the cached data without starting the DOORS client.

Improvements in configuration of Enterprise Architect adapter

The artifact type configuration of the EA adapter has been improved. It is now possible to assign a custom name and to access built-in attributes like „name”, „metatype”, etc. Of course, you can still access tagged values.

Selection propagation to PTC Integrity

The user can now decide whether he wants to use PTC Integrity’s web application or the client application when navigating to these artifacts. Just set your preference.

Bug Fixes

Fixed a bug regarding looong matches in MS Word

We had a problem when we tried to select and reveal engineering artifacts in Word when the text match was larger than 255 characters. Word did not let us. We found a workaround.

Fixed a bug during data extraction

In the batch/CLI mode, the data extraction was not robust with regards to special data constellations, namely if a link type attribute – as specified in the YT configuration – was not set. We fixed this.

L release, milestone 5 (LM5 1.1.1917)

YT Search view

In this release, a new search view is available, which supports search term suggestions and search for combined attribute values.
YT Search

Improved multi-file support in Rhapsody adapter

The Rational Rhapsody adapter is able to read models where subsystems are stored in separate files in the project folder. It can also extract links.

For collaboration, it is possible to store subsystems of a project in separate files in the project folder of Rhapsody. This allows different people to concurrently change these documents and to collect these changes in a source code management system without the need to merge conflicting changes in the same file. The adapter is aware of these files and can read artifacts and links.

Support XML resources from URI

The XML Adapter supports fetching artifacts from remote URIs in addition to local files. Instead of the resource keyword, the resourceURI can be defined in the data access. You may also use both keywords in the same data access definition.


Module properties are accessed less often and the launcher for the DOORS client can be configured.

Checking the module properties can lead to higher memory consumption and slow performance of the DOORS client. To avoid accessing the properties, they are only read after other constraints, like „name” or „fullName”, have been matched.

For use cases where the client has to be launched with different databases, it is possible to define a launcher:../user-guide/adapters.html#ibm_doors_adapter_client_launcher in the workspace preferences. This executable is called when YT finds no running DOORS client. It is responsible for starting the client with the required parameters.

Reduced memory requirements for adapters Excel and XML

The way how files are processed and links are extracted was optimized behind the scenes to load data with less memory consumption. As a side effect, the progress shows which file is currently processed and gives a hint where the time is spent.

Bug Fixes

Stabilized batch data extract

Under some circumstances, like heavy load in combination with Mylyn or query-based links, the data extract failed with 'No TVM was provided until timeout'.

Support for DOORS NG improved

The requirements for projects in DOORS NG were reduced. Projects without explicit configuration or description can be loaded.

L release, milestone 3 (LM3 1.1.1913)

Values in configuration parameters are now decoded similar to strings.

It is now possible to copy an expression from the configuration directly to a parameter without the need to escape any characters.

Added help section on how to enable the welcome page under Linux.

In order to display the welcome page on a Linux system, it is sometimes necessary to install third party libraries. We added a section on how to do the necessary installation to the user documentation.

The preference dialog will now open on the YAKINDU Traceability page by default.

When opening the preferences, the YAKINDU Traceability preference page is selected as a default, instead of the „General” page.

Bug Fixes

Update the PTC adapter to use the latest mksapi.jar

The PTC adapter now uses the latest version of mksapi.jar.

PTC update on configuration change

Under certain conditions, the PTC adapter did not invalidate its cache when the data access configuration was changed.

YT start up performance leak fixed

There was an issue that under certain circumstances created a large number of threads during YT startup. This has been fixed.

‚Delete all links’ confirmation dialog also contained links that can not be deleted

There was an issue that caused read-only (locked) links to show up in the „delete all links” confirmation dialog, after selecting „delete all” via context menu.

Adapter DOORS – Links were not evaluated correctly for links across baselines

Links that point from one baseline to a previous baseline were mistakenly considered as links within the same baseline. This can lead to additional links.

Adapter Text – Links were sometimes considered twice when the search pattern contained white spaces

Under some circumstances it was possible that the text adapter extracted links as duplicates when the search pattern contained white spaces.

L release, milestone 2 (LM2 1.1.1909)

Improved IBM Rhapsody adapter

The adapter can read attributes for artifacts and read links based on relations (Generalization, Association) and the containment of elements.

Bug Fixes

Enterprise Architect can distinguish elements with the same name in one container

In Enterprise Architect it is possible to create several elements, for example classes, with the same name in the same package. YT now takes this into account and will derive one artifact for every element, even if they are only different in their GUID (Globally Unique identifier). This is also considered when constructing the hierarchy of artifacts in YT, i.e, child elements will be inserted into the correct position.

Integrity content assist proposals include more fields

Integrity’s im fields command does not always return all available fields. Now we propose also fields which are not returned by this command, but are known to be available on the given item types. We also fixed a problem with reference cycles of Integrity items while loading the document structure.

Batch mode waits for query-based link extraction

Under some circumstances, the batch mode did not wait for the latest update of the query-based link extraction and failed because data was changed while exporting. Now the data export will wait until all links have been loaded.

L release, milestone 1 (LM1 1.1.1905)

Important: The YAKINDU Traceability license now contains information regarding eligibility for updates

We added a version concept to YAKINDU licenses. The driver for this change is that we want to improve the support for YT updates: Now a user or administrator can figure out whether she is eligible for an update by double-clicking the license within the YAKDINU licenses view.

license details dialog
The screenshot shows that the current license supports updates up to version 19.6 .

As a consequence, together with this milestone/release you need to exchange your existing license file.
The YT support will contact you proactively to support you during this exchange.
In order to support further YT updates, this exchange will be necessary with each renewal of the maintenance contract.

Important: We now have a dedicated license for batch runs

The YAKINDU Traceability batch mode now requires a dedicated license.
As a consequence, together with this milestone/release users of the YT batch mode need to exchange the existing license file.
The YT support will contact you proactively to support you to set up your license management.
In order to support further YT updates, this exchange will be necessary with each renewal of the maintenance contract.

YT improved validations

Custom validations

YT now supports custom validations. You can specify „invalid” artifacts by YT Queries. Please refer to the help for details.

custom validations example

Merge of Model Consistency and the Suspicious Links validation

We received several requests to merge the Model Consistency and the Suspicious Links validation. The main reason was that users wanted one validation which reveals changed artifacts and deleted artifacts. Therefore, we merged this validation in the menu, the menu item Suspicious Links now triggers both validations.

PTC Integrity adapter: Extended customization for field Names

Independent of the configuration of YT, YT always accesses some standard fields while extracting data from PTC Integrity (namely: summary, test, document id, contains ). As the field names may be customized within Integrity, it is up to YT now to reflect such adjustments in the YT configuration. This customization was supported for summary and text before and now also covers document id and contains .

Bug Fixes

ModelViewer invasive storage: Added handling for brackets

YT can store link information within Matlab slx files. There was a bug that brackets within this link information were not escaped which carried the risk to corrupt the slx file. Now, brackets are escaped.

We fixed a bug in BIRT (Reporting Engine)

YT comes together with BIRT as Reporting Engine. There is a bug in the Oxygen-Release of BIRT – it does not include the BIRT preview viewer. We fixed this bug for YT Distros.

The configuration editor now prohibits editing of configurations residing in a snapshot

Configurations in a snapshot are immutable. Before this fix, the YT Configuration Editor suggested that the mappings were still editable.

K release (KM5 1.1.1850)

Prototype of a DOORS NG adapter

We created an adapter for the new version of IBM DOORS, called „IBM Rational DOORS Next Generation” (DOORS NG). So far, this adapter is only a prototype with basic functionality. The adapter supports loading DOORS NG objects as artifacts and mapping certain properties of these objects to the artifacts' custom attributes. Artifacts can be filtered based on these properties. The adapter also supports loading of links between objects into YT.

DOORS NG artifacts

Currently, the DOORS NG adapter is not yet production ready and is not explained in the help document.

Native File data access now has support for files that were created for different configurations

The Native File adapter stores links in files (usually called „”) in YT’s own format. Up to now, there was no support for loading files that were created with a different configuration, even if that configuration was essentially identical to the current one. Moving or renaming the configuration also made it incompatible with these files. Now the adapter will try to automatically map artifact and link types used in a file to those in the current configuration. If this is not possible, it creates markers in the YT Issues view with quick fixes that allow for manually assigning the correct types.

Improved progress report for DOORS adapter

While loading links and artifacts, the DOORS adapter will now report its progress in more detail in the Progress view. It displays the name of the currently processed module, how many modules it has already loaded and how many it still needs to process.

Bug Fixes

Fixed issue that could prevent snapshots from being loaded correctly

In some cases, the links and artifacts of a snapshot weren’t loaded when YT was already running before opening the snapshot.

K release, milestone 3 (KM3 1.1.1846)

We changed the Eclipse platform

Please note: YAKINDU Traceability has moved from Eclipse Luna to Eclipse Oxygen.
When migrating from KM1/KM2 to KM3 or from any YT version to K, we strongly recommend to not use the built-in update mechanism (i.e. Help > Check for updates), but to replace your existing YT by unzipping a new YT Distro.

Improved DOORS adapter’s data extraction mechanism

We implemented a new strategy of how YT extracts data from DOORS. Main driver for this implementation was the DOORS memory consumption during the YT data extraction. Instead of extracting „as much data as possible” in one DXL run, we now use a split strategy: We run several DXL scripts and collect/unify the results in YT itself. As a side effect, the performance of the data extraction has been improved.
As we didn’t change anything regarding the YT configuration, there is no need for you to adjust it. The only effect that is visible to a user is that we removed YT preference whether to load DOORS data to multi files/one single file, as multi file is the only option now.

By the way, we are now extracting / preserving line breaks that exist in DOORS attributes (e.g. within the text of a requirement)

Usability Improvements

We overhauled the YT menu structures

For the YT perspectives (YT Tracing, YT Configuration, YT Analysis), we overhauled the menu structures by removing entries which were not relevant.

We also added a menu item to directly switch the „current” YT configuration.

The Error Details dialog closes after fixing the last error

Imagine that YT revealed some suspicious link validation issues and you are in the process of fixing them one by one.
You will probably open the „Error Details” dialog, iterate over the issues and trigger the fixes. Once you applied the fix of the very last error, the Error Dialog now closes automatically.

Bug Fixes

„Export Queries” is now more robust

  • It is now possible to append YT queries to any Excel file format. Before, it was restricted to xls and xlsx.
  • In some cases, it was not possible to export query results containing empty cell representing ‚null’ values to Excel. We fixed this.

It is now possible to open YT configurations files residing outside your workspace

Until now, it was not possible to open a YT configuration file residing not in your workspace. Now, you can simply use File > Open and choose the desired yt file.

Suspicious Validation failed for links stored in Excel

The suspicious validation failed if

  • links were stored in Excel
  • the link had attributes configured which are also to be stored in Excel
  • the link cardinality is exactly 1
  • one of these attributes was empty.

We fixed this!

Polarion adapter support custom fields with whitespace

YT failed to extract data from polarion if you configured custom fields with names containing whitespace characters,
e.g. include objects if( customField ("code Freeze Date")=="" ) .
Now, you can extract the code Freeze Date (and any other custom field holding whitespaces).

K release, milestone 2 (KM2 1.1.1842)

Nothing new here ... we didn’t even ship this milestone.
But don’t think we were lazy: We heavily worked on the re-implementation of the DOORS data extraction which will be published in KM3.

K release, milestone 1 (KM1 1.1.1838)

„New” YT Explorer

We moved YT Explorer to a new technical platform. The one and only reason to do so was that the old platform led to a bad performance on Windows when exploring larger trees. From a functional point-of-view, we did not change anything – except for one detail: We removed the „artificial subnodes” and, as a consequence, the „maximum number of children” setting from the preferences. Since we had introduced these subnodes as a workaround for the suboptimal performance on Windows, they now have become dispensable.

The Microsoft Word adapter can now read control elements

The Microsoft Word adapter now can read the content of form controls existing in Microsoft Word documents, e.g., it can read the value the user selected within a „Combo Box Content Control”.

Improved robustness of suspicious validation

The suspicious validation failed if it identified changes in huge attribute values (more than 30,000 characters). The reason for that is a „natural size limit” of error messages within the Eclipse platform. We now create shorter messages in such cases.

Suspicious Validation

Usability improvements

Honoring user preferences in YT Overview

One of the features of YT Overview is that it can draw multiple traceability graphs on the same canvas, e.g., if the user selects a multiplicity of artifacts in YT Explorer. In order to avoid an over-population of YT Overview, we introduced a preference setting which controls the maximum number of artifacts/graphs to be considered. Before KM1, we simply did not render all the selected artifacts/graphs. In order to avoid confusion, we now give a clear signal to the user in such cases.

YT Overview

Better feedback if the user tries to link artifacts which are not configured to be linked

If YT Editor was populated with artifacts which were not meant to be linked, YT Editor simply stated „no editable link type found”. Now, the feedback to the user has become a little bit more proactive.

YT Editor

Artifact tree in artifact search dialog and bulk link creation editor is expanded by default

If an artifact tree in the artifact search dialog or in the bulk link creation editor has only a single root node, the whole tree is expanded directly. Anyhow, if an artifact type defines more than one resource, e.g., if you specify more that one file containing test cases, the behavior is unchanged.

Artifact search dialog

Batch mode improvements

Query results are now exported not only in CSV format, but also as Excel file

When running YT in command-line mode, YT exported query results only to CSV files. With this milestone, YT also creates Excel files containing the results.

A batch run fails if DOORS is unavailable

When running in in command-line mode, YT ignored an error that could occur if data were to be extracted from DOORS and either the DOORS client or the connection from the DOORS client to the DOORS server was not available. YT then analyzed the remaining artifacts. We removed this „robustness”, and now the batch run fails in such cases.

J release (JM5 1.1.1831)

Better layout of user preferences views

The structure of the user preference views has been improved.

YT user preferences

Several layout adjustments

We did several (minor) layout adjustments, namely

  • The location of the console view in the YT tracing perspective
  • The location of the YT issues view in the YT configuration perspective
  • If the user decides to SetUp workspace on the welcome page, YT now opens the configuration perspective.
  • The layout of the artifact search dialog is no longer broken in cases of long artifact type names.
  • The user cannot open the YT snapshot list, if the application is not in snapshot mode.

Bug fixes

Suspicious validation did not work in cases of huge attribute deltas

In cases of attribute deltas which were larger than 65,000 characters (imagine, e.g., a requirement which needs ~10 pages of specification), YT had a bug when notifying the user about the suspicious artifact. We fixed this.

J release, milestone 3 (JM3 1.1.1826)

YT now supports parameters in the configuration

Imagine you want to re-use the same configuration with only slight adjustments, e.g., analyze the traceability of your project for different releases.

In such cases, the release has to be configured for several data accesses, artifact types or link types. You now don’t need to adjust the ‚release’ specification in all these definitions individually, but you can introduce a parameter. That will have to be adjusted only once, and its new value will be applied everywhere the parameter is used.

Parameters in YT Configuration

Parameters in YT Configuration

Improvements and fixes of the Polarion adapter

  • We improved both performance and memory consumption when reading links from Polarion.
  • It is possible ow to configure YT to read custom fields from Polarion.
    Custom attributes in Polarion
  • YT can be configured to log SQL statements that are sent to Polarion.
  • We fixed a bug regarding the artifact type configuration: YT did not evaluate camel-cased attribute filter criteria such as valueOf(project)=="MyProject" correctly. We now honor case-sensitivity.
  • YT raised an error if an artifact type was configured without any filter criteria. This has been fixed.

The PTC adapter now supports attribute names with commas

The PTC adapter now supports commas in (custom) attribute names. This enables configurations such as the following:

map to "Test" if ("Category" = "Test") {
  "manual result" to "result,manuallyDerived"

Usability improvements

  • Improved guidance in the YT configuration editor: The wizard that enables the creation of link types now gives a clearer warning if a user creates a duplicate link type.
    Warning when creating duplicate link type
  • If the user clicks on the hyperlink in the Validation succeeded dialog, YT does not only open the issues view, but now also closes the dialog.

Validation succeeded dialog

Bug fixes

Fixed an error when propagating (no) selection from Excel to YT

In cases where an Excel file which was not relevant for traceability resided in the YT workspace and this file was opened in Excel, YT needed quite some time to figure out that the selection propagation from Excel to YT was not relevant (because the whole file was not configured to be relevant). This has been fixed.

Improved means to open a query file

In some cases, it was not possible to open a query file using the edit button or the context menu, while it was still possible to open the file by a double-click. We fixed this.

Query file context menu with edit button

J release, milestone 2 (JM2 1.1.1821)

Improvements to the IBM DOORS adapter

  • In case of the multi-project mode, YT now supports a white list of project names in the configuration of the DOORS data access.
    DOORS multi project whitelist
  • Similar to the configuration of the objects that should be read from DOORS, it is now possible to configure the link modules to be considered by YT.
    DOORS link module filter

Performance improvement for Excel

We improved the performance of the selection propagation from Excel to YT.

Similar to the YT editor, the bulk link creation editor now warns the user if it is about to create duplicate links.

Warning duplicate links

Bug fixes

YT now saves C/C++ files after link creation

If the user creates links to/from C/C++ by means of dragging-and-dropping into the C editor, YT saves the C source file. The file does no longer remain „dirty” in the editor.

Avoiding warnings in the Serna editor

In some cases, the Serna plugin shipped with YAKINDU Traceability tried to disconnect Serna from YT, even if no connection had been established yet. This lead to an annoying exception notification, which popped up in Serna. We fixed this.

J release, milestone 1 (JM1 1.1.1817)

Improvements to the Mylyn adapter

The Mylyn adapter can now read custom attributes

Mylyn is the task and application lifecycle management (ALM) framework for Eclipse and comes with dozens of extensions, integrating Mylyn with ALM and developer collaboration tools. We enhanced our Mylyn adapter to not only support the built-in Mylyn attributes, but to also support custom attributes of the specific Mylyn extension. If one uses Mylyn to, e.g., trace to Jira issues, YT is not only able to read the attributes of the Mylyn representation of Jira issues (which is a subset of all Jira attributes), but to also read all additional Jira attributes.


The Mylyn settings can be applied in batch mode

Imagine you configured Mylyn to extract tasks from an issue tracker which are relevant for traceability. Mylyn stores these pieces of information locally. In order to share such configurations among your team, Mylyn provides means to export and import them. It even updates the surrogates of the tasks that have been extracted.

YT is now able to import Mylyn configurations in batch mode – and even to trigger the live data synchronisation during batch runs.


Performance tuning for reports: YT attribute mapping now supports propagation of attributes from linked artifacts to the link itself

In order to improve the performance of generating reports and to ease the specification of custom queries, it is now possible to populate derived links with attributes of the linked artifacts. The goal of that approach is to feed the reporting engine with a list of links and to avoid the need to instantiate the linked artifacts during data analysis.


New default report "Link coverage"

We added a new report illustrating the capabilities of the built-in reporting engine. The report lists ratios of source coverage and target coverage for each link type defined in the YT configuration.


I release (IM5 1.1.1813)

Tracing perspective adjusted

The new bulk link creation editor provides search and filter mechanisms, which are especially designed for occasional users, e.g., filters similar to Excel’s auto filter. Thus we replaced the YT Query view by the bulk link creation editor. And, by the way: If you want to enlarge a view – for instance the bulk link creation editor – you can do this by a simple double-click on the view’s tab. Double-click on it again, and the view’s size is restored to its former dimensions.


Progress bars no longer stalling

The progress reported by YAKINDU Traceability when reading data, namely from DOORS and Excel, was in some cases not accurate. In fact, YT’s progress bar stalled at some points during the data load. We made this more accurate.

Better user guidance in the configuration editor

We improved the user guidance especially for setting up new configurations, i.e. if data access, artifact type, or link type are not yet specified.

Better guidance on empty tabs

Deleting a link now requires a confirmation

In order to prevent accidental deletions, deleting a link using the [DEL] key now requires an explicit confirmation.


Excel link storage now escapes the separator character

With YT, you can store link informations invasively in Microsoft Excel. If YT stores two or more links for the same Excel artifact, the information in the Excel cell is separated by the pipe symbol ( |). Any pipe symbol within the link information itself is now escaped by a backslash, i.e. ( \|).

Bug fixes

Fixed a bug regarding updates of the YT Issues view

Under certain circumstances, the YT Issues view was not updated after doing a validation. To be more precise, this happened if the validation was triggered while both YT Issues view and configuration editor were open, and the YT Issues view was emtpy. We fixed this.

I release, milestone 3 (IM3 1.1.1809)

New Bulk link creation editor

We added a new link editor: The Bulk link creation editor facilitates fast link creation by a simple drag-and-drop mechanism.

Bulk link creation editor

In order to find the relevant artifacts in your particular case, the Bulk link creation editor also supports general text filters as well as attribute specific filters which can be defined for particular columns.

DOORS adapter: Alternative data extraction strategy

In order to optimize the performance of DOORS data retrieval of YAKINDU Traceability, we now offer two data extraction strategies

  • all in one run: YT triggers one DXL run which reads all data from DOORS for all artifact types and all link types in one run. This is the established strategy.
  • dedicated run per artifact mapping: YT triggers a dedicated DXL run for each configured artifact mapping. This run extracts all relevant artifacts incl. outgoing links. On one hand, this may slow down the performance of a full raed as link modules may be read multiple times if they contain link sets belonging to multiple artifact types. On the other hand, partial reads are now possible: If you change the YT configuration for one artifact type, only the data of this type is reloaded from DOORS.

YT DOORS preference settings

Background: For larger projects, we ran into situations with the DOORS client stating „Memory exhausted”. It was simply not possible to extract all data in one run. Therefore, we now offer the above option – together with the established option to „always reload DOORS on startup” you can configure the DOORS data extraction strategy to optimal performance with regards to your project size.

Polarion adapter: Support navigation to Polarion

It is now possible to navigate from YAKINDU Traceability to Polarion by means of a doubleclicking the representative of the Polarion work item in YT.
On doubleclick, YT opens the browser with an URL directly pointing to the Polarion work item.
Note: In order to use this feature, you may want to adjust the configuration of the Polarion data access in order to give YT a hint regarding the Polarion base URL.

Polarion URL

Better feedback when creating links by drag-and-drop into editors

We improved the hover feedback when dragging artifacts into text editors or C/C+editors. YT gives now better guidance whether the current cursor position is a valid drop location.

Hover feedback

Changed strategy for description of YT Issues

We changed the pattern of the description of issues which were revealed by YT validations (e.g. suspicious links, missing artifacts).
The old pattern was Artifact + Kind of Issue . This made it hard to seach for issues by kind, especially in cases when only a part of the description was visible. In order to improve the usability in this case, we changed the pattern to Kind of Issue + Artifact

YT Issues text

New query function "unionAll"

In order to overcome potential misunderstandings regarding duplicate elements in unions of query results, we added a new query function unionAll .
As a rule of thump, keep in mind that the following:
- union : duplicates are discarded
- unionAll : duplicates are retained

Bug fixes

YT Configuration Editor: Better synchronization of tabs during edit

It happened that the tabs of the YT Configuration Editor were not synchronized during edits. It required e.g. to steps incl. an intermediate save if you wanted to add a new data access and a new artifact type. THis has been improved, now you can e.g. map an artifact type to a newly created data access even if the configuration without an intermediate save.

Eclipse Explorer adapter: Fixed a bug in selection propagation

Each selection that happened in the Eclipse Explorer was propagated to YAKINDU Traceability.
As a consequence, the selected resources (i.e. files and folders) and their related artifacts had been visualized in YT.
This worked even for those files and folders which were – according to the YT configuration – not relevant for Traceability.
This has been fixed, selections of irrelevant resources are now ignored by YT.

I release, milestone 2 (IM2 1.1.1805)

New welcome page

We adjusted the welcome pages for the whole YAKINDU product family.

New setup wizard

Text editor: (hyper) linking improved

If the YT text adapter is configured to invasively store links in text files, these links are now recognized as hyperlinks. [Ctrl + Click] opens the related work product directly from the text editor.

Configuration editor: improved validations for links stored invasively in C/C++/text files

The configuration of links stored in C/C++/text files is based on regular expressions, especially based on groups in these regular expressions.

Query language: support for Java methods added, especially for strings, e.g., contains, matches, etc.

In order to not confuse the user, existing Java methods were not supported by the query language, even though the query language uses Java at runtime.

This has been changed: Java methods are not supported.

As we still do not want to confuse the user, only „prominent” methods are provided as code completion suggestions, but especially for strings any method can be used by manually entering it in the editor.

String proposals in query language

Bug fixes

Fixes for macOS user interface

On macOS, some columns in the YT configuration editor were overlapping.
In addition, the YT link editor layout crashed in some situations, when reloading the current configuration. Both user interface issues have been fixed.

Export query results to Excel: corrected error message if Excel file is not available

If a user configures the export query results wizard to append data to an existing Excel file, YAKINDU Traceability now shows an explanatory error message if the Excel file does not exist.

Improvements for Serna adapter

  • In some situations, the user preference specifying the Serna location was emptied. This has been fixed.
  • We changed the Serna plugin that is provided by YAKINDU Traceability: The plugin now disables multiprocessing of logging within Serna (which is possible by the API, but not supported at runtime). For Serna exports, the YT plugin sets logMultiprocessing=0 programmatically. This overwrites the corresponding setting in
  • We improved the guidance for a user trying to open an artifact in Serna without having the Serna location configured:

Serna dialog

  • The connection between YAKINDU Traceability and Serna is robust with regards to YT restarts: Serna tries to re-connect eagerly.
  • When navigating from YT to Serna, YT always opened a new instance of the affected file. This has been improved: If the file is already open in Serna, YT selects the artifacts in the open file.

Improved synchronization of „YT issue detail” dialog and „YT issues” view after applying quick fixes

If a user fixed multiple YT issues at once while the YT issue detail dialog was open, the system lost the synchronization between YT detail dialog and YT issues view. It also happened that the detail dialog showed the details of an error that has just been quickfixed. Both cases have been fixed.

Query language: increased robustness regarding null values

Queries with aggregations, i.e., with groupBy expresssions, such as

select traceLinks(A,B)
.collect(,, @max(B.releaseNr))

returned wrong results if the aggregation encountered null values, in this case if one B.releaseNr was null).

I release, milestone 1 (IM1 1.1.1801)

New setup wizard

We added a wizard providing guidance on how to set up an empty workspace. It helps unexperienced users to create or import projects or YAKINDU Traceability configurations.

New setup wizard

Polarion adapter supports attributes

The Polarion adapter now supports the retrieval of work items attributes. Here’s an example taken from the corresponding documentation section:

You can map attributes, too. Example:

include objects if(
	attribute to valueOf(author)
	^severity to valueOf(severity)
name valueOf(id)

This example expands the previous example. Here we are mapping two attributes to the values of a Polarion work item.

New link storage for text files

The text file adapter now supports storing link information in text files invasively.

The following image illustrates this:

New link storage for text files

In the YT configuration belonging to this screenshot, requirements in the text file are recognized based on the pattern „REQ” followed by digits, and links are recognized based on the pattern „@LinkedDetailedDesign:” followed by the path to the linked artifact.

Links can be created using the YT Editor or by a simple drag-and-drop operation.

Usability improvement for validations

If the user is notified that the YT validation has found some issues, YT now offers a link to immediately navigate to the YT Issues view.

Usability improvement for validations

Constraint that only one PTC Integrity data access can be active is now explicit

YT now validates that only one PTC Integrity data access is active.

Constraint that only one PTC Integrity data access can be active is now explicit

Better notification if server port in use

YT now explicitly notifies the user if it cannot offer remote procedure calls due to the configured port being already in use. This may occur if, e.g., more than one YT instances are running on the same machine.

Better notification if server port in use

Better consistency in YT configuration editor

In some situations, changes to the configuration that had been specified on one tab were not propagated unless the configuration was saved. If a user, e.g., created a new data access, this new data access was not available for the mapping definition of artifact types unless the configuration file was saved or the editor was refreshed. This has been fixed.

Fixed a bug in the YT editor when replacing artifacts

If a user wants to replace the very same artifact in all links from/to that artifact, e.g., because the original artifact has been deleted and a new one has been created instead, the Artifact search dialog now displays artifacts of the correct type only.

Better consistency in YT configuration editor

Documentation overhauled

The documentation sections on several topics have been overhauled and extended considerably:

H release (HM5 1.1.1749)

Wizards ease the creation of new data accesses, artifact types, and link types in the YT configuration.

We added wizards that guide the user when adding data accesses, artifact types, and link types to the YT Configuration.

Better support of the exchange of YT snapshots

In order to make the traceability of your project more comprehensible, we added out-of-the box support for the exchange of snapshot of YT data.

  • A snapshot is now contained in one single file with the .ytsnapshotzip filename extension.
  • The YAKINDU Traceability batch runner can be parameterized to create a snapshot after all artifacts and links have been loaded. This is controlled by the snapshot parameter, e.g., YT.exe … --snapshot /some/path/snapshotname … creates the file snapshotname.ytsnapshot in the /some/path folder(s).
  • We added a snapshot viewer application. It takes a snapshot file as parameter, launches YAKINDU Traceability which then displays the specified snapshot. Currently on Windows only, you can now drag a .ytsnapshotzip file and drop in on YT_Snapshot_Viewer.bat to start the snapshot viewer.

We added the File menu to the Tracing perspective

The File menu is required to setup a workspace from scratch. Therefore, we added this menu to the Tracing perspective.

Improvements of user notifications

  • We now better explain what it means that Excel is „busy”.
  • We explicitly name the type of suspicious links.
  • We improved notifications regarding missing files.
  • Especially for the Enterprise Architect adapter:
    • We verify that links to be stored in EA are related to artifacts extracted from EA.
    • The configuration of links stored in EA now supports the synchronization of the name of a „linked artifact” and its representation in EA (in addition to any custom attribute).

Bug fixes

Query results: YT does no longer freeze when selecting a large number of results

Under special conditions, YAKINDU Traceability froze when a large number of query results was selected by, e.g., pressing [Ctrl]+A in the query results view. The reason for that freeze was that the YT overview was updated to draw the graph with all selected artifacts resp. links. We added a preference setting controlling the maximum number of artifacts that are used to update the YT overview.

If deactivated, YT no longer complains about missing licenses

In the YAKINDU Licenses preferences settings, it is possible to deactivate the checkout of YAKINDU Traceability licenses from a floating license server. Without a license, YT was deactivated – except for the license check. As a consequence, YT complained about the missing licenses every two minutes. We deactivated the license check as well.

HM3 (1.1.1743)

Improvements of YT Explorer

  • Improved performance: On Windows, the YT Explorer was slow when showing large numbers of artifacts (more than 1,000) all belonging to the same artifact type. This has been improved by introducing an artificial grouping of nodes in the YT Explorer, based on their count. The group size can be adjusted in the preferences.
  • Improved usability of link deletion: It is now possible to delete multiple links at once by doing a multi-select in the YT Explorer and then hitting the [DEL] key.

Improved usability of the error detail dialog

When the user did a quick fix on an error, the error detail dialog was not updated – it still showed the error, which may have been fixed already. This has been improved: Now the dialog shows the next error or closes itself if no more errors exist.

Improved usability of snapshot management

  • We improved the guidance when deleting snapshots.
  • If the user is in snapshot mode and chooses to reload the current configuration, the snapshot mode is ended and shows the artifacts and links defined in the current configuration.
  • YT now stores the changes to the size of the snapshots list’s columns.
  • YT shows a warning if the user compares snapshots that are based on different configurations of YAKINDU Traceability.

Improved usability of the YT configuration editor

If suitable, the code completion now suggests chains of keywords. For example, imagine the attribute mappings section for an adapter: In most cases, the configuration starts with the keyword map and an opening curly brace { . The code completion now offers map { as proposal.

Bug fixes

Excel adapter: Improved error message when Excel is busy

If Excel is busy, e.g., because a dialog is open or the user is editing a cell’s contents, YT cannot open Excel documents. In these cases, YT showed a general error message saying „make sure that Excel is installed.” We improved this message.

Text file adapter now takes Eclipse’s encoding settings into account

YT did open text files with Java’s default encoding. This has been adjusted; the text adapter now takes the Eclipse encoding preferences into account. This pertains to all levels, i.e., the global encoding settings as well as settings on project, folder, and file level.

Fixed wrong role labels in the YT link editor

For your convenience, YT Editor creates links even if artifacts are entered into the „wrong” sections. Imagine you have a link type specified from A (Requirement) to B (TestCase). In this case, YT creates the link even if the TestCase is added to the editor’s section A and the Requirement is added to section B.

However, if the link type had role labels configured and artifacts were entered into the „wrong” sections, the role labels were not added to the artifact sections correctly. This might have confused the user. Now the role labels have been removed from YT Editor completely.

C adapter: Fixed a performance leak regarding source files with lots of comments

Due to this bug in Eclipse’s C/C++ Development Tooling, YT checks comments for uniqueness. When doing these checks on a large number of files, a performance leak occurred. This leak has been closed now.

HM2 (1.1.1739)

New Text File adapter

We created a new Text File adapter. It replaces the existing one, which was rarely used.

The new adapter is able to recognize artifacts based on regular expressions and to a populate artifact attributes with the values of the groups defined in the corresponding regular expression.

„Drag and drop” support when linking into C/C++ source code

YT now supports drag and drop of artifacts (e.g., requirements) into source code. Dropping an artifact results in a comment storing the link information. This requires such links to be defined in the YT configuration.

Decoration of Matlab Simulink and Stateflows

When linking to Matlab Simulink or Stateflows, YT now „decorates” blocks or states with a YAKINDU icon if traceability links exist.

A click on the decoration offers a pop-up menu, providing support for the navigation to the linked artifacts. In other words: You can navigate, e.g., from a Simulink block to a linked requirement (let say, to DOORS) directly.

Selection propagation from/to Enterprise Architect in database mode

YT is able to read Enterprise Architect models stored in .eap files or in relational databases. In the latter case, the selection propagation between Enterprise Architect and YAKINDU Traceability has been implemented.

Exporting query results as CSV files

It is now possible to export query results not only to Excel files, but also in the CSV format.

Improvements of artifact search dialog

  • Hitting [Enter] when specifying a search term does no longer close the dialog. It simply has no effect.
  • The search terms entered by the user have always been interpreted as regular expressions, which in some cases produced unexpected results. Now, the user has the option of either using full text search (the default) or a search based on regular expressions.

The XML adapter is now able to populate artifacts with metadata

It is now not only possible to populate artifacts extracted from XML files with data read from XML, but also with metadata, such as the name of the XML file.

Better information when YAKINDU Traceability is inactive

The information about the status of an inactive YT has been improved. YT informs the user better if, e.g., a license is missing or no active configuration is set or if it is simply just starting up.

Improved performance when linking PTC Integrity artifacts

The performance of the „remote control” plug-ins for PTC Integrity, which ease the creation of links from/to PTC Integrity items, has been improved.

Bug fixes

DOORS adapter: Work-around closing DOORS accidently

In some cases, IBM DOORS decided to shut down if YAKINDU Traceability cut the connection to DOORS (e.g., because of a restart). The handling of such cases has been improved.

HM1 (1.1.1735)

More flexible attribute mapping for artifact types

It is now possible to apply string operations ( trim, substringBefore, substringAfter, match, replace) and regular expressions in the name and attribute mapping configuration of artifact types.

Enterprise Architect adapter supports EA models residing in MSSQL database

The EA adapter now is able to read models residing in MSSQL databases.

License management: Support of on-off switch

The YAKINDU license management now supports the (de-)activation of YAKINDU components by means of an on-off switch.

This makes it possible to deactivate YAKINDU Traceability in a running Eclipse instance in order to avoid occupancy of a floating license when you don’t need one.

Bug fixes

Query Language

  • The @join aggregate function is now more robust regarding null values.

  • A performance leak in function “Export query results to Excel” has been fixed.

G-Release (GM5 1.1.1734)

Snapshots and change reports

A snapshot is a „frozen copy” of the current state of your traceability data. As a new feature, YT supports

  • the creation of snapshots.
  • exploration of a the snapshot.
  • the creation of delta reports listing the differences of two snapshots or of a snapshot and the „current” state of your traceability data.

Read more details about snapshots of trace data in our blog in the YT help.

Improvement of the query language

We added several improvements to the query language:

  • We improved the usability of the edit proposals; they are now more helpful.
  • We added a new aggregate function @join which allows you to „flatten” lists
  • The export of query results to MS Excel adjusts the column size and adds and activates Excel’s auto filter by default.

For XML data sources, the DTD validation can now be deactivated by configuration

In cases where the DTD during the analysis of XML files is not available in the YT workspace, it is now possible to deactivate the DTD validation.

In the YT Configuration Editor, it is no longer possible to set a data access mapping with the mouse wheel

There where several cases when the data access mapping was changed unintentionally when turning the mouse wheel.
Therefore we ignore the mouse wheel in the context of the data access combo box.

Bug fixes

DOORS adapter: Fixed a bug in the evaluation of system attributes

When defining include .. if filters that use system attributes such as level or path , YT did in some cases not recognize all DOORS objects. This has been fixed.

CDT adapter supports hpp files

The CDT adapter now recognizes c, h, cpp and hpp files.

Query Language: Fixed a bug when evaluation null or empty values

In some cases, the query language did not evaluate empty or null values correctly.
We fixed this and improved the query functionality:

  • where(AttributeValue("<attribute_name>") == null) is true if the attribute is null
  • where(AttributeValue("<attribute_name>") == "") is true if the attribute is null or empty

GM3 (1.1.1726)

Enterprise Architect adapter supports EA models in Microsoft SQL

The Enterprise Architect (EA) adapter can now access EA models that are stored within Microsoft SQL repositories. It recognizes artifacts and links and can store external links as usual.

IBM DOORS data access is configurable in batch mode

It is now possible to select the IBM DOORS server that the DOORS adapter should use in batch mode on each invocation. The selection is done by providing the address of the DOORS database as an argument to the new -data command line parameter.

New simplified Tracing perspective for YT

This release introduces a new Eclipse perspective for YT, called Tracing. The Tracing perspective focuses on providing YT’s core functionality only. It omits UI elements for the configuration of adapters and also omits most of Eclipse’s general-purpose UI elements. This helps YT users without an Eclipse background and without being involved in creating or maintaining the YT configuration to use YT more efficiently.

The existing YT perspectives have been renamed as part of this change: The former YT Tracing perspective is now called Advanced tracing, while YT Analysis is now simply Analysis.

The new Tracing perspective is the default for new workspaces. However, this change is not applied to any existing workspaces.

Improved dialog for report creation

The report creation dialog has been improved on usability, e.g., it is now easier to remove parameters. Additionally, the visual appearance of coverage reports has been tweaked.

Xtext adapter supports grammar inheritance

The Xtext adapter has been extended such that it can be configured to recognize artifacts based on „inherited” grammar rules. If the grammar of the configured Xtext language includes another grammar by using the with keyword, the rules of this grammar can also be used for finding artifacts.

Additionally, the Xtext adapter now handles some corner cases more consistently.

Wizard for creating new YT configurations

A new wizard has been added to allow for easily creating new YT configurations. You can choose the name and the folder of the configuration file. The wizard can be opened via menu Traceability → Configuration → Add new configuration.

Improved Papyrus adapter

The improved adapter for Eclipse Papyrus supports navigation from YT to artifacts within Papyrus and vice versa.

GM2 (1.1.1722)

Improved performance of the CDT adapter with regards to large projects

YT does no longer rely on the CDT index when analyzing C/C++ files. This change carries the risk that the analysis of small C/C++ projects consumes a little bit of extra time, but it will decrease the time for larger C/C++ projects significantly.

Excel adapter can access template files

The Excel adapter is now able to access template files (filename extensions .xlt, .xltx, and .xltm).

PTC Integrity adapter with improved usability

We improved the usability of the PTC Integrity adapter in two aspects:

  • If the PTC-provided file mksapi.jar, which is necessary to connect to PTC Integrity, is not installed in YT, the user is now notified only once, and no longer obtrusively.
  • The representation of the document structure, i.e., the order of items, is now the same in YT as it is in PTC Integrity.

YT configuration editor with improved usability

We improved the usability of the configuration editor as follows:

  • When configuring the IBM DOORS data access, YT might request project information and baseline information from DOORS in order to provide smart proposals. The maximum waiting time for a response from DOORS has been changed from five minutes to five seconds, which is more suitable during configuration.
  • We added templates for the configuration of all adapters and we improved/overhauled existing templates.

YT editor improvements

  • For artifacts with a lot of attributes configured, the Artifact Search dialogue was slow when changing the layout of the results table (column order, column size). This has been improved.
  • The editor is now more strict when trying to edit a link to an artifact which was deleted after link creation: The deletion is possible, but the link cannot be adjusted.

Improved usability of YT TCP server preference setting

YT has a built-in TCP server to support remote procedure calls. The preference setting that is controlling whether the TCP server is enabled or disabled, is now labeled Enable instead of Not disable, which is easier to comprehend.

YT query language

We added means to close multiple query results tabs at the same time, so that you can easier control how many query results should be visible in parallel.

Bug fixes

IBM DOORS adapter honors Module.valueOf("AttributeName") within configuration of artifact names

Module.valueOf("AttributeName") expressions now not only work in the attribute mapping section, but also in the name section of a DOORS artifact type configuration.

IBM DOORS adapter: regression with undefined attribute value

We fixed a regression bug: The undefined attribute value configured in the IBM DOORS data access was not honored.

Microsoft Word adapter now supports selection propagation for large files

The selection propagation from YT to Microsoft Word did not work if YT was configured to recognize a large number of headings in a Word document. This has been fixed.

GM1 (1.1.1718)

It is now possible to configure a separator character when extracting multi-valued attributes (enumerations or external links) out of DOORS.

The data extract (a.k.a batch mode) logs result of the configuration consistency validation

In batch mode, any warning or error found by the configuration consistency validation is logged.
This will reveal, e.g., data access definitions with no matching resource found.

The Enterprise Architect adapter supports package names containing dots

When configuring the EA adapter, YT used the dot (.) as the separator character in package names. It was not possible to configure YT to focus on namespaces whose package names contained dots. (A dot is a valid character in EA package names.) Now YT uses the double colon (::) as a separator. The dot is still supported for backward compatibility.

Added noasadmin option to PTC Integrity adapter

Some commands that YT sends to PTC Integrity are only allowed when the PTC user has the view admin rights granted. As a workaround, PTC offers to set the noasAdmin option when invoking these commands. With this option set, PTC provides less details, but the information can still be sufficient for YT, based on the configuration. In YT, it is now possible to configure whether YT should set the noasadmin option when querying PTC Integrity.

XML adapter extended to support HTML

A data access for XML can now be configured to analyze HTML. Similar to XML, it creates a DOM tree under the hood, representing the HTML. Thus you can filter artifacts and map attributes similar to XML by means of XPath.

We overhauled the welcome page

The welcome page has been overhauled. We will continue to improve it. Feature requests are welcome!

Usability improvements

YT search dialog filters hide empty folders

When you entered a textual filter in the YT search dialog, YT did not hide any subtrees that were empty with regards to the filter. As an example, the dialog below does not show source code files which do not contain elements matching the search criteria.

The YT issue details dialog is no longer modal.

The dialog showing the details of an issue that was found during validation of your trace data is no longer modal.

Bug fixes

Fixed a bug regarding mnemonics for optional report parameters

For your convenience, YT populates the Create Report dialog with the parameters that you chose in the most recent report creation. We fixed a bug that prevented the Create Report dialog from opening when you did not populate optional parameters in the prior report creation.

F-Release (FM5 1.1.1715)

Update of license management

The YT licensing now supports LMX-based licenses which means that both file-based licenses and floating licenses are possible.

Please note that the established Flex licensing is still supported. However, a hybrid approach of Flex and LMX is not possible. The consequence affects customers who want to switch from Flex to LMX „now” in order to switch from file-based licenses to floating licenses „tomorrow”: As LMX does not honor existing Flex licenses, the latter have to be replaced/migrated. Please contact us in such cases.

Improvements of YT configuration editor

Live validation of configuration in mapping area

Live validation (i.e., validation during edit) of text in the mapping area for data access, artifact types and link types is now triggered more often (e.g., if one adds an attribute) so that the error markers are better up-to-date.

The deactivation of a data access doesn’t affect the dirty state of the configuration

If the YT configuration editor is open while YT deactivates a data access, e.g., due to some invalid configuration, the Active checkbox had been consequently unticked, which was interpreted as a configuration change. As a consequence, the editor suggested to save the configuration. This holds no longer true, such changes don’t require a save.

Better usability for quick fixes

It is now possible to navigate from the error details dialog to the quickfix menu directly.

Query-based attribute mapping notifies about runtime errors

If a query-based attribute mapping has been defined utilizing a query that does not provide artifacts that should be linked (e.g., it provided strings instead), YT reports an appropriate error message during runtime.

Attribute mapping now supports metadata

Similar to configuration means of link types mapped to the CDT adpater, it is now possible to consider metadata such as file name or identifier when defining attribute mappings.

Improvements of the DOORS adapter

Login to DOORS is cancelled on restart of YT

YT now stops the waiting for a DOORS login if restarted (and most likely starts a new wait process).

Offer means to waive the DOORS cache (always load DOORS data)

YT offers a preference to waive the DOORS cache. This may be suitable for smaller projects which therefore can be more up-to-date.

Excel data are updated on close of an Excel file

Until now, YT only updated data from Excel if the underlying Excel file had been saved. The following sequence led to wrong trace data:

  1. Open Excel.
  2. Create a link that is stored in Excel.
  3. Close Excel without saving.

Before the fix, the „reflection” of the link that had not been saved in Excel survived in YT’s trace data until the Excel file was reloaded. Now, the file is reloaded automatically.

Microsoft Word adapter is now more robust when reading large files

The Microsoft Word adapter ran into a timeout when reading large files. Now the timeout is ignored. However, the user has the chance to cancel the reading operation manually via the progress bar. Reading a Word document comprising 7,700 pages and two million words takes about three minutes.

Bug fixes

Fixed a bug with DOORS artifact types having more that one mapping configuration

With the preceding release, we introduced a regression affecting the assignment of DOORS attributes to artifacts if an artifact type had more than one mapping: The belonging of an artifact to a mapping was not calculated correctly. This regression had been fixed.

Removed redundancy of the adapter for files and folders (Eclipse Explorer)

The artifacts are shown in the search dialog hierarchically and less redundant.

FM3 (1.1.1709)

Added joins and set operations to YT query language

The query language now supports SQL-like joins and – for result sets with identical columns – the set operations union, reduce, and intersect.

// Example for join of Query_A and Query_B
query "some join query"	
	source (join(q('Query_A'), "joinColumnOfA", q('Query_B'), "joinColumnOfB"))
	.collect(left("someColumnOfA"), right("joinColumnOfB"), right("someColumnOfB"))
// Example for set operations reduceBy and union	
query "Passed SW-Integration-Tests"
	reduceBy(q('All SW-Integration-Tests'), 
		union(q('Failed SW-Integration-Tests'),q('Untested SW-Integration-Tests'))

Unified configuration of Model Viewer (Matlab-Simulink/Stateflow) adapter

The configuration for traceable artifacts of Matlab-Simulink (i.e., blocks) and Stateflow models (i.e., states and/or transitions) has been unified.

// Example mapping for blocks and states
include blocks  if(valueOf(path) contains "StatechartHierarchyOr/Chart2/") {
	name "B_" + valueOf(name)
	//  matlab_type is mapped only for blocks 
	map{ matlab_type to valueOf(type) }
include states if(valueOf(name) contains "State1" ) {
	name "S1_"+valueOf(name)
//  matlab_path is mapped both for blocks and states
map{ matlab_path to valueOf(path) }

Attribute mapping now supports recognition of regular expression matches, prefix and suffix

The flexibility of attribute mapping has been improved significantly. The mapping configuration now supports attribute evaluations based on regular expression groups and/or cutting out of prefixes and suffixes.

Here’s a „prefix” example:

where A. attribute.separatedBy("/").substringBefore(":") in [...]   
//In this case, an attribute value of „A:1/B:2/C:3” 
//will result in a list of 3 values [A, B, C] considered for attribute mapping.

For more details, refer to Attribute mapping documentation

Improvements to the DOORS adapter

Support of multiple projects

The DOORS data access now supports wildcards in the project names, i.e., it is possible to extract requirements and links out of a set of projects. Note that when using this feature, the specification of a baseline is not supported.

projects "/YT/*/IMPORTANT/*_PROJECT" 
undefined attribute value = "MY_UNDEFINED_VALUE"

YT is able to recognize DOORS projects and modules as traceable artifacts

With an artifact type being configured in a DOORS artifact type, YT is able to recognize DOORS projects and modules as traceable artifacts.

artifact type = Module 
include projects if(
 valueOf("Name") == "MY_PROJECT"
include modules if(
 valueOf("FullName") == "MY_NAME"
 valueOf("Created By") != "ME"

YT is able to extract external links out of DOORS

DOORS' external links can now be mapped to attributes of YT artifacts. YT extracts the entirety of external links – separated by comma – for the given requirements into one attribute.

map {
 EXTERNAL_LINKS to external links 

Added constraint: Only one DOORS data access can be activated at one point in time

YT facilitates direct navigation from C files to linked artifacts

YT can now directly navigate from the C editor to any linked artifacts, e.g., requirements in an external tool. When pressing the [Ctrl] in the C editor the link information turns into hyperlinks on mouse-over.

Improved usability of text filter in YT Explorer

When the user enters a regular expression as textual filter in the YT Explorer, YT now assumes the .* wildcard at both start and end of the regular expression entered by the user.

Improved performance of Excel adapter

We closed a performance leak that occured if a column with header was specified, but the specified header did not exist in the Excel sheet.

Improved recognition of XML artifacts

YT now honors the identified by part of the configuration of XML-based artifact types. In addition, the XML adapter is now more robust regarding document changes when recognizing XML nodes. The performance has been tweaked as well.

Improved coverage report

The built-in link type-based coverage report now contains bar charts and creation date.

YT Overview does no longer provide means to show the whole trace graph

The menu item View Context → All traces has been removed from the YT Overview. Even for small projects this functionality had been proven to be not adequate. As an alternative, you may utilize YT’s Graphviz export to see the whole graph. It can be triggered in the Traceability menu: Traceability → Export → Export Data.

YT data extract reports an error if any adapter gets disabled

In GUI mode, YT may disable adapters, e.g., due to faulty configurations. Even if one adapter is deactivated, other adapters remain active and provide traceable artifacts and links. During data extracts in batch mode, such a situation is now considered as global configuration error; the batch data extract returns an exit code signaling an error (i.e., != 0) in such cases.

Bug fixes

Fixed a bug when searching a non-existing column header in Microsoft Excel

When YT had been configured

  • to consider multiple Excel sheets in the same file and
  • at least one of these sheets did not contain the „header” that had been configured to identify traceable artifacts in YT

the Excel adapter ran into a bug and did not find any artifacts.

Now, the sheet without a matching header is ignored. Only matching artifacts from other sheets are recognized.

Fixed „select and reveal” when opening a Microsoft Word document

When the user triggered YT to show an artifact which had been extracted from Microsoft Word, YT opened the document, selected the given artifact, but did not scroll to the position of the artifact. Now, YT opens the document and selects and reveals the artifact in such cases.

Fix in Enterprise Architect adapter

When links were stored in Enterprise Architect, YT populated the link attributes only if they were fed from link end A. Now, YT considers both link ends.

FM2 (1.1.1705)

New – MS Word adapter recognizes „headings” as candidates

We extended the MS Word adapter to recognize headings as candidates. The configuration language now supports the „heading” keyword as in the example below.

locate heading where pattern matches ".*" {

This will find any heading as candidate that matches the regular expression „.*”. Find all details in the Microsoft Word – Artifact Type documentation.

New – quick fix remove all duplicate links at once.

A new quick fix was added to remove all duplicate links in one step. This means that all, but one link is removed. The user can not influence which link survives the clean up. „Read-only” links can not be deleted, therefore the result of the quick fix is one of the following:

  • YT will keep all „read-only” links.
  • YT will keep exactly one „editable” link.

Improvement – Error handling for the batch export.

When running the YT batch export application on a continues integration server, the job will now be marked as failure when an error occurs during YT execution.

Improvement – Name validation for configuration editor.

The configuration editor will now validate that there are no name clashes for data access and artifact types.

Improvement – Error handling for the batch export.

When running the YT batch export application on a continues integration server, the job will now be marked as failure when an error occurs during YT execution.

Improvement – Name validation for configuration editor.

The configuration editor will now validate that there are no name clashes for data access, artifact types, artifact categories, artifact attributes, link classification and link roles.

Improvement – Performance tweak for suspicious link validation.

We increased the performance of suspicious link validation for large link numbers.

Improvements of YT Issues

Improvement – YT Issues view allows limiting the number of displayed issues.

The YT Issues view now allows to limit the number of issues displayed to a user defined number.

Improvement – YT Issues view – YT Issues view allows filtering and grouping issues by type.

The YT Issues view now allows to filter and group the shown issues by type displayed.

Improvement – YT Issues view „Previous” and „Next” issue buttons behave more intuitive.

When opening the YT issues details view the „Previous” and „Next” issue buttons will jump to issues respecting the order of the issues list.

Improvement – Visual overhaul of YT Overview.

The artifact representations in the YT Overview are now drawn with a color gradient and will cast a shadow.

Bug fix – Overlapping artifact configuration cause bad performance of IBM Doors adapter

When configuring multiple artifact types that point to the same objects in Doors, under certain circumstances the Doors adapter did not fetch all relevant attributes in one swing. This results in poor performance since the adapter has to reload missing attributes lazily.

Bug fix – Wrong tool tips in YT Overview

The tool tip for the link direction evaluation switch now change their text based on the state of the switch.

Bug fix – Native YT data not correctly reloaded

Fixed an issue that prevents YT from recognizing changes in the native data storage outside YT. When the file changed outside YT, e.g., by the version control system YT will now reload the file correctly.

Bug fix – Column order and size lost after restart

The columns can now be reordered and resized. The changes will not be reset after closing the dialog or restarting YT.

Bug fix – The role label for artifacts in YT Editor were not updated correctly

Bug fix - „Active” indicator in the configuration editor did not reflect the correct state of artifact and link types.

The „active” check mark is now updated correctly for artifact and link types even when multiple mappings are defined.

FM1 (1.1.1701)

Improvements of XML adapter

We updated the XML and XPath framework which is used under the hood of YT. This does not only improve the performance of the XML adapter, it also faciliates the evaluation of substrings. Think of an XML such as

  <testcase id="12">
	  <Req data="id=r44,status=approved"/>
	  <Req data="id=r47,status=approved"/>

In this case, YT can extract the requirement IDs r44 and r47 based on a configuration similar to

 reqIDs to valueOf("Req/substring-before(substring-after(@data,'id='),',')")joined with separator ";"

Improvement of Enterprise Architect adapter

Link types mapped with the EA data access can now be configured to recognize an UML relation as a trace link in opposite direction.

Let’s say we have a dependency in UML from DesignDetail to Design (i.e., DesignDetail is dependent, Design is supplier). In this case, YT can be configured to recognize this relation as trace link from DesignDetail to Design or in opposite direction. Before, YT always recognized such relations as being directed from the owner to the related element (i.e., from DesignDetail to Design ). A link type configuration of

link source is B 

configures YT to recognize the relation in opposite direction.

Better error handling if DOORS cache is corrupt

When the DOORS cache was corrupt, you had either had to delete it manually from disk or by means of YT. The latter required entering a sequence of commands

  1. Deactivate data access "DOORS"
  2. Choose Update DOORS data
  3. Reactivate data access "DOORS"

We improved the usability in such cases by means of a notification dialog which encapsulates the above sequence.

Improvements of YT Overview

It is now possible to choose whether the graph in the YT Overview is calculated by evaluating links in direction „from A to B” or bidirectionally.

Improvements of YT Configuration Editor

  • We made the auto-completion in the mapping area for data access, artifact types and link types a little smarter: When entering strings, the recognition of the closing double quote has been improved so that the auto completion does no longer insert two double quotes at the end of Strings.
  • Issues that were found during the validation of configuration consistency are now not only listed in the YT Issues view, but also marked in the YT Configuration editor.

YT prevents evaluation or validation during data load

When triggering a validation or a report creation, YT notifies the user that the result of the current operation may be based in incomplete data and offers the choice to validate immediately or to wait until data are loaded completely.

Order of columns of Artifact Search Dialog can be adjusted by the user

You can now order columns or change the width of columns. The changes are specific for the chosen artifact type which means that you can define different layouts for different types. Once adjusted, the layout is stored as a preference on your disk so that your adjustments are applied valid if YT is closed and re-opened.

Query language supports AND and OR

The expressions in the where clause of the query language now support the combination of conditions by && (and), || (or) and () (brackets specifying precedence), e.g.

query "All Test Results with exactly three incoming links"
source (linkedArtifacts('Test Result'))
	.collect(Name as ArtifactName)
	.where(LinksAsB.size > 2 && LinksAsB.size < 4)

Bug fixes

Fix in YT Editor

We fixed a bug in the YT Editor regarding the labels of sections Artifact A and Artifact B:

In multiple types mode, i.e., when a section is populated with artifacts of more than one artifact type, the label does no longer append the role configured for one of the associated link types. Instead, it simply states multiple types.

Fix regarding YT Favorites view

We also now prevent the YT Favorites view from pushing to the front.

Before, the view was pushed to the front during startup of YT even if you put another view in front of the YT Favorites view within a prior session.

EM6 (1.1.1649)

The YT Explorer now supports multi-select and drag and drop

It is now possible to select multiple artifacts in the YT Explorer at once and to drag and drop the whole selection directly into the YT Editor. You may select ranges of artifacts (by means of the [SHIFT] key) or more distributed artifacts (by means of the [CTRL] key)

YT visualizes the attributes of artifacts in the YT Explorer

You may already know the hover showing the attributes of a trace artifact in the YT Overview. This has been applied to YT Explorer as well.

Bug fixes

DOORS adapter

We fixed several minor bugs regarding the connection of YT and DOORS, e.g., that the selection from DOORS to YT has not been propagated if DOORS had been closed and re-opened while YT was running. We also tweaked the generator that creates – based on the YT configuration – the DXL script which extracts the relevant data from DOORS. Time and memory consumption have been reduced by about five percent. Not that much; but it’s noticeable as YT is used in projects with more than 80,000 DOORS objects.

YT Editor

We fixed a bug in the YT Editor where the Set As A and Set As B buttons were sometimes deactivated for no reason.

EM5 (1.1.1647)

Creation of m:n links of different types

It is now possible to create a plurality of trace links in a single step. The YT Editor supports the creation of trace links for the cartesian product of artifacts in sections A and B – even for a combination of trace links of multiple link types.

As this method carries the risk of creating unintended links, it is guarded several times in YT.

  • First of all, the feature is disabled by default. Before first usage, it has to be activated manually in the YT preferences. (Window → Preferences → …)
  • Furthermore, YT requires a user confirmation if creating trace links of different types in a single step.

    This confirmation cannot be deactivated.
  • And of course, YAKINDU Traceability will never link artifacts without a valid link type definition provided by the YT Configuration.

The YT Configuration now supports attribute names with special characters

YT now supports attribute names with special characters for the definition of trace artifact types or trace links types. In the mapping definition, they have to be quoted.

EM4 (1.1.1643)

  • New features
    • The license management is now unified for all YAKINDU products. The YAKINDU license management supports file and floating licenses.
    • For CDT artifacts , it is now possible to configure which artifacts are relevant based on their type (e.g., YT should recognize only TranslationUnits). If no configuration is given, YT recognizes translation units, functions and function declarations.
    • YT visualizes the attributes of artifacts now in the properties view and in the YT Overview (in an hover).
    • It is now possible two create „m:n” links by means of the YT Editor. YT links the cartesian product of artifacts in sections A and B.
    • The coverage report is now better configurable: It is possible to add more than one link type and to choose whether unlinked Artifacts should be integrated in the report.
    • YT offers a validation that reveals duplicate links . As quick fix, the duplicate can be removed.
  • Improvements
    • YT does no longer trim the name of candidates.
    • When creating a new artifact type, YT now assigns colors with more contrast (rainbow color scheme).
    • MS Word Adapter
      • For configured regular expressions with more than one match, YT now creates one linkable artifact instead of ignoring duplicates completely.
      • Word does ignore matches of regular expressions in text sections that are marked as deleted.
    • The dialog showing suspicious link ends now uses a table and a diff viewer to show deltas in longer texts.
    • The YT Explorer view can be configured to also show unlinked artifacts.
  • Bug fixes
    • Fixed a resource leak (memory and performance) when quickfixing hundreds of suspicious Excel links at once.
    • The local cache for DOORS data had been deleted on any error during read (e.g., in case of an out-of-memory error). This has been fixed; YT deletes the cache only if it recognizes the file as corrupt.
    • The layout of tables in the YT Favorites view and in the YT Selection History was sometimes broken after YT restart. This has been fixed. YT also applies a smarter layout algorithm.
    • Sometimes, YT considered the local storage „” as read-only, when the file was empty and the first link had been saved.
    • Fixed a bug when editing an YT Configuration that is write protected. YT notifies the user and offers a „save as” option.
    • YT considers multiple mappings for the same DOORS artifact type correctly.

EM3 (1.1.1639)

  • New features
    • YT’s data management layer has been reworked completely. This affects mainly the mechanics and scheduling of how YT loads and updates data for the different data accesses, artifact types and link types. For example, YT now reloads links and artifacts automatically if a document changes. As a consequence, the buttons which triggered a reload of Excel, Enterprise Architect and attribute mapping links have been removed.
  • Improvements
    • Word adapter can be configured to use the font style as a filter, e.g., requirements will be recognized only if style is not strikethrough.
    • Excel adapter can use cell headers for artifact localization, e.g., locate cell where { … column with header „Requirement ID” }.
    • Better usabilty for context menu of YT Explorer. The /[Entf] button now deletes the link from the currently selected artifact to its parent.
    • Better user information if a search does not find any artifacts of a given type, e.g., because the data access had been disabled by the user.
  • Bug fixes
    • A potential inconsistency in the configuration of the Word adapter has been removed. The adapter does no longer accept more that one subset definition if locating bookmarks.

EM2 (1.1.1635)

  • Improvements
    • Word adapter supports these new features:
      • Finding headings as artifacts
      • Finding attributes in nearby cells, when the artifact is in a Table
      • More accurate results for *.doc files (Word 97-2003): special (hidden) characters are properly removed. Note that this may cause a version change for existing artifacts. This may affect attributes for artifacts located in tables, or containing special fields (such as references).
    • Usability of configuration editor has been improved.
      • Editing values requires a double-click instead of a single click.
      • It is now possible to delete table entries by hitting the /[Entf] key.
      • Better synchronization of editor content if the underlying file is updated.
    • YT Explorer
      • We added a new grouping. It is now possible to show the tree „in direction from A to B, but not from B to A” by means of Group by → Artifact Type (directed).

EM1 (1.1.1631)

  • Improvements
    • Mylyn artifact type: To be consitent with other adapters, keyword ‚valueOf’ is now mandatory
    • Data Extract: Improved the editor for mapping defintions from YT data to custom RDBMS schema
    • Several minor usabilty improvements (error messages, field labels, etc.)

DM4 (1.1.1627)

  • Improvements
    • YT Configuration editor has been redesigned
        • Improved usability
        • Better visualization of configuration items data access, artifact types, link types
        • A configuration can be activated directly from the editor
    • Excel adapter: Improved performance of link derivation
    • DOORS adapter: Better management of connection to DOORS
    • XML adapter
        • It’s now possible to read XML files in ZIP archives.
    • Adapter can now be configured to join attributes of multiple XML nodes into one single YT attribute
  • Bug fixes
    • DOORS adapter: Fixed a bug when querying a project baseline


  • New features
    • Added a new default report showing unlinked artifacts
  • Improvements
    • Better information message if user tries to copy ‚nothing’ into YT Editor
    • YT now supports custom queries in YT data extract
    • YT now remembers user’s adjustments to the size of the Artifact Search dialog
    • DOORS adapter:
      • Added code completion for data access configuration (values of project, baselineSet, baselineSetDefinition)
      • YT allows the configuration of default values if an attribute of a requirement does not exist in DOORS.
      • YT puts DOORS in foreground if a requirement is opened
    • Improved information message if user saves a YT configuration with errors.
    • Removed support for „unnamed” link attributes for EA and Excel links.
    • Configuration Editor: Added means to synchronize (i.e., update) declaration of attributes with attribute’s value assignments.
  • Bug fixes
    • C adapter does no longer mix files if more than one data access defined
    • Fixed a bug in Quickfix-Action „Delete all links” for missing artifacts
    • If a user fast deletes multiple artifacts from YT Editor, YT does not open these artifacts (fast clicks no longer perceived as double-click)
    • PTC Integrity adapter: data access no longer disabled if user installs the mksapi.jar
    • YT does no longer loose connection to DOORS if user refreshes DOORS data during load
    • Fixed a bug in dialog for Report Generation: YT „forgot” parameter values if a parameter had been selected and de-selected immediately.
    • YT now is robust regarding „links to self” if executing a query on the traceability graph.


  • Improvements
    • Several Usability improvements for the Favorites View and Selection History
    • Removed YT Observer functionality (outdated)
    • Add custom queries to YT batch data extract
    • The DOORS data load now honors user cancellation
    • Invasive Excel storage: YT always suffixes the link information with the separator symbol (i.e., Vertical bar a.k.a Pipe-Symbol)
  • Bug fixes
    • Refresh file after close in Excel does no longer block out YT
    • „All validations” now includes configuration consistency validation
    • Progress bar is shown when updating DOORS data
    • YT is now more robust regarding race conditions occurring if the Eclipse UI decides to decorate nodes in the YT Explorer during restart of YT
    • Fixed a bug when processing selection from Enterprise Architect. Updated user documentation as well.


  • Improvements
    • Reduced memory consumption when reading links stored in a plurality of files (which is the case, e.g., for Eclipse CDT)
    • Made „names” (i.e., YT the representation) of DOORS requirements configurable
  • Bug fixes
    • Enterprise Architect adapter can update also EA replica models


  • New features
    • Added Suspicious Validation for Excel and Enterprise Architect invasive storages
    • YT is able to store links in Enterprise Architect invasively
  • Improvements
    • Improved performance when reading data from DOORS
  • Bug fixes
    • Key-based link derivation for invasive storages and Attribute Mapping is more robust regarding missing keys
    • Re-enabled code completion during configuration of artifact types for PTC Integrity


  • New features
    • YT is able to store links in Excel invasively
    • YT is able to store links in Enterprise Architect invasively
  • Improvements
    • DOORS adapter: Query all data in one request instead of sending several smaller requests
    • Removed password protection from Configuration Editor
    • Improved Logging for several link types (Excel, Attribute Mapping, DOORS)
    • Improved capabilities to update data for dedicated data accesses (Excel, Attribute Mapping, DOORS, PCT Integrity) and YT as a whole
    • Improved performance for adding C artifacts to YT Editor
    • Smarter content assist for file resources
    • Excel artifacts: Mapping of attributes can now be defined based on column with header
    • YT Editor gives a warning if a user is about to create link duplicates
    • Suspicious Validation: Better performance when doing a quickfix for a plurality of issues
    • Bug fixes
    • Textual filter in YT Explorer now works also if grouped by link type
    • Attribute Mapping does no longer consider a match if attributes are missing on both sides


  • Improvements
    • Consolidated YT Configuration Editor: roles, classification and categories can be defined "in place"
    • Improved performance when deleting multiple links at once
    • DOORS adapter: Added performance logging
  • Bug fixes
    • If the active configuration is already opened in an editor, „Opening” the active configuration by means of menu does not open a second editor, but activate the one which is already open
    • Fixed a bug regarding User Interface blocks when editing two YT configurations in parallel
    • YT Reporting: Fixed a bug when appending new Excel-Sheets to xlsm files
    • Removed unnecessary restriction regarding artifact types that could by linked from CDT adapter


  • New features
    • link type for Enterprise Architect stores links as Requirements in EA
  • Improvements
    • DOORS adapter & Word adapter
      • the „version” of an Artifact in YT is computed by a snapshot of the attributes mapped the artifact type definition
    • CDT adapter
      • Fixed a bug when deleting multiple links within the same comment at once
    • PTC Integrity adapter
      • YT ensures that an artifact type definition for „PTC Integrity” must be mapped to a data access for "PTC Integrity"
  • Bug fixes
    • Closing YT does no longer cause a launch of the DOORS client
    • Fixed a bug regarding white spaces in the path to DOORS cache
    • Quick fixing a plurality of suspicious links at once works
    • CDT adapter filters duplicates of comments (this is a compensation for a bug in CDT)
    • When reading the currently selected requirement in DOORS, YT is no longer blocked by modal dialog in DOORS.
    • Fixed a bug in the evaluation of the configuration of Excel / Word adapters with more than one resource definitions


  • New features
    • Introduced Traceability menu
    • link type for Enterprise Architect derives links based on tagged values of EA Requirements
  • Improvements
    • DOORS adapter
      • Link recognition supports either Artifact A or Artifact B as „source” of a link
      • Improved representation of enumeration values in YT attributes (honors not only „string”, but also „value”)
    • CDT adapter
      • Improved performance for link derivation
      • Added expressive logging
  • Bug fixes
    • Report creation dialog recognizes templates in linked projects (i.e., projects not residing physically in workspace)
    • Removed duplicate initialization of DOORS Data access


  • Improvements
    • EA adapter retrieves Tagged Values as attributes of artifacts
    • Stronger validation for PTC adapter (only one data access is supported)
    • Improved performance when creating multiple links at once
  • Bug fixes
    • Fixed wrong assignment of stereotypes in graphviz export
    • Report creation now honors report parameters (they were ignored before)


  • Improvements
    • Improved usability of „Create Report” Dialog
  • Bug fixes
    • Fixed a bug regarding artifact recognition when copying artifacts from Excel to the YT Editor
    • DOORS adapter now considers only assigned (not all) data accesses during evaluation of baseline configuration
    • Fixed inconsistencies in YT Configuration Editor when creating new artifact and link types in one modification


  • Improvements
    • Suspicious Validation shows Attribute values ‚before’ and 'after'
    • Excel adapter: Provides access to Excel metadata such as ‚title’ or custom metadata attributes
    • CDT adapter: Improved performance for link evaluation
    • Improved progress bar messages when waiting for a DOORS login
    • Updated base technology EMF Compare from 3.0 to 3.1
  • Bug fixes
    • Fixed a bug which disabled quickfixes for Suspicious Validation
    • Search in YT Explorer now works when grouped by 'link type'
    • DOORS adapter: Fixed a bug affecting link recognition in baselines
    • Fixed inconsistencies in YT Configuration Editor when creating new artifact and link types in one transaction


  • New features
    • YT supports invasive linking to C-Artifacts (based on Eclipse CDT)
    • Introduced native DOORS adapter which reads requirements and links from IBM DOORS
  • Improvements
    • Rhapsody adapter: configuration language supports filters for relevant artifacts (e.g., Class, State, UseCase, …)
    • YT warns if a new report overrides an existing file
    • Improved two-way-compare of YT data files
    • YT Configuration Editor
      • Edit any configuration file (not only the active configuration)
      • Improved warnings on save of configuration
  • Bug fixes
    • Rhapsody adapter
      • Fixed bug in selection propagation from YT to Rhapsody
      • YT now traverses Rhapsody models which are spread over several modules correctly
    • YT Selection History: Icon for „Set As A” does no longer overlay the whole application
    • Attribute Mapping Storage: Fixed race conditions if several Attribute Mappings are configured at once


  • New features
    • Added means to cancel the load of PTC Integrity artifacts
    • As an option, a report now can be amended to an existing Excel file
    • Support of paste for a multiplicity of artifacts for MS Word and PTC Integrity
    • For Word artifacts, YT supports access to document’s metadata for attribute mappings
  • Improvements
    • YT Explorer
    • Improved rendering performance
    • Better support for textual filters containing a SPACE
    • Context-menu item „Delete All Links” is now inactive if links are read-only
    • Context-menu item „Specific Link Actions” contains also read-only links
    • Added sorting the the list of artifacts in the YT Editor
    • MS Excel adapter notifies the user if references to non-existing cells are specified
    • Better proposals for the configuration of the Enterprise Architect adapter
  • Bug fixes
    • YT Explorer now highlights a selected filter
    • YT Overview is now synchronized on "Delete All Links"
    • YT now handles operator „!=” (not equal) for PTC Integrity correctly
    • Attribute-mapping access: Fixed a bug in the recognition of artifacts with cardinality one-to-many


  • New features
    • Added Rhapsody 8 support
    • Added generic XML adapter
    • MS Word adapter supports regular expression
  • Improvements
    • Refactoring of internal data model to improve performance
    • PTC Integrity
      • A link type is no longer mandatory for a data access
      • introduces operators „contains” and „doesNotContain” in the artifact type configuration
      • Default fields summary and text used for labels can be changed by configuration
    • If not active, YT shows a status message in all views, instead of complaining about the status in a dialogue.
  • Bug fixes
    • Fixed several typos in User Guide, several amendments
    • Fixed an error in the Error Dialog
    • Avoid Exception in installation dialog of mksapi.jar
    • Corrected the completion proposal within YT Configuration Editor for MS Excel artifact types
    • Enabled deletion of trace links with inconsistent link types
    • A hidden or closed YT Overview does no longer complain about the fact that it cannot render
    • YT doesn’t try anymore to validate the connection to PTC Integrity if server and port are not yet specified
    • It is now possible to activate the password protection for a YT configuration that just had been saved.
    • YT does no longer notify the user that „searching for candidates is not supported” if the search revealed an error or if simply no artifacts had been found.


  • New features
    • Native Enterprise Architect Storage
    • Additional supported types for Rhapsody adapter
    • Non modal YT Search dialog for search artifacts by type
  • Improvements
    • Core
    • proper reporting if configured adapters aren’t installed
    • EA adapter
    • supports Enterprise Architect 10
    • filter/subset by namespace
    • Performance of Excel adapter in files with macros improved
    • Word adapter
    • Support for artifacts based on regular expressions
    • Existing configuration has to be changed (see Microsoft Word adapter for details).
  • Bug fixes
    • Hide artifact tab in properties view, if trace is selected
    • Subset evaluation consistently use ‚AND’ for different kinds and ‚OR’ for subset of the same kind
    • Errors during JAR installation (especially PTCs MKS-API)
    • avoid NPE during selections in Eclipse general 'Problems View'
    • Dependencies of UML2 adapter changed to complete UML2 editor
    • Fixed typos in User Guide


  • Improvements
    • ReqIF-Compare shows images embedded in XHtml
    • ReqIF-Editor shows progress monitor when opening larger files
    • YT Editor: Fixed bug regarding button state
    • EA adapter: Configuration honors UML meta-types and stereotypes
    • Added Welcome Screen
    • Improved performance in the UI (faster issue decorator)
    • Suspicious Validation does no longer cover derived links
    • Artop adapter honors subset namespace
  • Bug fixes
    • YT Editor: Fixed bug regarding button state
    • Excel adapter
    • YT does no longer prevent Excel’s save
    • Adapter does no longer create processes on non-Windows-OSs


  • New features
    • Suspicious Validation: Versioning of trace-links from and to ReqIF and Excel honors the mapped attributes of the trace type.
    • Excel adapter: Cells are referenced by value (i.e., a cell reference is still valid if for instance a prior row in Excel is deleted).
    • Jira adapter: Added more Jira-Attributes that one may address, esp. status
  • Improvements
    • ReqIF Editor
    • Editor can show deleted elements
    • Improved "Group by"
    • Improved Filtering
    • Improved XHTML display
    • Harmonized font types
    • YT Editor
    • Better user support in Link Edit mode
    • Buttons Search and Add won’t fade if editor’s display size shrinks
    • Suspicious Validation: Renamed menu item to Suspicious Links
    • Quick-Filter in YT Explorer shows used filter criteria
    • Improved synchronization of selection in YT Explorer and YT Overview
    • Improved usability of filter import
    • Improved performance of YT Explorer
    • A note within YT licenses is no longer mandatory
    • Licenses search covers union of licenses in user-home and/or installation directory
    • Splash Screen appears also on windows
    • Improved coupling with MS Word and Excel


  • Several improvements and bug fixes
  • Quick Search in Explorer
  • Search for Artifacts supports hierarchical presentation and artifact attributes
  • Integrity connection is more defensive to avoid wrong login attempts
  • Delete in context-menu
  • View contexts
  • Copy & Paste artifacts


  • Several improvements and bug fixes
  • Suspicious links
  • Trace data validations
  • New Tool adapter
    • Eclipse Browser
    • SQS Test
    • YAKINDU Simulink Viewer


  • Several improvements and bug fixes
  • Type filter for overview
  • Read only trace types
  • Tool adapter for MS Word
  • Tool adapter for MS Excel – Improvements
  • Tool adapter for AUTOSAR – Configuration
  • Tool adapter for IBM Rhapsody
  • Storage for PTC – PTC/MKS API installation support


  • Several improvements and bug fixes
  • Derived custom attributes that are only available for reporting
  • Quick fix to update invalid name and custom attributes of a trace point
  • Storage for PTC – Conditional mapping


  • Several improvements and bug fixes
  • License management
  • Improved filter options (contains, contains not and match by regular expression)
  • Tool adapter for Eclipse Explorer – Project Explorer, Package Explorer & Navigator can be used simultaneously
  • YT Explorer shows trace point type colors for trace points
  • Storage for Mylyn
  • ODA driver supports custom attributes fetching for trace point candidates
  • YT preferences can be imported/exported
  • File extension for trace configuration and trace data changed from „.xmi” to ".crema"
  • (Migration have to be done manually by renaming both files and replacing the textual occurrences in the <data>.xmi to <conf>.xmi by <conf>.crema)
  • Configurable coloring for trace point types which is visualized in the graphical overview view
  • Compare (diff/merge) support for trace data files
  • YT Editor can be synchronized with trace or trace point selection
  • YT Editor can edit trace points
  • YT Editor supports fast trace creation (automatic mode)
  • Custom attributes of traces and trace points can be edited in the Eclipse Properties view
  • ODA driver can fetch candidates
  • Storage for PTC – Initialization of PTC data runs asynchronous and provides better user feedback
  • Storage for PTC – Supports custom attributes mapping