Computer and Science Books

Great book! I've been working in transmission systems and networking for more than seven years now, and I've never found a book which had both subjects together. If your are planning to give some classes or seminars, this book is a very good outline and in-depth info source.

The book cover many important part about Data Comm.Useful for student and researcher.

I was very impressed with this vendor's service. The book was in great shape and got to me very quickly. Safe bet here.

This is one of the all-time best books on computer networking and data communications. The diagrams make it perhaps the simplest to understand, of all books. The style is lucid, plenty of examples are given and there are exercises after every chapter. Apart from Tanenbaum and Comer, this is a must for every serious student of data communications.

The book which is written by Behrouz is one of the greatest book I haven't read in my life. I preffered to read this book to all of the viewer's who want to gain some knowledge in data communication and network field.

Excerpt from review on bsmDigest.com:
"Mark Lutchen's groundbreaking book continues to influence technology leaders with its vision for building mature IT organizations. As more CIOs and CEOs grapple with the challenge of applying effective management processes to their increasingly critical technology organizations, this engaging book offers very practical advice for doing it successfully. Drawing on his experience both as an actual CIO managing a large, global IT organizations and as a management consultant working with many large organizations, Lutchen delivers a clear, integrated vision for enlightened IT management."

Great help for someone that has just upgraded
from IT Management to a CIO role and needed to
upgrade as well his agenda. Excellent source of inspiration
and perfect guide for a profession that is still
under transformation. Definitely a must have.

The book is focused (and written by) on world class CIO positions,
but I found it equally useful for smaller scale CIOs.
It's exactly there that it lacks some information
on the organization of smaller IT groups (<20 persons).

If you are a CIO then buy it. If you are an IT manager
you need something else.

In the fall of 2003, the Harvard Business Review published an article advancing the proposition that "IT doesn't matter." The article's author suggested that because IT was now a commodity, and everyone had it, it no longer conveyed any distinctive competitive advantage and therefore, strategically, did not matter. In fact, at many companies, IT doesn't matter as much as it should - not because it is a commodity that other companies also use, but because most companies don't get every potential benefit from their IT. To advance your business agenda effectively, make IT a real part of the business. Author Mark D. Lutchen shows managers, particularly CEOs and CIOs, why IT is not fully a part of business at the moment, and what it will take to turn IT into a competitive, strategic asset. We recommend this useful, well-written, clearly organized book to anyone whose job involves decisions on IT budgets, organization, investments or strategy.

This is a fabulous book for experienced or aspiring IT managers whose goal is to prepare for ascension through the ranks, especially to the CIO level. In simple yet rich language, Mark presents a clear picture of the future of the IT organization and the competencies needed in the CIO and senior team heading up this professional services operation. The examples and case studies are rich with insights. In short, this book is pragmatic and weighty, yet also highly readable and I dare say outright enjoyable. I highly recommend it as a must read for anyone who wants to develop an effective IT career roadmap. Thank you Mark Lutchen.

Joe Santana,
Co-author Manage IT

I have only one simple statement - where were you Mark when I started my IT career 17 years ago? Today I would have been a CIO! I highly recommend this book for those starting out their careers in IT as it gives a big picture look to the field. Own it and refer to the clear and relevant graphics in the book.

This is a GREAT reference book. You won't learn how to program Mathematica from it. You will learn an amazing amount about how Mathematica works by reading it. If you don't believe me, check out it's thorough explanation of cubic splines. It's better than the Mathematica Help. It also comes with the complete book which can be installed in the Mathematica help system.

There is, literally, a wealth of information to work with in this book.

I would also strongly recommend getting An Introduction to Programming with Mathematica, Third Edition. This is a first rate "course in a book" for programming.

There are other books which are good. Between these two books, you will have an amazing arsenal to work with!

Paul

I agree with many of the other reviewers - this book is great. I recently got Mathematica and found the imbedded Help browser a little cryptic at times. I purchased Mathematica Navigator after reading many of the reviews here. I haven't read the book from cover to cover, but instead use it as a reference after having read chapters 1 through 3.

I'm studying Matrix algebra, so I skipped to Chapter 18 and worked through the examples without any problem, save a small error on page 467 where an upper case P was typed in lower case.

Highly recommend for anyone wanting help making the most out of very powerful software.

Very well written and full of useful information to start learning Mathematica. It covers all the foundamentals.

