Rating: 
Summary: One of the best
Review: As an author myself of a competing requirements book, you might expect me to pan this one. But, no, I must admit that this is one of the bext requirements books ever written. It is quite obvious that these two authors have actually lived and breathed software requirements for many, many years. The book is chock full of real-life experiences and practical advice. Unlike many other requirements books, this one covers the full breadth of classical requirements management, including both elicitation and specification. It is not a religious piece (I mean that as a compliment) in that it does not preach any single "best" way to do anything. Instead, it offers the readers a wide range of choices: brainstorming, storyboarding, use cases, prototyping, and so on. If you are writing requirements, you need to read this book. Alan M. Davis
Rating:
Summary: A great read on a difficult topic
Review: As an experienced Software Engineer the last thing I wanted to read was another book about "structured methodologies". Typically, these books are 1) hard to read and 2) frustrating to apply to real-life software development. Dean Leffingwell has addressed both of these problems in "Managing Software Requirements: A Unified Approach". The writing is enjoyable and easy to digest. You can read it from start to finish without getting lost in academic discussions. In addition to being well written, this book addresses many of the issues we face in software development from a practical viewpoint. Leffingwell stresses how requirements should be a living part of the development lifecycle (in contrast to the common practice of gathering and documenting requirements, then putting them on a shelf.) While it does not provide a cookbook recipe for the software development lifecycle, this book does show us how different projects require different approaches, giving some realistic examples. And it doesn't gloss over the fact that gathering requirements can be just plain hard. This is a big and meaty book. It goes into great depth but doesn't stall out. Less technical users won't understand all of it, but will get a solid overview of the importance of requirements management. Developers will get insight into the current thinking by some of the industry leaders in requirements management and software engineering. Skeptics who are tired of the unfulfilled promises of structured methodologies will see that real progress is being made in the field of software engineering.
Rating:
Summary: A great read on a difficult topic
Review: As an experienced Software Engineer the last thing I wanted to read was another book about "structured methodologies". Typically, these books are 1) hard to read and 2) frustrating to apply to real-life software development. Dean Leffingwell has addressed both of these problems in "Managing Software Requirements: A Unified Approach". The writing is enjoyable and easy to digest. You can read it from start to finish without getting lost in academic discussions. In addition to being well written, this book addresses many of the issues we face in software development from a practical viewpoint. Leffingwell stresses how requirements should be a living part of the development lifecycle (in contrast to the common practice of gathering and documenting requirements, then putting them on a shelf.) While it does not provide a cookbook recipe for the software development lifecycle, this book does show us how different projects require different approaches, giving some realistic examples. And it doesn't gloss over the fact that gathering requirements can be just plain hard. This is a big and meaty book. It goes into great depth but doesn't stall out. Less technical users won't understand all of it, but will get a solid overview of the importance of requirements management. Developers will get insight into the current thinking by some of the industry leaders in requirements management and software engineering. Skeptics who are tired of the unfulfilled promises of structured methodologies will see that real progress is being made in the field of software engineering.
Rating:
Summary: An excellent addition to your bookshelf!
Review: First of all, let's get to the point. If you are serious about Software Engineering this book belongs on your bookshelf. It covers the full range of topics relating to Requirements Management, from 'Defining the Problem' to 'Managing Your Customer' to 'Managing Change.' There is enough information in here to make your brain hurt, but it is presented well - with many diagrams, stories, and a conversational tone. The book focuses on large team development of large systems, but the concepts will be useful to anyone who has to manage interactions between Developers, Customers, and Users. This book is a logical, systematic, and thorough description of the current 'state of the art' for Requirements Management, defined as ''a systematic approach to eliciting, organizing, and documenting the requirements of the system, and a process that establishes and maintains agreement between the customer and the project team on the changing requirements of the system.'' It divides the discipline into six team skills, each with its own goals, concepts, and techniques.
- Analyzing the Problem: understanding the problem that needs to be solved.
- Understanding User Needs: eliciting requirements from Users and other Stakeholders.
- Defining the System: organizing and documenting the user's requirements.
- Managing Scope: keeping the workload under control.
- Refining the System Definition: converting the user's requirements to design inputs.
- Building the Right System: implementing, verifying, and validating the system.
Finally, the authors provide a four-page recipe for getting started in your organization. This book is well worth buying.
Rating: 
Summary: A pleasant overview on requirements
Review: First of all, this book is rather pleasant to read and give a good overview on different skillness needed for Software Requirements. I especially appreciate the 3 layer approach for requirements and the good description of the Vision document. On the other hand, true and effective guidelines are often missing for each technique used, and the book often stay on the description level. I personnaly prefer the Robertson's "Mastering the requirements process" which give a more strong process plan and guidelines. Nevertheless, it's not a useless reading.
Rating:
Summary: A bit much
Review: I bought this book sight unseen, after it was recommended by the local computer society. The organisation I work for now builds medium-size community based web-portal applications. Speed of delivery is important. So in my current situation, a light-weight process works better. This book is probably better suited to developing teams in large corporate or government organisations. It is well written, well thought out, but just a bit too much for me. I found the templates in the back useful, but haven't read the book page for page. I might keep it as a reference for when I consult with large organisations.
Rating:
Summary: Anyone involved with developing software - read this book
Review: I have survived many approaches to "capturing" a system design over the last 22 years. This book, however, lays out a tactical plan that can be used to flush out design issues up front, where the seeds of larger design problems start. There are several references to "Quality Before Design", and this book extends those ideas into a very tangible process of requirements management. The authors were working with these ideas before the Rational system was developed, and the book ties together its approach with the Capability Maturity model and the Rational Unified process at the very end of the book. The book is very clearly written, and organized to build upon earlier concepts and help the reader take the ideas from concept to practice.
Rating:
Summary: Anyone involved with developing software - read this book
Review: I have survived many approaches to "capturing" a system design over the last 22 years. This book, however, lays out a tactical plan that can be used to flush out design issues up front, where the seeds of larger design problems start. There are several references to "Quality Before Design", and this book extends those ideas into a very tangible process of requirements management. The authors were working with these ideas before the Rational system was developed, and the book ties together its approach with the Capability Maturity model and the Rational Unified process at the very end of the book. The book is very clearly written, and organized to build upon earlier concepts and help the reader take the ideas from concept to practice.
Rating:
Summary: Outstanding
Review: I previously wrote a positive review, and said the only thing that would make the book better is if they'd elaborated on the case study in an appendix. This is a mea culpa: The full Vision document and other artifacts ARE in the appendicies - I just hadn't taken the time to look. Great book. If you're involved with software development, this is must reading.
Rating:
Summary: Every IT analyst and software consultant should read this
Review: Managing Software Requirements gives a true-to-life overview of the problems and pitfalls inherent in getting business people and software people to speak a common language. The first six chapters leverage the authors' combined 40+ years of experience in solving business problems with software. Their insight is keen. Their advice is practical. The section on understanding user needs, though a bit shallow at times, gives the consultant a useful collection of tools to help elicit issues from business people who have trouble expressing them. The section on managing scope should be read by everyone who hands projects over to software development teams. These four chapters give more useful information in 38 pages than most books give in 400 pages. I was disappointed in the light treatment of use case methodology. However, the broad overview of involving consultants in the software analysis and design process is priceless. Anyone implementing the Rational Unified Process or similar iterative design method would find this work timely and pragmatic. This is a must read for development managers, project coordinators, business analysts, and even architecture and planning administrators.
| 
