Proceedings Fourth International Conference on Tools With Artificial Intelligence TAI '92
DOI: 10.1109/tai.1992.246425
|View full text |Cite
|
Sign up to set email alerts
|

Comparative evaluation of expert system testing methods

Abstract: Effective testing (validation, verification and evaluation) for expert systems is becoming important. In this paper we do a comparative evaluation of blackbox, white-boz, consistency and completeness testing methods based on the criteria of eflectiueness, robustness and cost. Testing methods are evaluated using "life-cycle mutation testing" on a VLSI manufacturing diagnostic expert system.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

2
5
0

Publication Types

Select...
5

Relationship

0
5

Authors

Journals

citations
Cited by 8 publications
(7 citation statements)
references
References 14 publications
2
5
0
Order By: Relevance
“…This confirms the previous studies which have used manual or automated versions of these kinds of verification. In particular, our results agree with the Concordia and SAIC studies of consistency and completeness checking (Preece & Shinghal, 1992;Miller, Hayes & Mirsky, 1993), and the SRI and Minnesota studies of testing (Rushby & Crow, 1990;Kirani et al, 1992).…”
Section: Discussionsupporting
confidence: 88%
See 4 more Smart Citations
“…This confirms the previous studies which have used manual or automated versions of these kinds of verification. In particular, our results agree with the Concordia and SAIC studies of consistency and completeness checking (Preece & Shinghal, 1992;Miller, Hayes & Mirsky, 1993), and the SRI and Minnesota studies of testing (Rushby & Crow, 1990;Kirani et al, 1992).…”
Section: Discussionsupporting
confidence: 88%
“…In view of this, our fault classes are based on the implementation. They are similar to those of the SAIC study (Miller, Hayes & Mirsky, 1993), and a subset of those in the Minnesota study (Kirani et al, 1992) (which defined fault classes for requirements and design documents also). We accept that faults may be introduced prior to implementation (e.g.…”
Section: Classes Of Faultsupporting
confidence: 57%
See 3 more Smart Citations