
Software Component
VIRTUAL FUNCTIONAL BUS
ECU Software Architecture
AUTOSAR Software
AUTOSAR Runtime Environment
AUTOSAR Basic Software
Classification of interfaces
AUTOSAR Methodology
VIRTUAL FUNCTIONAL BUS
ECU Software Architecture
AUTOSAR Software
AUTOSAR Runtime Environment
AUTOSAR Basic Software
Classification of interfaces
AUTOSAR Methodology
Classification of interfaces
In the image three different types of interfaces are shown: "AUTOSAR Interface", "Standardized AUTOSAR Interface" and "Standardized Interface". Please note that the boxes define the classification of the interfaces for the different modules, i.e. the interface boxes in the image shall not be regarded as separate modules or layers. The semantics of these classifications are as follows:
- AUTOSAR Interface
An AUTOSAR Interface describes the data and services required or provided by a component and is specified and implemented according to the AUTOSAR Interface Definition Language. An AUTOSAR Interface is partly standardized within AUTOSAR, e.g. it may include OEM specific aspects. The use of AUTOSAR Interfaces allows software components to be distributed among several ECUs. The RTEs on the ECUs will take care of making the distribution transparent to the software components. - Standardized AUTOSAR Interface
A Standardized AUTOSAR Interface is an AUTOSAR Interface standardized within the AUTOSAR project. - Standardized Interface
A software interface is called Standardized Interface if a concrete standardized API exists (e.g. OSEK COM Interface).
