2007 4th IEEE International Workshop on Visualizing Software for Understanding and Analysis 2007
DOI: 10.1109/vissof.2007.4290693
|View full text |Cite
|
Sign up to set email alerts
|

Requirements of Software Visualization Tools: A Literature Survey

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
26
0
1

Year Published

2008
2008
2018
2018

Publication Types

Select...
4
2
2
1

Relationship

0
9

Authors

Journals

citations
Cited by 46 publications
(28 citation statements)
references
References 56 publications
1
26
0
1
Order By: Relevance
“…ACM SOFTVIS, IEEE VISSOFT, MSR, ICPC, WCRE, ICSE, and CSMR, building useful and used tools is difficult. Reasons cited for this include the small return-on-investment and recognition of tools in academia (as opposed to papers), high maintenance cost, and high ratio of infrastructure-to-novelty (truly usable tools need fine-tuned implementations, help modules, and platform-independence, while research prototypes can focus on novelty) [5,3,32,33]. Combining analysis and visualization in one tool makes development only more complex, so good design patterns and guidelines are essential.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…ACM SOFTVIS, IEEE VISSOFT, MSR, ICPC, WCRE, ICSE, and CSMR, building useful and used tools is difficult. Reasons cited for this include the small return-on-investment and recognition of tools in academia (as opposed to papers), high maintenance cost, and high ratio of infrastructure-to-novelty (truly usable tools need fine-tuned implementations, help modules, and platform-independence, while research prototypes can focus on novelty) [5,3,32,33]. Combining analysis and visualization in one tool makes development only more complex, so good design patterns and guidelines are essential.…”
Section: Related Workmentioning
confidence: 99%
“…This does not imply that such additional visualizations are not useful for specific use-cases, but it does support the hypothesis that general structure-and-metric comprehension of large code bases at a fine grained level is well supported by the techniques currently present in out toolset. [89,58,49] or test a tool vs a requirements set [32,74]. Technical aspects e.g.…”
Section: Are There Any Useful Tool Building Patterns For Software Engmentioning
confidence: 99%
“…Kienle et al [11] identified seven quality attributes for visualization tools: a) rendering scalabilty b) information scalability c) interoperability d) customizability e) interactivity f) usability g) adaptability. We base our design decisions based on these attributes.…”
Section: Related Workmentioning
confidence: 99%
“…There exists a large body of work dedicated to the visualization of software; its structure [2], the different relationships and metrics [3], and at different levels of granularity [4] . In this section, we focus on software evolution visualizations.…”
Section: A Software Evolution Visualizationsmentioning
confidence: 99%