1 / 33

On-To-Knowledge review Juan-Les-Pins/France, October 06, 2000 Hans Akkermans, VUA

K M. M e thodology. On-To-Knowledge review Juan-Les-Pins/France, October 06, 2000 Hans Akkermans, VUA Hans-Peter Schnurr, AIFB Rudi Studer, AIFB York Sure, AIFB. On-To-Knowledge. WP-5 Methodology and Management Guidelines: covered issues.

halil
Download Presentation

On-To-Knowledge review Juan-Les-Pins/France, October 06, 2000 Hans Akkermans, VUA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. KM Methodology On-To-Knowledge review Juan-Les-Pins/France, October 06, 2000 Hans Akkermans, VUA Hans-Peter Schnurr, AIFB Rudi Studer, AIFB York Sure, AIFB On-To-Knowledge

  2. WP-5 Methodology and Management Guidelines: covered issues Context-oriented requirements for envisaged knowledge management tools Principled foundation for any knowledge management tool in the organisation Knowledge pull and push instead of information overload KM applications remain successful and useful in a changing organisational environment Context-oriented requirements for envisaged knowledge management tools Principled foundation for any knowledge management tool in the organisation Knowledge pull and push instead of information overload KM applications remain successful and useful in a changing organisational environment • Identification of knowledge needs, opportunities and bottlenecks in focus areas of the organisation • Structured construction and validation of ontologies • User-focused introduction of KM tools • Maintenance and steady improvement of existing KM applications

  3. Month 17 Month 8 Month 30 Month 25 WP-5 Workpackage project plan Employment & Evaluation Employment & Evaluation Expansion & Revision Expansion & Revision Final version Final version Baseline version • Baseline version • Based on CommonKADS • Literature study • Systematization of existing practical experiences • Employment of baseline version in the set of case studies • Feedback on KM guidelines • Revision and Expansion based on feedback • General and comprehensive KM guidelines • Practically illustrated by real-life industry cases • Guide book

  4. Agenda • The Knowledge Management challenge • Processes in a KM project • Overall picture • Feasibility study • User driven use cases • Supporting use cases • Focus: ontology development • Summary KM challenge

  5. OTK offers solutions to KM access problems • Benefits • Less time • Lower costs • Higher quality • Usage scenarios • Querying • Navigating • Community of Knowledge Sharing Usually, there is no easy, fast and guided access to knowledge • Problems • Search... find? • No context, no guidance • What you get is hardly ever what you want KM challenge

  6. Example: WWW Search Engine KM challenge

  7. Solution: semantic querying • Context via Ontology • Generalize / refine via Ontology • Match natural language queries into ontological concepts • Predefined queries 1. Usage Scenario: Querying for knowledge • Problems of keyword based search engines • Too many results and often not the right ones • Word selection matters! • Generalization / refinement not possible • Actual systems • WWW Search Engines • e.g. Altavista • Intranet Search Tools • e.g. Verity KM challenge

  8. Example: WWW Portals KM challenge

  9. Solution: Ontology as a guidance for navigation • Guidance via Ontology • Individual views to knowledge • Dynamic views to knowledge • Visualization of hierarchies • Predefined queries 2. Usage Scenario: Navigating • Problems of navigating • Categorization of user differs from systems categories • None or weak user guidance within categorization • Missing visualization • Actual systems • WWW Portals • e.g. Yahoo! KM challenge

  10. Example: Discussion forum KM challenge

  11. Solution: Integrated platform • Organizational issues • Methodology captures users needs and integrates them into application assembly • Embedded in work applications • Ontology-based profiling 3.Usage Scenario: Community of knowledge sharing • Problems of communities • Motivation / incentives • Overhead work • None or weak personalization features available • Actual systems • Discussion forum • e.g. Knowlity • Groupware systems • e.g. Lotus Notes KM challenge

  12. Agenda • The Knowledge Management challenge • Processes in a KM project • Overall picture • Feasibility study • User driven use cases • Supporting use cases • Focus: ontology development • Summary Processes

  13. OTK toolset Push services Ontology development Comm. of know. sharing Maintenance Knowledge engineer Nav. / browse KB Assign people Annotation Management Querying KB Fill KB Knowledge provider Seek knowledge Knowledge worker From usage scenarios to processes: Use cases Processes - Overall pic

  14. Community of Knowledge Sharing Navigate and browse KB Querying KB Input to the KB Ontology develop- ment Annotation of documents Fill the Knowledge Base Maintenance Processes in an OnToKnowledge KM project User-driven Knowledge Management processes Processes - Overall pic Feasibility study Supporting Knowledge Management processes

  15. Input to KM processes People involved People Knowledge assets Application selection Processes Focus domain for ontology development Context Modelling with a Feasibility study Feasibility study Processes Identifying problem/opportunity areas and potential solutions, and putting them into a wider organizational perspective. Deciding about economic, technical and project feasibility, in order to select the most promising focus area and target solution - Feasibility

  16. Tool selection Focus domain for ontology development People involved: GUI CommonKADS - Context Modelling Road Map Start OM-1 worksheet: problems, solutions, context TM-1 worksheet task analysis TM-2 worksheet knowledge item analysis [If feasible] OM-3 worksheet process break-down Processes TM-2 worksheet knowledge item analysis TM-2 worksheet knowledge item analysis - Feasibility OM-5 work-sheet Judge Feasibility (Decision Document) OM-2 worksheet: description of organi-zation focus area Refine Integrate OM-4 worksheet knowledge assets TM-2 worksheet knowledge item analysis AM-1 worksheet agent model [If unfeasible] Stop Context analysis ready

  17. Community of Knowledge Sharing Navigate and browse KB Querying KB Input to the KB Ontology develop- ment Annotation of documents Fill the Knowledge Base Maintenance Processes in an OnToKnowledge KM project User-driven Knowledge Management processes Processes - Overall pic Feasibility study Supporting Knowledge Management processes

  18. Querying for knowledge ? ? ? ? ? ? Processes - User driven use cases • Context via Ontology • Generalize / refine via Ontology • Match natural language queries into ontological concepts • Predefined queries

  19. Example: Predefined queries Processes - User driven use cases

  20. Ontology as a guidance for navigation • Guidance via Ontology • Individual views to knowledge • Dynamic views to knowledge • Predefined queries Processes - User driven use cases

  21. Example: Guidance via Ontology Processes - User driven use cases

  22. Example: Dynamic views to knowledge Processes - User driven use cases

  23. Community of knowledge sharing • Organizational issues • Methodology captures users needs and integrates them into application assembly • Embedded in work applications • Ontology-based profiling Processes - User driven use cases

  24. Community of Knowledge Sharing Navigate and browse KB Querying KB Input to the KB Ontology develop- ment Annotation of documents Fill the Knowledge Base Maintenance Processes in an OnToKnowledge KM project User-driven Knowledge Management processes Processes - Overall pic Feasibility study Supporting Knowledge Management processes

  25. Ontology development ONTOLOGY • Kickoff Refinement Evaluation Maintenance Processes • Requirement specification • Analyze input sources • Develop baseline taxonomy • Concept elicitation with domain experts • Conceptualize and formalize • Add relations and axioms • Revision and expansion based on feedback • Analyze usage patterns • Analyze competency questions • Manage organizational maintenance process - Ontology

  26. Ontology development Processes - Ontology

  27. Ontology development Processes - Ontology

  28. Ontology refinement supported by OntoEdit Processes - Ontology

  29. Community of Knowledge Sharing Navigate and browse KB Querying KB Input to the KB Ontology develop- ment Annotation of documents Fill the Knowledge Base Maintenance Processes in an OnToKnowledge KM project User-driven Knowledge Management processes Processes - Overall pic Feasibility study Supporting Knowledge Management processes

  30. Agenda • The Knowledge Management challenge • Processes in a KM project • Overall picture • Feasibility study • User driven use cases • Supporting use cases • Focus: ontology development • Summary Summary

  31. Tools vs. User-driven use cases Querying the KB Navigate and browse KB Community of knowlege sharing Push services provided to users Inferencing Tool Visualization Tool QL Engine User Interface Knowledge Sharing Facility Summary

  32. Tools vs. Supporting use cases Ontology development Annotation Maintenance Fill Knowledge Base Ontoedit Inferencing Tool Corporum Visualization Tool Knowledge Sharing Facility Summary

  33. Next steps • Employment of baseline version in the set of case studies • Feedback on KM guidelines Summary

More Related