Through the envisioned AUTOSAR methodology, the integration of hardware and software components shall become simpler and more flexible than ever. But in addition to standardized functional APIs, this approach also needs interfaces for non-functional component properties, specifically timing. However, formalizing the required parameters and defining new methodological steps is not trivial. In this paper, we illustrate ideas to structure timing properties by means of hand-over points and timing contracts using realistic examples, and we show how scheduling analysis provides key information to parameterise the resulting timing interfaces. Finally, we derive (sufficiently dark) gray-box timing chain segments that can be communicated between OEMs and suppliers without loss of IP protection. The resulting models are a) compatible with the AUTOSAR software architecture definitions and b) fit into the envisioned methodology.
How timing interfaces in AUTOSAR can improve distributed development of real-time software
Wie können zeitbestimmte Schnittstellen in AUTOSAR verteilte Entwicklungen von Echtzeit-Software verbessern
2008
6 Seiten, 4 Bilder, 9 Quellen
Aufsatz (Konferenz)
Englisch
AUTOSAR Basic Software in Real Life
Online Contents | 2013
|AUTOSAR basic software in real life
Kraftfahrwesen | 2013
|Autosar standardised application interfaces - support of efficient software sharing
Kraftfahrwesen | 2009
|Model-Based Software Development – Autocode to Autosar
IEEE | 2022
|