{'fraction_non_alphanumeric': 0.02181818181818182, 'fraction_numerical': 0.0018181818181818182, 'mean_word_length': 5.054945054945055, '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}}
Using i * to identify candidate aspects

Aspect-orientation has been capturing researcher’s attention for the last few years. We have seen the birth of several aspect-oriented programming techniques and also the propagation of the aspect concept to the earlier stages of the software development process, such as requirements analysis and design. Our long-term goal is to extend aspect-orientation to the business modelling activity. This paper discusses our first results by using the i*1 technique to assist us with the concern elicitation process.