Software Books

I like this book and am still reading it and I think I can pick up lots of skills and knowledge about Web Services. One more thing I want to mention here is that I accidentally hit a button on amazon web pages for purchasing this book so I ended up buying 2 copies of this book, a hard copy and a soft copy. I should get refund on the soft copy becuase I never review it online. The following is the part of the order info for the soft copy:

Order #: D01-8384140-5827130
Subtotal of items: $ 11.99
------
Total before tax: $ 11.99
Estimated Tax: $ 0.00
------
Total: $ 11.99
------
Total for this Order: $ 11.99

My primary reason for buying this book was the eye-catcher word "Real-World Projects" in the subtitle. I'm a professional developer/architect of enterprise size IT-projects and the fastest way for me to learn new things is by using examples. So in fact the "Development Perspective" chapter was the first chapter I've read and found it very useful if you are going to use WebSphere 5 in your project.
I was pleased to see that the next chapter "Operational Perspective" actually deals with questions regarding deployment and configuration. This is something most books are missing and many projects underestimate the importance of these aspects for a successful rollout.
Finally after reading two very useful chapters (written in an enjoyable style), I've decided to give the other chapters also a try and I wasn't disappointed. This book covers all important aspects for a successful webservice project and I strongly recomment it if you are going to start such a project.
During my time as a technical lead at Hewlett-Packard, I've got the opportunity to participate a pretty expensive software architect workshop. I was pleased to see lots of "Does and Dont's" I've learned in this workshop in the "Architecture Perspective" chapter of this book.
I finally ended up in reading all chapters of the book. I haven't read all pages of this book because of my previous knowledge and because of the excellent offered shortcuts within this book. But the time I've spent reading the rest was a rewarding investment. Whatever role you are going to play in a webservice project: you will find something useful within this book.
And finally don't forget: even Grady Booch thinks this book is a must-have. He wrote a nice forword for the book.

If you had to time or money for just one book on Web Services, this would be it. The book truly delivers on different perspectives namely, business, training, architecture, development, operational and "future". You start by learning enough to convince your boss (or clients, in my case) of the benefits of using your approach and then proceed to master the whole XML based implementations as well. Dense read, though: there is enough material in each chapter to cover an entire book. If you are a java programmer, it makes it even better, most probably because the book came out in 2003 when Microsoft .NET was still pretty clueless about all this web services stuff anyway. Even the J2EE world is way ahead of the book in terms of implementation. Still an excellent read, so my only request would be...a second, updated edition!

This book excells in explaining the IBM Toolsets and their applicability in the Web Services and SOA area. Unfortunately they are for version 5 and a version 6.x addendum would be great.
Having said that working the examples into version 6 format is good practice and not too much sweat.
This book provides all the coverage you need if you are dealing with the IBM WebSphere kit (all the IBM Redbooks are also a great help!)

Review:

"Perspectives on Web services: Applying SOAP, WSDL, and UDDI to Real-World Projects" Zimmermann O., Tomlinson M., Peuser S.; Springer-Verlag New York, Inc., Secaucus, NJ, 2003.

This voluminous text is essentially about the classic man-machine relationship model.

The reviewer became interested in this topic and monitored the slowly evolving field until 1962 when he published a paper entitled "Shaping and Controlling Human Behaviour in Man-Machine Systems"; Proceedings of The Institution of Mechanical Engineers, Industrial Administration and Engineering Production Group, Vol. 177, Number 34, pp 935-950; 1963 (1 Birdcage Walk, Westminister, SW 1).

He presented the Performance System Spectrum with Man at one end and the Machine at the other. In between these two extremes he defined and illustrated a multitude of combinations including Simple Man-Machine, Complex Man-Machine, Men-Machine, Man-Machine-Man, Man-Machine-Men, and Men-Machine-Men.


By 1963, time-sharing and remote operator terminals had evolved and the computer systems were mainframe...the personal computer and the Internet, if they were envisioned at all, would have been considered purely science-fiction. In relation to the Men-Machine-Men system, he wrote: "...the total system has become so complex, with so many inputs from and outputs to human(s), that design engineers tend to move towards a fully automated system..." In the more than four decades which followed, the flood of computerized systems (and computer acronyms) increased as anyone reading this can testify. And that brings us to today...and Web Services.

We shall see that Web Services satisfies the definition and is a Men-Machine-Men system. To quickly understand what Web Services is the average reader shouldn't start with the text under review but with an excellent article, "The Web Within the Web," Enrique Castro-Leon, IEEE Spectrum, February 2004, pp 42-46. Examining this paper first and then delving leisurely into "Perspectives on Web Services: Applying SOAP, WSDL, and UDDI to Real-World Projects" will have a higher payoff even for those readers who are experienced software engineers, developers, analysts, and systems architects.

Castro-Leon presents a concise thumbnail view of this emerging concept. He argues that "...dusty, musty databases filled with useful data that would be far more useful if linked with other, equally dusty databases; enormous databases that are locked up inside ancient mainframes and quaintly archaic minicomputers; lonely databases residing on specialized file servers throughout an enterprise (pronounced business); even modern databases on Web servers...(are) stuck in long-obsolete proprietary formats or accessible only through hypermodern scripting languages..." Further, "... Web services are a way programmers can make their databases available across the Web , let other programmers access them, and tie these disparate databases together into services that are novel, perhaps even wonderful..." This, of course, is the basic reasoning for improving the Machine part of the Men-Machine-Men performance system.

