{'fraction_non_alphanumeric': 0.028374233128834355, 'fraction_numerical': 0.0, 'mean_word_length': 5.658163265306122, '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}}
Time, event and self-management aspects in model-driven development of information systems

Cross-cutting concerns, or aspects, are parts of the system that in standard design mechanisms are scattered across multiple program components, and tangled with other components. The ideas of separation of cross-cutting concerns, originated from aspect-oriented programming (AOP), have gained attention in aspect-oriented design (AOD) and model-driven development (MDD), endeavoring to aspect-oriented decomposition and composition at model level. This paper focuses on adequate representing of time, events and management concerns in information systems owning behavior inspired by system agents. Event-based aspect-oriented approach seems to be the most appropriate solution for this situation, although it lacks smooth methodology going from requirements to code and often is hidden in technological level. Time aspect, thoroughly analyzed in embedded and real-time systems, also lacks of proper attention in the area of information systems despite it is closely related to many information system projects. To fill the gap, the method of design independent modeling was extended with concepts and techniques for time, event and self-management aspects modeling in model-driven information system development