Matches in DBpedia 2016-04 for { <http://wikidata.dbpedia.org/resource/Q1532172> ?p ?o }
Showing triples 1 to 50 of
50
with 100 triples per page.
- Q1532172 subject Q7058146.
- Q1532172 subject Q7155980.
- Q1532172 subject Q7169854.
- Q1532172 subject Q8915757.
- Q1532172 abstract "Technical debt (also known as design debt or code debt) is a metaphor referring to the eventual consequences of any system design, software architecture or software development within a codebase. The debt can be thought of as work that needs to be done before a particular job can be considered complete or proper. If the debt is not repaid, then it will keep on accumulating interest, making it hard to implement changes later on. Unaddressed technical debt increases software entropy. Also known as a feature gap. Analogous to monetary debt, technical debt is not necessarily a bad thing, and sometimes technical debt is required to move projects forward. Some experts claim that the "technical debt" metaphor tends to minimize the impact, which results in insufficient prioritization of the necessary work to correct it.As a change is started on a codebase, there is often the need to make other coordinated changes at the same time in other parts of the codebase or documentation. The other required, but uncompleted changes, are considered debt that must be paid at some point in the future. Just like financial debt, these uncompleted changes incur interest on top of interest, making it cumbersome to build a project. Although the term is used in software development primarily, it can also be applied to other professions.".
- Q1532172 wikiPageExternalLink wiki?WardExplainsDebtMetaphor.
- Q1532172 wikiPageExternalLink citation.cfm?id=156632.
- Q1532172 wikiPageExternalLink Technical_Debt.
- Q1532172 wikiPageExternalLink lehmanslaws.pdf.
- Q1532172 wikiPageExternalLink TechnicalDebt.html.
- Q1532172 wikiPageExternalLink 2006-06-26.AndyLester.
- Q1532172 wikiPageExternalLink www.ontechnicaldebt.com.
- Q1532172 wikiPageExternalLink watch?v=lEKvzEyNtbk.
- Q1532172 wikiPageExternalLink ward-cunningham-interview-about-technical-debt-sqale-agile.
- Q1532172 wikiPageExternalLink interview-with-jean-louis-letouzey-on-technical-debt-and-sqale.
- Q1532172 wikiPageExternalLink interview-with-philippe-kruchten-on-technical-debt-rup-ubc-decision-process-architecture.
- Q1532172 wikiPageExternalLink technical-debt-interview-with-ipek-ozkaya-on-technical-debt-sei-ieee-software-architecture-agile.
- Q1532172 wikiPageExternalLink Software_cancer_the_seven_early_warning_signs.
- Q1532172 wikiPageWikiLink Q1130645.
- Q1532172 wikiPageWikiLink Q1141067.
- Q1532172 wikiPageWikiLink Q116877.
- Q1532172 wikiPageWikiLink Q1329550.
- Q1532172 wikiPageWikiLink Q1475717.
- Q1532172 wikiPageWikiLink Q170924.
- Q1532172 wikiPageWikiLink Q1812883.
- Q1532172 wikiPageWikiLink Q2295111.
- Q1532172 wikiPageWikiLink Q2425187.
- Q1532172 wikiPageWikiLink Q2996135.
- Q1532172 wikiPageWikiLink Q3196867.
- Q1532172 wikiPageWikiLink Q3448624.
- Q1532172 wikiPageWikiLink Q3459978.
- Q1532172 wikiPageWikiLink Q352213.
- Q1532172 wikiPageWikiLink Q368399.
- Q1532172 wikiPageWikiLink Q3799353.
- Q1532172 wikiPageWikiLink Q6315486.
- Q1532172 wikiPageWikiLink Q638608.
- Q1532172 wikiPageWikiLink Q6453666.
- Q1532172 wikiPageWikiLink Q6751015.
- Q1532172 wikiPageWikiLink Q7058146.
- Q1532172 wikiPageWikiLink Q7155980.
- Q1532172 wikiPageWikiLink Q7169854.
- Q1532172 wikiPageWikiLink Q7637.
- Q1532172 wikiPageWikiLink Q788790.
- Q1532172 wikiPageWikiLink Q79872.
- Q1532172 wikiPageWikiLink Q846636.
- Q1532172 wikiPageWikiLink Q8915757.
- Q1532172 wikiPageWikiLink Q92803.
- Q1532172 wikiPageWikiLink Q958242.
- Q1532172 comment "Technical debt (also known as design debt or code debt) is a metaphor referring to the eventual consequences of any system design, software architecture or software development within a codebase. The debt can be thought of as work that needs to be done before a particular job can be considered complete or proper. If the debt is not repaid, then it will keep on accumulating interest, making it hard to implement changes later on. Unaddressed technical debt increases software entropy.".
- Q1532172 label "Technical debt".