Programming Books

The book doesn't teach you Java. It is assumed that you already know Java.
doesn't cover all of Numerical calculus and not all of mathematical proofs but great if you are looking study practical programming with Java.

I recommend this book only if you know Java and have basic numerical knowledge.

This book is an introduction to numerical computing that is both comprehensive and fun. It is not a textbook on numerical methods or numerical analysis, although it shows many key numerical algorithms all coded up in Java. The book examines these algorithms enough that you get a feel for how they work and why they're useful, without formally proving why they work. There are also demonstrations of many of the algorithms with interactive graphical programs. Overall I enjoyed this book a great deal. It is not a beginner's book on Java - you should be a pretty good Java programmer already. Also, you should be at least somewhat mathematically mature for the material past part one. That is, you should have had some Calculus and some Linear Algebra prior to reading the last 3 of the 4 parts of this book. I further describe this book in the context of its table of contents.

Part 1: WHY GOOD COMPUTATIONS GO BAD - Simply copying formulas out of a math or statistics textbook to plug into a program will almost certainly lead to wrong results. The first part of this book covers the pitfalls of basic numerical computation.

Chapter 1 discusses floating-point numbers in general and how they're different from the real numbers of mathematics. Not understanding these differences, such as the occurrence of roundoff errors, and not obeying some basic laws of algebra can lead to computations that go bad.

Chapter 2 looks at the seemingly benign integer types. They don't behave entirely as the whole numbers of mathematics do. Arithmetic operations such as addition, subtraction, and multiplication take place not on a number line, but on a clock face.

Chapter 3 examines how Java implements its floating-point types. The chapter examines the IEEE 754 floating-point standard and shows how well Java meets its provisions.

Part 2: ITERATIVE COMPUTATIONS - Computers are certainly good at looping, and many computations are iterative. But loops are where errors can build up and overwhelm the chance for any meaningful results.

Chapter 4 shows that even seemingly innocuous operations, such as summing a list of numbers, can cause trouble. Examples show how running floating-point sums can gradually lose precision and offer some ways to prevent this from happening.

Chapter 5 is about finding the roots of an algebraic equation, which is another way of saying, "Solve for x." It introduces several iterative algorithms that converge upon solutions: bisection, regula falsi, improved regula falsi, secant, Newton's, and fixed-point. This chapter also discusses how to decide which algorithm is appropriate.

Chapter 6 poses the question, Given a set of points in a plane, can you construct a smooth curve that passes through all the points, or how about a straight line that passes the closest to all the points? This chapter presents algorithms for polynomial interpolation and linear regression.

Chapter 7 tackles some integration problems from freshman calculus, but it solves them numerically. It introduces two basic algorithms, the trapezoidal algorithm and Simpson's algorithm.

Chapter 8 is about solving differential equations numerically. It covers several popular algorithms, Euler's, predictor-corrector, and Runge-Kutta.

Part 3: A MATRIX PACKAGE - This part of the book incrementally develops a practical matrix package. You can then import the classes of this package into any Java application that uses matrices.

Chapter 9 develops the matrix class for the basic operations of addition, subtraction, and multiplication. It also covers subclasses for vectors and square matrices. The chapter's interactive demo uses graphic transformation matrices to animate a three-dimensional wire-frame cube.

Chapter 10 first reviews the manual procedure you learned in high school to solve systems of linear equations. It then introduces LU decomposition to solve linear systems using matrices. An interactive demo creates polynomial regression functions of any order from 1 through 9, which requires solving a system of "normal" equations.

Chapter 11 uses LU decomposition to compute the inverse of a matrix efficiently and reliably. A demo program tests how well you can invert the dreaded Hilbert matrices, which are notoriously difficult to invert accurately. The chapter also computes determinants and condition numbers of matrices, and it compares different algorithms for solving linear systems.

Part 4: THE JOYS OF COMPUTATION - The final part of this book covers its lighter side of numerical computation.

