Protégé An Environment for Knowledge- Based Systems Development Haishan Liu.

Slides:



Advertisements
Similar presentations
ARCHITECTURES FOR ARTIFICIAL INTELLIGENCE SYSTEMS
Advertisements

16/11/ IRS-II: A Framework and Infrastructure for Semantic Web Services Motta, Domingue, Cabral, Gaspari Presenter: Emilia Cimpian.
Architecture Representation
Lecture # 2 : Process Models
ArchE Presented By Samanvitha Ramayanam. TOPICS 1. Introduction 2. Theoretical assumptions 3. ArchE as an expert system 4. Overall flow of ArchE 5. Key.
Intelligent Agent for Designing Steel Skeleton Structures of Tall Buildings Zbigniew Skolicki Rafal Kicinger.
Object-Oriented Analysis and Design
Internet Reasoning Service: Progress Report Wenjin Lu and Enrico Motta Knowledge Media Institute Monica Crubézy Stanford Medical Informatics.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Designing Help… Mark Johnson Providing Support Issues –different types of support at different times –implementation and presentation both important.
A Review of Ontology Mapping, Merging, and Integration Presenter: Yihong Ding.
Software Engineering General Project Management Software Requirements
PROMPT: Algorithm and Tool for Automated Ontology Merging and Alignment Natalya Fridman Noy and Mark A. Musen.
1 SWE Introduction to Software Engineering Lecture 5.
PROMPT: Algorithm and Tool for Automated Ontology Merging and Alignment Natalya F. Noy Stanford Medical Informatics Stanford University.
Supervised by, Mr. Ashraf Yaseen. Overview…. Brief Introduction about Knowledge Acquisition. How it can be achieved?. KA Stages. Model. Problems that.
PROMPT: Algorithm and Tool for Automated Ontology Merging and Alignment Natalya F. Noy and Mark A. Musen.
Artificial Intelligence Research Centre Program Systems Institute Russian Academy of Science Pereslavl-Zalessky Russia.
Sepandar Sepehr McMaster University November 2008
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
Knowledge Management in Geodise Geodise Knowledge Management Team Liming Chen, Barry Tao, Colin Puleston, Paul Smart University of Southampton University.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Methods for Computer-Aided Design and Execution of Clinical Protocols Mark A. Musen, M.D., Ph.D. Stanford Medical Informatics Stanford University.
Faculty of Informatics and Information Technologies Slovak University of Technology Peter Kajsa and Ľubomír Majtás Design.
1 CS 456 Software Engineering. 2 Contents 3 Chapter 1: Introduction.
Knowledge representation
Applying Belief Change to Ontology Evolution PhD Student Computer Science Department University of Crete Giorgos Flouris Research Assistant.
Introduction to MDA (Model Driven Architecture) CYT.
Second Generation ES1 Second Generation Expert Systems Ahme Rafea CS Dept., AUC.
Metadata Models in Survey Computing Some Results of MetaNet – WG 2 METIS 2004, Geneva W. Grossmann University of Vienna.
Design engineering Vilnius The goal of design engineering is to produce a model that exhibits: firmness – a program should not have bugs that inhibit.
Configuration Systems - CSE Sudhan Kanitkar.
1 Introduction to Software Engineering Lecture 1.
Knowledge Representation of Statistic Domain For CBR Application Supervisor : Dr. Aslina Saad Dr. Mashitoh Hashim PM Dr. Nor Hasbiah Ubaidullah.
Elizabeth Furtado, Vasco Furtado, Kênia Sousa, Jean Vanderdonckt, Quentin Limbourg KnowiXML: A Knowledge-Based System Generating Multiple Abstract User.
2004/12/13 National Tsing Hua University, Taiwan1 USING KNOWLEDGE-BASED INTELLIGENT REASONING TO SUPPORT DYNAMIC COLLABORATIVE DESIGN Allen T.A. Chiang*,
Semantic web course – Computer Engineering Department – Sharif Univ. of Technology – Fall Knowledge Representation Semantic Web - Fall 2005 Computer.
Christoph F. Eick University of Houston Organization 1. What are Ontologies? 2. What are they good for? 3. Ontologies and.
COMM89 Knowledge-Based Systems Engineering Lecture 8 Life-cycles and Methodologies
Object-Oriented Modeling: Static Models. Object-Oriented Modeling Model the system as interacting objects Model the system as interacting objects Match.
Generic Tasks by Ihab M. Amer Graduate Student Computer Science Dept. AUC, Cairo, Egypt.
User Profiling using Semantic Web Group members: Ashwin Somaiah Asha Stephen Charlie Sudharshan Reddy.
1 Knowledge Acquisition and Learning by Experience – The Role of Case-Specific Knowledge Knowledge modeling and acquisition Learning by experience Framework.
A View-based Methodology for Collaborative Ontology Engineering (VIMethCOE) Ernesto Jiménez Ruiz Rafael Berlanga Llavorí Temporal Knowledge Bases Group.
EEL 5937 Ontologies EEL 5937 Multi Agent Systems Lecture 5, Jan 23 th, 2003 Lotzi Bölöni.
Issues in Ontology-based Information integration By Zhan Cui, Dean Jones and Paul O’Brien.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
Some Thoughts to Consider 8 How difficult is it to get a group of people, or a group of companies, or a group of nations to agree on a particular ontology?
1 Software Design Lecture What’s Design It’s a representation of something that is to be built. i.e. design  implementation.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
Problem-Solving Methods in Protégé-2000 Monica Crubézy Stanford Medical Informatics MIS November 1999.
Henrik Eriksson Department of Computer and Information Science Linkoping University SE Linkoping, Sweden Raymond W. Fergerson Yuval Shahar Stanford.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Cognitive Architectures and General Intelligent Systems Pay Langley 2006 Presentation : Suwang Jang.
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.
OBJECT-ORIENTED TESTING. TESTING OOA AND OOD MODELS Analysis and design models cannot be tested in the conventional sense. However, formal technical reviews.
Protégé/2000 Advanced Tools for Building Intelligent Systems Mark A. Musen Stanford University Stanford, California USA.
Knowledge Engineering. Sources of Knowledge - Books - Journals - Manuals - Reports - Films - Databases - Pictures - Audio and Video Tapes - Flow Diagram.
16 April 2011 Alan, Edison, etc, Saturday.. Knowledge, Planning and Robotics 1.Knowledge 2.Types of knowledge 3.Representation of knowledge 4.Planning.
Mechanisms for Requirements Driven Component Selection and Design Automation 최경석.
Artificial Intelligence
DOMAIN ONTOLOGY DESIGN
Protégé/2000 Advanced Tools for Building Intelligent Systems
Independent Study of Ontologies
William Grosso Stanford Medical Informatics Stanford University
Knowledge Representation
KNOWLEDGE REPRESENTATION
Ontology-Based Approaches to Data Integration
ONTOMERGE Ontology translations by merging ontologies Paper: Ontology Translation on the Semantic Web by Dejing Dou, Drew McDermott and Peishen Qi 2003.
Building Ontologies with Protégé-2000
Presentation transcript:

