A multiple case study of design pattern decay, grime, and rot in evolving software systems

Izurieta, Clemente; Bieman, James M.

doi:10.1007/s11219-012-9175-x

Cited by 41 publications

(43 citation statements)

References 33 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…They conducted empirical studies across [10] open source systems to validate and refine this extended taxonomy. Further studies on grime have shown implications of grime on the testability of a system [12]. Although evidence for class grime has been inconclusive to date [11], we believe that this was due to a less than refined definition of class grime, which the research herein is a step towards validating.…”

Section: Background and Related Workmentioning

confidence: 80%

“…Yet even with such a wide spread adoption and well-studied implementation practices, design pattern realizations are not immune to decay over their evolution [9][10][11][12]. The decay of pattern realizations, specifically design pattern grime, involves the obfuscation or deviation of pattern structure and behavior from the original intent [10].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Design pattern decay

Griffith

Izurieta

2014

Proceedings of the 8th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement

Self Cite

View full text Add to dashboard Cite

Context:We investigate class grime, a form of design pattern decay, wherein classes of the pattern realization have extraneous attributes or methods, which obfuscate the intended design of a pattern. Goal: To expand the taxonomy of class grime using properties of class cohesion. Using this expanded taxonomy we explore the effect that forms of class grime have on pattern realization understandability. Method: A pilot study utilizing a formal experiment to explore the effects of class grime on design pattern understandability. The experiments used simulated injection of 8 types of class grime into design pattern realizations randomly selected from 16 design pattern types from a set of 6541 realizations from 520 distinct software systems. Results: We found that for each of the 8 identified class grime forms, understandability was negatively affected. Conclusion: This work serves as early communication of research for the validation of the extended taxonomy as well as the method of grime injection used in the experiment.

show abstract

Section: Background and Related Workmentioning

confidence: 80%

Section: Introductionmentioning

confidence: 99%

Design pattern decay

Griffith

Izurieta

2014

Proceedings of the 8th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement

Self Cite

View full text Add to dashboard Cite

show abstract

“…Model Rot -Refers to the deterioration of the structural integrity of a model when compared to its meta-model. This is a corollary to design pattern rot [14]. viii.…”

Section: Definitionsmentioning

confidence: 92%

Preemptive Management of Model Driven Technical Debt for Improving Software Quality

Izurieta

Rojas

Griffith

2015

Proceedings of the 11th International ACM SIGSOFT Conference on Quality of Software Architectures

Self Cite

View full text Add to dashboard Cite

Technical debt has been the subject of numerous studies over the last few years. To date, most of the research has concentrated on management (detection, quantification, and decision making) approaches -most performed at code and implementation levels through various static analysis tools. However, if practitioners are to adopt model driven techniques, then the management of technical debt also requires that we address this problem during the specification and architectural phases. This position paper discusses several questions that need to be addressed in order to improve the quality of software architecture by exploring the management of technical debt during modeling, and suggests various lines of research that are worthwhile subjects for further investigation.

show abstract

“…Grime represents a form of TD, since the effort to keep the patterns cleanly instantiated has been deferred. In prior studies, Izurieta and Bieman [25] introduced the notion of design pattern grime and performed a study on three open source systems, JRefactory, ArgoUML, and eXist.…”

Section: Identification Of Technical Debt Guo and Seamanmentioning

confidence: 99%

Supporting Technical Debt Cataloging with TD-Tracker Tool

Foganholi

Garcia

Eler

et al. 2015

Advances in Software Engineering

View full text Add to dashboard Cite

Technical debt (TD) is an emergent area that has stimulated academic concern. Managers must have information about debt in order to balance time-to-market advantages and issues of TD. In addition, managers must have information about TD to plan payments. Development tasks such as designing, coding, and testing generate different sorts of TD, each one with specific information. Moreover, literature review pointed out a gap in identifying and accurately cataloging technical debt. It is possible to find tools that can identify technical debt, but there is not a described solution that supports cataloging all types of debt. This paper presents an approach to create an integrated catalog of technical debts from different software development tasks. The approach allows tabulating and managing TD properties in order to support managers in the decision process. It also allows managers to track TD. The approach is implemented by TD-Tracker tool, which can integrate different TD identification tools and import identified debts. We present integrations between TD-Tracker and two external tools, used to identify potential technical debts. As part of the approach, we describe how to map the relationship between TD-Tracker and the external tools. We also show how to manage external information within TD-Tracker.

show abstract

A multiple case study of design pattern decay, grime, and rot in evolving software systems

Cited by 41 publications

References 33 publications

Design pattern decay

Design pattern decay

Preemptive Management of Model Driven Technical Debt for Improving Software Quality

Supporting Technical Debt Cataloging with TD-Tracker Tool

Contact Info

Product

Resources

About