Software visualization: Difference between revisions

Revision as of 23:49, 10 December 2014

Revision as of 23:36, 4 February 2015

Line 19:

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]]<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]].<Refref>{{cite doi|10.1002/smr.270}}</ref>{{rp|99-10099–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>

==See also==

Line 59:

==External links==

{{linkfarmexternal links|date=July 2014}}

* [http://www.softvis.org SoftVis] the ACM Symposium on Software Visualization

* [http://vissoft.iro.umontreal.ca VISSOFT] 2nd IEEE Working Conference on Software Visualization

* [http://softvis.wordpress.com/ Software Visualization Blog] information on Software Visualization

* [http://code.google.com/p/epdv/ EPDV] Eclipse Project Dependencies Viewer

=== Research groups ===

* [http://www.hpi.uni-potsdam.de/doellner/research/softvis.html SoftVis at Hasso Plattner Institute for IT Systems Engineering]

Line 69 ⟶ 70:

* [http://www.cc.gatech.edu/gvu/softviz/ SoftVis at Georgia Tec (GVU)]

* [http://www.cs.hut.fi/Research/SVG/ SoftVis at Helsinki University of Technology]

[[Category:Software engineering]]