The YT query-based data access derives links between artifacts based on queries of the YT query language.
Open the YT configuration with the YT configuration editor, and add a new data access as described in section "Data accesses". Select Query-based as data access type.
Within the configuration panel, no further configuration will be done. Instead, the link type provides means to define the query, see section Link type.
The example shows the definition of a query-based data access. Create a new data access, give it a name, and pick Query-based from the Type drop-down list. No further configuration is required.
YAKINDU Traceability can derive links based on the query language.
Please find below the required steps to specify such a derivation rule.
The configuration consists of a query. Usually queries will produce a table with multiple columns as output. In order to derive links and attributes from this table it is required to stick to certain conventions. The query result has to contain one column named ArtifactA and another column called ArtifactB. The values in these columns have to match those specified as Artifact Type A and Artifact Type B, respectively. You can specify additional columns for the query. If the link type defines a custom attribute with the same name as a column, the column’s value in the query result will be assigned to this attribute for the created link.
The example shows the definition of a query-based link type between EA Operation and TestCases (Excel). The links are inferred by the query that is defined in the mapping section. The query will collect traces from EA Operation to TestCases (Excel). Queries output a table. In order to use a query for link inference it is required to have columns named ArtifactA and ArtifactB as shown in the collect clause.
Links of this link type will never become suspicious.