Introduction to Knowledge Engineering

Slides:



Advertisements
Similar presentations
© 2012 | The Logic Factory R 247 / G 150 / B 72 R 38 / G 157 / B 192 R 35 / G 41 / B 66 Knowledge Acquisition and Modelling Practical use in projects Lecture.
Advertisements

The design process IACT 403 IACT 931 CSCI 324 Human Computer Interface Lecturer:Gene Awyzio Room:3.117 Phone:
Software Process Models
A Linguistics-Based Approach for Use Case Driven Analysis Using Goal and Scenario Authoring Vijayan Sugumaran Oakland University Rochester, Michigan, USA.
Object-Oriented Analysis and Design
Chapter 6: Design of Expert Systems
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
1 Software Testing and Quality Assurance Lecture 15 - Planning for Testing (Chapter 3, A Practical Guide to Testing Object- Oriented Software)
Fundamentals of Information Systems, Second Edition
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
Information Modeling: The process and the required competencies of its participants Paul Frederiks Theo van der Weide.
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
Software Architecture Quality. Outline Importance of assessing software architecture Better predict the quality of the system to be built How to improve.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Introduction to Systems Analysis and Design
Chapter 1 The Systems Development Environment
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
What is Business Analysis Planning & Monitoring?
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
Software Development Process
Software Engineering Muhammad Fahad Khan
1 Introduction to modeling General Concepts. 2 Where are we? #TitleDate 1Introduction General concepts ORM modeling Relational.
1 Introduction to modeling Introduction. 2 Where are we? #TitleDate 1Introduction ORM modeling Relational modeling ER.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
“Enhancing Reuse with Information Hiding” ITT Proceedings of the Workshop on Reusability in Programming, 1983 Reprinted in Software Reusability, Volume.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
ITEC224 Database Programming
Chapter 1: Introduction to Systems Analysis and Design
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Business Analysis and Essential Competencies
T. Dawson, TASC 9/11/13 Use of a Technical Reference in NASA IV&V.
 Knowledge Acquisition  Machine Learning. The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
OHTO -99 SOFTWARE ENGINEERING LECTURE 5 Today: - An overview to OO Analysis and OO Design - Introduction of Assignment 2.
1 Chapter 15 Methodology Conceptual Databases Design Transparencies Last Updated: April 2011 By M. Arief
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
Identify steps for understanding and solving the
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Lecture on Computer Science as a Discipline. 2 Computer “Science” some people argue that computer science is not a science in the same sense that biology.
Software Engineering Principles Principles form the basis of methods, techniques, methodologies and tools Principles form the basis of methods, techniques,
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
Lecture 7: Requirements Engineering
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
1 Introduction to Software Engineering Lecture 1.
Methodology - Conceptual Database Design
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
Presented By: Aly Aboul Nour Supervised By: Dr. A. Rafea CommonKads.
1 What is OO Design? OO Design is a process of invention, where developers create the abstractions necessary to meet the system’s requirements OO Design.
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
Chapter 4 프로세스 모델 Process Models
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Identifying needs and establishing requirements Data gathering for requirements.
Human Computer Interaction
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
1 Sobah Abbas Petersen Adjunct Associate Professor, NTNU Researcher, Sintef TDT4252 Modelling of Information Systems Advanced Course TDT4252,
Introduction to Software Engineering 1. Software Engineering Failures – Complexity – Change 2. What is Software Engineering? – Using engineering approaches.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
The Systems Engineering Context
Usability Techniques Lecture 13.
Chapter 1: Introduction to Systems Analysis and Design
Presentation transcript:

Introduction to Knowledge Engineering CommonKADS course Introduction to Knowledge Engineering What is Knowledge Engineering? History & Terminology

Data, information & knowledge Introduction Data, information & knowledge CommonKADS course Data “raw signals” . . . - - - . . . Information meaning attached to data S O S Knowledge attach purpose and competence to information potential to generate action emergency alert ® start rescue operation Introduction

Knowledge engineering Introduction Knowledge engineering CommonKADS course process of eliciting, structuring, formalizing, operationalizing information and knowledge involved in a knowledge-intensive problem domain, in order to construct a program that can perform a difficult task adequately Introduction

Problems in knowledge engineering Introduction Problems in knowledge engineering CommonKADS course complex information and knowledge is difficult to observe experts and other sources differ multiple representations: textbooks graphical representations heuristics skills Introduction

Importance of proper knowledge engineering Introduction Importance of proper knowledge engineering CommonKADS course Knowledge is valuable and often outlives a particular implementation knowledge management Errors in a knowledge-base can cause serious problems Heavy demands on extendibility and maintenance changes over time Introduction

A Short History of Knowledge Systems Introduction A Short History of Knowledge Systems CommonKADS course Introduction

First generation “Expert” Systems Introduction First generation “Expert” Systems CommonKADS course shallow knowledge base single reasoning principle uniform representation limited explanation capabilities Introduction

Transfer View of KE Extracting knowledge from a human expert Introduction Transfer View of KE CommonKADS course Extracting knowledge from a human expert “mining the jewels in the expert’s head”’ Transferring this knowledge into KS. expert is asked what rules are applicable translation of natural language into rule format Introduction

Problems with transfer view Introduction Problems with transfer view CommonKADS course The knowledge providers, the knowledge engineer and the knowledge-system developer should share a common view on the problem solving process and a common vocabulary in order to make knowledge transfer a viable way of knowledge engineering Introduction

