Content deleted Content added
Kj cheetham (talk | contribs) Changed section order as per WP:MOS |
m Removing link(s) Wikipedia:Articles for deletion/Robustness (morphology) closed as soft delete (XFDcloser) |
||
| (2 intermediate revisions by 2 users not shown) | |||
Line 1:
{{Multiple issues|{{more citations needed|date=October 2012}}{{technical|date=October 2012}}
}}
'''Robustness validation''' is a skills strategy with which the
▲'''Robustness validation''' is a skills strategy with which the [[Robustness (morphology)|Robustness]] of a product to the loading conditions of a real application is proven and targeted statements about risks and [[Reliability engineering|reliability]] can be made. This strategy is particularly for use in the [[automotive industry]] however could be applied to any industry where high levels of reliability are required
== History ==
Line 21 ⟶ 19:
Robustness Validation is used to assess the reliability of electronic components by comparing the specific requirements of the product with the actual "real life values". With the introduction of this methodology, a specific list of requirements (usually based on the [[Original Equipment Manufacturer|OEM]]) is required. The requirements for the product can be defined in the environmental requirements (mission profiles) and the functional requirements (use cases).
=== Mission
<!--[[Image:Potato_Diagram.jpg | thumb | Robustness for robustness validation based on the comparison of the application requirements, specification and technological limits of the component <ref name="RVHB_SC" />]]-->
Line 27 ⟶ 25:
The mission profiles describes the loads and stresses acting on the product in actual use. These are, for example, changes in temperature, temperature profile, vibration and working of electrical and mechanical fields, or other environmental factors. It is important to specify the relevant stressors in their nature, intensity and duration of exposure, as well as the mix as closely as possible. With these details it is possible, within specified accuracy, projections regarding reliability of application and its components in field applications.
=== Use
The use cases describe the nature and frequency of the operating conditions for which the product is designed. One should make sure that this addition to the normal operation of the possible cases of special operation and emergency operation. Intentional abuse is not included.
Line 35 ⟶ 33:
The lifetimes can be hedged by specific, tailored to the application and the failure mechanisms, determined tests. An essential process are [[End of life test]]s. From the distance of the requirements to the test results, the reliability and robustness of the device can be determined.
== Product
<!--[[Image:RV_flow.jpg | thumb | upright | Robustness Validation schedule of product development to mass production <ref name="RVHB_SC" />]]-->
| |||