"...Web browsers have liberated us from the tyranny of specific hardware and the near monopoly of the Windows operating system...(because of)...the Hypertext Transfer Protocol, which provides a standard for the way Web pages are downloaded from a Web site to a computer, and the generic nature of Web pages themselves..." The Hypertext Markup Language (HTML) ",...was designed to encode things that will be viewed by people, rather than processed by another machine. HTML mixes formatting commands...with data because it was designed as a display language..." Castro-Leon continues: "...if Web services are to build powerful networks of collaborating databases and services, the first step is replacing HTML with something more compatible with the world of databases, something that can be understood by another computer...such a new language has been developed...a subset of HTML, called XML, for Extensible Markup Language..."

This movement to improve the Machine subsystem did not end with the invention of XML. There had to be some mechanism to move XML data rather than HTML across the Internet. This was SOAP --- Simple Object Access Protocol --- a generic wrapper which is an envelope recognized and accepted by Web browsers and servers. Together, XML and SOAP give Web Services interoperability.

However, another specification was needed called UDDI ---Universal Discovery, Description and Integration --- which, as Castro-Leon states, "...lets Web Services look for databases (by Machine) in the same way that Google lets humans look for Webpages..." But the process didn't end with the development of UDDI. There had to be a standard which allowed the Machine to determine what is at a site once it has been identified. This standard was WSDL --- Web Services Description Language. All of these protocols took years to develop....and the improvements continue to this day.

Having presented an overview of Web Services from Castro-Leon, it is now time to review the 648 page text entitled, "Perspectives on Web Services: Applying SOAP, WSDL, and UDDI to Real-World Projects" This is in essence a "how-to" or a "cook" book, using an old world term, which goes into exquisite detail about how these software elements work inside the Machine and how to utilize them effectively and profitably. One might describe it as a "Web Services for Dummies" type of text but written at a much higher intellectual and professional level. The occasional humor is within acceptable limits and not extreme.

In the Men-Machine-Men model, the Machine is represented by all of the computer systems in the Internet world-wide and includes SOAP, WSDL, and UDDI as software and all of the hardware world-wide. The Men at one side are all the humans dealing with the Internet as users while the Men on the other side of the Machine are all the software people feeding the Machine world-wide with data and graphics which are then manipulated inside the Machine by SOAP, WSDL, and UDDI. You can visualize that the users might have a population of millions and possibly billions of individuals and the software people might represent a population of millions of individuals. That is why this volume on Web Services is an important reference today as the system is being implemented --- but there is a cautionary poem by the systems guy Kenneth Boulding regarding this Machine:

A system is a big black box
Of which we can't unlock the locks,
And all we can find out about
Is what goes in and what comes out.

Perceiving input-output pairs
Related by parameters
Permits us, sometimes, to relate
An input, output, and a state.

If this relation's good and stable,
Then to predict we may be able.
But if this fails us - heaven forbid
We'll be compelled to force the lid!

Having forced the lid --- you are now inside the Machine! The book is structured using the "goto" branching command. The authors encourage the reader to study a section and then decide to continue on or "goto" a different section. In fact, they suggest not reading from cover-to-cover at all but selecting those parts directly related to the reader's job role.

The text is neatly divided into Perspectives chapters which follow a typical project sequence: Business, Training, Architecture, Development, Operational, Engagement, and Future. The authors state that they and their anticipated readers are "technical people" and their approach in writing was shaped in that way

Chapter 1 is The Business Perspective. In 30 pages they discusses definitions, EAI (Enterprise Application Integration), B2C (Business-to- Consumer), B2B (Business-to-Business), A2A (Application-to-Application), H2A (Human-to-Application), and potential inhibitors to decision-making. The Case Study of a fictitious insurance company is introduced which will be threaded throughout the book. Some of the flowchart models are clearer than others.

Chapter 2 is The Training Perspective. A better term for this perspective would be the "technical information" found in a manual used by individuals for self-instruction to learn about the software. 123 pages are devoted to a tutorial of concepts and technologies but the reader is not expected at this point to be able to apply them.

There is an overview of WebServices concepts and detailed information on the XML markup language including namespaces and schema. Attention to given to SOAP message formats and encoding. This is followed by WSDL, the interface description, containment structure of WSDL documents, and binding-related document elements. There are descriptions of UDDI's registry structure, identifier bag, category bag, binding template, tModel structure, linking to a UDDI registry, an API (Application Programming Interface) overview, and brief mention of WSIL (Web Service Inspection Language). There many well-designed coding sheet examples which would make sense to experienced programmers but probably not to novices.

About 86 pages are assigned to Chapter 3: The Architecture Perspective. The authors provide an introduction to Web Services architecture oulining paradigm changes, J2EE (Java 2 Enterprise Edition) and defining Web Services as the software part of the Machine. WSA (Web Services Architecture) is explained with the use of stacks and a disclaimer is provided since not all of the terms are universally accepted. WSA building blocks and component walkthrough is covered. Explanations are given for WS principles, Generic vs. Generated API, design patterns, business patterns, architectural patterns (microflow, intermediary, and interceptor/pipeline) and process choreography including public-to-private process mapping. Architectural decisions are outlined along with service matchmaking. In addition, NFRs (Non-Functional Requirements), gaps and countermeasures and SOAP Section 5 encoding are discussed. Finally, XML-based, WS, and application layer security are explained. There is a useful FAQ (Frequently Asked Questions) section ending the chapter.

Chapter 4 is The Development Perspective. Consisting of 192 pages, this chapter has a considerable amount of meat and consequently may cause indigestion for the vegetarians among us. The authors state that a reader should have a "...solid reading comprehension of J2SE and J2EE APIs..." It is written at a fairly deep level of detail related to reader motivation and categorizes this interest as: casual, steady or junkie. There is an emphasis on "goto" branching. Most of the coding examples are also found on Springer websites.