I liked the first version so much that I bought this second edition also. The first edition was based on Mathematica 3 but this second edition is based on Mathematica 5 (Mathematica 6 has only just shipped within the past 2 months).

As did the first edition, this second edition comes with a cd that contains the entire book in Mathematica notebook form. The style sheets used to format the second edition cd notebooks are much cleaner looking than the first.

At anyrate, I definitely recommend the second edition even if you already have the first edition.

Mathematica is an excellent program, with good built-in and online documentation - although many feel the Documentation Centre in version 6 is not as good as the Help Browser in version 5.2. But sooner or later you will find a problem for which the official Mathematica documentation does not help. The program can then be very frustrating, as the syntax is complicated and error messages can be very cryptic. Help online is painfully slow, as the official resource, the news group comp.soft-sys.math.mathematica (Mathgroup), is moderated, so help requests have to be approved before they will appear. (The newsgroup sci.math.symbolic is sometimes helpful and since its not controlled by Wolfram Research, posts appear immediately). Hence Mathematica users will need one or more good books - more so than with other similar programs such as Maple or Matlab.

In addition to the book Mathematica Navigator by Ruskeepaa, I own several other books on Mathematica, including:
* The Mathematica Book, Fifth Edition by Stephen Wolfram
* The Mathematica Guidebook: Programming by Michael Trott.
* The Mathematica GuideBook for Symbolics (w/ DVD) by Michael Trott.
* Schaum's Outline of Mathematica by Eugene Don
* An Introduction to Programming with Mathematica, Third Edition by Paul Wellin
* Programming in Mathematica (3rd Edition) by Roman Maeder - I also own the first edition.
* The Beginners Guide to MathematicaRG, Version 4 by Jerry Glynn and Theordore Gray

plus a few more old books I've either had a very long time or bought very cheaply on Amazon.

Given the choice of only one book, I would choose Mathematica Navigator by Ruskeepaa. It comes with a CD-ROM which has the whole contents of the book, which may be integrated into Mathematica's help system. It's not unique in that respect, as so do Micheal Trott's Mathematica Guidebooks, but they have far too much irrelevant material in them. Ruskeepaa's book sticks to important facts about Mathematica. The book covers a wide range of topics. Sometimes I wish in more depth, but the book offers a good compromise between width and depth. In particular, the information on writing Mathematica programs is far too short, so its unlikely to satisfy someone wanting to write a major Mathematica package. For writing packages, Programming in Mathematica (3rd Edition) by Roman Maeder based on Mathematica 3 is arguably still the best, although Maeder's 1997 book is very old.

The only significant fault I can find of Ruskeepaa's book is its age. Mathematica 6 is a really major upgrade from 5 with many functions now built into the kernel which previously needed to be loaded from packages. Many functions or options have been deprecated. As such, some of the information is no longer accurate. But given at the time of writing (December 2007) there is no book on Mathematica 6 published, I think Ruskeepaa's book, which is based on version 5, is the best Mathematica users can get. However, if by the time you read this, someone has published a book on Mathematica 6, then it might be worth buying that instead.

I would have given this 5 stars, but it is getting a bit dated now.

Kishor's book is one of the few highly readable books on queueing
and stochastic processes. The abundant examples and discussions
of reliability also aid in understanding the material.
I would recommend this book to undergraduates and beginning
graduate students.

Second edition of "Probability and Statistics with Reliability, Queuing and Computer Science Applications" by Kishor S. Trivedi is a highly recommendable book. The concepts provided for probability theory and stochastic processes are excellent for students of communication, networking and computer science. It provides a good understanding of stochastic processes and Markov chains which are very relevant for students and teachers especially working in the speech processing area. I found the book and its contents very relevant and the examples provided could be very well related to networking and computer science, a unique aspect of this book. The students grasped the concepts well and found the problems very challenging and helpful in building up their concepts and knowledge. I had previously taught a number of other books and introduced this book last year at my University, I feel very satisfied and content with the decision of choosing this book for my students. All eleven chapters are equipped with excellent examples, problems and exercises broadening the reader's mind. The first 5 chapters constitute the probability theory while the rest of the chapters emphasize on stochastic processes very relevant to students of advanced networking and speech processing. Other books on probability and statistics usually lack an important aspect specially when used for computer science and telecommunication students. The examples and exercises not only make students learn and understand and probability and statistics concepts but also create its relevance to their very fields, therefore the book is an extremely precious gift from Prof. Trivedi specially for the students of computer science and telecommunication. An inexpensive Asian edition (paperback), a solution manual and powerpoint slides of each chapter are now available.

