Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Defect Flow in a Test System

IP.com Disclosure Number: IPCOM000100673D
Original Publication Date: 1990-May-01
Included in the Prior Art Database: 2005-Mar-16
Document File: 2 page(s) / 73K

Publishing Venue

IBM

Related People

Dorrington, AW: AUTHOR

Abstract

A generic test system defect flow is described that can be tailored to individual products via process controls.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Defect Flow in a Test System

       A generic test system defect flow is described that can
be tailored to individual products via process controls.

      Historically, defect handling within a test system has been
structured around a specific product or the test system itself.
Bringing new products on-line would necessitate changes to the test
system architecture or assurances that the new product meets certain
error- reporting criteria.

      The defect flow has been designed so that isolation, analysis,
and repair actions can be tailored to the product being tested.  This
is accomplished through a modular design that serially relinquishes
control to product specific modules.  The architecture allows the
productspecific modules to establish their own level of complexity.

      At their extreme, the product-specific modules can utilize the
defect-handling support so that isolation, analysis, repair action
logging, and verification are accomplished entirely by the system.

      In its most simplistic state, the product-specific code can be
virtually NO-OPed so that isolation, analysis, and repair action
logging is done entirely by the test technician.  The technician can
also perform manual verification before logging the repair action.
The system will always perform verification whenever a repair action
is logged, regardless of the technician's action previous to the log.

      The defect flow consists of five modules (see the figure)
executing under control of the product test driver.
-  EIM - This is the first module to gain control after a defect
symptom has been logged by AUTOTEST.  This module controls th...