2011
DOI: 10.1007/978-3-642-24485-8_13
|View full text |Cite
|
Sign up to set email alerts
|

Identifying the Weaknesses of UML Class Diagrams during Data Model Comprehension

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
10
0
2

Year Published

2012
2012
2019
2019

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 13 publications
(12 citation statements)
references
References 16 publications
0
10
0
2
Order By: Relevance
“…Despite the dominance of UML there is a certain degree of difficulty in understanding a system represented by means of UML diagrams (Bavota et al, 2011;Otero & Dolado, 2004;Siau & Cao, 2001;Siau, Erickson, & Lee, 2005). Previous research has indicated several reasons: among which (1) the level of structural complexity of UML exceeding the limits of human working memory (cognitive load) in terms of the ability for effective information processing (Cruz-Lemus, Genero, & Piattini, 2008;Cruz-Lemus, Maes, Genero, Poels, & Piattini, 2010;Erickson & Siau, 2007;Wilmont, Hengeveld, Barendsen, & Hoppenbrouwers, 2013); and (2) lack of comprehension methodologies (Erickson & Siau, 2007) and, in particular, its impreciseness about the combination of interactive, structural and behavioral aspects together in a single model (Gustas, 2010).…”
Section: Introductionmentioning
confidence: 99%
“…Despite the dominance of UML there is a certain degree of difficulty in understanding a system represented by means of UML diagrams (Bavota et al, 2011;Otero & Dolado, 2004;Siau & Cao, 2001;Siau, Erickson, & Lee, 2005). Previous research has indicated several reasons: among which (1) the level of structural complexity of UML exceeding the limits of human working memory (cognitive load) in terms of the ability for effective information processing (Cruz-Lemus, Genero, & Piattini, 2008;Cruz-Lemus, Maes, Genero, Poels, & Piattini, 2010;Erickson & Siau, 2007;Wilmont, Hengeveld, Barendsen, & Hoppenbrouwers, 2013); and (2) lack of comprehension methodologies (Erickson & Siau, 2007) and, in particular, its impreciseness about the combination of interactive, structural and behavioral aspects together in a single model (Gustas, 2010).…”
Section: Introductionmentioning
confidence: 99%
“…According to the first two works [15] [16], the authors suggest that the CD notation is generally more comprehensible than the EER notation. However, in the third work [17], the authors conclude that the understanding of EER model is significantly higher than CD if "composite attribute", "multi-value attribute" and "weak entity" are required in a modeling. To summarize this discussion, we think that any comparison between the EER model and the CD can provide results to debate and arguing, and the choice for a particular notation rather than other is a matter of preference or project contingency.…”
Section: Fig 1 Constructors Of the Eer Modelmentioning
confidence: 95%
“…The considered systems are hosted on GitHub and built on the TravisCI [32] platform. We followed the methodology of Bavota et al [3] to select systems that developers can easily get familiar with and that are, at the same time, representative for real software systems. While our selected systems have less than 500K lines of code, they are very popular (more than 100 stars on GitHub) and frequently built (more than 100 builds on the master branch).…”
Section: Contextmentioning
confidence: 99%