In the TwinSpace project, our Software Twins stand out as powerful tools. These extra-functional counterparts are more than just mock-ups—they enable seamless integration of new software components without prematurely revealing or exposing them. This is particularly valuable during early development stages when confidentiality and flexibility are essential.

However, the effectiveness of these Software Twins relies on one crucial principle: measurability and equivalence. For a Software Twin to serve its purpose, it must faithfully mirror the behavior of the original system. That means we must be able to measure, compare, and annotate the original system to its twin in detail. Only then can we verify that they behave identically under the same conditions.

Ensuring such equivalence is not trivial. While it may seem straightforward to compare timing of instructions, memory access patterns, and task scheduling, doing so accurately is far from straightforward. In many cases, traditional measurement techniques involve inserting additional code or instrumentation, which can ironically distort the very timings you’re trying to observe. These “observer effects” introduce inaccuracies, making precise comparison difficult or even infeasible.

This is where the Virtual Prototype Frameworks developed by the University of Lübeck offer a significant advantage: These are not physical boards but software-based prototyping environments that replicate the functionality of actual hardware. Virtual Prototypes provide an advanced platform for debugging, tracing, collecting extra-functional properties and seamless hardware-software integration—all within a digital space. In essence, these Virtual Prototypes act as digital twins of physical hardware, complementing our Software Twins. Together, these Hardware Twins form the second foundational axis of our Twin Space.

One of their standout capabilities is precise, non-intrusive timing measurement. Because everything is simulated in software, you gain access to internal signals and event timelines without effecting the behavior of the system. This enables developers to analyze performance, verify real-time constraints, and simply test without available hardware. In addition, it helps us verify the Software Twins ensuring synchronization between the original and the twin down to the instruction level—all without the risk of interference from measurement tools.

In short, Virtual Prototypes bring together the best of both worlds: the flexibility and safety of virtualisation with the accuracy and depth of real-world prototypes. When used in tandem with Software Twins in TwinSpace, they form a powerful foundation for next-generation of automotive software integration—one that emphasizes transparency, accuracy, and integration without compromise. This makes TwinSpace an important driver for a successful Software Defined Vehicle.