Proceedings of the 56th Annual Design Automation Conference 2019 2019
DOI: 10.1145/3316781.3317779
|View full text |Cite
|
Sign up to set email alerts
|

Assessing the Adherence of an Industrial Autonomous Driving Framework to ISO 26262 Software Guidelines

Abstract: The complexity and size of Autonomous Driving (AD) software are comparably higher than that of software implementing other (standard) functionalities in the car. To make things worse, a big fraction of AD software is not specifically designed for the automotive (or any other critical) domain, but the mainstream market. This brings uncertainty on to which extent AD software adheres to guidelines in safety standards. In this paper, we present our experience in applying ISO 26262-the applicable functional safety … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
23
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
6
3

Relationship

6
3

Authors

Journals

citations
Cited by 20 publications
(23 citation statements)
references
References 5 publications
0
23
0
Order By: Relevance
“…The input size of the first layer has been extended to hold the 64 × 64 × 3 color images of the GTSRB datasets. We have also started an activity to assess the performance of Posits using the Yolo (You Only Look Once) approach [60,61] and on Apollo [62] (http://apollo.auto/) heterogeneous framework and the results achieved confirm [33,34]) on famous datasets like CityScapes, see Figure 7. The results we are obtaining are in line with those obtained on, MNIST and fashion-MNIST and GTRS benchmark datasets.…”
Section: A Mnist Fashion-mnist and Cifar-10mentioning
confidence: 99%
“…The input size of the first layer has been extended to hold the 64 × 64 × 3 color images of the GTSRB datasets. We have also started an activity to assess the performance of Posits using the Yolo (You Only Look Once) approach [60,61] and on Apollo [62] (http://apollo.auto/) heterogeneous framework and the results achieved confirm [33,34]) on famous datasets like CityScapes, see Figure 7. The results we are obtaining are in line with those obtained on, MNIST and fashion-MNIST and GTRS benchmark datasets.…”
Section: A Mnist Fashion-mnist and Cifar-10mentioning
confidence: 99%
“…In order to analyze the impact of input data on timing variability, we focus on a controlled scenario in which we can reason on the variability caused by input data (both random and deterministic) and the platform related variability. Note that Apollo's modules have more than 130,000 lines of code, and 6,200 functions with intricate dependences and high cyclomatic complexity [55]. Furthermore, these functions are event-triggered by events arriving from the sensors at different frequencies.…”
Section: A Reasoning On Apollo's Variabilitymentioning
confidence: 99%
“…The effectiveness and scalability of traditional Verification and Validation (V&V) approaches are threatened by the complexity and unboundedness of the input and result spaces of functionalities such as perception and tracking [55,6]. The untenable number of potential inputs from the operational environment, and the non-deterministic nature of decision-making algorithms, complicate the definition of worst-case scenarios in both functional and non-functional dimensions [55]. As a result, it is hard to define budgets for software timing, relevant criteria for software timing V&V, and adequate testing methodologies.…”
Section: Introductionmentioning
confidence: 99%
“…The latter are covered, under the stringent time constraints of the automotive domain, by executing AD software on powerful hardware [6,7,11,18], e.g. high-end GPUs despite the existing challenges [8,16,24]. Naturally, these hardware devices consume significant amounts of energy, which recent studies show can reduce the driving range (i.e.…”
Section: Introductionmentioning
confidence: 99%