{'fraction_non_alphanumeric': 0.022127659574468085, 'fraction_numerical': 0.0, 'mean_word_length': 5.461538461538462, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
History Coupling Space: A New Model to Represent Evolutionary Relations

During software evolution, files are usually changed together for accommodating modifications. Although co-change analysis has been widely adopted for difference studies, such as defect prediction, impact analysis, architectural relations identification etc., there has been little work characterizing co-changed files as a group and modeling the evolution of these files to represent software maintenance and evolution. In this paper, we present the concept of history coupling dependency, based on which, we propose a novel model, history coupling space (HCSpace), to link the co-changed files and represent how files are historically connected as a group. Our investigations on seven open source projects show that each HCSpace could be treated as a maintenance unit where the involved files are more likely to evolve together. The results also show that the HCSpaces have important impacts on a project's maintenance. In particular, we demonstrate that identified HCSpaces consumes a relatively large portion of maintenance effort spent on a project, and these HCSpaces are still actively evolving.