Resumen:
PART I. SOFTWARE REQUIREMENTS: WHAT, WHY, AND WHO -- CHAPTER 1. The essential software requirement -- CHAPTER 2. Requirements from the customer’s perspective -- CHAPTER 3. Good practices for requirements engineering -- CHAPTER 4. The business analyst -- PART II. REQUIREMENTS DEVELOPMENT -- CHAPTER 5. Establishing the business requirements -- CHAPTER 6. Finding the voice of the user -- CHAPTER 7. Requirements elicitation -- CHAPTER 8. Understanding user requirements -- CHAPTER 9. Playing by the rules -- CHAPTER 10. Documenting the requirements -- CHAPTER 11. Writing excellent requirements -- CHAPTER 12. A picture is worth 1024 words -- CHAPTER 13. Specifying data requirements -- CHAPTER 14. Beyond functionality -- CHAPTER 15. Risk reduction through prototyping -- CHAPTER 16. First things first: Setting requirement priorities -- CHAPTER 17. Validating the requirements -- CHAPTER 18. Requirements reuse -- CHAPTER 19. Beyond requirements development -- PART III. REQUIREMENTS FOR SPECIFIC PROJECT CLASSES -- CHAPTER 20. Agile projects -- CHAPTER 21. Enhancement and replacement projects -- CHAPTER 22. Packaged solution projects -- CHAPTER 23. Outsourced projects -- CHAPTER 24. Business process automation projects -- CHAPTER 25. Business analytics projects -- CHAPTER 26. Embedded and other real-time systems projects -- PART IV REQUIREMENTS MANAGEMENT -- CHAPTER 27. Requirements management practices -- CHAPTER 28. Change happens -- CHAPTER 29. Links in the requirements chain -- CHAPTER 30. Tools for requirements engineering -- PART V. IMPLEMENTING REQUIREMENTS ENGINEERING --CHAPTER 31. Improving your requirements processes -- CHAPTER 32. Software requirements and risk management.