Protégé An Environment for Knowledge- Based Systems Development Haishan Liu

Outline Things will be covered  The evolution of Prot é g é and the underlying driven idea  Major features of different versions of Prot é g é Things will not be covered  The detailed mechanisms and algorithms of the implementation

What is Protégé The Prot é g é system is an environment for knowledge-based systems development From a single tool to reduce the knowledge-acquisition bottleneck to a general-purpose environment for knowledge modeling

The classical model of expert system development

Difficulties in the classic model The knowledge engineer is involved in all phases of system construction  characterize the reasoning tasks  identify the major domain concepts  categorize the type of knowledge  identify the reasoning strategies used by experts,  define an inference structure for the resulting application,  and formalize all this knowledge in a generic and reusable way. domain experts are seen simply as resources for knowledge engineers to draw upon.

An early view: expert system shell Reuse of knowledge Base Knowledge acquisition is carried out by the knowledge engineer. The introduction of a knowledge engineer in between could lead to errors and misunderstandings. Time-consuming

Domain expert

Protégé Ancestry: Oncocin and Opal

Information-partitioning hypothesis structural domain concepts ① domain knowledge ② case data ③ ① ② ③

Advantage of Opal/Oncocin architecture Actual tools developed for knowledge acquisition The domain experts directly build the knowledge base  reduce the likelihood of errors  Streamline knowledge base construction

