I. Introduction
Concepts and means for timing modeling and analysis are mandatory in the automotive software development process to allow verification and systematic reasoning about the timing behavior of a system under development. Elements influencing the timing behavior due to hardware or software can be scattered all over the system. Their timing properties, which may depend on the implementation and vary between manufacturers, shall be verified against the timing constraints derived from the safety analysis. Those timing properties could be task execution times, bus latencies and sensor sampling rates, for instance. A timing constraint can be a requirement of a controlling algorithm for an ECU that expects updated sensor data every 1ms, for example. When timing properties as well as timing constraints are not modeled explicitly, it is nearly impossible to apply an (automated) verification process.