Proceedings of the 2003 ACM Symposium on Software Visualization - SoftVis '03 2003
DOI: 10.1145/774856.774857
|View full text |Cite
|
Sign up to set email alerts
|

Nice class diagrams admit good design?

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
49
0
1

Year Published

2006
2006
2012
2012

Publication Types

Select...
3
2
2

Relationship

1
6

Authors

Journals

citations
Cited by 23 publications
(50 citation statements)
references
References 0 publications
0
49
0
1
Order By: Relevance
“…Eichelberger also points out that the UML standard lacks a specification for the readability of the diagrams [12]. As a result, there are no common agreements on the criteria of readable and understandable layout of class diagrams.…”
Section: Uml Class Diagram Layout Criteriamentioning
confidence: 99%
See 1 more Smart Citation
“…Eichelberger also points out that the UML standard lacks a specification for the readability of the diagrams [12]. As a result, there are no common agreements on the criteria of readable and understandable layout of class diagrams.…”
Section: Uml Class Diagram Layout Criteriamentioning
confidence: 99%
“…UML tools have been developed to generate class diagrams automatically from source code. However, few tools can generate "nice" layouts for the diagrams [12].…”
Section: Introductionmentioning
confidence: 99%
“…Furthermore, the purpose of having context-information in the same view is to facilitate the further exploration and explanation of the elements in the model. We can now introduce secondary notations [9] of node-metrics as used in [6]. The width of a symbol is used to represent the number of classes abstracted and the height of the symbol is used to represent the number of levels abstracted along a relation.…”
Section: Onion Notations For Uml Class Modelsmentioning
confidence: 99%
“…The quality of a design in the layout algorithm is presented in [6]. Also, there exist algorithms that incorporate other semantic information such as design patterns and architectural importance [1,7].…”
Section: Layoutmentioning
confidence: 99%
“…So, positioning class symbols in their semantic context overweighted the connections the class had to other classes in the respective diagram [17]. However, there was no preferred direction of connections; though if a diagram depicted classes in a clear hierarchical context, then a top-down direction of connections was preferred [18].…”
mentioning
confidence: 99%