Welcome to the InfoSci Platform
Seamless Structured Knowledge Acquisition

Seamless Structured Knowledge Acquisition

Päivikki Parpola
Copyright: © 2009 |Pages: 7
ISBN13: 9781605660103|ISBN10: 1605660108|EISBN13: 9781605660110
DOI: 10.4018/978-1-60566-010-3.ch262
Cite Chapter Cite Chapter

MLA

Parpola, Päivikki. "Seamless Structured Knowledge Acquisition." Encyclopedia of Data Warehousing and Mining, Second Edition, edited by John Wang, IGI Global, 2009, pp. 1720-1726. https://doi.org/10.4018/978-1-60566-010-3.ch262

APA

Parpola, P. (2009). Seamless Structured Knowledge Acquisition. In J. Wang (Ed.), Encyclopedia of Data Warehousing and Mining, Second Edition (pp. 1720-1726). IGI Global. https://doi.org/10.4018/978-1-60566-010-3.ch262

Chicago

Parpola, Päivikki. "Seamless Structured Knowledge Acquisition." In Encyclopedia of Data Warehousing and Mining, Second Edition, edited by John Wang, 1720-1726. Hershey, PA: IGI Global, 2009. https://doi.org/10.4018/978-1-60566-010-3.ch262

Export Reference

Mendeley
Favorite

Abstract

Some parts of this text, namely “Co-operative Building, Adaptation, and Evolution of Abstract Models of a KB” and most subsections in “Performing Reasoning in SOOKAT According to a KB”, have appeared in an article (DOI:10.1007/s10115-004-0181-6) published in the ‘Knowledge And Information Systems’ journal (Parpola, 2004). A knowledge base (KB) contains data and instructions for using it (e.g., as a rule base). A KB containing knowledge possessed by experts can be used in an expert system. It can solve problems requiring expert knowledge, explain its decisions and deal with uncertainty. An expert system can be used as a basis for a larger system, called a knowledge-based system (KBS). Knowledge acquisition (KA) that is the development and maintenance of KBs, (e.g. an expert system), can be divided into several phases, performed sequentially and iteratively. Some phases may be performed in parallel with other phases. The most commonly recognised phases are requirements definition, analysis, design, and implementation. Disintegration, or the gap between phases of development, especially between abstract and executable descriptions, was recognised during the early stages of KA (Marcus, 1988a; Motta, Rajan and Eisenstadt, 1988). It complicates the development of KBs and hinders traceability between parts of abstract and executable descriptions.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.