AutoMoDe - Model-Based Development of Automotive Software

Ziegenbein, Dirk; Braun, Peter; Freund, Ulrich; Bauer, Andreas; Romberg, Jan; Schätz, Bernhard

doi:10.1109/date.2005.77

Cited by 7 publications

(2 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Automotive software systems have become increasingly complex and huge, leading to long development cycle and increased development difficulty 1‐3 . To shorten the development time, reduce the development workload, and promote the standardization of the development process, auto manufacturers often use model‐based development (i.e., model‐driven development) tools (e.g., MATLAB, Simulink, and ASCET) to develop automotive software systems 4,5 . However, using model‐driven development could automatically generate logic codes and corresponding configuration information.…”

Section: Introductionmentioning

confidence: 99%

AutoToolVCC: Variable consistency check tool for automotive software projects

Xie

Wang

He³

et al. 2020

Softw Pract Exp

View full text Add to dashboard Cite

Automotive software systems have become increasingly complex and huge, leading to long development cycle and increased development difficulty. When a complete automotive software project has reached a scale of several gigabytes, the complicated development process is prone to produce the following two irregular problems: (1) variable inconsistency problem and (2) code coexistence problem. These irregular problems may eventually lead to serious consequences, such as car crashes. In response to the above irregular problems, we develop a variable consistency check tool called AutoToolVCC for automotive software projects. AutoToolVCC divides the variable consistency check process into two stages: (1) extracting all variable information from the automotive software project and (2) checking the consistency of the variables through the variable preprocessing technique and the variable attribute check technique. After an actual check of multiple automotive software projects (approximately 500–1000 MB in size) provided by an automotive manufacturer, the accuracy of variable consistency check is as high as 100%, and the check time only takes about 10–30 s, whereas the pervious plain method needs 100–600 s.

show abstract

Section: Introductionmentioning

confidence: 99%

AutoToolVCC: Variable consistency check tool for automotive software projects

Xie

Wang

He³

et al. 2020

Softw Pract Exp

View full text Add to dashboard Cite

show abstract

“…In today's automotive software design and development processes hundreds of different legacy artifacts have to be considered such as already developed legacy code files (codes for application, diagnosis, hardware abstraction layer (HAL) and driver), ECU associated libraries, compiler settings, task specifications in OSEK [7] and finally complex strategies for communication in a multi-bus network environment, including FlexRay, CAN (Controller Area Network) and/or LIN (Local Interconnect Network). Although particular phases in the development process are already executed by application of model-driven principles [8], these steps are often restricted to an isolated signal processing and flow control design (e.g. done with MATLAB Simulink and Stateflow [9] that is often used in the body/chassis domain or ASCET [10] in the powertrain domain).…”

Section: Introductionmentioning

confidence: 99%

An Integrative Approach for Embedded Software Design with UML and Simulink

Farkas

Neumann

Hinnerichs

2009

2009 33rd Annual IEEE International Computer Software and Applications Conference

View full text Add to dashboard Cite

The increased amount of software in automotive embedded systems has challenged its C code development to successfully manage software design, reuse, flexibility and efficient implementation. Modelbased methods help to address such challenges with more abstract specification, code generation and simulation to determine if software design will meet requirements. However, in today's development processes lots of different legacy artifacts are involved, that hamper a frictionless migration from C code to model-based design. Therefore, migration concepts and adequate domain-specific methods with adoption of modeling languages and their tools in established embedded coding environments are needed. In our approach we present a novel migration concept considering the integration of two different modeling languages UML and Simulink in a traditional automotive software engineering process. The proof is demonstrated within the software development of a real automotive car door-controller ECU.

show abstract

Eigenschaftsorientierte Beschreibung der logischen Architektur eingebetteter Systeme

Trachtenherz¹

2010

View full text Add to dashboard Cite

KurzfassungAutomobile eingebettete Systeme sind komplexe und verteilte Netzwerke, die aus 20-80 Steuergeräten aufgebaut werden, auf denen jeweils eine oder mehrere Softwarekomponenten laufen. Der logische Architekturentwurf ist somit ein wichtiger Bestandteil des Entwicklungsprozesses.Die Spezifikation der Netzwerkarchitektur findet in der Entwurfsphase statt -hier werden die vernetzten Funktionalitäten und die Verbindungsstruktur zwischen den Komponenten definiert. Eine Verhaltensspezifikation für die einzelnen Komponenten wird in der Analysephase überwiegend mit informalen/semi-formalen Mitteln durchgeführt. Eine formale Spezifikation des Verhaltens wird häufig erst bei der Implementierung durchgeführt. Die Qualitätssicherung für die vernetzten Funktionalitäten findet deshalb erst durch Integrationstests und damit sehr spät in dem Entwicklungsprozess statt. Es fehlt eine hinreichend abstrakte formale Spezifikation der einzelnen Komponenten, die eine präzisere Analyse der Kompatibilität und der Inkonsistenzen in und zwischen den Verhaltensspezifikationen verschiedener Komponenten bereits in der Entwurfsphase und insbesondere vor der Erstellung einer ausführbaren Spezifikation ermöglicht.In der vorliegenden Arbeit entwickeln wir den Lösungsansatz der eigenschaftsorientierten Beschreibung der logischen Architektur eingebetteter Systeme, der eine präzise deklarative Spezifikation mit wählbarem Grad der Abstraktion für unterschiedliche Entwicklungsphasen und -Ebenen ermöglicht. Hierfür erfüllen die verwendeten Beschreibungsmittel für die logische Architektur folgende Anforderungen: Modulare Struktur-und Verhaltensspezifikation; Eindeutigkeit und Präzision durch formale Semantik der Beschreibungsmittel; Möglichkeit der Unterspezifikation / wählbarer Abstraktionsgrad der Spezifikation; Möglichkeit der integrierten Spezifikation struktureller und funktionaler Eigenschaften; Anschauliche Darstellung der Spezifikation. Die Hauptbeiträge dieser Arbeit sind die folgenden:• Die Semantik des CASE-Werkzeugs AUTOFOCUS wurde formalisiert und so erweitert, dass die modulare hierarchische Beschreibung der logischen Architektur eingebetteter Systeme vereinfacht wird. AbstractAutomotive embedded systems are complex and distributed networks consisting of 20-80 ECUs (electronic control units), on each of them single or multiple software components are running. Hence the logical architecture design is an important constituent part of the development process.The network architecture is specified in the design phase -here are defined the networked functionalities and the connection structure between the components. A behavioural specification for the single components is performed in the analysis phase prevailingly by means of informal/semi-formal techniques. A formal behavioural specification is often given at first during the implementation. The quality assurance for networked functionalities is therefore at first feasible by integration tests and hence very late in the development process. A sufficiently abstract formal specificati...

show abstract

AutoMoDe - Model-Based Development of Automotive Software

Cited by 7 publications

References 6 publications

AutoToolVCC: Variable consistency check tool for automotive software projects

AutoToolVCC: Variable consistency check tool for automotive software projects

An Integrative Approach for Embedded Software Design with UML and Simulink

Eigenschaftsorientierte Beschreibung der logischen Architektur eingebetteter Systeme

Contact Info

Product

Resources

About