Software visualization: Difference between revisions

Revision as of 15:25, 3 November 2005

Revision as of 15:29, 3 November 2005

Line 1:

Software Visualization (Diehl, 2002; Knight, 2002) is concerned with the static or animated 2-D or 3-D (Marcus et al., 2003) visual representation of information about software systems based on their structure (Staples & Bieman, 1999), size (Lanza, 2004), history (Lopez et al., 2004), or behavior (Stasko et al., 1997). Typically, the information used for [[visualization]] is [[software_metricssoftware metric|software metric]] data from measurement activities. [[Visualization]] is inherently not a method for [[software quality assurance]] but can be used to manually discover anomalies similar to the process of [[visual data mining]] (Keim, 2002; Soukup, 2002).

The objectives of software visualizations are to support the [[program_understanding|understanding]] of software systems (i.e., its structure) and algorithms (e.g., by animating the behavior of sorting algorithms) as well as the analysis of software systems and their anomalies (e.g., by showing classes with height [[coupling]]).