Technology
Q 1. How does AUTOSAR secure conformance in the market?
In order to ensure and to maintain a stable standard, the control of the conformance with respect to the valid set of specifications is mandatory. Conformance test specifications for Release 4.0.2 and process definitions are in place. Next, AUTOSAR is preparing acceptance tests.
Q 2. How does AUTOSAR keep the standard up to date?
Updates and improvements of the standard will be introduced by future releases of AUTOSAR. Corrections are handled by a change management process and are provided as revisions of the existing releases. This process has been specified and is alive.
Q 3. Does AUTOSAR consider a standardization of functional and logical decomposition?
AUTOSAR will deal with decomposition, although the method of decomposition will not be standardized.
Q 4. Does AUTOSAR consider standardization of application interfaces, e.g. interface to brake-system?
Yes, it is foreseen to standardize different APIs (Application Programming Interfaces) to distinguish software layers and to realize the AUTOSAR architecture.
Q 5. Migration: How does the integration of non-AUTOSAR compliant software work?
One of the main requirements of AUTOSAR is to assure the interoperability with legacy software. This will enable the re-use of existing, non-AUTOSAR compliant software, e.g. drivers. The most obvious way to reach this integration is using a Complex Driver as a wrapper around the non-AUTOSAR compliant software.
Q 6. What are the requirements on the controller to support an AUTOSAR ECU?
The acceptance of AUTOSAR will depend heavily on processing and memory requirements. AUTOSAR will imply only small memory and performance impacts in micro controllers.
Q 7. Does AUTOSAR use existing standards?
In general, existing standards should be given the highest priority. If existing standards do not fit the requirements, it is useful to adopt existing standards wherever possible.
Q 8. How will AUTOSAR handle conformance testing for application software?
This is currently not planned.
In order to ensure and to maintain a stable standard, the control of the conformance with respect to the valid set of specifications is mandatory. Conformance test specifications for Release 4.0.2 and process definitions are in place. Next, AUTOSAR is preparing acceptance tests.
Q 2. How does AUTOSAR keep the standard up to date?
Updates and improvements of the standard will be introduced by future releases of AUTOSAR. Corrections are handled by a change management process and are provided as revisions of the existing releases. This process has been specified and is alive.
Q 3. Does AUTOSAR consider a standardization of functional and logical decomposition?
AUTOSAR will deal with decomposition, although the method of decomposition will not be standardized.
Q 4. Does AUTOSAR consider standardization of application interfaces, e.g. interface to brake-system?
Yes, it is foreseen to standardize different APIs (Application Programming Interfaces) to distinguish software layers and to realize the AUTOSAR architecture.
Q 5. Migration: How does the integration of non-AUTOSAR compliant software work?
One of the main requirements of AUTOSAR is to assure the interoperability with legacy software. This will enable the re-use of existing, non-AUTOSAR compliant software, e.g. drivers. The most obvious way to reach this integration is using a Complex Driver as a wrapper around the non-AUTOSAR compliant software.
Q 6. What are the requirements on the controller to support an AUTOSAR ECU?
The acceptance of AUTOSAR will depend heavily on processing and memory requirements. AUTOSAR will imply only small memory and performance impacts in micro controllers.
Q 7. Does AUTOSAR use existing standards?
In general, existing standards should be given the highest priority. If existing standards do not fit the requirements, it is useful to adopt existing standards wherever possible.
Q 8. How will AUTOSAR handle conformance testing for application software?
This is currently not planned.