Software visualization: Difference between revisions

Revision as of 12:06, 15 March 2020

Revision as of 19:30, 18 March 2020

Line 1:

{{confused|Visualization (graphics)}}

'''Software visualization'''<ref>{{cite book |first=Johannes |last=Bohnet |first2=Jürgen |last2=Döllner |chapter=Analyzing Feature Implementation by Visual Exploration of Architecturally-Embedded Call-Graphs |title=4th International Workshop on Dynamic Analysis |publisher=ACM Press |___location= |year=2006 |pages=41–48 |doi=10.1145/1138912.1138922 |isbn=1595934006 }}</ref><ref>{{harvnb|Diehl|2002}}; {{harvnb|Diehl|2007}}; {{harvnb|Knight|2002}}</ref> or '''software visualisation''' refers to the visualization of information of and related to software systems—either the [[software architecture|architecture]] of its [[source code]] or metrics of their [[Run time (program lifecycle phase)|runtime behavior]]- and—and their development process by means of static, interactive or animated 2-D or 3-D<ref>({{harvnb|Marcus|Feng|Maletic|2003}}; {{harvnb|Wettel|Lanza|2007}})</ref> visual representations of their structure,<ref>{{harvnb|Staples|Bieman|1999}}</ref> execution,<ref>{{cite book |first=J. |last=Trümper |first2=J. |last2=Döllner |first3=A. |last3=Telea |chapter=Multiscale Visual Comparison of Execution Traces |doi=10.1109/ICPC.2013.6613833 |title=Proceedings of the International Conference on Program Comprehension |publisher=IEEE Computer Society |year=2013 |isbn=978-1-4673-3092-3 |pages=53–62 }}</ref> behavior,<ref>({{harvnb|Kuhn|Greevy|2006}}, {{harvnb|Stasko|Brown|Domingue|Price|1998}})</ref> and evolution.

== Software system information ==

Line 13:

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 |first=J. |last=Bohnet |first2=S. |last2=Voigt |first3=J. |last3=Döllner |chapter=Projecting code changes onto execution traces to support localization of recently introduced bugs |title=Proceedings of the 2009 ACM symposium on Applied Computing |date=2009 |pages=438–442 |isbn=9781605581668 |doi=10.1145/1529282.1529378 }}</ref>

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 |first=J. |last=Bohnet |first2=J. |last2=Döllner |chapter=Monitoring Code Quality and Development Activity by Software Maps |doi=10.1145/1985362.1985365 |title=Proceedings of the IEEE ACM ICSE Workshop on Managing Technical Debt |publisher=Association for Computing Machinery |year=2011 |isbn=9781450305860 |pages=9–16 |chapter-url=}}</ref> Visualization is not inherently a method for [[software quality assurance]].{{fact|date=September 2017}}. Software visualization participates to [[Software intelligence|Software Intelligence]] in allowing to discover and take advantage of mastering inner components of software systems.

==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 |first=D. |last=Limberger |first2=B. |last2=Wasty |first3=J. |last3=Trümper |first4=J. |last4=Döllner |chapter=Interactive software maps for web-based source code analysis |title=Proceedings of the 18th International Conference on 3D Web Technology |date=2013 |pages=91–98 |isbn=9781450321334 |doi=10.1145/2466533.2466550 }}</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">{{harvnb|Diehl|2007|p=63}}</ref>

==See also==

Line 25:

* [[NDepend]]

* [[Sotoarc]]

* [[Sourcetrail]][https://www.sourcetrail.com]

* [[Softagram]][https://softagram.com]

* [[Getaviz]][https://github.com/softvis-research/Getaviz]

* [[SonarGraph]][https://www.hello2morrow.com/products/sonargraph]

;;Related concepts:

Line 65 ⟶ 61:

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

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

{{Visualization}}

[[Category:Software engineering]]