Software Books

Image processing is used to improve the visual appearance and transmission of images to a the human eye. It also concerns the preparation of images with respect to measuring an image's features and structures. Now in a newly updated and significantly expanded fifth edition, "The Image Processing Handbook" by academician John C. Russ (Materials Science and Engineering Department, North Carolina State University, Raleigh, North Carolina) "The Image Processing Handbook" features an informative chapter explaining which visual cues elicit a response from the viewer; descriptions of the latest hardware and software for image acquisition and printing including digital cameras; multichannel images and an analysis of their principle components; the issues of deconvolution, extended dynamic range images, and image enlargement and interpolation, and so much more. Enhanced with more than 2000 illustrations, and with the availability of a companion CD-ROM, "The Image Processing Handbook" is a seminal and essential addition to professional and academic library Computer Science and Electrical Engineering reference collections.

This, the fifth edition of this industry standard reference book on image processing has been significantly expanded. There are some 600 new and revised images. A major feature of the new edition is to describe the new advances that have come about in hardware for image capture and printing. This includes both new versions of traditional equipment and new emerging technologies. The text has been expanded in areas like deconvolution, extended-dynamic-range images and multichannel imaging including principal-components analysis.

In general this book does not cover the background mathematics that enables image processing. Those are left to specialty books on the subject. Instead this book is intended to be used in conjunction with hands-on equipment where the reader is encouraged to experiment with different methods to determine what is needed for the particular job.

While suitable for use as a text, this book is really a handbook for technical users. The book is more oriented to what the various tools availavle to help actually do.

I am a biologist with a little background in math. Using this book and matlab I could quickly implement basic feature recognition tools to analyze microscope images. The book focuses on concepts and explains them in intuitive language rather than in mathematical terms. Overall, it worked perfectly for me, but could be over-simplying for people with technical background.

John Russ' book on image processing was never intended to be a textbook on how to understand and write your own image processing algorithms, as you might believe by looking through the table of contents. It does cover just about everything you would see in such a textbook, but from a user's standpoint of these operations, not as an author of image processing code who needs to understand the algorithms behind these operations. Instead, Russ explains all of the operations, their value in various applications, and provides many illustrations showing before and after pictures of what each operation does. There are no algorithms, pseudocode, or mathematics in this book.

The jewel in the crown of this book is the companion CD. It contains over 200 Photoshop plug-ins for performing the operations mentioned in this book. These plug-ins work on 8-bit grayscale and 24 bit RGB images and are divided into the categories of image adjustment, color manipulation, image math, boolean operations, Fourier processing, morphological operations, neighborhood processing, distance-map operations, thresholding, feature measurement, calibration, stereology, and surface rendering. The bad news is that you have to obtain the CD separately. If you need to understand the detailed mathematics behind such operations, you might consult Digital Image Processing by Gonzalez and Woods, and then come back to this book for the tools to accomplish the operations explained in that book. The updates to this fifth edition include an additional chapter on human vision and how it ties into image processing. Also, the author has updated his sections on image acquisition hardware and software to describe the latest tools available. Finally, the topic of tomographic imaging has been expanded and given its own chapter and the chapter on 3-D image acquisition has been deleted.

This is an excellent book on image processing from a systems engineering and user standpoint. You will be disappointed if you expect to learn the algorithms behind the techniques demonstrated in this book.

As others have stated, this book comes as close as you'll ever get to a single-source reference on image processing. But if I were ever going to shoot anything down in it, I'd say that a little more mathematical background on some topics (and maybe pseudocoded examples) would help. For example, in the satellite geometric correction section, only a very high level view is given yet this is a challenging topic that could use more depth. Geometric transformations in general could use more depth, e.g. camera calibrations or image warping/morphing/mapping to other projections for example. Another example would be the need for a little more depth on how to make slow algorithms fast ...like convolution multiplications for example. Sure, you could write out the multiplies and spot commonalities, then re-use results that appear in more than one subsequent equation and what not, but some exploration of matrix math and how to make it efficient would be nice. But again ...I'm picking at small things here, and if John's book covered everything that I'd like it to, then it would become 2 books, not one ...hey! Now THERE's an idea! A 2+ book set by John Russ that covers a broader range of topics and does so in greater depth! That's something that I'd pay for (and much better to read than Ballard & Brown)

After several trips to car shows with my husband, I had lots of beautiful photos sitting in iPhoto ready to print. I thought a DVD would be more useful and enjoyable for him, and tried to make a DVD project - NOT! Having already used The Missing Manual books, I promptly went out and bought this one. Great choice, as it filled in the blanks and gave me lots of ideas also. I am a photographer, not a tech person, and am pretty clueless when it comes to creating projects on the computer.

This series suits me perfectly and the book is highly recommended - with the aid of the book I sat down and promptly made a beautiful DVD, with lots of lovely effects, great music, and best of all it was easy. My husband was very happy with his DVD and watches it often.

