Search Results

AUTOSAR introduces standardization of software development in three areas, namely Architecture, Application Interfaces and Methodology. The most frequently employed method for application SW migration is the Bottom-up approach, wherein the existing software architecture is reused with no or minimal change. This approach can introduce software performance and maintainability issues. Still, it is often preferred, as it is relatively easy to implement, because of experience with the architecture and the need for quick results. In the Top-down approach, on the other hand, the entire AUTOSAR architecture is created from a Vehicle System and Control System perspective. The Top-down method has potential for a superior result, although it is effort-intensive. A custom methodology for migration from a traditional SW architecture to AUTOSAR architecture is described in this paper.

The potential to reduce the cost of embedded software by standardizing the application behavior for Automotive Body and Comfort domain functions is explored in this paper. AUTOSAR, with its layered architecture and a standard definition of the interfaces for Body and Comfort application functions, has simplified the exchangeability of software components. A further step is to standardize the application behavior, by developing standard specifications for common Body and Comfort functions. The corresponding software components can be freely exchanged between different OEM/Tier-1 users, even if developed independently by multiple suppliers. In practice, individual OEM users may need to maintain some distinction in the functionality. A method of categorizing the specifications as ‘common’ and ‘unique’, and to configure them for individual applications is proposed. This allows feature variability by means of relatively simple adapter functions.