| 000 | 00966nam a22002537a 4500 | ||
|---|---|---|---|
| 003 | BDCtgAUW | ||
| 005 | 20250509182751.0 | ||
| 008 | 250509b bg ||||| |||| 00| 0 eng d | ||
| 020 | _a9780262542111 | ||
| 040 |
_aBDCtgAUW _cBDCtgAUW _dBDCtgAUW |
||
| 050 | _aQA76.76.Q35 E76 | ||
| 100 |
_aErnst, Neil _eAuthor _977006 |
||
| 245 |
_aTechnical Debt in Practice: _b How to Find It and Fix It |
||
| 260 |
_aCambridge, Massachusetts: _b The MIT Press, _c2021 |
||
| 300 |
_a294 pages ; _c 24 cm |
||
| 520 | _a"A look at technical debt in software that focuses on the practical implications of technical debt for the entire software lifecycle" | ||
| 650 |
_a Computer software _xDevelopment _x Quality control. _977007 |
||
| 650 |
_aSoftware failures _xPrevention _977008 |
||
| 650 | _aProject management | ||
| 650 |
_aMaintainability (Engineering) _977009 |
||
| 700 |
_aKazman, Rick _eAuthor _977010 |
||
| 700 |
_aDelange, Julien _eAuthor _977011 |
||
| 942 |
_2lcc _cBK _n0 |
||
| 999 |
_c14295 _d14295 |
||
| 887 |
_28 _aPapia Akter |
||
| 888 | _28 | ||