Prof. Trivedi has done a tremendous job in introducing topics of advanced research not found before; the students gained knowledge about the modern research environment and felt confident too. This book is not only recommended for beginners but also for professionals and engineers.

This book from Prof. K. Trivedi is another great guide for the novice student and the expert researcher for modeling tools and techniques. It builds upon neatly explained concepts of probability, queuing and stochastic processes to provide a variety of examples of applications. It is definitely a book that one has to keep at hand, as it contains recipes for a huge number of performance and dependability evaluation needs. Besides the rich content, the structure and the presentation are great: a bit of theory and soon one example from practical life, the reader never gets lost but he is rather brought step by step to a comprehensive understanding of the topics.

The "Probability and Statistics with Reliability, Queuing and Computer Science Applications - 2nd edition " by Kishor S. Trivedi is a valuable reference for students and professionals. Didactically organized the eleven chapters presents the core concepts of probability theory and stochastic processes in an accessible easy-to-understand approach. The rich set of examples and exercises, based on numerous computer science and engineering real world applications, allow the readers to build their knowledge gradually.
I would like to highlight the system reliability fundamentals covered and articulate with the remains topics.

A very useful book. A good choice for somebody who is just starting to get a feel of the subject, or someone who is looking to build a strong foundation in the area. The best feature of this book is its lucid language. There are many books in the market, which cover a lot of material but, for the average reader, are very difficult to understand. The example-based approach coupled with a comprehensive material coverage are additional selling points. I would highly recommend this book

Good book for beginner, if you are just learning get this book.There are things in this book that took me years to learn by trial and error unfortunaely for me I only learned a couple of new things, but it did give me some certainty in what I did know. However Im now looking for a intermediate book which is what I really needed.

The book lives up to its reputation as being a beginners guide. Good resource for those now getting into computers. And, it also has some good steps for Vista too.

Like most people,i avoided the 21st century technology by continuly saying to myself it was not something i needed.I finally took the plunge,a friend set up my Toshiba A2125 and found the"Absolute beginners guide on your web page.It,s format coinsides with my 73 year old mindset.Congradulations Michael Miller

This a great book for aquainting yourself with your computer. If you are new to the computer world as I was you will find this book very helpful in taking control of your computer instead of it controlling you. It covers both versions of Windows: XP & Vista. I would recommend it to anyone just starting out. I think it would be safe to say it could save you a lot of time in the longrun and maybe keep you from pulling your hair out!

I have been using a computer for many years and still did not understand all the task/programs I could have been using. This book has been extremely helpful working as a primer explaining everything very clearly and is still up to date with the Windows Vista. I would highly recommend this book.

I purchased Jain's "The Art of Computer Systems Performance Analysis" for a 3-month graduate course, and I must admit that, in retrospect, I was a bit daunted by its size upon receipt (we were to cover the entire text). Further, I had my doubts about the relevancy of the text in the current environment, given its age.

But I must say, both of these initial questions proved wholly unfounded.

I've never used a text quite like this one before; it is a significant departure from the standard engineering text that weighs heavily on the side of analytical proof and mathematical equations, while foregoing textual elaboration. On the contrary, this book adopts a conversational tone whereby the author develops all of the book's topics in great detail, relying on substantial insight and experience. Truly, a breath of fresh air.

There's such a richness about this text, that a careful read--while admittedly quite time-consuming--is bound to give the reader a sense that he has just become the beneficiary of a heck of a lot of wisdom.

All of this is not to say the text is overly-subjective; in fact, there is plenty of detailed analytical analysis. It is just to say that the book is different, and one that exudes quality communication: it reads more like a lecture than it does lecture notes.

So, back to my initial doubts. It turns out that the verbose depth of material which constitutes the book's 720 pages is really a foundation of its main qualities: it is a very readable and highly-detailed exploration of the art and the craft of performance analysis. And it's for that foundational reason that its age is irrelevant.

A solid book indeed. It has the right mixture of theory and practical cases well dealt with. The techinques must be tried for performance analysis and implemented in real time projects.

