Content deleted Content added
→Cite journal, book, harvnb | Alter: isbn. Add: isbn, series, volume, chapter-url. Removed or converted URL. Some additions/deletions were actually parameter name changes. | You can use this tool yourself. Report bugs here. | via #UCB_Gadget |
Citation bot (talk | contribs) Added bibcode. | Use this bot. Report bugs. | Suggested by Abductive | Category:Infographics | #UCB_Category 53/121 |
||
(17 intermediate revisions by 11 users not shown) | |||
Line 1:
{{confused|Visualization (graphics)}}
'''Software visualization'''<ref>{{cite book |
== Software system information ==
Line 11:
== Objectives ==
The objectives of software visualization are to support the [[program comprehension|understanding of software systems]] (i.e., its structure) and algorithms (e.g., by animating the behavior of sorting algorithms) as well as the analysis and exploration of software systems and their anomalies (e.g., by showing classes with high [[coupling (computer science)|coupling]]) and their development and evolution. One of the strengths of software visualization is to combine and relate information of software systems that are not inherently linked, for example by projecting code changes onto software execution traces.<ref>{{cite book |
Software visualization can be used as tool and technique to explore and analyze software system information, e.g., to discover anomalies similar to the process of [[Data mining|visual data mining]].<ref>({{harvnb|Keim|2002}}; {{harvnb|Soukup|Davidson|2002}}; {{harvnb|Burch|Diehl|Weißgerber|2005}})</ref> For example, software visualization is used to monitoring activities such as for code quality or team activity.<ref>{{cite book |
==Types==
Tools for software visualization might be used to visualize source code and [[software bug|quality defect]]s during software development and maintenance activities. There are different approaches to map source code to a visual representation such as by [[software map]]s<ref>{{cite book |
More or less specialized [[graph drawing software]] is used for software visualization. A small-scale 2003 survey of researchers active in the [[reverse engineering]] and [[software maintenance]] fields found that a wide variety of visualization tools were used, including general purpose graph drawing packages like [[GraphViz]] and
==See also==
* [[Imagix 4D]]
* [[NDepend]]
* [[
* [[Application discovery and understanding]]
* [[Software maintenance]]
Line 42 ⟶ 35:
==Further reading==
*{{cite book |
*{{cite book |
*{{cite book |first=S. |last=Diehl |title=Software Visualization. International Seminar Dagstuhl Castle, Germany, May 20–25, 2001 Revised Papers |volume=2269 |publisher=Springer |year=2002 |doi=10.1007/3-540-45875-1 |isbn=978-3-540-43323-1
*{{cite book |first=S. |last=Diehl |title=Software Visualization — Visualizing the Structure, Behaviour, and Evolution of Software |publisher=Springer
*{{cite book |
*{{cite book |
*{{cite journal |first=D.A. |last=Keim |title=Information visualization and visual data mining |journal=IEEE Transactions on Visualization and Computer Graphics |volume=8 |issue=1 |pages=1–8 |date=January–March 2002 |doi=10.1109/2945.981847 |
*{{cite book |last=Knight |first=C. |chapter=System and Software Visualization |editor=Chang Shi-kuo |series=Handbook Of Software Engineering And Knowledge Engineering |volume=2 |title=Emerging Technologies |
*{{cite book |
*{{cite book |first=M. |last=Lanza |chapter=CodeCrawler — polymetric views in action |title=Proceedings. 19th International Conference on Automated Software Engineering, Linz, Austria, 20 24 Sept. 2004
*{{cite book |
*{{cite book |
*{{cite book |
*{{cite journal |
*{{cite book |
*{{cite book |
*{{cite book |
*{{cite book |first=K. |last=Zhang |title=Software Visualization — From Theory to Practice |publisher=Kluwer |year=2003 |isbn=1-4020-7448-4 }}
Line 66 ⟶ 59:
* [http://code.google.com/p/epdv/ EPDV] Eclipse Project Dependencies Viewer
{{Visualization}}
[[Category:Infographics]]
[[Category:Software maintenance]]
|