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 >

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 >

Structuring your statecharts with subdiagrams

Composite states are a good means to bring order and structure to a statechart. However, as a statechart grows, it may easily become too big to give a comprehensive overview of the whole model anymore. Let's have a look at how subdiagrams can help you out. Read more >

Style your statecharts with YAKINDU Statechart Tools

Did you know you can style your statecharts with YAKINDU Statechart Tools? For example, it might be useful to highlight certain states by color – especially when dealing with large state machines. You can group states by color and point out semantics by coloring states. Or maybe you want to mark statecharts that need to be reworked by color. Therefore it's our "feature of the month". 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 >

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 >

Refactor your statechart models

YAKINDU Statechart Tools has a lot of useful features. In this series we present the "feature of the month" that will help you domesticating your maybe exceeding statechart models. 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 >


Popular posts