{'fraction_non_alphanumeric': 0.01434878587196468, 'fraction_numerical': 0.0, 'mean_word_length': 5.046666666666667, '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}}
" Why Determining the Intent of Code Changes Helps Sustaining Attached Model Information During Code Evolution "

Various approaches have been proposed to face the difficulties related to constructing and maintaining modern software systems. Often, they incorporate models in some part of the development or evolution process. Even the use of models at runtime seems to receive more and more attention as a way to enable the quick, systematic and automated application of change operations on software as it executes. Assuming that existing systems have been largely developed in code and that novel target architectures depend on – or even embed – models to some extent, the possible roles of models and code as well as their interaction and interchangeability need to be thoroughly examined. In this position paper, we attempt to initiate a discussion on why models and code should become closer friends.