Software Books

Business Process Change provides a very clear and comprehensive discussion of the methodologies surrounding successful business process management. This has become my new guide for developing a BPM Group within our organization. I very much look forward to more writings by Paul Harmon.

This is about the best Business Process book I have read so far. I worked in a IT transformation for a big Telecommunications company which entailed adopting a new approach to Business Process and Operational Process Development and I found this book very useful. This book with the book Business Process Management - Practical Guide to Successful Implementation provided me with most of the knowledge needed.

I have been leading business process management projects and working in the BPM space since the late 1990's. I found this book to be as complete and well written as any reference could hope to be.

From my perspective, this book does for BPM what Harold Kerzner's books do for project management - set the standard for others to follow.

I think this is the best book that I have seen that allows an organization to consider business process at the enterprise and department level. I have been engaged in business process management in the government for years, trying to define the processes, trying to communicate them, trying to improve them. This is by far the best treatment and guide I have seen. This is what I have been looking for and couldn't find.

In 2004, I worked in a business unit at my company that had experienced a period of declining performance. Our senior management felt that one of the causes was work processes that had become cumbersome and inefficient over the years. I was asked to sponsor a process improvement initiative to try to simplify and streamline how we did work. I didn't know where to start, so I went on a crash course to learn everything I could about improving business processes. I read some great books by Geary Rummler, Roger Burlton, Michael Hammer, and many others. I learned about things like process modeling, process redesign, process improvement, process automation, BPM tools, swimlanes, value chains, CMMI, process owners, Six Sigma, Lean, process architectures--and the role of IT in enabling all of this.

This intense study provided me with a valuable foundation of knowledge, but I still didn't know how pull all of the pieces together. Organizations are extremely complex systems. To improve performance, which approaches work best under which situations? Which tools to use? What skills are needed to improve and redesign processes? What's appropriate, and what's not?

In early 2005, I discovered Business Process Change, First Edition, by Paul Harmon. This book provided me with the big picture perspective of the BPM world that I sorely needed. It helped me to ask the right questions and to structure our process improvement plans more effectively. The issues we have been addressing require long term solutions, and this work continues today. But, we are building an infrastructure that will integrate people and technology into our process change initiatives to ensure the sustainability of our efforts and results.

The First Edition not only helped me organize a more effective process improvement strategy in our business unit, but I also consider the knowledge and perspective gained to be a significant factor in my being selected to lead our relatively new Center for Process Excellence (CPE), a central BPM group located in our corporate offices. The mission of our CPE is to promote a process-based culture throughout our company. We currently lead process improvement and redesign projects to solve specific business problems, and we have begun to develop process modeling skills in our lines of business. We are now focusing on establishing an enterprise business process architecture for our organization and securing executive support for large-scale business transformation.

Thankfully, I now have the Second Edition to consult as we continue on our process journey and take our work to even higher, more ambitious levels. I bought my copy two weeks ago, and while I haven't read it cover-to-cover yet, I have read enough to know that this is not the First Edition with just some cosmetic changes. It is a complete overhaul. It reflects the newest and best thinking in business process change and management today. Like the First Edition, it is a surprisingly clear, practical and useful guide. That's the bottom line for me--what works and how can I use it.

If there was ever a must read book for business process change professionals, this is it.

If you are thinking about learning how to program in C++, this book is for you. I've used many books and must say that this is definitively the best book for absolute beginner. Greg goes at a nice pace that's easy for most to pick up. Book introduces program flow controls, scopes, functions, basic I/Os, arrays and pointers and touches up on object-oriented programming. Review questions and review excercises at the end of each chapter are helpful in testing your knowledge of a particular chapter. If you are looking for extensive OOP that book is not for you, otherwise a beginner cannot go wrong with this book.

