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.
A systems engineering project comprises tens or even hundreds of thousands of development artifacts, be it stakeholder requirements, elements of the system architecture, software units, test cases etc. Read more
Tracking changes and impact analysis is a common task in the field of requirements traceability. It helps you e.g. to find out which requirements changed in a given period of time, it identifies the particular changes and their impact. Read more
This post is about how a simple toggle button might resolve a philosophical conflict. The conflict arises from the following question: "How many directions does a trace link have?". Pop quiz! Read more
Many tools support requirements traceability in one or the other way – may it be... Read more
In April, we improved our Matlab adapter of YAKINDU Traceability (YT). The adapter recognizes Matlab Simulink Blocks as well as Matlab Stateflow States and Transitions. Based on this artifact recognition, YT provides traceability for these artifacts, e.g. between Matlab Simulink Blocks and DOORS requirements or between Matlab Stateflow States and Software Units or various test specifications. Read more
In the last month, our team behind YAKINDU Traceability received a couple of questions regarding how to establish bidirectional traceability between requirements or design elements and software units a.k.a source code – as for example required in the Automotive Spice model. We also optimized the performance of our C/C++ adapter and therefore decided that it qualifies to be called “feature of the month”. Read more