Objective: The main objective of our study is to assess whether the use of UML (Unified Modeling Language) object diagrams improves comprehensi- bility of software design when this kind of diagrams is added to UML class diagrams. Method: We have conducted a family of four controlled experiments. We involved groups of bachelor and master students. Results: Results suggest that the use of object diagrams does not always introduce significant benefits in terms of design comprehensibility. We found that benefits strongly depend on the experience of participants and their familiarity with UML. More experienced participants achieved better design comprehensibility when provided with both class and object diagrams, while less experienced seemed to be damaged when using class and object diagrams together. Results also showed the absence of substantial variations in the time needed to comprehend UML models, with or without object diagrams. Implications: Our results suggest that it is important to be aware and take into account experience and UML familiarity before using object diagrams in software modeling.

Do UML Object Diagrams Affect Design Comprehensibility? Results from a Family of Four Controlled Experiments

SCANNIELLO, GIUSEPPE;
2017-01-01

Abstract

Objective: The main objective of our study is to assess whether the use of UML (Unified Modeling Language) object diagrams improves comprehensi- bility of software design when this kind of diagrams is added to UML class diagrams. Method: We have conducted a family of four controlled experiments. We involved groups of bachelor and master students. Results: Results suggest that the use of object diagrams does not always introduce significant benefits in terms of design comprehensibility. We found that benefits strongly depend on the experience of participants and their familiarity with UML. More experienced participants achieved better design comprehensibility when provided with both class and object diagrams, while less experienced seemed to be damaged when using class and object diagrams together. Results also showed the absence of substantial variations in the time needed to comprehend UML models, with or without object diagrams. Implications: Our results suggest that it is important to be aware and take into account experience and UML familiarity before using object diagrams in software modeling.
2017
File in questo prodotto:
File Dimensione Formato  
VLC.pdf

solo utenti autorizzati

Tipologia: Documento in Pre-print
Licenza: DRM non definito
Dimensione 431.95 kB
Formato Adobe PDF
431.95 kB Adobe PDF   Visualizza/Apri   Richiedi una copia

I documenti in IRIS sono protetti da copyright e tutti i diritti sono riservati, salvo diversa indicazione.

Utilizza questo identificativo per citare o creare un link a questo documento: https://hdl.handle.net/11563/123559
Citazioni
  • ???jsp.display-item.citation.pmc??? ND
  • Scopus 8
  • ???jsp.display-item.citation.isi??? 6
social impact