Browse Prior Art Database

Hardware Functional Compatibility Test Methodology

IP.com Disclosure Number: IPCOM000037209D
Original Publication Date: 1989-Nov-01
Included in the Prior Art Database: 2005-Jan-29
Document File: 3 page(s) / 48K

Publishing Venue

IBM

Related People

Pancoast, S: AUTHOR [+2]

Abstract

When a new PC or PS/2 system is developed, the system must go through a series of tests to ensure hardware compatibility with the previous PC systems. This testing is often done by testing a variety of functions via software applications or custom applications. The testing would often be done by a variety of test groups and there was little way to track what functions were tested by the various groups and which functions had not been tested. The task of making a list of functions with all the various permutations of software and hardware seemed insurmountable. There continued to be a need to map the coverage performed by the various test groups in order to determine what areas had not been tested.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 3

Hardware Functional Compatibility Test Methodology

When a new PC or PS/2 system is developed, the system must go through a series of tests to ensure hardware compatibility with the previous PC systems. This testing is often done by testing a variety of functions via software applications or custom applications. The testing would often be done by a variety of test groups and there was little way to track what functions were tested by the various groups and which functions had not been tested. The task of making a list of functions with all the various permutations of software and hardware seemed insurmountable. There continued to be a need to map the coverage performed by the various test groups in order to determine what areas had not been tested.

This article describes a methodology for performing the hardware compatibility testing along with a method for tracking the areas tested. This methodology makes use of two matrices to define the functional characteristics of the system and the various permutations or configurations of interest. The first matrix is called the functional test point (FTP) matrix, and the second matrix is called the configuration matrix. The methodology is based on testing various aspects of the hardware system and comparing the results to an existing system (target system) to which the system should be compatible. When a discrepancy occurs the hardware system under test should be modified to yield similar results as the target system. This testing procedure is based on the following methodology. Methodology: The functional behavior of a system can be represented

by a finite

number of FTPs within a given system configuration.

FTPs may vary between various system configurations.

A FTP consists of functional characteristics, behavior,

attributes,

modes, etc. that can be observed, mea...