Analysis of Simulation Results
How can I find out if my tests are passed or failed?
Pass or fail isn't a single check — it's traffic rules, safety and quality-of-service, combined.
In traditional requirements-based testing, we typically check the I/O behavior of the system-under-test against expected values. Scenario-based testing of ADAS/AD applications requires a more sophisticated approach: monitoring the traffic situation and the system's behavior against traffic rules, safety requirements, or quality-of-service rules — for example a fuel-economy goal. Judging pass or fail means combining these rules to decide on safe and liable behavior.
Rule creation with Universal Pattern
To solve this, BTC Embedded Systems provides a dedicated graphical language for the intuitive specification of the needed rules. This formal language allows the automatic generation of corresponding observers, which are used to automatically analyze the simulation results.
Universal Pattern is an intuitive, easy-to-learn graphical language for creating and managing traffic rules and safety goals. Thanks to its machine-readable formal language, all rules can be used directly to automatically analyze every traffic scenario for potential rule violations.
Talk to our engineering team.
Tell us where your engineering problem actually is. We'll tell you whether an evaluation license, a workshop, or a conversation is the right next step.