2009 · 25 citations · 24 references
ComputingSystems EngineeringAgile Project ManagementResistance To ChangeSoftware EngineeringAgile Software DevelopmentSoftware DesignSoftware EvolutionSoftware MaintenanceSoftware RefactoringSoftware ReuseComplexity AnalysisRefactoringRefactoring DetectionRefactoring Opportunity DetectionRefactoring PlanningSoftware Evolution AnalysisTask Complexity
Software entropy is a phenomenon where repeated changes gradually degrade the structure of the system, making it hard to understand and maintain. This phenomenon imposes challenges for organizations that have moved to agile methods from other processes, despite agile's focus on adaptability and responsiveness to change. We have investigated this issue through an industrial case study, and reviewed the literature on addressing software entropy, focussing on the detection of ldquocode smellsrdquo and their treatment by refactoring. We found that in order to remain agile despite of software entropy, developers need better support for understanding, planning and testing the impact of changes. However, it is exactly work on refactoring decision support and task complexity analysis that is lacking in literature. Based on our findings, we discuss strategies for dealing with entropy in this context and present avenues for future research.
24
Java quality assurance by detecting code smells
Eva van Emden, Leon Moonen · 2003 · 380 citations
Detecting object usage anomalies
Andrzej Wasylkowski, Andreas Zeller, Christian Lindig · 2007 · 274 citations
Changing the paradigm of software engineering
Václav Rajlich · Communications of the ACM · 2006 · 171 citations
Management, Project Management, Agile Project Management +14