Managing software requirements : a use case approach / Dean Leffingwell, Don Widrig.

Introduction: 1. The requirements problem -- 2. Introduction to requirements management -- 3. Requirements and the software cycle -- 4. The software team -- Team skill 1. Analyzing the problem: 5. The five steps in problem analysis -- 6. Business modeling -- 7. Systems engineering of software-intensive systems -- Team skill 2. Understanding user and stakeholder needs: 8. The challenge of requirements elicitation -- 9. The features of a product or system -- 10. Interviewing -- 11. Requirements workshops -- 12. Brainstorming and idea reduction -- 13. Storyboarding -- Team skill 3. Defining the system: 14. A use case primer -- 15. organizing requirements information -- 16. The vision document -- 17. Product management -- Team skill 4. Managing scope: 18. Establishing project scope -- 19. Managing your customer -- Team skill 5. Refining the system definition: 20. Software requirements, a more rigorous look -- 21. Refining the use cases -- 22. Developing the supplementary specification -- 23. On ambiguity and specificity -- 24. Technical methods for specfiying requirements -- Team skill 6. Building the right system: 25. From use cases to implementation -- 26. From use cases to test cases -- 27. Tracing requirements -- 28. Managing change -- 29. Assessing requirements qulity in iterative development -- Getting started: 30. Agile requirements methods -- 31. Your prescription for requirements management -- Appendixes: A. HOLIS artifacts -- B. Vision document template -- C. Use-case specification template -- D. Supplementary specification template -- E. Requirements management in the rational unified process -- F. Requirements management in the SEI-CMM and withing ISO 90000:2000.