Best description of trying to capture requirements I have ever read. Spot on. Lots of very good ideas on how to minimize the risk of software development. ( )

I was recently exposed to the concept of "Wicked Problems" through my systems engineering work, so I purchased this book for background.

I can see how this was a ground breaking book at the time it was published, almost 25 years ago. Since then, many of the concepts that it was proposing have indeed become commonplace.

So, for us current readers, the book seems a bit dated, but it is wonderful to see where the concepts of modern software engineering hailed from, and what the challenges for change were perceived at the time.

Worth reading, but perhaps purchasing a gently used copy (as I did) makes the value even better. ( )

.
.
Contents
Illustrations
Introduction
1. Software Engineering And Science
2. A Personal View Of The "State Of The Art" In Programming
3. The Waterfall Model
4. Problems With The Waterfall Model
5. Whirlpools, Incrementals, And Spirals....
6. Prototyping
7. The All-At-Once Model
8. Other Models
9. Professionalism And Science
Bibliography
Index ( )