How were add hotspots into Annotation Sniffer software to decouple and extends software design.

1. Annotation Sniffer
Hotspots

2. Annotation Sniffer
What?
Annotation Sniffer is an Eclipse plugin to detect Annotation's Bad Smells.
How?
Download Annotation Sniffer Java ARchive (JAR) file; place into dropins Eclipse’s
directory and done!
Why?
Code metrics are important; Annotations are code; Code should be well written;

3. Hotspot: Metrics
Targets:
• Change XML file to Read directory files;
• Only files with @IsAMetric annotation;
• Should keep original output;

4. Load all metrics with annotation
 MetricsRepository injected as dependency into MetricsEvaluator
 Held old output interface

5. Hotspot: Thresholds
Targets:
• Remove Thresholds information from
BadSmellDetector class;
• Create a pluggable way to add new Thresholds data;
• Load thresholds on the fly (able to load other
Threshold’s data file)
• Keep old output interface.

6. Old way

7. New way
XML file

8. Threshold Object Diagram

9. Hotspot: Bad Smell
Targets:
• Change hard-coded to Read directory classes;
• Only class with @BadSmell annotation;
• Decouple a BadSmell from Threshold and Metric.

10. Old way

11. New way

12. Annotation Sniffer
Metrics as Hotspot: https://github.com/hlegius/annotation_sniffer/pull/1
Thresholds as Hotspot: https://github.com/hlegius/annotation_sniffer/pull/2
BadSmell as Hotspot: https://github.com/hlegius/annotation_sniffer/pull/5
https://github.com/hlegius/annotation_sniffer