If you have absolutely no idea of C++, this is a great book to begin. Though it does not cover much (any) of OOPs, its a nice book to get you hands wet with. This book can easily be read over a couple of days. I strongly recommend Greg Perry's sequel to this book "Moving from C to C++" for a neat understanding of OOPs. I read these two books and was doing great in my C++ course. The nice thing about these two books is that it gives the reader a nice conceptual understanding of why C++ is doing many of the things that is does as against C.

This book is an excellent book for learning C++. It teaches you the fundamentals, and it will keep you coming back for more and more reading because you are learning something about the language. I highly recommend this book to anyone who doesn't know anything about C++. I can't believe I'm learning C++! Buy the book, you won't be sorry.

Out of all the souce books I have on C++, this book is without a doubt the most user friendly and comprehensive that I have found. I consider myself lucky to have come across it. Obviously, the author not only knows his subject, but also knows how to write for the reader. For once, a book that purports to be for beginners is written for the beginner. If you can get your hands on this book, do it. The book stops at OOP which is a very good place to change course and speed.

I've tried learning C++ from many books from various authors. Many started out well, and, by so doing, led me to a false belief that they would actually teach me the language. Each time, I came away frustrated. Perry's book is, however, the one and only exception I have thus far found. Not only does it start out well, it STAYS that way. It genuinely teaches you C++. I find myself actually looking forward to reading and studying from it. This is simply the best book written to date on C++. Now, if I could only get Perry to write one on Visual C++, I would really be in business!

I bought this book for general project evaluation purposes, for a project that I was called in on that was in trouble.

Well worth the read - a lot of it is just good common sense, straightforward project management process, but it provided a great roadmap for validation of my plan to put the project back on track.

Definitely would recommend it - it's an easy read; I finished it in under 5 hours on the flight out, complete with note-taking. Kudos to E.M. Brennatan for writing this in a straightforward fashion.

It is a law of nature, grouped under the general name of entropy, that it is easy to mess things up and very hard to straighten them out. In fact, it is the natural state of nature to tend towards increasing disorder. This law also applies to software projects, since they are naturally very complicated entities; they easily reach a point where difficulties compound to the point of dysfunction. The author calls this state a catastrophe, although in my opinion that is an overstatement.
A catastrophe is a major disaster, far beyond what most software development projects actually are. Granted, there are problems, but most of the situations described in this book are ones that can be recovered from with more effective planning and focused execution. The author puts forward a ten-step plan for disentanglement:

1) Stop the project - not permanently, just long enough to examine the project in detail before things get worse.
2) Assign an evaluator - a disinterested party is assigned to perform an honest and unbiased appraisal of the project and what is going wrong.
3) Evaluate the project - the evaluator takes the lead in doing a complete dissection of all aspects of the project, what is being done right and what is going wrong.
4) Evaluate the team - examine the people working on the project and determine if all are suited to their jobs and if all are performing at the appropriate level.
5) Define minimum goals - determine what is considered to be the minimum level of achievement that will be considered a success.
6) Determine if the minimum goals can be achieved - if the minimal level of success is not possible, then the decision must be made to terminate the project.
7) Rebuild the team - this step has two basic components. Personnel changes if necessary and reinvigorating those who are going to remain part of the team. One of the greatest tasks is to overcome the defeatist mindset.
8) Risk analysis - attempt to identify all possible risks and assign a reasonable probability of occurrence to all of them.
9) Revise the plan - as circumstances change, modify the plan to reflect the different conditions.
10) Create an early warning system that will flag the appearance of problems when they are not yet serious.

These ten steps are each the topic of a chapter. Exercises for further practice are included at the end of each chapter, although no solutions are given.
I enjoyed the book; it contains a lot of sound advice on how to right a rudderless software project. Most of the advice will work only on a project that is not yet seriously out of control. Quite frankly I don't believe that a ten-step plan like this is powerful enough to get the most dysfunctional death marches back to a point of potential profit. Therefore, while I believe that the advice is sound, it is limited in scale, where the measurement is of the level of dysfunction in the project. On that basis, I can recommend the book.

