{'fraction_non_alphanumeric': 0.021929824561403508, 'fraction_numerical': 0.003654970760233918, 'mean_word_length': 5.8793969849246235, '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}}
Towards Multi Dimensional Methods1

ABSTRACT Recently, new paradigms have emerged to improved standard object-oriented methods. However, most of these lack guidelines for developers on how to design complex real-life systems using these techniques. In this position paper, we investigate proposed methods and reason why they still fail to meet key requirements of the standard design methodology. We also present a few key requirements for such methodology and show potential pitfalls along the way. Keywords Software Architecture, Product Line, Product Family, Subject-oriented Programming, Aspect-oriented Programming, Multidimensional Separation of Concerns 1 INTRODUCTION Recently new multidimensional paradigms of software development have been proposed by multiple researches.[1,2,3] They are all based on different implementation techniques that allow separating different concerns into more manageable parts than the original system if built using traditional object-oriented methods. Naturally, this technology is needed to being able to derive the actual instances of the system under considerations. However, this implementation focus does not offer enough tools for real-world software developers to cope with the new challenges that emerge with these tools. Especially, there is no generally accepted development methodology for multidimensional software.