Rapid Prototyping Positive Negative Introduction Rapid Prototyping CommonKADS course Positive focuses elicitation and interpretation motivates the expert (convinces management) Negative large gap between verbal data and implementation architecture constrains the analysis hence: distorted model difficult to throw away Introduction

Methodological pyramid Introduction Methodological pyramid CommonKADS course Introduction

World view: Model-Based KE Introduction World view: Model-Based KE CommonKADS course The knowledge-engineering space of choices and tools can to some extent be controlled by the introduction of a number of models Each model emphasizes certain aspects of the system to be built and abstracts from others. Models provide a decomposition of knowledge-engineering tasks: while building one model, the knowledge engineer can temporarily neglect certain other aspects. Introduction

CommonKADS principles Introduction CommonKADS principles CommonKADS course Knowledge engineering is not some kind of `mining from the expert's head', but consists of constructing different aspect models of human knowledge The knowledge-level principle: in knowledge modeling, first concentrate on the conceptual structure of knowledge, and leave the programming details for later Knowledge has a stable internal structure that is analyzable by distinguishing specific knowledge types and roles. Introduction

Introduction CommonKADS theory CommonKADS course KBS construction entails the construction of a number of models that together constitute part of the product delivered by the project. Supplies the KBS developer with a set of model templates. This template structure can be configured, refined and filled during project work. The number and level of elaboration of models depends on the specific project context. Introduction

CommonKADS Model Set Organization Model Task Agent Knowledge Introduction CommonKADS Model Set CommonKADS course Organization Model Task Agent Knowledge Communication Design Context Concept Artefact Introduction

Model Set Overview (1) Organization model Task model Agent model Introduction Model Set Overview (1) CommonKADS course Organization model supports analysis of an organization, Goal: discover problems, opportunities and possible impacts of KBS development. Task model describes tasks that are performed or will be performed in the organizational environment Agent model describes capabilities, norms, preferences and permissions of agents (agent = executor of task). Introduction

Model Set Overview (2) Knowledge model Communication model Introduction Model Set Overview (2) CommonKADS course Knowledge model gives an implementation-independent description of knowledge involved in a task. Communication model models the communicative transactions between agents. Design model describes the structure of the system that needs to be constructed. Introduction

Principles of the Model Set Introduction Principles of the Model Set CommonKADS course Divide and conquer. Configuration of an adequate model set for a specific application. Models evolve through well defined states. The model set supports project management. Model development is driven by project objectives and risk. Models can be developed in parallel. Introduction

Models exist in various forms Introduction Models exist in various forms CommonKADS course Model template predefined, fixed structure, can be configured Model instance objects manipulated during a project. Model versions versions of a model instance can exist. Multiple model instances separate instances can be developed example: ''current'' and ''future'' organization Introduction

The Product Instantiated models Additional documentation Software Introduction The Product CommonKADS course Instantiated models represent the important aspects of the environment and the delivered knowledge based system. Additional documentation information not represented in the filled model templates (e.g. project management information) Software Introduction

Roles in knowledge-system development Introduction Roles in knowledge-system development CommonKADS course knowledge provider knowledge engineer/analyst knowledge system developer knowledge user project manager knowledge manager N.B. many-to-many relations between roles and people Introduction

Knowledge provider/specialist Introduction Knowledge provider/specialist CommonKADS course “traditional” expert person with extensive experience in an application domain can provide also plan for domain familiarization “where would you advise a beginner to start?” inter-provider differences are common need to assure cooperatio Introduction

Knowledge engineer specific kind of system analyst Introduction Knowledge engineer CommonKADS course specific kind of system analyst should avoid becoming an "expert" plays a liaison function between application domain and system Introduction

Knowledge-system developer Introduction Knowledge-system developer CommonKADS course person that implements a knowledge system on a particular target platform needs to have general design/implementation expertise needs to understand knowledge analysis but only on the “use”-level role is often played by knowledge engineer Introduction

Knowledge user Primary users Secondary users Introduction Knowledge user CommonKADS course Primary users interact with the prospective system Secondary users are affected indirectly by the system Level of skill/knowledge is important factor May need extensive interacting facilities explanation His/her work is often affected by the system consider attitude / active tole Introduction

Introduction Project manager CommonKADS course responsible for planning, scheduling and monitoring development work liaises with client typically medium-size projects (4-6 people) profits from structured approach Introduction

Knowledge manager background role monitors organizational purpose of Introduction Knowledge manager CommonKADS course background role monitors organizational purpose of system(s) developed in a project knowledge assets developed/refined initiates (follow-up) projects should play key role in reuse may help in setting up the right project team Introduction

Roles in knowledge-system development Introduction Roles in knowledge-system development CommonKADS course Introduction

Terminology Domain Task Agent some area of interest Introduction Terminology CommonKADS course Domain some area of interest banking, food industry, photocopiers, car manufacturing Task something that needs to be done by an agent monitor a process; create a plan; analyze deviant behavior Agent the executor of a task in a domain typically either a human or some software system Introduction

Terminology Application Application domain Application task Introduction Terminology CommonKADS course Application The context provided by the combination of a task and a domain in which this task is carried out by agents Application domain The particular area of interest involved in an application Application task The (top-level) task that needs to be performed in a certain application Introduction

Terminology knowledge system (KS) expert system Introduction Terminology CommonKADS course knowledge system (KS) system that solves a real-life problem using knowledge about the application domain and the application task expert system knowledge system that solves a problem which requires a considerable amount of expertise, when solved by humans. Introduction