Difference between revisions of "Wiki User's glossary"

From COST Action FP0804: FORSYS
Jump to: navigation, search
Line 22: Line 22:
  
 
'''
 
'''
References'''
+
 
 +
== References ==
 +
'''
  
 
- Heinrichs, J.H., Hudspeth, L.J., Lim, J.S., 2003. Knowledge management. In: Hossein Bidgoli, ed., Encyclopedia of Information Systems, Academic Press, Amsterdam, Volume 3: 13-31;
 
- Heinrichs, J.H., Hudspeth, L.J., Lim, J.S., 2003. Knowledge management. In: Hossein Bidgoli, ed., Encyclopedia of Information Systems, Academic Press, Amsterdam, Volume 3: 13-31;

Revision as of 15:55, 23 June 2011

Knowledge management (KM) = systematic strategy of creating, conserving, and sharing knowledge to increase the performance of individuals, companies, or nations (Heinrichs et al., 2003).

KM technique = set of procedures and tools used to achieve a specific purpose in knowledge management. In others words, techniques refer to the goals we want reach, the activities we will carry out to reach the targets and the tools used in the procedures.

KM tool = tool which support the performance of applications, activities or actions such as generation, knowledge codification or knowledge transfer (Ruggles, 1997).It can be say that the goal of a KM tool is not to manage knowledge by itself but to facilitate the implementation of the knowledge process. Not all tools are computer based but much emphasis is placed on these electronic tools due to their dynamic capabilities, quick evolution, and organizational impacts (Tyndale, 2002)

Technology = making, usage and knowledge of tools, techniques, crafts, systems or methods of organization in order to solve a problem or serve some purpose.








References

- Heinrichs, J.H., Hudspeth, L.J., Lim, J.S., 2003. Knowledge management. In: Hossein Bidgoli, ed., Encyclopedia of Information Systems, Academic Press, Amsterdam, Volume 3: 13-31;

- Ruggles, R.L., 1997. Knowledge management tools, Butterworth-Heinemann, 1997;

- Tyndale, P., 2002. A taxonomy of knowledge management software tools: origins and applications. Evaluation and Program Planning 25 (2002) 183-190;