loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
12th IEEE European Test Symposium (ETS'07)
Freiburg, Germany
May 20-May 24
ISBN: 0-7695-2827-9
ASCII Text
x 
 
Ben Bennetts, "Electronics Design-for-Test: Past, Present and Future," European Test Symposium, IEEE, pp. 4, 12th IEEE European Test Symposium (ETS'07), 2007.
 
 
BibTex
x
 
@article{ 10.1109/ETS.2007.21,
author = {Ben Bennetts},
title = {Electronics Design-for-Test: Past, Present and Future},
journal ={European Test Symposium, IEEE},
volume = {0},
year = {2007},
issn = {1530-1877},
pages = {4},
doi = {http://doi.ieeecomputersociety.org/10.1109/ETS.2007.21},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - CONF
JO - European Test Symposium, IEEE
TI - Electronics Design-for-Test: Past, Present and Future
SN - 1530-1877
SP
EP
A1 - Ben Bennetts,
PY - 2007
KW - null
VL - 0
JA - European Test Symposium, IEEE
ER -
 
Ben Bennetts, ex-DFT Consultant, UK
Do you know how many ENIAC vacuum tubes were replaced every day during its heyday? What did it teach us about Test, or Design-For-Test? Did Eldred really invent the stuck-at fault model in 1959? Is 99.999% fault cover all it?s cracked up to be or are we fooling ourselves? Are we better off with 115% or even 80%? Where did Design-For-Test come from? Where is it now? Where?s it heading? Is it true that boundary scan is the panacea of test? What are all these new Joint Test Action Groups -- Internal, System and compact? Are they boondoggles, or are they serious?
Citation:
Ben Bennetts, "Electronics Design-for-Test: Past, Present and Future," ets, pp.4, 12th IEEE European Test Symposium (ETS'07), 2007
Usage of this product signifies your acceptance of the Terms of Use.