The manual is clear, concise, easy to read and enjoyable. Unlike so many texts, it is not dry or overly technical. Anyone can make a great DVD easily with this reference. Next project - a video. Ready.....

This is the book you really want if you use iMovie at all!

I had recently started using a Mac at work, and suddenly I was put in a position to work with video on the Mac. Mr. Pogue's other books had been very helpful to me as I began to learn my way around the Mac, so I thought I would pick up this one to help me with my video work. I was very glad that I did. You see, iMovie HD has tools that help your movie look professional, but the iMovie HD help files are very tedious to go through. There is a great deal of referencing, cross-referencing, and nothing is smoothly laid out. This book is another story, as it is very well laid out with clear instructions and illustrations. It is very long, but since these applications are powerful, it would be expected that any clear explanation of them is going to require some space.
What is particularly good about this book is that the author doesn't assume you are a professional video author, and he spends part one of the book helping you learn how to shoot videos and shares tricks that will make you good at it. Part 2 is dedicated to iMovie, and shares not just how to use the application, but the little extras that will make your video special - transitions, effects, titles, captions, and even how to work with sound in your movie. Part 3, on finding your audience, was another unexpected treat. There the author shows you how to move between iMovie and Quicktime, and how to post your movie to your phone and to the web. Part 4 of the book is on iDVD. I particularly liked the chapter on iDVD secrets, where the author shows how you can use AppleScript to customize iDVD itself.
It's hard to believe that a year ago I didn't even know how to use a Mac, and now I am quite the fan, especially when it comes to multimedia applications. I notice Amazon does not show the table of contents, so I do that here:
Part 1: CAPTURING DV FOOTAGE
1. The DV Camcorder
2. Turning Home Video into Pro Video
3. Special Event Filming
Part 2: EDITING IN IMOVIE
4. Camcorder Meets Mac
5. Building the Movie
6. Transitions and Effects
7. Titles, Captions, and Credits
8. Narration, Music, and Sound
9. Still Pictures and QuickTime Movies
10. Professional Editing Techniques
Part 3: FINDING YOUR AUDIENCE
11. Back to the Camcorder
12. From iMovie to QuickTime
13. Movies on the Web - And on the Phone
14. QuickTime Player
Part 4: iDVD5
15. From iMovie to iDVD
16. iDVD Projects by Hand
17. Designing iDVD Themes
18. iDVD Secrets
Part 5: Appendixes
A. iMovie HD: Menu by Menu
B. Troubleshooting
C. Master Keyboard Shortcut List

Very informative AND entertaining! If you feel you are even the least bit interested in breaking into digital film making this book is fantastic. I have been using iMovie for several years now and have a camcorder. However, I thought this book might help me kick things up a notch. It certainly will. I have only gotten through the first fifty pages, but I've already learned enough justify this purchase.

When I first received this rather intimidating 450+ page book I thought I would use it mainly for reference. Well, that was before I started reading it. Now I find it hard put down. It is very well written and arranged by areas of interest.

This book is great for everyone, from beginner to expert. It will undoubtedly prove to be a very valuable reference book in the future, but for now it's a great read.

If you're a heavy user of iMovieHD and iDVD, this book is a must. Most questions that users have about both software can be found in this manual (though he doesn't read like a boring manual). Pogue not only provides all the how-tos for learning the software, he also helps you troubleshoot problems that will crop in movie and DVD productions. There's hardly no aspect of either software that I didn't find covered in this book.

As a veteran Oracle DBA, I had some potential customers with both Informix and Oracle to support and since I had not used Informix in 5 years, I needed to brush up on my Informix skills. This book is unfortunately now out of print, but my copy from 5 years ago is still used on occasion. I agree with other poster that on a general DBA basis, it covers Informix quite well. I just wish that it had more coverage of high available clustering and replication topics as well as troubleshooting problems with Informix. Still good and only book that really covers Informix in detail.

This is a really good look and is suitable for both the novice and expert. There should have been more coverage of topics on HA & Replication. Also it is sad that it does not cover the latest releases. As this is out of publication, I paid a bit more than original price for a used look, but it was worth its weight in gold. The reseller from Ohio promptly sent me the book and answered my calls. Book arrived in new and good Condition. The book's website has been neglected. It needs some attention. Visited the InformiX users group for info and latest trial software after talking to the author, when I found that the CD needed keys. In the end everything was available at www.iiug.org and I had a pleasant experience using the book.

All In All A Good Book.

Of all the books I have read about Informix, Flannery's is the easiest to use. The topics are well organized and cross-referenced, which helps me find what I need quickly. In addition, the book has a web site which keeps it current. Also, the book's numerous examples make it easy for me to apply the knowledge it contains. I love the formatting and the way that I don't have to read hundreds of pages to find the answers. Well done!