This old book is one of the most valued on my shelf. I was first exposed to it in a graduate class, and I have to say that the book is so good I was not aware that my professor was not a good instructor until I had him a second time in a class where the textbook was less than stellar. Don't judge the book by a quick perusal either. At first glance, especially if you are looking at Part I, it looks like one of those books on Six Sigma that will put you to sleep. In fact, the vast majority of the book is quite interesting.

Part II, "Measurement Techniques and Tools", are where things get interesting. The good part about this entire book is that it uses problems in the analysis of computer systems as the basis of presentation for all tools presented. The graphs are excellent, the mathematics are largely self-contained, and if algorithms are presented they are usually given in numbered steps and an actual computer program shown. This is one drawback of the book - it uses the ancient Simula language for its demonstration code. However, if you are familiar with C, Java, or any of the other mainstream procedural languages, you'll find that Simula looks like very readable pseudocode, so this should not be an obstacle to understanding.

Part III is a section dedicated entirely to probability theory and statistics. Starting with the simple definition of the mean, this handy section not only derives all of the statistics you need in this book, it talks about common mistakes made in applying them.

Part IV is about experimental design and analysis. Using the mathematics developed in part three this section talks about all aspects of designing a proper experiment for the measurement or simulation of a computer system, including common mistakes and the best choice for the size of your experiment.

Part V presents the key issues in simulation modeling. First it discusses simulation terminology, simulation design criteria, and stopping conditions. Random number generation is the subject of three chapters in reference to inputs to your simulation. Finally there is a chapter on the commonly used distributions such as Bernoulli, beta, binomial, etc. that talks specifically about random number generation algorithms for each of the distributions presented. What makes this section so valuable is that although you may have possibly seen the math before, more than likely you don't know the value of each kind of distribution. This section makes that issue clear in terms of modeling computer performance.

Part VI is on queuing models, and is probably the most difficult section in the book. Although it is one of the better written pieces I have read on queueing theory, it is not as easily grasped as previous sections based on reading the textbook alone. There are examples present, and the book does a good job of presenting "the big picture" as to the use of queueing theory in computer performance analysis, but you may need outside material to really grasp how to set up a queueing problem from a mathematical standpoint.

No other book I've found does such a good job of discussing all of the topics covered and clearly tying it into practical issues in measuring and monitoring system performance. I highly recommend it.

I'm a performance analyst. I couldn't do my job properly without this book. It really is that simple.

This is an absolute gem. I really think that this book must be read by every CS/EE engineer. Performance analysis is always something that comes as an afterthought and engineers think that some some "mathematical" guy called a perf analyst will stop by after the product is completed and analyze the product. This is def wrong. PA should be done at every stage of production.

This book has been written assuming a novice reader. Several parts of the book have to re-read to really understand what the author is trying to convey, but trust me you will really appreciate it.

I suggest reading the following parts of the book(in order):

Part I (whole)
Part II (4, 5, 6, browse {7,8}, 9, 10 ) 10 is cool stuff..impress your peers with this
Part III (whole) read, re-read, re-read till you have digested every line..worth it really!!!!
Part IV (whole) read, re-read, re-read till you have digested every line..worth it really!!!!
Part V : You can skip this if you are not into simulation.
Part VI : Not really that easy to follow. I suggest Gunter's book for this.

I had a good time reading through this reprint of Morris Morgan's 1893 translation of Xenophon's "The Art of Horsemanship" (350 BC). Unlike many of the other ancient Greek translations and authors, this one is very easy to read.

The text itself is fairly short and reads quickly, sprinkled with wisdom. After the text is another short portion from 1893, which talks about "The Greek Riding-Horse", based on Xenophon and all the other available sources. Additionally, the footnotes to the text are quite interesting--I read them, for the most part, en block after reading the text.

As the title implies, the text is a very hands-on, practical guide to "everything you need to know" about how to take care of and look good riding a horse, reading like a "Horsemanship for Dummies" book. If you're interested in Ancient Greece and horses, you've got to read this short "instruction manual", though if you're only interested in the ancients, it's still fun to breeze through this text, nevertheless.

If more people took the time to educate themselves about horses and horsemanship in general and Xenophone's book in particular, perhaps we not see so many "show horses" of various popular breeds so physically manipulated by in breeding for only one or two specific traits rather than breeding for the whole horse. What was true in Ancient Greece is truer still today - without good feet, balance in the body and common sense a horse is worthless. Bravo to Amazon for bringing us this excellent book dirt cheap!

