Revision as of 16:14, 6 October 2015 edit 96.235.16.228 (talk) →External links ← Previous edit		Revision as of 09:06, 4 February 2016 edit undo 89.73.64.133 (talk) No edit summary Next edit →
Line 17: ==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 ~~maps~~map]]s<ref>D. Limberger et al.: ''Interactive Software Maps for Web-Based Source Code Analysis''. Proceedings of the International Web3D Conference, ACM, pp. 8, 2013.</ref> Their objective includes, for example, the automatic discovery and visualization of quality defects in object-oriented software systems and services. Commonly, they visualize the direct relationship of a class and its methods with other classes in the software system and mark potential quality defects. A further benefit is the support for visual navigation through the software system. 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 [[GraphEd]], UML tools like [[Rational Rose]] and [[Borland Together]], and more specialized tools like [[Visualization of Compiler Graphs]] (VCG) and [[Rigi (software)\|Rigi]].<ref>{{cite journal \| doi = 10.1002/smr.270 \| title=Software visualization in software maintenance, reverse engineering, and re-engineering: a research survey \| journal=Journal of Software Maintenance and Evolution: Research and Practice \| date=2003 \| volume=15 \| issue=2 \| pages=87–109 \| first=Rainer \| last=Koschke}}</ref>{{rp\|99–100}} The range of UML tools that can act as a visualizer by reverse engineering source is by no means short; a 2007 book noted that besides the two aforementioned tools, [[ESS-Model]], [[BlueJ]], and [[Fujaba]] also have this capability, and that Fujaba can also identify [[design pattern]]s.<ref name="Diehl2007">{{cite book\|author=Stephan Diehl\|title=Software Visualization: Visualizing the Structure, Behaviour, and Evolution of Software\|year=May 2007\|publisher=Springer Science & Business Media\|isbn=978-3-540-46505-8\|page=63}}</ref>

Software visualization: Difference between revisions