We are constantly developing YAKINDU traceability. In each development cycle, new features are added, others are optimized, bugs are fixed. Once a month, we present our feature of the month here and in the blog.
Wouldn’t it be nice if your systems/software-development process was so matured that you want to re-apply it to future projects? Wouldn’t it be even better if your development tooling was matured in way that supports not only the re-use, but also specific adjustments (of tool-configurations, templates for artifacts etc.) so that you can re-apply the implementation of your process easily? Read more
A prominent task of YAKINDU Traceability for sure is to create traceability links. It already provides different means to do so. However, based on our users’ feedback, we got the impression that the existing means are not sufficient and do not fulfill all users’ needs. Thus, we started to develop a new concept to create links more quickly and easier than before, and we did so in strong cooperation with our users. This post will present the result – the new bulk link creation editor – as well as the way we got there. Read more
Do you want to establish (requirements) traceability to your custom scripts, text files and tools, e.g. link requirements residing in DOORS or Polarion to test cases defined in tools such as VectorCAST or maybe to a custom scripting language? In this post I want to illustrate how to achieve not only the linking in such a case, but also how easy it is to navigate such links and to create a coverage report based on those links. Read more