Comparing software design for testability to hardware DFT and BIST

AUTOTESTCON (Proceedings)

Volumn , Issue , 2011, Pages 272-278

  Alanen, Jack ^a   Ungar, Louis Y ^b  

^a CALIFORNIA STATE UNIVERSITY   (United States)

^b ATE Solutions Inc   (United States)

Author keywords

BIST; design for testability; DFT; hardware test; software design for testability; software test

Indexed keywords

DEBUGGING SOFTWARE; DFT; HARDWARE DESIGN; HARDWARE FAULTS; HARDWARE SYSTEM; HARDWARE TEST; SOFTWARE COMMUNITY; SOFTWARE COMPONENT; SOFTWARE FAULT; SOFTWARE TEST; TESTABILITY;

BUILT-IN SELF TEST; COMPUTER SOFTWARE MAINTENANCE; DESIGN FOR TESTABILITY; DIAGNOSIS; HARDWARE; PROGRAM DEBUGGING; SOFTWARE TESTING;

SOFTWARE DESIGN;

EID: 81055138952     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/AUTEST.2011.6058776     Document Type: Conference Paper

References (5)

1. US Navy, MIL-HDBK-2165 Testability Handbook for Systems & Equipment, July 1995.
2. IEEE Standard 1149.1-1990 "IEEE Standard Test Access Port and Boundary-Scan Architecture," New York, 1990.
3. A.T.E. Solutions, Inc., The Testability Director v 3.2 software, www.besttest.com/OurProducts/TestabilityDirector/, 2005-2009.
4. Surface Mount Technology Association (SMTA) and Testability Management Action Group (TMAG), SMTA and TMAG Testability Guidelines 2008TP-101D, SMTA Minneapolis, MN 2008.
5. Bret Pettichord, "Design for Testability," presentation at the Pacific Northwest Software Quality Conference, Portland, OR, October 2002, 28 pp.