Traceability management is required in several industries, e.g., the automotive industry, to comply with legal requirements such as ISO 26262. Traceability deals with documenting the life of a requirement by creating bidirectional links between various associated artifacts, such as requirements, architectural components, source code, test cases, and test results. To benefit from the advantages of traceability it is necessary to be able to create traceability across all tools which are involved in the development process.
YAKINDU Traceability (YT) enables easy and well-arranged traceability management across all tools. It connects to the tools involved in the development process by means of custom tool adapters which are able to access the data-representing artifacts of the development process and related traceability information. These adapters do not only read or write data from those tools, they even support navigation across tools. As an example, by means of YT, an Autosar component designed in Enterprise Architect is only two clicks away from its specification in PTC Integrity (and vice versa).
YT offers several possibilities to evaluate the data gathered from connected tools and the link information stored in YT itself, e.g., in the form of a coverage report or a validation of the links.
As YT unifies access to development artifacts across the whole tool chain, it supports you in various use cases of your daily work:
YT combines several approaches to manage associations between development artifacts:
For those links whose lifecycle is managed by YT (i.e., neither derived nor adopted, but stored by YT), several YT functions ease link creation: YT recognizes selections in external tools and shows the selected artifacts in a selection history; it is possible to search for specific artifacts of different tools and you can store often-used artifacts in a favorites list and then re-use them for creating links.
For those links which are derived based on attributes, it is possible to create links by manipulating the original data in their specific tools. Imagine a test case in Excel with an identifier in one column and a concatenation of identifiers of related requirements in another column. If a so-called attribute mapping is configured, YT iterates over these columns and – if the attributes match – creates links between the test cases and the requirements, independent of the tool the requirements originate from. This means that you do not have to switch to YT to create any links, but instead you can work in, say, Excel and let YT derive the links automatically. The same is possible with the Eclipse CDT adapter.
As artifacts and circumstances can change during work, it is sometimes necessary to change existing links. YT allows you to
YT also provides you with different visualizations of existing links:
YT Explorer and YT Overview
As it is often necessary to edit some artifacts or to check for their correctness, YT offers you an easy way to navigate artifacts: In all views displaying artifacts, you can double click on an artifact to open and select it in its native tool.
Data often changes. Therefore, it is necessary to validate if they are still valid. In the context of traceability this means to validate if the links between changed artifacts are still valid. YT provides three validations to check the data validity:
As an addition, the configuration of the traceability project could have been changed. The configuration consistency validation detects potential errors and inconsistencies in the configuration of YT.
All three types of validations offer you various quick fixes that help you to re-establish the validity of the data.
In order to analyze the current traceability status, YT provides several different means.
The YT Dashboard displays a visualization of the current traceability status including the percentage of linked artifacts and existing traces between specific artifact types. This feature provides you with an up-to-date overview of your project. In addition to the pie chart visualization, it is possible to do a drill-down from the pie chart, i.e., if you select a pie section, a table containing the affected artifacts is shown.
YT also provides you with reporting functionality. By configuring individual report templates you can find answers to your own specific questions concerning the traceability data.
Sometimes it is necessary to create a snapshot of your current traceability model. For this purpose, you can extract the entirety of data visible to YT – the configuration, all artifacts, and all links – and export everything to external files. The first option is to export a model snapshot . Model snapshots cannot only be exported, they can also be imported back into YT, and they can even be compared among each other.
A second option is to export everything in the form of CSV files. As these CSV files are designed with referential integrity in mind, they can easily be imported into any RDMBS (Relational Database Management System) for further evaluations. CSV snapshots are „export only”; they are not intended to be read back into YT again.
Especially for visualization purposes, it is also possible to export a graph representing the configuration of YT or a graph representing all linked artifacts. This helps you for example to discuss configurations with colleagues or to get an overview on the whole traceability project.
As explained above, YT allows to access data from a multitude of tools via adapters.
In order to automatically perform certain tasks on a regular basis, e.g., creating reports etc., you can run YAKINDU Traceability in batch mode, which does not require any human interaction. This way, you can execute YT from a script or from a continuous integration (CI) server, like Jenkins.