Roadmap
Q 1. What is the roadmap for AUTOSAR?
The AUTOSAR project plan was released in May 2003. It has been divided in two phases. Phase I, which covered the definition of the basic software specifications, was finalized by December 2006. The documented specifications made the AUTOSAR standard available to automotive product development. The activities in Phase II, reaching from beginning of 2007 to end of 2009, were the exploitation and maintenance of the outcome of Phase I, and the further development of the standard. The top level goals of Phase III, which started 2010, are to maintain existing specifications, improve maintainability, and further develop to augment the established AUTOSAR architecture. The first cars with AUTOSAR technology inside were launched in the market in 2008. The exploitation plans of the Core Partners show that an increasing number of cars with complete AUTOSAR products are going to be on the road.
Q 2. What will happen after Phase III?
The aims of Phase III are the exploitation and maintenance of the results of Phase II and I, and the further development of the standard. In the next years, AUTOSAR will be found in a rising number of cars. The appropriate way how AUTOSAR will be handled beyond 2012 is currently discussed by the Core Partners.
Q 3. What was new with Release 2.1?
Release 2.0 defined specifications on software architecture components such as basic software and runtime environment. The release 2.1 also includes specifications on development methodology and templates. In addition, the specifications on the maintenance and conformance test process have been expanded and the first descriptions for application interfaces for body and interior electronics have been introduced. Release 2.1 also incorporates the first results of the second implementation cycle called Validator 2.
Q 4. What was new with Release 3.0?
Release 3.0 contains on the one hand significantly updated and improved documents from the previous release and on the other hand also some new specifications. Regarding application interfaces, R3.0 for the first time addresses more than 20 different compositions from the body, powertrain, and chassis domain. Specifications of standardized application interfaces are now also available for the powertrain and chassis domain. The number of standardized application interfaces has been expanded for the body domain, and explanatory documents have been prepared for the interfaces of all domains. In addition, the developers have harmonized the concept for wakeup of ECUs and start-up of networks in the vehicle and have introduced state managers for the bus systems CAN, LIN, and FlexRay.
Q 5. What was the reason for the Release 3.1?
The integration of the feature OBD 2 originally was planned for R3.0, but could not be finished in time. As OBD 2 is highly requested in the standard, we decided for the minor release 3.1 mid of 2008 instead of delivering this with the next major release 4.0 end of 2009.
Q 6. What will be new with Release 4.0?
The first Revision of Release 4.0 was available end of 2009. It introduced new concepts on both architecture and methodology. In addition, a set of conformance test specifications on basic software specifications was provided on basic software module level for Release 4.0 Revision 2. The Release 4.0 contains a large set of application interfaces standardized by the AUTOSAR development cooperation. The efforts have been focused on the non innovative applications to support software re-use and exchange considered as one of the main requirements. Currently, AUTOSAR works on further conceptual additions for Release 4.0. By doing that AUTOSAR aims to be backward compatible with former Revisions of Release 4.0.
The AUTOSAR project plan was released in May 2003. It has been divided in two phases. Phase I, which covered the definition of the basic software specifications, was finalized by December 2006. The documented specifications made the AUTOSAR standard available to automotive product development. The activities in Phase II, reaching from beginning of 2007 to end of 2009, were the exploitation and maintenance of the outcome of Phase I, and the further development of the standard. The top level goals of Phase III, which started 2010, are to maintain existing specifications, improve maintainability, and further develop to augment the established AUTOSAR architecture. The first cars with AUTOSAR technology inside were launched in the market in 2008. The exploitation plans of the Core Partners show that an increasing number of cars with complete AUTOSAR products are going to be on the road.
Q 2. What will happen after Phase III?
The aims of Phase III are the exploitation and maintenance of the results of Phase II and I, and the further development of the standard. In the next years, AUTOSAR will be found in a rising number of cars. The appropriate way how AUTOSAR will be handled beyond 2012 is currently discussed by the Core Partners.
Q 3. What was new with Release 2.1?
Release 2.0 defined specifications on software architecture components such as basic software and runtime environment. The release 2.1 also includes specifications on development methodology and templates. In addition, the specifications on the maintenance and conformance test process have been expanded and the first descriptions for application interfaces for body and interior electronics have been introduced. Release 2.1 also incorporates the first results of the second implementation cycle called Validator 2.
Q 4. What was new with Release 3.0?
Release 3.0 contains on the one hand significantly updated and improved documents from the previous release and on the other hand also some new specifications. Regarding application interfaces, R3.0 for the first time addresses more than 20 different compositions from the body, powertrain, and chassis domain. Specifications of standardized application interfaces are now also available for the powertrain and chassis domain. The number of standardized application interfaces has been expanded for the body domain, and explanatory documents have been prepared for the interfaces of all domains. In addition, the developers have harmonized the concept for wakeup of ECUs and start-up of networks in the vehicle and have introduced state managers for the bus systems CAN, LIN, and FlexRay.
Q 5. What was the reason for the Release 3.1?
The integration of the feature OBD 2 originally was planned for R3.0, but could not be finished in time. As OBD 2 is highly requested in the standard, we decided for the minor release 3.1 mid of 2008 instead of delivering this with the next major release 4.0 end of 2009.
Q 6. What will be new with Release 4.0?
The first Revision of Release 4.0 was available end of 2009. It introduced new concepts on both architecture and methodology. In addition, a set of conformance test specifications on basic software specifications was provided on basic software module level for Release 4.0 Revision 2. The Release 4.0 contains a large set of application interfaces standardized by the AUTOSAR development cooperation. The efforts have been focused on the non innovative applications to support software re-use and exchange considered as one of the main requirements. Currently, AUTOSAR works on further conceptual additions for Release 4.0. By doing that AUTOSAR aims to be backward compatible with former Revisions of Release 4.0.