{'fraction_non_alphanumeric': 0.0279027902790279, 'fraction_numerical': 0.0, 'mean_word_length': 5.465116279069767, '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': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Using Sequence Diagram to Support Aspect-Oriented Programming in MDA

Model-Driven Development (MDD) aims to shift the focus of software development activity from coding to modeling. However, managing relationships and specifying transformations between models at various levels of abstraction are complex tasks. System models tangled with concerns such as security make it difficult to develop complex systems and specify model transformations. Aspect-Oriented Programming (AOP) is an emerging software engineering paradigm that improves separation of cross-cutting concerns as aspect in a program. At present, the AOP paradigm has expanded to all the lifecycle of the software development, as a result, Aspect-Oriented Software Development (AOSD) is becoming a new technique, which has an important step of modeling the aspects. We present, In this paper, a Sequence Diagram describes the Aspectual Sequence Model based on the Unified Modeling Language (UML) to identify the cross-cutting concerns in the framework of Model-Driven Architecture (MDA), and using a mature language AspectJ to write aspect codes.