{'fraction_non_alphanumeric': 0.017127799736495388, 'fraction_numerical': 0.0, 'mean_word_length': 5.38655462184874, '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}}
Implementation of Decision Modules

Separation of concerns can have different forms. The well accepted concern is an object behavior usually specified as a life cycle module. In this paper, we define another type of concern, a decision module, and identify it in requirements and models. Separation of decision modules in programs may improve traceability of requirements and simplify code analysis. We present the results of our experiments with implementation of decision modules. We implement the modules using object composition, reflection, the publisher-subscriber design pattern and aspects. We present the possibilities of different implementation forms and illustrate our observations of pros and cons with an example of a document submission system.