Protégé-I generalization of the Oncocin/Opal architecture

Assumptions of Protégé-I Problem specific KB  Only works well on certain PSMs Problem-solving method (PSM) provides semantics of KB  No formalization of the knowledge model Atomic PSM and KB  Self-contained KB (no reference to the others)  Single monolithic PSM

Summary of Protégé-I Generating knowledge-acquisition tools from structured meta-knowledge Neither reusable nor general purpose  Problem-specific KB  Lacking formal semantics

Protégé-II reusable problem-solving methods. A problem-solving method could be developed independently from the knowledge base. PSMs were generic algorithms that could be used with different knowledge bases to solve different real-world tasks.  constraint satisfaction  Classification  Planning  Bayesian inference

Problem-solving knowledge automates specific tasks Domain knowledge + Problem-solving method Intelligent behavior

Protégé-II Reusable problem-solving methods

Developing Knowledge-based Systems with Protégé-II Developing or reusing a problem-solving method Defining an appropriate domain ontology Generating a knowledge-acquisition tool Building a knowledge base using the tool Integrating these components into a knowledge-based system  defining mappings between problem-solving methods and specific knowledge bases.

Three classes of ontologies Domain ontologies (reusable)  define the concepts related to an application domain (e.g., different symptoms, anomalies, and remedies) Method ontologies (reusable)  specify the data requirements of the problem- solving methods (i.e., the input and output structure of each method) Application ontologies (application specific)  define the concepts that are specific to a particular application or implementation.

Protégé-II components for building knowledge bases. “Downhill Flow” Model Knowledge engineer Domain Expert

Integrating the Components of a Knowledge-Based System—Mappings KB and PSM are developed separately PSM may not match KB Use mapping relations to connect KB and PSM  Marble – a special KA tool to build mapping relations  A generic mapping interpreter producing adapted view of KB to PSM

Summary of Protégé-II Reusable PSMs as components Adoption of ontology Generation of KA-tools from any ontology “ Downhill Flow ” assumption of class over instance

Protégé/Win Besides the re-implementation The use of modular ontologies, via an ontology inclusion mechanism  build large knowledge bases by “ gluing ” together a set of smaller, modular ontologies  scale to large problems better than monolithic ontologies A more integrated, streamlined set of tools A more custom-tailoring knowledge- acquisition tool

Protégé-2000 significant augmentations Underlying knowledge model A single unified application A plug-in architecture

The Protégé-2000 Knowledge Model Protégé-Ihand-coded Lisp object Protégé-II and Protégé/Win a simple frame-based model provided by CLIPS Protégé-2000OKBC protocol Retrospect

Open Knowledge Base Connectivity (OKBC) Standard mechanism to access knowledge bases stored as “ frames ” of classes and attributes Adopted by several well-known knowledge- representation systems (Ontolingua, LOOM) Will allow Prot é g é to be used as an ontology- and knowledge-editing system for any OKBC-compliant server

OKBC – cont’d OKBC specifies a knowledge model of KRSs  with KBs, classes, individuals, slots, and facets It also specifies a set of operations based on this model  find a frame matching a name  enumerate the slots of a frame  delete a frame An application uses these operations to access and modify knowledge stored in a OKBC-compliant KRS.

The OKBC Knowledge Model Constants Frames Slots Facets Classes Individuals knowledge bases

Frames, slots and facets Frame  primitive object that represents an entity in the domain of discourse  Class Frame, Individual Frame Slot  Binary relation associate to a frame (describing the property of the frame) Facet  Constraints on the slot

The plug-in architecture of Protégé-2000

The OntoViz tab plug-in

A Protégé-2000 KA tool for entering rules for monitoring nuclear power plants

Elements of Protégé-2000 Slots as first-class objects Slots as first-class objects Classes and class hierarchy Classes and class hierarchy Facets standard and user-defined Facets standard and user-defined Instances Customizable instance forms Customizable instance forms Easy browsing Easy browsing Means to view large data sets Means to view large data sets Custom widgets Custom widgets Domain- specific tabs Domain- specific tabs Components for building knowledge-based applications Components for building knowledge-based applications