{'fraction_non_alphanumeric': 0.0113314447592068, 'fraction_numerical': 0.0, 'mean_word_length': 5.486238532110092, '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}}
Supporting the Comprehension of Object-oriented Software Systems by Extended M-M Graph

Tracing user functional requirements to the source code components implementing them is a difficult, time consuming and expensive software comprehension task, specially when adequate documentation is absent. In objectoriented systems functional requirements are implemented by a chain of method activations started by an input event and terminating when an output event is generated. Such a chain may be modelled by the Method-Message Graph that has been used to effectively support the identification of sequences of method activations responsible of a given system behaviour and to recover use cases from object ori-