LEADER 02234nam  2200349   450 
001 9910412446903321
005 20230830135907.0
024 7 $a10.5555/3355321
035   $a(CKB)5280000000244491
035   $a(NjHacI)995280000000244491
035   $a(EXLCZ)995280000000244491
100   $a20230830d2019      uy             0
101 0 $aeng
135   $aur|||||||||||
181   $ctxt$2rdacontent
182   $cc$2rdamedia
183   $acr$2rdacarrier
200 10$aProceedings of the Second International Conference on Technical Debt /$fParis Avgeriou, Klaus Schmid
210  1$aPublisher: IEEE Press :$cIEEE Press,$d2019.
215   $a1 online resource
330   $aTechnical debt is a metaphor that software developers and managers increasingly use to communicate key trade-offs between business constraints and internal quality issues, especially those related to time to market. While other software engineering disciplines---such as software sustainability, maintenance and evolution, refactoring, software quality, and empirical software engineering---have produced results relevant to managing technical debt, none of them alone suffices to model, manage, and communicate the different facets of the complex trade-offs involved in managing technical debt. Similarly, while many software engineering practices can be used to get ahead of technical debt, organizations struggle with managing technical debt routinely and strategically. Technical debt draws on research from many domains that is becoming part of the answer to the technical-debt question: how do we quantify and monitor the economic impact of decisions over time? This research includes software engineering disciplines in software aging and decay, risk management, qualitative methods and appreciation for context, software metrics, program analysis, and software quality.
606   $aSoftware engineering$vCongresses
615  0$aSoftware engineering
676   $a005.1
700   $aAvgeriou$b Paris$0887137
702   $aSchmid$b Klaus 
801  0$bNjHacI
801  1$bNjHacl
906   $aBOOK
912   $a9910412446903321
996   $aProceedings of the Second International Conference on Technical Debt$93461963
997   $aUNINA