Chapter 12 covers Java's BigNumber and BigDecimal classes, which support "arbitrary precision" arithmetic--subject to memory constraints, you can have numbers with as many digits as you like. This chapter explores how these classes can be useful. You compute a large prime number with more than 3,000 digits, and you write functions that can compute values such as the square root of two and e^x to an arbitrary number of digits of precision.

Mathematicians over the centuries have created formulas for computing the value of pi. Enigmatic Indian mathematician Ramanujan devised several very ingenious ones in the early 20th century. An iterative algorithm supposedly can compute more than 2 billion decimal digits of pi. Chapter 13 uses the big number functions from Chapter 12 to test some of these formulas and algorithms.

Chapter 14 is about random number generation. A well-known algorithm generates uniformly distributed random values. It examine algorithms that generate random normally distributed and exponentially distributed random values. The chapter concludes with a Monte Carlo algorithm that uses random numbers to compute the value of pi.

Mathematicians have mulled over prime numbers since nearly prehistoric times. Chapter 15 explores primality testing and investigates formulas that generate prime numbers, and it looks for patterns in the distribution of prime numbers.

Chapter 16 introduces fractals, which are beautiful and intricate shapes that are recursively defined. There are various algorithms for generating different types of fractals, such as Julia sets and the Mandelbrot set. In fact, Newton's algorithm for finding roots, when applied to the complex plane, can generate a fractal.

I have got hold of this book just recently. This is an excellent book on numerical computing using Java that covers many important aspects in numerical computing. I have been writing numerical methods in Java back in graduate school as well as in my professional career for mission critical programs. I must say this book has addressed many issues that must be taken into account such as machine epsilon, choices of numerical methods for different problems, limitations and precautions in using different data types, etc in Java in which if taken for granted, would produce disastrous results.

Ronald Mak has taken the trouble to explain IEEE floating point standards in a fun and easy-to-understand manner.

Another thing about this book that is worthy of a mention is its great OO programming styles. Codes are also well commented and reader friendly. Overall, it is a great source to learn not just on how to program numerical methods in Java but how to write good OO programs.

The only two bad things I could say about this book is that I should have gotten of this book much earlier and if only Amazon allows a Six Stars rating.

As the author says, last time I looked Java still had the +, -, /, * and % mathematical operators.. though most programmers end up forgetting it lost as they are in the boring, vulgar and repetitive coding of boiler-plate "enterprise" (read "sell sell sell") applications. This book does a very good job of introducing a Java programmer to one of the most fun and interesting powers that Java can offer ... that is playing with numbers and exploring the world of mathematics. Forget (at least for a little while) Servlets, JSP, EJB, and database massaging... and give a look to how you can use your JDK to study functions, solve differential equations, integrals, system of equations, discover prime numbers and admire the beauty of fractals. The treatment of the various subjects is done is sufficient detail to be clear and sound, but without burderdening the reader
with detail and depth best left for more specialized and hard-core texts that the curious reader can explore after this one. Refreshing.

At one time or another, most of us will likely have to write code performing some amount of numerical computation beyond simple integer arithmetic. As many of us are neither mathematicians nor intimately familiar with the bit gymnastics our machines must perform in order to manipulate numbers, we can get ourselves into trouble if we're not careful. Luckily, "Java Number Cruncher" comes to the rescue.

This book is an introduction to numerical computing using Java providing "non-theoretical explanations of practical numerical algorithms." While this sounds like heady stuff, freshman level calculus should be sufficient to get the most out of this text.

The first three chapters are amazingly useful, and worth the price of admission alone. Mak does a fine job explaining in simple terms the pitfalls of even routine integer and floating-point calculations, and how to mitigate these problems. Along the way the reader learns the details of how Java represents numbers and why good math goes bad. The remainder of the book covers iterative computations, matrix operations, and several "fun" topics, including fractals and random number generation.

The author conveys his excitement for the subject in an easy-to-read, easy-to-understand manner. Examples in Java clearly demonstrate the topics covered. Some may not like that the complete source is in-line with the text, but this is subjective. Overall, I found this book educational, interesting, and quite enjoyable to read.

My knowledge of Oracle and Java is beginner/intermediate level and I like this book a lot.

