Robustness validation: Difference between revisions

Content deleted Content added
m WPCleaner v1.33 - Repaired 1 link to disambiguation page - (You can help) - Lessons Learned, 2 to be fixed - REM, Robustness
JIK1975 (talk | contribs)
No edit summary
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 (e.g., from knowledge bases Lessons Learned) gained from previous projects in order to avoid known vulnerabilities. Using the analysis of the changes of the new product and the use of different methods, such as [[Rem|REM]]{{Disambiguation needed|date=October 2012}}, [[DRBFMDesign Review Based on Failure Mode|RBFM]]'' or'' design reviews, new potential vulnerabilities are identified early in order to make potential risks
 
== Other applications of robustness validation ==