13th International Workshop on Program Comprehension (IWPC'05)
DOI: 10.1109/wpc.2005.26
|View full text |Cite
|
Sign up to set email alerts
|

On Evaluating the Layout of UML Class Diagrams for Program Comprehension

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

1
3
0

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 18 publications
(4 citation statements)
references
References 20 publications
1
3
0
Order By: Relevance
“…Since trees are planar, it is possible to create layouts without crossings, justifying the first constraint (C1). Overlapping labels detract from readability and are often a metric for the usability of the labeled network layouts [32,51]. This supports the second constraint (C2).…”
Section: Introductionsupporting
confidence: 57%
See 1 more Smart Citation
“…Since trees are planar, it is possible to create layouts without crossings, justifying the first constraint (C1). Overlapping labels detract from readability and are often a metric for the usability of the labeled network layouts [32,51]. This supports the second constraint (C2).…”
Section: Introductionsupporting
confidence: 57%
“…This property is also needed in the final step of creating map-like visualization: semantic zooming depends on linearly increasing edge lengths. Uniform edge lengths (a special case where all desired edge lengths are the same) are preferable in cases where all edges represent the same notion of connectivity [46,51]. These reasons validate the first optimization goal (O1).…”
Section: Introductionmentioning
confidence: 81%
“…software engineering data has been done in a myriad of ways including with UML diagrams [SW05], treemaps [RVET14], tabular visualizations [ESS92], icicle plots [CCeT * 12], and multiple coordinated views [CCeT * 12, RVET14]. Adjacency matrices, though less common, have been used to compare the hierarchies of two different systems [BD13].…”
Section: Visualizingmentioning
confidence: 99%
“…In a study about visualizations for software exploration, Storey et al [28] name the reduction of user effort in adjusting interfaces as an important design element. Guidelines for UML class diagrams [37], [38] recommend to avoid edge crossings or overlapping nodes, to support users in recognizing the presented objects.…”
Section: Where Does This Connect? Clarifying Edgesmentioning
confidence: 99%