  AUTOSAR (AUTomotive Open System ARchitecture) is an open industry standard
for the automotive sector. It defines the three-layered automotive software
architecture. One of these layers is the application layer, where functional
behaviors are encapsulated in Software Components (SW-Cs). Inside SW-Cs, a set
of runnable entities represents the internal behavior and is realized as a set
of tasks. To address AUTOSAR's lack of support for modeling behaviors of
runnables, languages such as Simulink are employed. Simulink simulations assume
Simulink block behaviors are completed in zero execution time, while real
execution requires a finite execution time. This timing mismatch can result in
failures to detect unexpected runtime behaviors during the simulation phase.
This paper extends the Simulink environment to model the timing properties of
tasks. We present a Simulink block that can schedule tasks with non-zero
simulation times. It enables a more realistic analysis during model
development.
