KnowledgeBusAn Architecture to Support Intelligent and

Flexible Knowledge Management

Johannes Magenheim, Knut Hinkelmann, Wolfgang Reinhardt, Tobias Nelkner, Kai Holzweißig, and Michael Mlynarski

Who are we?

• MoKEx (Mobile Knowledge Experience)

• ongoing interdisciplinary international project series

• universities and industrial partners from Germany and Switzerland

• interested in innovativeways of information management with various existingknowledge sources

• analyzing training andinformation managementscenarios at companiessites 2

Where‘s the problem?

• most corporate system architectures are characterized by a rich heterogeneity of IT systems

• leads to information silos within organizational units

• information is stored in various different systems that often do not interface with each other

• People do not know where to find the stored / searched information

• EAI tries to solve these problems by various middleware technologies or by SOAs

• EAI uses data-centric approaches

• Our goal: design a content- and information oriented architecture for knowledge management with unified access to all objects in all subsystems

3

The Vision

• support the user‘s easy access to information

• create a Single Point of Information that provides access to all information in all coupled applications

• no more need to worry about

• which application holds the information

• where is an information physically stored

• how to access the favoured information4

The KnowledgeBus

• central integration interface for all coupled subsystems

• managing all communication between the systems

• extension points to attach new subsystems to the KnowledgeBus

• metadata database as essential part of the architecture

• customized and extended set of LOM

• automatically generated, manually entered and contextual metadata

• central storage of meta-information of any object

5

The first prototype ifKMS

• three different kinds of subsystems

• LMS (e-tutor)

• DMS (Xinco DMS)

• Problem Solver (Solvatio)

• different degrees of integration of single subsystems

• interfaces for administrationand retrieval of objects

6

The first prototype ifKMS (II)

7

• single storage pointas network volume

• no folder structure

• store, annotate

• unified search

• search for any metadata available

• information based approach

The first prototype ifKMS (III)

8

• extended search

• taxonomies and processes• search results

• actions on objects

What‘s next?

• extended empirical tests and integration in real-life scenarios

• actual project execution focusses on highly automatically metadata extraction and semantic analysis of knowledge objects

• more flexible and extensible architecture

• from bus architecture to server architecture

• flexible docking of subsystems via so called adapters

• next prototype in 1st Quarter 20089

Quest ons

University of Paderborn

Faculty of Electrical Engineering, Computer Science and Mathematics

Working Group Didactics of Informatics

Dipl.-Inform. Wolfgang Reinhardt

wolle@upb.de

http://ddi.upb.de

http://www.mokex.de10

?

Thank you for listening