Rigorous model-based design &amp; verification flow for in-vehicle software

Ramesh, S.; Gadkari, Ambar A.

doi:10.1145/2024724.2024728

Cited by 2 publications

(1 citation statement)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Therefore, it is highly desirable to validate CPS design as early as possible. However, the existing CPS design tools stay at the domain-specific levels [4], [10], [26], and this inhibits the possibility of appropriately handling the cross-cutting concerns that characterize CPS. For example, the early design of an automotive requires an experienced designer with a broad multidomain knowledge to manually make decisions such as: Should the control be implemented in a traditional continuous-domain architecture or in an E/E hybrid-domain architecture?…”

mentioning

confidence: 99%

Cyber–Physical Codesign at the Functional Level for Multidomain Automotive Systems

Canedo

Faruque

2015

IEEE Systems Journal

View full text Add to dashboard Cite

Software-integrated multidomain automotive systems, which is also referred to as automotive cyber-physical systems (CPS) consist of various interacting domains (software, hardware, multiphysics, communication, etc.). Design decisions in one domain may completely change the constraints and requirements in the other domains, e.g., adding more functions in a modern automotive CPS may require changes to thousands of lines of software code or even the mechanical architecture. Existing CPS design methodologies are siloed in a specific domain and therefore have limited design space exploration capabilities because only one domain can be tested at a time. This paper presents a functional-level cyber-physical codesign methodology starting from the functional model of the CPS capable of concurrently expressing (multi-)physics and control in automotive applications. Moreover, we introduce a high-level synthesis algorithm capable of selecting a set of optimized system architectures using various executable simulation components and cost metrics. We demonstrate our methodology with a realistic automotive use case and explore various design alternatives for implementing the control systems in pure continuous domain (e.g., traditional automotive subsystems without engine control units) or hybrid domain (e.g., brake-by-wire, steer-by-wire, drive-by-wire, etc.) under power, performance, and reliability constraints.

show abstract

mentioning

confidence: 99%