{'fraction_non_alphanumeric': 0.02185792349726776, 'fraction_numerical': 0.0, 'mean_word_length': 5.1066666666666665, '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': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
An Architectural Style to Integrate Components and Aspects

In the last few years Component Based Development (CBD) and Aspect Oriented Programming (AOP) are gaining more and more relevance. Whilst CBD has been shown as a good mean to reuse designs and to build complex systems by the plug-and-play mechanisms, AOP makes code more reusable and complex systems more comprehensible. However, little efforts have been made to integrate both paradigms and consequently, developers are condemned to don’t get all the advantages offered by the two paradigms simultaneously. In this paper a proposal to integrate AOP and CBD is presented. The work introduce the concept of Aspect Component and it is split in two different parts: first, an architectural style to support both, functional and aspect components is proposed and second, an approach to document, search and find aspect components in repositories is presented.