A previous post outlined an example project and a set of key metrics (KPIs) that I want to be able to calculate based on information gathered from multiple different development tools. In this follow up post, I will illustrate how to calculate one of those metrics using traceability information and an example query over the trace graph. Read more >

A manager of a single project, working closely with a small team on a daily basis, can fairly easily know the status of the project. However, a manager of several projects, maybe a department manager, manager of a large branch of a company, or even the manager of a company, will find it harder to have a personal feel for the status of the project he/she is responsible for, and will rely on information provided by other people and other sources. 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 >

In the development of safety-critical systems it is essential to prove that the developed product fullfills all requirements (including system requirements, safety requirements and security requirements) to ensure the correct functionality and to prove that engineering is up to the state-of-the-art for legal reasons. Read more >

The Polarion adapter of YAKINDU Traceability provides traceability for Polarion work items. Work items are not restricted to source code only, they can rather also be any other development artifact type, for example test cases in an external tool. YAKINDU Traceability can also recognize links existing within Polarion between Polarion work items. As part of the latest release, we based the Polarion adapter on a new technical foundation.  Read more >

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 >

For more and more systems, functional safety requirements must be met. For software development, the fulfillment of IEC 61508 "Functional safety of safety-related electronic / electronic / programmable electronic systems" is to be demonstrated – especially in the automotive sector. Read more >

Software and systems traceability has long been recognized as critical elements of rigorous software systems developments. Recent studies deliver evidence that this long-term perception in fact is true.  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 >