Rating: 
Summary: Such a RARE and excellent Book.
Review: 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.
Rating: 
Summary: An enlightening read that jumps around quite a bit
Review: Let's face it, writing a book about software requirements is tough. Michael Jackson does a great job here exposing the core disciplines, the historical growth of the process and introduces some great approaches to the probem space (notably his Problem Frames). The book is succinct, to the point and written in language that just about anyone can follow. The Predicate Logic sections are the only areas where he assumes any prior knowedge with regards to following the notation. The only reason I gave this book four out of five stars is becuase the author got too cute with the structure of the book. The chapters are listed in alphabetical order based on chapter title. The book is presented as a "Lexicon" so I'm sure this was why the book was ordered in this way. Still there where many chapters that, in my opinion would have been more powerful if they had been grouped together. This is not a good enough reason not to buy read and enjoy this book. I strongly urge anyone interested in the topic to do so. I just wish an editor had taken the time to encourage Jackson to create sub sections .
Rating:
Summary: The best book of s/w requirements ever read
Review: Many thanks to Michael Jackson. His book is full of wisdom and insights. I just wonder why there is only one more book (Practical software requirements - as far as I know) so far on this topic since Michael published his book 5 years ago. I am looking forward to further elaboration of his approach by Michael or other writers.
Rating:
Summary: The best book of s/w requirements ever read
Review: Many thanks to Michael Jackson. His book is full of wisdom and insights. I just wonder why there is only one more book (Practical software requirements - as far as I know) so far on this topic since Michael published his book 5 years ago. I am looking forward to further elaboration of his approach by Michael or other writers.
Rating:
Summary: Brilliance (Jane-style)
Review: Published in 1995 but showing hardly any age. No methodology can substitute for clear thinking, and Jackson has produced a detailed lexicon that speaks concisely (just over 200 pages) to his extensive experience in the field. His approach, focusing on the problem itself and providing verifiable requirements, rebukes the habit of writing ambiguous specifications that serve no purpose. I found every page to carry new insight -- this should be on the reading list for any analyst/programmer.
Rating:
Summary: Probably the best book on requirement analysis
Review: Thanks to Michael Jackson. This book gives excellent guides in performing requirement analysis. Strangely enough, there is only one book (as far as I know), "Practical Software requirements", explicitly applies and elaborates the principles presented in this book. So you can accompany this book with PSR. The latter gives you more practical examples. I am looking forward to more books on further treatment of control and connection problem frames and even new problem frames.
Rating:
Summary: Probably the best book on requirement analysis
Review: Thanks to Michael Jackson. This book gives excellent guides in performing requirement analysis. Strangely enough, there is only one book (as far as I know), "Practical Software requirements", explicitly applies and elaborates the principles presented in this book. So you can accompany this book with PSR. The latter gives you more practical examples. I am looking forward to more books on further treatment of control and connection problem frames and even new problem frames.
Rating:
Summary: Useful Lexicon
Review: This book approaches to attack the essence of Software Construction rather the accidents. It is arranged as a lexicon(dictionary) so browsing for a specific topic is simple. It also provides a nice vocabulary for specifying software systems. Main themes seem to be: 0. People who make software should become good at describing the domain, the domain-system boundary and the system itself. Talks about partial descriptions, multiple descriptions etc. 1. Strong problem focus. Knowing what to solve is more important than how to solve the wrong problem. All in all well worth for the language, insights and original content.
| 
