Concept map: Difference between revisions
No edit summary |
(Added info on DRed (sent by Dustin DeHaven)) |
||
| Line 12: | Line 12: | ||
==See Also== | ==See Also== | ||
* [[Diagramming Software]] | * [[Diagramming Software]] | ||
* DRed (Design Rationale editor) ([http://www.users.muohio.edu/burgeje/dred_eindhoven.pdf] [http://www.kunst.dtu.dk/upload/institutter/ipl/sektioner/2004asme.pdf]) | |||
==References== | ==References== | ||
<references/> | <references/> | ||
Revision as of 21:04, 10 November 2011
This page was tagged as a candidate for deletion. If this page does not meet our criteria for deletion, please remove this notice.
(Explanation: single link redirected to wikipedia)
A concept map is a diagram showing the relationships among concepts. They are graphical tools for organizing and representing knowledge.
Concepts, usually represented as boxes or circles, are connected with labeled arrows in a downward-branching hierarchical structure. The relationship between concepts can be articulated in linking phrases such as "gives rise to", "results in", "is required by," or "contributes to".
The technique for visualizing these relationships among different concepts is called "Concept mapping".
An industry standard that implements formal rules for designing at least a subset of such diagrams is the Unified Modeling Language (UML). [1]
See Also
- Diagramming Software
- DRed (Design Rationale editor) ([1] [2])