Traceability for Polarion and source code

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 >

Weaving Testing into the Web of Traceability

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 >

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 >

IEC 61508: What does this standard mean for software development?

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 >

Effective traceability in inter-organizational projects

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 >

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 >

5 + 1 questions a requirements traceability matrix answers

In the previous part we had a short introduction to requirements traceability and took a look at how to create a requirements traceability matrix. Now it is time to see how we can harness the information it contains and use it to answer five important questions in day-to-day project work.  Read more >

How to convince customers of design decisions by the use of traceability

During the software development process various partial results are generated, but it is not always easy to maintain an overview of them. This is however essential for monitoring progress, analysis of the impact of changes and the justification of (design) decisions.  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 >


Popular posts