CodeCrawler - Lessons Learned in Building a Software Visualization Tool

  • Authors:
  • Michele Lanza

  • Affiliations:
  • -

  • Venue:
  • CSMR '03 Proceedings of the Seventh European Conference on Software Maintenance and Reengineering
  • Year:
  • 2003

Quantified Score

Hi-index 0.00

Visualization

Abstract

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.