Development Interface Agreement

https://is1-ssl.mzstatic.com/image/thumb/Podcasts211/v4/63/cb/2d/63cb2dd3-abc3-8bef-e8ea-12e57f67136a/mza_1236235421606985468.jpg/600x600bb.jpg

Applied FuSa

Wolfgang Freese

8 episodes

20 hours ago

According to ISO 26262, an impact analysis must be performed at the beginning of a project to identify work products that can be tailored, provided the project is based on a predecessor project. Differences between the two projects are assessed with respect to the following three categories:

Changed requirements;
Revised design; and
New integration environment.

In this episode, we will not only introduce the method itself, but also explain why an impact analysis makes sense not just at the beginning of a project.

How To

Education

RSS

All content for Applied FuSa is the property of Wolfgang Freese and is served directly from their servers with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.

Changed requirements;
Revised design; and
New integration environment.

In this episode, we will not only introduce the method itself, but also explain why an impact analysis makes sense not just at the beginning of a project.

How To

Education

Development Interface Agreement

Applied FuSa

16 minutes 22 seconds

1 month ago

Development Interface Agreement

Hello and welcome to a new episode of “Applied FuSa,” a podcast for FuSa pragmatists.

The DIA, or Development Interface Agreement, is often used as a document whose sole purpose is to allocate responsibility for FuSa work products between customer and supplier. Who is supposed to develop what, and in what form – if any – should the results be exchanged. That’s it.

That’s it? Does that really meet the requirements of ISO 26262? Or do those requirements perhaps go beyond that? Let’s take a closer look.