1 comments about All-Weather Surfaces for Horses.

1. This book raises several important questions for those planning to build a training area for horses. Unfortunately, it's also an advert for the authors own brand of surface material for said training areas. It's also heavily focussed on english conditions, with its chalk geography. Finally, the type of all-weather surface planned in this book is of the expensive type. There are cheaper methods, though not as good.
   
   If these conditions don't put you off you will find it an excellent book.
   
   I had already aquired most of the information I needed from other, free sources, but found the book a good summary which also confirmed many of the thoughts I had already had on training surfaces.
   
   Summary: Worth it if your conditions matches those described in the book.

5 comments about Functional Verification Coverage Measurement and Analysis.

1. I must admit only reading the first few chapters, as all I am interested in is functional coverage. I will some day read the rest of the book (I hope).
   
   Commenting on the parts that I did read so far - I found this book an excellent learning tool. I had to learn how to write functional coverage in e, and this book was very valuable in getting me started, both with basic concepts, as well as examples. The example involving the wood stove is excellent. Unlike the documentation available from (Cadence), which is highly fragmented, Andy Piziali did an excellent job providing examples of complete - start - to -finish solutions.



2. In his forward to Piziali's book, Harry Foster, of Jasper Design Automation, says that this is "the first book to introduce a useful taxonomy for coverage metric classification." I agree that "useful taxonomy" describes this book well. I think it would be hard to find a more clear and complete introduction to functional verification coverage concepts and methods.
   
   As an added bonus, this book is a good read. Piziali has a passion for verification coverage and a passion for language. The result is prose that not only is clean and easy to follow, but that also infects you with the excitement Piziali feels for his subject.



3. This book covers features of related tools extensively without talking about specific tools.
   
   Before buying this book, it is a good idea to read the discussion between the author and others at http://verificationguild.com/modules.php?name=Forums&file=viewtopic&p=185#185 if you are interested in using coverage measurement. There, none of the experts were able to address the following question:
   
   Coverage tools are often used to set goals for simulation efforts. The flexible functional coverage allows such goals to be set too high or too low. Has any user made such mistakes? What can people do to get back on track quickly when the goals are too ambitious or too conservative?
   
   This book also suggests using functional coverage for setting goals for simulation, but it also avoids the above question. The recent answers from some other authors are available:
   
   Authors of http://www.research.ibm.com/journal/rd/494/victor.html set the coverage goals conservatively and assure each coverage point got hit many times.
   
   A.Adir, H.Azatchi, E.Bin, O.Peled, and K.Shoikhet of "A generic micro-architectural test plan approach for microprocessor verification" in Proceedings of the 42nd Design Automation Conference (paper 47.1 from www.dac.com) suggested setting functional coverage goals according to project budgets.
   
   Peet James' book (ISBN: 1402076193) seems to recommend using functional coverage but not to use it for setting goals.
   
   Andreas Meyer's book (ISBN: 0750676175) provides an option to avoid using coverage because it can be too much work to explain the coverage data.
   
   After reading some of the above, it can be easier to decide how useful this book is.



4. First, this book is short for the price, it only weighs in at 135 pages, excluding a unnecessary BNF description of the "e" language, and the more useful definitions. Furthermore, the book wasn't typeset well, it has widow and orphan lines all over - while this probably won't bother most, I find it jarring to my reading.
   
   I'm somewhat familiar with coverage analysis, but no expert. I think the book serves as a OK introduction to the subject, but I found it wanting in concrete suggestions. When should I choose one technique over another? What coverage methods uncover the most bugs? Can I expect to get 100% line coverage? How do I make expression coverage more valuable and reduce false negatives? I'd like statistics, more what-to-do when, and more coverage of recent techniques based on PSL/OVL assertions - currently limited to two pages.
   
   To summarize, it lacks the detail I'd want to make it worth the price. If you desire an introduction to coverage, I think you are better off with a recent book on general verification tecniques.



5. In the field of functional verification, coverage has been traditionally seen as a luxury activity which is done if time permits (and we all know what that means !). In recent years, along with the exponential growth of design complexity, this situation has drastically changed. Coverage is now typically a mandatory part of the verification process. However, in most cases, it is still effectuated in an ad-hoc manner, since there is no agreed upon methodology in this field yet. Andy's book comes in time to fill this gap.
   
   The book's content spans from the basics of functional verification and functional coverage up to state of the art topics such as coverage-driven verification and usage of Hybrid models to improve coverage fidelity. In between, Andy reviews the different types of coverage, namely functional, code, and assertion coverage.
   
   There is no assumption of prior knowledge, and the concepts are very clearly articulated. Examples are mostly shown using the e language (Andy works for the late Verisity), but it is done in a generic manner which allows to implement the core ideas in any environment.

1 comments about Van Nostrand Reinhold manual of rendering with pen and ink (Van Nostrand Reinhold manuals).

1. 
   "'Rendering' is the reproduction or representation of an architect's design in the form of a drawing of the building as it will appear, complete with accessory details such as trees, traffic and people. It is also much used in preparing drawings for engineers, designers and manufacturers, and in advertising and industry generally. Mr. Gill has produced a concise, thorough and copiously illustrated guide to techniques and methods, including sections on perspective, projection, shadow, reflections, and on how to draw cars, ships, aircraft, trees, human figures and so on."

No comments about Building with Reclaimed Components and Materials: A Design Handbook for Reuse and Recycling.

No comments about AutoCAD 2006 Tutorial - Second Level: 3D Modeling.

2 comments about Mastering Autocad 3D.

1. I bought this book, because I tought it is good for learning AutoCad 3D. I have to say this is the second book I read from this Author. Authough not as boaring as the first one, this book may help you only if you have been working many years as an architect. But the biggest problem is that you have to type step by step commands and numbers all the time. Why you have to do the next step is never explain, so if you stop to follow the book and decide to do something on your onw, you can't do it.
   Another problem is that you can't save your work because the book comes with copywrite cd so if you want to stop and continue later you have 2 options: either never to turn off the program or to finish few chapters at once.
   So as a sumary I must say another Big, Bad and Boaring Book.



2. An excellent step-by-step approach to learning the fundamentals of AutoCad for the architect.

No comments about Architecture, Technology and Process.

No comments about Beginning AutoCAD 2000.

No comments about Mississippi Valley Architecture: Houses of the Lower Mississippi Valley.

No comments about AutoCAD LT 2000 Fundamentals and Applications.