The document describes a tool for visualizing class name distributions and detecting inconsistencies in class naming conventions. The tool analyzes class names to identify naming patterns based on common prefixes and suffixes. It then visually displays classes grouped by consistent hierarchies and highlights possible inconsistencies. The tool was evaluated on both Java and Pharo projects, identifying valid renamings and providing insights into projects' internal designs. Experts and non-experts found the tool intuitive and effective at detecting misnamed classes.

1. ClassName Distribution Visualization:
Detecting inconsistencies in class names
Nour J. Agouf
Arolla, Inria, Univ. Lille, CNRS, Centrale Lille,
UMR 9189 - CRIStAL
nour-jihene.agouf@arolla.fr

2. Problematic:
2
How can we identify inconsistent class
names inside projects?

3. Understanding class names:
HorizontalFlowLayout
3
Noun
Adjective
(prefix) (suffix)
Noun

4. Classes of the same hierarchy follow the same
naming pattern- following the same descriptive
vocabulary
Class name consistency:
4

5. CanvasBuilder
Event
Canvas
ShapeEvent
ColorPalette
ColoredTreePalette
Object
Interaction
AbstractCanvas
ShapeInteraction
Layout
CircleLayout
FlowLayout
ExtentChangedEvent
PositionChangedEvent
ScaleChangedCanvas
ShapeAddedEvent
HighlightableEvent
HighlightEvent
UnHighlightEvent
CompositeInteraction LineInteraction
GridLayout
Package 1.
Package 2.
AbstractContainerBuilder
AbstractShapesBuilder
UMLAbstractBuilder
UMLClassBuilder UMLPackage
Scale
Example:
5
A sample of the Roassal Project

6. CanvasBuilder
Event
Canvas
ShapeEvent
ColorPalette
ColoredTreePalette
Object
Interaction
AbstractCanvas
ShapeInteraction
Layout
CircleLayout
FlowLayout
ExtentChangedEvent
PositionChangedEvent
ScaleChangedCanvas
ShapeAddedEvent
HighlightableEvent
HighlightEvent
UnHighlightEvent
CompositeInteraction LineInteraction
GridLayout
Package 1.
Package 2.
AbstractContainerBuilder
AbstractShapesBuilder
UMLAbstractBuilder
UMLClassBuilder UMLPackage
Scale
6
A sample of the Roassal Project
..24 (bright colors)
Possibly Inconsistent Naming:
A hierarchy using more than one suffix is identified by an
attracting color

7. CanvasBuilder
Event
Canvas
ShapeEvent
ColorPalette
ColoredTreePalette
Object
Interaction
AbstractCanvas
ShapeInteraction
Layout
CircleLayout
FlowLayout
ExtentChangedEvent
PositionChangedEvent
ScaleChangedCanvas
ShapeAddedEvent
HighlightableEvent
HighlightEvent
UnHighlightEvent
CompositeInteraction LineInteraction
GridLayout
Package 1.
Package 2.
AbstractContainerBuilder
AbstractShapesBuilder
UMLAbstractBuilder
UMLClassBuilder UMLPackage
Scale
7
..24 (bright colors)
Possibly Inconsistent Naming:
A hierarchy using more than one suffix is identified by an
attracting color
Consistent Hierarchy: Uses one suffix
identified by the color gray
A sample of the Roassal Project

8. CanvasBuilder
Event
Canvas
ShapeEvent
ColorPalette
ColoredTreePalette
Object
Interaction
AbstractCanvas
ShapeInteraction
Layout
CircleLayout
FlowLayout
ExtentChangedEvent
PositionChangedEvent
ScaleChangedCanvas
ShapeAddedEvent
HighlightableEvent
HighlightEvent
UnHighlightEvent
CompositeInteraction LineInteraction
GridLayout
Package 1.
Package 2.
AbstractContainerBuilder
AbstractShapesBuilder
UMLAbstractBuilder
UMLClassBuilder UMLPackage
Scale
..24 (bright colors)
Possibly Inconsistent Naming:
A hierarchy using more than one suffix is identified by an
attracting color
Consistent Hierarchy: Uses one suffix
identified by the color gray
Class or trait:
belongs to no hierarchy,
colored in white
8
A sample of the Roassal Project

9. CanvasBuilder
Event
Canvas
ShapeEvent
ColorPalette
ColoredTreePalette
Object
Interaction
AbstractCanvas
ShapeInteraction
Layout
CircleLayout
FlowLayout
ExtentChangedEvent
PositionChangedEvent
ScaleChangedCanvas
ShapeAddedEvent
HighlightableEvent
HighlightEvent
UnHighlightEvent
CompositeInteraction LineInteraction
GridLayout
Package 1.
Package 2.
AbstractContainerBuilder
AbstractShapesBuilder
UMLAbstractBuilder
UMLClassBuilder UMLPackage
Scale
Consistent hierarchy of classes
Possible Inconsistent hierarchies
Mono class (in no hierarchy)
{
A sample of the Roassal Project
ClassName Distribution of the sample from the
Roassal project
Example:
9
Suffix: Event Suffix: Canvas
Package 2.
Suffix: Interaction Suffix: Layout
Suffix: Scale
Suffix: Event
Package 1.
Suffix: Package Suffix: Palette
Suffix: Builder

10. • Supports both Pharo and Java projects.
• Supports suffix analysis, prefix analysis and both of suffix and
prefix mixed to chose the most accurate word in the hierarchy,
describing its concept.
Languages:

11. Java: Quantitative Evaluation
on 50 Java Projects
Evaluation
11
Pharo: Qualitative Evaluation on 6
Pharo Projects
Experts of the tool/
Non-experts of the project
Non-experts of the tool/
Experts of the project
232 Validated Renamings
✓ >1000 Stars
✓ >50 Forks
✓ >5000 K.B

12. 12
‣ The tool has shown to be easy to use and pretty intuitive,
‣ The tool provides a good summary of the distribution of classes inside
packages and their vocabulary.
‣ The tool is a good source of information about projects internal design,
‣ The tool has proven to be effective in detecting Pharo misnamed classes
‣ The tool showed inconsistencies also exist in Java projects
‣ A journal paper in the process of being published
Conclusion