Learn best practices for traceability of automotive functional safety requirements flow when designing IP or SoC for ADAS.
Automotive functional safety systems continue to incorporate complex features to meet wide range of consumer demands. Developing functional safety systems, including all the components such as the system-on-chip (SoC) and IP, hinges on the ability to meet the stringent automotive functional safety requirements such as definition, implementation, verification, and validation. Functional safety SoCs use a large number of IP blocks that must be developed according to the Safety Element Out of Context (SEooC) method as defined by the ISO 26262 standard. Since functional safety system requirements are complex and distributed in nature, it is critical to ensure the large number of complex and interdependent requirements are correctly distributed, allocated, refined, implemented, and verified. Such requirements must be bidirectionally traceable from the time the SoC and IP are designed and implemented in the system to the time the system is delivered.
This white paper explains the best practices for traceability of automotive functional safety requirements flow when designing IP or SoC for ADAS. Depending on the Automotive Safety Integrity Level (ASIL), the functional safety requirements can vastly change.
Click here to continue reading.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Leave a Reply