CS62S: Expert Systems Knowledge acquisition and system implementation Based on Chap. 12: The Engineering of Knowledge-based Systems: Theory and Practice,

Slides:

Advertisements

Similar presentations

FT228/4 Knowledge Based Decision Support Systems Knowledge Engineering Ref: Artificial Intelligence A Guide to Intelligent Systems, Michael Negnevitsky.

Advertisements

B. Ross Cosc 4f79 1 Knowledge acquisition (Ch. 17 Durkin) knowledge engineering: building expert systems knowledge acquisition: process of extracting knowledge.

1 Chapter 2: Product Development Process and Organization Introduction Importance of human resources: Most companies have similar technology resources.

lamsweerde Part 1: Introduction © 2009 John Wiley and Sons 1 Requirements Engineering From System Goals to UML Models to.

Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,

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.

Analysis Concepts and Principles

Requirements Engineering Processes

Information Systems Development and Acquisition Chapter 8 Jessup & Valacich Instructor: Ramesh Sankaranarayanan.

Represent the following sentences in first-order logic, using a consistent vocabulary

Building knowledge bases The fundamental problem of understanding intelligence is not the identification of a few powerful techniques, but rather the question.

Given Connections Solution

Part 2: Requirements Days 7, 9, 11, 13 Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain.

7M822 Software Requirements Introduction 7 September 2010.

Requirements Engineering Process – 1

What is Business Analysis Planning & Monitoring?

Requirements Engineering Processes

Institut Experimentelles Software Engineering Fraunhofe r IESE Andreas Birk Ulrike Becker-Kornstaedt Sauerwiesen 6 D Kaiserslautern Germany Experience.

Knowledge Acquisition. Concepts of Knowledge Engineering Knowledge engineering The engineering discipline in which knowledge is integrated into computer.

CS62S: Expert Systems Based on: The Engineering of Knowledge-based Systems: Theory and Practice A. J. Gonzalez and D. D. Dankel.

المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.

Business Analysis and Essential Competencies

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.

Chapter 6 Supplement Knowledge Engineering and Acquisition Chapter 6 Supplement.

E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER S OFTWARE D ESIGN C OPYRIGHT © 2011 DSR C ORPORATION.

Software Design: An Introduction by David Budgen Presented by Shane Marcus EEL 6883 – Spring 2007 Presented by Shane Marcus EEL 6883 – Spring 2007.

School of Computing FACULTY OF ENGINEERING Developing a methodology for building small scale domain ontologies: HISO case study Ilaria Corda PhD student.

Artificial Intelligence Building Knowledge Base Chapter 8.

Data Mining – A First View Roiger & Geatz. Definition Data mining is the process of employing one or more computer learning techniques to automatically.

Requirements Engineering Requirements Elicitation Process Lecture-8.

Project Analysis Course ( ) Course Overview Project ideas Presentation.

1 Introduction to Software Engineering Lecture 1.

CS62S: Expert Systems Requirements Specification and Design Based on Chap. 12: The Engineering of Knowledge-based Systems: Theory and Practice, A. J. Gonzalez.

University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 systems analysis 1 what is systems analysis? preparation of the system’s requirements/definition,

Chap. 5 Building Valid, Credible, and Appropriately Detailed Simulation Models.

CS62S: Expert Systems Based on: The Engineering of Knowledge-based Systems: Theory and Practice, A. J. Gonzalez and D. D. Dankel.

Math – What is a Function? 1. 2 input output function.

Requirements Engineering. Requirements engineering processes The processes used for RE vary widely depending on the application domain, the people involved.

Requirements Engineering Process

Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.

ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.

Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?

Requirements Determination Fact finding process A critical initial stage in systems analysis Highly unstructured 72% of all errors in systems can be traced.

Some Thoughts to Consider 5 Take a look at some of the sophisticated toys being offered in stores, in catalogs, or in Sunday newspaper ads. Which ones.

Project Communication Management Manage Communications - Inputs Inputs Communications Management Plan Work Performance Reports Enterprise Environmental.

Requirements. Outline Definition Requirements Process Requirements Documentation Next Steps 1.

Requirements Elicitation Requirements Engineering (CI 2323) Daniel Siahaan.

Knowledge Engineering. Sources of Knowledge - Books - Journals - Manuals - Reports - Films - Databases - Pictures - Audio and Video Tapes - Flow Diagram.

SYSTEM ANALYSIS AND DESIGN LAB NARZU TARANNUM(NAT)

1 Requirements Elicitation – 2 Lecture # Requirements Engineering Process Requirements Elicitation Requirements Analysis and Negotiation Requirements.

Software Engineering Developing Requirements. © Lethbridge/Laganière 2001 Chapter 4: Developing requirements2 4.1 Domain Analysis The process by which.

1 Processes and Process Models Lecture # 5. 2 Process - 1 A process is an organized set of activities, which transforms inputs to outputs We can use synonyms.

Scope of Systems Requirements: Definition o f Requirements Not to define the full system Not to define the full system Describe or define the essential.

Chapter 1 Connections to Algebra Review

Knowledge Elicitation – Converting Tacit Knowledge to Explicit

Processes and Process Models

Plan Risk Management Outputs T &T Inputs Project Management Plan

Requirements Elicitation – 1

EXAMPLE 1 Represent relations

CS62S: Expert Systems Based on:

ورشة عمل حول مهارات العمل الإرشادي وكيفية تطويعها في

Verification and Validation

Modeling in the Time Domain

2.1: Represent Relations and Functions HW: p.76 (4-20 even, all)

Requirements Engineering Process – 1

Part of knowledge base of fuzzy logic expert system for exercise control of diabetics

Requirement Engineer Terms and Conditions

Processes and Process Models

Presentation transcript:

CS62S: Expert Systems Knowledge acquisition and system implementation Based on Chap. 12: The Engineering of Knowledge-based Systems: Theory and Practice, A. J. Gonzalez and D. D. Dankel

Knowledge acquisition Involves two parts: Knowledge elicitation, and Knowledge representation

Knowledge elicitation Kick-off interview Acquaint the knowledge engineer with the discipline Acquaint the expert to what will take place over the elicitation period Discuss expectations Suggest reading materials Make schedule

General knowledge-gathering sessions Understand the domain better Understand the expert’s opinions Build rapport

Specific problem-solving knowledge-gathering sessions Extraction of knowledge of a particular sub-area, assuming it is: Well understood by the expert Fairly understood by the knowledge engineer Broad enough to represent a sub-section of the knowledge in the domain Small enough to require a ‘short’ time to develop

Knowledge organization Outputs – the solutions to the problem Inputs – the information used to deduce the output Middle – the expert’s knowledge that connects the input to the output

Knowledge documentation Rule-base knowledge diagrams:

Knowledge elicitation techniques Observational On-site observation Quiet Discussion Intuitive – knowledge engineer becomes expert in role-playing