{'fraction_non_alphanumeric': 0.008602150537634409, 'fraction_numerical': 0.0, 'mean_word_length': 5.0519480519480515, '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}}
Direct Mapping and User Interface

Direct Mapping is the rule that there should be a direct correspondence between object types in the problem domain and in the software solution. But once direct mapping has been achieved, how should user interface object types be designed to work with the behavioral object types? This paper answers that question and presents some design patterns which were employed by Fowler Software Design in a recent Eiffel software project.