Design validation
From apppm
(Difference between revisions)
| Line 1: | Line 1: | ||
== Abstract == | == Abstract == | ||
| − | The Ford company realized in 1957 that making a perfectly functional car was not enough to achieve commercial success. Indeed, nobody wanted to buy it, and the company suffered a loss of 250 million dollars. The goal of validation is to ensure that a design meets the user's needs, and it is just as important as producing a functional design. Indeed, an inadequate validation will result in designing an undesired or unsuitable product, wasting significant amounts of resources, money, and time. The increase in complexity and duration of design projects often causes the initial objectives to get forgotten. Validation closes the production loop and ensures that the functionality intended for the user is fulfilled. Traditionally, validation is performed at the end of the product design process, through direct user testing, among other methods. However, a newer validation approach is called User-Centered Design and consists of early user integration in the design process, which spreads out the validation in time. | + | The Ford company realized in 1957 that making a perfectly functional car was not enough to achieve commercial success. Indeed, nobody wanted to buy it, and the company suffered a loss of 250 million dollars <ref name="R1">. The goal of validation is to ensure that a design meets the user's needs, and it is just as important as producing a functional design. Indeed, an inadequate validation will result in designing an undesired or unsuitable product, wasting significant amounts of resources, money, and time. The increase in complexity and duration of design projects often causes the initial objectives to get forgotten. Validation closes the production loop and ensures that the functionality intended for the user is fulfilled. Traditionally, validation is performed at the end of the product design process, through direct user testing, among other methods. However, a newer validation approach is called User-Centered Design and consists of early user integration in the design process, which spreads out the validation in time. |
| − | <div class="csl-entry">Bahill, A. T., & Henderson, S. J. (2005). Requirements Development, Verification, and Validation Exhibited in Famous Failures. <i>Www.Interscience.Wiley.Com). Syst Eng</i>, <i>8</i>, 1–14. https://doi.org/10.1002/sys.20017</div> | + | == Reference == |
| + | |||
| + | <references > | ||
| + | |||
| + | <ref name="R1"> <div class="csl-entry">Bahill, A. T., & Henderson, S. J. (2005). Requirements Development, Verification, and Validation Exhibited in Famous Failures. <i>Www.Interscience.Wiley.Com). Syst Eng</i>, <i>8</i>, 1–14. https://doi.org/10.1002/sys.20017</div> | ||
Revision as of 18:10, 10 February 2022
Abstract
The Ford company realized in 1957 that making a perfectly functional car was not enough to achieve commercial success. Indeed, nobody wanted to buy it, and the company suffered a loss of 250 million dollars Cite error: Closing </ref> missing for <ref> tag
