Software Requirements, Second Edition (Pro-Best Practices) (Paperback)

by Karl E. Wiegers (Author) "If you've ever been on the customer side of a conversation like this, you know how frustrating it is to use a software product that..." (more)
Key Phrases: dialog map, elicitation workshops, proposed requirements changes, Chemical Tracking System, Next Steps, Graphics Engine (more...)

Editorial Reviews

Amazon.com
"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.

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 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

Topics covered: software requirements specifications (SRS); business and user requirements; risk management; the requirements process; sample documents and templates; requirements development: elicitation, analysis, specification, and verification; rights and responsibilities for software customers; best practices; project management tips; process assessment and improvement; types of users; product champions; use cases and other diagrams; tips for prototyping; managing requirements change; change centered boards (CCBs); evaluating and using requirements tools; requirements traceability matrix; impact analysis. --This text refers to an out of print or unavailable edition of this title.

Product Description
Have you ever delivered software that satisfied all the project specifications - and seemingly none of the customer's expectations? As a customer, do you find yourself guessing exactly what kind of information developers need from you? Without formal, ver

See all Editorial Reviews

• Paperback: 544 pages
• Publisher: Microsoft Press; 2 Sub edition (March 26, 2003)
• Language: English
• ISBN-10: 0735618798
• ISBN-13: 978-0735618794
• Product Dimensions: 9 x 7.3 x 1.4 inches
• Shipping Weight: 2.2 pounds (View shipping rates and policies)
• Average Customer Review: