3
General overview
This section shall contain a brief description ofthe background of and/or reason forthisdevelopment project.
Describebriefly the system being developed.If the product/itemdeveloped at this level is part of a system, alsobriefly describethe products’relationship to the system.
Mark unused sections of this document as “NOTAPPLICABLE”, do not remove the paragraph heading.
Text marked with a<green background>is to be replaced by something specific. This shall be used if there are specific keywords within standardized paragraphs that shall be replaced when creating the Work Product from the template.
Blue text in italic is information/explanation directed to the issuer of the document.Before releasing theWork Product (document)all blue italic text must be removed.
6
State reference to any Non Disclosure Agreement (NDA) here.
7
List all safety activities in this paragraph. State which party (XXXAor supplier) is responsible “R” and supporting “S” for each activity.
The DIA is a bilateral contract determining each party’s interfaces and responsibilities.
The parties this DIA applies to are:
XXXXAutomotive (named “XXXA” hereafter)
Development Interface Agreement - DIA
1
1Table of Contents2
2Revision History3
3Introduction4
3.1General overview4
3.2About this document4
3.3Abbreviations4
4References6
Abbreviations
Abbreviation
Applicable
TBC
To Be Confirmed
TBD
To Be Defined
4
Ref
Id
Issue
Document Name
[R1]
5
Define here the background to why this DIA has been established.
5Background to DIA7
6Reference to NDA7
7Processes7
8Work Products7
9Responsibilities8
10Interfaces8
10.1Milestones9
11Combined activities9
11.1Combined confirmation reviews9
and
<supplier name>
This DIA shall be put under configuration control and updated if necessary during the course of the development project.
For further information and recommendation of how to set up this DIA please refer to ISO 26262-8:5.4.
About this document
This Development Interface Agreement (DIA) applies to the development work carried out for the above stated development project where the system contains software (Automotive Spice) and/or requirements regarding functional safety (ISO 26262).
11.2Planning of Safety Assessments9
12Communication9
13Responsibilities after SOP9
2
Version
ECN no.
Changed by
Change from last version
01
The change history shall be a detailed enough description of what sections that have been changed since the last version. Depending on the changes that have been made it may be necessary to describe the changes more in detail.