|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Les Hatton, "N-Version Design Versus One Good Version," IEEE Software, vol. 14, no. 6, pp. 71-76, November/December, 1997. | |||
| BibTex | x | ||
| @article{ 10.1109/52.636672, author = {Les Hatton}, title = {N-Version Design Versus One Good Version}, journal ={IEEE Software}, volume = {14}, number = {6}, issn = {0740-7459}, year = {1997}, pages = {71-76}, doi = {http://doi.ieeecomputersociety.org/10.1109/52.636672}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - N-Version Design Versus One Good Version IS - 6 SN - 0740-7459 SP71 EP76 EPD - 71-76 A1 - Les Hatton, PY - 1997 KW - diversity KW - n-version KW - formal methods KW - defect density KW - reliability VL - 14 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/52.636672
Evidence indicates that n-version development techniques are more reliable than producing one "good" version-and cost effective in the long run. The author concludes that diverse, independent channels used in parallel are significantly superior to even the current state of the art, especially in situations where cost of failure is high.
Index Terms:
diversity, n-version, formal methods, defect density, reliability
Citation:
Les Hatton, "N-Version Design Versus One Good Version," IEEE Software, vol. 14, no. 6, pp. 71-76, Nov.-Dec. 1997, doi:10.1109/52.636672
Usage of this product signifies your acceptance of the Terms of Use.

