Realization phase verification

It would be difficult to enumerate all Ron s scientific achievements in the field of polymer thermodynamic. One can name the generalizations of the Flory-Huggins Gibbs energy leading to the prediction and experimental verification of coexistence of three phases in pseudobinary system with sufficiently broad distribution or, the analysis of the functional form of the interaction term leading to the appearance of off-zero critical concentration , at variance with zero critical concentration associated with theta-temperature. Thanks largely to Ron, polymer scientists realize that the cloud point curve is not the binodal and its maximum or minimum are not identical with the critical temperatures. 

Generally, it is only possible to conduct a functional analysis as a top down approach since the function of a certain hardware element needs to be known first before the cause of failure can be derived. On the other hand, for the failure observation of sheer technical (realized) elements, such as components or structural elements, the failure of elements and also random hardware failures can be inferred from the characteristics of the elements. The failure effects can then be referred to as inductive analysis. However, as a result only the inductive analysis truly addresses the effects of random hardware failure. By a deductive approach only requirements for random hardware-failure could be elaborated so that required failure rates and related diagnostics could be specified. By adequate verifications and tests the fulfillment of given metric requirements could be shown. This will widely indicate a mix of inductive and deductive analysis, whereas the lower level is designed inductively and in the upper level the technical malfiinctional behaviour is described functionally, so that the consistency (see Figs. 4.35 and 4.36 analysis phase) could be assured. 

Does the verification really only happen during the development of the requirements Is the development of requirements completed before the realization Obviously not When the result is validated and all requirements are correctly implemented at the product, there are always new aspects that can occur in the usage phase, which haven t been sufficiently considered. 

---