This book is awesome, I just wish more topics including replication, more detailed troubleshooting techniques, and finally a good DBA practices/methods section. I now have two books, one for work and one for home. It is constantly open on my desk (both places). The sections on privileges and optimizing indexes have been my favorites due to the easy layout. Each section presented the infomation in clear and concise ways, allowing for quick implementation.

As a new DBA (1yr.), I can't thank Mr. Flannery enough. I only wish the rest of the Informix Press books would strive to meet or exceed this standard.

Since I'm new to Informix, I was forever looking for a book that would help me get a better understanding on how to support Informix databases. The Informix user manuals were very unorganized make it very difficult to get the answers I needed. This book is well organized, making it easy to locate the needed information. There are plenty of useful examples that are easy to understand. This book has now become my main reference source. For the novice or expert, this book should should be in your reference library.

I have taught a course in computation theory for computer science majors for almost two decades. Before the first time, I had never had any of the material in a course so I was required to learn the material on my own. This was the book that I used. For about a month, I set aside a block of time each day and went through the material section by section. When I had completed each section, I would work a few of the problems and would not move on until I understood what the answers should be.
The coverage is:

*) Deterministic and nondeterministic finite automata
*) Regular expressions
*) Context-free grammars and languages
*) Chomsky normal form
*) Pushdown automata
*) Turing machines
*) Post machines
*) The relationship between machines and computers

When it came time to teach the class for the first time, it all went very smoothly. This remains the most readable book for the self-study of computation theory that I have ever seen. Cohen has written a later, more concise edition and that is what I have been using as the text in my course.

I read it during my undergraduate, it was the course book for the thoery of automata course. More recently when I tried the popular "Introduction to Automata Theory, Languages, and Computation" by Hopcroft et al. for the purpose of revising the concepts, I realized how great this book is. It is definitely a better book than Hopcroft et al's, with in-depth explanations of all topics, lots of examples and exercises and in a writing style very friendly for the novice readers. Very good work!

I must say this is one of the best books I have ever read. The auther is humorous and insightful. He manages to take very abstract concepts and explain them in clear concrete terms and metaphors.

This an excellent book. Basically, the whole point of it is to mathematically define what a computer is and prove that it works. The author does this by defining and manipulating mathematical alphabets and languages without resorting to any kind of advanced math. Starting from nothing, the whole thing leads up to Turing Machines. More specifically, according to the Preface, the goals of the book are:

"(1) to introduce a student of Computer Science to the need for and the working of mathematical proof; (2) to develop facility with the concepts, notations, and techniques of the theories of Automata, Formal Languages, and Turing machines; and (3) to provide historical perspective on the creation of the computer with a profound understanding of some of its capabilities and limitations."

The author did a wonderful job of it. Plus, unlike almost all other computer/math books I've read, this book is almost enjoyable to read. Again, as stated in the Preface:

"This book is written for students with no presumed background of any kind. Every mathematical concept used is introduced from scratch. Extensive examples and illustrations spell out everything in detail to avoid any possibility of confusion."

