2019 IEEE/ACM 41st International Conference on Software Engineering: Software Engineering Education and Training (ICSE-SEET) 2019
DOI: 10.1109/icse-seet.2019.00019
|View full text |Cite
|
Sign up to set email alerts
|

Mistakes in UML Diagrams: Analysis of Student Projects in a Software Engineering Course

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

3
11
0
1

Year Published

2020
2020
2023
2023

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 24 publications
(15 citation statements)
references
References 8 publications
3
11
0
1
Order By: Relevance
“…Chren et al [12] evaluated over 2700 UML diagrams and examined students' mistakes with use case diagrams, activity diagrams, class diagrams, state machine diagrams, sequence diagrams, communication diagrams, and entity-relationship diagrams. They produced their catalogue from papers and their own research and identified 146 mistakes.…”
Section: Analysis Of Existing Mistakes Classificationsmentioning
confidence: 99%
See 2 more Smart Citations
“…Chren et al [12] evaluated over 2700 UML diagrams and examined students' mistakes with use case diagrams, activity diagrams, class diagrams, state machine diagrams, sequence diagrams, communication diagrams, and entity-relationship diagrams. They produced their catalogue from papers and their own research and identified 146 mistakes.…”
Section: Analysis Of Existing Mistakes Classificationsmentioning
confidence: 99%
“…The overview of the classification scheme is in fig. 1 [12]. Reuter [8] classified mistakes in a category system that is commonly known from errors in programming languages and the Standard Classification for Software Anomalies [20]: Lexical, Syntactic, Semantic, Logic, Missing, and Unnecessary.…”
Section: Analysis Of Existing Mistakes Classificationsmentioning
confidence: 99%
See 1 more Smart Citation
“…Other common beginners' errors have been investigated in the literature. The studies were conducted with students and identified difficulties with choosing the right type of relationship, defining the direction of the extend relationship and proper naming of elements (Kruus et al, 2014a) (Chren et al, 2019a) (Holt and Perry, 2008). For example, they reported the absence of verbs in use case names and the use of proper names for actors rather than a common name representing a role.…”
Section: Difficulties For Beginnersmentioning
confidence: 99%
“…Finally, some authors examined the problem of UML design from the educational point of view. The studies (Chren et al, 2019b) and (Kruus et al, 2014b) had pointed out the common mistakes made by students in SysML/UML courses. In (Ramollari and Dranidis, 2007), Ramollari proposed an object-oriented modelling tool suitable for students.…”
Section: Assistance For Use Case Diagram Creationmentioning
confidence: 99%