by Georgios Kanakis, Djamel Eddine Khelladi, Stefan Fischer, Michael A. Tröls, Alexander Egyed
Abstract:
Model and code co-changing is about the coordinated modifi- cation of models and code during evolution. Intermittent inconsistencies are a common occurrence during co-changing. A partial co-change is the period in which the developer changed, say, the model but has not yet propagated the change to the code. Inconsistency feedback can be provided to developers for helping them to complete partial co-changes. However, there is no evidence whether such inconsistency feedback is useful to devel- opers. To investigate this problem, we conducted a controlled experiment with 36 subjects who were required to complete ten partially completed change tasks between models and code of two non-trivial systems. The tasks were of different levels of complexity depending on how many model diagrams they affected. All subjects had to work on all change tasks but sometimes with and sometimes without inconsistency feedback. We then measured differences between task effort and correctness. We found that when subjects were given inconsistency feedback during tasks, they were 268% more likely to complete the co-change correctly compared to when they were not given inconsistency feedback. We also found that when subjects were not given inconsistency feedback, they nearly always failed in completing co-change tasks with high complexity where the partially completed changes were spread across different diagrams in the model. These findings suggest that inconsistency feedback (i.e. detection and repair) should form an integral part of co-changing, regardless of whether the code or the model changes first. Furthermore, these findings suggest that merely having access to changes (as with the given partially completed changes) is insufficient for effective co-changing.
Reference:
An Empirical Study on the Impact of Inconsistency Feedback during Model and Code Co-changing (Georgios Kanakis, Djamel Eddine Khelladi, Stefan Fischer, Michael A. Tröls, Alexander Egyed), In J. Object Technol., volume 18, 2019.
Bibtex Entry:
@Article{Kanakis2019,
author = {Georgios Kanakis and Djamel Eddine Khelladi and Stefan Fischer and Michael A. Tröls and Alexander Egyed},
journal = {J. Object Technol.},
title = {An Empirical Study on the Impact of Inconsistency Feedback during Model and Code Co-changing},
year = {2019},
number = {2},
pages = {10:1--21},
volume = {18},
abstract = {Model and code co-changing is about the coordinated modifi- cation of models and code during evolution. Intermittent inconsistencies are a common occurrence during co-changing. A partial co-change is the period in which the developer changed, say, the model but has not yet propagated the change to the code. Inconsistency feedback can be provided to developers for helping them to complete partial co-changes. However, there is no evidence whether such inconsistency feedback is useful to devel- opers. To investigate this problem, we conducted a controlled experiment with 36 subjects who were required to complete ten partially completed change tasks between models and code of two non-trivial systems. The tasks were of different levels of complexity depending on how many model diagrams they affected. All subjects had to work on all change tasks but sometimes with and sometimes without inconsistency feedback. We then measured differences between task effort and correctness. We found that when subjects were given inconsistency feedback during tasks, they were 268% more likely to complete the co-change correctly compared to when they were not given inconsistency feedback. We also found that when subjects were not given inconsistency feedback, they nearly always failed in completing co-change tasks with high complexity where the partially completed changes were spread across different diagrams in the model. These findings suggest that inconsistency feedback (i.e. detection and repair) should form an integral part of co-changing, regardless of whether the code or the model changes first. Furthermore, these findings suggest that merely having access to changes (as with the given partially completed changes) is insufficient for effective co-changing.},
bibsource = {dblp computer science bibliography, https://dblp.org},
biburl = {https://dblp.org/rec/journals/jot/KanakisKFTE19.bib},
doi = {10.5381/JOT.2019.18.2.A10},
timestamp = {Wed, 17 Feb 2021 08:57:50 +0100},
url = {https://doi.org/10.5381/jot.2019.18.2.a10},
}