Catastrophe Disentanglement : Getting Software Projects Back on Track teaches the kind of skills you hope you never have to use. It's something like taking a CPR class for project management. You hope you never have to administer CPR in real life, but when you do get put in that position, you're really glad you have that training to fall back on. That clear, logical list of steps can mean the difference between life and death. In the world of project management, the skills taught in this book can save projects and careers.

This book differs from traditional project management books in that it focuses on corrective rather than preventive measures. The author teaches two critical things. First, he presents a set of criteria used to recognize a project that is in need of rescue. This is an important step! Once a project is identified as seriously out of control, you can apply the steps presented in this book to bring it back on track and guide it to a successful completion. This book will give you the reasoning and courage necessary to make hard decisions.

Table of Contents
Chapter 1 An Introduction to Catastrophe Disentanglement
Chapter 2 When Is a Project a Catastrophe?
Chapter 3 Step 1--Stop
Chapter 4 Step 2--Assign an Evaluator
Chapter 5 Step 3--Evaluate the Project
Chapter 6 Step 4--Evaluate the Team
Chapter 7 Step 5--Define Minimum Goals
Chapter 8 Step 6--Can Minimum Goals Be Achieved?
Chapter 9 Step 7--Rebuild the Team
Chapter 10 Step 8--Risk Analysis
Chapter 11 Step 9--Revise the Plan
Chapter 12 Step 10--Create an Early Warning System
Chapter 13 Epilogue: Putting the Final Pieces in Place

I would recommend this book to anyone involved in software projects.

Good book, good subject, well covered. The book builds an organized process around the rescue of a failed (or failing) software project. The steps are easy to read and understand, and seem well thought out. Some good methods for identifying projects headed for serious trouble. Also, some useful guidance on how to handle political (not just technical) problems. Obviously, the result of significant experience. Well recommended.

There are plenty of books that try to help you keep your project on track. But what happens when you are sitting on a catastrophe and you don't know how to salvage it? E. M. Bennatan fills a necessary niche with the book Catastrophe Disentanglement : Getting Software Projects Back on Track.

Contents: An Introduction To Catastrophe Disentanglement; When Is A Project A Catastrophe?; Step 1 - Stop; Step 2 - Assign An Evaluator; Step 3 - Evaluate The Project; Step 4 - Evaluate The Team; Step 5 - Define Minimum Goals; Step 6 - Can Minimum Goals Be Achieved?; Step 7 - Rebuild The Team; Step 8 - Risk Analysis; Step 9 - Revise The Plan; Step 10 - Create An Early Warning System; Epilogue - Putting The Final Pieces In Place; References; Glossary; About The Author; Index

If you're in IT for any length of time, you'll be part of a project that is massively over budget or late. Rather than just continue the death by 1000 cuts or a quick mercy killing, Bennatan presents a ten step process that allows an organization to take a (hopefully) objective look at the project and decide what can possibly be saved from it. I was impressed that it wasn't a long drawn-out procedure either. The plan calls for an evaluator (or a small team for huge projects) to come in and quickly assess the environment... what's been done, the climate of the team, and what could be redefined as a "minimum system". At the end of this process, the organization should be able to either kill it off with the knowledge that it can't be saved, or continue on with a redefined set of deliverables that are achievable. It won't be everything that was originally wanted, but it will be more than you'd get by letting it die. I was also impressed with the "What Can Go Wrong (And What To Do About It)" section in each step. He doesn't present this as some cut and dried panacea that will flow smoothly every time. It may not be an easy task, but the book will give you the help you need to make it all work.

Definitely a book that is worthy to be on every IT project manager's bookshelf, as you *will* need it some day...

Good for someone who is just starting to use CATIA V5

It is an excellent book for beginner. It lets you get into Catia easily. It is important to make things simple for beginners. This book does a good job of making things simple.

