View source for Robert bosch gmbh (20240193071). COMPUTER-IMPLEMENTED METHOD AND SYSTEM FOR GENERATING TEST DATA FOR COMPUTER-IMPLEMENTED AUTOMATED DRIVING FUNCTIONS simplified abstract

=COMPUTER-IMPLEMENTED METHOD AND SYSTEM FOR GENERATING TEST DATA FOR COMPUTER-IMPLEMENTED AUTOMATED DRIVING FUNCTIONS=


==Organization Name==

[[:Category:robert bosch gmbh|robert bosch gmbh]]


[[Category:robert bosch gmbh]]

==Inventor(s)==

[[:Category:Lukas Koenig of Grossbottwar (DE)|Lukas Koenig of Grossbottwar (DE)]][[Category:Lukas Koenig of Grossbottwar (DE)]]

[[:Category:Michael Messer of Adolzfurt (DE)|Michael Messer of Adolzfurt (DE)]][[Category:Michael Messer of Adolzfurt (DE)]]

[[:Category:Michael Hanselmann of Korntal-Muenchingen (DE)|Michael Hanselmann of Korntal-Muenchingen (DE)]][[Category:Michael Hanselmann of Korntal-Muenchingen (DE)]]

==COMPUTER-IMPLEMENTED METHOD AND SYSTEM FOR GENERATING TEST DATA FOR COMPUTER-IMPLEMENTED AUTOMATED DRIVING FUNCTIONS - A simplified explanation of the abstract==


This abstract first appeared for US patent application 20240193071 titled 'COMPUTER-IMPLEMENTED METHOD AND SYSTEM FOR GENERATING TEST DATA FOR COMPUTER-IMPLEMENTED AUTOMATED DRIVING FUNCTIONS

'''Simplified Explanation''': 

This patent application describes a computer-implemented method for generating test data for automated driving functions. The method involves using a model checker to analyze a software component's compliance with specified formal requirements and generating test data based on edge case parameters if non-compliance is detected.

* '''Key Features and Innovation''':
  * Provision of a computer-implemented automated driving function as a software component.
  * Specification of an environment model with boundary conditions to limit the state space of the software component.
  * Utilization of a model checker representation of the software component constrained by the environment model.
  * Application of a model checking method to analyze compliance with formal requirements and generate test data based on edge case parameters.

'''Potential Applications''':
This technology can be applied in the development and testing of computer-implemented automated driving functions to ensure compliance with formal requirements and improve overall safety and reliability.

'''Problems Solved''':
This technology addresses the need for efficient generation of test data for automated driving functions and the identification of edge case parameters that contribute to non-compliance with formal requirements.

'''Benefits''':
The benefits of this technology include improved testing accuracy, enhanced safety of automated driving functions, and increased reliability of software components.

'''Commercial Applications''':
Potential commercial applications of this technology include software development for autonomous vehicles, testing of automated driving systems, and quality assurance in the automotive industry.

'''Prior Art''':
Readers interested in prior art related to this technology could explore research on model checking methods, software testing for autonomous vehicles, and formal verification techniques in the automotive industry.

'''Frequently Updated Research''':
Stay updated on the latest advancements in model checking methods, software testing for automated driving functions, and formal verification techniques in the automotive industry.

'''Questions about Automated Driving Test Data Generation''':
1. What are the key components of the computer-implemented method for generating test data for automated driving functions?
2. How does the model checking method contribute to improving the compliance of software components with formal requirements in automated driving systems?


==Original Abstract Submitted==

a computer-implemented method for generating test data for computer-implemented automated driving functions. the method includes: provision of a computer-implemented automated driving function in the form of a software component; specification of an environment model with boundary conditions that limit the state space of the software component; provision of a model checker representation of the software component that is limited by the environment model; specification of a formal requirement as an input for a model checking method; and application of the model checking method to the model checker representation to analyze the software component with respect to compliance with the specified formal requirement. if the specified formal requirement is not complied with, the model checking method provides the states and state transitions of the software component that contribute to non-compliance as edge case parameters. based on the edge case parameters, test data are then generated.



[[Category:G06F11/36]]
[[Category:CPC_G06F11/3608]]