Copyright (c) 2013 John L. Jerz

Knowledge Acquisition in Practice (Milton, 2007)

Home
A Proposed Heuristic for a Computer Chess Program (John L. Jerz)
Problem Solving and the Gathering of Diagnostic Information (John L. Jerz)
A Concept of Strategy (John L. Jerz)
Books/Articles I am Reading
Quotes from References of Interest
Satire/ Play
Viva La Vida
Quotes on Thinking
Quotes on Planning
Quotes on Strategy
Quotes Concerning Problem Solving
Computer Chess
Chess Analysis
Early Computers/ New Computers
Problem Solving/ Creativity
Game Theory
Favorite Links
About Me
Additional Notes
The Case for Using Probabilistic Knowledge in a Computer Chess Program (John L. Jerz)
Resilience in Man and Machine

A Step-By-Step Guide

MiltonKAP.jpg

Review

From the reviews:

"Building on Nigel Shadbolt’s pioneering work in the field of knowledge acquisition, Milton, prominent artificial intelligence researcher, here provides a clear guide for knowledge acquisition projects. … Overall, this comprehensive work approaches knowledge bases holistically, by exploring both the process of creating knowledge bases and the strengths and weaknesses of competing knowledge base structures. Glossary, index, appendixes, bibliography. A highly technical work appropriate for academic libraries. Summing Up: Highly recommended. Upper-division undergraduates through professionals." (K. J. Whitehair, CHOICE, Vol. 45 (5), January, 2008)



Product Description

Recent years have seen an upsurge of interest in knowledge. Leading organisations now recognise the importance of identifying what they know, sharing what they know and using what they know for maximum benefit. Many organisations employ knowledge engineers to capture knowledge from experts using the principles and techniques of knowledge engineering. The emphasis is on a structured approach built on a sound understanding of the psychology of expertise and making use of knowledge modelling methods and the latest web technologies.

Knowledge Acquisition in Practice is the first book to provide a detailed step-by-step guide to the methods and practical aspects of acquiring, modelling, storing and sharing knowledge. The reader is led through 47 steps from the inception of a project to its successful conclusion. Each step is described in terms of the reasons for the step, the required resources, the activities to be undertaken, and the solutions to common problems. In addition, each step has a checklist which lists the key items that should be achieved during the step.

Knowledge Acquisition in Practice will be of value to knowledge engineers, knowledge workers, knowledge officers and ontological engineers. The book will also be of interest to students and researchers of AI, computer science and business studies.

vi This book presents a systematic presentation of processes, procedures and routines to organize a general knowledge acquisition project. The beauty of the approach is that it is independent of whether the project is to deliver a decision support system, a knowledge management product or a website.
 
p.1 A quick definition of knowledge is that it is equivalent to expertise. And what is expertise? It is the ability of people to do effective and efficient work and to deal with complex situations.
 
p.3 knowledge is an active thing that manipulates, transforms or creates something out of something else. It is a machine in someone's head that takes in data and information at one end and spurts out decisions and actions at the other end.
 
p.4-5 Procedural knowledge... is about processes, tasks and activities... Conceptual knowledge... is about the ways in which things (which we call 'concepts') are related to one another and about their properties... Basic, Explicit knowledge.. is concerned with basic tasks that an expert performs, basic relationships between concepts, and basic properties of concepts... Deep, Tacit Knowledge... is the sort of knowledge that someone gains when they practice something.
 
p.8 We are good at communicating - evolution has seen to that - and we are good at developing expertise in performing complex activities. But we are not so good at communicating complex ideas with people who are not in the same subject area.
 
p.46,47 Identify where you will get the knowledge... Alongside people, you are likely to identify knowledge resources that have already been written by experts... For all but the shortest document, it is important to identify which parts of the document, website or database will be of most use for the project
 
p.61 Familiarize yourself with basic knowledge in the domain from the available sources of knowledge (documentation, websites, people)... It is important to move yourself up the learning curve to prepare for the next steps. The more you can find out now by reading and informal knowledge gathering, the more effective will be the semi-structured interviews and the subsequent steps that involve modelling.
 
p.62 You should already have identified all of the relevant sources of knowledge (during step 9). You now need to select those that are most applicable to this stage... Read relevant sections from documents, websites and databases... Analyse and model relevant sections from documents, websites and databases.
 
p.118 A knowledge web is a website that presents the contents of a k-base to human end-users in a clear and navigable way.
 
p.119 A knowledge document is a document that details the knowledge that is required for the development of an intelligent software system, such as an expert system
 
p.168 I would not say 'Knowledge is power', but rather I would say 'Knowledge is powerful'... Exciting times are ahead for those working in the world of knowledge.

Enter supporting content here