Loading...
Please wait, while we are loading the content...
Similar Documents
AUTOSAR- Challenges and Solutions from a Software Vendor’s Perspective
| Content Provider | CiteSeerX |
|---|---|
| Author | Galla, Thomas M. Pallierer, Roman Gmbh, Elektrobit Austria |
| Abstract | Abstract — The automotive standard AUTOSAR provides a broad standardized basis for ECU software development con-sisting of over 80 software modules and libraries accompanied by an associated development methodology. The potential benefits of (re-)using these standardized software modules are undisputed and make the use of AUTOSAR very attractive. When deploying AUTOSAR, however, both the OEMs and the Tier1 are con-fronted with significant challenges. This paper highlights some of these major challenges from a software vendor’s perspective, namely the dealing with multiple AUTOSAR versions, the handling of the complexity, the need for optimizations to cope with limited hardware resources, the integration with legacy modules, and the support of the migration between different different OEM projects as well as between different AUTOSAR versions. Possible approaches approaches and solutions to these challenges are illustrated using Elektrobit’s products EB tresos Studio and EB tresos AutoCore as examples. Index Terms — Automotive embedded software, AUTOSAR |
| File Format | |
| Access Restriction | Open |
| Subject Keyword | Autosar Challenge Software Vendor Software Module Multiple Autosar Version Potential Benefit Ecu Software Development Con-sisting Index Term Automotive Development Methodology Software Vendor Perspective Broad Standardized Basis Automotive Standard Autosar Elektrobit Product Eb Tresos Studio Different Different Oem Project Different Autosar Version Major Challenge Possible Approach Approach Legacy Module Limited Hardware Resource Significant Challenge |
| Content Type | Text |
| Resource Type | Article |
