scispace - formally typeset
Search or ask a question

Showing papers on "Design for testing published in 1981"


Journal ArticleDOI
TL;DR: A technique for modifying networks so that they are capable of self test is presented, partitioning the network into subnets with sufficiently few inputs that exhaustive testing of the subnetworks is possible.
Abstract: A technique for modifying networks so that they are capable of self test is presented. The major innovation is partitioning the network into subnetworks with sufficiently few inputs that exhaustive testing of the subnetworks is possible.

246 citations


Journal ArticleDOI
Sridhar1, Hayes
TL;DR: I-testability ensures that identical test responses can be obtained from every cell in an ILA, and thus simplifies response verification, and the application of C- and I-testing to the design of bit-sliced (micro-) computers is investigated.
Abstract: Bit-sliced systems are formed by interconnecting identical slices or cells to form a one-dimensional iterative logic array (ILA). This paper presents several design techniques for constructing easily testable bit-sliced systems. Properties of ILA's that simplify their testing are examined. C-testable ILA's, which require a constant number of test patterns independent of the array size, are characterized, and a method for making an arbitrary ILA C-testable is presented. A new testability concept for arrays called I-testability is introduced. I-testability ensures that identical test responses can be obtained from every cell in an ILA, and thus simplifies response verification. I-testable ILA's are characterized, as well as CI-testable arrays, which are simultaneously C- and I-testable. A method of making an arbitrary ILA CI-testable is presented. The application of C- and I-testing to the design of bit-sliced (micro-) computers is investigated. For this purpose a family of easily testable processor slices is described. The design of a self-testing CPU based on I-testing is discussed, and compared with a more conventional self-testing design.

94 citations


Journal ArticleDOI
E. I. Muehldorf1, A. D. Savkar1
TL;DR: The paper concentrates on the testing of logic components and presents in-depth discussions of the methods of fault modeling, test pattern generation, fault simulation, and design for testability.
Abstract: The development of large scale integration (LSI) testing is reviewed. The paper concentrates on the testing of logic components and presents in-depth discussions of the methods of fault modeling, test pattern generation, fault simulation, and design for testability. It is shown how these methods are used in the design of components and how they can be used in support of design automation. Finally, a brief account of test equipment and test data preparation is given.

60 citations


Journal ArticleDOI
TL;DR: Automated layout of PCBs and LSI chips is a successful operation; testing is an active area of development; DA tools, however, are seldom used in logic design.
Abstract: Automated layout of PCBs and LSI chips is a successful operation; testing is an active area of development. DA tools, however, are seldom used in logic design.

23 citations


Journal ArticleDOI
TL;DR: In this paper, a set of statistically based experiments is developed to estimate near optimal designs, and an analysis of variance is used to indicate the relative importance of various decisions in a system design.
Abstract: Design automation at the register transfer level of design is still in its infancy, and it is not yet completely understood what the appropriate measures used in direction the automated design process should be. To establish these measures, results of these design automation systems must be compared with some near optimal designs. A set of statistically based experiments is developed to estimate near optimal designs. A method is demonstrated for gathering data on designer performance, specifically at the different levels of systems design, and in general for calibration of other design automation systems where the intuitive designer still performs more capably than the present design algorithms. An analysis of variance is used to indicate the relative importance of various decisions in a system design. It is shown that the algorithm to be implemented and the hardware design style account for 90 percent of the variation in the results. Thus, selecting the design style (e.g., distributed, microprocessor, pipelined, etc.) is the most important parameter for a design automation system.

17 citations


Journal ArticleDOI
Priester1, Clary
TL;DR: New measures for both testability and test complexity which are quantitative, capable of handling multiple faults, and have a well-defined interpretation are introduced.
Abstract: The failure analysis of analog electronic systems is characterized by numerous, difficult problems. Assessing the testability and test complexity of a given system is one such problem. In fact, robust, quantitative measures of these important features have not been available to the analog testing community. This paper introduces new measures for both testability and test complexity which: 1) are quantitative, 2) are capable of handling multiple faults, and 3) have a well-defined interpretation. These measures are based upon published results from optimal experiment designs as developed in the discipline of systems identification. Parameter testability is defined in terms of information (in the sense of Fisher) return, while test complexity is functionally related to the experiment time required to achieve specified accuracy with regard to the uncertain parameters of interest. Thus both of the new measures introduced depend, not only upon the specific system at hand, but also upon the experimental conditions used in performing the tests. The results of this approach lead to quantitative measures that have optimality features based upon the Cramer–Rao bound.

6 citations


Proceedings Article
M.T.M.R. Segers1
01 Sep 1981
TL;DR: In this article, the question "why design for testability?" is answered by discussing some existing test philosophies, such as exhaustive testing, functional testing and structural testing, with regard to their usefulness for VLSI circuits.
Abstract: The question ``why design for testability?'' will be answered by discussing some existing test philosophies. Exhaustive testing, functional testing and structural testing will be treated, also with regard to their usefulness for VLSI circuits. There is no general agreement on how to design for testability. Various approaches exist, and each has its specific applications. Some of these approaches will be discussed in detail, also regarding the influence of the complexity on necessary CAD tools for test pattern generation.

1 citations


Journal ArticleDOI
John Monk1
TL;DR: This paper outlines some of the detail of hardware design essential for even simple peripheral equipment in microcomputer-based products, using as an example of a small computer designed for educational purposes.

1 citations