The material in this book is thousands of years old but amazing in how modern the approach is to horsemanship. Most of Xenophon's advice is timely even today. It shows how little has changed over the centuries.

This is a must if you are passionate about horses. It is so clear and to the essential point that it is a pleasure to read.

Xenophon covers several aspects of horsemanship, from grooming, leading, and choosing a horse, to mounting, riding, and training a war mount. Very, very interesting to see what is still applicable today. While this isn't a "training" or even a "horse care book," its a great historical reference from those interested in how horses we cared for and trained 2000 years ago. However, for those looking for a story or a book to teach riding skills, I suggest you look elsewhere. Those interested in dressage will find this worth-while, as it is considered the oldest text on the subject.

Despite its title this book is an easy and entertaining read for a broad audience. While specifically written from the perspective of management of software projects, the book actually addresses management at large. It makes a concise case showing how dangerous and detrimental it is (to the successful outcome of large scale (software) projects that is, defined by the author as a "quality product on time and on budget") to separate technical leadership/management from personnel leadership/management, as so often mandated by many organizations. The "manager-architect," as termed by the author in his book, is key to success. Consequently not everybody can be up for this task, and only few who dare to try will succeed at it, as evidenced by the disconcerting fact that many "top level managers" manage nothing but major budgetary overruns (be they hidden or not), for which they are "held accountable" by society by being hailed as "America's Best Leaders." This book puts an end to such phoniness and provides especially the inexperienced/naive reader with a skill set to reveal/uncover such mismanagement and the individuals responsible.

The book is a true eye opener for aspiring and "want-to-be" managers alike. Also, having posters on "true leadership" pinned to the office wall does not magically inhale the ability of leadership into the office occupant. Leadership is an ability rather than a skill as clarified by the author. It is just like playing an instrument: it only gets you so far if you do not have it in you and practice every day. Chapter 12 "The Impact of Leadership on Software Development" should be read by any manager (aspiring, "want-to-be", or acting alike), and in particular by those who confuse management with suddenly having power over people. Moreover, management does not and should not mean "tenure" along the lines of "now I have made it, now I can relax" or "now I am in power." Rather the "Old Fritz" (Friedrich II, Prussian King) statement, simple yet true, comes to mind: "I am the first servant of the country" ("Ich bin der erste Diener meines Staates"), and serves as a good guide.

The author puts forth an interesting concept for true autonomy founded on the philosophical considerations of the human mind, upon which the AI-(IF-THEN-ELSE)-community will most likely have to choke. In doing so, the author outlines nicely the profound difference between automation and autonomy, two terms, which are often confused, intermixed, or misunderstood, even by so-called experts in the field.

If management is done right, as exemplified/laid out in this book and practiced by its author in an exemplary fashion, managers would rather have to be pitied because of their huge added responsibility for their people/troops and the projects they manage/lead (in that order!). Special attention should be paid throughout the book and in particular throughout Chapter 12 to the "Machiavellian Prince," as this kind of "leader" unfortunately exists (and not in small numbers!), and, while striving only for personal power and gain, causes a lot of damage to otherwise noble causes.

The author of this book has deep insights and wisdom for any level of interface with computer science applications. You simply cannot go wrong for putting your weight down on patterns to follow from someone who has had success in the field. The techniques in this book go beyond basic head knowledge, into the live action of software development where the rubber meets the road. Only an experienced person can give these insights. I am very impressed with the advanced mapping, made simple. This book seems to be written for people who are looking to find answers to every day problems in a rapidly moving computer world, without fear.

Mr. deGyurky gives a great overview of his experience at JPL in organizing and developing large, complex, software systems, and delivering them on schedule, on cost. Mr. deGyurky demonstrated that the most important contribution to software management is that of leadership in life, carries over in software development also.

If you are thinking of becoming a manager of a software development project, you should check this book out, and You will be a step ahead of the game!

The author has given us a framework for conceptualizing, organizing and developing large, complex, software systems, and delivering them on schedule, on cost.

His approach to software development emphasizes two basic ideas. Unique is his application to the development process of the cognitive philosophies of the great Nineteenth Century German cognitive philosophers, principally Schopenhauer, Kant and Hegel, which De Gyurky has studied for years (- in the original Nineteenth Century High German). De Gurky also emphasizes to an extraordinary degree the active role of personal leadership required of the successful software development manager.

