mulit-level system integration based on autosar. the design of distributed embedded real-time system is a challenging task. besides solving the control-engineering issues, one has to consider real-time scheduling, reliability and production requirements w.r.t. production cost of the electronic control unit (ecu). this has a considerable impact on the employed software design techniques. these design techniques are well known in the automotive software industry, but are applied with different flavors at each vehicle manufacturer and their suppliers. this situation has changed considerably with the results of the autosar development partnership, which unifies the flavors of automotive software design. automotive software design is embedded in the so-called v-cycle of embedded automotive system development[1]. it starts with the requirements analysis which results later on in a model of the control algorithm. the control algorithm is tested against a vehicle model and establishes the topmost level in system integration. the second system integration level is the adaptation of the control algorithm to be run on a rapid-prototyping system. the rapid-prototyping system is integrated into an existing e/earchitecture. the e/e-architecture consists of the ecus connected by networks like can or flexray and gateways. sensors- and actuators being used by several control algorithms are coupled to an ecu, which might propagate signals to other ecus via a vehicle network. from the software point of view, the controlalgorithm has now to respect real-time scheduling and the quantization of the sensor- and actuator signals, no matter whether these signals are generated on the rapid-prototyping system or exchanged via the bus with other ecus. further development steps in the v-cycle are the software implementation, the ecu- and the network integration. the integrated ecus and networks are tested against vehicle models running on hardware-in-the-loop (hil) systems. if this works fine, the ecus are integrated in the real vehicle for calibration. the software implementation and the ecu integration are deeply influenced by autosar. autosar is a development partnership of all stakeholders in the automotive software development (e.g. vehicle manufacturers and their suppliers) which unifies several software implementation techniques[2]. it describes a common ecu software architecture[3] consisting of configurable basic software modules (bsw), a runtime environment (rte) and a software component description[4]. the software component description describes the interfaces for dataexchange as well as the access points for the rte. the basic idea of consisting of interconnected software components which are later mapped to an e/e-architecture. currently, the vfb structure of autosar software architectures is mainly driven by the next generation e/e-architectures. the vfb structure forms the third system integration level. the next integration step into an autosar environment is the integration of the rapid-prototyping tested control algorithm to autosar software components. since most vfb descriptions use fixed-point interfaces, the control algorithm has to be transformed to fixed-point arithmetic. if the control algorithm is modelled in tools like ascet, this conversion can be achieved by code-generation. the same holds true for control algorithms already being used in e/e-architectures without an autosar software architecture. the vfb-description with the control-algorithms forms the fourth system integration level, which can be simulated with plant-models on a pc by tools like intecrio-vp. the fifth system integration level is given by the mapping process as defined in the autosar methodology[5] and requires the configuration of the rte and the bsw modules for a single ecu. at this integration level, one can perform hil testing and calibration in the same way as for non-autosar systems. several evaluation projects, e.g. [6] and [7], have shown that the multi-level integration approach is feasible to guide the configuration capabilities of autosar software architectures.