Model-based Toolchain for the Efficient Development of Safety-Relevant Automotive Embedded Systems

Armengaud, Eric; Zoier, Markus; Baumgart, Andreas; Biehl, Matthias; Chen, De Jiu; Grießnig, Gerhard; Hein, Christian; Ritter, Tom; Tavakoli-Kolagari, Ramin

doi:10.4271/2011-01-0056

Cited by 15 publications

(9 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The following benefits have been concluded from the evaluation of the proposed integrated tool chain (Armengaud et al, 2011b): " Fast synchronization: Due to the use of a semi-formal language (EAST-ADL) for the system architecture, possible misunderstandings between the teams have been minimized and it allowed a quick synchronization between large teams (in our case a 15 person team across 3 countries).…”

Section: Automotive Test Management Tool-chainmentioning

confidence: 99%

Improving automotive embedded systems engineering at European level

Grießnig

Kundner

Armengaud

et al. 2011

Elektrotech. Inftech.

View full text Add to dashboard Cite

Complexity in embedded systems engineering is increasing, imposing challenges to many industries. Especially the automotive industry has gone through significant changes with the application target of embedded systems moving towards safety-relevant applications. New safety standards as well as an increasing number of functionalities in a context of stringent cost constraints represent a complex challenge the industry is dealing with. In this paper, we provide an overview of two major challenges, the automotive industry is facing and of the main European research projects -with an emphasis to CESAR -focused on solving these challenges with respect to embedded systems engineering. We further discuss the reference technology platform as concept for tool integration and interoperability standard in order to significantly reduce costs. Finally, an exemplary realization of such reference technology platform for the automotive domain is presented.Verbesserung von Methoden und Prozessen bei der Entwicklung von eingebetteten Systemen in der europ€ aischen Automobilindustrie. Erh€ ohte Komplexit€ at in der Entwicklung von Embedded Systems stellt heute viele Industriezweige vor Herausforderungen. Dies trifft besonders die Automobilindustrie; hier werden immer mehr sicherheitskritische Funktionen mit Hilfe von Embedded Systems realisiert. Die Wechselwirkung zwischen neuen Standards und steigender Anzahl von Funktionalit€ aten bei strikter Kostenbegrenzung stellt eine komplexe Aufgabe dar, die es zu bew€ altigen gilt. Dieser Artikel behandelt zwei dieser Herausforderungen der automotiven Industrie und stellt -mit einem Fokus auf CESAR -die wichtigsten europ€ aischen Forschungsprojekte im Bereich Embedded Systems vor. Weiters wird die Referenz Technologie Plattform als Konzept f€ ur Werkzeugintegration und Interoperability Standard pr€ asentiert. Ziel ist es, hiermit die Kosten des Entwicklungsprozesses sp€ urbar zu senken. Abschließend wird eine beispielhafte Realisierung einer solchen Referenz-Technologieplattform f€ ur die Automobilindustrie behandelt. Schlü sselwö rter: Automobilindustrie; sicherheitskritische Embedded Systems; ISO 26262; integrierte Tool-Chain

show abstract

Section: Automotive Test Management Tool-chainmentioning

confidence: 99%

Improving automotive embedded systems engineering at European level

Grießnig

Kundner

Armengaud

et al. 2011

Elektrotech. Inftech.

View full text Add to dashboard Cite

show abstract

“…Simulink is a proprietary software and is not based on a metamodelling standard. There are, however, several research projects during which a grammar and metamodel for the Simulink file format has been reverse-engineered [68,143,3]. These approaches offer a conversion of the Simulink MDT file format into a metamodel-based representation, which can be used for further analysis and transformations.…”

Section: Modelling Languagesmentioning

confidence: 99%

“…The differences are expressed as instances of a comparison model, which is described in the EMF Compare developer guide. 3 Besides matching and differencing, EMF Compare can also be used for a full three-way comparison of conflicting model revisions, and also for the resolution of these conflicts.…”

Section: Changes At the Model Levelmentioning

confidence: 99%

“…The documentation of Ecore describes it as a "dialect of UML". 3 The Eclipse Modeling Framework contains an Ecore-based UML metamodel, which can be used to create instances of UML, and which is the base of Ecore-based UML modelling tools, such as Papyrus. 4 The core components of Ecore are displayed in Figure 2.3: As mentioned above, the EReference element is a structural feature that is always contained in an EClass element.…”

Section: The Ecore Metamodelmentioning

confidence: 99%

“…Tools like EtherPad 1 or Google Docs 2 even offer synchronous real-time editing of (non-structured) textual documents. The ModelBus approach [67,3] aims to provide sharing mechanisms for models in a distributed and heterogenous model-driven process. A central repository serves as the store for models, which are then transformed into tool-specific formats using service-based invocation techniques.…”

Section: Collaborationmentioning

confidence: 99%

See 2 more Smart Citations

Flexible views for view-based model-driven development

Bürger¹

2013

Proceedings of the 18th International Doctoral Symposium on Components and Architecture

View full text Add to dashboard Cite

Modern software development faces growing size and complexity of the systems that are being developed. To cope with this complexity, several languages and modelling formalisms are used during the development of a system in order to describe it from various view points and at multiple levels of abstraction. These languages and modeling formalisms are specific to the domain of the system under development, to the paradigms that are followed, and to the developer tools being used. For example, in a component-based process, the software architecture may be defined using a component metamodel, while class diagrams are used for the object-oriented design of the system; performance and reliability models express the extra-functional properties; program code in a general-purpose programming language defines the execution semantics, and is used for the implementation of the system. Although all these artefacts follow different concepts and formalisms, they express the same system from various view points and can thus be understood as views on the system under development. The entirety of these views can be identified as a complete definition of the system. Although the usage of multiple formalisms offers the advantage that different developers can describe the system from different view points, and in languages and models that are specially designed for this purpose, it introduces the problem of fragmentation of information across heterogeneous artefacts in different formats, concepts, and languages. With increasing complexity of the systems, this makes navigation through the system description difficult for developers and other roles in the development process. Furthermore, since the concepts and formalisms are managed independently, they can share semantic overlaps, so that a piece of information about the system under i Abstract development can be expressed in several ways and contexts. For example, while a component model may be used to express the prescriptive software architecture of a system, the implementation in a general-purpose programming language also determines an implicit architecture of the system, which leads to redundancies in the system descriptions. The independent evolution of these artefacts can lead to inconsistencies, which cannot be identified automatically if the semantic correspondances between the artefacts are not modelled explicitly.View-based software development processes offer two fundamental principles of adressing this problem: While synthetic approaches integrate the information of heterogeneous models to form a complete system description, projective approaches introduce a common formalism in which all view points of the system can be represented, and generate the views from this central model. While the pure synthetic approach suffers from a quadratic increase of interdependencies between the view types, which become very numerous with a growing number of formalisms that have to be supported, the projective approach faces the problem of providing a common formalism that is ab...

show abstract

Future of Systems Engineering

Faustmann

Kranabitl

Bajzek

et al. 2020

Systems Engineering for Automotive Powertrain Development

View full text Add to dashboard Cite

Cyber-physical systems, electrification, autonomous driving, connectivity, and shared mobility pose new challenges for powertrain development. To cope with these challenges, development approaches such as systems engineering need to be applied and further improved. Possible directions for the development of systems engineering are discussed together with the required skills and changes in education. The challenges of current development approaches are described from the powertrain development perspective. As the complexity of mechatronic and cyber-physical systems continues to increase rapidly, a deep understanding of

show abstract

Model-based Toolchain for the Efficient Development of Safety-Relevant Automotive Embedded Systems

Cited by 15 publications

References 4 publications

Improving automotive embedded systems engineering at European level

Improving automotive embedded systems engineering at European level

Flexible views for view-based model-driven development

Future of Systems Engineering

Contact Info

Product

Resources

About