Far from being a purely theoretical work, the book is richly illustrated with pungent examples from De Gyurky's near-incredibly varied experience both in the US military as a Special Forces officer commanding a detachment of Montaignards in the mountains of Vietnam, as an action officer at NATO Headquarters, and as the civilian developer of very large military flight-schedule management systems as well as spacecraft software command and control systems.

All the examples are exquisitely pertinent to the software development process. But in addition, four detailed programmatic examples are presented, together with comments, figures and schedules. The author's application of the principles he developed is wholly consistent and unfailingly pertinent, if sometimes challenging, due to the likely unfamiliarity on the part of the typical software engineering reader with the application of the philosophical concepts.

In fact, the single characteristic of the book which may challenge the typical software developer is the accessibility of some of the concepts. Some of the most powerful concepts discussed, e.g., the dialectical process by which an ill-formed idea becomes an object that reflects the meeting of the minds of the design team, are likely to be unfamiliar. However this process has profound implications for the organization of the design team, its management, team-member responsibilities, and on and on. It might have been helpful if the author had expanded on these key concepts, perhaps in context closer to their original use. It would be demanding on the reader, but probably no more so than parts of the book itself.

This unique contribution is recommended to software developers interested in on-time, on-cost development of large software systems, and willing to invest in the intellectual effort required to understand the author's unique contribution. They will be well rewarded.

I have read many books on systems and software development and management principles over the years. The ones that most influenced me were: "More Reliable Software Through Composite Design" by Glen Meyers; "Up the Organization" by Robert Townsend; and "Reengineering the Corporation" by Michael Hammer and James Champy. And of course no system developer's library would be complete without "Managing the Software Process" and other books by Watts Humphry, a giant in our industry. Mr. Szabolcs Michael deGyurky's book will occupy a place along side these on my bookshelf.

In this book, Mr. deGyurky has provided a completely different and refreshing, but no less important, viewpoint on systems development. As different as all the above mentioned books are, the one theme common to all of them is their focus on the "real" problem by differentiating between the truly important and the seemingly important - commonly referred to as separating the wheat from the chaff..

"The Cognitive Dynamics of Computer Science" focuses on strength of character as being indispensable to successful completion of complex systems development projects, which not only satisfy the "real" requirements, but ensure the system is delivered within an agreed to budget and schedule. This book draws on the philosophy of such estimable historical figures as Kant, Hegel and Schopenhauer, among others, in defining the behavioral characteristics of successful leaders and managers. Personal experiences in real world projects by Jet Propulsion Laboratory (JPL) provide a substantive backdrop for Mr. deGyurky's approach to managing systems development.

It is impossible to adequately relay the impact of such a book in so short a review, but I do come away with some points which derive more meaning because of my own experience: 1) Design from the user in, but develop from the inside out, in layers, 2) Don't implement until you have an initial design documented and understood by the development team - expect that to change, 3) Manage change through the Project Implementation Plan (PIP), which is the Project Manager's equivalent to the Software Development Folder, 4) Don't hire staff until you have their tasks well defined (control burn rate and you have controlled your budget), 5) Make sure you understand exactly what your customer wants through constant customer involvement, 6) make your customer's goal, your goal, then incentivize the entire development team to focus on that goal as the highest priority, 7) There shall be no implementation without documented, repeatable process and standards, which should be tailored to the individual project, but at no time should process and standards replace common sense in a dynamically changing development environment, 8) Employ tools and ensure the team is involved in their selection, 9) Ensure the development team is trained in methodology, process, standards, tools and system requirements, and 10) the manager should place the needs of his customer and his team ahead of his personal goals.

All of this is done in concert with the philosophical teachings of our great philosophers, who would encourage strict honesty and ethics in dealing with our customer, subordinates, colleagues, company management, even if it means being fired. Of course, one does not fit all the meaning of a 300-page book into such a short review, and one could easily list another 10 or more points of interest.

I agree with almost everything in this excellent book, but may differ on the role played by Computer Aided Software Engineering (CASE) and Computer Aided Design (CAD) in systems development. Since CASE tools became mature enough to use effectively, I personally selected my tools, then built my process and standards around them. This includes the way I modify process and standards (including DoD) to conform to streamlining development and associated documentation. The CASE tool, when used with discipline can ensure that interface errors are avoided during the design process, as provided through automatic leveling and validation as the system design progresses. Fixed price contracts caused me to gravitate to using the latest tools available and build around them each time.

