Data-Centric Communication and Containerization for Future Automotive Software Architectures

Kugele, Stefan; Hettler, David; Peter, Jan M.

doi:10.1109/icsa.2018.00016

Cited by 28 publications

(17 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Whole SOA becomes inoperative if the orchestration system is unreachable. [24] • Fast response time -Some dependable applications require fast and almost deterministic response times. If one service provider goes down, the switch to another one needs to happen fast.…”

Section: Requirements For Dependable Service Orchestration In Hybrid Cloudsmentioning

confidence: 99%

See 1 more Smart Citation

Service Orchestration for Object Detection on Edge and Cloud in Dependable Industrial Vehicles

Pettinen¹,

Hästbacka

2021

JMM

View full text Add to dashboard Cite

Industrial applications, including autonomous systems and vehicles, rely on processing data on multiple physical devices. The composition of functionality across heterogeneous computing infrastructure is challenging, and will likely get even more challenging in the future as software in vehicles is updated to introduce new features and ensure the safety. New soft real-time use cases emerge and in such cases the model of offloading processing from a limited or malfunctioning device is a viable solution. This study examines orchestration of services across edge and cloud for an industrial vehicle application use case involving image based object detection using machine learning (ML) based models. First, service orchestration requirements are defined taking into account the dependable nature of industrial vehicle applications. Second, an implementation based on Arrowhead framework is presented and evaluated. The open Arrowhead framework offers means for dynamic service discovery, authorization and late binding of computational units. The feasibility of object detection as a service and the suitability of Arrowhead framework to support such orchestrations across edge and cloud is assessed.

show abstract

Section: Requirements For Dependable Service Orchestration In Hybrid Cloudsmentioning

confidence: 99%

“…Kugele et al [24] defined requirements and key quality attributes for automotive SOA. Their listing includes testability which is an important aspect of increasing interest with the growing use of machine learning (ML) based components.…”

Section: Requirements For Dependable Service Orchestration In Hybrid Cloudsmentioning

confidence: 99%

Service Orchestration for Object Detection on Edge and Cloud in Dependable Industrial Vehicles

Pettinen¹,

Hästbacka

2021

JMM

View full text Add to dashboard Cite

show abstract

“…The most prominent example of a layered architecture for automotive software is probably AUTOSAR [28], which decouples application software components from base software components within an ECU. However, also within the application software, there is a trend towards structuring the application software components with respect to different dedications (e.g., sensor fusion, controllers, service functionality) [29,30]. Figure 3 shows an example of an application software component architecture that has a dedicated platform component layer (PCL).…”

Section: Layered Component Architectures and Communal Componentsmentioning

confidence: 99%

“…A recent trend in automotive architectures is the migration to service-oriented architectures [29,40,41] to allow for more flexible and faster development and deployment. In a recent case study, we have shown how an advanced driver assistance function can be migrated to a microservice architecture [30].…”

Section: Related Workmentioning

confidence: 99%

Feature dependencies in automotive software systems: Extent, awareness, and refactoring

Vogelsang

2020

Journal of Systems and Software

View full text Add to dashboard Cite

Many automotive companies consider their software development process to be feature-oriented. In the past, features were regarded as isolated system parts developed and tested by developers from different departments. However, in modern vehicles, features are more and more connected and their behavior depends on each other in many situations. In this article, we describe how feature-oriented software development is conducted in automotive companies and which challenges arise from that. We present an empirical analysis of feature dependencies in three real-world automotive systems. The analysis shows that features in modern vehicles are highly interdependent. Furthermore, the study reveals that developers are not aware of these dependencies in most cases. For the three examined cases, we show that less than 12% of the components in the system architecture are responsible for more than 90% of the feature dependencies. Finally, we propose a refactoring approach for implicit communal components, which makes them explicit by moving them to a dedicated platform component layer.

show abstract

“…An alternative development environment is described by Kugele et al [4]. In their work, the throughput of the OpenDDS software middleware is evaluated.…”

Section: Background and Related Workmentioning

confidence: 99%

Microservice Architectures for Advanced Driver Assistance Systems: A Case-Study

Lotz

Vogelsang

Benderius

et al. 2019

2019 IEEE International Conference on Software Architecture Companion (ICSA-C)

View full text Add to dashboard Cite

The technological advancements of recent years have steadily increased the complexity of vehicle-internal software systems, and the ongoing development towards autonomous driving will further aggravate this situation. This is leading to a level of complexity that is pushing the limits of existing vehicle software architectures and system designs. By changing the software structure to a service-based architecture, companies in other domains successfully managed the rising complexity and created a more agile and future-oriented development process. This paper presents a case-study investigating the feasibility and possible effects of changing the software architecture for a complex driver assistance function to a microservice architecture. The complete procedure is described, starting with the description of the software-environment and the corresponding requirements, followed by the implementation, and the final testing. In addition, this paper provides a high-level evaluation of the microservice architecture for the automotive use-case. The results show that microservice architectures can reduce complexity and time-consuming process steps and make the automotive software systems prepared for upcoming challenges as long as the principles of microservice architectures are carefully followed.

show abstract

Data-Centric Communication and Containerization for Future Automotive Software Architectures

Cited by 28 publications

References 8 publications

Service Orchestration for Object Detection on Edge and Cloud in Dependable Industrial Vehicles

Service Orchestration for Object Detection on Edge and Cloud in Dependable Industrial Vehicles

Feature dependencies in automotive software systems: Extent, awareness, and refactoring

Microservice Architectures for Advanced Driver Assistance Systems: A Case-Study

Contact Info

Product

Resources

About