Modeling

It is evident that the book must have been translated into English because of the frequent misuse of grammer. This English version of the book also contains too many textual errors. The bond graph novice will not find this book of any value because the large amount of errors beg the question as to whether what was written is an accurate representation of the bond graph methodology. The book is better suited for the person who understands bond graphs and can sift through any errors that might exist.

Note that I have not yet read enough of this book to provide a detailed review. I do feel obligated though to present information about the book that I feel is lacking.
1.This is a cookbook.
The authors (in the introduction) state that this book presents information as "recipes." So many different models are presented, but little is said about the reasons for picking particular models or the theoretical aspects of them. That being said, the book still can be useful since, presumably, the authors have surveyed the field of literature and picked out the "most useful" techniques for you. You can always follow the many references for further information.
2.Dated information in volume 1, and maybe volume 2.
Almost all of the references are pre-1990. They state that much of the information on this topic is "too mathematical." So I guess that's why they stick to the oldies.

This is a good book for the total beginner. You do not need any experience with any cad software.
For the more experience users this book takes about 2 hours to read through and it covers the basics. But that is all.
It does not cover anything more complex than drawing simple shapes. It does not cover references or relations at all.
You will most likely need to buy another more comprehensive book.

Storm Personal Version 3.0 is one of a nearly extinct species of programs: DOS. It defies logic that Prentice Hall and Storm Software have not updated the format to Windows. At this point in time, they should be working on a Java version of the program. The book is written with the operation manager in mind, another rare and endangered species. The language is overly perky, "...Little else need be said, except so long and come back soon!" (pg. 44), and the examples are presented but not adequately explained for the newcomer. Perhaps my poor opinion of the book and diskette's format is a result of not being a member of its intended audience, the long-time operations manager or material scheduler. I would hypothesize that the main population of the audience is not the professional manager, but rather the newly introduced student of the decision sciences. If this is the case, the publishers would do well to revise the focus of the book and format of the program.

This book may be of value if you are trying to get two Symbian devices to communicate. But if you need to communidate with another OS, it is sorely lacking.

The book leaves out very critical info on using RNetDatabase in order to be discovered. It also glosses over actual data exchange not realizing that RecvOneOrMore() is not supported on some devices.

As bad as the Symbian SDK documentation is, this book does nothing to add to it.

Don't waste your money.

This text does a rather poor job of introducing the student to system dynamics. I think Dorny does a disservice to the students by treating everything in the frequency domain. Unclear and poor layout.

This book gave me an understanding of the basics of Novell Netware 4.1. For the needs of running a Novell site on a daily basis, the book leaves you hanging. Not enough detail is provided on Novell utilities, their mentioned, but never explained how to use them.

The book attempts to present models usable for study of the complex TMDL problem which tries to separate the contribution of non-point to point sources to water quality in a water body. It indicates to some extent that in most cases the loadings to a water body are 60-80% non-point source, but the book only deals with reducing point sources-not how to clean up non-point sources.

The series of water quality models presented for use are very oversimplified for real applications and reviews by groups such as the WERF indicte that most of them are out of date in that they do not consider real water body hydrodynamics coupled with advanced water quality models.

A better starting place to overcome these deficienies would be the recent workbook published by American Society of Civil Engineers Press "Water Body Hydrodynamic and Water Quality Modeling" on Three dimensional water body modeling, and including an introductory 3D model on a CD ROM.

Don't waste your money on this book.

I have been purchased at least 3 books on lightwave and this is the only I regret.

This book is excellent for aspiring authors as it proves anybody can get a book published, even if you can't write and you have nothing of value to say. This is just about the only useful thing about this book.

This book is just as awful as every other title written by Mr. Mortier.

The really bad part is that someone at Charles River Media seems to think Mr. Mortier's books are worth publishing. Because of the pitiful nature of every one of this author's titles I've seen to date I am now very reluctant to purchase any Charles River published book. It's sad that a company with so many excellent titles would continue to publish such poor quality books by the same author.

If you're expecting anything along the lines of something that would be written by Tim Albee, Patrik Beck, or Dan Ablan you will be sadly disappointed. If you were looking for in-depth coverage of modeling in Lightwave keep looking, it's not in here.

Sadly, this book doesn't really give any help at all in modeling in Lightwave. Instead, it reads like a book written by a guy who simply opened the program and sat with the manual in his lap, writing down what he discovered. Nothing about modeling your own creations using the many tools available in the program.

The idea the Mortier doesn't actually know much about Lightwave is given credence by the amount of space given to programs that aren't Lightwave but that Mortier does know. Talking about Amapi and Poser doesn't give any information about Modeling in Lightwave, but it does fill space. We'll have to wait for a really good book specifically about Lightwave modeling. As for this one: AVOID!

This book is not difficult to understand. However, I find that this book's examples have too many errors. For example, in chapter 8, the examples given have errors. The result of the examples are not what I expected. It makes me feel whether my understanding is correct or not. Moreover, there is no author email address in this book. The reader cannot send comments to the author.

The book is good in the sense of the simplicity with which the author tries to explain and introduce the concepts. However, it is full of errors: I could not find one example without errors. Specially in Chapter 4, which introduces SQL, there are too many errors. That is unforgivable!! I think the author of this book did not even check what he was writing. I do not recommend this book to anyone until a serious revision of all the examples is perfomed!

I read this book to get some ideas for setting up a database with multiple servers in different countries. One requirement was high availability and fast response times under the condition of instable network connections. I am not a database expert, so I can not assess the accuracy and completeness of the material very well. The following is my view as a "novice" reader.

The book is divided into three parts: theory, distributed database architectures, and multi-database architectures. Part one introduces relational algebra, SQL, database models (hierarchical, network, relational), ER-diagrams and such. Part two concentrates on homogenous distributed database architectures. Part three is about heterogenous (e.g. mixed hierarchical/relational) distributed database systems.

The book is demonstratively well structured and easy to read. The author begins with a roadmap, and each chapter begins with a statement of purpose, a description what will follow and how this relates to the topic. I found part one to be a decent introduction to general database concepts. However, I had the impression that the book is too shallow overall. One of the more noticable omissions (to me) is in the part about deadlocks: the author concentrates entirely on deadlock detection, while deadlock avoidance and deadlock prevention are not even mentioned. I can't say if this is because the latter are not used in databases. Moreover, as another reader noted, the examples are full of errors, which is quite annoying.

Altogether, the book entirely failed to give me any hints for solving my problem. Data replication, which is probably the one technique that I need to apply under the circumstances described above, is mentioned in only one paragraph in the entire book. The author instead focuses entirely on database partitioning. If you need that, the book may be for you, although I assume there are better books on the subject. I do not recommend this book.