Knowledge Gap
Knowledge GapTechnical
In RAFAEL I learned a 4-level system of KnowledgeGap-s used for assessing TechnicalRisk-s:
Level 1 - We have done this before. In hardware, this means fabricating again the same thing. In software, it means reusing almost all the code, maybe with some minor adjustments (like fonts and colors).
Level 2 - We have done similar things before. This is the gap involved in most new projects. For example: Porting an existing system to a different environment. The system is not new, the environment is not new - only the combination is new.
Level 3 - Someone else has done this before. Getting into a new business or technological field. For example: Adopting OO technologies.
Level 4 - It has never been done before. The good stuff :) The first space shuttle would be a good example.
Risk was assessed based on the level of KnowledgeGap and the project estimated complexity.
This looks vaguely similar to the so-called OrdersOfIgnorance.
Societal
The knowledge gap theory was first proposed by Tichenor, Donohue and Olien at the University of Minnesota in the 70s. They believe that the increase of information in society is not evenly acquired by every member of society: people with higher socioeconomic status tend to have better ability to acquire information (Weng, S.C. 2000). This leads to a division of two groups: a group of better-educated people who know more about most things, and those with low education who know less.
EditText of this page
(last edited March 8, 2011)
or FindPage with title or text search