The Release of Autonomous Vehicles

Wachenfeld, Walther; Winner, Hermann

doi:10.1007/978-3-662-48847-8_21

Cited by 127 publications

(115 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Hence, the scenarios have to be derived and documented systematically. In addition, 1 Authors are with the Institute of Control Engineering, Technische Universität Braunschweig, 38106 Braunschweig, Germany menzel, bagschik, maurer @ifr.ing.tu-bs.de 2 Authors wrote their master theses at the Institute of Control Engineering, Technische Universität Braunschweig, 38106 Braunschweig, Germany l.isensee, a.schomburg @tu-braunschweig.de they have to be traceable along the development process. For this purpose, Menzel et al [3] propose three levels of abstraction for scenario representation: functional scenarios, logical scenarios and concrete scenarios.…”

Section: Introductionmentioning

confidence: 99%

From Functional to Logical Scenarios: Detailing a Keyword-Based Scenario Description for Execution in a Simulation Environment

Menzel

Bagschik

Isensee

et al. 2019

2019 IEEE Intelligent Vehicles Symposium (IV)

View full text Add to dashboard Cite

Scenario-based development and test processes are a promising approach for verifying and validating automated driving functions. For this purpose, scenarios have to be generated during the development process in a traceable manner. In early development stages, the operating scenarios of the item to be developed are usually described in an abstract, linguistic way. Within the scope of a simulation-assisted test process, these linguistically described scenarios have to be transformed into a state space representation and converted into data formats which can be used with the respective simulation environment. Currently, this step of detailing scenarios takes a considerable manual effort. Furthermore, a standardized interpretation of the linguistically described scenarios and a consistent transformation into the data formats are not guaranteed due to multiple authors as well as many constraints between the scenario parameters. In this paper, the authors present an approach to automatically detail a keyword-based scenario description for execution in a simulation environment and provide a basis for test case generation. As a first step, the keyword-based description is transformed into a parameter space representation. At the same time, constraints regarding the selection and combination of parameter values are documented for the following process steps (e. g. evolutionary or stochastic test methods). As a second step, the parameter space representation is converted into data formats required by the simulation environment. As an example, the authors use scenarios on German freeways and convert them into the data formats OpenDRIVE (description of the road) and OpenSCENARIO (description of traffic participants and environmental conditions) for execution in the simulation environment Virtual Test Drive.

show abstract

Section: Introductionmentioning

confidence: 99%

From Functional to Logical Scenarios: Detailing a Keyword-Based Scenario Description for Execution in a Simulation Environment

Menzel

Bagschik

Isensee

et al. 2019

2019 IEEE Intelligent Vehicles Symposium (IV)

View full text Add to dashboard Cite

show abstract

“…Furthermore, test-driven approaches will gain importance, requiring to start testing at the beginning of the life cycle. This supports efficient processes, in which one get maximum amount of [12], [13], [15] Test automation [9], [10], [15], [17] Standards and certification [8], [10], [13] Communication (e.g., V2I)…”

Section: Results: Challenges Of Testing Automated Vehicles a Idenmentioning

confidence: 80%

Paving the roadway for safety of automated vehicles: An empirical study on testing challenges

Knauss

Schröder

Berger

et al. 2017

2017 IEEE Intelligent Vehicles Symposium (IV)

View full text Add to dashboard Cite

Abstract-The technology in the area of automated vehicles is gaining speed and promises many advantages. However, with the recent introduction of conditionally automated driving, we have also seen accidents. Test protocols for both, conditionally automated (e.g., on highways) and automated vehicles do not exist yet and leave researchers and practitioners with different challenges. For instance, current test procedures do not suffice for fully automated vehicles, which are supposed to be completely in charge for the driving task and have no driver as a back up. This paper presents current challenges of testing the functionality and safety of automated vehicles derived from conducting focus groups and interviews with 26 participants from five countries having a background related to testing automotive safety-related topics. We provide an overview of the state-of-practice of testing active safety features as well as challenges that needs to be addressed in the future to ensure safety for automated vehicles. The major challenges identified through the interviews and focus groups, enriched by literature on this topic are related to 1) virtual testing and simulation, 2) safety, reliability, and quality, 3) sensors and sensor models, 4) required scenario complexity and amount of test cases, and 5) handover of responsibility between the driver and the vehicle.

show abstract

“…For driver assistance systems, this proof is furnished by driving many test kilometers on test grounds and public roads. However, for higher levels of automation a distance-based validation is not an economically acceptable solution [4].…”

Section: Introductionmentioning

confidence: 99%

Scenarios for Development, Test and Validation of Automated Vehicles

Menzel

Bagschik

Maurer

2018

2018 IEEE Intelligent Vehicles Symposium (IV)

326

188

View full text Add to dashboard Cite

The latest version of the ISO 26262 standard from 2016 represents the state of the art for a safety-guided development of safety-critical electric/electronic vehicle systems. These vehicle systems include advanced driver assistance systems and vehicle guidance systems. The development process proposed in the ISO 26262 standard is based upon multiple V-models, and defines activities and work products for each process step. In many of these process steps, scenario based approaches can be applied to achieve the defined work products for the development of automated driving functions. To accomplish the work products of different process steps, scenarios have to focus on various aspects like a human understandable notation or a description via state variables. This leads to contradictory requirements regarding the level of detail and way of notation for the representation of scenarios. In this paper, the authors discuss requirements for the representation of scenarios in different process steps defined by the ISO 26262 standard, propose a consistent terminology based on prior publications for the identified levels of abstraction, and demonstrate how scenarios can be systematically evolved along the phases of the development process outlined in the ISO 26262 standard.

show abstract

The Release of Autonomous Vehicles

Cited by 127 publications

References 10 publications

From Functional to Logical Scenarios: Detailing a Keyword-Based Scenario Description for Execution in a Simulation Environment

From Functional to Logical Scenarios: Detailing a Keyword-Based Scenario Description for Execution in a Simulation Environment

Paving the roadway for safety of automated vehicles: An empirical study on testing challenges

Scenarios for Development, Test and Validation of Automated Vehicles

Contact Info

Product

Resources

About