{'fraction_non_alphanumeric': 0.018962075848303395, 'fraction_numerical': 0.0, 'mean_word_length': 5.229813664596273, '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}}
Traceability Mechanism for Error Localization in Model Transformation

Model Driven Engineering (MDE) introduces the model paradigm as the basis of system design. It increases reusability in the development of complex systems. Nevertheless, with this new paradigm, traditional issues such as system debugging or system evolution management have to be performed in a different way. Existing techniques require to be adapted. We have shown the feasibility of traceability to solve these issues. However, system debugging can only be undertaken if the developer trusts the compiler. In MDE, the compiler is a transformation chain. It is hence important to test the transformations and possibly to debug them. In this paper, we demonstrate that our traceability mechanism coupled to our error localization algorithm eases the transformation test. Indeed, it highlights the succession of rule that leads to a faulty output element. This approach is illustrated in the context of embedded system development.