Refactoring and aggregation

Johnson, Ralph E.; Opdyke, William F.

doi:10.1007/3-540-57342-9_78

Cited by 53 publications

(22 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Our data suggests DIT 3 to be the threshold value and NOC to be limited to as small as possible a value. Second, the study highlights a) the need to maintain a pragmatic view of the entire hierarchy and b) the vigilance needed on the part of developers and project managers to apply consistent, remedial techniques such as refactoring [Fowler99] and re-engineering; for example, the replacement of inheritance with aggregation or other forms of coupling [Johnson93]. Third, if, as we suggest, there is a level of DIT and NOC which show a higher propensity for faults, then what is a project manager or developer to do in the face of consistent pressure for a system to grow in size as it evolves [Girba05]?…”

Section: Discussionmentioning

confidence: 99%

Size, Inheritance, Change and Fault-proneness in C# software.

Gatrell¹,

Counsell²

2010

JOT

View full text Add to dashboard Cite

P u b l i s h e d b y E T H Z u r i c h , C h a i r o f S o f t w a r e E n g i n e e r i n g © J o t , 2 0 1 0 O n l i n e a t h t t p : / / w w w . Abstract This paper documents a study of change in commercial, proprietary C# software and attempts to determine whether a relationship exists between class changes and faults and the design context of a class, namely its size and inheritance relationships.Results showed a strong positive correlation between the size of a class and change-proneness but not for all the class features studied. Classes within a specific range of a) inheritance depth and b) number of children were found to be relatively more prone to change. For the fault data and for the same class features, similar results were found. The most striking result to emerge however was the existence of an inheritance depth 'interval' between which change (and faultproneness) were at their highest. Below and above that interval, both features were less prominent. The results thus add weight to the claims of other previous studies which suggest that there is an optimal level of inheritance, beyond which maintenance may become problematic from both a change and fault perspective.

show abstract

Section: Discussionmentioning

confidence: 99%

Size, Inheritance, Change and Fault-proneness in C# software.

Gatrell¹,

Counsell²

2010

JOT

View full text Add to dashboard Cite

show abstract

“…It should be possible to dynamically introduce levels of indirection as soon as a more flexible coupling becomes necessary. For instance, this could be the case in the context of run-time management or refactoring along aggregation relations [24]. In this and the following section we introduce the notions Dynamic Facade as well as Role and Core Object in order to enable naming and referencing of particular indirection concepts in use.…”

Section: Dynamic Facadesmentioning

confidence: 99%