The book explains how SQLJ relates to SQL, PL/SQL, Java, JDBC and it provides a good introduction to the JDeveloper IDE (Integrated Development Environment).

The book is written very clearly and the appearance and organization of the text is well up to the O'Reilly standard.
I can't comment on the worked examples yet as I have not yet tried them out.

This is just an easy read with good code examples. It is geared toward the intermediate or beginner programmer, and presents clear explanation for easy understanding.

This is an outstanding book. SQLJ is a simpler way of embedding SQL statements in a Java programming, and is possibly the successor to PL/SQL.

I liked this book because it covers SQLJ programming, as well as:
1. Oracle SQL.
2. Oracle PL/SQL.
3. Oracle JDeveloper.
4. Developing J2EE components for the Oracle9i Application server (9iAS) such as EJB, servlets and JSP.
5. Java stored procedures.

I liked the author's writing style: it is clear and to the point. I found it very easy to read, and was able to follow the examples in the book and apply them to my own programs.

I highly recommend this great little book!

This is a great book if you are interested in building J2EE applications and want to link to an Oracle database but don't want to learn the complicated JDBC API. It isn't an 'intro to programming' book like so many out there; it is, however, perfect for object-oriented programmers who are wanting to learn java with a quikness. Finally, a great SQLJ book has emerged!

I found this book to be concise, to the point, and very readable. A large amount of material was well presented in a relatively small amount of space. And the examples worked as advertised.

I found myself incorporating the material presented into my work before I finished reading the book.

An excellent resource.

Mr. Ulrich has delivered a framework with which IT areas can effectively leverage their existing applications and data to meet the ever-changing business environment. Bill's chapter on Case Studies provides real life examples of how to use his methodology. We face rapidly changing business drivers, including the need to make our businesses internet-ready. This book provides the materials to allow companies a fighting chance to succeed.

I read Bill Ulrich's book and was delighted to see that he was clearing laying out strategies that we were dealing with as we worked with our clients. We now make Mr. Ulrich's book part of our mandatory reading for our consultants and have purchased copies for distribution to some of our key clients. This has helped both our consulting teams and our clients in planning and project executiion.

Mr. Ulrich understands how businesses have a tremendous reliance on legacy systems. Pressure is always on the IT staff to meet the demands of the business cusomter. The IT community is asked to bring products and services to the consumer through the internet while managing the internal demands to keep expenses under control. Bill's book lays out a framework in which the business community can build company-specific plans to leverage their prior investments while striving to meet today's business drivers in a manner that is cost effective.

Bill has filled this book with tremendous value for any one working with existing systems of any kind. He builds in the flexibility of approach by mapping many common and not-so-common methods and strategies through his exploration of specific case studies. Chapter 3 is a valuable item on its own - rarely have I seen such a thorough and clear examination of all the different 'movements' in IT in the last 10 years. Nice job, Bill.

Corporations have been trying to retire legacy systems for the past couple of decades. Each new technology (be it client/server, ERP packaged apps, etc) were supposed to put the nail in the coffin for legacy systems. Yet, legacy systems continue to thrive despite attempts to retire them. One reason why they continue to exist is that in many instances, they support business processes in the most efficient and cost-effective manner possible. Bill's book views this area more as a transformation effort (evolution) rather than wholesale legacy replacement (revolution). This book is a must read for IT departments as they struggle to remain relavent in an era of outsourcing.

The strategies outlined in this book will help the IT department become a partner with functional business units in delivering solutions that address burning business problems. The focus shifts to providinig measurable value to the business as opposed to implementing unified and elegant technologies.

From beginner to expert this book contains all of the answers to your lingo needs. It is packed with examples and thorough descriptions.

I can't find an updated version of it - if anyone knows of one please let me know!...

This book has got to be the best computer related book I ever bought. I wish there were reference books in this format for every other programming subject like Perl and JavaScript. It's the only book you will ever need for Director's lingo.

The thing I like most is having the Lingo grouped by subject, it makes things so easy to look up.

Darrel, please make a reference like this for Perl!!!!

