{'fraction_non_alphanumeric': 0.022511848341232227, 'fraction_numerical': 0.0, 'mean_word_length': 5.1678832116788325, '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': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Taming Model Round-Trip Engineering

Round-trip engineering is a challenging task that will become an important enabler for many Model-Driven Software Development approaches. Model round-trip engineering involves synchronizing models by keeping them consistent, thus enabling the software engineer to freely move between different representations. The vision of model round-trip engineering (MRTE) is only realized to a limited degree in Integrated Development Environments (IDE) nowadays, and it proves to be a very difficult problem to solve in general. In this paper, our goal is to clarify some of the issues in automating MRTE and point out some of the high-level qualities that are desirable for MRTE approaches to possess. Clarifying this domain is an important first step towards being able to automate round-trip engineering of models.