I am certain that Autonomous Cognitive systems are in our future, but not without application of increasingly sophisticated CASE tools and compilers (Autonomous Cognitive Compilers), which can parse complex combinations of Boolean expressions with many operations per expression to simulate the human thought system in making decisions. Neither can these systems be built without addressing the transducers (sensors), which would connect to and provide stimuli to be interpreted and processed by any autonomous system as the 5 senses (sight, hearing, touch, smell and taste). I look forward to Mr. deGuyrky's next book, which may address this highly complex problem.

I would only close this review with one last comment, directed to JPL. Mr. deGyurky and his team were on the right track with Ada. It is unfortunate that JPL didn't adopt this very highly typed and disciplined high order language as their standard development language. I believe it would have saved more than one failed project. Based on my 40 plus years of developing computer systems, I would humbly suggest that JPL require mandatory use of Ada in all "Class A" development projects.

I have to say that this is a true classic. It gives a very nice treatment of what is NP-completeness in a fashion that really defends the topic well. It gives nice illustrations to show different situations and how to deal with it. But after the first couple of chapters it does get a little out there with the proofs it does. It is still approachable, but it assumes that the reader is already familiar with the basics of combinatorial complexity, especially in reductions. I would only recommend this book to readers who has gone through such books as Introduction to Algorithms by Cormen et al. or Combinatorial Complexity by Papadimitriou and Steiglitz. Those two books are more for beginners and this book should be one to help anyone interested in NP-complete problems to get more practice and depth understanding. Overall a great book for anyone interested in the topic. The grand challenge is to reduce everything to at least something within the 150 problems listed on your own.

The book is excellent in explaining NP-completeness problem. Take it as a reference if you would like to do research in this field.

This is a rare example of a textbook where the authors actually go to the trouble of considering the fact that the intended reader is a non-expert. Published in 1979 and still the best.

The book arrived in time, in good condition, and adequate packing.

This is among the most eloquently written books that I have ever read in my life. Highly recommended.

Most texts on industrial control are long on theory and short on practice. This book is a rare gem that presents the theory (without overloading you on details) and then explains how to actually use the theory in practice. (One note: the practical applications are focused on electric motor control, which is the author's background.) If I had to have only one book on controls in my library, this would be the one.

This is a really good book that simplified control system for the real world. Most text spend too much time on theory and analysis and end the discussion with a bunch of equations and graphs without explaining how to implement the design. This book covers both analog and digital control, and lets you download a software from the author's web site. This software, ModelQ, lets you play with various parameters so you can see how the system behaves when it is not optimized.

One drawback with the book is it only covers PID control and its variants, but doesn't cover state-space control. While state-space control may be considered "overkill" by many control engineers, state-space is used in industry. The decision to use state-space is often not in the hands of individual engineers, so it may not be an option to ignore state-space. It would be nice if Mr. Ellis could cover state-space in his next edition of the book.

I had three main reasons for buying this book:
1. To bridge the gap between the control theory from school and the systems that I now design and build
2. To gain insight on how to improve the performance and reliability of real motion systems
3. To find ways to apply advanced techniques to help meet challenging performance requirements

I got all of this and more from this book. The topics covered clearly and concisely in this book span three courses I took at Cal Poly SLO: basic controls, digital controls, and modern/advanced control theory. Mr. Ellis does a great job of quickly introducing these topics and getting straight to the practical implications.

The free software and examples work well to illustrate his points quickly and easily while helping to commit the insights to memory. I also hope to use it as a training tool for our techs.

I highly recommend this book to anyone working with control systems, especially grad students and people getting started in the field. I look forward to reading his book on observers.

The author attempts to bridge the gap between theory and practice, and does a good job at it. Familiarity with control concepts will help one to get more out of the book, because the book focuses more on the practical aspects. The explanations in some of the sections can definitely be more complete, and thus I have to give it only a 4 star rating. Overall it is a good book.

Ellis has made a fantastic book on PID and similar control loops. He takes a very different tact than most controls books -- he writes with a voice similar to a handbook, but delivers enough content to compete with more traditional textbook-style controls books. It is light on the math in comparison, but I don't find myself wanting for more math.

I do a lot of controls design, consulting, and teaching. I recommend this book often and find that people that buy it uniformly track me down and thank me for the recommendation. I can't think of much higher praise for this book.