If you are already familiar with the Director interface, and want to do things in Lingo that most people only wish they could do, pick this book up right now! This is the only book I use on a daily basis for quick information. Darrel Plant not only gives a clear explanation on every command but also gives you examples that you can understand and use in everyday applications. I also greatly appreciated the way that the book content is organized. Rather than list the commands in alphabetical order, they are grouped according to the type of element or function that they control. It's nice to put something together that the user/client likes, but use this book and they will be saying, "Awsome! Love it! Wow, how did you do that?" ------ Thanks Darrel

...your life will be easier if this book is within reach. I even take it with when I have to go on-site to a client. Very useful having the Lingo grouped by subject. Also very useful icons by each Lingo word showing if it can be used in Shockwave and which versions of Director it can be used in. A must-have for a Lingo programmer.

(excuse my english, I'm Swiss) Before purchasing this book or even knowing about it, I had some heavy problems in finding the right way (or a shorter one) to solve several problems in programming Multimedia-applications. I ordered this book and everything changed! It's descriptions are so easy (even when you aren't originally english-speaking!), because you just can read the text and know what the command, keyword, property a.s.o. is all about. You have even more than one solution showed in examples. There is only one bad thing: if you use this book very often, the cover of the book looks old soon; it could be a little stronger. My suggestion: if you suffer a headache from studying and controlling your non-functioning scripts, you better get this book as soon as possible and keep it handy! You will gain a hell of a time!

Have fun

Best regards

Patric Simon

I am a .NET developer (MCP).

I bought this book because our company launches a new dev project for providing alerts to customers on their financial data (wires, etc.), and I've read that SQL NS is way better than any custom app.

First of all, now that I've read most of the book (and worked through all the samples), I totally support that info.

Secondly (yet very important), I swear I have never had a technical book that was as easy to read and comprehend as this one!
Microsoft is inclined to use some sort of "bureaucratic English" on MSDN, which is a pain in the neck to understand for someone like me (apparently, English is not my native language).
However, even though the author is a Development Lead for SQL NS at Microsoft, his book is as easy to read as my favourite science fiction books (and far easier to read than most of fantasy books like those by Tolkien).

The examples in this book lead you from the most basic concepts of NS to the most advanced features such as developing a custom delivery protocol or a custom standalone event provider.
All you need to start with it is basic knowledge of T-SQL (or, just any flavor of SQL) and XML (REALLY basic!).

And, yes, it's true, you can build a fully functional prototype in less than 2 weeks. I did.

It's a pity that the maximum number of stars is 5.

This book is truly a masterpiece.
A must-have for everybody working with data-driven applications.

It's 600 pages of "SQLNS as a way of life", from beginning to end. It explores setup (without any gratuitous screen shots of setup, THANK YOU), configuration, programming instances and applications, writing the processing configuration files, the subscription management application. There are chapters about custom event providers, formatters, and delivery protocol; there is an example of each. But of course, where this book shines most (is shine most the correct construct? hmmm...) is in the description of internals, tuning, and troubleshooting. That's where it's invaluable. I still remember going over "quantum theory" and all its permutations when I read that chapter.

If you use SQLNS as a notification application framework, it's very easy to get a first instance working, but when your app gets popular and you need 10 more just like it immediately, working with SQLNS quickly becomes all-consuming, that's what I meant by "SQLNS as a way of life". If you're looking to "check out" SQLNS or see if its "right" for your application that's fine too, the preface even gets you quickly up to speed on the SQLNS lingo. I also remember Shyam writing to me a few times about the "its not a custom delivery channel, its a custom delivery protocol". In any case, there's *no way* you can be dissapointed with this book.

This book has been very well written and covers all the aspects of Notification Services a developer must know about. Not only are the various concepts explained very well, the numerous examples and code samples given make this an easy read as well.

One of the key sections of the book is how to troubleshoot your NS application which is the USP of this book, seeing that such treatment to that particular area has not been given anywhere else.

I would strongly recommend this book to anyone who is interested in developing NS applications.

This is a book well worth reading from beginning to end, from preface to appendix. I have done so twice, with the result that I have learned SQL-NS well enough to explain its concepts and architecture to my teammates and higher-ups and to embark upon design and development of notification apps of my own. Mr. Pather puts mastery of this platform within your reach. His pedagogical approach is exemplary, for its organization, pacing, clarity, style and tone. And he covers absolutely everything you need to know about SQL-NS. I wish every computer book out there were written this way.

I would highly recommend this book for anybody developing Sql Server 2000 Notifications Services applications. This book fills the gaps in the Books Online, which, for a large scale application are very important.

The book is structured to provide quick, step-by-step implementation instructions as well as detailed explanations of the hows and whys of Notification Services.

I was particularly grateful for Part III of the book that details optimization, deployment and administration requirements.

Another invaluable part of the book is the chapter on setting up your development environment. I had to do my first application before the publication of this book and I will tell you that had I had this book then, the time I would have saved would have paid for the price of the book many times over.

One of the few WM development books, and certainly the only one that merits five stars. This book is thorough, timely, and informative about the technologies relevant to making great WM apps in native and managed code.

I purchased this book, among others, to learn more about the compact framework. This has ended up being the one that is always on my desk and constantly referred to. There is information in here that is not on any google search, and the code used by the author to demonstrate complicated operations (such as creating opacity in CF forms), is easier and clearer than I have seen anywhere else. A very good book, and well worth purchasing.

Definitely a good book: I found it very complete and easy to read. Useful and interesting, straightaway.

Got 2 copies for my moble development team. The book is simply invaluable. Either you read cover to cover, or select any chapter of special interest the result is in depth information and guidance. Very often our two copies are not enough for everyone in the team.

It is like my bitacora or bible when i am offline. I guess it has a little of everything you need to know in very compact book (i thought a 600 book will be wider but the size is great)

I am an ancient programmer switching from C to .NET. I have read a lotta books in my time and this is the best presentation and layout of a book I have ever seen. Its easy to read. Content is great. I wish I had found it first in my conversion to .NET. I am so impressed that I am checking out the other Murach titles for something to buy.

I needed to learn ADO.NET for my job and this book was the best on the topic I read the entire book in about 3 weeks. Everything is explained wonderfully. I love how the examples are laid out on the right with explanations on the left. I also really found the program files extremely helpful. I opened each chapters program and followed right along with the book. All the examples are already created so that you can see how they work and even modify them.

I liked this book so much that I also bought the ASP.NET, SQL, and Visual Basic 2005...all topics I need to brush up on. As far as I can tell these other books follow the same great format.

From someone who thousands of dollars worth of technical and programming books...these are great even for beginners. However if you are not familiar with vb2005 get murach's visual basic 2005 to read first.

As with the other Murach Press books I have reviewed, this book is extremely readable. It shows step-by-step how to develop database applications with VB. NET 2005 and ADO.NET. This book is best suited to someone new to database development with Visual Studio 2005 but that has a passing familiarity with VB syntax. If you are unfamiliar with flow control statements and VB syntax, you might want to look at Murach's "Visual Basic 2005" book first. I highly recommend this book for entry to mid level developers.

ADO.NET is a huge and sometimes daunting topic to attempt to cover, but in traditional Murach fashion, this book has the capacity to make its reader an expert if read cover to cover. All of the important topics are coverered, including use of the base objects, data binding, typed vs. untyped data sets, and most importantly (in my opinion): use of object data sources.

The best part of Murach books (including this one), aside from the paired page layout, is that they make no assumption about the reader's skill level, and cover enough background on each topic to ensure that you will come away with a thorough understanding of not just what and how, but also why.

Both beginner and expert programmers alike will find this book extremely useful, and it's a great addition to the Murach family of programming reference and tutorial books.

I am a C# developer but when I started browsing this book I couldn't help it but to continue reading it. It is not only about the VB language itself, but instead, how to use it so solve software problems. It teaches how to better write software, best practices and approaches.
This book doesn't cover all the theory in the world about a topic. Also, not all topics. But it tells you how to use them and what to watch for.
I am glad to have read it.

I have partially read so many bad romance novels recently (e.g., boy meets girl & saves the day). The plot of this book was unique and kept me reading straight through. The characters were very likable (the hero was not the overbearing Alpha male so often written into a romance novel). I did not read the other books yet in the trilogy - this was my first Holling book. Not having read the other two was not a problem for me. I hope her other books are as entertaining.

I truly enjoyed this series. There is so much depth and emotion in all three books. My Shadow Warrior concludes the story of the three sisters; Isobel, Gillian and Rose. Rose is a strong heroine, intent on saving her dying father at any cost. She seeks out the Wizard of the North, William in hopes that he will be able to save her father using his powers. After a rocky start he agrees to travel home with Rose to heal her father. The story is romantic and dark with lots of sexual chemistry. Deidra, William's daughter who is the heroine of My Immortal Protector (my favorite Holling book) is introduced in this book.

The fascination with the paranormal implies a big dose of imagination; Jen Holling is creating three heroines of different mystical powers: Isobel, Gillian and Rose MacDonell; in My Shadow Warrior, they merge the powers toward solving the mystery of the illness of Allan MacDonell, their father, and the fate of Lilian MacDonell, their mother.
Must read the entire trilogy

I am a die hard fan of romantic novels. I have all three of the series and I absolutely love them they are all really good.

This is the third installment of The Brides of the Bloodstone trilogy. It's the story of Rose, youngest of the three MacDonell sisters. While they were little girls, their mother, a powerful witch, was burned at the stake. In fear for their lives, their father hid them separately. Now many years later, and on his deathbed from a mysterious illness, the MacDonell has summoned his daughters home.

Their lives are still in danger so he has arranged each of them to be married to men he can entrust with their safety. Rose, the youngest and blessed with the healing touch, is betrothed to Jamie MacPherson, a childhood friend she hasn't seen in years. Her wedding, however, has been postponed so she can devote herself to discovering the source of her father's illness.

Despite her many efforts, her father continues to deteriorate. To Rose's mind, her only hope is William MacKay, a gifted healer also known as the Wizard of the North. Since her many letters to him have gone unanswered, Rose decides to travel to his fortress to see him in person.

William is determined to shun the girl who has traveled many miles to see him, but curiosity forces him to disguise himself and seek her out. What he finds is a beautiful woman who is dedicated to helping others, even at risk to herself.

His fascination with her finally forces him to see her and eventually agree to travel to MacDonell castle to see her father. But in truth there is a sinister plot behind the MacDonell's illness and his wife's death and this mysterious enemy will stop at nothing to get what he wants.

This was such a great ending to a wonderful trilogy. The plot of the MacDonnell's illness and the mother's death at the stake is woven throughout all three books. It is finally resolved in this last tale but what an ending. Jen Holling has done a masterful job weaving several storylines together to create an enchanting tale of love, treachery, and greed.

I am an intermediate programmer, who in the past, has done some Visual Basic 6 and Win32 API integration programming. After learning VB.NET and C#, I found that the .NET Framework was missing some functionality of the Win32 API, which surprised me a little since Microsoft is really pushing .NET as the "API" of choice for developers.

I agree with the book that the .NET Framework is mostly targeted at business developers and the Internet for B2B and B2C applications, as well as internal Enterprise applications. Having said that, I have found the .NET framework lacking, and as the author points out, most likely due to how young it is in comparison to the Win32 API.

This book will get you up and running with making those Win32 API calls when you can't find that same functionality duplicated in the .NET Framework. There isn't much documentation on this subject matter on MSDN or the web (searching on Google), so this is pretty much it. The author did a great job, however, at times, the examples were a little light or topics weren't explained as thoroughly as they should have been. For example, the author will tell you what data type he used in place of a native Win32 data type, but doesn't clearly explain his reasoning for the choice. But other than that small complaint, this book is a must have for any .NET developer.

Let's face it, .NEt is really cool, but it isn't a finished product. For everything else, there's this book. He has some Great examples and explains everything amazingly well. I'm a book junkie and this is definitely one of the best books I've come across recently. I think this book would be a tremendous asset to anyone who wants to learn how to get around .NET's current limitations.

.Net Framework Solutions is a very useful resource for those .Net developers (using C# or VB.Net) who want to access the Win32 api from their .Net programs.A no of working examples (with source code available on accompanying CD) and lucid writing style makes this book a pleasure to read and can be very useful to avoid the traps in calling Win32 API. This book assures that you are not stuck with some problem because the .Net Framework does not provide support(which still lacks support for a no of Win32 APIs.)

If you are doing .NET -> Native interop., this book should pretty have almost all that you need. Note that it does not cover COM (RCW) interop in that much detail and does not talk about CCW (COM -> .NET). However, the coverage of MarshalAs() and the clever examples that show how to deal with the complex DirectX structures are alone worth the price of admission.

What I liked best was the author didn't take the cop out solution (managed C++) unless it was absolutely necessary. Most of the code examples in the book are in C# and this might be of some concern to the VB.NET programmers. The chapters are well organized and there's an appendix with 50+ good tips on PInvoke. If you are still struggling with your PInvoke interop problem after reading this book, it's time to bring out the heavy weight (Adam Nathan's bible) -- good luck!!!

Atul

This is a great book for developers seeking to understand how to translate C++ datatypes in the Win32 API functions into C# and VB.NET. It's not in-depth like Dan Appleman's VB's Guide to the Win32 API in past years, but it's the first of its' kind for .NET. My only wish is that the author not have spent so much time on DirectX and instead provided more general examples of other API calls. DirectX coverage should have been left for another book aimed specifically at that technology.

I have been fascinated by the simplicity and usefulness of the
Object-Process Methodology paradigm and approach expressed in the book. As a
researcher in Science Education I have been grappling with how to represent
complex, technology-enhanced educational systems that involve humans,
processes and educational artifacts. OPM and the OPCAT software enclosed
were very instrumental in enabling me to model and represent the "big
picture" of educational systems I developed. With OPM I was then able to
gradually refine portions of the system to any desired level of detail.
The applicability of OPM to IT-intensive educational systems is a testimony
to the generic nature of the methodology and to the fact that it is useful
in so many domains. The combination of a single simple graphical model that
generates natural language on the fly is really unique and valuable. I
wholeheartedly recommend the book to anyone interested in modeling complex
systems, be they of technological, economical, or social nature. The method
is straightforward, easy to learn even for non IT-professionals, and most
rewarding in terms of the quality and clarity of the resulting graphical and
textual model.

This book describes how Object-Process Methodology (OPM) CASE can be used as a tool for generating complete system intent specifications by graphical object diagrams, precise semantic and syntactic language, and intuitive symbols, definitions and structures. As systems have become more complex, a prevalent problem in systems development has been the number of accruing errors. These errors can cause catastrophic failure in the worst-case in addition to intolerable schedule delays and cost overruns. Introducing errors as well as difficulty finding and successfully correcting them occurs because of the lack of proper analysis and design tools for complex system specifications. OPM has the attributes to mitigate against the possibility of system failure, providing comprehensive visibility for better schedule and cost control in product development. It enhances reuse of system modules, processes and software routines in different contexts, while reducing the chance of errors. OPM automatically generates intent specifications that are readily understood by both customers and product team members and are translatable to machine control subsystems. OPM is a holistic systems paradigm that extends the Object-Oriented (OO) paradigm and overcomes its major shortcomings by integrating system structure and behavior in a single integrated graphic and natural language model. OPM successfully tackles the task of development and lifecycle management of systems, products and projects. OPM is a significant extension of and a major departure from the OO approach. It incorporates the system static-structural and dynamic-procedural aspects into a single, unified model. Presented as a concise visual formalism by a set of Object-Process Diagrams (OPD set), it is automatically translated into a set of Object-Process Language (OPL) script, a subset of natural English. At the basis of the OPM philosophy is the observation that to faithfully and naturally analyze and design systems in any domain, processes, like objects, should be considered as stand-alone "things" (entities) that are not necessarily encapsulated within objects. This detachment and de-coupling of processes from objects emphasizes the duality and complementarity of objects and processes, and opens the door for structure-behavior unification. At any point in time, objects exist with some structure and state. This is the static aspect of the system. Processes affect objects by changing their states. This is the dynamic aspect of the system. System complexity is managed through a number of graphical scaling options: zooming into and out of processes, unfolding and folding objects, and expressing or suppressing object states. These mechanisms provide for selectively detailing a subset of things while still maintaining the high-level context of the details.

OPM provides a new framework for specifying design intents and capturing the complexity of hardware and software interaction. Through OPL, it is possible to translate the process into a machine executable code. In addition, OPM can capture the dynamic behavior of the hardware attributes and software states in a single integrated graphical and textual language that is understandable by domain experts who have no programming experience. These traits of OPM ease the development effort for evaluating the system reliability during the design stages. Simulation and testing protocols can be automatically generated though future extensions of OPM to reduce lengthy system verification efforts.
The main benefit of OPM is its ability to identify system objects, processes, and the relationships among them in a structured way. The resulting OPD set becomes an excellent framework for identifying how to implement structural and procedural improvements. The resulting OPL script provides a well-defined set of existing and future specifications for the system. The ability to freely switch from text to graphics and back is of great value to understanding the system as a whole with a single graphic and textual model, without the need to consult various models and carry out mental transformation among these various models.
Based on my personal experience, the following points highlight the benefits OPM can bring to the particular projects described in this paper.
1. OPM is an excellent way to represent daily activities, products, processes and other complex things
2. OPM has allowed representing the complete system with its various aspects in a single model. The model specifies the systems function, structure and behavior aspects without sacrificing clarity.
3. OPM can be used as a common language to exchange design among members of a team.
4. Since OPM design is visual and textual at the same time, it is easy to explain the design.
5. OPL is very easy to generate from OPD
6. OPM will be a good tool for documenting the existing processes and as ISO documentation.

I have used many methodologies over my career. Most of them are based around the object-oriented and structured design paradigms. I found out about OPM quite by accident about a year ago. I've been using it ever since. I have used it to model both hardware and software systems, as well as for business process modeling. It is an excellent methodology and I recommend it for anyone developing any kind of system.

One of the nice things about OPM is that it is easy: I was able to get a team "up-and-running" with the methodology in less than an hour of teaching them some basic concepts (try doing that with UML). Another feature is that you can use this for any type of project; you are not locked into a structured or object-oriented mindset like structured analysis or UML. OPM can handle both types of concepts with ease.

Finally, this methodology is fast. It is just easier and more intuitive to model in an OPM fashion. I've also found that others can comprehend the OPM models better than other methodologies too.

I used to be a UML advocate until I found OPM. I have found concepts that are difficult to model in UML are quite easy to model in OPM. It is just more flexible.

The book is really good by the way. It is very complete and gives plenty of good exammples. I congratulate Dov Dori and his team for providing something that all engineering disciplines can use to design their systems.

OPM is a methodology for modeling systems, technical as well as any other system. In the techical world it compares with UML. OPM is designed with consistant and simple notations, uses simple rules that when combined can be used to model any system (real or informational) to any level of complexity that is desired by the system architect. Also, it integrates object modeling and process modeling in one diagram (although you can still keep them separate if you wanted).

UML uses complex rules to model complex systems, something that is very difficult to make happen, therefore it is very difficult to learn and use. OPM uses simple rules and consistant notations to model complex systems. After simple introductions to the methology, we have been able to start using it in our organization. More powerful and far simpler then UML. The way UML should have been done long time ago.

There is an eternal debate between system designers
and architects of software, products and large systems:
Is it ever possible to show structure (the arrangement
of objects) and system behavior (over time) in the same
representation? Dov Dori's book shows convincingly that it can
be done. Particularly powerful is the duality between
graphical system representation and natural language.
Also, the CD-ROM with OPCAT software allows one to follow
the examples in the book and apply OPM directly to a project.
The book is clearly written and will appeal to engineers,
computer scientists and software developers. A refreshing
contrast to the traditional way of looking a object-centered
systems architecting. This begs for more ... in terms of
connecting OPM to other tools such as Design Structure Matrices,
but also for representing highly complex systems over >2 levels
of decomposition.