Abstract
The development of automotive software has been an evolving process for the last decades. As a result, the paradigm of software development which is independent of the target hardware platform has been adopted in almost all parts of the automotive industry. Deploying software to a hardware platform is now controlled by an enormous parameter set stored in a mapping configuration. This led to the creation of numerous vendor-specific tools for electronic control unit (ECU) development. While this approach simplifies and supports the re-usability of vehicle functions it also increases the complexity as well as the difficulty for integration tests and error localization. In this paper, we present a conceptual platform which allows to establish references between different development and test phase items in a developer-friendly way. It revolves around two self-developed tools supported by an extensive AUTOSAR knowledge base. The system creates inter-connectivity so that it becomes easier to locate the actual origin of a misbehavior or to find a test error manifestation in the actual end system for developers and testers alike.
Highlights
Automotive software development is an ever changing and evolving process
Nowadays vehicle functionalities are developed based on the V-model, but in a hardware and communication technology independent way [1]
A configuration which consists of large parameter sets defines the necessary constraints to deploy the functionality to an actual target hardware platform
Summary
Automotive software development is an ever changing and evolving process. As a result, nowadays vehicle functionalities are developed based on the V-model, but in a hardware and communication technology independent way [1]. A configuration which consists of large parameter sets defines the necessary constraints to deploy the functionality to an actual target hardware platform. This methodology resulted in a large number of diverse tools and a fragmented development environment for electronic control units (ECUs). In Europe, the de facto standard for platformindependent automotive software development is AUTOSAR [2], which in itself is a rather complex architecture and platform By adhering to this standard, the development of reusable vehicle functions can be greatly improved both with regard to time and effort. There is a strong need to resolve behavioral relationships between the functionality and the required communication data of a single ECU under test as well as a large set of integrated ECUs in preseries vehicles to allow efficient testing and validation at any stage of the development process
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
