| 000 | 01515nam a2200229Ia 4500 | ||
|---|---|---|---|
| 005 | 20250730164923.0 | ||
| 008 | 250728s9999 xx 000 0 und d | ||
| 020 | _a978-0-13-814181-3 | ||
| 082 | _aC 005,1 P47s | ||
| 100 | _aPfleeger, Shari Lawrence | ||
| 245 | 0 | _aSoftware Engineering Theory And Practice | |
| 250 | _a4th ed. | ||
| 260 | _aNew Jersey | ||
| 260 | _b Pearson | ||
| 260 | _c2010 | ||
| 300 | _a782 p. | ||
| 300 | _bIncludes bibliography and index | ||
| 520 | _aSoftware engineering has come a long way since 1968, when the term was first used at a NATO conference. And software itself has entered our lives in ways that few had anticipated, even a decade ago. So a firm grounding in software engineering theory and practice is essential for understanding how to build good software and for evaluating the risks and opportunities that software presents in our everyday lives. This text represents the blending of the two current software engineering worlds: that of the practitioner, whose main focus is to build high-quality products that perform useful functions, and that of the researcher, who strives to find ways to improve the quality of products and the productivity of those who build them. Edsgar Dykstra continually reminded us that rigor in research and practice tests our understanding of software engineering and helps us to improve our thinking, our approaches, and ultimately our products. | ||
| 650 | _aSoftware Engineering | ||
| 700 | _aAtlee, Joanne M. | ||
| 942 |
_2ddc _cBK |
||
| 999 |
_c95 _d95 |
||