A Precise Method-Method Interaction-Based Cohesion Metric for Object-Oriented Classes

Abstract

The building of highly cohesive classes is an important objective in object-oriented design. Class cohesion refers to the relatedness of the class members, and it indicates one important aspect of the class design quality. A meaningful class cohesion metric helps object-oriented software developers detect class design weaknesses and refactor classes accordingly. Several class cohesion metrics have been proposed in the literature. Most of these metrics are applicable based on low-level design information such as attribute references in methods. Some of these metrics capture class cohesion by counting the number of method pairs that share common attributes. A few metrics measure cohesion more precisely by considering the degree of interaction, through attribute references, between each pair of methods. However, the formulas applied by these metrics to measure the degree of interaction cause the metrics to violate important mathematical properties, thus undermining their construct validity and leading to misleading cohesion measurement. In this paper, we propose a formula that precisely measures the degree of interaction between each pair of methods, and we use it as a basis to introduce a low-level design class cohesion metric (LSCC). We verify that the proposed formula does not cause the metric to violate important mathematical properties. In addition, we provide a mechanism to use this metric as a useful indicator for refactoring weakly cohesive classes, thus showing its usefulness in improving class cohesion. Finally, we empirically validate LSCC. Using four open source software systems and eleven cohesion metrics, we investigate the relationship between LSCC, other cohesion metrics, and fault occurrences in classes. Our results show that LSCC is one of three metrics that explains more accurately the presence of faults in classes. LSCC is the only one among the three metrics to comply with important mathematical properties, and statistical analysis shows it captures a measurement dimension of its own. This suggests that LSCC is a better alternative, when taking into account both theoretical and empirical results, as a measure to guide the refactoring of classes. From a more general standpoint, the results suggest that class quality, as measured in terms of fault occurrences, can be more accurately explained by cohesion metrics that account for the degree of interaction between each pair of methods.

Recognising object-oriented software design quality: a practitioner-based questionnaire survey

“…Chidamber and Kemerer used viewpoints collected from practitioners to drive the development of their metrics. Concerns about the theoretical validity of some of the cohesion and coupling aspects of the original C&K metrics (Hitz and Montazeri 1996;Mayer and Hall 1999;Kitchenham 2010) have led to refinements such as LCOM4 (lack of cohesion) (Hitz and Montazeri 1995) and Low level design Similarity-based Class Cohesion metric (LSCC) (Al Dallal and Briand 2012).…”

Analysis of Metric-Based Object-Oriented Code Refactoring Opportunities Identification Approaches

“…2. Moreover, there are several approaches or techniques that have been proposed and utilized in the identification of refactoring opportunities [17][18] [25]. These approaches are either completely automated or semi-auto mated [12][17] [18].…”

“…However, some of the approaches shared identification techniques, though designed for d ifferent refactorings operations. The approaches that utilized code structural informat ion emp loyed prediction models whiles others only relied on [26] while the approach by Al Dallal and Briand [25] relied on the code structural information using either OO metrics, traditional metrics or hybrid of them to identify opportunities for refactorings.…”

“…"A precise method-method interaction-based cohesion metric for object-oriented classes": Al Dallal and Briand [25] also proposed a cohesion metric based on pre-existing cohesion metrics of classes that relied mostly on method-method interactions (MMI) metrics to identify where refactorings are needed in code. The metric called Low-level design Similarity-based Class Cohesion (LSCC) [25], was used to quantify the degree of communicat ion between methods in a class.…”

“…The metric called Low-level design Similarity-based Class Cohesion (LSCC) [25], was used to quantify the degree of communicat ion between methods in a class. It collects common attributes that exis t between methods in a class and used them to quantify the degree of similarity.…”