The Social Aspects of HIV series of books offers readers authoritative introductions and overviews, together with summaries of enduring and cutting edge concerns.
Such "cross-cutting concerns" include things like interrupt events, exception handling, and security protocols.
Like code, data also has cross-cutting concerns such as versioning, security, privacy, and reliability.
Our validation agents utilise "component aspects" that describe functional and non-functional cross-cutting concerns impacting software components.
Aspect-oriented (AO) modeling allows developers to model the cross-cutting behavior independently of the normal behavior, thus supporting model-based testing of cross-cutting concerns.
Aspects are useful for representing cross-cutting concerns in complex system architectures, as first introduced by the aspect-oriented programming paradigm in object-oriented design.
In this case, however, there are evidently many cross-cutting concerns, such as decision outcomes, for example, that do not fit neatly into one or the other concern.
However, aspects addressing cross-cutting concerns need to be incorporated in an object-oriented design without support from a higher-level design.
In this paper, we show how to use aspect-oriented (AO) modeling techniques in MBD as a systematic way to segregate domains of expertise and cross-cutting concerns within the model.
The main motivations of this work are (1) identifying cross-cutting concerns in existing agent-oriented code, and (2) making them explicitly available to software engineers involved in the evolution of agent-oriented code in order to facilitate its refactoring and, consequently, to improve its understandability, reusability and maintainability.
