Boris Holzer is site manager of itemis in Lünen and product manager for YAKINDU Traceability. He is committed to the continuous improvement of both the developed software and the development process.
Applying standard compliant traceability to your projects is quite a challenge. YAKINDU Traceability helps you to achieve and prove compliance. Furthermore it provides benefits such as easy analysis and project overview capabilities.
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 ...
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 ...
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.
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.
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!