No matter how much instruction youave had on managing software requirements, thereas no substitute for experience. Too often, lessons about requirements engineering processes lack the no-nonsense guidance that supports real-world solutions. Complementing the best practices presented in his book, Software Requirements, Second Edition, requirements engineering authority Karl Wiegers tackles even more of the real issues head-on in this book. With straightforward, professional advice and practical solutions based on actual project experiences, this book answers many of the tough questions raised by industry professionals. From strategies for estimating and working with customers to the nuts and bolts of documenting requirements, this essential companion gives developers, analysts, and managers the cosmic truths that apply to virtually every software development project. Discover how to: ac Make the business case for investing in better requirements practices ac Generate estimates using three specific techniques ac Conduct inquiries to elicit meaningful business and user requirements ac Clearly document project scope ac Implement use cases, scenarios, and user stories effectively ac Improve inspections and peer reviews ac Write requirements that avoid ambiguityNotice that all these use cases begin with a verb. This is a standard convention for naming use cases. The analysts ... flight itinerary. We cana#39;t use a software system to change the weather, but we might be able tocheck the weatherif this capability is deemed to be in scope for the project. ... a use case. When discussing the airline flight reservation kiosk, a student will often suggest as a possible use case, anbsp;...
|Title||:||More About Software Requirements|
|Publisher||:||Microsoft Press - 2005-12-20|