Astonishingly, those are all true statements. At a guess, I'd say that almost anyone interested in computers could get through this book without undue stress. To make it more meaningful, I'd suggest (only suggest) prerequisites of having programmed a computer and knowing some discrete math. From that point of view, it's odd that as of last year, this book was used in Florida State University's (FSU's) COT 4420: "Theory of Computation" course, which, obviously, is a 4000 level course requiring various prerequisites that put it out of the reach of all but senior (or graduate) level students.

Now, with all that glowing out of the way, there are a couple of small problems with the book. The first is simply that the exercises don't have any solutions. For the self-studyer, that's a bad thing. In a school teaching environment, it's probably acceptable, though. The second problem is that after getting through the book, I simply have to ask: "So what? WHY should I learn this?" Again, in the Preface, the author states:

"Leaving aside the obvious worth of knowledge for its own sake, the terminology, notations, and techniques of Computer Theory are necessary in the teaching of courses on computer design, Artificial Intelligence, the analysis of algorithms, and so forth. Of all the programming skills undergraduate students learn, two of the most important are the abilities to recognize and manipulate context-free grammars and to understand the power of the recursive interaction of parts of a procedure. Very little can be accomplished if each advanced course has to begin at the level of defining rules of production and derivations."

But, in my experience, I have to say that except for one reference in one other book I've read, I've never seen any of this stuff used. Even more, I've never known anyone who even knew of anyone who used (or even knew of) any of it. EVERYTHING has been done at a much higher level of abstraction than alphabets, languages, and various levels of algorithms and machines up to Turing Machines. I'm not saying that the material in this book isn't used SOMEWHERE. But, I'd honestly have liked to have seen actual, specific, concrete cases: they'd be fascinating.

So, factoring those two nits in, I rate this book at 4 stars out of 5. If those two things don't bother you, then you could easily consider this a 5 star book.

The book has one important attribute: it's clear, undoubtedly. Having a minimum of prerequisites, I think there's no way to not understand what Prof. Cohen says through its pages. It makes the job of learning this part of theory easier than any other text.
But ... but I can't totally agree with Cohen's crusade against formalism. I agree that the first target of a book should be to clearly transmit the intended knowledge, and Cohen perfectly succeeds in this. But formalism too has its importance, thereafter. A compact and clear formalism helps to communicate efficiently, and moreover unambiguously. Like in mathematics, the first, important thing is to understand. Yet, there's no way for you to efficiently work with math without using any kind of formalism, should it be more or less "standard".
That's it: a very powerful book for a "profound" understanding of the subject; a bit more of natural formalism would make it a "complete" understanding also, and the book a five stars one.

Although it's the teacher's addition it actually work better for my benefit, it has all the odd and even answers in the back. It doesn't come with the solution book but that's fine with me for the price i'm giving. Overall it's worth my money

This is a great text book....easy to understand and really helpful. And I'm awful at math! haha

Great condition for a used book. Plus you can't beat the price at any College Bookstore.

I picked this book (sixth edition) from many others after watching my daughter struggling with Mario Triola's Elementary Statistics that her teacher used in the classroom. I wish Weiss's Statistics was her (and mine) first encounter with the subject. The book is well written and structured, easy understandable, and at the same time interesting and engaging to learn more. My daughter found it very helpful. I also enjoyed reading the book; it helped me to put my knowledge in order and finally understand the logic behind different hypothesis tests and other statistical concepts. If you always wanted to learn basic statistics just read this one book and you will be surprised to discover that learning and applying statistics can be easy and fun (do exercises!).

I can not say enough about this book I have never taken a class in statistics for fear that I would fail it .However, this book mapped it out so well if you fail the class it won't be because of this product.My first grade was a 94%, which is great for a person who hates math. I breezed through the class with this book. purchase it you will not be sorry.

The author explains vendor independent concepts of load balancers and discusses their (dis)advantages.

He is dividing them into four major applications:

* Server Load Balancing (63p)
* Global Server Load Balancing (19p)
* Firewall Load Balancing and (15p)
* Transparent cache Switching (8p)

additions:

* application examples (4p)
* future outlook (2p)

What makes the book so enjoyable to read is the authors love to the details. The story just flows very smooth.

Especially the thorough explanation, screenshots and technical details deserve the mark "distinction" (Very good). While I read the book it was like puzzle peaces suddenly falling all together to show me the bigger picture.

I did like the follow up of technical issues like session persistency (server affinity), URL switching, system design vs. functionality considerations and the limitations that come with the chosen solutions. The described issues are exactly those that system designers will face in real life and it doesnt stop there of course. The book is laying a good groundwork for development of advanced concepts.

The part of the book that I enjoyed most was the chapter about firewall solution concepts. As the author points out correctly the traffic flow in both directions must be managed. This is also why the setup from a redundant firewall to a load balanced redundant firewall must justify multiple complex issues.

In this case the author went through the analysis of the traffic flow, a stateful vs. stateless discussion, a layer2 vs. layer3 discussion, proxy firewalls, synchronized firewalls, multizone firewalls, VPN load balancing, active-active vs. active-standby discussion and the interaction between routers, load balancers and firewalls. While some topics could only be scratched on the surface the concepts and ideas behind it are explained very clear.

There is no doubt for me that a 2nd edition can easily just pickup where this edition left off. The author clearly shows that there are more scenarios to be discovered and discussed.

On the one side I would love to see a updated 2nd edition from the same author, on the other side I guess it's been hold back to keep the competitions products in a distance ;-)

Also the book was published 6+ years ago I felt that the concepts did not loose any of its value. Which leads me to the point that this must have been " THE Technical Book of the Year 2002"

This book still receives well deserved full marks.

Bravo !!

if you are new to load balancing, get this book. Clear concept explanation, with diagrams. Highly recommend.

With his background in server products and networking products, this author is uniquely qualified with the product experience to present these topics.

From the simple beginnings of DNS server load balancing Kopparapu explains the driving forces behind and solutions presented to load balancing. The majority of the book is an introduction to the concepts and solutions available for server load balancing suitable for everyone from business casual to advanced technical users.

In addition to detailed explanations, the author demonstrates load balancing techniques through a number of illustrations. The illustrations are detailed enough to explain the concepts, but occasionally lack enough practical detail to go out and bulid in a lab or on a network without further understanding.

In combination with a good manual from a load balancing product, any reader would have enough information to implement sophisticated load balancing configurations.

In addition to server load balancing, the text covers caching techniques available through the use of some layer 4-7 devices. Of all the topics this one is the least detailed in the text. The author understandably covers only that part of cache technology related to layer 4-7 devices. A great deal of the technology required to put together an entire cache system resides in other parts of the system outside of the scope of this book. The implications for the architecture of a network are far reaching and worthy of at one more dedicated book on the topic.

Finally, the author presents the topic of firewall load balancing. Like caching, this is a complex topic. A complete understanding of network security and firewalls would require at least a few other books.

For those that already understand caches or firewalls though, this book provides detailed information on how to scale those systems with layer 4-7 technology.

This is certainly the most comprehensive and easy to read text on the topic. Anyone who reads this will also look forward to future texts from the author on emergning challenges in layer 4-7 network security and streaming content and distribution.

Compared with Tony Bourke's book, this one depicts more on technical details such as how packets flow, how health check is done and etc.. On the other hand, Bourke's book mentions more about the basic concept and the introduction to current available products.

If you are interested in how load balancers are designed, this is the right book for you. However, if you are just shopping around and only want to know what load balancers are, get Brouke's one.

Btw, I was a bit disappointed at chapter 9. I expected to see more opinions on the future development of load balancers but it was not mentioned too much.

This book is a very well written and nicely organised introduction to server load balancing. The author describes the basics of load balancing, including NAT, session persistence, and network architectures. A discussion on application-layer parsing was quite good. There is also a chapter on global server load balancing (including incorporating load-balancing into the authoritative DNS server) which I found to be very detailed and interesting.

Much of the book is centered on how to load balance TCP (and to a lesser extent UDP), and the author uses HTTP and FTP as his primary driving examples. Throughout the book, the author provides some insight regarding what approaches real companies use (e.g. "this method is what Foundry and Cisco uses."), which I liked very much. Also, the illustrations were plentiful (although a bit primitive-looking).

There are only a few negatives about this book. The english writing is a bit stilted at times, and the chapters on firewalls and caches were basically rehashes of earlier chapters. Finally, I was hoping the author would have provided more detail on the load-distribution heuristics (which server to choose) with more metrics and actual real-world results.

I found the book to be extremely well organised. You will not get lost while reading this book, but you will need a university-level understanding of TCP/IP (and probably the link layer as well to get the NAT material) and networks in general to fully appreciate the matieral. Overall, a great book.

This truly excellent book fills a large void in the software engineering and IT world - tying the business case to software. It is of paramount importance to demonstrate a quantitative, bottom-line impact when embarking on a software development or evolution project. Too few engineers and managers consider the full business context when making decisions. Many hard lessons in my 20 years of experience could have been avoided if I had the insights and techniques that this book provides.

I expect Mr. Reifer's book to be a classic in the field. It is chockfull of practical methods with worked-out examples of making the software business case. Not only is it rigorous in it's quantitative approach, but the author's broad and seasoned perspective helps practitioners steer through the minefield of people, politics and organizations. I seriously believe we would have more successful software projects if all technical people took on such a balanced view.

Don Reifer's book provides information not found in existing books on software engineering, process improvement, and project management. His primary audience is technical people who must sell a project to business people. In particular, he provides concrete, practical advice for selling a process improvement program. For example, Chapter 4 stresses the importance of focusing on cost avoidance instead of cost reduction to justify improvements. In Chapter 7 he suggests briefing middle managers individually to obtain their support. Based on my experience, this is sound advice because middle managers are often the most difficult people to convince in an organization. Giving personal attention to each manager pays big dividends later. He also suggests taking advantage of state tax laws to partially offset the costs of training employees. This is a win-win strategy for both the firm and the state. Training gives employees new skills and improves retention. This, in turn, helps the firm obtain more business and so generate more income for the local economy and more tax revenues for the state. He explains the difference between project and capital funds, and how to exploit this difference to obtain the resources you need. The book has many useful checklists. For example, one identifies the types and sources of information needed to prepare a business case. Another identifies the critical items to check when deciding to acquire a business.

His book will also be of interest to marketing people who are preparing sales presentations for complicated technical products. For example, these individuals could prepare business cases to compare possible alternatives. Even experienced managers unfamiliar with software products and process improvement will find the case studies useful.

Don Reifer illustrates the concepts presented in Part 1 with actual case studies in Part 2. These are based on his 30+ years of experience in the software field. The case study in Chapter 7 begins with what amounts to an engineering view of the problem and then the author provides comments indicating how a manager would like to see the information presented. This case study really shows the contrast between the technical and management ways of thinking. The case study in Chapter 8 shows how to assess the value of a company whose primary assets are intellectual property and knowledge capital.

Overall, the book is concise and well written. I was able to quickly absorb the concepts and techniques without spending a lot of time. It is a valuable addition to my reference shelf.

Making the Software Business Case: Improvement by the Numbers covers an area too few software engineers have any exposure to: financial modeling and business analysis, as it relates to the IT domain. Reifer's concise (300 page) book provides a broad overview of how the IT area appears from the business side, including critical material on how to frame technical proposals in business terms.

Amongst the many nuggets to be found in this book are:

· useful tips on where money can be found
· good insights into the politics of proposals and budgeting
· getting middle management buy-in
· countering executive challenges
· successful management of cross-project initiative dynamics
· software capitalization/depreciation
· Discussion of reuse from a cost avoidance perspective.

This book is not only good in terms of its material, it is also an eminently readable book in terms of style. Reifer elaborates his argument through the clever use of case studies that provide human interest and momentum to otherwise dry material. These case studies include:

· A defense contracting firm implementing software process improvement
· A public utility replacing an outdated mainframe-based transactional system with modern client-server technology
· An industrial controls firm suffering from moribund products
· A firm seeking to Internet-enable its internal systems

Reifert places strong emphasis on "making your numbers believable." He argues that this believability must address these nontechnical considerations:
· Cash flow
· Cost basis
· Cost/benefit
· Estimate fidelity
· Present value
· Profit and loss
· Risks
· Source of funds
· Tax implications

He does an admirable job in placing these concepts in context, and providing a clear overview of each.
The utility case study demonstrates the importance of understanding the overall financial dynamics affecting one's enterprise. For example, the differences between capital and expense budgets can be key in determining whether to purchase or lease equipment. As Reifert elaborates in the utility scenario, "Because this has been a profitable year, an increase in expenses [i.e. leasing as opposed to purchase capital expenditures] could have a profound positive tax consequence." The book has many examples of this type of valuable, integrated business insight.

Reifer has much sound general IT management advice mixed in with his financial message. A recurring theme through many of the discussions is the need for an executive sponsor, to provide political cover and tactical advice in forwarding the business case.

He also urges the reader to frame benefits in terms of cost avoidance rather than cost reduction-promising cost reductions often lead to the question, "OK, then who are we going to let go?" Not a good way to win friends.

I found his observations on the subject of central process quality assurance groups interesting:

"Reinventing staff organizations such as process and quality assurance groups is a good idea. Engineers assigned to such staff groups get stale once they've put in more than three years of service. Being in an audit and support role, they forget how hard it is to develop and deliver quality products under extreme deadline pressures." (p 137). The book displays a continual awareness of the need to balance these contending issues of cost, schedule, and quality.

The case study based on the industrial controls firm has an explicit architectural theme. This is an especially compelling discussion; software engineers are well aware how critical architectural decisions are, and how often they are compromised in the rush to write code. The discussion demonstrates how to make the case for architecture and include it in an overall work breakdown structure. Reifert is exceptionally creative in his case study creation, taking the opportunity to demonstrate hidden agendas, the pitfalls of contractor estimates, and developing a good working relationship with high-level consultants.

The book provides a solid summary of software estimation. There are whole books written on this subject, so the chapter is necessarily at a high level (although it does dive into some detail on the COCOMO II model in particular). However, it provides a valuable discussion of aspects of high-level IT budgeting beyond tactical project estimation, presenting numerous examples of cost breakdowns covering all phases of the systems development lifecycle, from architecture to maintenance.

The final case study moves into even more adventurous ground, discussing a company seeking to Internet-enable its internal systems via takeover (hostile if necessary) of a specialist firm. The ensuing narrative outlines the due diligence such a move requires, and the various tactical and strategic issues it may raise. A brief discussion of international intercultural relationships is excellent.

The book has only one minor flaw: it was obviously written during the dot-com bubble. There are frequent references to industry dynamics such as a venture-funded firm's survival depending on extreme time-to-market pressures, and perhaps an overemphasis on faddish Web technology.

This book is easily on my Top 10 software engineering book list. It provides a lucid, crisp overview of business issues that are all too mysterious to the average software engineer. Given the potential that well-architected, business-responsive software has to increase productivity, this volume is a service to both the software engineers and the enterprises that employ them.

This book is the aggregation of Mr. Reifer's extensive experience in software management and economics of reuse. His earlier books, "Practical Software Reuse" (ISBN 0471578533), and "Software Management" (ISBN 0769511007) evidence his experience, and probably account for the realistic approach he takes in this book.

Despite his technical background he takes a business-focused approach early in this book by explaining the difference between business and technical cases. Too many technical managers confuse the two, and this plus the other material in Chapter 1 explaining the fundamentals of business cases will set you on the right course.

Chapter 2 is the essence of this book, with advice on relating goals to metrics (using the Goal/Question/Metric technique), and the development and alignment of business cases to development life cycles. This is followed by two excellent chapters covering principles, rules, and analysis tools, and strategies. Much of this material is standard fare, but Mr. Reifer's clear explanations are better than most books that cover this material.

The second part of the book employs case studies that lead you through the development of a business case using principles, concepts and techniques given in the first part of the book. These reinforce part one of the book, as well as provide clear examples of business cases that work, and the process with which to develop them - including challenges, how assumptions were derived, and other nuances of which you should be aware.

The final part of the book is a single chapter on overcoming major barriers, and the sage advice is well worth heeding.

Overall, this is one of the best books on business case development because it is business-oriented, has an approach that is financially and tactically sound, and is written for technical-oriented managers in their own language.

This is not a book for software developers or managers who work in a small shop where there is focused development, little formal bureaucracy and a great deal of camaraderie. It is written for the person with responsibility in a large organization who has an idea for a major new project and needs to get it approved. Essentially, it tells you how to survive and thrive in a large organization that builds software.
The advice is fairly simple but quite accurate. Use numbers in your presentation that can be justified and are consistent with any previous numbers that relate to the project. Have solid data concerning the expected return-on-investment (ROI) from the project as well as any additional costs that may not be outwardly obvious. Quite accurately, the author is emphatic about the principles of present and future value. So much so that appendix B is just a set of basic compound interest tables. This is the most important advice that anyone in a large organization with a business case to plead can ever receive.
A lesser, but still critical point is that you must have a manager to champion your proposal through the managerial hierarchy. That champion must also know the expected ROI from the project very well, as upper echelons will consider a lack of knowledge on the part of the champion to reflect a lack of interest. Another point to reckon with is that if you receive the budgetary increase, it most likely means that someone else in your organization had theirs cut. Nasty, but also the way things are.
Finally, the author takes you through a case study as to when you should acquire a company rather than build a new internal division from scratch. His analysis of what to examine and consider significant is a solid strategy for determining which is the better option.
This is a book that really has two audiences, those who are lower level managers in large organizations with an idea for a new project and those who are starting a company and need to convince the people with the money to open their wallets. For them, it is priceless, but for all others it is difficult to see where they will find it of value.

This is great book, It has a lots of example and explained really well. Great Work!

The book is good but many solutions are not tested fully so its not that they can be cut and pasted directly out of the book. you may have to troubleshoot many of them. Otherwise a real good book.

As a Developer working predominantly with Oracle Databases for over five years, I'm always looking for books to help me produce better code. I have to say this is one of them. The author has produced a book that explains concepts in a practical manner that is also easy to read. I began reading this book just before starting a major development project and the code insights and examples assisted me greatly in this project.

Probably more a information and guidence book rather than a reference book. I found I read it from cover to cover and used the information as a platform for future developing. Some great code examples which I have used to great effect though!

With 15 years experience in Oracle as DBA and developer, I wrote a lot of packages and found in this book true advices and practical solutions, wich sound good to me. The best feature is that you can experiment all the code found in it and see by yourself the advantage of using the way proposed by McDonald. I like these books where autors breaks some common ideas ans show by "A + B" that the right solution is not the most common. A real useful book written by a true professional.

The book takes a bottom-up approach: the first part shows useful coding and optimizing techniques, while the second one gives real world applications and tips on program design.

I have two minor complaints, however:

Most chapters assume at least a good knowledge of PL/SQL and build on that, which I think is fair for a book titled "Mastering ...". On the other hand, two of the chapters (Triggers especially, and PL/SQL Debugging to a degree) take a different approach and start from the beginning, explaining the basics, too. It may be just me, but I think those pages are wasted.

Furthermore, there is a certain amount of overlap with Tom Kyte's Expert One-on-One Oracle, also from Apress.

The book got to me in a timely manner. I'm very pleased and hope to do well on the exam.

I used this book together with the corresponding Training Guide, by the same authors (this was redundant because the two books essentially repeat each other - I could have just used the Training Guide.) I think these authors are amazing - they have ability to present everything in such an easy understandable way, that I didn't just memorize the stuff for the exam but actually understood it. Now my next one is 70-229 - SQL server exam, I wish Kalani had a book for that one as well...

This book is pretty good at explaining the needed topics. I only used this book to pass the exam and found it compact and accurate.

Two bad notes are since coriolis was bought out it is tough to get errata for this book and there are a few problems. The securit section is a bit weak so read some online stuff to fill it in.

Good luck ZoOnI

I skipped reviewing the Microsoft study guide and used this book as my primary reference in passing the exam. Each component on this exam (web services, windows services, enterprise services) has its own architecture and interface. This book did a great job of distilling that information in a way that was easy to understand. I especially liked how the chapters were organized to introduce a concept, and then show you the code for implementing it. I simply wrote my own example for each chapter and did well on the exam. I didn't get much use out of the study guide or CD, but the practice tests in the book are very useful.

This certification study-resource from Author Amit Kalani, served as a rather indispensable part of the revision portfolio for Exam 70-320 (XML Web Services and Server Components with C# .NET ).

Simply put, it is a very useful & sound comprehensive reference for Exam 70-320. It served me greatly in gaining both an overview of all the elements that would appear on the 320 exam, but also served well in my overall review and revision endeavours for the 70-320 Exam.

using this resource got me to the place where i felt i had covered the core objectives for the exam and was ready to move on to the next phase ie: having a go at tackling past question scenarios.

i was glad i bought it.

what i liked about this book :
- it is a comprehensive read at 344 pages -(ie: the 2 Testing chapters non factored)
- there are exam questions after every chapter, relating to that chapter and the exam objectives the chapter tackles
- Answers with explanations are provided with every question featured in the book.
- there is a CD with questions set in an application that simulates the exam room scenario
- The CD also comes with a .pdf, e-version of the book.

I purchased the book in question as a pair with the companion Exam Training guide -(equally written by the same authors: Amit Kalani + Priti Kalani) from Que press ISBN: 0789728249; and i basically have'nt looked back one second since taking that decison.

the two books complement each other very well and provide a very fine balance between the need to train & equip the reader with the strong hands-on .NET XML Web-services development skills he/she will require in order to thrive as a C#.NET web developper; whilst at the same time fully framing these necessary hands-on expertise , in the context & framework of the exam the reader probably seeks to take at the end of working/ploughing his/her way through the book.

Amit Kalani is a very good author. he is well known in the C#.NET world. and he has a way of making a typically difficult material to teach, clearly explained, and he reinforces this with ample examples and practise, so it sinks in and becomes proper knowledge. So for those starting out on C#.NET or others looking for a place to start the preparation for the MCAD.NET with C# or 70-320 exam, these Books could easily serve as the spot to take it from.

However, i would add but the small proviso that depending on where you are along the previous "C#" programming-experience scale, i'd say you'd do well to buy yourself a good companion C# programming language text to accompany you on your journey.

There are lots of books on Amazon that would serve you well in this function/capacity . the text i used to give me a helping hand is called the: "C# Bible" by author: jeff ferguson (et al); it has for ISBN:0764548344.i found this easy to read and got through the first 20 chapters of concise, easy to follow, C# language basics, with relative ease.

After working through the 70-320 ExamCram resource in question and using the Training guide counterpart to acquire deeper hands-on practise to cement the interface between :( knowledge of the .Net Framework1.0 XML Web-services development concepts as treated in the books), with that of proper programming competence;(ie:knowing your stuff); I was ready for the next phase ie: going on to tackle past exam questions

using Transcender and the Testking more than sufficed to ensure & assure success at the exam;

Take & Ace the exam with ease: 150minutes & 43 questions.

Success at the exam-level is assured by appropriate preparation; ie: tackling past questions regarding .NET programming & C# XML Web-services development related problem scenarios in order to sharpen your wits about choosing the right solution in any given problem scenario. this is the crunch of it. do that ,and u pass.

End of.

The passing mark is 700 ie: 70%. i sat the exam on Tuesday (31st October 2006); scored 98% ie: 984.

MCAD.NET requirements accomplished!

Good luck.

cheers :-)

This book has saved me a lot of time that I would have otherwise spent combing through huge Exchage reference books. As an Exchange Administrator, I have already found this book to be an invaluable asset in my reference library. Answers to many common administrative questions and "How To's" are easily found in this handy little volume. You gotta love its size.

Out of all the Exchange 2000 Server books I purchased, this one is the only one I used regularly. I have since purchased Stanek's Exchange Server 2003 book and it is equally as good if not better. For admins, it provides the essential details with clear, precise steps for implementing common features. For devs, it provides the cut to the chase info you need to get in there and get out quickly. I would recommend this very highly.

I bought this book for our Exchange admin when we were moving to Exchange 2000 from 5.5. Two months later I was going to be the one implementing Exchange and this book came to the rescue in a big way. As a total Exchange newbie I learned everything I needed (and now know) about Exchange from this book. Sure there are bigger books but not better books. If you are a Exchange guru, this book will be a little on the basic side for you. However, if you are anything less than a guru or if you are a new I would highly recommend this book.

I had a need to quickly resolve a problem with Exchange 2000 Server, having never worked with it before. This book was an excellent resource for that purpose. Not because it gave me the exact answer I needed (which I doubt many books would do) but because it clearly and concisely explained what you can do with Exchange 2000 Server and how to do it. It showed how to do things properly and from that it was fairly easy to deduce what was wrong.

Because the book is well structured (no excess verbage, no "chattiness") it's easy to read, clear and to the point. It gets to the point and stays on target.

All in all an excellent reference you'll use over and over and, I think, an excellent place to start learning Exchange 2000 Server. I find that this book tells what Exchange 2000 Server can do and how to do it. With that knowledge I think you'll be better grounded if and when you go for more in depth understanding of architecture and the like. After this book, if you want more in depth information you can move on to other (bigger) books but I think you'll get the biggest bang for the buck from this one..

This is excellent when used for quick reference and only for the experienced and knowledgeable. This is inappropriate for beginners since Exchange is intertwined with Active Directory. Without knowing all the implications of performing the various tasks outlined in the book, it can be detrimental to a company.