Top critical review
This book is cumbersome, lacks quality writing, and is nearly void of illustrations.
Reviewed in the United States on September 2, 2012
First off, I am a professor and teach systems engineering. I bought/acquired both a hard copy and a soft Kindle copy of this text book and made it the required text for my course. I bought the Kindle version so I could cut and paste items into briefing slides for use in class presentation materials. When I got half way through the text, I got a notice that I exceeded the copy limit the publisher had set up. If you want to cut and paste material out of the text, don't buy a Kindle version of it since you will be prohibited from doing so.
The first half to the text is cumbersome. The author defines his own unique phases for his own unique life cycle model and breaks out the conceptual design phase into 3 phases and grudgingly goes through all the typical system engineering tasks in each phase. The result is he doesn't release a top-level requirements spec until the last page of chapter 8. Once you get through the first eight chapters, the layout improves and there is some pretty good content in the second half of the book. Throughout the entire book, however, there are relatively few figures or illustrations, and the ones that are presented are fairly basic.
Overall, this text doesn't measure up to the system engineering works offered by Blanchard, or by Eisner's book on Project and Systems Engineering Management. Both Blanchard and Eisner write much more persuasively, and they both fill their works with worthwhile figures that help illustrate system engineering topics. After all, a picture is worth a thousand words.