Have you ever wondered how to analyze traceability data comprising tens of thousands of requirements, test cases, software units, etc.? This video shows how coverage reports, impact analyses or other queries can be customized according to your needs.
This tutorial shows how to create your first (and your second and third) customized requirements coverage analysis. It is the second part of our video series introducing the YAKINDU Traceability query language.
Please notice: This is a german speaking webinar.
Especially in the development of safety-critical systems where standards and guidelines such as ISO 26262, Automotive SPICE, DO-178, IEC61508, IEC 62304 and EN 50128 require the collection of requirements traceability in order to demonstrate that critical requirements have been adequately implemented and validated, are making traceability highly relevant. Consistent traceability speeds up and improves development activities and helps to avoid programming errors. However, in today's development projects, capturing traceability information leads to high acquisition costs due to the sheer volume of requirements and the resulting design artifacts, source code, and test cases. The use of custom tools to create and manage requirements, software design, source code, or software testing often does not allow for cross-tool traceability. Not infrequently, complex analyzes are necessary because artefacts are not linked directly but indirectly via other artifacts.
In this webinar, we will tackle the biggest challenges with solutions and show a consistent traceability-implementation from requirement to model and source code to testing of individual modules.
Speakers are Ingo Nickles, Senior Field Application Engineer for Vector Software, and Boris Holzer, Requirements Engineer, Software Architect and technical project lead for YAKINDU Traceability for itemis.