Content deleted Content added
m Reverted 1 edit by Rsesha2001 (talk) to last revision by 86.252.73.143 (TW) |
→Cite journal, book, harvnb | Alter: isbn. Add: isbn, series, volume, chapter-url. Removed or converted URL. Some additions/deletions were actually parameter name changes. | You can use this tool yourself. Report bugs here. | via #UCB_Gadget |
||
Line 1:
{{confused|Visualization (graphics)}}
'''Software visualization'''<ref>{{cite book |first=Johannes |last=Bohnet
== Software system information ==
Line 11:
== Objectives ==
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
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
==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
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">{{
==See also==
Line 42:
==Further reading==
*{{cite book |last=Roels
*{{cite book |last=Burch
*{{cite
*{{cite
*{{cite book |last=Eades
*{{cite book |last=Gîrba
*{{cite
*{{cite book |last=Knight
*{{cite book |last=Kuhn
*{{cite
*{{cite book |last=Lopez
*{{cite
*{{cite book |first=Tom |last=Soukup |first2=Ian |last2=Davidson |title=Visual Data Mining: Techniques and Tools for Data Visualization and Mining |url=https://books.google.com/books?id=9HsVknVqbo4C |date=2002 |publisher=Wiley |isbn=978-0-471-27138-3 |ref=harv}}
*{{cite journal |last=Staples
*{{cite book |first=John |last=Stasko |first2=Marc H. |last2=Brown |first3=John B. |last3=Domingue |first4=Blaine A. |last4=Price |title=Software Visualization: Programming as a Multimedia Experience |url=https://books.google.com/books?id=13PaPtQqtHUC&pg=PP1 |year=1998 |publisher=MIT Press |isbn=978-0-262-19395-5 |ref=harv}}
*{{cite book |first=F. |last=Van Rysselberghe
*{{cite book |last=Wettel
*{{cite
==External links==
|