The book’s commonsense approach provides exemplary project management skills tailored to gathering (and refining, implementing, and eventually tracking) software requirements. While the book often cites recent software engineering studies, the focus always returns to practical management techniques.
A case study for a chemical tracking application frames the book, and most chapters begin with anecdotes that demonstrate situations in which users and developers misunderstand each other about a software project’s ultimate goals. (If you’ve ever worked in the field, these stories will probably sound all too familiar.)
This book offers hope, though, for improving your “Requirements” are essential for creating successful software because they let users and developers agree on what features will be delivered in new systems. Karl Wiegers’s Software Requirements shows you how to define and get more out of software requirements with dozens of “best practices” and tips that make this book a valuable resource for both software project managers and developers.
Software design process, with dozens of tips on getting better design input from your customers and then using these requirements to generate a variety of design documents. There are numerous templates and sample documents too–a big help for the busy software manager. Several standout sections cover negotiating difficult steps in the process, particularly how to manage shifting requirements as projects move forward and keep the various users and stakeholders content throughout the software process. Late in the book, the author surveys today’s software management tools and shows how to pick the right ones for your organization. Anchored by the author’s considerable experience and software engineering expertise, this jargon-free and practical guide to software requirements can definitely give you the edge in managing software projects more efficiently.
Richard Dragan
View: Software Requirements, Second Edition (Pro-Best Practices) (Paperback)
