Difference between revisions of "Concept mapping"
(→Constructing good concept maps) |
(→Description) |
||
| Line 12: | Line 12: | ||
== Description== | == Description== | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
===Constructing good concept maps=== | ===Constructing good concept maps=== | ||
A good way to define the context for a concept map is to construct a Focus Question, that is, a question that clearly specifies the problem or issue the concept map should help to resolve. Every concept map responds to a focus question, and a good focus question can lead to a much richer concept map. | A good way to define the context for a concept map is to construct a Focus Question, that is, a question that clearly specifies the problem or issue the concept map should help to resolve. Every concept map responds to a focus question, and a good focus question can lead to a much richer concept map. | ||
Revision as of 13:36, 31 May 2014
Contents
Definition
Concept mapping is The process of organizing and representing knowledge using concept maps.
Summary
One paragraph.
Description
Constructing good concept maps
A good way to define the context for a concept map is to construct a Focus Question, that is, a question that clearly specifies the problem or issue the concept map should help to resolve. Every concept map responds to a focus question, and a good focus question can lead to a much richer concept map.
Given a selected domain and a defined question or problem in this domain, the next step is to identify the key concepts that apply to this domain. Usually 15 to 25 concepts will suffice. These concepts could be listed, and then from this list a rank ordered list should be established from the most general, most inclusive concept, for this particular problem or situation at the top of the list, to the most specific, least general concept at the bottom of the list.
The next step is to construct a preliminary concept map. Group work may be necessary as one begins to struggle with the process of building a good hierarchical organization. Computer software programs are even better in that they allow moving of concepts together with linking statements and the moving of groups of concepts and links to restructure the map.
It is important to recognize that a concept map is never finished. After a preliminary map is constructed, it is always necessary to revise this map. Other concepts can be added. Good maps usually result from three to many revisions. This is one reason why using computer software is helpful.
Once the preliminary map is built , cross-links should be sought. These are links between concepts in different domains of knowledge on the map that help to illustrate how these domains are related to one another. Cross-links are important in order to show that the learner understands the relationships between the sub-domains in the map.
Finally, the map should be revised, concepts re-positioned in ways that lend to clarity and better over-all structure, and a “final” map prepared. When computer software is used, one can go back, change the size and font style, and add colors to “dress up” the concept map.
Thus, we see that concept maps are not only a powerful tool for capturing, representing, and archiving knowledge of individuals, but also a powerful tool to create new knowledge.
Source: Reference [1]
Outcome
The outcome of concept mapping is a concept map.
References
[1] Joseph D. Novak, Alberto J. Cañas, The Theory Underlying Concept Maps and How to Construct and Use Them, Technical Report IHMC CmapTools 2006-01 Rev 2008-01, http://cmap.ihmc.us/Publications/ResearchPapers/TheoryCmaps/TheoryUnderlyingConceptMaps.htm.
