In order to support re-use and adjustment of YAKINDU Traceability configurations, we developed a new feature called parameterized configuration – our feature of the month for July 2018.
In this post I want to illustrate how to achieve not only the linking of requirements to your custom scripts, text files and tools, but also how easy it is to navigate such links and to create a coverage report.
You want to maintain your traceability data efficiently? Nothing easier than that with YAKINDU Traceability.
Learn everything about how YAKINDU Traceability supports the task of tracking changes and impact analysis by means of our newly introduced snapshot feature.
Bidirectional traceability means that a trace link has two directions, right? Let's take a look at that.
There's something new with YAKINDU Traceability! We've just integrated the query language so it’s definitely the feature of the month May ‘17.
Warum ein Sprint im Scrum nichts mit einem Wettrennen zu tun haben sollte: Boris Holzer nimmt sich im Blog die Terminologie von Scrum zur Brust.
If you're dealing with the term requirements coverage you might know that there's no generally accepted definition. Boris Holzer knows how to measure it anyway.
Our feature of the month in April: Integration of Matlab Simulink and Matlab Stateflow in YAKINDU Traceability.
With YAKINDU Traceability you can create bidirectional trace links from source code artifacts to requirements – our feature of the month March!
itemis AGAm Brambusch 15Lünen NRW email@example.com