Overcoming the interoperability barrier in mixed-criticality systems

0Citations
Citations of this article
6Readers
Mendeley users who have this article in their library.
Get full text

Abstract

Concurrent engineering of system parts with diverging requirements can be extremely challenging. One example are mixed-criticality systems that integrate hard real-time software for safety-critical functionality and general purpose software providing a sophisticated user interface. The automotive industry, as well as other industrial branches, has a growing need to integrate consumer electronics applications (e.g. Linux based) and safety-relevant applications requiring an underlying hard real-time operating system. Some established concepts for mixed-criticality systems can be found in the avionics domain. This paper demonstrates that the principles behind these concepts are a dead end regarding innovations requiring a close interoperation. The second contribution of the paper is to present a different solution approach as a potential remedy that allows the different developer groups (hard real-time and standard IT) to retain their attitude to software development. The core of the novel approach is a worst-case execution time (WCET) directed OS service, which could serve as solution pattern for further problems in mixed-criticality systems. © Springer-Verlag London 2013.

Cite

CITATION STYLE

APA

Schneider, J. (2013). Overcoming the interoperability barrier in mixed-criticality systems. In Advanced Concurrent Engineering (pp. 1093–1104). Springer-Verlag London Ltd. https://doi.org/10.1007/978-1-4471-4426-7_92

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free