000 | 01184nab a22002417 4500 | ||
---|---|---|---|
001 | H004.415 JOU | ||
003 | AR-sfUTN | ||
008 | 190909b xx |||p|r|||| 00| 0 spa d | ||
040 | _cAR-sfUTN | ||
080 | _aH004.415 JOU | ||
100 | _aMcGregor, John D. | ||
245 | _aTaking testing to the extreme | ||
336 |
_2rdacontent _atexto _btxt |
||
337 |
_2rdamedia _asin mediaciĆ³n _bn |
||
338 |
_2rdacarrier _avolumen _bnc |
||
505 | _aAt almost every presentation I make these days someone asks me, What do you think about Extreme Programming? This usually occurs after I have been talking about the importance of design and the effectiveness of testing. Apparently, the assumption on the part of the questioner is that Extreme Programming (XP) downplays the importance of both design and testing. My standard answer is, I have seen Extreme Programming used effectively, and I have seen it fail miserably. | ||
650 | _aMETHODS | ||
650 | _aTESTING | ||
650 | _aOBJECT ORIENTED PROGRAMMING | ||
773 |
_tJOOP : the journal of object-oriented programming _wH004.415 JOU _nS.T.:H004.415 JOU PP3430 _g(vol. 13, nro. 10, Feb. 2001), p. 8-11 |
||
942 | _cAN | ||
999 |
_c37421 _d37421 |