Product Description

Have you ever delivered software that satisfied all of the project specifications, but failed to meet any of the customers' expectations? Without formal, verifiable requirements--and a system for managing them--the result is often a gap between what developers think they're supposed to build and what customers think they're going to get. Too often, lessons about software requirements engineering processes are formal or academic, and not of value to real-world, professional development teams. In MORE ABOUT SOFTWARE REQUIREMENTS: THORNY ISSUES AND PRACTICAL ADVICE, the author of Software Requirements, Second Edition, describes even more practical techniques for gathering and managing the software requirements that help you meet project specifications and customer expectations. A leading speaker and consultant in the field of requirements engineering, Karl Wiegers takes questions raised by other professional software developers and analysts as a basis for the practical solutions and best practices offered in this guide. Succinct and immediately useful, this book is a must-have for developers and analysts.

Product Details

• Amazon Sales Rank: #117564 in Books
• Published on: 2006-01-17
• Original language: English
• Number of items: 1
• Binding: Paperback
• 224 pages

Features

• ISBN13: 9780735622678
• BUY WITH CONFIDENCE, Over one million books sold! 98% Positive feedback. Compare our books, prices and service to the competition. 100% Satisfaction Guaranteed
• Brand New from Publisher. No Remainder Mark.

From the Publisher
From the author of Software Requirements, Second Edition, this follow-up handbook answers real questions raised by professional software developers and business analysts. It tackles many tough issues about gathering and managing software requirements and offers expert guidance and real-world solutions.

Key Book Benefits:

-Delivers concise information that guides readers through difficult requirements issues -Provides thoughtful guidance based on the author’s extensive real-world application-development and consulting experiences -Features practical solutions and demonstrates best practices for software requirements engineering that can lead to fewer change orders, more satisfied customers, and lower development costs

About the Author
Karl E. Wiegers, Ph.D., is Principal Consultant with Process Impact, a software process consulting and education company in Portland, Oregon. Previously, he spent 18 years at Eastman Kodak Company, where he held positions as a photographic research scientist, a software applications developer, a software manager, and a software process and quality improvement leader. He has led process-improvement activities for small teams, for a division of 500 software engineers building Kodak’s digital imaging products, and for the Kodak Internet development group. His writing and teaching are based largely on his experience in improving development processes, technical practices, and quality practices in all these environments, as well as incorporating experiences drawn from his dozens of consulting clients. Karl is the author of three previous books, and he has written more than 160 articles on software engineering and management, chemistry, and military history during the past 30 years. He is a frequent speaker at software conferences, public seminars, and professional society meetings. As an independent consultant, Karl presents training seminars and consulting engagements at companies worldwide on requirements engineering, software peer reviews, process improvement, risk management, and related topics. He has worked with nearly 80 companies and government agencies in many different industry sectors since 1997.

Customer Reviews

It depends...
It was with high expectation that I picked up Karl Wiegers latest book on requirements. I had read the previous book, Software Requirements 2nd edition, and liked it. However, one of the people quoted on the back of the book had told me that Karl had rethought the role of use cases. Well, I wanted to see that. Also there was this whole subtitle of "Practical Advice". I wanted some of that too.
You see, I teach a requirements seminar and I almost always get asked the "Thorny Issues" Karl lists: How long does requirements take? How much detail is appropriate? What does a good requirement look like? What should be in the specification? My favorite is, "What should marketing put in their document and what should development put in theirs?" My answer always started with, "It depends..." and I wanted better answers.
The answers I got from the book were things like, "There are no fixed answers to the question. Multiple variables contribute to this issue." Or "There is no simple formulaic approach to software specification." Yep, it depends. Well, at least I agree with him.
Lest I sound a bit harsh, there is a lot of Practical Advice in here. There is a good primer on estimating from requirements and acknowledging the cone of uncertainty, the importance of customer input - even on agile projects, the role of specifications, and the need for text and models for a good specification. It is just that for me, I like to think that I already gave that advice to my clients. In fact, there were several sections in the book were I wondered if he had attended my class! (He hasn't.) Perhaps that is why I like his books, I think on the same wavelength.
Oh, about Karl's rethinking of Use Cases. Well, it turns out that Use Cases are not functional requirements but containers of functional requirements. And there are other, sometimes more appropriate, ways to capture functional requirements. Also, functional requirements should be specified outside of the Use Case. However, Karl still really, really likes Use Cases. So, Karl has done not so much of a rethinking of Use Cases but a clearer statement about the multiple variables that go into capturing requirements.
So, should you buy this book? Well if you are ready to accept that requirements are hard, that there is no one best way, that there are some better ways but it depends on where you are and the problem you are trying to solve, then this book will work for you. It has enough to guide you in the right direction. You still will have questions but those need to be worked out in your environment and culture. For those who want a cookie cutter approach to requirements and no ambiguity, it depends...

Right on target
This book is a very good addition to any software library. Chapter 15 (Elements of Requirements style) contains some really good and practical advise and is a perfect example of what makes this book great. It just seems to answer some questions that other books don't address and it does it in a very readable format.
It is not as complete as other books on requirements but it does not pretend to be complete. The title says "More about Software Requirements" and this is exactly what you get.
If you do not have another manual that covers the fundamental of software requirements you might want to get "Software Requirements 2nd Edition". Those two books together will give you a nice complete package.

Wiegers is the best, as always :)
Karl Wiegers is the person I recommend all my employees to read. This book is even better than 'Software Requirements, 2nd Edition' by Karl. He gives practical advises together with theory and important references. This book could be used as a tutorial for requirements engineers. One of the best books in this subject area.