Review of 'Software requirements & specifications' on 'Goodreads'
4 stars
I don't remember how I discovered this book. Maybe it was through Bentley's "Programming Pearls". In any case, it's not one of the books that show up in those "Top N books every programmer must read"--what is is with list makers and imperatives anyway? But it is a good book. And you'll get a lot out of it if you read it. At least I did.
The book's format means you can read it in leisurely sittings (but don't forget about ACTIVE READING). And you can pick and choose which parts you find most interesting. But it helps if you treat this book as a graph, and read a whole path at a time. There are a few in the introduction.
Despite the author's idiosyncratic terminology, the lexicon entries are full of insightsful and useful suggestions. I honestly don't think I picked up on everything, but the few main ideas …
I don't remember how I discovered this book. Maybe it was through Bentley's "Programming Pearls". In any case, it's not one of the books that show up in those "Top N books every programmer must read"--what is is with list makers and imperatives anyway? But it is a good book. And you'll get a lot out of it if you read it. At least I did.
The book's format means you can read it in leisurely sittings (but don't forget about ACTIVE READING). And you can pick and choose which parts you find most interesting. But it helps if you treat this book as a graph, and read a whole path at a time. There are a few in the introduction.
Despite the author's idiosyncratic terminology, the lexicon entries are full of insightsful and useful suggestions. I honestly don't think I picked up on everything, but the few main ideas that come up again and again stuck with me, and I'll try to apply them in my day to day practice.
