Guidelines for the Verification and Validation of Expert System Software and Conventional Software

This eight-volume report presents guidelines for performing verification and validation (VV they are also applicable to object-oriented programming systems, rule-based systems, frame-based systems, model-based systems, neural nets, genetic algorithms, and conventional software systems. This is because many of the components of AI systems are implemented in conventional procedural programming languages, so there is no real distinction. The report examines the state of the art in verifying and validating expert systems. V&V methods traditionally applied to conventional software systems are evaluated for their applicability to expert systems. One hundred fifty-three conventional techniques are identified and evaluated. These methods are found to be useful for at least some of the components of expert systems, frame-based systems, and object-oriented systems. A taxonomy of 52 defect types and their delectability by the 153 methods is presented. With specific regard to expert systems, conventional V&V methods were found to apply well to all the components of the expert system with the exception of the knowledge base. The knowledge base requires extension of the existing methods. Several innovative static verification and validation methods for expert systems have beenmore » identified and are described here, including a method for checking the knowledge base {open_quotes}semantics{close_quotes} and a method for generating validation scenarios. Evaluation of some of these methods was performed both analytically and experimentally.« less

[1]  Jag Sodhi Software Requirements Analysis and Specification , 1992 .

[2]  J. E. Huffman,et al.  Partially automated in-line documentation (PAID): design and implementation of a software maintenance tool , 1988, Proceedings. Conference on Software Maintenance, 1988..

[3]  Robert Dunn,et al.  Software Defect Removal , 1984 .

[4]  Sidney L. Smith,et al.  Guidelines for Designing User Interface Software , 1986 .

[5]  Paul T. Ward,et al.  The transformation schema: An extension of the data flow diagram to represent control and timing , 1986, IEEE Transactions on Software Engineering.

[6]  G. H. Chisholm,et al.  Formal System Specifications : a Case Study of Three Diverse Representations , 1990 .

[7]  F. A. Mohammed,et al.  A survey of software functional testing methods , 1991, SOEN.

[8]  Daniel E. O'Leary,et al.  Validating the weights in rule-based expert systems: a statistical approach , 1988 .

[9]  John Rushby,et al.  An Introduction to Formal Specification and Verification using EHDM , 1991 .

[10]  Anneliese Amschler Andrews,et al.  Software engineering - methods and management , 1990, Int. CMG Conference.

[11]  William E. Howden,et al.  Functional Program Testing , 1978, IEEE Transactions on Software Engineering.

[12]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[13]  Watts S. Humphrey,et al.  Managing the software process , 1989, The SEI series in software engineering.

[14]  Michael S. Deutsch Software Verification and Validation: Realistic Project Approaches , 1981 .