Automotive virtual integration platforms: why's, what's, and how's

Giusto, Paolo; Ferrari, Alberto; Lavagno, Luciano; Brunel, Julien; Fourgeau, Eliane; Sangiovanni‐Vincentelli, Alberto

doi:10.1109/iccd.2002.1106796

Cited by 22 publications

(11 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For that purpose, many standards were agreed on to enforce guidelines during the design, development, and testing phases of the software and hardware architectures of an automotive system [12].…”

Section: Problem Statementmentioning

confidence: 99%

Functional design and verification of automotive embedded software: An integrated system verification flow

Shedeed

Bahig

El-Kharashi

et al. 2013

2013 Saudi International Electronics, Communications and Photonics Conference

View full text Add to dashboard Cite

Automotive systems are diverse, extensively interactive, and multi-disciplinary by nature. We propose a flow that integrates the different environments and tools needed for modeling and simulation of sub-components at each abstraction level, namely, Model in the Loop, Model-to-Software in the Loop, Software in the Loop, and Hardware in the Loop. The proposed flow verifies the system at each of these abstraction levels in the automotive domain. We present a systematic methodology and verification flow for a detailed migration procedure between these different abstraction levels to fulfill complicated automotive system requirements. Our flow has been tested using a brake-bywire anti-locking car system use case. Experimental results show the efficiency of the proposed flow in discovering early incorrect system behavior at each abstraction level. A common graphical test design and generation tool complements the proposed flow at each level to ensure that the generated tests address the same system functionality at each abstraction level and optimizes the cost of test design and generation. Keywords-Anti-lock Braking System (ABS), AutomotiveSoftware Component (SWC), AUTOSAR, Brake-by-Wire (BBW) brakes, Electronic Control Unit (ECU), Hardware in the Loop (HiL), Model in the Loop (MiL), Model-to-Software in the Loop (MiL-to-SiL), Software in the Loop (SiL).

show abstract

Section: Problem Statementmentioning

confidence: 99%

Functional design and verification of automotive embedded software: An integrated system verification flow

Shedeed

Bahig

El-Kharashi

et al. 2013

2013 Saudi International Electronics, Communications and Photonics Conference

View full text Add to dashboard Cite

show abstract

“…In general, one demands a level of safety that is higher or equal to the level of safety of the systems that are replaced. In these ultra-dependable applications, a maximum failure rate of 10 −9 critical failures per hour is demanded [1][p. 10]. This can only be achieved by utilizing fault-tolerant strategies that enable the continued operation of the system in the presence of component failures [2].…”

Section: Introductionmentioning

confidence: 99%

The Fault Assumptions in Distributed Integrated Architectures

Obermaisser¹,

Peti²

2007

SAE Technical Paper Series

View full text Add to dashboard Cite

Distributed integrated architectures in the automotive and avionic domain result in hardware cost reduction, dependability improvements, and improved coordination between application subsystems compared to federated systems. In order to support safety-critical application subsystems, a distributed integrated architecture needs to support fault-tolerance strategies that enable the continued operation of the system in the presence of failures. The basis for the implementation and validation of faulttolerance strategies are realistic fault assumptions, which are captured in a fault hypothesis. This paper describes a fault hypothesis for distributed integrated architectures, which takes into account the sharing of the communication and computational resources of a single distributed computer system among multiple application subsystems. Each node computer serves for the execution of multiple jobs. In analogy, the communication network interconnecting the node computers has to support message exchanges of more than one application subsystem. Using a generic system model of a distributed integrated architecture, we argue in favor of a differentiation of fault containment regions for hardware and software faults. Based on these fault containment regions, we discuss the failure modes, the failure rates, the maximum number of failures, and the recovery intervals. In particular, the fault hypothesis describes the assumptions concerning the respective frequencies of transient and permanent failures in consideration of recent semiconductor trends.

show abstract

“…easily repeatable and therefore expensive [3]. Hence there arises a need for health monitoring ECU to take preventive measures.…”

mentioning

confidence: 99%

Deploying Health Monitoring ECU Towards Enhancing the Performance of In-Vehicle Network

Mishra¹,

Hegde²,

Gurumurthy³

2012

Computer Science &Amp; Information Technology (CS &Amp; IT)

View full text Add to dashboard Cite

show abstract

Automotive virtual integration platforms: why's, what's, and how's

Cited by 22 publications

References 1 publication

Functional design and verification of automotive embedded software: An integrated system verification flow

Functional design and verification of automotive embedded software: An integrated system verification flow

The Fault Assumptions in Distributed Integrated Architectures

Deploying Health Monitoring ECU Towards Enhancing the Performance of In-Vehicle Network

Contact Info

Product

Resources

About