1 / 51

Technical Debt

Technical Debt. CS 577 Software Engineering Supannika Koolmanojwong. Wednesday Oct 30 Team Presentation. Each team will briefly introduce your project Team 3 – OCD: Boundary Diagram, Business Workflow, Project plan (5 minutes) Team 4 – Prototype (10 minutes)

quant
Download Presentation

Technical Debt

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Technical Debt CS 577 Software Engineering Supannika Koolmanojwong

  2. Wednesday Oct 30Team Presentation Each team will briefly introduce your project Team 3 – OCD: Boundary Diagram, Business Workflow, Project plan (5 minutes) Team 4 – Prototype (10 minutes) Team 6 – Prototype (10 minutes) Team 13 – Prototype (10 minutes) Team 14 – Prototype (10 minutes) Team 16 – Prototype (10 minutes) Team 15 – Risks & Configuration Management & Quality Management Strategy (5 minutes)

  3. Outline Total Cost of Ownership Technical Debt

  4. What are the cost of a software? Think about the whole life cycle

  5. Total cost of ownership • a financial estimate whose purpose is to help consumers and enterprise managers determine direct and indirect costs of a product or system. • including the costs to research, develop, acquire, own, operate, maintain, and dispose of a system

  6. Potential total cost of ownership • HW and SW • Network • Server • Workstation • Installation & integration • Purchasing research • Warranties and licenses • License tracking - compliance • Migration expenses • Risks: susceptibility to vulnerabilities, availability of upgrades, patches and future licensing policies, etc. • Infrastructure • Electricity • Testing costs • Downtime, outage and failure expenses • Diminished performance • Security (including breaches, loss of reputation, recovery & prevention) • Backup and recovery process • Technology training • Audit • Insurance • IT personnel • Replacement • Future upgrade or scalability expenses • Decommissioning

  7. Relative* Total Ownership Cost (TOC)For single system life cycle (TOC-SS) ~5% architecture investment ~5% architecture investment ~25% architecture investment * Cumulative architecting and rework effort relative to initial development effort

  8. CodeSmell Deficit programming Code Debt Technical Debt Software Decay coined by Ward Cunningham Design Debt Technical Inflation

  9. Technical Debt “is a measure of how untidy or out-of-date the development work area for a product is” Not the deferred requirements http://www.c2.com/cgi/wiki?TechnicalDebt

  10. Technical Debt http://petdance.com/perl/technical-debt “I don’t know what happened, I just changed one line” “We can’t upgrade, It will break” “We can’t upgrade the code, we don’t have time” “We can’t upgrade the code, no one understands it” “Just put in the comment XXX, we will do it later” “Just put in the TODO comment”

  11. Financial debt vsTechnical Debt http://martinfowler.com/bliki/TechnicalDebt.html

  12. http://pkruchten.files.wordpress.com/2011/10/kruchten-111027-techdebt.pdfhttp://pkruchten.files.wordpress.com/2011/10/kruchten-111027-techdebt.pdf

  13. Technical Debt • intentional technical debt • cost to taking short cuts • unintentional technical debt • making mistakes • Conscious decision to optimize for the “present” rather than the “future” • cost of not dealing with these short cuts and mistakes will increase over time.  Read more: http://www.javacodegeeks.com/2012/02/technical-debt-how-much-is-it-really.html#ixzz1phjvB5A9

  14. Common causes of technical debt Business pressures Lack of process or understanding Lack of building loosely coupled components (hard-coded) Lack of documentation Parallel Development Delayed Refactoring http://en.wikipedia.org/wiki/Technical_debt

  15. Technical DebtArchitecture or the platform technology mistake Read more: http://www.javacodegeeks.com/2012/02/technical-debt-how-much-is-it-really.html#ixzz1phnGFlUV Scalability, reliability Foundations are poorly design you don’t find out until too late (operations phase) no choice but to start again or rewrite big chunk to keep it working

  16. Technical DebtError-prone code Read more: http://www.javacodegeeks.com/2012/02/technical-debt-how-much-is-it-really.html#ixzz1phnGFlUV http://petdance.com/perl/technical-debt/technical-debt.007.html “ .. If I change X, it is going to break Y, I think ..” “ Don’t touch that code, last time we did, we spent a week fixing it…” 20% of the code where 80% of bugs are found Hard to understand Dangerous to change because done poorly one in the first place Not rewriting this code is one of the most expensive mistakes that developers make

  17. Technical DebtNot easily tested Read more: http://www.javacodegeeks.com/2012/02/technical-debt-how-much-is-it-really.html#ixzz1phnGFlUV “ .. I thought we had a test for that ..” Don’t have good automated tests Tests keep falling apart when you change the code Testing costs tend to go up over time as you write more code

  18. Technical DebtCode that mysteriously works Read more: http://www.javacodegeeks.com/2012/02/technical-debt-how-much-is-it-really.html#ixzz1phnGFlUV nobody is sure how or why Might be written by the geek who left the company if nobody on the team understands it, it’s a time bomb

  19. Technical DebtOthers Read more: http://www.javacodegeeks.com/2012/02/technical-debt-how-much-is-it-really.html#ixzz1phnGFlUV • Forward and backward compatibility • Short term debt • Duplicate, copy-and-paste code • How many ? Trackable ? • Hard coding • Out of date documentation • “We just lost the drive, where are the backups” • If nobody is using it, get rid of it. If people are using it, why isn’t it up to date?

  20. Technical Debt Cost average $3.61 to $5.42 per line of code. Example of Technical Debt Calculation http://docs.codehaus.org/display/SONAR/Technical+Debt+Calculation

  21. Technical Debt Observations“Agile Project Management”, Jim Highsmith, second edition

  22. Types of Debt“Managing Software Debt: Building for Inevitable Change”, Chris Sterling • Technical Debt • These are activities that a team or team members choose not to do well now and will impede future development if left undone • Quality Debt • There is a diminishing ability to verify the functional and technical quality of software • Configuration Management Debt • Integration and release management becomes more risky, complex and error-prone • Design Debt • The cost of adding features is increasing toward the point where it is more than the cost of writing from scratch. • Platform Debt • The availability of people to work on software changes is becoming limited or cost-prohibitive. www.psmsc.com

  23. Committed Costs 95% 85% 500X-1,000X 70% Cost to Extract Defects 20X-100X 3X-6X The Cost of Undetected Defects Operation  Disposal 100% 100% 90% 80% 70% 60% Production/Test Cumulative Percentage of Life-Cycle Cost 50% 50% 40% 30% Development 20% Design 20% Concept 15% 10% 8% 0% Reference: Defense Systems Management College (DAU) Time

  24. Development Cost(Perfect World) % Effort per Phase Analysis Test Integration Design Implementation

  25. Typical Defect Profiles Classification of Defects Design Defects Implementation Defects Integration Defects Analysis Test Integration Design Implementation Defect Insertion Defect detection & Removal

  26. Development Cost(Real World) % Effort per Phase Analysis Test Integration Design Implementation

  27. Development Cost % Effort per Phase Analysis Test Integration Design Implementation Real world Perfect World

  28. Development Cost Technical Debt? Technical Debt? % Effort per Phase Technical Debt? Technical Debt? Analysis Test Integration Design Implementation Real world Perfect World

  29. Development Cost Technical Debt? % Effort per Phase Technical Debt? Analysis Test Integration Design Implementation Real world Perfect World

  30. COTS Integration % Effort per Phase Technical Debt? Analysis Test Integration Design Implementation Real world Perfect World

  31. Fixing technical debt • 80/20 rule • 20% initial build • 80% clean up

  32. Fixing technical debt http://www.javacodegeeks.com/2011/11/dealing-with-technical-debt.html#ixzz1pjQ8bQpF • Big Bang • no new features for a year? Really?  • spend some time cleaning up the mess • Good ? • Dedicated Team • Have another team dedicated • Good ? 80/20 rule ? • Boy Scout • remove technical debt little and often • If no tests, add some. If poor test, improve them. If bad code, refactor it • The boy scout rule – leave the camp cleaner than you found it

  33. Fixing technical debt • Think time & risk & $$$ • No gold-plating • Unnecessary task that no one wants • BigResearchUpFrontvsBigDesignUpFront

  34. Technical Debt vs Agile : Bad http://www.startuplessonslearned.com/2009/07/embrace-technical-debt.html • Quick and dirty approach • Scalability vsDoTheSimplestThingThatCouldPossiblyWork • Just-in-time Scalability • change the architecture in response to actual customer demand • Wasted Code

  35. Technical Debt vs Agile : Good http://www.startuplessonslearned.com/2009/07/embrace-technical-debt.html Get feedback faster Smaller batches

  36. Technical Debt vs Lean : Good http://www.startuplessonslearned.com/2009/07/embrace-technical-debt.html Less waste, less debt Just-in-time nature

  37. Technical Debt vs NDI : Bad http://www.startuplessonslearned.com/2009/07/embrace-technical-debt.html • Product Development Leverage • Your product is fortified by others • Open-source, COTS, Services • Pros: Faster • Cons • Code understanding • Different coding styles, architecture, quality • No direct control

  38. http://pkruchten.files.wordpress.com/2011/10/kruchten-111027-techdebt.pdfhttp://pkruchten.files.wordpress.com/2011/10/kruchten-111027-techdebt.pdf

  39. http://pkruchten.files.wordpress.com/2011/10/kruchten-111027-techdebt.pdfhttp://pkruchten.files.wordpress.com/2011/10/kruchten-111027-techdebt.pdf

  40. http://pkruchten.files.wordpress.com/2011/10/kruchten-111027-techdebt.pdfhttp://pkruchten.files.wordpress.com/2011/10/kruchten-111027-techdebt.pdf

  41. Enablers and Inhibitors of Technical Debt For a new single system For an existing single system A system of systems

  42. Top 10 Inhibitors – Similarities

  43. Top 10 Inhibitors – Differences

  44. Top 10 Enablers - Similarities

  45. Top 10 Enablers - Differences

  46. ObservationsFlip side of a coin

  47. ObservationsGrey Area Common standard Flexible rules Requirements Volatility Requirements Flexibility Agile/lean approach Constituent Documentation

  48. ObservationsOverlap & Similar but not the same Lack of Domain Experience Unprecedentedness Technology Immaturity Technology Volatility Lack of decision making at lower levels Lack of decision making authority

  49. The bottom line • Trade off between • Technical Debt • Flexibility (Design for Reuse) • Expedition

More Related