Software Requirements (Dv-Best Practices) [Englisch] [Taschenbuch]

"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' 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 common-sense 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 fail to comprehend 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 here cover negotiating difficult steps in the process, particularly how to manage shifting requirements as projects move forward and keeping the various users and stakeholders contented 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 organisation.

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 centred boards (CCBs), evaluating and using requirements tools, requirements traceability matrix, impact analysis.

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

Concise, readable, and expert advice for collecting and analyzing software requirements. Wiegers presents a palette of best practices for collecting, validating and managing software requirements, together with examples of their successful application to real-world projects. This is one of the few pragmatic resources on this topic.

A practical guide to improving your requirements processes
Many software development organizations struggle to gather, document, and manage the requirements for their information systems or commercial products. Even fast-moving projects need a clear understanding of what they're supposed to deliver; otherwise, they might move fast at first, but they can bog down in lengthy rework and extensive modification. Slighting the requirements process typically leads to cost and schedule overruns, disappointed customers, and tired, frustrated developers.

After seeing the common problems that plague many projects, I wrote this book to help business analysts, software developers, managers, and customers do a better job on these critical project activities. I describe several dozen "good practices" for requirements elicitation, analysis, specification, verification, and management. These methods are practical and effective, not cool theoretical concepts. I've used the methods myself and have seen others use them as well. I've illustrated the techniques with examples drawn from my own experiences and those of my consulting clients, and from a sample project that threads throughout the entire book. Typical discussions that take place among project participants also illustrate some common requirements-related situations. I've addressed important some topics that don't often appear in books on requirements, including defining the product's vision and scope, crafting a collaborative customer-developer partnership, prioritizing requirements, and analyzing the impact of proposed requirements changes.

Requirements, and hence software success, are about communication. Sustained software success relies on process improvement, applying new methods that lead to better results. Although there aren't any magic solutions or silver bullets, thoughtfully applying the practices in this book can help any project reach its objectives.