This book offers the principles needed for any Catia user, both experienced and new, to be able to obtain a firm understanding of Catia V5. It teaches through easy-to-follow examples and illustrations. It was well worth the money.

A good book is the one that doesn't require an engineer to understand. This book is excellent! It slowly guides a beginner step by step away from frustration and closer to satisfaction. However, the minus side is that it doesn't cover any electrical application. I would pay triple the price if this book had electrical coverage.

This book is a good introduction to Catia. The steps taken and the end result of the book is good and successfully takes you through the basic workbanches. However much of the book is waisted with repetition and over worded explinations for the simplest tasks. The illustrations, typography and loayout are typical home-word processor stuff (clearly an accademic project) after the first chapter the lengthy explinations take far to long to get through and you find yourself skipping them and just getting on with the task. At the end of the day there dont seem to be any other books out there so this is probably your best bet, but I was still left with a few basic problems that were not covered. This book could probably have been edited down to half its size if the wordy introductions were cut out and you would be able to get though it much quicker - after this work book you are left with both a need to learn all the workbenches covered in more depth and many many more workbenches to learn.

I read this book and was able to configure two 1720 routers to communicate over a WAN without any problems. I would suggest getting one of the CCNA books for a reference guide. This book does not go into great details about the commands.

The author did a great job of presenting the relatively basic information on configuring Cisco routers. You will find quite a few useful IOS commands discussed in the book that will want to keep it as a handy reference. I would also suggest looking into getting "Cisco IOS for IP Routing" by Andrew Colton. That book would take you deeper into mechanics of modern routing protocols (EIGRP, OSPF, IS-IS, BGP), along with a discussion of Cisco IOS commands.

These authors know how to write technical literature that did not confuse me!

Our company uses IPX and Appletalk for various departments although we are moving with haste to an all IP shop. I found this book to help me with building a multiprotocol network and to better understand the details of IP routing. The book covered IP routing in depth and covered enough of IPX and Appletalk to help me optimize my network. I found the example network with the full IOS configuration files quite useful.

There is the CCNA certification which takes you down the path to learning about routers, LANs and WANs, but what if you don't want that you only need to know how to configure the router. The Cisco Pres has put together the book that tackles that very subject.

In 350 plus pages you'll begin with a good breakdown of the OSI model followed up with the basics of how to configure the router. The information has screen shots to show you what things should look like.

After that you move in the always challenging world of TCP/IP with routing protocols and access lists. This section has a great deal of information but you may want to check other sources for more detailed information.

You also go into areas like AppleTalk with LAN and WAN configuration, IPX, SAP and basic management of the router including time control. While most of the book is geared towards the beginner all skill levels should be able to find some useful information within the book.

I found that the information seems to be up to date including topics like Network Time Protocol and Simple Network Time Protocol. Overall a very good value for the money.

Who would have thought that a 350 page book on routing could be so comprehensive? This book is a perfect place to start for MCSE's who want to move onto the 'good stuff' - routing with Cisco routers. Use this and the Sybex CCNA Study guide and you'll get through the test no problems.

I think you must buy this excellent book about grasses with a lot of good photos.

Excellent and complete information about ornamental grasses. A great book.

Thirty pages on the botany, anatomy, and classification of grasses. Twenty pages on native habitat, thirty pages on designing with grasses, and twenty pages of growing and propagating grasses. 170 page encyclopedia listing 400+ species / varieties of grasses. Each species is described in a paragraph or two of text along side a clear photograph of the plant. In the back of the book, you find a 2 page glossary, 5 page bibliography, 2 page grass nursery listing, USDA and European hardiness maps, and a complete index of all grasses by common name. Very complete book.

As a bonus, the book is also filled with awesome photography.

If you garden with ornamental grasses, this book is a must buy. Excellent information, well worth the money!

