Content deleted Content added
Okeyes (WMF) (talk | contribs) Added tags to the page using Page Curation (refimprove, technical) |
GoingBatty (talk | contribs) m WPCleaner v1.19 - Repaired 2 links to disambiguation page - (You can help) - Breaker, Flasher, 2 to be fixed - REM, Robustness / Fixed using WP:WCW - Reference before punctuation - Spelling and typography |
||
Line 3:
'''Robustness validation''' is a skills strategy with which the [[
== History ==
At the beginning of the 1970s a relatively high failure rates of electronic components were tolerable in [[automobile]]s, because they replaced mechanical components, which had a much higher [[failure rate]]. The underlying failure rates of bimetallic [[Automotive lighting|flasher]]s were 10% per year and the lifetime of mechanical [[
The establishment of the Automotive Electronic Council ([[Automotive Electronics Council | AEC]]) 1994 by [[Ford]], [[Chrysler]], [[General Motors | GM]] - [[ACDelco | Delco]] was also the Starting point for the AEC-Q100 qualification process, <ref> Automotive Electronic Council's Stress Test Qualification for Integrated Circuits, AEC Q100, Rev. G, 2007, to [http://www.aecouncil.com/AECDocuments.html aecouncil.com] </ref>
Due to the development of [[automotive]] and the ever-increasing complexity of vehicles associated with the demands for lower error rates of this qualification process
== Initiators and participants ==
Line 40:
Today's standard qualification procedures for electronic components, assemblies and components for the automotive industry is based on the use of standardized tests at the end of the product development of parts and components. In contrast, Robustness Validation is a process that includes the entire product development process, as well as mass production. The qualification of the components based on the robustness analysis is thus implicit. With the introduction of robustness validation, priorities are focused on the development process again. The aim is to reduce the construction error's during the later phases of the project, which means ''front loading'' measures in the product development time line process.
It is necessary that the requirements from the product to the next level of the value chain be broken down in order to meet specific statements about possible vulnerabilities. Back in the early phases of the project is the knowledge (
== Other applications of robustness validation ==
|