17. 4. extract thresholds from metric values where
aggregated weight is 70%, 80% and 90%
0% 10% 30% 70% 80% 90% 100%
SCAM 2016 17
1. order by metric value
2. weight
3. weight aggregation
27. 1. order by metric value
only controllers
SCAM 2016 27
28. 1. order by metric value
2. aggregate the weight
0% 10% 30% 70% 80% 90% 100%
SCAM 2016 28
29. 1. order by metric value
2. aggregate the weight
3. extract thresholds from metric values where
aggregated weight is 70%, 80% and 90%
0% 10% 30% 70% 80% 90% 100%
SCAM 2016 29
33. RQ1. What differences in metric values
distributions does SATT find for common
architectural styles such as MVC?
SCAM 2016 33
34. RQ2. Can the differences in distributions
thus found be explained from the
architectural constraints imposed on
classes fulfilling dedicated architectural
roles?
SCAM 2016 34
35. RQ3. What impact do these differences
have on the use of thresholds for quality
assessments?
SCAM 2016 35
37. RQ1. The approach indeed finds architectural roles
that present significantly higher (or lower) values
for certain metrics when compared to other classes.
SCAM 2016 37
39. SCAM 2016 39
“Controllers are coupled to the framework while
Services are coupled to domain objects.”
“Entities contain getters and setters”
40. RQ2. Experts considered most of the differences in
metric values for architectural roles to be coherent.
Their key explanation is that architectural roles
have specific responsibilities.
SCAM 2016 40
45. RQ3. The state-of-art approach tends to return
doubtful results for architectural roles that have
metric values distribution significantly different
from other classes. Our approach improves it by
using the architectural role’s metric values
distribution to define thresholds.
SCAM 2016 45