Conceptual graph matching: a flexible algorithm and experiments
Journal of Experimental & Theoretical Artificial Intelligence - Special issue: conceptual graphs workshop
The Class Blueprint: Visually Supporting the Understanding of Classes
IEEE Transactions on Software Engineering
Visualizing live software systems in 3D
SoftVis '06 Proceedings of the 2006 ACM symposium on Software visualization
Mondrian: an agile information visualization framework
SoftVis '06 Proceedings of the 2006 ACM symposium on Software visualization
The SEXTANT Software Exploration Tool
IEEE Transactions on Software Engineering
Tool users requirements classification: how software visualization tools measure up
AFRIGRAPH '07 Proceedings of the 5th international conference on Computer graphics, virtual reality, visualisation and interaction in Africa
Co-evolving code and design with intensional views
Computer Languages, Systems and Structures
genDMG: A Generic Graph Representation Layout to Visualize Existing Software Artifacts
IVIC '09 Proceedings of the 1st International Visual Informatics Conference on Visual Informatics: Bridging Research and Practice
Information and Software Technology
A code reuse interface for non-programmer middle school students
Proceedings of the 15th international conference on Intelligent user interfaces
Experiments with pro-active declarative meta-programming
IWST '09 Proceedings of the International Workshop on Smalltalk Technologies
Science of Computer Programming
Refactorings of design defects using relational concept analysis
ICFCA'08 Proceedings of the 6th international conference on Formal concept analysis
Unanticipated integration of development tools using the classification model
Computer Languages, Systems and Structures
Hi-index | 0.00 |
Software visualization tools face many challenges interms of their implementation, including scalability, usability,adaptability, and durability. Such tools, like many otherresearch tools, tend to have a short life cycle and are vulnerbleto software evolution processes because of the complexproblem domain and the constantly changing requirementswhich are dictated by research goals. In this paper we discussthe implementation of the software visualization toolCodeCrawler according to five criteria, namely the overallarchitecture, the internal architecture, the visualizationengine, the metamodel and the interactive facilities. Thisdiscussion generates implementation recommendations anddesign guidelines that hold for our tool and the class of toolsits stands for. We then also extract common design guidelinesand recommendations that apply for other softwarevisualization and general reverse engineering tools as well,and hope that these insights can be used fruitfully by otherresearchers in this field.