Bruce Porter (University of Texas) Peter Clark (Boeing) and Colleagues Building KB’s by Assembling Components: An early evaluation of the approach.

Slides:



Advertisements
Similar presentations
Intelligence Step 5 - Capacity Analysis Capacity Analysis Without capacity, the most innovative and brilliant interventions will not be implemented, wont.
Advertisements

A Library of Generic Concepts for Composing Knowledge Bases Ken Barker, Bruce UTAustin Peter
How an SME Might Assemble a KB from Components Bruce Porter (University of Texas) Peter Clark (Boeing) and Colleagues.
Object-Oriented Analysis and Design
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Conceptual modelling. Overview - what is the aim of the article? ”We build conceptual models in our heads to solve problems in our everyday life”… ”By.
Dr. Kalpakis CMSC 461, Database Management Systems Introduction.
Domain-Specific Software Engineering Alex Adamec.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
The Business Skills Handbook
Traditional Approach to Requirements Data Flow Diagram (DFD)
Environment Change Information Request Change Definition has subtype of Business Case based upon ConceptPopulation Gives context for Statistical Program.
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
Conquering Complex and Changing Systems Object-Oriented Software Engineering Chapter 1, Introduction to Software Engineering.
An Object-Oriented Approach to Programming Logic and Design
1 The Architectural Design of FRUIT: A Family of Retargetable User Interface Tools Yi Liu, H. Conrad Cunningham and Hui Xiong Computer & Information Science.
Software Models (Cont.) 9/22/2015ICS 413 – Software Engineering1 -Component-based software engineering -Formal Development Model.
T. Dawson, TASC 9/11/13 Use of a Technical Reference in NASA IV&V.
Help Desk System How to Deploy them? Author: Stephen Grabowski.
Knowledge Entry as the Graphical Assembly of Components Peter Clark, John Thompson (Boeing) Ken Barker, Bruce Porter (Univ Texas at Austin) Vinay Chaudhri,
School of Computing FACULTY OF ENGINEERING Developing a methodology for building small scale domain ontologies: HISO case study Ilaria Corda PhD student.
UNIVERSITÉ LAVAL Centre for Research in Geomatics, Université Laval, Cité universitaire, Quebec, QC Canada G1K 7P4 Semantic Interoperability of Geospatial.
Software cost estimation Predicting the resources required for a software development process 1.
Metadata Models in Survey Computing Some Results of MetaNet – WG 2 METIS 2004, Geneva W. Grossmann University of Vienna.
Jigsaw A Social Interactive Model for Teaching. Each piece of the puzzle is needed in order to create the whole picture.
MD – Object Model Domain eSales Checker Presentation Régis Elling 26 th October 2005.
Environment Change Information Request Change Definition has subtype of Business Case based upon ConceptPopulation Gives context for Statistical Program.
OBJECT-ORIENTED PROGRAMMING (OOP) WITH C++ Instructor: Dr. Hany H. Ammar Dept. of Electrical and Computer Engineering, WVU.
Requirements Engineering Methods for Requirements Engineering Lecture-30.
INTRODUCTION A syllabus is an extremely important document because it will likely be the most viewed document in our course by our students. DEFINITION.
Enabling Reuse-Based Software Development of Large-Scale Systems IEEE Transactions on Software Engineering, Volume 31, Issue 6, June 2005 Richard W. Selby,
ISO-PWI Lexical ontology some loose remarks Thierry Declerck, DFKI GmbH.
©Ian Sommerville 2000Software Engineering, 7th edition. Chapter 26Slide 1 Software cost estimation l Predicting the resources required for a software development.
What is it? Why do it? How do you do it?
Guiding Inference with Conceptual Graphs Bruce Porter Univ Texas at Austin Peter Clark Boeing Research.
PRJ566 Project Planning & Management Software Architecture.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 28Slide 1 CO7206 System Reengineering 4.2 Software Reengineering Most slides are Slides.
Chapter 5: Software Re-Engineering Omar Meqdadi SE 3860 Lecture 5 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Enabling Domain Experts to Convey Questions to a Machine: A Modified, Template-Based Approach Peter Clark (Boeing Phantom Works) Ken Barker, Bruce Porter.
Knowledge Entry as the Graphical Assembly of Components Peter Clark, John Thompson (Boeing) Ken Barker, Bruce Porter (Univ Texas at Austin) Vinay Chaudhri,
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Compiler Construction (CS-636)
Building KB’s by Assembling Components Bruce Porter (UT Austin) Peter Clark (Boeing)
IAEA International Atomic Energy Agency Methodology and Responsibilities for Periodic Safety Review for Research Reactors William Kennedy Research Reactor.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 15a: Product Metrics for Software Software Engineering: A Practitioner’s Approach, 6/e Chapter.
Business Rules 12 th Meeting Course Name: Business Intelligence Year: 2009.
SwE 455 Tutorial. What is Evolve? Evolve is a tool for defining components and connecting them together to form new components. Also provides a runtime.
READING ACROSS DISCIPLINES Caroline Gordon Messenger, English Kelly Leary, Social Studies The Common Core and construction of meaning.
DATA FLOW DIAGRAMS.
DESIGN PROCESS AND CONCEPTS. Design process s/w design is an iterative process through which requirements are translated into a “blueprint” for constructing.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Ontologies COMP6028 Semantic Web Technologies Dr Nicholas Gibbins
MDD-Kurs / MDA Cortex Brainware Consulting & Training GmbH Copyright © 2007 Cortex Brainware GmbH Bild 1Ver.: 1.0 How does intelligent functionality implemented.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
COMP6215 Semantic Web Technologies
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Title: Validating a theoretical framework for describing computer programming processes 29 November 2017.
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Introduction Software is becoming very expensive:
Chapter 1, Introduction to Software Engineering
SwE 455 Tutorial.
Verification Concepts for SysmL v2
Engineering Processes
MSDI training courses feedback MSDIWG10 March 2019 Busan
Verification Concepts for SysmL v2
THE SYSTEMS APPROACH TO CURRICULUM DEVELOPMENT
Session 3 Formulating Strategic Marketing Plans
From Class Diagram to Contract Diagram
Presentation transcript:

