Goodreads helps you keep track of books you want to read.
Start by marking “Software Requirements: Practical Techniques for Gathering and Managing Requirements Throughout the Product Development Cycle” as Want to Read:
Software Requirements: Practical Techniques for Gathering and Managing Requirements Throughout the Product Development Cycle
Enlarge cover
Rate this book
Clear rating
Open Preview

Software Requirements: Practical Techniques for Gathering and Managing Requirements Throughout the Product Development Cycle

3.97  ·  Rating Details ·  305 Ratings  ·  21 Reviews

Without formal, verifiable software requirementsand an effective system for managing themthe programs that developers think they’ve agreed to build often will not be the same products their customers are expecting. In SOFTWARE REQUIREMENTS, Second Edition, requirements engineering authority Karl Wiegers amplifies the best practices presented in his original award-winning

Paperback, Second Edition, 516 pages
Published March 8th 2003 by Microsoft Press (first published January 1st 1999)
More Details... edit details

Friend Reviews

To see what your friends thought of this book, please sign up.

Community Reviews

(showing 1-30 of 996)
filter  |  sort: default (?)  |  Rating Details
Preston Ray
Feb 24, 2012 Preston Ray rated it it was amazing
Recommends it for: Business Analysts, Requirements Analysts, Software Developers
Been a BA for about 20 years. Best book on this topic I have read.
If I was teaching a class on the documentation artifacts that a BA uses in a typical waterfall style SDLC this would be THE book. If you are not looking for that topic in particular this book might be a 4(or possibly even 3) stars.

First the good things.
- Excellent discussion and overview of all the major requiremetns documentation artifacts that are used today.
- Covers not only the documents but tries to also cover the "why" behi
Alexander Lisitsyn
Actually I'm not a SA and can rate this book just from developer's position.
This book fully covers the topic of requirements analysis and helped me to delve into this step of software development lifecycle.
The books is very easy and interesting to read, most of chapters starts with real life story that helps you to understand a problem and than author gives you a possible solutions.
Of course applicability of given solutions, approaches and patterns depends on your project size and developments
Roman Kot
May 29, 2015 Roman Kot rated it it was amazing
Great choice as your first in BA
Apr 07, 2013 Pēteris rated it liked it
Easy to read. Not at all boring.
Andrey Kuznetsov
Apr 04, 2016 Andrey Kuznetsov rated it it was ok
От книги ожидал большего. Тяжеловато читается. Профессия аналитика позиционирована как сложная и ответственная.

На самом деле суть аналитика - в особой форме мышления. Плюс ответственность. Этого достаточно. По опыту. Всё просто и это далеко не самая сложная профессия, к тому же интересная.

В конце книги приведены примеры документов Vision и SRS - довольно полезные. Нашёл несколько фишек для себя.
May 21, 2014 Vicky rated it liked it
I only got to read part of this while writing some requirements for a current project at work. I really would have preferred some more specific examples, and I tried skimming/flipping looking to see if they existed elsewhere in the book, but I wasn't able to find what I needed.
Dec 29, 2014 Norm rated it really liked it
I took this out of the library and then bought a copy for my office. It has been a great guide over the years.
Marcos Moret
Mar 26, 2016 Marcos Moret rated it liked it
Easy-to-read, practical guide to requirements gathering and management.
Aug 01, 2016 Assem rated it really liked it  ·  review of another edition
обязателен к прочтению для бизнес-аналитиков
Dec 25, 2013 Pete rated it really liked it
Worth reading. The book does a good job of capturing the method, process and content of requirements capture. One area I would expand upon is agreement and consensus. Requirements have to be captured and as part of this process we have to build consensus and agreement around them. If you are looking for an excellent reference on requirements capture - this is a good source.
Michael Ryan
Aug 30, 2013 Michael Ryan rated it it was amazing
Karl Weigers is the accepted master when it comes to requirements definition. This book adds to his first by covering the process of requirements gathering and all the detail of quality analysis and specification. It is a craft that is easy to do badly but difficult and demanding to do well. This book is a valuable addition to the practice.
Richard Hamilton
An excellent book on requirements development and management. Read the book from cover to cover and have a thorough understanding of the Requirements Engineering process.
Kronik kronik
Mar 26, 2010 Kronik kronik rated it really liked it
Readers of this book will find very good theoretical knowledge with combination of good examples. It is also a practical guidance.
Jan 05, 2016 Vadim rated it liked it
Pretty good, many interesting topics covered, even risk management to some extent.
But I'd prefer it to be more laconic.
TK Keanini
Apr 07, 2007 TK Keanini rated it it was amazing
Recommends it for: Product Managers
If you design, implement, or a part of a software development lifecycle, this is a must read book.

Lori Grant
Mar 29, 2013 Lori Grant rated it really liked it  ·  review of another edition
A should-read book on product management for knowledge workers and entrepreneurs.
May 10, 2012 Peter rated it it was amazing
Essential guide for any Analyst and Project Manager. A definitive must read.
Rejeev Divakaran
Aug 22, 2015 Rejeev Divakaran rated it it was amazing
Shelves: programming
Must read for all business analysts and architects
Mohammad Abu-Ali
Jun 27, 2011 Mohammad Abu-Ali rated it really liked it
As a software developer it was beneficial for me.
Oct 18, 2011 Laucisija rated it it was amazing
Good book for software requiments
Robert is currently reading it
Sep 26, 2016
GRZEGORZ marked it as to-read
Sep 25, 2016
Elena Vladimirova
Elena Vladimirova marked it as to-read
Sep 25, 2016
Nataliia Chausova
Nataliia Chausova marked it as to-read
Sep 25, 2016
Omar Espinosa
Omar Espinosa marked it as to-read
Sep 24, 2016
Sergey Kochergan
Sergey Kochergan marked it as to-read
Sep 19, 2016
Pavel Abradushkin
Pavel Abradushkin is currently reading it
Sep 14, 2016
Aliah marked it as to-read
Sep 14, 2016
Raheel Imtiaz
Raheel Imtiaz marked it as to-read
Sep 13, 2016
« previous 1 3 4 5 6 7 8 9 33 34 next »
There are no discussion topics on this book yet. Be the first to start one »
  • Mastering the Requirements Process
  • Writing Effective Use Cases
  • Software Estimation: Demystifying the Black Art
  • User Stories Applied: For Agile Software Development
  • Waltzing with Bears: Managing Risk on Software Projects
  • UML Distilled: A Brief Guide to the Standard Object Modeling Language
  • The Business Analyst's Handbook
  • Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise
  • The Best Software Writing I
  • Writing Solid Code
  • Coder to Developer: Tools and Strategies for Delivering Your Software
  • Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development
  • Software Architecture in Practice
  • Writing Secure Code
  • Eric Sink on the Business of Software
  • A Guide to the Business Analysis Body of Knowledge
  • Ship It!
  • Exploring Requirements: Quality Before Design

Goodreads is hiring!

If you like books and love to build cool products, we may be looking for you.
Learn more »

Share This Book

“If possible, quantify the contribution the feature makes towards the business objectives, so that people can make scoping decisions on the basis of facts rather than emotions ([ref013]). Will a specific feature contribute roughly $1,000, $100,000, or $1,000,000 toward a business objective? When an executive requests a new feature that he thought of over the weekend, you can use quantitative analysis to help determine if adding it is the right business decision.” 0 likes
“Assign someone who isn’t actively participating in the discussion to be the scribe, responsible for taking accurate notes. Session notes should contain an attendee list, invitees who did not attend, decisions made, actions to be taken and who is responsible for each, outstanding issues, and the high points of key discussions.” 0 likes
More quotes…