The introduction to the development of WS in Java presents the WebSphere Studio Workbench and Eclipse.org. WebSphere SDK (WSDK), the Emerging Technologies Toolkit (ETTK), and Apache SOAP 2.3 are described with some caveats regarding known flaws. This is followed by JAX-RPC and Apache Axis, definitions, an introduction to WS for J2EE and JSR 109 and the WSDK Toolkit.

At this point, starting on page 259, the first example or case in The Case Study is considered --- all the prior pages having been dedicated to technical information to bring the reader up to speed. The authors refer to the example as a "sample" and it is, of course, a simulation where the case problem is run on the WS model being described so the reader can learn how to do it later in real-life. More precisely it is a training simulation testing (with some debugging) of the solution provided by the authors....the author's terminology will be used here.

The case scenario involves several fictitious insurance companies. In terms of the Performance System Spectrum, this scenario deals with the Men-Machine-Men model with Men being Internal Users and the Machine processing risk and fraud management matters. Business logic requirements are considered and "The Great Debate" over Apache Soap or JAX-RPC occurs, followed by configuring and building the sample. To build RPC/Encoded Services for Java the bottom-up and top-down approaches are reviewed. There is a discussion of building EJB (Enterprise Java Beans) WS with Apache SOAP, and using the WS Wizard. The process of exploring and modifying generated files is described. Building EJB WS with JAX-RPC and JSR 109 follows, In addition, exploring generated server side files, updating the project build paths, modifying generated files, and testing the deployed service are briefly delineated.

The reader is encouraged to build RPC/encoded services from WSDL first creating WS from WSDL using Apache SOAP and then testing the WS client. There is also the process of creating WS from WSDL using JAX-RPC/JSR 109 and updating the WSDL document and installing the SOAP Router, and finally testing the WS. A section is devoted to programmatic access to WSDL, using the WSDL4J toolkit, testing the JWSDL application and creating JWSDL clients with JAX-RPC and JSR 109. The reader learns to use WS-Inspection to build service indices from Java and also with Apache Soap and to configure WSIL4J.. There many excellent figures illustrating this part of the simulation. At this point, the text moves ahead to the use of UDDI.

There are discussions of UDDI access from Java and browsers, using UDDI with Apache SOAP and also with JAX-RPC and JSR 109, using other Web Services bindings, creating a document/literal Service from WSDL and a document/literal Service Client. A secton is dedicated to orchestrating Web Services and use of the Process Editor. The reader learns about using attachments with SOAP, using SOAP headers and finally exporting the completed sample. While space is assigned to finding more information, there isn't any for FAQ which could have been useful at this stage. Some System Administrators have argued that constructing the application in this chapter was the easy part. The next stage deals with implementing it in a production environment and might be viewed as more difficult.

Chapter 5 presents The Operational Perspective which the authors have truncated to 79 pages and rely on the experience of the reader to fill in some technical gaps. There are many specific references to coding samples in .zip format on Springer websites. This chapter deals with the system architecture hosting the software and we are now deep inside the Machine in the Men-Machine-Men system --- and continually aware of Boulding's admonition: "....If this relation's good and stable, Then to predict we may be able. But if this fails us - heaven forbid, We'll be compelled to force the lid!..."

There is a discussion of topology, standalone topology, additional components,and clustered and managed topology. Reference is made to the Access Management Subsystem, load balancing and high availability support. At this point, the Case Study simulation of a fictitious insurance company continues and for the remaining pages is interspersed with tutorial information .

There are explanations of Deploying Web Services, the WebSphere Application Server, deployment and configuring the application server. There is information on JDBC configuration, JAAS authentication and Cloudscape, and restarting and testing the installation. Next comes Deploying Services, wsadmin, ANT; working on the private UDDI Registry, including configuring and adding WSDL documents to the UDDI Registry. Descriptions are provided for testing, clustering, and node agents; working with the IBM HTTP Server, starting, testing clusters, and finally cold standby.

Attention is given to Securing the WS Implementation: security threats, countermeasures, WS-Security, and future WS-Security extensions, Securing WS with HTTPS and SSL --- as the simulation continues. The chapter closes with the WS Gateway and how to configure it, deploying a WS to the Gateway, updating and client testing. Frequent mention is made of specific websites to support the simulation so the reader is not completely alone with just the text.

Chapter 6 is The Engagement Perspective of 27 pages and a typical reader would sense that the end is in sight!! This chapter reviews many technical points emphasized in the Case Study simulation and adds the following: Planning a WS Development Project, Outlining Requirements and High Level Design, Planning and Staffing, Running the Project, including testing and going live, Success Factors, Elements of Risk,lessons learned and design advice. There is a final look at the Case Study simulation.

The Future Perspective appears in Chapter 7. The authors briefly identify SOAP Version 1.2, WSDL Version 1.2, UDDI Version 3.0, and grid computing for the immediate future. The Semantic Web including RDF and OWL are mentioned and they provide mid- and long-term visions.

The chapter concludes with "Now enjoy the first project in which you apply and exploit this hot technology!"

There are rather complete coding steps, flowcharts, and screen displays in the boilerplate content of the Appendix including: Building the Case Study Policy Systems, Java to XML Mapping, and C# --- and 87 References for those who desire additional background.

As Castro-Leon in summarizing his IEEE Spectrum article said: "...the semantic Web's benefits won't be seen for some time; Web Services are here today...it will connect almost every island of data, software, and device on the planet..." The reviewer believes that this volume which introduces Web Services is a valuable asset in the drive to improve the Men-Machine-Men system which we call the Internet.

Leonard C. Silvern
Systems Engineering Laboratories
Clarkdale, AZ

