Lars Stockmann1, 2, *, , Sven Laux2, Eric Bodden1, 3,
Software Engineering Group, Heinz Nixdorf Institute, Paderborn University, Fürstenallee 11, Paderborn, 33102, North Rhine-Westphalia, Germany
dSPACE GmbH Rathenaustraße 26, Paderborn, 33102, North Rhine-Westphalia, Germany
Fraunhofer IEM, Zukunftsmeile 1, Paderborn, 33102, North Rhine-Westphalia, Germany
Received 19 January 2020, Accepted 14 January 2021, Available Online 16 February 2021.
- Architecture; Runtime Verification; Database; AUTOSAR; Cloud
Analyzing runtime behavior as part of debugging complex component-based systems used in the vehicle industry is an important aspect of the integration process. It is a laborious task that involves many manual steps. One reason for this is that, as of today, the analysis is usually not performed on the architecture level, where the system has initially been designed. Instead, it relies on source code debugging or visualizing signals and events. With an ever-growing complexity of such systems, it becomes increasingly difficult to find errors that manifest at integration level, i.e., when the components interact with each other in a complex environment. Architectural Runtime Verification (ARV) is an approach specifically designed for the integrator—a generic way to analyze system behavior on architecture level using the principles of Runtime Verification. This paper draws on our initial publication. It provides further details and an evaluation of the ideas using a database hosted in the cloud.
- © 2021 The Authors. Published by Atlantis Press B.V.
- This is an open access article distributed under the CC BY-NC 4.0 license (http://creativecommons.org/licenses/by-nc/4.0/).