How can I create the needed millions of scenarios?
How can I avoid the test explosion problem?
How can I find out if my tests are passed or failed?
How can I create the needed millions of scenarios?
How can I avoid the test explosion problem?
How can I find out if my tests are passed or failed?
How can I find out if my tests are passed or failed?
In a traditional requirements-based testing, we typically check the I/O behavior of the SUT against expected values. In contrast to this, the scenario-based testing of ADAS/AD applications requires a more sophisticated approach to monitor the traffic situation and the SUT behavior regarding traffic rules, safety requirements or quality-of-service rules (for example a certain goal for fuel economy). Judging if a test is passed or failed requires to combine these rules together, for example, to decide safe and liable behavior.
To solve this, BTC provides a dedicated graphical language for an 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.
With Universal Pattern, we provide and intuitive and easy to learn graphical language for the creation and management of traffic rules and safety goals. Thanks to the machine readable formal language, all rules can be directly used to automatically analyze all your traffic scenarios for potential rule violations.
Taichi Ando
BTC Japan Co., Ltd.
[email protected]
Copyright © 2024 BTC Embedded Systems & BTC Japan