This is such a wonderful informational book... AND ... a gorgeous coffee table book. It is terrific from beginning to end! If you like or are interested in, or even thinking about Ornamental Grasses ... then THIS IS THE BOOK FOR YOU! I can't imagine anyone who has an interest in Ornamental Grasses NOT LOVING THIS BOOK, and would be delighted they purchased it. My only concern is that it is going to look dog-earred from my reading it over and over and over again ... which frankly takes away from its beauty on our coffee table.

This book is structured, written, photographed and edited with parallel purpose and effect: communication of the author's respect and regard for the book's subject and for its readers. Mr. Darke sets out to inform and does so with enconomy but in full course; when he instructs, he teaches the novice and gives pause to the critic; when he photographs he shows his passion and inspires with the nature and wonder of his subjects. The book is encyclopedic, yet its prose is always to the point with the agreeable dryness of a good, well-bodied wine. Credible, trustworthy, enlightening. This is the best gardening book I have ever read. Negatives? Only one: Mr. Darke's standards are unimpeachable; those of the book's typographer and designer, however, are not.

Rick Darke's book is typical of his work. It is extremely well written, a detailed, very thorough guide to ornamental grasses, full of helpful pictures as well as information on growing and maintaining grasses. This book should be a classic for decades to come.

The book contains a common-sense approach to software process improvement strategies for most organizations to follow. Wiegers takes the mystique out of the Software Engineering Institute's CMM and offers the CMM as one way of many to accomplish process improvement. He balances technology and process-focus against real-world people issues. Must reading for anyone involved in a Software Engineering Process Group or for senior managers trying to figure out what all this stuff is about. Text is well illustrated by case studies and examples from the author's experience at Kodak

This is a great overview of all the elements of a successful software project - from project planning to system design on up to testing and project postmortem. Many of the topics are covered too lightly to allow a practitioner to use all of Wieger's advice right out of the gate. But that's fine - the book is meant to be a handbook of great ideas from which practitioners should choose, study and implement. Pay particular attention to the discussion on determing project drivers and constraints during the project planning phase - an area usually breezed over, with devastating consequences.

This is a good book for software leaders who need ideas on how to improve the engineering culture in their organization. I thought the Culture Builders and Killers in each chapter were particularly useful.

A practical guideline for building strong and successful software development methodologies.

Wiegers' experience in a relatively small group at Kodak and his practical approach embodied in this book provide sound and strong encouragement for anybody to improve their software processes. There may be no silver bullet, but this book comes awfully close.

This book tells you all the basics of family news letters. It gives you great info on subjects to talk about and naming your news letter.
I have already started my family news letter and so far every one just loves it. This is a good book and it covers EVERYTHING you need to know about starting a family news letter. Buy this book and you don't need to look at any other books on the subject.

I enjoyed the photos of example newsletters, all in different formats. It really got the ideas floating around in my mind. The interview questions and checklists were helpful also. This book really shows how unique a newsletter can be, and I would recommend it to anyone dabbling with the idea of a family publication. I think the original price is a teeny bit high, but the quality of the material is also!

I JUST LOVE THIS BOOK! I learned about it after I had already written a few family newsletters and I wish I had heard about it sooner! The book presents a whole lot of ideas that will get you going. Before buying this book, I had only written family newsletters once a year... but now I'm inspired to write more times than that and in different and more creative formats as well! Writing about your family now will be a treasure for your family in the future. This book will help you if you don't know where to start or if you've run out of ideas. Plus, the quality of the book is so nice... you get your money's worth!

I enjoyed the photos of example newsletters, all in different formats. It really got the ideas floating around in my mind. The interview questions and checklists were also helpful. A nice touch would be the list of words to use for a newsletter name.
This book shows how unique a newsletter can be, and I would recommend it to anyone dabbling with the idea of a family publication. I think the original price is a teeny bit high, but the quality of the material is also.

