Identifying class name inconsistency in ...
Document type :
Communication dans un congrès avec actes
DOI :
Title :
Identifying class name inconsistency in hierarchy: a first simple heuristic
Author(s) :
Alidra, Abdelghani [Auteur]
Université Badji Mokhtar [Annaba] [UBMA]
Saker, Moussa [Auteur]
Université Badji Mokhtar [Annaba] [UBMA]
Anquetil, Nicolas [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Ducasse, Stephane [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Université Badji Mokhtar [Annaba] [UBMA]
Saker, Moussa [Auteur]
Université Badji Mokhtar [Annaba] [UBMA]
Anquetil, Nicolas [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Ducasse, Stephane [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Conference title :
IWST 2017 - 12th International Workshop on Smalltalk Technologies
City :
Maribor
Country :
Slovénie
Start date of the conference :
2017-09-04
Journal title :
IWST '17 Proceedings of the 12th edition of the International Workshop on Smalltalk Technologies
Publisher :
ACM
HAL domain(s) :
Informatique [cs]/Langage de programmation [cs.PL]
Informatique [cs]/Génie logiciel [cs.SE]
Informatique [cs]/Génie logiciel [cs.SE]
English abstract : [en]
Giving good class names is an important task. Good programmers often report that they take several attempts to find an adequate one. Often programmers do not name consistently classes within a package, project or hierarchy. ...
Show more >Giving good class names is an important task. Good programmers often report that they take several attempts to find an adequate one. Often programmers do not name consistently classes within a package, project or hierarchy. This is a problem because it hampers understanding the systems. In this article we present a simple heuristic (a distribution) to characterise class naming. We combine such a heuristic with structural information to identify inconsistent class names. In addition, we use this simple heuristic to give packages a shape. We applied such heuristic to 285 packages in Pharo to identify misnamed classes. Some of these misnamed classes are reported and discussed here.Show less >
Show more >Giving good class names is an important task. Good programmers often report that they take several attempts to find an adequate one. Often programmers do not name consistently classes within a package, project or hierarchy. This is a problem because it hampers understanding the systems. In this article we present a simple heuristic (a distribution) to characterise class naming. We combine such a heuristic with structural information to identify inconsistent class names. In addition, we use this simple heuristic to give packages a shape. We applied such heuristic to 285 packages in Pharo to identify misnamed classes. Some of these misnamed classes are reported and discussed here.Show less >
Language :
Anglais
Peer reviewed article :
Oui
Audience :
Internationale
Popular science :
Non
Collections :
Source :
Files
- https://hal.inria.fr/hal-01663603/document
- Open access
- Access the document
- https://hal.inria.fr/hal-01663603/document
- Open access
- Access the document
- https://hal.inria.fr/hal-01663603/document
- Open access
- Access the document
- https://hal.inria.fr/hal-01663603/document
- Open access
- Access the document
- document
- Open access
- Access the document
- abdou.pdf
- Open access
- Access the document