UML toolkit
Detecting defects in object-oriented designs: using reading techniques to increase software quality
Proceedings of the 14th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
SPSS Base 9.0 Syntax Reference Guide
SPSS Base 9.0 Syntax Reference Guide
Empirical Software Engineering
Digital Sound Recorder: A Case Study On Designing Embedded Systems Using the UML Notation
Digital Sound Recorder: A Case Study On Designing Embedded Systems Using the UML Notation
OPM vs. UML—Experimenting with Comprehension and Construction of Web Application Models
Empirical Software Engineering
Improving CRC-card role-play with role-play diagrams
OOPSLA '05 Companion to the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Journal of Systems and Software - Special issue: Quality software
An Empirical Investigation on Dynamic Modeling in Requirements Engineering
MoDELS '08 Proceedings of the 11th international conference on Model Driven Engineering Languages and Systems
A Comparison of Metric-Based and Empirical Approaches for Cognitive Analysis of Modeling Languages
Fundamenta Informaticae - Cognitive Informatics, Cognitive Computing, and Their Denotational Mathematical Foundations (I)
Quality and comprehension of UML interaction diagrams-an experimental comparison
Information and Software Technology
An experimental comparison of ER and UML class diagrams for data modelling
Empirical Software Engineering
ER'05 Proceedings of the 24th international conference on Conceptual Modeling
A Comparison of Metric-Based and Empirical Approaches for Cognitive Analysis of Modeling Languages
Fundamenta Informaticae - Cognitive Informatics, Cognitive Computing, and Their Denotational Mathematical Foundations (I)
Hi-index | 0.00 |
The goal of this empirical study is to compare the semantic comprehension of three different notations for representing the dynamic behaviour in unified modelling language (UML): (a) sequence diagrams, (b) collaboration diagrams, and (c) state diagrams. Eighteen students of Informatics analysed the three types of diagrams within three different application domains. We performed a 3 × 3 factorial experimental design with repeated measures. The metrics collected were total time and total score. The main conclusion of this study is that the comprehension of the dynamic modelling in object-oriented designs depends on the diagram type and on the complexity of the document. The software project design written in the UML notation is more comprehensible, when the dynamic behaviour is modelled in a sequence diagram. While if it is implemented using a collaboration diagram, the design turns out to be less comprehensible as the application domain, and consequently, the document is more complex.