Content deleted Content added
Fact tag |
m Dating maintenance tags: {{Fact}} |
||
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>J. Bohnet et al.: ''Projecting Code Changes onto Execution Traces to Support Localization of Recently Introduced Bugs''. 24th ACM Symposium on Applied Computing, ACM, pp. 438–442, 2009.</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 [[visual data mining]].<ref>(Keim, 2002; Soukup, 2002; Burch, 2005).</ref> For example, software visualization is used to monitoring activities such as for code quality or team activity.<ref>J. Bohnet, J. Döllner: ''Monitoring Code Quality and Development Activity by Software Maps''. Proceedings of the IEEE ACM ICSE Workshop on Managing Technical Debt, pp. 9-16, 2011.</ref> Visualization is inherently not a method for [[software quality assurance]]{{fact|date=September 2017}}.
==Types==
| |||