Data and Applications Security Developments and DirectionsOutline of the UnitWhat is Knowledge ManagementKnowledge Management ComponentsKnowledge ModelsSlide 6Slide 7Slide 8Slide 9Slide 10Slide 11Knowledge Management: Strategies, Processes, Metrics and ToolsKnowledge Management ArchitectureOpen System Concept for Knowledge Management ArchitectureKnowledge Exchange & Annotation Engine (KEAN)Software Components “The KeanBeans Component Framework”The Three Versions of KEAN ArchitectureStructure of Version 1 - Beta Version of KEANStructure of Version 2Structure of Version 3Goal of Version 3Secure Knowledge ManagementKnowledge Management for CoalitionsData and Applications Security Developments and DirectionsDr. Bhavani ThuraisinghamThe University of Texas at DallasLecture #16Knowledge ManagementGuest LectureMarch 3, 2005Outline of the UnitWhat is Knowledge Management?Basic concepts: Components and ModelsOrganizational Learning ProcessKnowledge Management ArchitectureSecure Knowledge Management and Trust NegotiationKnowledge ModelsDirectionsWhat is Knowledge ManagementKnowledge 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 knowledgeReference: http://www.commerce-database.com/knowledge-management.htm?source=googleKnowledge Management ComponentsComponents:StrategiesProcessesMetricsCycle:Knowledge, CreationSharing, Measurement And ImprovementTechnologies:Expert systemsCollaborationTrainingWebComponents ofKnowledge Management: Components,Cycle and TechnologiesKnowledge ModelsLevel 1: Highest Level-Mental models utilized by psychologists-Social models (e.g. social network models) used by sociologistsLevel 2: Mid-level-Models utilized by expert systems-Process modelingLevel: Bottom level-Models understood by machines-E.g., rule-based, frame-based, etc.Identification CreationDiffusion - Tacit, ExplicitIntegration ModificationActionOrganizational Learning ProcessMetricsSource: Reinhardt and PawlowskyIncentivesalso see: Tools in Organizational Learninghttp://duplox.wz-berlin.de/oldb/forslin.htmlSix Principals of Effective Learning•Effective Learning Requires:-Understanding1) Mental models, paradigms, context, observation, assumptions, opinion, fact, truth2) Systems Thinking - Variation -Skills3) Ability to challenge assumptions 4) Listen to Understand-Process5) Complete observe, assess (reflection, gain understanding), design (develop theory, prediction, vision), implement (test), cycle6) Teach othersKnowledge 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 PressmanLearning 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 ProcessKnowledge Management: Incentive-based ApproachesReceiverPositive Incentives • Knowledge Gained• Can teach others what is learnedTeacherPositive Incentives • “Knowledge Transfer Champion” prestige•Can improve knowledgeNegative Incentives•Time•Unqualified teacherNegative Incentives•Time•Students not willing to learnEffective 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 ToolsKnowledge Management: Within and Across Corporations and AgenciesStrategiese.g., Management Plans; Policies;Data sharing vs. PrivacyProcessese.g., best practicesMetricse.g., web usageToolse.g., Semantic WebKnowledge Management ArchitectureKnowledge Creation and Acquisition ManagerKnowledge RepresentationManagerKnowledge ManipulationManagerKnowledge Dissemination and SharingManagerOpen System Concept for Knowledge Management Architecture-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 softwareKnowledge Exchange & AnnotationEngine (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 browserSoftware Components“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-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 objectsStructure of Version 1 - Beta Version of KEAN “Thin http” client•Html•JavaScript•AppletsStored Procedures(PL/SQL)Database tier•ORACLEORACLE WEBSERVERStructure of Version 2 “Thick” clientDatabase
View Full Document