Automotive Software Engineering

Schäuffele, Jörg; Zurawka, Thomas

doi:10.1007/978-3-322-91194-0

Cited by 38 publications

(8 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The main use cases are from the OEM perspective: 2 Software layer that joints OEM und supplier specified software. 3 Non Volatile Random Access Memory (1) Validation of distributed or neighbouring systems which have functionally related SWCs on several ECUs.…”

Section: Virtual Integration Conceptmentioning

confidence: 99%

See 1 more Smart Citation

Test front loading in early stages of automotive software development based on AUTOSAR

Michailidis

Spieth

Ringler

et al. 2010

2010 Design, Automation &Amp; Test in Europe Conference &Amp; Exhibition (DATE 2010)

View full text Add to dashboard Cite

Embedded software development has become one of the greatest challenges in the automotive domain, due to the rising complexity of vehicle systems. A method to handle the complexity of automotive software is Model Based Design (MBD). As MBD offers great advantages in early simulation and testing, it has become today's mainstream method for automotive software engineering. However, some aspects can be initially tested after the integration of software on real hardware components (usually by the supplier) and when all parts of a system (e.g. bus systems, sensors, actuators) are present. The consequence is that the requirement specification of the according system possibly contains gaps that can lead to software defects. New technologies like the AUTOSAR standard enable additional potentials for the validation of model based developed software. Due to the AUTOSAR software architecture it is possible for an OEM to realize an early "virtual" software integration with an acceptable effort and perform at next step a front loading of system tests. In this paper we present an approach that improves the quality of the requirement specification artifacts by using test front loading. In detail, we analyze the requirement engineering part of the software development process to identify aspects that can not be tested without having all system components. Afterwards, we classify these aspects and define an abstract test pattern that can be globally used for testing. Additionally, we illustrate our approach in a case study on an interior light system for the next MercedesBenz M-Class generation.

show abstract

Section: Virtual Integration Conceptmentioning

confidence: 99%

“…and powerful tools [2]. In order to meet the short development time, a change in the development of the ECU-software of vehicle systems has for several years been taking place.…”

Section: Introductionmentioning

confidence: 99%

Test front loading in early stages of automotive software development based on AUTOSAR

Michailidis

Spieth

Ringler

et al. 2010

2010 Design, Automation &Amp; Test in Europe Conference &Amp; Exhibition (DATE 2010)

View full text Add to dashboard Cite

show abstract

“…In fact, model-based development is well established and increasingly becoming a favorite approach in the automotive industry [8], [9], [10], [11].…”

Section: Model-based Testingmentioning

confidence: 99%

Model-Based Testing Design for Embedded Automotive Software

Mjeda¹,

McElligott²,

Ryan³

et al. 2009

SAE Technical Paper Series

View full text Add to dashboard Cite

The Engineering Meetings Board has approved this paper for publication. It has successfully completed SAE's peer review process under the supervision of the session organizer. This process requires a minimum of three (3) reviews by industry experts. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. ISSN 0148-7191 Positions and opinions advanced in this paper are those of the author(s) and not necessarily those of SAE. The author is solely responsible for the content of the paper. SAE

show abstract

“…Es entsteht somit eine logische Systemarchitektur, bestehend aus einem Funktionsnetzwerk, den Schnittstellen der Funktionen und der Kommunikation zwischen den Funktionen des gesamten Systems [59]. Im Zuge des daran anschließenden System-Entwurfs wird das Produkt erstmals in einem noch abstrakten Plan dargestellt, der vor allem die (Haupt-)Funktionen des Produktes sowie deren Abhängigkeiten untereinander berücksichtigt.…”

Section: Aufbau Des 3-ebenen-vorgehensmodellsunclassified

Embedded Systems - qualitätsorientierte Entwicklung

Bender¹

2005

View full text Add to dashboard Cite

Automotive Software Engineering

Cited by 38 publications

References 0 publications

Test front loading in early stages of automotive software development based on AUTOSAR

Test front loading in early stages of automotive software development based on AUTOSAR

Model-Based Testing Design for Embedded Automotive Software

Embedded Systems - qualitätsorientierte Entwicklung

Contact Info

Product

Resources

About