Customer Rating: 
Summary: It is a lexicon
Comment: This book needs structure. Themas are alphabetically sorted, but are not organized according their semantical contents.
The following sentence from "Jules Henri Poincare" may be the best description for this book:
Science is built up of facts as a house is built of stones, BUT an accumulation of facts is no more a science than a heap of stones is a house.
This book gives you all ingredients, but does not tell you how to be a good cook. It does not give you the aim.
Problems are isolated, but not related. They are just sorted in alpabetical order without context, like the heap of stones...
Customer Rating:
Summary: Not what I expected
Comment: I bought this book based on the rave reviews listed here. I was looking for insights into the requirements specifications process based on case studies, experience, etc. The topics discussed are very abstract, and the organization of the book (in alphabetical order of topics) contributed to this abstraction. One of the topics I found extremely interesting throughout the book was the use of mathematical notation to accurately specify relationships and concepts. In my own software engineering consulting practice with Fortune 500 firms, the use of mathematical notation in requirements specifications, such as is used for mathematical and logical proofs, is rarely used, primarily because most users, stakeholders, and developers cannot read or understand mathematical notation with respect to logic! Nevertheless, the book's treatment of mathematical notation in software specifications is refreshing and a keen reminder that the purpose of requirements specifications is precision and to eliminate misinterpretations. If you are looking for a textbook that provides insights into the practice and successful techniques of requirements engineering through case studies and anecdotes, I recommend reading other texts that are aligned with methodologies and techniques such as UML, CRC, etc.
Customer Rating:
Summary: Such a RARE and excellent Book.
Comment: In Software Engineering, a book that is a good read is a rare find.Most books bore you to tears, so you are asleep before you learn anything.
Jackson's book is well written, interesting, and EXTREMELY informative. I strongly suggest ALL Software Developer's read this book.
Customer Rating:
Summary: "Problem Frames" expands on its themes
Comment: Folks who like this book (like me!) will want to know that Jackson has published a follow-on book in which he expands on the central themes of this book. The follow-on book is called "Problem Frames", and of course it is available on Amazon.
Customer Rating:
Summary: Technology Survival Manual
Comment: How many technologies have you survival from? How many do you think you still gonna live? The best tool to survival technology change is *discernment*. Jackson's book the is best source of discernment I know. His point of view about so many technologies and software engineering themes are enlightening. The book organization is also a plus: any subject has links to other corelated themes. I've been referencing this book for 3 years and it seems not to get old.
