| 000 | 02490nam a22002777i 4500 | ||
|---|---|---|---|
| 005 | 20251030135901.0 | ||
| 007 | t| | ||
| 008 | 230502s2013 wau||||| |||| 00| 0 spa d | ||
| 020 | _a9780735679665 | ||
| 040 |
_aCO-ViULL _erda _bspa |
||
| 041 | _heng | ||
| 082 | 0 |
_223 _a005.1 _bW645 |
|
| 100 | 1 |
_aWiegers, Karl _9160699, _eautor. _4aut |
|
| 245 | 1 | 0 | _aSoftware requirements. |
| 250 | _a3. | ||
| 264 | 1 |
_aWashington : _bMicrosoft, _c2013. |
|
| 300 |
_a637 páginas : _b: tables ; figuras. |
||
| 336 |
_atexto _btxt _2rdacontent |
||
| 337 |
_asin mediación _bn _2rdamedia |
||
| 338 |
_avolumen _bnc _2rdacarrier |
||
| 500 | _aContents at a glance. | ||
| 505 | 8 | _a1. The essential software requirement. -- 2. Requirements from the customer’s perspective. -- 3. Good practices for requirements engineering. -- 4. The business analyst. -- II. Requirements development. -- 5. Establishing the business requirements. -- 6. Finding the voice of the user. -- 7. Requirements elicitation. -- 8. Understanding user requirements. -- 9. Playing by the rules. -- 10. Documenting the requirements. -- 11. Writing excellent requirements. -- 12. A picture is worth 1024 words. -- 13. Specifying data requirements. -- 14. Beyond functionality. -- 15. Risk reduction through prototyping. -- 16. First things first: Setting requirement priorities. -- 17. Validating the requirements. -- 18. Requirements reuse. -- 19. Beyond requirements development. -- III. Requirements for specific project classes. -- 20. Agile projects. -- 21. Enhancement and replacement projects. -- 22. Packaged solution projects. -- 23. Outsourced projects. -- 24. Business process automation projects. -- 25. Business analytics projects. -- 26. Embedded and other real-time systems projects. -- IV. Requirements management. -- 27. Requirements management practices. -- 28. Change happens. -- 29. Links in the requirements chain. -- 30. Tools for requirements engineering. -- V. Implementing requirements engineering. -- 31. Improving your requirements processes. -- 32. Software requirements and risk management. | |
| 520 | _aNow in its third edition, this classic guide to software requirements engineering has been fully updated with new topics, examples, and guidance. Two leaders in the requirements community have teamed up to deliver a contemporary set of practices covering the full range of requirements development and management activities on software projects. | ||
| 700 | 1 |
_aBeatty, Joy _9160700. |
|
| 942 |
_2ddc _cBK |
||
| 999 |
_c47452 _d47452 |
||