150 likes | 286 Views
Basics of Knowledge Management. ICOM5047 – Design Project in Computer Engineering ECE Department J. Fernando Vega Riveros, Ph.D. What is knowledge?.
E N D
Basics of Knowledge Management ICOM5047 – Design Project in Computer EngineeringECE Department J. Fernando Vega Riveros, Ph.D.
What is knowledge? Merriam-Webster Dictionary - a (1) : the fact or condition of knowing something with familiarity gained through experience or association (2) : acquaintance with or understanding of a science, art, or technique b (1) : the fact or condition of being aware of something (2) : the range of one's information or understanding <answered to the best of my knowledge> c: the circumstance or condition of apprehending truth or fact through reasoning : COGNITIONd: the fact or condition of having information or of being learned <a man of unusual knowledge>
What is knowledge? Knowledge is a key organizational assetthat creates and adds value to the organization’s products and services. It is composed of those insights and understandings that give meaning to the information and data at the organization’s disposal. Knowledge originates in the minds of knowing subjects, who evaluate and interpret it in the light of the framework provided by their experiences, values, culture and learning. In the organizational context, knowledge takes a range of explicit forms and formats, including processes, procedures and documents, as well as more tacit forms, including values, beliefs, emotions, judgments and prejudices. If properly applied, all forms of knowledge can provide the driving force for action.Edward Sallis and Gary Jones, Knowledge Management in Education
Types of Knowledge • Tacit knowledge • Explicit knowledge • Critical knowledge • Embedded knowledge • Formal knowledge • Informal knowledge
What is Knowledge Management? • Knowledge is our most important engine of production – Alfred Marshal • Knowledge the key resource of the 21st-century • Problem today is not how to find information but how to handle it!
What is Knowledge Management? • Set of strategies, practices and supporting technologies that helps to improve the use and sharing of data, information and knowledge in decision-making. • Learning to know what we know • Know what we do not know Knowledge Information Data
A model of a Knowledge Management System CoP/CoI Repositories Data & Information Sources Knowledge Resources Network Repositories Data & Information Sources
Goal of this presentation • Practice and develop a taxonomy for documents, data and information used in the project • Use the taxonomy to organize the directory structure for the document repository of the project
Taxonomies and ontologies • Taxonomy is the classification of information entities in the form of a hierarchy, according to the presumed relationships of the real-world entities they represent. • Ontology defines the common words and concepts (the meaning) used to describe and represent an area of knowledge. It is an engineering product consisting of a specific vocabulary used to describe reality, plus a set of explicit assumptions regarding the intended meaning of that vocabulary
What will we obtain from using a taxonomy in this course? • Organization of information in the project repository • Easy finding of information • Order in the storage of information • Facilitate collaboration of team members through information sharing
The ontology spectrum (from Daconta et-al. The Semantic Web, Wiley 2003) Modal Logic First Order Logic Local Domain Theory Is disjoint subclass of + transitivity property Description logic DAML+OIL, OWL UML Conceptual Model Is subclass of RDF/S XTMExtended ER Thesaurus Has narrower meaning than ER Schema Taxonomy Is subclassification of Relational Model
Steps in the development of the project taxonomy • Establish information requirements for the project • Data requirements and purpose (project assessment – metrics and indicators of achievement, costs, quality control, etc) • Information and document requirements (internal and external communication (with customer, providers, management, team members, etc), design and implementation documentation, customer feedback, contingencies and solutions, decisions, legal issues, user manuals, etc.) • Brain storming – terms in knowledge domain of project • Discuss and organize hierarchy of terms • Implement directory in document repository • Appoint responsible for information management in project • Agree on taxonomy and repository maintenance • Agree on information policy and management processes
Issues in information management • Metadata: naming, subject, author, manager, company, category, keywords and terms, comments • Document naming (optional) • Confidentiality, disclosure and security