I bought this book after having owned the editing program for about a year........and suffered all the heartache that can occur if you do not know what you are doing....including crashing Windows.....finally located this superb manual that is user friendly and written by a pro in the field. Since that time, I have produced several projects that are startlingly complex.......and am currently being PAID to produce VHS/DVD productions. A MUST BUY if you purchase Pinnacle Studio 8.

Well laid out and quite thorough. Really a must-have if you are new to Pinnacle Studio DV.

I've had this book for less than a day and it's already paid for itself. I bought Studio 8, which now has been updated to version 8.10 (eight point ten, not 1.0). I figured even if the book were good for the very first versions of Studio 8, OK. As soon as you open the book, you see that Jan refers to changes made as recently as v. 8.6; I was thrilled. This is a brand new book/edition. Studio 8 ships with a 258 page manual right out of the box, which is somewhat amazing for a piece of software like this, but admittedly, the manual is very remedial. This book, from the earliest pages, delves into some seriously useful components within Studio. I have a bunch of these Visual QS books; I'm always ammazed at the bang for the buck in every one of them, this one no exception.

This book is a MUST for anyone new to Pinnacle Studio. I bought the software thinking I could "figure it out on my own"...Not!
This book has saved me!

This book tries to sell itself on the photos of the GUI that you will be using. The photos are a bit small, but good enough when you really need them, which is rare, because the author does a wonderful job of explaining how Pinnacle works. I recieved the software with no documentation and within a few minutes of opening this book I was well on my way to creating DVDs out of some digital movies. The author does a great job explaining both the simple and the complex parts of the software. And refreshingly, the author actually offers opinions on better ways to do some tasks. This is a good buy for anyone using this software.

What is the internet?
How and when did it begin?
Where does the network go?
Who originally thought of the concept?
Why is the internet useful and necessary?
Was Al Gore involved?

All these questions and more (minus the Al Gore one) are in The Pocket Guide To The Internet.

From ISPs to Packets, from AOL to telnet, and emoticons to netiquette, it's all present. There's a wealth of knowledge in every chapter, and the steps are slow enough for all. In fact, many of even the most novice users of the Internet will find much of the information mundane.

The book provides page after page of helpful information, providing a multitude of web addresses, acronyms, and definitions that, if anything, provid a sort of printed dictionary/encyclopedia about the internet.

This is a great resource for someone starting at ground zero with no knowledge whatsoever.

The "concept" of the Net is very important for the uninitiated. Your zeroing in on how the Internet should be viewed in the mind's eye is excellent. It's the idea or the "vision" of the over-all system as a "place" that is expanding its own boundaries in all directions gives your readers a sense of the sheer "enormity" of it all. And yet, all of it is reachable by a simple wire with a tiny, plastic push-in-and-click wall plug!! Marvelous. Robert M. Jackson, Jr.

I'm about half way through your book. In fact I'm on page 148 beginning Web Culture. I have found your book to be very informitive. Was very interested in the section on Gopher. Tried to get information on swollen joints, but reread and found that I needed to use WWW and Exite to pull it up. As I read your book I try the new reading out on my computer. Again thanks for the information.

Al Witte

