Search Results

Automotive applications classed as safety-related or safety-critical are now important differentiating technologies in the automotive industry. The emergence of safety standard ISO 26262 underlines the increasing importance of safety in automotive software. As well as functional requirements, hard real-time requirements are of crucial importance to safety-related software as there is a need to prove that the system functionality is fulfilled, even in worst-case scenarios. Measurement-based WCET (Worst-Case Execution Time) analysis combines on-target timing measurements with static analysis of program structure to calculate predicted worst-case paths and times. This is in contrast to traditional end-to-end timing measurements, which give no confidence that the worst-case path is actually tested and no insight into the location of any timing problems that do emerge.

ISO 26262 is the actual standard for Functional Safety of automotive E/E (Electric/Electronic) systems. One of the challenges in the application of the standard is the distribution of safety related activities among the participants in the supply chain. In this paper, the concept of a Safety Element out of Context (SEooC) development will be analyzed showing its current problematic aspects and difficulties in implementing such an approach in a concrete typical automotive development flow with different participants (e.g. from OEM, tier 1 to semiconductor supplier) in the supply chain. The discussed aspects focus on the functional safety requirements of generic hardware and software development across the supply chain where the final integration of the developed element is not known at design time and therefore an assumption based mechanism shall be used.