Graph drawing by force-directed placement
Software—Practice & Experience
Computer graphics (2nd ed. in C): principles and practice
Computer graphics (2nd ed. in C): principles and practice
Journal of Software Maintenance: Research and Practice
Polymetric Views-A Lightweight Visual Approach to Reverse Engineering
IEEE Transactions on Software Engineering
Topigraphy: visualization for large-scale tag clouds
Proceedings of the 17th international conference on World Wide Web
Visually localizing design problems with disharmony maps
Proceedings of the 4th ACM symposium on Software visualization
A Tool for Visual Understanding of Source Code Dependencies
ICPC '08 Proceedings of the 2008 The 16th IEEE International Conference on Program Comprehension
Consistent Layout for Thematic Software Maps
WCRE '08 Proceedings of the 2008 15th Working Conference on Reverse Engineering
Mobile topigraphy: large-scale tag cloud visualization for mobiles
Proceedings of the 20th international conference companion on World wide web
Software systems as cities: a controlled experiment
Proceedings of the 33rd International Conference on Software Engineering
Data clone detection and visualization in spreadsheets
Proceedings of the 2013 International Conference on Software Engineering
Software Analytics for Mobile Applications--Insights & Lessons Learned
CSMR '13 Proceedings of the 2013 17th European Conference on Software Maintenance and Reengineering
Hi-index | 0.00 |
A large and complex software system could contain a large number of bugs. It is desirable for developers to understand how these bugs are distributed across the system, so they could have a better overview of software quality. In this paper, we describe BugMap, a tool we developed for visualizing large-scale bug location information. Taken source code and bug data as the input, BugMap can display bug localizations on a topographic map. By examining the topographic map, developers can understand how the components and files are affected by bugs. We apply this tool to visualize the distribution of Eclipse bugs across components/files. The results show that our tool is effective for understanding the overall quality status of a large-scale system and for identifying the problematic areas of the system.