Lecture 7: Knowledge Capture Systems

Slides:



Advertisements
Similar presentations
Knowledge Acquisition and Modelling Concept Mapping.
Advertisements

Modeling Human Reasoning About Meta-Information Presented By: Scott Langevin Jingsong Wang.
Analyzing the tradeoffs between breakup and cloning in the context of organizational self-design By Sachin Kamboj.
Lecture 13 Revision IMS Systems Analysis and Design.
Concept Mapping. What is Concept Mapping ? Concept mapping is a technique for representing knowledge in graphs. This technique was developed by Professor.
Computational Thinking Related Efforts. CS Principles – Big Ideas  Computing is a creative human activity that engenders innovation and promotes exploration.
More than Knowing At Mercy College Karin Gilbert & Michelle Cotter.
Becerra-Fernandez, et al. -- Knowledge Management 1/e -- © 2004 Prentice Hall Chapter 14 Knowledge Capture Systems: Systems that Preserve and Formalize.
Module 3: Business Information Systems Chapter 11: Knowledge Management.
ARTIFICIAL INTELLIGENCE [INTELLIGENT AGENTS PARADIGM] Professor Janis Grundspenkis Riga Technical University Faculty of Computer Science and Information.
Business Analysis and Essential Competencies
Ecological Interface Design
3231 Software Engineering By Germaine Cheung Hong Kong Computer Institute Lecture 12.
Knowledge Management in Theory and Practice
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Basic Concepts Software Architecture. What is Software Architecture? Definition: – A software architecture is the set of principal design decisions about.
1 Introduction to Software Engineering Lecture 1.
Illustrations and Answers for TDT4252 exam, June
Chapter 15: KNOWLEDGE-BASED INFORMATION SYSTEMS. What is Knowledge? Data: Raw facts, e.g., Annual Expenses = $2 million Information: Data given context,
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Knowledge Management in Theory and Practice
Artificial Intelligence: Research and Collaborative Possibilities a presentation by: Dr. Ernest L. McDuffie, Assistant Professor Department of Computer.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Ecological Interface Design Overview Park Young Ho Dept. of Nuclear & Quantum Engineering Korea Advanced Institute of Science and Technology May
1 2. Knowledge Management. 2  Structuring of knowledge enables effective and efficient problem solving dynamic learning strategic planning decision making.
Becerra-Fernandez & Sabherwal -- Knowledge Management © 2010 M.E. Sharpe Chapter 7 Knowledge Capture Systems: Systems that Preserve المحافظة and Formalize.
The Study of Organizations
Knowledge Representation Techniques
CHAPTER 6 Decision Making
Classifications of Software Requirements
Fundamentals of Information Systems, Sixth Edition
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Object-Oriented Analysis and Design
Knowledge Capture Systems: Systems that Preserve and
Unified Modeling Language
The Systems Engineering Context
Organization and Knowledge Management
Implementing Knowledge Management in Organization
Iterative design and prototyping
Software Quality Engineering
The Nature and Scope of Organizational Behavior
Abstract descriptions of systems whose requirements are being analysed
Requirements Elicitation – 1
By Dr. Abdulrahman H. Altalhi
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
المپیاد علمی دانشجویان پزشکی
MANAGING KNOWLEDGE FOR THE DIGITAL FIRM
SBD: Analyzing Requirements
Leader-Member Exchange Theory
Informatics 121 Software Design I
HCI – DESIGN RATIONALE 20 November 2018.
Path-Goal Theory Lecture 7 Md. Mahbubul Alam, PhD Associate Professor
May 17, 2018 Deedee Myers, PhD, MA, MSC, PCC
Chapter 20 Object-Oriented Analysis and Design
Geospatial and Problem Specific Semantics Danielle Forsyth, CEO and Co-Founder Thetus Corporation 20 June, 2006.
Business and Professional Excellence in the Workplace
KNOWLEDGE REPRESENTATION
Section VI: Comprehension
Chapter 11 user support.
Skills Approach Lecture 3 Md. Mahbubul Alam, PhD Associate Professor
KNOWLEDGE MANAGEMENT (KM) Session # 37
KNOWLEDGE MANAGEMENT (KM) Session # 31
SYSTEM TESTING AND DEPLOYMENT
Human Computer Interaction Lecture 14 HCI in Software Process
Lecture 6: Knowledge Application Systems
Appendix A Object-Oriented Analysis and Design
Chapter 9 Authentic Leadership
Chapter 4 System Modeling.
Presentation transcript:

Lecture 7: Knowledge Capture Systems Md. Mahbubul Alam, PhD Associate Professor Dept. of AEIS Sher-e-Bangla Agricultural University

Chapter Highlights Describe what are knowledge capture systems Explain how to elicit and store organizational and individual knowledge Explain the two types of knowledge capture systems To capture knowledge in educational settings To capture tactical knowledge

What is knowledge capture systems? A process of eliciting explicit or tacit knowledge from people, artifacts or organizational entities. Rely on mechanism and technologies to support externalization and internalization.

