AUTOSAR Automotive Open System Architecture can be defined as a common platform for the whole automotive industry that is designed to enhance the scope of application for vehicle functionality without affecting the current operating model. AUTOSAR is basically an open and standard software architecture which was jointly developed by automobile manufacturers, suppliers and tool developers. This unique architecture was developed in order to establish and maintain a common standard among the manufacturers, software suppliers, and tool developers so that the outcome of the process can be delivered without the need of any alterations. As the demand for the intelligent, safer and smarter vehicle increases the competition in the automotive industry will also increase.
|Published (Last):||26 June 2015|
|PDF File Size:||14.48 Mb|
|ePub File Size:||3.77 Mb|
|Price:||Free* [*Free Regsitration Required]|
It pursues the objective to create and establish an open and standardized software architecture for automotive electronic control units ECUs. Goals include the scalability to different vehicle and platform variants, transferability of software, the consideration of availability and safety requirements, a collaboration between various partners, sustainable use of natural resources, and maintainability during the whole product lifecycle.
In , work on the Adaptive Platform began. A first release was published in early , followed by release in October  and release in March AUTOSAR provides a set of specifications that describes basic software modules, defines application interfaces and builds a common development methodology based on standardized exchange format. Basic software modules made available by the AUTOSAR layered software architecture can be used in vehicles of different manufacturers and electronic components of different suppliers, thereby reducing expenditures for research and development and mastering the growing complexity of automotive electronic and software architectures.
Based on this guiding principle, AUTOSAR has been devised to pave the way for innovative electronic systems that further improve performance, safety, and environmental friendliness and to facilitate the exchange and update of software and hardware over the service life of the vehicle.
It aims to be prepared for the upcoming technologies and to improve cost-efficiency without compromising quality. Its main deliverable is specifications. The application software layer is mostly hardware independent. Communication between software components and access to BSW happens via RTE, which represents the full interface for applications. Services are divided further, into functional groups representing the infrastructure for system, memory and communication services.
This virtual bus is an abstract set of RTEs that are not yet deployed to specific ECUs and decouples the applications from the infrastructure. It communicates via dedicated ports, which means that the communication interfaces of the application software must be mapped to these ports. From an application point of view, no detailed knowledge of lower-level technologies or dependencies is required. This supports hardware-independent development and usage of application software.
New use-cases required the development of the Adaptive Platform. This can require communication with traffic infrastructure e. Further, CarX applications require interaction to vehicles and off-board systems. That means that the system has to provide secure on-board communication, support of cross-domain computing platforms, smartphone integration, integration of non-AUTOSAR systems, and so on. Also, cloud-based services will require dedicated means for security, such as secure cloud interaction and emergency vehicle preemption.
They will enable remote and distributed services, such as remote diagnostics, over the air OTA update, repair, and exchange handling. One of the key features of the Adaptive Platform is service-oriented communication since the Platform is based on the Service - Oriented Architecture. For the Adaptive Platform two types of interfaces are available: services and application programming interfaces APIs. The foundation contains common requirements and technical specifications for example protocols shared between the AUTOSAR platforms, and the common methodology.
Acceptance Test Specifications are system test specifications using the specified interfaces of the respective Platform. Also, they are considering the specified behavior on the bus. They can be seen as a black box test case for a given platform function.
The specification of standard acceptance tests contributes to these objectives. Standardization of functional interfaces across manufacturers and suppliers and standardization of the interfaces between the different software layers is seen as a basis for achieving the technical goals of AUTOSAR. The contribution of partners varies depending on the type of partnership:  .
Strategic Partners are appointed for a period of two years from the circle of Premium Partners and support the project leader team in the various technical, organizational and everyday processes. They also give new strategic inputs to the project leader round. Premium and Development members contribute to work packages coordinated and monitored by the Project Leader Team established by the Core Partners. While the standard is open, many vehicle manufacturers use commercial implementations and toolsets that may be costly to buy.
From Wikipedia, the free encyclopedia. This article has multiple issues. Please help improve it or discuss these issues on the talk page. Learn how and when to remove these template messages. This article contains content that is written like an advertisement. Please help improve it by removing promotional content and inappropriate external links , and by adding encyclopedic content written from a neutral point of view.
December Learn how and when to remove this template message. This article relies largely or entirely on a single source. Relevant discussion may be found on the talk page. Please help improve this article by introducing citations to additional sources. This article relies too much on references to primary sources.
Please improve this by adding secondary or tertiary sources. February Learn how and when to remove this template message. A major contributor to this article appears to have a close connection with its subject. It may require cleanup to comply with Wikipedia's content policies, particularly neutral point of view. Please discuss further on the talk page.
April Learn how and when to remove this template message. Retrieved 11 December Archived from the original PDF on 19 December Retrieved 14 May Archived from the original on 19 December Retrieved Archived from the original on 23 September Stack Overflow.
Retrieved 27 May Categories : Engine technology Software architecture Automotive software. Hidden categories: Articles with a promotional tone from December All articles with a promotional tone Articles needing additional references from February All articles needing additional references Articles lacking reliable references from February All articles lacking reliable references Wikipedia articles with possible conflicts of interest from April Articles with multiple maintenance issues Official website different in Wikidata and Wikipedia Wikipedia articles with GND identifiers Wikipedia articles with VIAF identifiers Wikipedia articles with WorldCat-VIAF identifiers.
It pursues the objective to create and establish an open and standardized software architecture for automotive electronic control units ECUs. Goals include the scalability to different vehicle and platform variants, transferability of software, the consideration of availability and safety requirements, a collaboration between various partners, sustainable use of natural resources, and maintainability during the whole product lifecycle. In , work on the Adaptive Platform began. A first release was published in early , followed by release in October  and release in March
Basics of AUTOSAR – Part 1
The design model uses application software components which are linked through an abstract component, named the virtual function bus. The application software components are the smallest pieces of application software that still have a certain functionality. The software of an application can then be composed by using different application software-components. By only defining the interfaces, there is still freedom in the way of obtaining the functionality. The virtual function bus connects the different software components in the design model.