Paul Werbicki
Concept Mapping Summary and Critical Comments
Concept mapping is a very simple and intuitive type of visual language that represents knowledge in a pictorial graph form. Concepts maps are essentially graphs of nodes connected by arcs that represent relationships between these nodes (Kremer 1998). Many different styles may be used when creating concept maps to help bring visual understanding to what is being mapped. Node and arc labels may be used, along with different line colors; line styles; fill colors; fill styles; shadows and node shapes. All of these elements combine to produce a visual representation of a concept for easier understanding, communication and retention.
When classifying concepts maps a distinction is made between informal concept maps and formal concept maps. An informal concept map might be used for “naive” users (such as executives who always ask for the “big picture”). Another place where informal concept maps are useful is in meetings as brainstorming tool. The ease and speed of information capture when creating informal concept maps helps to facilitate visual communication especially when the problem domain is unclear or has not yet been well defined. Formal concept maps are used when there is a need for precision without ambiguity. Such precision is required in software architecture or design documents, or when a computer will be interpreting the concept map (such as in the case of UML diagrams).
Concept mapping is a powerful tool that is used extensively in software engineering. Concept mapping can be done using a variety of tools such as pen and paper, on a whiteboard with dry erase markers, or on a computer using mapping software. Concept mapping is the process of creating the concept map artifact, and both are independent of the tool being used. Whiteboards are a very popular tool for concept mapping. These maps tend to be informal, but they provide a great mechanism for discussing ideas and concepts and getting them down in a pictorial form. Nowadays it is uncommon to find a software development group without a whiteboard.
Concept mapping software is another tool that is used extensively to create concept maps. Unlike whiteboards these tools make it very easy to create formal concept maps that can then be used for computer interpretation. Many programs exist for this purpose including Rational Rose and Microsoft’s Visio, two popular software packages used extensively in business analysis and software engineering.
Using software tools to create concept maps generally have a limited role in meetings and brainstorming sessions, as they are very distracting to use when there are more then two people involved. With whiteboards, because they are so simple and intuitive, they act like an extension to your hand and so the fact you are using them does not really enter the meeting. Most often a picture of the whiteboard (using a digital camera) or a printout (on the more expensive whiteboards) is taken at each stage during the meeting and these are later transcribed into formal concepts maps using the software tools. These can then are manipulated and tend to form some of the artifacts of the software design.
URLs
SMART Ideas Software is available at
Concept mapping software can be accessed at
References
Kremer, R. (1998). SENG 611 Requirements Engineering – Concept Mapping. University of Calgary.
Shaw, M.L.G. and Gaines, B.R. (1995). Concept Maps as Hypermedia Components. Knowledge Science Institute, University of Calgary.
1