12/7/2016 | 1 An outlook on Technical Debt Management Reducing Friction in Software Development Paris Avgeriou, Philippe Kruchten, Robert Nord, Ipek Ozkaya, Carolyn Seaman paris@cs.rug.nl
State of the art 12/7/2016 | 2 › From source code to the whole lifecycle › Glossaries and ontologies (convergent) › Tooling (industrial & prototypes) › Economic theories
State of practice 12/7/2016 | 3 SW engineers › Understand the concept and challenges › Deal with it during maintenance › TD management in place • Resource-intensive • Realistically only a portion managed
Main thesis 12/7/2016 | 4 › Technical debt grows › Managing TD is dominant in SW evolution • Established as a core SE practice › It’s the next big thing ++ Investment -- Bankruptcy
A perfect storm? For every 100 KLOC an average software application had approximately US$361,000 of technical debt* . Curtis et al. “ Estimating the Principal of an Application’s TD,” IEEE Software ‘12
Is this really new? 12/7/2016 | 7 Communities › Maintenance & evolution › Reengineering / refactoring Terms › Aging › Decay › Sustainability › Little progress › “Dull” topic
Convergence 12/7/2016 | 8 › Program analysis/comprehension › SW Quality measurement › Qualitative research methods › SW risk management › Industry-academia
Research output is soaring 12/7/2016 | 9 Z. Li et al., A systematic mapping study on technical debt and its management, JSS 2015
12/7/2016 | 10 4 ways to prepare for the storm
1. Management process 12/7/2016 | 11 › TD prevention › TD identification › TD measurement › TD prioritization › TD monitoring › TD repayment › TD documentation › TD communication Li et al., Architectural Debt Management in Value-oriented Architecting, Elsevier ‘14
2. Software Economics 12/7/2016 | 13 › Mimic economics data-driven focus • Availability of rich data › Investment strategies › Assign business value to intrinsic qualities › Bridge the communication divide
3. Design and Architecture 12/7/2016 | 14 › Acknowledge elephant in the room • Main concerns stem from architecture • But hard to detect automatically › Architecture backlog › Traceability with code › Architecture evaluations and refactoring
4. TD in the curriculum 12/7/2016 | 15 › “No bugs found” vs. • Internal qualities • Trading off features with qualities • Decisions as investments › Throughout the SE courses • Brownfield projects • Linked with software economics
Submit to MTD9@XP2017
Recommend
More recommend