I recently bought your paperback (The Pocket Guide to the I'Net) at the local Wal-Mart. Of course I was skeptical, since I've read or scanned through a dozen how-to books and intro-to books in my endeavours to learn better and train better.

But ... something about your style engaged me. So I bought the book. Halfway through it I think I know what it is I like about your text ... you're an Internet teacher who agrees with *me*!

I was talking with Wendy Green last week (literally talking, not virtually) and described my reaction to your book. She encouraged me to drop you a line. She says you lurk on the misc.writing newsgroup from time to time and she recognized your name. (What a high-traffic newsgroup!)

I webmaster for my company (www.ag.org) and am also responsible to train anybody in our midst how to understand and navigate the 'Net. For a good part of the last year I lectured to our local Internet users' group and now moonlight at a local cybercafe teaching Internet classes for paying customers. So, my plate is full and I'm happy to find material which so nicely augments my own presentations!

For a while I struggled with the relative worth of helping people understand this beast. Especially when they're *paying* to do so! After all, these people just want to know how to send email and 'surf the Web', why should I waste time talking about its military roots for goodness sake?

So, if for no other reason, I appreciate your book for the affirmation I've found there. Of course, I don't *always* agree with your presentation or your choice of wording, but then who agrees with *anybody* one hundred percent? I can't argue with the facts of your text, though, you have certainly done your research! (I only wish it was footnoted! ) At heart I am a teacher and no matter what I do or where I'm at that's likely the role I've fallen into. From one teacher to another: you done good. (Of course, I'm sure you know that! The royalties should speak well enough!)

I bought your book 'Pocket Guide to the Internet' (Pocket Books) a couple of months back here in Dhaka, Bangladesh, and enjoyed it greatly. It was a great introduction to the Net. Thought provoking and nicely written. I continue to use it as a reference.

The fact that everyone uses the web in some way or another, this is a good book to have. I am a computer junkie and this book definitely kept my head afloat. But I highly recommend you read "A Branded World" by Michael Levine. This author really knows what he's talking about. The next time a company hands out memos to its employees, make sure "A Branded World" is on the top of the page!

Bob really knows what he is talking about. He gives a lot of wonderful easy to read tips on how to get your name recognized on the web. He is very clever & witty and fun to read. I recommend you get a copy now.

The Internet offers a lot of "get rich quick" schemes, and advice based on 20th-century advertising techniques. However, what worked in the past century and before the Internet, is not working now. From "Cluetrain" to "Gonzo Marketing," there's ample proof of that.

But, if you're self-employed and/or building your online identity... how do you start? And, if you've been online for awhile but you're somehow missing the boat--or at least your audience--what do you do without a corporate advertising budget and webmaster/advisors to help you?

The answer is simple: You get this book. And read it. I've read Chapter Two at least ten times, and I'm still making notes about what I'm changing on my own website (online since 1995, and boy-oh-boy have I made mistakes! *sigh*).

Baker's books are not for wimps. And, they're not the sitcom version of business, where you spend a few days creating a by-the-numbers clone of others' websites, and then sit back expecting income to flood in like clockwork.

Instead of being a book that you read, say, "Oh, that made some good points," and then put on a shelf to collect dust, this is a book that you'll read, re-read, and keep close to hand. Baker's book is information-packed. There is no way that you'll learn it all in one reading, or even two.

This is easily in the top five books that everyone who is (or wants to be) in business online MUST own. Sure, you can read the sample chapters at Baker's website, or take this book out of the library, but it contains too much important advice for that. And, you'll refer to it often, as well.

Buy this book. Roll up your sleeves and do what he says. It's how to succeed on- and offline, in the 21st century. It's not your parents' business era anymore. Learn the new rules in this book, and give yourself a genuine chance for success.

Baker's information would be cheap at ten times the price; it's already helped me to increase the daily hits at one of my websites from 500/day to over 800/day. And, I'm still on Chapter Three!

I haven't made it past chapter 3 and I have already read a wealth of helpful information on branding your business name and branding tools. The author provides a detailed, step-by-step guide to branding and marketing techniques one can use both online and offline. This book is a must read for first-time start-ups and entreprenuers.

This is a great book for those of you who want to make a name for yourself on-line. Bob has an abundance of ideas to get you started and to keep you going as you explore the ways to market yourself online. Bob has a very witty and humorous way to keep you interested in what he has to say. I think Mr. Baker is on the cutting edge of where the future of online marketing is headed. I highly recommend this book.

Very readable and highly useful book. One major hit. It is ironic that the author complains about the symbols in other books. For queueing he invents his own, instead of sticking with standard practices. This is very fustrating to readers that have other books on queueing and need to compare.

The book is well written and "user friendly". As Dr. Gunther said during a class I recently attended which is based on this book, "You will not look at performance analysis the same after taking class." -- or reading the book. He was correct ... I don't. My views have changed for the better.

The only mark against the book I have is it doesn't have an example section (with answers for each example as an appendix) at the end of each chapter to help people apply the concepts they learned reading the chapter.

The author provides good practical coverage of queuing concepts and then goes on to show how to use queuing models.

I found it interesting that he gives an example of typical computer time periods scaled up to human proportions. If a computer clock speed in nanoseconds were analagous to seconds then a main memory access of 100 cpu cycles would be like some minutes and a disk access would be like some months.

His coverage of queuing concepts is very accessible with a minimum of math.

Scalability is frequently discussed concept that often is not very well quantified. He has the most original approach to quantifying scalability that I have seen.

A queuing modeling package called PDQ is also provided with the book. The source code in C is provided for the PDQ package.
There are some PDQ examples within the book. This is a real bargain because certainly the PDQ software is worth much more than the cost of the book.

If you have and interest in capacity planning and performance analysis (especially if you work in this area) this is a must have book.

If understanding and managing computer systems performance is in your job description and you can only buy two books, this is one of the two (the other is Raj Jain's, "The Art of Computer Systems Performance..."). Neil Gunther's book is not just another tome on queueing theory. Immediately useful methods and formulas are presented in the context of real problems. The two chapters on instability in systems and scaling of multiprocessor systems alone make the book worth its price. Readers need to know that there is some math in the book (there is just no escaping it) and that some of the cited vendor products are becoming dated. The Web site associated with the book contains many items of current interest, an errata sheet correcting minor errors in the book, and downloadable programs related to performance evaluation.

Although this book's full value will be realized if you understand the C programming language (he uses source code it illustrate points throughout the book and provides a C library for performance analysis on the accompanying disk), anyone with good math skills will gain much from this outstanding book.

The core approach is Performance By Design, which is aligned to product development. His approach, if used properly, will ensure that performance goals are established in the design phase, and are met as a system or software evolves through the development life cycle.

Highlights of the book are:
(1) Through introduction to the foundation of performance: queuing, parallelism and multiprocessor systems.
(2) Coverage of contemporary issues, such as client/server and web system performance,
(3) Unexpected forays into performance characteristics and considerations that I've encountered in no other book. For example, Part 3 of this book addresses subtle issues such as transient analysis, scaling behavior and similar topics. Here the author integrates theoretical physics into performance analysis - while this may seem odd, it only reinforces that much can be added to the performance analysis body of knowledge by drawing from sources outside of computer science. His qualifications for this material includes a Ph.D in theoretical physics, and his ability to clearly explain concepts that are foreign to the average computer scientist or performance practitioner is excellent.

I like the conversation style that the author employs, the way he starts with the basics and builds upon them and the thoroughness in which all aspects of performance are discussed. More importantly, although advanced math concepts are introduced the way they are presented can be understood by anyone with high school or college freshman knowledge of probability and calculus.

For quantification of models, queuing theory is one of the oldest variants, used for simple first feelings with the processes. This book provides the theory of random arrive processes, probability and all kind of queues. The reader is introduced in single queues like m/m/1 and learns how to calculate and forecast the most important statistics as a start. Later on more complex queue systems are explained in detail all with graphs, simple formulas to calculate and enough text to understand the formulas and steps of the writer. At the moment the theory of the single queues cannot solve the problem, the writer uses some PASCAL procedures. At that moment it looks more like a black box to me, but I am sure the writer knows what he is doing!

A superb guide that manages a realistic introduction without terrible challenges to higher mathematics anxiety. My biggest complaint is one of omission -- it deals with networking at the data link level, and doesn't get into more modern networking.

This is a very good book on queuing theory and applications. I have read or looked at dozens of similar books, but find this to be one of the best. ...

There is also a UK/European edition of this book, which is, at the time of writing, in stock with McGraw-Hill Europe.

The UK edition of Practical Queueing Analysis is available, and can be ordered from McGraw-Hill in the US (609-426-5793). The only difference between the USA and UK editions is a diskette that was shrink-wrapped with the US edition. Contact Mike Tanner if you need the diskette.

We as users of the PSM with years of experience in the quality and measurements world tend to over complicate the measurement system we develop. This book is a yardstick and is a good tool to ground you when you are creating the measurements. It keeps your mind in the more simple and effective road to resolving the issues. Remember the old saying, "Keep it simple stupid (KISS)!"; this one helps guide you to accomplishment of this goal.

This is a good solid presentation of the subject that gives a good overview of the several types of approaches to measurement. While I would prefer that the subject matter also focused on software engineering as well, it does a good job of what it was created to cover.

This is a good read for anyone thinking about employing metrics for software projects. I have read several books and articles on metrics, software and program managment, in the last 6 months and this one of the few which was worth reading. Text is easy to read and the message and methods are presented in a straight forward manner. No, you will not find any amazing breakthoughs in software project managment in this book. What you will find is a good foundation for adding metrics which add value to software program management.

There is a wealth of material available from the PSM site, including the PSM Insight application and PSM Guidebook. However this book is not redundant because it is structured as a clearly written introduction to practical software measurement, that includes excellent guidance for implementing it into your organization. In addition, the 304 pages that comprise this book manages to convey the information contained in the existing PSM documentation, and does so much more succinctly.

I found the most valuable parts of this book to be the clearly described measurement model, and the way the authors distinguish between data that is useful to projects and organizational data collection and analysis. This material places PSM in context and is a sound starting point for an organizational SQA initiative.

The case studies reinforces the mechanics of PSM, and also contain advice and pointers for implementing enterprise-wide measurement. Although I've been following the PSM initiative almost since its inception and have read all of the copious materials available, I still gained much from this book. If you're establishing an SQA function or striving for CMM level 4 or above you'll find this book invaluable. The URLs provided will lead to even more material, including a free Windows-based software tool that fully supports the practical software measurement process.

I would rate this book ****** if it were possible. If you are looking for material on how to start a "software metrics program", look no further. This is the ultimate reference on software measurement initiatives. The PSM method is compatible with the CMMI (Measurement & Analysis Process Area) and the foundation for the ISO/IEC 15939 standard. All of the authors are recognized authorities in software measurement and process improvement. Dr. Barry Boehm (COCOMO author) has written the foreword. The PSM process is sponsored by the DoD and the U.S. Army. The book itself is comprehensive, well-written, and easy to read. It provides ready-to-use templates such as "Measurement Construct Template", "Project Measurement Plan Outline", and "Data Verification Checklist". Chapter outline:

1 - Measurement: Key Concepts and Practices
2 - Measurement Information Model
3 - Plan Measurement
4 - Perform Measurement
5 - Analysis Techniques
6 - Evaluate Measurement
7 - Establish and Sustain Commitment
8 - Measure for Success
Appendix A - Measurement Construct Examples
Appendix B - Information System Case Study
Appendix C - Synergy Integrated Copier Case Study

Note: Appendix A provides 14 detailed, complete examples of measurement constructs ("metrics"). Appendixes B and C provide 2 comprehensive case studies (approximately 60 pages).

It would require at least a 2-day workshop to address all the information provided by this book (probably at 10 times its price). You can't afford to miss it if you are more than casually interested in software measurement. Hope you enjoy it as much as I did.

This is by far the best book available on DNS. It is very informative and yet the reading style is entertaining (not fluffy though). Overall, it is a joy to read. The author is able to communicate effectively to both the expert and the novice. Look no further than here for a great DNS reference book. Way to go Ron Aitchison!

After reading several of the chapter sections at the authors website, I needed a bit more understanding about how to install and configure Bind 9 onto our Windows box. I wanted to use Bind on old hardware running NT4. I fired off an email to the author and got several pointers that fixed the problems I was having. I realized the pointers he had given me were all covered in his book. After purchasing the book, I not only found out lots of stuff about what all the parameters are but also discovered how to manage bind over the LAN in a secure way. This book is a must have for anyone that wants to use Bind 9 for the first time. It has helped me several times already.

The Domain Name System is a critical component of any large network or any computer connected to the Internet. While a home user would not need to setup a DNS server, business networks of any significant size would benefit from an internal server, DNS caching router or other components. This book takes the reader through a very good explanation of DNS and BIND, how it works, how to set it up, how to test it, and how to troubleshoot it. There are many books on DNS and BIND but most either assume a certain level of prior knowledge, provide theory without implementation information, or provide implementation information without any theory so you have no idea how to troubleshoot a problematic implementation. Author Ron Aitchison does an excellent job of discussing both theory and implementation in this book so you end up with a thorough education. He even covers the implementation of a secure DNS server. This book actually takes the reader from a level of complete novice through advanced DNS administrator and does an excellent job of it. Pro DNS and BIND is highly recommended and one of the better books on the subject available.

Ron Aitchison's Pro DNS and BIND packs a whopping 550 pages of material which is easy to read for the novice or ongoing DNS administrator, and which is very well written (I greatly enjoyed the author's style). After a short introduction in which I learnt some interesting facts about the provisioning of the root servers, the author implements a first zone describing the necessary concepts such as resource records, queries and zone transfers very clearly, followed by the different types of DNS setups (master, slave, caching, forwarding and stealth servers); these are covered in depth in chapter 7. Chapter five covers IPv6 and its relevance to BIND. Throughout the book, references to other DNS server implementations are given, but the primary focus is of course BIND 9.3.0.

Aitchison leads the reader through detailed installation of BIND on Linux, FreeBSD and even Windows (ISC has an installer for Windows in its portfolio), after which common DNS tasks are discussed (how to delegate a subdomain, how to define SPF records, etc. read it on-line here) as well as a chapter on tools.

The third part of the book is dedicated to securing DNS configurations with topics ranging from simple administrative issues (chroot jails) through securing DNS updates and zone transfers with TSIG and DNSSEC.bis which is covered very extensively in chapter 11.

Chapters 12 and 13 provide extensive commented references on BIND configuration and Zone files. There is of course plenty of on-line reference information on these two topics (including the author's very good DNS for Rocket Scientists) but I like to have reference information on hardcopy (in the event my DNS servers fail, and I can't reach the on-line documentation :-) )

In part 5 the author shortly covers programming with the BIND API and the resolver libraries, and he follows that with an interesting chapter on DNS Messages and Records, good to have if you want to sniff your way through DNS traffic.

The publisher's web site carries a sample chapter as well as the source code to the book which is also available in TAR format on the author's web site together with complementary information and pointers to further resources.

My only complaint about this otherwise excellent book is that on two or three occasions I read a paragraph that I thought I'd just read before; some duplication must have taken place (or I was tired). For the next edition, I'd like to read a chapter on interoperability between BIND and Microsoft Windows DNS servers, specifically regarding DNSSEC.

This book is an absolute must have for anybody who needs to understand DNS in the first place (irrespective of the implementation he or she plans to use), and it is a must have for a systems administrator who is either intending to deploy or has already deployed BIND 9.3. I wish I'd read this book before the first mentioned above.

while the reference from Paul Albitz/Cricket Liu is sometimes hard to read and long winded, this text from Mr. Aitchinson covers everything and yet stays very clear and simple. I could configure and start a caching only DNS server in less than 30 minutes (well, after omitting the first few introductory chapters ;-). If you want to look up sth., there is also a big reference section. There is also an errata-page at:
http://www.netwidget.net/books/apress/dns/notes.html

I also found this book *much* more useful as the first, because of the fact that it is much more up-to-date!
I can recommend this book to everyone, who
*) wants to install/configure/start/maintain a DNS server
*) wants to get informed about the Domain Name System in general

