Knowledge Acquisition without Analysis
This paper suggests that a distinction between knowledge acquisition methods should be made. On the one hand there are methods which aim to help the expert and knowledge engineer analyse what knowledge is involved in solving a particular type of problem and how this problem solving is carried out. These methods are concerned with classifying the different types of problem solving and providing tools and methods to help the knowledge engineer identify the appropriate approach and ensure nothing is omitted. A different approach to knowledge acquisition focuses on ensuring incremental addition of validated knowledge as mistakes are discovered (validated knowledge here means only that the earlier performance of the system is not degraded by the addition of new knowledge). The organisation of this knowledge is managed by the system rather than the expert and knowledge engineer. This would seem to correspond to human incremental development of expertise. From this perspective task analysis is a secondary activity related to explanation and justification not acknowledge acquisition. Ripple Down Rules is a limited example of this approach. The paper considers the possibility of extending this approach to make it more generally applicable.