Knowledge Acquisition. Knowledge Aquisition Definition – The process of acquiring, organising, & studying knowledge. Identified by many researchers and.

Slides:



Advertisements
Similar presentations
Modelling with expert systems. Expert systems Modelling with expert systems Coaching modelling with expert systems Advantages and limitations of modelling.
Advertisements

FT228/4 Knowledge Based Decision Support Systems Knowledge Engineering Ref: Artificial Intelligence A Guide to Intelligent Systems, Michael Negnevitsky.
Software Development Languages and Environments. Programming languages High level languages are problem orientated contain many English words are easier.
Objective Knowledge Elicitation Interview Case Study Answers Questions Domain Expert Knowledge Engineer Results Knowledge Expert System.
Marzano Art and Science Teaching Framework Learning Map
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 2.
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Artificial Intelligence
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Requirements Analysis 5. 1 CASE b505.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis CASE Computer.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
School of Computing and Mathematics, University of Huddersfield Knowledge Engineering: Issues for the Planning Community Lee McCluskey Department of Computing.
Knowledge Acquisition CIS 479/579 Bruce R. Maxim UM-Dearborn.
Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall Chapter Chapter 1: Introduction to Decision Support Systems Decision Support.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Overview of Software Requirements
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
RESEARCH METHODS IN EDUCATIONAL PSYCHOLOGY
Writing Instructional Objectives
Knowledge Acquisition and Validation
Centralian Senior College. Examples  Add and subtract  Write a paragraph  An amoeba  The conventions of punctuation  When oppression meets resistance,
31 st October, 2012 CSE-435 Tashwin Kaur Khurana.
Expert Systems.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
S/W Project Management
ARTIFICIAL INTELLIGENCE [INTELLIGENT AGENTS PARADIGM] Professor Janis Grundspenkis Riga Technical University Faculty of Computer Science and Information.
1 CHAPTER 11 Knowledge Acquisition and Validation Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson 6th ed, Copyright.
O BJECT O RIENTATION F UNDAMENTALS Prepared by: Gunjan Chhabra.
Requirements Analysis
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
Chapter 6 Supplement Knowledge Engineering and Acquisition Chapter 6 Supplement.
 Knowledge Acquisition  Machine Learning. The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Requirements Engineering Requirements Elicitation Process Lecture-8.
A COMPETENCY APPROACH TO HUMAN RESOURCE MANAGEMENT
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
Lecture 7: Requirements Engineering
IS2210: Systems Analysis and Systems Design and Change Twitter:
1 Introduction to Software Engineering Lecture 1.
ES Design, Development and Operation Dr. Ahmed Elfaig Knowledge model, knowledge structure, presentation and organization are the bottleneck of expert.
 Dr. Syed Noman Hasany 1.  Review of known methodologies  Analysis of software requirements  Real-time software  Software cost, quality, testing.