Up to now, this book is really an insiders' tip!!

I have read several books on this topic, but this book was very structured wich made it easy to follow. It gave a very clear explaination on both base- and advanced OOP programming concepts. Many things I'v not read anywhere else and many times I yelled 'AHA!' and 'WOW!'. Yes, it was great fun to work trough all the 'Fun with...' examples.
I really can recommend this book, however NOT if you are a beginner!
I also learned that I'm a Generic Type, because I drink a lot Of T. :)

This book covers what programmers need to know. The pillars of OOP are presented and clear examples are shown.

I refer to this book often because it gets to the "meat" of things rather quickly and is not for beginners.

My only criticism is that this book's examples are 90% console applications. Nobody uses this in the real world. But I understand the focus is on the code, but I still like the Deitel approach better. Use Windows applications NOT console, take the time to get the screen shots. (Just my opinion).

Don't get me wrong, I can easily translate over what he is trying to convey, but still I see great authors such as Francesco Balena showing most examples with the console window. I don't like this trend. But hey that's me.

Very good book though..

This is best VB.NET I ever had. This book explains OO concept very clearly with easy to understand examples. I am still in middle of the book. So eager to finish till end. Waiting to read more books from this writer. Thanks for Excellant Work.

This book covers just about everything: The .NET platform; VB language fundamentals; OOP; Assemblies and classes. In each chapter the author gives a simplified example and then progresses thru to a complete module. He explains each step in detail and give many of the most-likely errors.

