One of the most significant innovations in test programming is Giordano Automation's Concurrent Engineering Tool Set (CETS). CETS consists of a development tool and a run-time tool. The run-time tool, Diagnostician, provides automated diagnostics in the test environment, and is seamlessly integrated into any test system configuration. The development tool, the Diagnostic Profiler, assists the engineer in preparing the run-time diagnostic knowledge base.
The Diagnostician is an implementation of a new paradigm for diagnostics: model-based reasoning. Model-based reasoning means that a diagnostic model of a system or item, derived from design data, serves as the basis for diagnostic reasoning. The diagnostic model is independent of the source of test result data and independent of the sequence of tests that are run. The Diagnostician contains a UUT diagnostic model in the form of a connectivity matrix which represents the propagation of faults (rows in the matrix) to observable measurement locations and the coverage of tests that Pass or Fail (columns in the matrix). When used in run-time, the software algorithms and knowledge base (matrix) operate to isolate faults without troubleshooting sequences and without hard-coded diagnostic test programs.

In the new paradigm, a model-based diagnostic software object called a Diagnostician is used in lieu of programmed No-Go flow paths. In run-time the Diagnostician provides dynamic fault isolation without complex diagnostic test programs. In run-time, the object or Diagnostician , is utilized to interact in real time with the test results to perform fault isolation. The concept of object oriented programs is taken full advantage of by dealing with the diagnostic logic as an independent entity in the test program. By thus separating diagnostic logic from test, the test program becomes significantly simpler. Further, the diagnostic logic contained in the software object can be rehosted to any platform without any problem.

Using the Diagnostician, the fundamental culture of diagnostics has been changed. Tests are discrete software programs and routines which may be independently executed. The interpretation of the tests is done by the Diagnostician which dynamically, on-the-fly, interprets test information based upon all information it receives in any order. The Diagnostician makes use of Artificial Intelligence in the form of Set Covering Algorithms that interpret the Cones of Evidence produced by both pass and fail data from the test results. In this type of test program structure, no code is duplicated. The list of faults is clearly identified and diagnostic data for each fault is kept in one spot. Model-based reasoning makes diagnostics affordable for limited production testing and effective for complex system and board test.
What is the Software Structure of the Diagnostician?
The Diagnostician is structured as a library of functions. This library of functions is compiled to different operating systems. For example, for Windows 3.x, the Diagnostician is compiled as a Dynamic Link Library. This allows for tremendous flexibility for integration onto actual run-time platforms and software systems.
Show me Tool Set for Generation of Knowledge Bases
CETS Advantages / Users / Questions and Answers