Rely on Traceability When the Specs Keep Changing. Case Study: Automotive IP & SoCs
How do you assure the integrity of a design when end-system requirements are frequently changed? This is a common issue with products that are subject to expectations that evolve in response to technological innovation – a perfect example is the automotive industry, where stringent requirements for functional safety systems are constantly being updated in response to rapid evolution in assisted driving (ADAS). This white paper explains the best practices for traceability of automotive functional safety requirements flow (definition, implementation, verification, and validation) when designing IP or SoC for ADAS. Depending on the Automotive Safety Integrity Level (ASIL), the functional safety requirements can vastly change.
Please disable any pop-up blockers for proper viewing of this Whitepaper.