Capturing Tacit Knowledge Organizational stories: A detailed narrative of past management actions, employee interactions, or other intra- or extraorganizational events that are communication informally within organizations. Typically includes a plot, major characters, an outcome, and an implied moral. Originated within organization and typically reflect organizational norms, values, and culture. Stories make information more vivid,, engaging, entertaining, and easily related to personal experience. Contains rich contextual details, therefore, ideal for capturing tacit knowledge.

Organizational Storytelling: Guidelines Stimulate the natural telling and writing of stories. Rooted in anecdotal material reflective of the community in question. Should not represent idealized behavior. An organizational program to support storytelling should not depend on external experts for its sustenance. Organizational stories are about achieving a purpose, not entertainment. Be cautious of over-generalizing and forgetting the particulars. Adhere to the highest ethical standards and rules.

Organizational Storytelling: Important considerations Effective means of capturing and transferring tacit organizational knowledge. Identify people in the organization willing to share how they learned from others. Use metaphors to confront difficult organizational issues. Storytelling provides a natural methodology for nurturing communities because it: builds trust knowledge seekers learn from knowledge providers. unlocks passion is non-hierarchical storytelling is collaborative.

Areas where storytelling can be effective Igniting action in knowledge-era organizations Bridging the knowing-doing gap Capturing tacit knowledge To embody and transfer knowledge To foster innovation Enhancing technology Individual growth Launching/Nurturing communities of practice thematic groups (World Bank) learning communities or learning networks (HP) best practice teams (Chevron) family groups (Xerox)

How to organize & use stories: Techniques Anthropological observation Naïve interviewers Caused the subjects to naturally volunteer their anecdotes Curiosity resulted in a higher level of knowledge elicitation. Storytelling circles Formed by groups having a certain degree of coherence and identify. Methods: Dit spinning(fish tales) represents human tendencies to escalate or better the stories previously. Alternative histories Shifting character or context Indirect stories character similarities with the real-life character are considered to be pure coincidence. Metaphor common reference for the group to a commonly known story, cartoon or movie.

Knowledge representation: Concept Maps Based on Ausubel’s learning psychology theory. Concepts, enclosed in circles or boxes are perceived regularities in events or objects designated by a label. Two concepts connected by a linking word to form a proposition, semantic unit or unit of meaning. Vertical axis expresses a hierarchical framework for organizing the concepts. Inclusive concepts are found at the top, progressively more specific, less inclusive concepts arranged below. Relationships between propositions in different domains are cross-links.

Concept Maps

Knowledge capture systems: CmapTools To capture and formalize knowledge resulting in context rich knowledge representation models to be viewed and shared through the Internet. Alleviates navigation problem with concept maps. Serve as the browsing interface to a domain of knowledge. Icons below the concept nodes provide access to auxiliary information. Linked media resources and concept maps can be located anywhere on the Internet. Browser provides a window showing the hierarchical ordering of maps.

Knowledge Representation: Context-based Reasoning Tactical knowledge Human ability that enables domain experts to assess the situation at hand (therefore short-term) among a myriad of inputs. Select a plan that best fits current situation, and executing plan Recognize and treat only the salient features of the situation Gain a small, but important portion of the available inputs for general knowledge. Therefore, tactical knowledge can be defined as “the continuous and dynamic process of decision making by a performing agent (human or otherwise) who interacts with his/its environment while attempting to carry out a mission in that environment.”. e.g., Commanding officer of Submarine.

Context-based Reasoning (CxBR): Principles & Tool Context-set of actions and procedures that properly address the current situation. As mission evolves, transition to other context may be required to address the new situation. What is likely to happen in a context is limited by the context itself. Mission Context-defines the scope of the mission, its goals, the plan, and the constraints imposed. Main Context-contains functions, rules and a list of compatible subsequent Main Contexts. Sub-Contexts-abstractions of functions performed by the Main Context which may be too complex for one function. Tool: Context-based Intelligent Tactical Knowledge Acquisition (CITKA) Uses its own knowledge base to compose a set of intelligent queries to elicit the tactical knowledge of the expert.

Context Hierarchy

Barriers to Use of Knowledge Capture Systems Two perspectives Knowledge Engineer (who seeks to build such systems) Requires developing some idea of the nature and structure of the knowledge very early in the process. Must attempt to become versed in the subject matter, or the nature of knowledge. An automate system for knowledge capture without a-priori knowledge of the nature, is essentially not possible. Subject matter expert (who would interact with an automated knowledge capture system to preserve his knowledge) Need to take the initiative of learning how to interact with the system. Some people may be resistant to trying new things. Can be overcome, with adequate training and the utilization of user-friendly interfaces.

Learning by observation capture knowledge Research on how humans and animals learn through observation. Use of learning through observation to automate the knowledge acquisition task. Learning by observation shows promise as a technique for automatic capture of expert’s knowledge, and enable computers to automatically “learn”.

Question Please ?