Front cover image for Managing software requirements : a use case approach

Managing software requirements : a use case approach

"Many projects fail because developers fail to build the right thing. Developers of any kind of application should read this book."--Grady Booch "A comprehensive solution to the requirements challenges faced by every development team. Full of insight and ideas all developers can learn from." -Ivar Jacobson Despite the wealth of development knowledge, experience, and tools available today, a substantial percentage of software projects fail, often because requirements are not correctly determined and defined at the outset, or are not managed correctly as the project unfolds. This second edition of the popular text Managing Software Requirements focuses on this critical cause of failure and offers a practical, proven approach to building systems that meet customers' needs on time and within budget. Using an accessible style, their own war stories, and a comprehensive case study, the authors show how analysts and developers can effectively identify requirements by applying a variety of techniques, centered on the power of use cases. The book illustrates proven techniques for determining, implementing, and validating requirements. It describes six vital Team Skills for managing requirements throughout the lifecycle of a project: Analyzing the Problem, Understanding User Needs, Defining the System, Managing Scope, Refining the System Definition, and Building the Right System. Managing Software Requirements, Second Edition, specifically addresses the ongoing challenge of managing change and describes a process for assuring that project scope is successfully defined and agreed upon by all stakeholders. Topics covered include: The five steps in problem analysis Business modeling and system engineering Techniques for eliciting requirements from customers and stakeholders Establishing and managing project scope Applying and refining use cases Product management Transitioning from requirements to design and implementation Transitioning from use cases to test cases Agile requirements methods 032112247XB05082003
eBook, English, ©2003
Addison-Wesley, Boston, ©2003
1 online resource (xxxvii, 502 pages) : illustrations
9780321122476, 032112247X
54115707
Print version:
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
English