Data and applications security developments and directions
1 / 23

Data and Applications Security Developments and Directions - PowerPoint PPT Presentation

  • Uploaded on
  • Presentation posted in: General

Data and Applications Security Developments and Directions. Dr. Bhavani Thuraisingham The University of Texas at Dallas Lecture #16 Knowledge Management Guest Lecture March 3, 2005. Outline of the Unit. What is Knowledge Management? Basic concepts: Components and Models

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.

Download Presentation

Data and Applications Security Developments and Directions

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript

Data and applications security developments and directions
Data and Applications Security Developments and Directions

Dr. Bhavani Thuraisingham

The University of Texas at Dallas

Lecture #16

Knowledge Management

Guest Lecture

March 3, 2005

Outline of the unit
Outline of the Unit

  • What is Knowledge Management?

  • Basic concepts: Components and Models

  • Organizational Learning Process

  • Knowledge Management Architecture

  • Secure Knowledge Management and Trust Negotiation

  • Knowledge Models

  • Directions

What is knowledge management
What is Knowledge Management

  • Knowledge management, or KM, is the process through which organizations generate value from their intellectual property and knowledge-based assets

  • KM involves the creation, dissemination, and utilization of knowledge

  • Reference:

Knowledge management components
Knowledge Management Components


Components of



Cycle and





Knowledge, Creation

Expert systems


Sharing, Measurement



And Improvement




Knowledge models
Knowledge Models

  • Level 1: Highest Level

    • Mental models utilized by psychologists

    • Social models (e.g. social network models) used by sociologists

  • Level 2: Mid-level

    • Models utilized by expert systems

    • Process modeling

  • Level: Bottom level

    • Models understood by machines

    • E.g., rule-based, frame-based, etc.

Data and applications security developments and directions

Organizational Learning Process

Diffusion -

Tacit, Explicit









Reinhardt and Pawlowsky

also see: Tools in Organizational Learning

Data and applications security developments and directions

Six Principals of Effective Learning

  • Effective Learning Requires:

    • Understanding

      1) Mental models, paradigms, context, observation, assumptions, opinion, fact, truth

      2) Systems Thinking - Variation

    • Skills

      3) Ability to challenge assumptions

      4) Listen to Understand

    • Process

      5) Complete observe, assess (reflection, gain understanding), design (develop theory, prediction, vision), implement (test), cycle

      6) Teach others

Data and applications security developments and directions

Knowledge Management Metrics - The Goal of Metrics

  • Measuring Success (How am I doing?)

  • Benchmarking (How am I comparatively doing?)

  • Tracking Improvement (Am I getting better?)

  • Direct

    • future investment (technology, employees)

    • strategy

    • alignment (culture, incentives)

“One way to ensure your doing worse is to not measure” - Adapted from Pressman

Data and applications security developments and directions

Learning By-Product Measures

  • Papers in Competitive Journals and Magazines

  • Percentage New Technology compared to all Technology

  • Process Cycle Time

  • Employee Surveys

    • Involvement with decisions

    • Recognition for work achieved

    • Access to information

    • Rewarding risk taking

    • Overall Satisfaction

  • Employee Retention

  • ‘Employee Suggestion Process

Data and applications security developments and directions

Knowledge Management: Incentive-based Approaches

  • Receiver

  • Positive Incentives

    • Knowledge Gained

    • Can teach others what is learned

  • Teacher

  • Positive Incentives

    • “Knowledge Transfer Champion” prestige

    • Can improve knowledge

  • Negative Incentives

    • Time

    • Unqualified teacher

  • Negative Incentives

    • Time

    • Students not willing to learn

Data and applications security developments and directions

Effective Information Access Vision

  • Available - If information exists, it is available for retrieval

    • Internal and External sources

    • Processed from available data

  • Relevant - Information retrieved applies to information need

    • If available, information is retrieved

  • Useful - Information has a positive impact

    • Influences behavior to improve productivity - best practices and techniques

    • Raises understanding of a domain

    • Not misinformation

  • Accessible - Information obtained during the time of need; In common language and ontology.

Knowledge management strategies processes metrics and tools
Knowledge Management: Strategies, Processes, Metrics and Tools

Knowledge Management: Within and Across

Corporations and Agencies


e.g., Management

Plans; Policies;

Data sharing vs. Privacy


e.g., best



e.g., Semantic Web


e.g., web usage

Knowledge management architecture
Knowledge Management Architecture Tools

Knowledge Creation and Acquisition Manager

Knowledge Representation


Knowledge Dissemination and Sharing


Knowledge Manipulation


Open system concept for knowledge management architecture
Open System Concept for Knowledge Management Architecture Tools

  • When in need of a component:

    • Use a COTS one if available

    • Build one with a standard API and share it, reusing design from other components

    • Build a domain-specific one and share it

  • Allow component integrators and users to tailor or configure applications from components:

    • Compose systems from components

    • Tailor a component in unanticipated ways

    • Tailor a component in anticipated ways

  • Build software that can interoperate with other software

Knowledge exchange annotation engine kean
Knowledge Exchange & Annotation ToolsEngine (KEAN)

  • Resides on any web-accessible knowledge base (any intranet, www)

  • Increases incentive to share information

    • Author gets positive and negative feedback about information that is submitted

    • Feedback system - no more publishing documents that disappear into the ether

    • Prestige - top rated document views

  • Quality filters steer user towards best information

  • Domain specific instances of KEAN are created

  • Works with Java enabled browser

Software components the keanbeans component framework
Software Components Tools“The KeanBeans Component Framework”

  • Provides the infrastructure for the creation of an open system for KMA

  • A pallet of JavaBeans components that facilitate the creation of web tracklets by power users, component integrators and developers

  • Uses industry standards to prompt reuse. Examples: JavaBeans, enterprise JavaBeans(EJB), infobus and Java Foundation Classes(JFC)

The three versions of kean architecture
The Three Versions of KEAN Architecture Tools

  • Version 1 “beta version”

    • No reuse

    • Two-tiered

    • Stored procedures

  • Version 2 “newest version”

    • GUI reuse via JavaBeans

    • Two-tiered

    • JDBC access to database

  • Version 3 “final version”

    • Logic reuse via Enterprise JavaBeans (EJB)

    • Three-tiered

    • CORBA access to objects

Structure of version 1 beta version of kean
Structure of Version 1 - Beta Version of KEAN Tools






  • Html

  • JavaScript

  • Applets


“Thin http” client

Database tier

Structure of version 2
Structure of Version 2 Tools

Code reuse with a two tier architecture




  • KeanBeans


“Thick” client

Database tier

Structure of version 3
Structure of Version 3 Tools

web Server

  • KeanBeans

  • RDBMSs

  • and



  • EJB

“thin” client

middle tier

server tier

Goal of version 3
Goal of Version 3 Tools

  • Interoperability with other systems - “want to build an open system”

  • Developers do not have to code in Java to reuse our code. Will be able to get to our objects through the CORBA ORB

  • A more scaleable system “thin client”

  • Persistent storage of objects

Secure knowledge management
Secure Knowledge Management Tools

  • Protecting the intellectual property of an organization

  • Access control including role-based access control

  • Security for process/activity management and workflow

    • Users must have certain credentials to carry out an activity

  • Composing multiple security policies across organizations

  • Security for knowledge management strategies and processes

  • Risk management and economic tradeoffs

  • Digital rights management and trust negotiation

Knowledge management for coalitions
Knowledge Management for Coalitions Tools

Knowledge for Coalition









Knowledge for

Knowledge for

Agency A

Agency C


Knowledge for

Agency B

  • Login