1. Experience Management
11/17/2018
Sean White -- saw CSE 435

2. What is this? What’s a Case Base? 11/17/2018
Sean White -- saw CSE 435

3. Recall Data are facts with no context Information is interpreted data
Knowledge is a set of related information
Experience is stored specific knowledge
Case base as experience to be managed
11/17/2018
Sean White -- saw CSE 435

4. Warehouses of Experience
External
CBR Systems
Knowledge / Experience Base
Data Base
Documentation
People
11/17/2018
Sean White -- saw CSE 435

5. Observations May contain any level of classification Not independent
Some contain unknown resources
Dynamic
IDSS may contain any / all of these
11/17/2018
Sean White -- saw CSE 435

6. Knowledge / Experience Management
Requires systematic approach
Key functions
Retrieval
Adaptation
Maintenance
Storage
Analysis
11/17/2018
Sean White -- saw CSE 435

7. Example – Software Engineering
Sources of Knowledge / Experience
API Documentation
Software Objects (Classes)
Project Documentation (Feasibility Studies, etc.)
Software Manuals (e.g. Design Patterns)
Bug Reports (Ticket Systems)
Programmers
Customers
11/17/2018
Sean White -- saw CSE 435

8. Ex. Software Engineering
Access Patterns (Who needs this?)
Executive Officers
Senior Designers
Developers
QA Staff
Parallels – Manufacturing, Engineering, etc.
11/17/2018
Sean White -- saw CSE 435

9. Ex. Software Engineering
Maintenance (Who can make changes?)
Dedicated Staff? (Experience Engineers)
But, others may require / request changes
Developers
Designers
QA Staff
Need an explicit methodology for maintenance
11/17/2018
Sean White -- saw CSE 435

10. Knowledge / Experience Management – Revisited
Must consider all these sub-problems
Aggregate knowledge across domains
Provide methodology for interaction
Satisfy maintenance goals
Analyze usage
11/17/2018
Sean White -- saw CSE 435

11. Major Tasks for EM Creating the EB and related applications
Maintaining the EB
Gather new experience
Prune old or bad experience
Reorganization
Continual Adaptation
Presentation
Integration (Knowledge, Process)
All to facilitate knowledge reuse!!
11/17/2018
Sean White -- saw CSE 435

12. COIN Corporate Information Network
Provides Intranetwork Experience System
Framework for Integrating EM Technologies
Includes a Knowledge Base
Describes an EMCF
Experience Management Content Framework
11/17/2018
Sean White -- saw CSE 435

13. COIN – ECMF Knowledge Base CB CB CB 11/17/2018
Sean White -- saw CSE 435

14. Knowledge Base Systems
INRECA
Knowledge base system for developing…
Knowledge Base Systems
Note: Make sure everyone’s head is still attached.
11/17/2018
Sean White -- saw CSE 435

15. INRECA Integrated Platform for Reasoning from Cases
Induction and Reasoning from Cases
Methodology for constructing EM systems
Provides
Interfaces for case managers
Methods for knowledge collection
Processes for indexing knowledge
Models for representing knowledge
11/17/2018
Sean White -- saw CSE 435

16. INRECA – Applications Help-desk systems Maintenance systems
Robots, Toxicology
Maintenance systems
Boeing, Diesel ship engines
Risk assessment systems
Wind damage, Gas meters
Experience feedback systems
Nuclear power plants, Electrical systems
Feasibility assessment systems
11/17/2018
Sean White -- saw CSE 435

17. INRECA – Process Abstraction
Knowledge base contains processes
Specific Terminology
11/17/2018
Sean White -- saw CSE 435

18. INRECA – Knowledge Base
Consists of Three Levels of Objects
Common Generic Level
High Level Building Blocks, Approach
Cookbook Level
Types of Applications, Recipes
Application Level
Specific Previous Applications
Each level stores processes for creating products
11/17/2018
Sean White -- saw CSE 435

