institut f¨ur informatik - PST Thesis Management Interface - LMU
institut f¨ur informatik - PST Thesis Management Interface - LMU
institut f¨ur informatik - PST Thesis Management Interface - LMU
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
3.1. The AUTOSAR standard<br />
whereas a requiring component can invoke the operations. Equivalently, if a sender-receiver<br />
paradigm is used, a providing port generates the data whereas a receiving port consumes it.<br />
Virtual Functional Bus and Runtime Environment<br />
The Virtual Functional Bus (VFB) is a theoretical concept that represents an abstraction of<br />
the connections between AUTOSAR software components of the entire vehicle and between<br />
AUTOSAR software components and the components of the basic software. The VFB enables<br />
AUTOSAR software components to be integrated before the underlying ECU hardware<br />
is available, thereby speeding up the vehicle development process. The AUTOSAR runtime<br />
environment (RTE) functions as a communication center for both inter-ECU and intra-ECU<br />
information exchange that takes place between AUTOSAR software components [AUT10b].<br />
Since these communication requirements depend on the deployment, the RTE needs to be<br />
customized for each ECU. Therefore, it can be seen as a realization of the VFB on a specific<br />
ECU.<br />
Basic software<br />
The basic software provides services to the AUTOSAR software components and is required<br />
to run the application part of the software, but it does not fulfill any functional tasks itself<br />
[Hei04]. The basic software consists of standardized components - such as an operating<br />
system, a communication framework to the vehicle bus systems (CAN, FlexRay etc.), access<br />
to the ECU’s microcontroller and other hardware such as sensors and actuators that are<br />
specific to each individual ECU.<br />
3.1.2. AUTOSAR methodology<br />
The AUTOSAR methodology describes the common technical approach for steps that are<br />
necessary for AUTOSAR system development [AUT11a]. Figure 3.2 shows a broad view of<br />
the design steps from system configuration to generating an ECU executable. The methodology<br />
is formalized as a workflow that defines dependencies between documents containing<br />
information and activities processing that information.<br />
Figure 3.2.: Overview of the AUTOSAR methodology (image adopted from [AUT11a]).<br />
The formal description of the contained information is supported by the AUTOSAR metamodel<br />
(see section 3.1.3). The activities involve complex processing of a large amount of<br />
27