Problem statement
The scope of this use case is a single ECU that is under the responsibility of the OEM.
Modern automotive systems are developed in the context of a complex supplier chain. The OEM contracts the development of many components to so-called Tier-1 suppliers, which in turn entrust the development of some sub-components to their contractors.
Obviously, following such design style none of the involved parties is in possession of all system details that are necessary to reason about the global timing behavior. Unfortunately, there is no simple loophole to this situation, since the individual parties aim to protect their intellectual property and hesitate to share implementation details. This results in the fact that most timing related integration problems can only be discovered at integration time, i.e. when the implementation is done, which of cause leads to lengthy and costly development iterations.
The aim of this use case is to define a process between an OEM and his suppliers that allows to reason about the system timing behavior already at early design stages while protecting the individual intellectual properties. The process is based on the exchange of so-called timing models and is split into two parts:
1. The supplier side describing the supplier’s development process and describing how the timing model for the developed functionality can be derived.
2. The OEM side describing the OEM’s development process and describing how the timing models delivered by the suppliers can be used to validate the overall system timing behavior.
Please note that the use case focuses on the development of control applications which are the source of a large part of timing constraints in automotive systems.
|