1 Chapter 3 1.Quality Management, 2.Software Cost Estimation 3.Process Improvement.
Machine Learning Chapter 5. Artificial IntelligenceChapter 52 Learning 1. Rote learning rote( โรท ) n. วิถีทาง, ทางเดิน, วิธีการตามปกติ, (by rote จากความทรงจำ.
Week 8 MSE614 – SP 08 Ileana Costea. HW Questions on KA Due today, Week 8 Assigned last session, Week 7 A few verbal questions (see Transparency)
Human Computer Interaction
CSCI 1100/1202 April 1-3, Program Development The creation of software involves four basic activities: –establishing the requirements –creating.
OTHER KNOWLEDGE CAPTURE TECHNIQUES CHAPTER 6. Chapter 6: Other Knowledge Capture Techniques 2 On-Site Observation  Process of observing, interpreting,
KNOWLEDGE ACQUISITION, REPRESENTATION, AND REASONING
Chapter 6 Determining System Requirements. Objectives:  Describe interviewing options and develop interview plan.  Explain advantages and pitfalls of.
Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1.
1 CHAPTER 11 Knowledge Acquisition and Validation Decision Support Systems and Intelligent Systems, Efraim Turban and Jay E. Aronson 6th ed, Copyright.
Requirements Analysis
Of An Expert System.  Introduction  What is AI?  Intelligent in Human & Machine? What is Expert System? How are Expert System used? Elements of ES.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
 Knowledge Acquisition  Machine Learning. The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Victoria Ibarra Mat:  Generally, Computer hardware is divided into four main functional areas. These are:  Input devices Input devices  Output.
1 Knowledge Acquisition, Representation and Organization Dr. Jeffrey M. Sta. Ines.
Design of Expert Systems
CHAPTER 1 Introduction BIC 3337 EXPERT SYSTEM.
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Computer Aided Software Engineering (CASE)
Architecture Components
KNOWLEDGE ACQUISITION
Unit 6: Application Development
Chapter 11 Expert system architecture, representation of knowledge, Knowledge Acquisition, and Reasoning.
Members: Keshava Shiva Sanjeeve Kareena
전문가 시스템(Expert Systems)
Presentation transcript:

Knowledge Acquisition

Knowledge Aquisition Definition – The process of acquiring, organising, & studying knowledge. Identified by many researchers and practitioners (in particular Feigenbaum) as the bottleneck in ES development.

Knowledge Aquisition Two main types of sources of knowledge –  documented (which can take many forms) and  undocumented (usually in the expert’s mind). Categories of Knowledge. (three main ones)  Declarative – i.e. descriptive knowledge, facts.  Procedural – how things are done, how to use the declarative knowledge.  Semantics – consider words & symbols & what they mean, how they are related & manipulated. Reflects cognitive structure.

Why is it difficult to transfer knowledge? Hard to get experts to express how they solve problems Representation on machine requires detailed expression i.e. at a very low level. Must be represented in a structured way. Bringing together the ideas of all those involved in the knowledge transfer process.

Methods of knowledge aquisition Interview techniques  Expert focused interview  Structured interview  ‘Thinking aloud’ interview To elicit general knowledge about the domain 2 nd phase More specific questions from KE Expert encouraged to talk while thinking Helps understand experts Problem solving strategies

Other elicitation techniques Repertory grid (Kelly 1955)  Represents expert’s view of a problem Expert identifies important objects Expert identifies important attributes Expert establishes a bipolar scale with distinguishable characteristics (traits) and their opposites. Interviewer picks 3 objects & asks what distinguishes any 2 of these from the third. Continues for several triplets of objects. Each object is given a score for each attribute that represents a point on the range designated by the bipolar scale. (Usually use 1-3, or 1-5) The way in which the objects are distinguished from each other becomes clear to KE. Used in some automated KA tools.

Observational techniques Protocol analysis  Like thinking aloud. Expert is observed carrying out task and explains actions while doing it. Usually recorded. Observation  Saves experts time. Time consuming for KE. Can be embarrassing for expert – might behave unnaturally. Case studies  Look at specific cases.

Automated KA – various approaches Explanation facility can help, i.e. trials with knowledge coded so far. Special knowledge base editors as interfaces to check for consistencies and completeness. A KA aid known as TEIRESIAS was designed for work using EMYCIN.  Uses a NL interface & has expanded explanation facility.  Translates each new rule to LISP and then back again so can show inconsistencies, conflicts, etc. KADS is a more general approach to automated KA. Auto-intelligence – captures knowledge of expert through interactive interviews, distils knowledge, generates rule based system (see section rule induction)

Automated Rule Induction Rules are generated by a computer system given a number of examples. A series of examples (the training set) are provided and the inductive learning system generates rules from these. These rules can then be used to assess further examples where the outcome is unknown. This is done using algorithms. A well used algorithm is Quinlan’s ID3 algorithm which generates a decision tree from the knowledge in the example cases, and then provides rules. A later version of this algorithm is C5, and software to enable the use of it is See5 (windows version).

See5

Cross referencing in See5

Summary Knowledge acquisition bottleneck Approaches to KA  Interview techniques  Observational techniques  Automated techniques  Rule induction