Joachim Stroop

Models for model's sake: why explicit system models are also an end to themselves.

In automotive software and system design, explicit system and especially software models have found their way into the development process. This paper try to give an overview for what such models have so-far been used and which advantages they brought to vehicle manufacturers and suppliers. Another focus of this paper is the comparison to functional models which are already used in the automotive industry to define control algorithms and function implementation. In many cases too strong analogies have been seen between the existing functional control algorithm models and the new system models - leading to suboptimal development processes and tools. This paper therefore try to outline differences between these model types. Finally, a synthesis between functional, system, and software models was sketched.

Prototyping of automotive control systems in a time-triggered environment using flexray

Highly sophisticated control systems are a driving force for innovation in automotive electronics. However, the integration of these systems within current and future vehicle projects is facing a complexity problem. Established methods of realizing such control systems need to be revised. A promising approach to address these problems is to use deterministic time-triggered technologies within automotive electronic systems. In this paper we will describe how rapid prototyping of automotive control systems can be realized within a real-time and time-triggered environment

Effiziente Software-Entwicklung und -Verifikation in einer Autosar-Werkzeugkette

Der erfolgreich eingefuhrte Autosar-Standard definiert ein Austauschformat, welches das Zusammenspiel von Werkzeugen im Software- und Architekturentwurf vereinfacht. Aus der Anwendungs praxis des Autosar- Standards heraus soll im Rahmen dieses Artikels aufgezeigt werden, wie dieses Zusammenspiel durch die Nutzung einer prazise aufeinander abgestimmten Werkzeugkette und wohl definierter Arbeitsablaufe gelingt. Die Firma dSpace bietet hierzu die Werkzeuge SystemDesk und TargetLink an.

System verification throughout the development cycle

More and more complex software systems in modern vehicles require development processes being based on explicit software and system architecture models. If used in early phases of the process, errors and hazards can be identified when modelling new aspects of the overall system. This article will use the dSpace’s tool chain, including the company’s latest product SystemDesk, to outline possible implementations of these ideas.

Preliminary results of a case study: model checking for advanced automotive applications

Model checking is a promising formal verification technique successfully applied in several industrial environments, such as in chip design and in the telecommunication industry. In this paper, preliminary results of an automotive case study are presented as performed in the context of the European project EASIS.

Benefits of system simulation for automotive applications

The automotive industry faces the challenge of handling increasingly complex software systems in modern vehicles. The solution may be twofold: (i) A model-based development paradigm on the system level, using standards such as AUTOSAR, (ii) the usage of such models for a seamless testing and quality assurance process, using simulations and (reusable) tests. This paper describes, from an automotive industry perspective, system models and their advantages for manufacturers and suppliers. The main focus is on tooling for offline system simulations and on the introduction of such solutions in standard development processes. For this, different industrial simulation and testing scenarios are outlined; starting with single software component tests and ending with virtual integrations. For each phase of the development process, chances and problems are discussed.

Durchgehende Systemverifikation im Entwicklungsprozess

Immer komplexere Softwaresysteme in modernen Fahrzeugen erfordern Entwicklungsprozesse, die auf expliziten Software- und Systemarchitekturmodellen basieren. Werden solche Modelle schon in fruhen Phasen des Prozesses eingesetzt, konnen Fehler und Gefahrenquellen bereits bei der Modellierung neuer Aspekte des Gesamtsystems erkannt werden. In diesem Beitrag wird anhand der Werkzeugkette von dSpace einschlieslich des neuesten Produkts SystemDesk erlautert, wie sich diese Methoden umsetzen lassen.

Efficient software development and verification in an Autosar tool chain

The Autosar standard, which has now been successfully introduced, defines an exchange format that simplifies the interactions between tools used for behavior modeling and architecture design. Drawing on practical experi- ence with the Autosar standard, this article will demonstrate how an efficient Autosar development process can be set up by using a precisely coordinated tool chain and well-defined workflows. dSpace provides the System- Desk and TargetLink tools for this.

Standardisierter Datenaustausch im Steuergeräte-Entwicklungsprozess

Elektroniksysteme fur Fahrzeuge zu entwickeln, wird immer mehr zur Herausforderung. Insbesondere steigt der Bedarf an Systemmodellen und Beschreibungsformaten, um alle Aspekte eines Steuergerats oder der Vernetzung von Steuergeraten erfassen zu konnen. Parallel dazu etablieren sich Entwicklungswerkzeuge, um diese Formate zu verarbeiten. Im vorliegenden Beitrag von dSpace wird die Rolle eines architekturbezogenen Werkzeugs im Entwicklungsablauf am Beispiel von System Desk dargestellt.

Standardized data interchange in the ECU development process

Developing automotive electronics systems turns into an ever greater challenge. Among other things, there is an increasing need for system models and description formats that will cover all the aspects of an electronic control unit (ECU) or of an ECU network. At the same time development tools that can process these formats are becoming established. The present dSpace paper describes the role such an architecture-oriented design tool plays in the development process.