 |
|
|
|
|
|
|
|
 |
|
||||||
|
|||||||
you are here: > Self > 20.
EKA
| 20.8 |
EKA.KNOWLEDGE PRINCIPLES
|
|
| The Knowledge Principles are the standards by which all other components of the Electronic Knowledge Architecture and the enterprise as a whole are designed and developed. | ||
| The Knowledge Principles represents a core philosophy by which a group or individuals, enterprise, government or union consider knowledge, its classification, purpose and use. eg | ||
| Example of knowledge principles
(1) That the business has one category system for all information, functions, and descriptions. The same category system is used for classifying objects in accounts as well as ordering systems. (2) That the category system is complete and covers all needs. (3) That the category system is based on the standard language used by the business. (4) That the category system is scaleable (i.e. it can be viewed at different levels of detail) |
||
| As simple as the individual knowledge principles appear, their impact on the consequential design of applications and data structures is profound. For example, a single category system implies standards that few large organisations presently display. It implies centralised planning and distributed means by which this information can be understood and maintained. | ||
| Similarly, the belief of a single master record representing a person within the entire enterprise represents a profound shift away from duplicate data stored on duplicate systems. | ||
|
Copyright © 2010 UCADIA. All rights reserved. |
||