Identifying class name inconsistency in hierarchy | Zendy

Abdelghani Alidra | Zendy; Moussa Saker | Zendy; Nicolas Anquetil | Zendy; Sté́phane Ducasse | Zendy

AI Assistant Blog Pricing

Home ZAIA Blog

Open Access

Identifying class name inconsistency in hierarchy

Author(s) -

Abdelghani Alidra,

Moussa Saker,

Nicolas Anquetil,

Sté́phane Ducasse

Publication year - 2017

Publication title -

proceedings of the 12th edition of the international workshop on smalltalk technologies

Language(s) - English

Resource type - Conference proceedings

DOI - 10.1145/3139903.3139920

Subject(s) - heuristic , class (philosophy) , computer science , simple (philosophy) , hierarchy , task (project management) , class hierarchy , theoretical computer science , artificial intelligence , information retrieval , programming language , object oriented programming , engineering , philosophy , systems engineering , epistemology , economics , market economy

International audienceGiving 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

The content you want is available to Zendy users.

Already have an account? Click here to sign in.

Having issues? You can contact us here

Accelerating Research