Overview of the „YT Analysis” perspective

This section gives an overview of the YT Analysis perspective. You will find more detailed information in subsequent sections.

General project metrics: the dashboard

The dashboard provides answers to typical questions in traceability projects. For answers to not-so-typical questions, please see the section on customized queries.

  • Which kinds of trace links do we have and how many of each?
  • What are the artifacts we have and how many of each type?
  • Which of our artifacts have trace links to other artifacts, in total as well as broken down by artifact type?
  • Which of our artifacts do not have trace links to other artifacts, in total as well as broken down by artifact type?

Read an introduction on requirements coverage and what YAKINDU Traceability can do for you in this regard in the blog posts "What is requirements coverage and how can it be analyzed?" and "How to analyse your project status with YAKINDU Traceability".

Figure "The YT Analysis perspective; using the dashboard" exemplifies how this can look like:

  • The YT Dashboard view (top-left) displays a breakdown of the linked artifacts, including their numbers. Each pie chart section represents a different artifact type.
  • Selecting one or more pie chart sections makes them explode and displays their contents (here: artifacts) in the YT Dashboard Details view (bottom-left).
  • Selecting an artifact in YT Dashboard Details displays its properties in the Properties view (bottom-left) and its relationships to other artifacts in the YT Overview view (top-right).

The "YT Analysis" perspective; using the dashboard

The YT Analysis perspective; using the dashboard

Section "The YT Dashboard view" has more details on using the dashboard.

Writing and running customized queries

While the dashboard application answers common questions, it does not cover any specific needs of your particular project. However, this can be addressed with customized queries. Figure "Writing and running queries in the YT Analysis perspective" shows an example:

  • Hand-crafted queries in the YT query language have been established in a .query file (right). In this example, the idea is to trace stakeholder requirements to the results of software qualification tests, but only to those tests that have been executed successfully.
  • The YT Queries view (top left) shows a tree view of query files (here: only one) and the queries therein.
  • Double-clicking on a query executes it. Results are shown in the YT Query Results view (bottom left).

Writing and running queries in the "YT Analysis" perspective

Writing and running queries in the YT Analysis perspective

Section "The YT Queries view and the YT Queries results view" has more details on working with customized queries.