Software visualization: Difference between revisions

Revision as of 01:42, 1 April 2016

Revision as of 11:34, 10 August 2016

Line 1:

{{confused|Visualization (computer graphics)}}

{{mergefrom|Software map|date=August 2014}}

'''Software visualization'''<ref>Johannes Bohnet, Jürgen Döllner: ''Analyzing Feature Implementation by Visual Exploration of Architecturally-Embedded Call-Graphs''. 4th International Workshop on Dynamic Analysis, ACM, ACM Press, pp. 41–48, 2006.</ref><ref>Diehl, 2002; Diehl, 2007; Knight, 2002)</ref> or '''software visualisation''' refers to the visualization of information of and related to software systems -eithersystems—either the [[software architecture|architecture]] of its [[source code]] or metrics of their [[Run time (program lifecycle phase)|runtime behavior]]- and their development process by means of static, interactive or animated 2-D or 3-D<ref>(Marcus et al., 2003; Wettel et al., 2007)</ref> visual representations of their structure,<ref>(Staples & Bieman, 1999)</ref> execution,<ref>J. Trümper et al.: ''Multiscale Visual Comparison of Execution Traces''. Proceedings of the International Conference on Program Comprehension, IEEE Computer Society, pp. 53-62, 2013.</ref> behavior,<ref>(Kuhn et al., 2006, Stasko et al., 1997)</ref> and evolution.

== Software system information ==