The intricacies of a Development Interface Agreement, how it fits in the development flow, and outlines the typical activities during a distributed development process.
Automotive functional safety System-on-Chips (SoCs) for Advanced Driver Assistance Systems (ADAS) contain several complex Intellectual Property (IP) cores. The IP cores are developed as a Safety Element out of Context (SEooC), meaning the context of the end application is not fully known at delivery time. In addition, IP development might be distributed across the globe. To reduce the risk of functional safety failure, standards like ISO 26262[1] have defined appropriate requirements, processes, and methods that are applicable during the distributed development of the safety product and its sub-elements. To guide the functional safety SoC and IP development, the ISO 26262 standard contains several parts that define the high-level processes and supporting processes. One such supporting process[2], the Development Interface Agreement (DIA), is a work product that defines the interactions and dependencies between customers and suppliers for the distributed development activities. DIA applies during the development phase of the product life cycle and is necessary in a distributed development activity, where customers and suppliers for the development activities are separated geographically. When an SoC comprises of numerous sub-elements such as IP, the SoC integrator needs to execute several DIAs for each IP supplier. This whitepaper explains the intricacies of a Development Interface Agreement, how it fits in the development flow, and outlines the typical activities during a distributed development process.
Click here to continue reading.
 |
 |
 |
 |
 |
 |
 |
 |
 |  |
Leave a Reply