This is not novices. The author expects some level of programming experience with VB, C, C++ being the best. It is also best for a Visual Studio 2005 environment, though it is not required. If this is you and you are looking to move to VB.NET, this book is absolutely for you.

If you are looking for a Visual Basic book that covers a lot more than books like Wei-Meng Lee's Visual Basic 2005 Jumpstart than this book should be at the top of your list. As well as the basics this book is very good at explaining advanced concepts like Interfaces, IEnumerable Types, Generics, Asynchronous Delegates, and Multithreaded Applications. The author has an excellent writing style. He stays on track, does an excellent job at expaining complex concepts, and provides a lot of hints about how the topic he is writing about now is related to the big picture. Apress should also be commended for the graphical layout of the book. It is very easy to find information on a particular topic in this book as all of the book is divided into clearly labeled short sections.

Arsenovski has done a great job with this book. It is clearly written, easy to follow and very practical. A great one to keep on the shelf and reference as needed. The free tools that he covers in the book are a bonus! They really help to get you applying what you've learned quickly.

I highly recommend this book for any .NET developer, not just those who use Visual Basic.

Not a typical Wrox title, generally these tend deal with specific technology in "no-nonsense" fashion. This book has more theory in it and is not technology specific, you will find it valuable if you program in just any version of Visual Basic .Net and any type of application. Not likely to become obsolete very soon, since basic premises of refactoring will continue to be relevant even in upcoming versions of VB.

