Are Forward Designed or Reverse-Engineered UML diagrams more helpful for code maintenance?: A family of experiments

• Published in: Information and software technology Vol. 57; no. 1; pp. 644 - 663
• Main Authors: Fernández-Sáez, Ana M., Genero, Marcela, Chaudron, Michel R.V., Caivano, Danilo, Ramos, Isabel
• Format: Journal Article
• Language: English
• Published: Amsterdam Elsevier B.V 01-01-2015; Elsevier Science Ltd
• Subjects: Computer and Information Science; Computer programs; Computer science; Computer simulation; Controlled experiment; Data- och informationsvetenskap; Effectiveness studies; Family of experiments; Maintainability; Maintenance; Programming languages; Replication; Reverse Engineering; Software; Software engineering; Software maintenance; Statistical tests; Students; Systems design; UML diagrams; Unified Modeling Language; Software maintenance; Maintainability; Reverse Engineering; Family of experiments; UML diagrams; Controlled experiment
• ISSN: 0950-5849; 1873-6025
• DOI: 10.1016/j.infsof.2014.05.014

•Forward Designed UML class diagrams are useful for maintaining the code of well-known domains.•Reverse Engineered UML diagrams were considered difficult to understand and read.•It is recommended that UML class diagrams should be synchronized with source code.
Although various success stories of model-based approaches are reported in literature, there is still a significant resistance to model-based development in many software organizations because the UML is perceived to be expensive and not necessarily cost-effective. It is also important to gather empirical evidence in which context and under which conditions the UML makes or does not make a practical difference.
Our objective is to provide empirical evidence as to which UML diagrams are more helpful during software maintenance: Forward Designed (FD) UML diagrams or Reverse Engineered (RE) UML diagrams.
We carried out a family of experiments which consisted of one experiment and two replications with a total of 169 Computer Science undergraduate students.
The individual data analysis and the meta-analysis conducted on the whole family, show a tendency in favor of FD diagrams and are significantly different as regards the effectiveness and efficiency of the subjects who participated and played the role of maintainers. The analysis of the qualitative data, collected using a post-experiment survey, reveals that the subjects did not consider RE diagrams helpful.
Our findings show that there are some objective results (descriptive statistics or statistical tests) related to the maintenance effectiveness and efficiency in favor of the use of FD UML diagrams during software maintenance. Subjective opinions also lead us to recommend the use of UML diagrams (especially class diagrams) created during the design phase for software maintenance because they improve the understanding of the system in comparison with RE diagrams. Nevertheless, we can only assume that these results are valid in the context of Computer Science undergraduate students when working with small systems related to well-known domains, and other contexts should be explored in order to reaffirm the results in an industrial context by carrying out replications with professionals.