Icon graphs
Susanne Jucknath-John, Dennis Graf · 2006
Most models are expressed and visualized with UML nowadays and most UML diagrams are based on graphs. Such graphs can get quite large if a project contains more than 600 class files, which is not uncommon. But changes are hard to recognize in a graph with 600 nodes. Therefore, the user has to find a way to build his own mental map based on the original graph. This mental map should give an overview of the original graph size, structure and it should point to changed areas.We present in this paper an approach, which gives the user a smaller graph as a mental map. This smaller graph uses packages as foundations for nodes and displays the package's content as the node icon. This had be done beforehand to visualize the evolution of developer dependencies over time, where the node icon presented the package's developer information as a pie chart. A suitable icon to present a package's class diagram can be a smaller version of the class diagram itself, if the layout respects its predecessors to allow the user an overview of its evolution.