SummerCamp is an event in English, in which competing student teams develop the software of distributed automotive comfort systems in accordance with the AUTOSAR standard. The process follows the V-model of development, starting with requirements specification and working towards a technical implementation. Tools used in industrial practice will be provided for all stages of design. Component, integration, and system tests are performed through the execution of the developed software on Electronic Control Units. A final validation process ensures that the system meets customer expectations.
In addition to the technical tasks, specific focus will be on the challenges of project management in a team. Such assignments are designed to prepare the participants for job responsibilities in international companies.
The simulation game is complemented by presentations and training sessions by experts. Thus, attendees will have the opportunity to make company contacts for a future in the automotive and distributed systems industry.
The development approach followed during SummerCamp is built on practical experience and tool support available for the AUTOSAR design methodology. Presentations by experts additionally ensure a close link to industrial practice.
At the beginning, the course conveys a consistent and customer-oriented requirements management approach. Identified system requirements will be documented and structured in Rational DOORS (IBM). Test coverage and test performance will be continuously recorded in the same tool.
The component-based architecture of the application software linked to an initial hardware topology design will be modeled in SystemDesk (dSPACE).
Performance verification and optimization of the system architecture will be performed by analyzing the design in pyCPA.
The internal logic of application software components will be modeled state-based using MATLAB/Simulink in conjunction with Stateflow (MathWorks). TargetLink (dSPACE) allows the generation of production code straight from those models. One individual subsystem will in contrast be directly implemented in C code.
The ECU basic software required for executing developed software components is configured in EB Tresos (Elektrobit). Specifically, electrical signals of the target hardware are abstracted and mapped to logical signals in the application software.
Basic and application software components are linked and compiled into executable object code using Diab Compiler (Wind River Systems).
Automotive microcontrollers (Freescale) can be programmed using the object files generated with PROGPPCNEXUS (P&E Microcomputer Systems).
The system performance achieved by each team is evaluated through an acceptance test running test cases automatically in CANoe (Vector Informatik).