Software repositories include information which can be made available for bug fixing or maintenance using#R##N##R##N#repository mining. The identification of coupled changes have been proposed several times. Yet, existing#R##N##R##N#studies focus on the found couplings and ignore feedback from developers. We investigate three development#R##N##R##N#projects and their repositories to find files that frequently change together to support the software developers.#R##N##R##N#We complement the coupled files information with details from the issue tracking system and the project#R##N##R##N#documentation. We contrast our findings with feedback from the developers about how interesting our findings#R##N##R##N#are for them. We found that the small size of the repositories made an insightful analysis difficult. The response#R##N##R##N#to coupled changes both from experienced and inexperienced developers was mostly neutral. They accepted#R##N##R##N#most of the additional attributes we presented. Furthermore, developers also suggested other additional issues#R##N##R##N#to be relevant, e.g. the context of the coupled changes and the way they are presented, which we did not#R##N##R##N#cover in this study. Therefore, coupled change analysis research will need to take the presentation and context#R##N##R##N#information into account.
['Jasmin Ramadani', 'Stefan Wagner']
Are Suggestions of Coupled File Changes Interesting