扬州市2010年中小学骨干教师业务考核.ppt

IDA, TU Braunschweig Automotive Software Integration Razvan Racu, Arne Hamann, Rolf Ernst Outline Software Integration and AUTOSAR AUTomotive Open System Architecture AUTOSAR and System Timing System-level Timing Analysis Examples Conclusion Automotive Integration Challenges Complexity Hundreds of functions 50+ ECUs Networked control Many suppliers Heterogeneous Integration challenges are key Risks: reliability, quality, liability Meeting target SOP Development and production cost AUTOSAR Goals Modularity tailor the SW-components according to the individual requirements Scalability adaptability of SW-components to different vehicle platforms avoid proliferation of software with similar functionality Transferability remapping of SW-components among different HW-components balance the use of resources Re-usability adaptability of SW-components across different product lines shorten design process improve quality and reliability of E/E systems Standardized interfaces AUTOSAR Consortium AUTOSAR Methodology SW-Components (SW-C) encapsulate the applications Virtual Functional Bus (VFB) communication mechanisms interface to Basic SW Mapping configuration and generationof RTE and Basic SW Runtime Environment (RTE) VFB implementation on a specific ECU Basic Software (BSW) infrastructural functionalityon an ECU AUTOSAR Software The Atomic Software Component consists of software component description operations and data elements provided/required requirements on infrastructure required resources (memory, CPU-time, etc) implementation object code source code Virtual Functional Bus enables hardware and mapping independent integration of SW-components communication mechanisms Client-Server Sender-Receiver SW Components and Runnables SW-Components atomic components with respect to mapping provided by one supplier Runnables atomic components with respect to execution attached to different OS Tasks Outline Software Integration and AUTOSAR AUTomotive Open System Archit