Shortly after beginning to do serious genealogy, most family researchers want to begin to communicate their findings to others in their family. But an extended family, especially when it's spread out geographically, can mean a lot of individualized correspondence. Often, the solution (at least partially) is a family newsletter. It can be simply a lengthy typed letter, photocopied and mailed in bulk -- but wouldn't you like to turn it into a real "publication," complete with pictures? And these days, if you own a computer and printer of recent vintage, you can find yourself in the newsletter business before you know it. Floyd, who has published half a dozen books on newsletters and desktop publishing generally, turns her attention here to a variety of ways in which family newsletters can be produced with a minimum of layout, font, and graphics skills. What to write about, keeping it interesting, involving *all* your family, "clustering" your news stories, tailoring your writing style, and avoiding possible trouble spots -- it's all here. And so are tips specifically for the genealogist. There's also an enthusiastic chapter about producing e-mail newsletters, designing family Web sites, and the value of "cross-publishing." This very visual volume will appeal to many family historians.

As book titles go, CyberRegs: A Business Guide to Web Property, Privacy, and Patents sounds uninteresting. Fortunately, what the book lacks in flashy titles, it makes up in interesting content. CyberRegs is an engrossing and sometimes angry look at the perverse nature of patent law.

When many people think of the Internet and e-commerce, they think of a series of open and non-proprietary standards that enable computers to speak networking Esperanto. As the book shows, that does not necessarily jive with reality. Many companies have tried to homestead on pioneering technologies and use them to gain a lock on the market. Author Bill Zoellick cites numerous cases -- many still in litigation -- to illustrate this point.

The book starts with a brief background of the nature of copyright and patent law and doesnýt assume any type of legal background or expertise. Zoellickýs writing style is easy going but to the point, and he accomplishes his goal of examining the disruption and instability that the Web has introduced into the world of intellectual property.

Zoellick looks at the Web from many different perspectives, from business and legal to technological and political. While some may think they don't need a book about Internet law and regulations, the reality is that, for any organization doing business on the Internet, there exists the strong possibility that they may be infringing on someone elseýs intellectual property rights.

One of the most controversial issues that the book looks at is one-click patents issued to Amazon.com. The one-click patents preclude any Internet business that has not licensed the technology from Amazon.com from enabling their customerýs to complete their purchasing experience with a single mouse click. The question of whether one-click is even patentable is a controversial one. Those who say it is, feel that Amazon.com is protecting a vital business asset. Those who donýt support it say that it only serves to stifle productivity. Zoellick gives numerous other examples.

CyberRegs also goes into such issues as digital signature and privacy. Zoellick does not take sides, but provides a fair-minded look at the debate between greater and lesser control of privacy and the Internet. The book also tackles such controversial topics as the Digital Millennium Copyright Act, Napster and DeCSS.

In part 3, Zoellick provides an excellent overview of digital certificates. He goes into detail on the parameters around the groundbreaking E-SIGN (Electronic Signatures in Global and National Commerce) act. Many have complained that E-SIGN is extremely light on details and specifics, which it is.However, Zoellick says that with E-SIGN, Congress took the approach that we donýt really understand how to do business on the Internet so issues surrounding authentication of electronic signatures are not necessarily easy problems to solve.With that, Congress restricted government action to the parts of the problem where they are directly involved and required.Congress recognized that for any effective solution, markets need time to develop and patience is required. Although this approach is hard when dealing with Internet time, it is nonetheless necessary.

You donýt have to be a lawyer to appreciate CyberRegs. Anyone who wants to have a business presence on the Net should read this book so as not to get involved in a legal tussle. While John Grisham may own the legal fiction market, CyberRegs is as close to a non-fiction legal thriller as you can get.

I am a senior engineer for network security operations who frequently reviews technical books. I was hesitant to read "CyberRegs," given its "Business Guide" subtitle. Noticing the book mentioned controversial topics like the Digital Millenium Copyright Act (DMCA), Napster, and the DeCSS case, I decided I'd give "CyberRegs" a try. That proved to be a wise decision, and I strongly recommend this book to anyone worried about the future of the Internet.

