{'fraction_non_alphanumeric': 0.017804154302670624, 'fraction_numerical': 0.0, 'mean_word_length': 5.553398058252427, '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}}
Generalization from domain experience: the superior paradigm for software architecture research?

A very wide variety of software architecture research activities have taken place over the last decade. We argue that much, if not most, of the most successful results have come from projects in which researchers first have been steeped in the details of an application domain, and then have set forth architecture-level contributions based on insights from that experience. We consider several examples of this and draw some conclusions regarding the setting of research priorities, evaluation of results, identification of worthy problems, and the definition of scalability.