<p>Since the incorporation of electronic controls into automobiles in the 1970s, the complexity of automotive software has steadily increased. Recent cars and trucks have more electronics and lines of code than modern aircraft. This complexity has made the commoditization of the software exceptionally challenging. The AUTomotive Open System ARchitecture (AUTOSAR) standard was created to enable original equipment manufacturers (OEMs), Tier 1 and Tier 2 Suppliers, Vendors, and other players in automotive software to freely buy, sell, and integrate software components for automotive applications. AUTOSAR does this through a standardized set of software interfaces and a methodology for enabling software exchange, allowing software tools to interoperate. This study explored how AUTOSAR practitioners go about the business of conducting the methodology and its perceived benefits and problems. A global survey of AUTOSAR practitioners was conducted to collect company and respondent demographic information and details concerning specific practices. The survey results indicated practitioners believe AUTOSAR was good at abstracting hardware from the software and between the software components. Respondents also indicated that the AUTOSAR methodology was complicated and not sufficiently prescriptive, leading to inconsistent interpretation and application. Based on the survey results, it was concluded that more work is needed to provide more decisive clarity and direction for AUTOSAR practitioners.</p>