Presenting Compilation of Redesign Plans and Diagnosis Rules

Intro ] [ 01-slide ] 02-slide ]
03-slide ] 04-slide ] 05-slide ]
06-slide ] 07-slide ] 08-slide ]
09-slide ] 10-slide ] 11-slide ]
12-slide ] 13-slide ] 14-slide ]
15-slide ] 16-slide ] 17-slide ]
18-slide ] 19-slide ]

Up: Presentations ]

Generally speaking...

Time Frame: 1990 - 1992

Why use rules instead of a model?
  • Optimize problem solving performance for specific tasks
  • Simplify necessary reasoning
  • Trade generality for efficiency
  • Task serves to focus knowledge acquisition
Weaknesses
  • intensive effort to construct rule base manually
  • non-reusable: virtually no rules are transferable to a different task
  • brittleness: if a situation is not anticipated, results are unpredictable
 

by: Keith A. Pray
Last Modified: August 14, 2004 12:22 AM
© 2004 - 1975 Keith A. Pray.
All rights reserved.