No abstract

Software development in the automotive domain has been subject to changing and evolving processes for the last 15 years. As a result, the functionality of a vehicle is now developed independently of the target platform and communication technology. The actual mapping constraints to a hardware platform are then represented by a large parameter set stored in a configuration. This paradigm has spawned a heterogeneous tool environment for development of electronic control units (ECUs). On the one hand, this proceeding facilitates the development of reusable vehicle functions but on the other hand increases the difficulty for testing as well as error localization in the actual end system. The architecture of choice for platform independent ECU development in the automotive industry in Europe is AUTOSAR, which is in itself very complex but essential for automotive software developers. This makes it vital that students and junior developers of automotive software engineering can be trained in a fast and concise, industry-oriented way. In this paper, we present an educational concept which focuses on the inter-connections between different development and test phases in the automotive industry. It is mainly realized around two self-developed tools, which support learners and power a learning management system, all backed by an extensive AUTOSAR knowledge base. This system eases the learning and comprehension of automotive software development and test by hands-on-learning for both students and professional developers.

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.

No abstract

No abstract