Traceability for Hardware in the Loop Tests with Yakindu

Traceability with Yakindu

Many processes, especially for safety-critical systems, have high requirements for traceability of project information. YAKINDU Traceability offers an innovative approach for requirement traceability throughout the entire development process. Together with PROTOS miniHIL, this results in an end-to-end traceability solution for hardware in the loop testing.

Lernen Sie Yakindu Traceability kennen

Yakindu Traceability

YAKINDU Traceability offers a uniform requirement tracing for the entire development process. For example, system and stakeholder requirements can be easily linked to test cases, architecture elements or implementations. The different artifacts and tools are brought together in YAKINDU Traceability. A variety of tools are supported, such as requirement management (e.g. DOORS), modeling software (EA, Matlab), common programming languages (C/C++) as well as ticket systems (Bugzilla, JIRA) or office applications (Excel/Word) – a complete list can be found at YAKINDU Traceability adapters. Traceability plays an important role in the implementation of process and quality standards (YAKINDU Agility and Automotive SPICE).

Yakindu Traceability Projektübersicht

Yakindu Traceability for the miniHIL using the example of a MotorControl project.

The MotorControl project consists of the following documents and tools, which are merged in YAKINDU Traceability:

Impact Analyse mit Yakindu Traceability

Requirements – The requirements for the motor control are written in an Excel spreadsheet.

  • Software Architecture – The architecture of the System-under-Test (SUT) is defined using UML diagrams.
  • Implementation – The software implementation of the SUT is done in the C programming language.
  • Test Case – The test cases for the engine control system include module, integration and system tests. They are described in the CaGe test language and are executed on the miniHIL.
  • Test Suites – Test Suites aggregate Test Cases that logically belong together. They also serve as containers for generated combinatorial tests using CaGe.
  • Test Results – The results of test execution as XUnit reports.
  • Test Traces – The record of test execution for documentation and debugging as sequence diagrams.

A trace path can be displayed for each concrete document. For example, starting from a requirement, the associated architecture description, implementation or tests with results can be traced.

Impact Analyse mit Yakindu Traceability

The opposite direction enables an impact analysis. In this way, the affected requirements can be determined on the basis of failed tests. In addition, the link can be used to navigate immediately to the associated test definition, implementation or detailed test trace.

Protos Software Entwickler im Gespräch

Traceability for Hardware in the Loop Tests

The PROTOS miniHIL is a solution for early, lightweight hardware in the loop tests. Together with YAKINDU Traceability, these can be linked to requirement, specification, architecture or implementation. The result is an end-to-end traceability solution for hardware in the loop tests.

This can contribute decisively to quality assurance and process conformity in the development of embedded systems.

What are your traceability requirements?

By clicking send you accept our data protection agreement.