Comprehensive Aspectual UML Approach to Support AspectJ

Table 11

Aspectual Class Diagram semantic rules.

Aspectual Class Diagram rules
Semantic rule	Description
No Aspect name given	This semantic rule means that all Aspects should have a name.
“precedence” is an Aspect-Aspect relation	This semantic rule means that “precedence” is an Aspect-Aspect relationship.; This means that the user (system analyst (SA)) should not attempt to use the “precedence” relationship with a Class at any end.; The “precedence” relationship takes place only between Aspects, when both have to eject a piece of code at the same join point. So the “precedence” relation sets which of the two Aspects executes the code first.
“Aspect crosscutting” is an Aspect-Aspect relation	This semantic rule means that “Aspect crosscutting” is an Aspect-Aspect relationship.; This means that the SA should not attempt to use the “Aspect crosscutting” relationship with a Class at any end.; The “Aspect crosscutting” relationship takes place when two Aspects are cut across each other.
“crosscutting” is an Aspect-Class relation	This semantic rule means that “crosscutting” is an Aspect-Class relationship.; This means that the SA should not attempt to use it with no Class at any end.; The “crosscutting” relationship takes place between an Aspect and a Class to show that there is crosscutting.
This is an OO notation	This semantic rule means that this is an “OO notation.”; This means that the SA should not attempt to use OO relations such as dependency and inheritance as a relation with an Aspect at any end.; The OO notation cannot be connected to AO notations.