Weaving Multiple Aspects in Sequence Diagrams - Transactions on Aspect-Oriented Software Development - page 194

Fig. 16. Screenshot of the result

bSD, the join point formed by the messages a and b is detected in each behavior

generated by the cSD example . So, the expected behaviors allows any number

of messages c between a and b . Since the message d surrounds this potentially

infinite number of messages , the expected behaviors cannot be represented

with SDs (we cannot isolate anymore the message

c

in a loop).
When we consider the join points as general parts, safe part or enclosed part,
our future works are to identify the cases for which our static weaving is always
possible, even if the base scenario generates an infinite number of behaviors.
In the paper we have chosen to limit the approach to simple name matching.
However, in future work, our approach could be extended with more powerful
matching mechanisms such as roles or wildcards on object names.

c

8 Related Works

Clarke and Baniassad [7] use the Theme/UML approach to define aspects.
Theme/UML introduces a theme module that can be used to represent a concern
at the modeling level. Themes are declaratively complete units of modularization,
in which any of the diagrams available in the UML can be used to model one view
of the structure and behavior the concern requires to execute. In Theme/UML,
a class diagram and sequence diagrams are typically used to describe the struc-
ture and behaviors of the concern being modeled. The question addressed by
their work is more the specification of aspects than the weaving process into
non-aspectual models, but our definitions and detection of join point, and our