I am working with group of developers that came to VB .Net from VB6. Currently we are in process in improving the way things operate using some agile stuff. The overall disposition is pretty good, team has already been formed and things like daily stand-ups, client involvement or short iterations are generally welcomed by all. However, when more technical, code level stuff is discussed, there is more discussion (if not opposition). These folks pack years of experience and will not accept that you can teach them their job just like that. There is no way you can force things like unit testing or refactoring. You have to be able to hold your ground and answer all the questions with some good arguments.
This book gives you in-dept view of refactoring with a lot of practical, code examples. This means that you are well prepared to answer any uncomfortable question. It builds up gradually, so it is easy to follow.
Almost every chapter ends up applying the stuff that was just exposed on a sample application with a lot of code. Surely author spent a decent time on this title. You can download the code and see it progress from chapter to chapter. This gives a great insight since you can read and debug the code at the same time and not just some toy or isolated example.
Here is chapter to chapter break-down of the book.

Chapter 1
Intro chapter, defines refactorings end code smells and explains the kind of baggage VB carries because of its origins. Cool section on misinterpretations, this will prepare you for some tough questions that might come from uninitiated developers or managers.
Explains the importance of writing simple, comprehensible code. For example:
Dim oXMLDom as New DOMDocumet() vs Dim portfolio as new DOMDOcument.
The first statement gives you no idea of what first DOMDocument represents, in second it's the portfolio, and if you know the application context you will know what to expect.

Chapter 2
Teaser chapter but also good single-chapter sample of some typical refactoring work. Captures well typical process of development of VB applications. Starts out with few event-handling methods, ends up with number of domain classes and some inheritance thrown in.

Chapter 3
Chapter on refactoring tools, also gives you some insight of how different tools like refactoring add-ins and unit testing framework fit the big picture of agile development process.

Chapter 4
Intro chapter on application that is used to illustrate refactorings throughout the book. Explains the business case, requirements, lists some use cases. It is important to understand the context of the application to be able to follow-up on refactorings. Also some funny stuff here, like freshman developer that takes pride in copy-paste development.

Chapter 5
In-dept discussion on Static vs. Dynamic and Strong vs. Weak Typing that is rarely dealt with in such depth. This is basically controlled with Option Strict and Option Explicit options. If you program in VB, you must be aware how these work out.

Chapter 6
Chapter on error handling, especially legacy vs. structured error handling. Again, something everyone should know, but rarely explained in such depth. Cool stuff is step by step recipe for converting legacy to structured.

Chapter 7
Deals with some core refactorings like Dead Code Elimination, Scope Reduction etc. It's like cleaning up your code for some serious refactoring stuff.

Chapter 8
First step in structuring your code is getting serious about the problem (or business) domain. Also explains Rename and Safe Rename refactoring, talks about Interface vs. Abstract class, Open-Closed principle etc. some serious OO stuff.

Chapter 9
Some core refactoring stuff. Teaches you how to eliminate duplicated code and why it is the worst thing it can happen to your code. Explains Extract Method and Replace Magic Literal with Symbolic Constant variable. Nice and simple example based on circle geometric shape on how procedural design is transformed to Object Oriented design (Module and Shared method rings a bell?)

Chapter 10
If only method extraction would be as simple in real life... This chapter goes further with method extraction and deals with some common problems like temps.

Chapter 11
Where do objects come from? How you design classes? Some core OO stuff in this chapter, including Extract Class, Move Member (Method or Field) refactorings, smells like Database Driven Design or Data Class, Large Class, OO principles like Single Reasonability Principle etc. Lot of stuff and handful of pages in this chapter.

Chapter 12
Build upon previous chapter. Deals with inheritance, polymorphism, genericity. Explains the difference between class and interface (or implementation vs. interface inheritance), difference between delegation and inheritance and criteria to chose one or another, list some common misuses of inheritance etc. Again, a number of refactorings like Replace Inheritance With Delegation or Extract Interface, Extract Super etc. Some heavyweight OO concepts in this chapter, takes a time to digest.

Chapter 13
Explains what is important when taking a birds-view of software. This chapter is especially important for software architects. Talks a lot about dependencies in software and why you should minimize dependencies in your code.

Chapter 14
Single chapter for huge subject, still a lot of material covered. Design patterns are the most advanced subject in OO, so refactoring your code in order to make use of patterns is in no way child's play. Mostly deals with creational patterns. First mention of Dependency Injection in some VB book I come across. Now taking into account that Unity application block [...] has been released in April, this is really cutting edge stuff!

Chapter 15
Talks about latest VB improvements that come with VB 2008. Starts with XML enhancements like XML literals and then the rest is about LINQ. Explains a LINQ implementation called LINQ-to-SQL. This is first Microsoft Object-Relational Mapper (ORM). Again, cutting edge.

Chapter 16
If you still deal with VB6 code, than you know that migrating to .Net is no easy ride. This chapter explains some techniques that will help you migrate your code and make it .Net in sprit, not leaving it crippled by simple migration that will only make it execute in .Net. VB6 lacks inheritance, generics etc, so you need refactorings to make it VB .Net.

This book has no real competition as far as I know, no book on refactoring or agile for VB .Net developers. The one that come close is Agile Principles, Patterns, and Practices in C# (Robert C. Martin Series) but it is for C# developers and requires a lot higher starting point.
When other books come up, I am sure Professional Refactoring in VB will continue to hold its ground. Highly recommended!

Really great book on refactoring. Although it is based on Visual Basic examples, same advices can be applied to C#, Java or any other OO language.
Martin Fowler finally has a fair partner on my shelf ;).

First of its kind for VB.Net developers. While it does not contain a complete catalogue of all known refactorings, you get a thorough study case used throughout the book, tooling, how to use refactoring for upgrade of legacy VB6 code, a chapter on VB 2008, some important object oriented principles and even short intro on refactoring to patterns.
This book is deep and takes a while to digest. However, it's not about showing off some irrelevant academic knowledge. Author is not afraid to mention "Dependency Injection" or "Single Responsibility Principle" but all of these are demonstrated to be relevant and get illustrated through very practical and real-life examples.