Common Technical Baseline logo
Embedded Systems Guide
Common Technical Baseline
Free in-depth, easy to understand diagrams, texts and references. A world-wide registry of Embedded Systems companies.

 
»  Architecture Examples  
» Autosar: Mapping Software Components to ECUs       » Virtual Functional Bus (AUTOSAR)   

Virtual Functional Bus (AUTOSAR)

Using “Software Component Descriptions“ as input, the „Virtual Functional Bus“ validates the interaction of all components and interfaces before software implementation.

AUTOSAR defines the application environment so that the latter can be kept in a consistent form. The environment defines a component’s interface to the rest of the ECU and the vehicle. The abstraction of the environment is called the Virtual Function Bus – or VFB.

A software component is connected to the virtual function bus in order to be able to communicate either with other software components or in order to use input and output functions. In other words, the virtual function bus acts as a communications matrix connecting I/O units and software components.

-- See also (internal links) --

-- Related companies and institutions --

AUTOSAR
 AUTomotive Open System ARchitecture 

BMW Group
  

If you would like to add your company or institution to this page, feel free to contact us at:  contact@embedded-systems-portal.com.
 
   
The Common Technical Baseline / Embedded Systems Guide          •          Contact          •          Site Map
 
Autosar: Mapping Software Components to ECUs ::: Virtual Functional Bus (AUTOSAR)Embedded Systems Guide(cache)