The book is exceptionally well-written, with a clear style and a welcome lack of typos (gasp). In a former life I read plenty of boring, repetitive policy books, but I had no trouble digesting "CyberRegs."

The book is arranged around the themes of copyright, patents, electronic signatures, and privacy. "CyberRegs" gives both sides of each argument, but wisely includes the authors own helpful opinion. (I was pleased to see the author share many of the security community's views on the DMCA, Napster, and so on.) Because Zoellick presents balanced arguments, readers will understand the opposition's complaints and can more effectively counter them.

"CyberRegs" was written to help business people engage in the debates and legislation shaping the Internet. Along the way the reader gains a solid historical understanding of how we arrived at the current state of affairs. Would you believe that software or business methods weren't patentable until recently? Would you believe the United States was the world's most egregious intellectual property pirate until 1891? Given this background, readers gain a sense of why policies developed, and how one can help influence the present and future of the Internet.

I found no major weaknesses in this book or its arguments, but I have two technical/security comments. First, "Web bugs" can be used to transfer more information than an IP address; some use "Web bugs" to validate email addresses. Second, giving customers access to data collected by businesses opens bigger doors for malicious hackers to manipulate that data. Readers may share these concerns, which the author doesn't address.

"CyberRegs" seems marketed as a "business guide," and speaks in part to "business people." As a technical person, I gained the knowledge needed to better defend my opinions on copyright, patents, electronic signatures, and privacy. Technical staff looking for the "why" of state of the Internet will probably love this book -- I certainly did!

(Disclaimer: I received a free review copy from the publisher.)

This is a complete primer on intellectual property and its value to the enterprise. Key issues that are addressed include:

Digital Millennium Copyright Act (DMCA)- this is probably the most important discussion in the book because it continues to be controversial.

Complete discussions of all aspects of intellectual property law as it pertains to cyberspace. The clarification of the protections afforded to patent holders that are not given to trademark holders is invaluable. In addition, I learned much about the value of patents and how a business model can be developed around patents alone. I particularly liked the discussion of patent ownership (employee inventor vs. company to which the patent was assigned). This alone makes the book worth reading.

Case studies - many of the case studies which are used throughout the book focused on pending court cases when the book was published. Many have now been resolved, the resolution of which open more questions and further cloud issues. I'd like to see an update or second edition that provides closure.

Excellent introduction to technical issues. The author has a knack for reducing the key elements into easy-to-understand chunks of information that teach non-technical readers quite a lot about technology.

If you buy one book on intellectual property law from a cyber-business perspective, this is the one to get.

Laws relating to patents and copyrights are always moving targets, but at this time they are running on jets. The speed with which technology is changing how we use things has left the legal system struggling to understand, much less keep up. However, it is a critical part of our society at large, as well as how we do business now and in the future. Therefore, all citizens need to understand the basics of the law and it is unconscionable that anyone in business would not understand the rules of copyrights and patents to a high degree. Yes, it is possible to hire lawyers, but they are expensive and cannot be with you every moment of the business day.
This backdrop serves to demonstrate how critical this book is to the management of the modern business. Since an Internet presence that allows for interaction is nearly mandatory, this could be the most important book you read this year. It already has a place on my best books of the year list for 2002. What makes the book so impressive is that the author pounds home the point that copyrights and patents are not fundamental rights, but are in fact derived under the basic notion of the common good. They are designed to encourage the creators of new things to make them available for the general society, while reserving certain key aspects for the inventors. The case involving the music swapping company Napster is examined in detail without a step up on a virtual soapbox. Zoelick also recapitulates the famous legal case over the video cassette recorder, which went all the way to the Supreme Court, where the decision turned out to be a sensible one.
The end result of that case should provide all of us with an object lesson concerning new technologies. It is clear that fighting the new technologies is at best a holding action rather than an effective long-term strategy. The best solution is simply to ferret out the best ways in which your business can open new markets and profit from the changes. Yes, changes in copyright law take many years to resolve, but in the end, the market and society will get the greatest good, which is the way it must be.
This is a book that should be required reading of anyone in business who makes decisions concerning intellectual property. In fact, some of the chapters are recommended for any citizen concerned about how our society is changing, as the effective resolution of these issues may have a dramatic affect on our economy.

Although CyberRegs has a much wider audience, my perspective of this book is that of a competitive intelligence specialist. The four topic areas covered, from a CI specialist's point of view are illuminating.

The first two topics, copyrights and patents, are the foundation of intellectual property and by extension, corporate and shareholder value. The author's discussion of both copyrights and patents expose loopholes that can work for or against you, depending on which side you are on. One theme the author repeatedly addresses is the fact that copyright and patent law is lagging behind the technology. He cites numerous case studies, all of which you will either applaud or condemn depending on which side of the issue you happen to be. As a CI specialist who engages in "white ops" (collection of competitive intelligence using legal methods), I was somewhat dismayed by aspects of the Digital Millennium Copyright Act (DMCA) because it draws legal boundaries that didn't previously exist. The CI community needs to be aware of this particular law because what was heretofore "white ops" may fall under black ops (illegal intelligence gathering) under the provisions of the DMCA.

The more technical topics, electronic signatures and privacy, are presented in the same balanced and thought-provoking way as copyrights and patents. Having recently read Bruce Schneier's SECRETS & LIES I had some insights into the technical aspects, but the nuances that Mr. Zoellick brings to these topics makes for compelling reading. He manages to raise thorny issues and provide answers from both sides of the issue.

Overall this is an invaluable book that should be read by anyone who seeks to understand the current state of intellectual property laws, the challenges imposed by the connected world, or how the laws and challenges combine to change the playing field. As stated above, the DMCA alone will have wide implications in my profession, and is certain to affect business operations and corporate policy in far ranging ways.

Mr. Gunning has done it again!
Having studied under Phil Gunning and knowing the dept of his expertise this book brought to life real world experiences in a classroom like setting. As a DBA I found the Chapter#8 on "Tuning Buffer Pools" and Chapter #9 "The Optimizer" to be of great help to me personally. This book is a great reference material for any DBA faced with the challenge of daily performance. I was excited to read Mr. Gunning's explanation of the `Utilities" incorporated in DB2 V9. I would recommend this book for any DBA or DBM who needs an in-depth understanding of developing and monitoring DB2 V9.
DeWayne Stansell DBA

This is a great book for developers because covers pureXML and other features and great to for DBAs the chapter on monitoring is a must have when you are in trouble with your database

Just keep in mind that this book is focues on the LUW(Linux, Unix and Windows) version of DB2, I say this because a friend of mine bought for using with z/OS by mistake.

I bought this book because I needed to get up to speed real fast on using the new XML data type and Developer Workbench, and Chapter 2, 3, 4, and 5 contained everything I needed to get started. I also liked the Chapter on the Optimizer and Monitoring and Performance. A good reference.

This book is a must have for anyone who develops application code or administers DB2 databases on the windows/unix/linux platform.

The chapter on understand the DB2 optimizer is required reading because it provides deep insight into how DB2 will go about getting the data out of your relational database. Understanding this is fundamental for performance in your application.

The chapters on monitoring and peformance tuning are also very insightful and relay the authors years of experience in a very straight forward manner. Using the methods described in this book makes it easy to put procedures in place to track the performance of your database over time, and to spot problems before they start.

This book is a "must have".

Mr. Gunning's expertise provided the information I needed about the newest version of DB2. Service Oriented Architecture, in Chapter 6, and XML, in Chapter 9, were clearly written and understandable.