Boris Holzer

I've been working as (technical) project manager in several business domains. I like the power of language engineering and every other application that makes development easier and improves quality. Since 2014, I'm in charge of YAKINDU Traceability.
Boris Holzer

Recent Posts

Traceability – A generic way to link requirements and test cases

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 >

Automated Traceability Link Derivation and Maintenance

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 >

Snapshots and change reports for requirements traceability data

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 >

About bidirectional traceability, link semantics and a toggle button

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 >

A language to analyse trace data efficiently

Many tools support requirements traceability in one or the other way – may it be... Read more >

Über die Terminologie von Scrum

Kein Zweifel: Das Konzept von Scrum bringt tolle Ideen und Ansätze mit sich – und nicht nur das: In der Regel ist es auch auf den Prozess der Produktentwicklung übertragbar.  Weiterlesen >

What is requirements coverage and how can it be analyzed?

If you are dealing with the term requirements coverage in the context of systems or software development you might discover the following ambivalence: Read more >

Traceability for Matlab Simulink and Matlab Stateflow

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 >

Tracing requirements and source code

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 >

Verlinkung von Anforderungen im Quellcode

Im letzten Monat gab es einige Anfragen an das YAKINDU Traceability-Team speziell zur Verlinkung von Anforderungen und/oder Design-Elementen in den Quellcode, wie sie etwa im Automotive Spice gefordert wird – und stellen dieses "Feature des Monats" in diesem Artikel vor. Zudem haben wir im aktuellen Release nochmal an der Performance-Schraube speziell für die Verlinkung in den Quellcode gedreht. Weiterlesen >


Popular posts