[aosd-discuss] design metrics for Aspect Oriented System

[Günter Kniesel]

Vijayalakshmi Rajasekaran wrote:
>  I am doing my project in Aspect Oriented Design Level metrics.I have 
> chosen "Coupling On Advice Execution" as one of the metic. I want to 
> discuss on the impact of number of aspects on the design ie)what will 
> happen if we increase the number of aspects whether it affect the 
> quality or not?

*Which quality?* Readabilty? Understandabiliy? Safety? ...
Maintenability? Reusability? Efficiency? Lack of errors?

*Quality of what?* The apects? The base code? The whole?

Note that some quality X of the base code might be improved by aspects
(e.g. readability might increase because the base code gets shorter)
and the aspects themselves can have a "good" X value (e.g. aspects
can occasionally be quite readable) but the whole program might not
be necessarily "better" with respect to X (e.g. more readable).

So my advice would be to define first the "quality attributes"
(Which quality do you mean?) and the "quality criteria" (How do
you measure quality and which values are better) before asking your
question again.

By the way, for "coupling on advice execution" I would expect that
you count the number of matches of the advice not just the number
of aspects. The number of aspects says nothing about the coupling.
One can write 100 aspects that do not match anything in a given base
program and a single one that affects each method call!

Günter