{'fraction_non_alphanumeric': 0.011922503725782414, 'fraction_numerical': 0.0, 'mean_word_length': 4.894736842105263, '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}}
Partial comprehension of complex programs (enough to perform maintenance)

Many legacy programs are so large and so complex that they cannot be comprehended in their entirety no matter what forms of representation are used. Yet these programs must be maintained. The contention of this paper is that it is not necessary to comprehend a program in order to maintain it. It is only necessary to comprehend those sectors affected by the maintenance request. Only seven questions are required to pinpoint and comprehend program sectors well enough to be able to alter them without undesired side effects. These questions and their answers are proposed in the following paper.