19. INRECA – Knowledge Base
11/17/2018
Sean White -- saw CSE 435

20. INRECA – KB Contents Structured, linked hypertext
Products
Methods
Resources
Required to meet goals
Full text search -> Retrieval
Inaccurate, limited
Fine for most SW development projects
11/17/2018
Sean White -- saw CSE 435

21. INRECA vs. COIN Knowledge Representation
COIN text objects classification
INRECA hierarchy and classification
Observation
Managerial
Problem
Technical
Guideline
Maintenance
Feasibility
Solution
Organizational
Suggestion
Work flow
Pilots and stuff…
11/17/2018
Sean White -- saw CSE 435

22. INRECA Hierarchy (Classification)
Product
Process
Product
Project Idea
Develop Project
Living Application
Goal
Identification
Feasibility
Study
Organization
Analysis
Managerial
Technical
Organizational
11/17/2018
Sean White -- saw CSE 435

23. INRECA Hierarchy (Classification)
Goal
Identification
Project Idea
Develop Project
Living Application
Project Idea
Define Scope & Goals for Feasibility
Scope & Goal Definition
11/17/2018
Sean White -- saw CSE 435

24. INRECA Hierarchy (Classification)
11/17/2018
Sean White -- saw CSE 435

25. Stamping Advisor (SA) Ford Motor Co. Task (Process) Oriented
Assists in feasibility study (design support)
Task (Process) Oriented
Similar to INRECA
Well integrated into existing tools
Automatic retrieval / insertion
Knowledge drawn from Ford’s Best Practices
Indexed by Verity
11/17/2018
Sean White -- saw CSE 435

26. Stamping Advisor (SA)
11/17/2018
Sean White -- saw CSE 435

27. Graduate Admissions Advisor
University of Wollongong, Australia
Assists decisions regarding applicant acceptance
Classifies information using RDF ontology
Resource Description Framework (Semantic Web)
CBR
Uses agents for information retrieval
Goal driven
Browser based
11/17/2018
Sean White -- saw CSE 435

28. Graduate Admissions Advisor – Agents
Software entities (processes) specialized for
Retrieval
Performs Query
Reuse
Similarity Assessment
Adaptation
Storage
Indexing
Intelligent
Uses reasoning to construct a plan to achieve goal
11/17/2018
Sean White -- saw CSE 435

29. INRECA vs. COIN vs. SA vs. GAA Knowledge Integration
Compiling related knowledge
Possibly across domains
Include all relevant knowledge
Various sources
INRECA uses hierarchy to compose relations
COIN uses classification for retrieval
SA uses tasks to classify needed information
GAA uses RDF (XML – Semantic Web)
11/17/2018
Sean White -- saw CSE 435

30. INRECA – Maintenance (and Reuse)
Performed both during and after project
Project Characterization
Recipe Reuse (or Formulation)
Analyze and Combine Processes
Perform Project Plan
Documentation everywhere…
Analyze Project Plan
Add Project to KB
Add New Recipes
All of this can be in the KB!
11/17/2018
Sean White -- saw CSE 435

31. SA – Maintenance Automatic Takes no extra effort
As issues are identified
Prompts user for information
Adds to knowledge base
Takes no extra effort
Documenting fix enters new knowledge into base
Available immediately to downstream tasks
11/17/2018
Sean White -- saw CSE 435

32. Graduate Admissions Advisor – Maintenance
Automatic case adaptation
Still requires human intervention to verify
Web forms for new cases
Storage agent
Automatically re-indexes database for new cases
11/17/2018
Sean White -- saw CSE 435

33. COIN – Maintenance Maintenance Procedures as Knowledge
Quality Knowledge
Rate the KB/CBR system performance
Procedural Knowledge
How to maintain the KB
Decision Knowledge
Use Quality Knowledge to choose Procedures
Real-time – gathered from data mining
11/17/2018
Sean White -- saw CSE 435