Bruce Porter (University of Texas) Peter Clark (Boeing) and Colleagues Building KB’s by Assembling Components: An early evaluation of the approach

Claims A component is a set of axioms that: describe a consensus view of a common concept can be frequently reused with little modification … … to combine with other components … … to represent domain knowledge well.

Claims A component is a set of axioms that: describe a consensus view of a common concept can be frequently reused with little modification … … to combine with other components … … to represent domain knowledge well. versus an idiosyncratic view

Claims A component is a set of axioms that: describe a consensus view of a common concept can be frequently reused with little modification … … to combine with other components … … to represent domain knowledge well. versus infrequently reused without significant modification

Claims A component is a set of axioms that: describe a consensus view of a common concept can be frequently reused with little modification … … to combine with other components … … to represent domain knowledge well. versus difficult or impossible to combine (“round holes and square pegs)

Claims A component is a set of axioms that: describe a consensus view of a common concept can be frequently reused with little modification … … to combine with other components … … to represent domain knowledge well. versus representations are incomplete or inconsistent We’ll evaluate each of these claims in turn …

The Context for our Evaluation: The Component Approach in Practice We are building a component library while assembling a microbiology KB for the TKCP For each microbiology topic, we will: –Identify the core concepts used in textbook accounts –Build components for these concepts –Use these components to represent the topic in the KB

Do the components capture a consensus view? Internal evaluation: –Have multiple KE’s (team members) independently encode each component. –Measure the agreement among the representations External evaluation: –Translate components from KM into English, yielding “dictionary definitions” –Have n subjects review the definitions then revise them if they deem appropriate. –Have an independent subject extract the “consensus view” from the n definitions. –Measure the agreement between the consensus view and the original ones.

Can the components be frequently reused with little modification? Count the amount of reuse of each component. Count the number of modifications made for each instance of reuse, and weight it by its severity.

Do the components combine together well? For each microbiology topic: –Write a high-level design for its representation which shows: The components that comprise it Their instantiations and inter-relationships –Implement the design –Measure and study the times when implementation details force changes to the design

Do the components represent domain knowledge well? For each topic represented in the KB: –Measure how much of its representation was provided by components; the balance was coded specifically for this topic. –The TKCP will measure the quality of the overall representation, in terms of consistency, completeness, support for inference, and so on. –Analyze the KB’s successes and failures at the TKCP to assign responsibility to the components (versus other aspects of the KB system).

Summary We have identified the “strong claims” of the component approach We plan to evaluate the claims early – while building a microbiology KB The data we collect will be invaluable to study questions we’ve only begun to formulate