Software Books

I've read this book from cover to cover. I've read many books on software development, software processes, best practices, qualitative approaches, and quantitative approaches, many from SEI. This book has to be one of the top two. For software professionals in leadership positions facing today's pressures of delivering quality software that meets customer expectations according to plan, this book is a must-read. You will be able to implement techniques directly into your organizational processes and deliverables with considerable ease. Kolawa and Huizinga have forged a grimoire that should be on every software leaders' desk, be they Project Managers, Software Architects, PMO Directors, of Vice Presidents of Development. Here are the key take-aways from this book:

1. Clarity: All concepts, practices, and examples were extraordinarily clear. There was never a question as to what was meant, or confusion in the information conveyed.

2. Readability: The text is very user-friendly. Coming from a very technical background, I tend to read challenging and complicated material. In this book, you were able to frame both technical and complex material in a readable way. In other words, I never had to re-read anything in the book. All of the material was very easy to understand. I feel the ability to effectively reduce complexity to simplicity is the hallmark of good authorship.

3. Implementable: I found the practice-side of the book to be what I call `out-of-the-box.' This means I was able to take material directly from the text and apply that into my process(es) or deliverables with very little work or trouble. (I actually did this multiple times.) This is a testament to the subtitle of the book, Best Practices in Software Management.

4. Usefulness: The book is actually aimed at being useful within for-profit businesses. Theoretical books are good for concepts, but it's up to the readers to find ways to translate the theory into executable practices (which often is beyond the role and responsibility of the readers). Your book actually bridges this gap, and provides mechanisms to help readers implement valuable techniques into their organizations, independent of their infrastructure.

These four points make a huge difference for readers looking to improve their software development processes to ensure profitability, cost savings, and customer satisfaction. Producing quality software while building defect prevention into your processes is key in today's competitive software marketplace. With these techniques, your organization will continue to become better, managing, reducing, and even eliminating the traditional sources of defects in software deliverables. You won't be disappointed in buying this book, as you'll refer to over and over again as you build process improvement into your organization.

This book offers a straight-forward, realistic approach to solving challenges of day-to-day projects that the software industry faces. Not only does it address the necessity of technology businesses to increase efficiency and productivity, but it also takes into account the psychological need for individual software professionals to be challenged and intellectually fulfilled on a daily basis. The powerful gains of software automation are amplified by the strategic best practices described in this software management book.

What sets this book apart from other software quality management books is its focus on real-world solutions. Many quality improvement strategies sound great on paper, but are impractical to implement because they end up slowing project progress and stirring resentment throughout the ranks. Rather than ignore the demands of modern day development, this book embraces them. The result is a refreshingly realistic approach to boosting software quality... while at the same time actually improving team productivity and developer satisfaction.

Automated Defect Prevention delivers a realistic approach to the nagging software quality problem. If you are responsible for developers who deliver business applications, you need to read this book. If you are an software architect or engineer, the book will offer a pragmatic road map to achieve incremental productivity gains within your software development lifecycle.

When I read this book I had a huge realization. Most of the quality initiatives that I had been involved with or observed had introduced (or layered on) additional tasks and responsibilities for either the architect, developer or QA engineer. Over time, these layered tasks ultimately resulted in dragging down productivity. Investing in the *correct* infrastructure to automate the monotonous/repetitive is the key to success. Quality should be the outcome of intelligent investment in productivity.

One issue I have with the software industry is that too many project managers, or stake holders managing software people, lack the understanding of just how important software quality is and how it can benefit the software teams and products. As the people most accountable for what happens with a software initiative, managers should have a solid understanding of what options are available to improve developer skills and the software they release. This book provides that needed information and helps explain who is responsible for what tasks, when they should be considering phasing in a particular practice and the benefits of a given item.

I like the way the information is presented in this book because I feel a project manager would be able to quickly evaluate a practice for phasing in without facing an all-or-nothing approach that some other books take. If, for example, a manager felt that they enjoyed the chapter on testing models, this book provides the information on what is needed, the benefits and the roles people need to take to phase that approach into their teams.

I enjoyed this book and I wish that more development teams used many of the practices in this book. While there were samples at the end of the chapters and a chapter on case studies, I would have liked to have seen a bit more information on difficulty and time constraints presented within some of the sections themselves. Overall this is a great book and definitely worth having on your desk.

This is a concise, easy to read book that seems to cover a large variety of publications and projects. I can open it up to any page and get new ideas and insights on projects I'm working on.

This book explains the basics (and some more advanced concepts) of good graphic design without overwhelming the reader with technical terms nor "dumbing down" the vocabulary for the novice. There are plenty of colourful examples and the book follows its own advice! This book lacks, however, the specific steps to accomplish the different design goals, but this is probably due the many publishing packages available. It assumes the reader will figure that out for himself (or herself.) The book is a compact 200 page document that is filled with useful information from cover to cover and is a great addition to any designer's reference library.

Yet another great book from the folks at Before & After. I have the Before & After Page Design book and subscribe to the PDF magazine. Even with all that, I still liked the addition of this book. It covers the usual business situations like newsletters, stationery, logos, forms and charts. The ideas illustrated and dissected here were found to be light bulb creating. I was able to apply a few of the tips right away to some projects I was working on at the time.

Some of the nuggets I enjoyed most were the comparison and discussion of what typefaces are best for what text that can be applied to all sorts of type, logo creation and thought process and the charts. The charts were not just your average pie charts, but great design elements.

Again, I'm impressed by another Before & After project. The illustrations and explanations help new and intermediate designers improve the craft. I'm sure seasoned professionals can pick up a few tips too.

I am a former graphic worker and I now teach this matter to students who have no ideas of the state of the art.
The book is professionnal and easy to use, and all examples are so helpfull to any people who need advices in business graphics.

Before & After is one of my favorite design magazines. The project examples, step-by-step guidelines and practical articles have always been excellent resources for designers of all education and experiences levels. With Graphics for Business, author, designer and teacher John McWade teaches the reader how to make their business look great. The book is not logo or corporate identity specific. In addition to logo design, McWade covers the creation of newsletters, stationery, sales pieces and forms, and charts, reports, calendars and maps. Still, the logo and identity section of the book (44 pages of the volume) explains logos very well and provides great examples of how to design lettermarks, wordmarks, monograms, ligatures and other forms of identities. Playing with type, words, shapes and illustrative elements are all presented in fun and well-illustrated manner. The book will be a great addition to the design library of anyone interested in producing a strong image for their business, or that of a client. - Jeff Fisher, writer of bLog-oMotives and the "Logo Notions" column at CreativeLatitude.com

I am new to programming.

This book starts at the beginning: building a graphical web page in Web Matrix. Following a entertaining blend of practical, funny and insightful steps, in a short period I was using Visual Basic.Net and databases to add dynamic features, controls and web services.

I was amazed at how easy it is to do. This book provides an enjoyable was to grasp a firm foundation in ASP.NET programming.

I am a college student having some programming knowledge but totally new in dynamic/ data-driven web creation. I found this book really helpful to get started from static to exciting data-driven stuff with ASP and MSDE. Although WebMatrix has a limitation(which was developed by a team of people from Microsoft at their spare time), it's a real great tool for beginner to get to know how to install database engine, create a data table, link to your web form with drag-n-drop and some hands-on coding (provided in the book). If you need to go on to industrial level, this book or WebMartix won't help.
Chap 1 starts with step by step instructions on how to install .NET framwork, MSDE (you need this if you don't have SQL running), then WebMartix (which has its own web server, you don't need IIS to run samples from the book). One of the great styles of this book is easy-to-follow-and-understand examples which has "Try It Out" & "How it Works" section which explains the code line by line in detail. I found Chap16 and 17 really helpful for general knowledge on "Web Services" and "Beyond WebMatrix," but make sure you finish this book first, then go on to more exciting Visual Studio .NET (which is a "bigbrother" of WebMatrix)
Oh..2 case studies at the back of the book, which explains step by step how to make a guestbook, reconizing customer and "log-on" stuff..and the CD includes some software WebMatrix, MSDE, etc..
Thanks to David Sussman and Wrox P2P

Great combination and perfect fit of beginning book and tool: ASP.Net Web Matrix. Excellent examples and basic ASP.Net concepts explanation.

You will be amazed when you read it. It is a step by step guide. I highly recommend this book for ASP .NET so far.

This book is a not bad introduction to ASP.NET. The reason I purchased it is I really needed to master Web Matrix ASAP and Mr. Sussman's book was quite helpful in accomplishing that goal. Of course, it is better to begin with Visual Studio since Web Matrix is somewhat limited resemblance of Visual Studuo but Web Matrix has something nobody could resist - it is free.
Make sure you learn as profoundly as possible chapters about datagrids and reusable content; these two are absolutely irreplaceble components of practically any online database application. Also pay attention to inclusion of namespaces at the very top of your code, it is forgetable. The only thing which was not working for me is Web Services. Other code samples work fine.
I would recommend to start with this book to anybody who needs to master ASP.NET.

Internet Relay Chat (IRC) is an old technology by Internet standards, but still a very viable means of interpersonal communication; i.e., chat. Sure there are lots of nutcases out there, but you can also find people who can provide help on a wide variety of subjects (i.e., programming in specific languages), discussions on almost any subject (which is not to say they'll be intelligent or reasoned).

There's not much flash or glamour to be found in IRC or the tools to use with it. This book, however, is a great guide to IRC for those who need to know the nuts and bolts of whatever technology they deal with.

Though old, little in the technology or tools has changed since it was published in 2000.

It's an inexpensive and worthwhile addition to any techie's library or for anyone who is interested in enlarging their online social millieu.

Jerry

Very well written and illustrated guide that starts with the very basics and takes you all of the way through to advanced use. The IRC protocol and client side commands are explored in depth. Numerous clients for Window, OS X, and Unix are covered. This basic coverage, which is about two-thirds of the book ends with an excellent chapter on managing channels.

The advanced chapters cover installing an IRC server, using DCC, and some advanced security issues.

This book sets a comprehensive foundation of knowledge for IRC which is then supplemented by O'Reilly's IRC Hacks book. Beginners looking to get seriously into IRC will want to buy this book. More advanced users will want to look at the coverage of their areas of interest to make sure it's worth the investment.

An truly outstanding book. I have used IRC for many years now, and although I do not consider myself to be an expert-user I definitely know my way around. This book is really the only comprehensize "A - Z" source on IRC, and it is wonderfully-written as both an introductory text for IRC newbies as well as an in-depth compendium for power users. Even after using IRC for so long I could not believe how much I learned, particularly the last chapter which deals with server-side configurations.

Alex Charalabidis uses his expert knowledge of IRC to explain the network's subcultural quirks and expectations in all its many instances, and provides information about IRC on the whole in an amusing, almost rhythmical deliverance. In my opinion, a must read for all IRC users. Even Nick Burns, the company computer guy, suggests it! YOUR WELCOME!!!

I am an IRC junkie, so when I saw this book I just had to pick it up.

This book was written in 1999, and it shows. There are outdated server lists and statistics. The attacks described are mostly outdated (who "nukes" "jupes" and "floods" these days? This is only interesting from a historical perspective). The IRC clients described are now of outdated versions, and some of the now popular clients (xchat, irssi) aren't mentioned. The book claims to have a companion website with updates, which I was excited to see, but the site's domain (bookofirc.com) seems to have expired and been snatched up by an unrelated website.

All that aside, IRC is a pretty basic protocol, and most things about it haven't changed a whole lot, so this book is quite useful. It can walk someone new to IRC through the basics, describing what everything in the IRC world is, as well as providing experts with some interesting tidbits. The whole chapters on DCC and CTCP were especially informative to me. Appendix B "Terminology" was great for providing some of the "language" one might encounter in channels with tech/irc-saavy occupants.

The book even touches upon "IRC Netiquette" when it comes to what is acceptable or not behavior-wise in IRC (I think a whole chapter should have been devoted to this, this seems to be a major stumbling block to new IRCers). The fun way in which the author presents this book makes it very amusing to read, not at all like normal techical books (this is something I enjoy about all No Starch Press books).

In summary, this is a very informative book, even for someone like me who has been using IRC for over 6 years, and now run my own server. But it needs a second edition and/or the companion website revived.

This book is written by an experienced IRC user and operator and I can't think of anyone better qualified to write this book. Additionally, his sense of humor makes this book enjoyable to read as you find out about all the features of IRC. This book is useful for anyone who spends time on IRC, from the "newbies" to veteran IRC "addicts" like me. I wish there had been a book like this around six years ago, when I logged on to my first IRC channel.

Among the subjects the authors covers include a brief summary of IRC and its history, IRC clients for UNIX, Windows, and Macintosh machines, how to connect to an IRC server, finding various channels and people on IRC, and also a good description about the dreaded "net splits" and lag you will eventually run into on IRC. I just wish the author had gone into more detail about ways to deal with server splits and lag. Maybe the next edition will cover that.

More and more users are logging on to IRC all the time (which probably explains why it seems there's always those "splits" I mentioned) and this book is an excellent guide to what you can do on IRC and what to watch out for.

For anyone that uses Camtasia Studio, Daniel Park's Definitive Guide is just that. With an engaging and easy to digest style, Daniel leads you through pretty much every aspect of using this program suite to it's full potential.

Along the way, he also covers the intangible and often overlooked aspects of preperation, planning, and time saving tips and tricks that make it possible to produce a quality poduct with Camtasia.

Daniel Parks' book Camtasia Studio 3 is an excellent resource for those just beginning to learn the application or with a fair amount of knowledge about it. Although he doesn't delve into certain subjects as deeply as I would have liked (e.g., limitations with certain options), at 550+ pages you're still getting a good deal of information.

I've found one or two areas of the book I don't believe I agree with Parks on in how to manipulate the software, but maybe I'm just not reading his instructions in the way he intended.

If you've never used Camtasia but expect to need some of the lesser-used options, I highly recommend you buy this book when you buy the software. Good job, Daniel!

This book is my Camtasia "Bible." It's well-written and has answered a lot of questions I didn't even know I had. Now that Camtasia has moved to Version 4, I wonder if the book will undergo a revision to cover all the great new features.

If I could give 10 stars I would. THis book is the definitive guide to Camtasia and much, much more. The Camtasia part doesn't even start till Chapter 5. You spend the chapters before that learning about the how-to and why of 1) training, 2) marketing and 3) demo presentations. It's a Camtasia book and a How-To-Do-Great-Presentation book in one. And all done in an entertaining by the author's warm personable conversational style.
I wish the author would write more books. About Sony Vegas, about Serious Magic Ultra 2, about search engines. He is so good.

If you are serious about getting a proper understanding of Camtasia, then you definitely need this book. As far as I'm aware, it is the only such book available. Sure you can try using the Help material supplied with Camtasia, but it is difficult to learn well enough that way.

Camtasia Studio is a complex video recording and editing package, and there is a great deal of detail which is difficult to understand at first. Even with this book I'm needing to re-read whole chapters in order to get sufficient understanding of the suitable techniques to apply. The book isn't an easy read, but essential if you are to get maximum value from Camtasia.

The author, Daniel Park, has actually worked for the makers of Camtasia in the past, although he now works as a consultant. This gives him both an insiders and outsiders objective perspective, which allows a reader to get a fuller understanding of all the intricacies. The presentation is well-informed and conversational, although more attention could have been given to the learning needs of a naive user.

This is a very well-written study-guide. It gets to the point without getting too wordy. It could serve as a model for other study guides. But, I do have a few minor gripes. First, some of the pages were printed kind of blurry, a kind of shadow image. Second, there is too much preaching about what the author feels are best practices, some of which I question. Best practices questions are not on the exam, at least the one I took, and thus should be left out of a study guide except as perhaps small footnotes. There were also a few minor typos, but being a niche market I can forgive that for technical books.

This is pretty much the only material you need to pass the certification. I was thinking of getting the exam buster as previous reviewer suggested, but exam buster does not promise same day delivery of their products, and with the exam one day away, I had only this guide to rely on.

Here is the approach I took that might work for you as well if you are pressed for time: Work on the end of chapter exercises first, mark all the questions that you are unsure of, if you have the time, go back and read the chapters and correct your own mistakes (I skipped this one because of time issue), and finally check the answers at the back. Note all the ones you were unsure of or didn't get right and studied the reasons provided with each answer. If you don't feel confident of the topic or you have made enough mistakes in the questions, read that chapter.

Before I read the guide, I scored a 70% using Ben's site. After a day of going through the guide using the "algorithm" above, I got an Advanced certification the next day. It goes to show you how good the guide is. One thing to be aware of, some answers are not correct (ran into about 4-5 incorrect answers at the back of the book), thankfully the answer analysis are correct most of the time so you can catch any mistakes in the answers the book provides. Do Ben a favor and get this book, he really deserves the royalty.

Ben Forta's deep experience and practical application overflows from the pages of this book that I highly recommend. Of the dozens of computer books I've ever read, this one kept me astounded me with its perfect-sized chapters, handy reference and cross-reference segments, and the well-written pages. Not only is Ben Forta a good writer, he's an outstanding teacher.
Clarke Schroeder
Advanced Macromedia ColdFusion Certified

This is a very good book, however the coupon for 15% off of the exam is no longer valid. It expired December 31st of 2003.

This book does a good job of giving you information on every possible topic of the certification exam. I used the original study guide to take and pass the first exam. This book includes just about everything in the first book, and goes into topics that are relaevent for MX (i.e. CFCs, XML, Flash intergration, etc.). If you want answers in a few pages vs. a few chapters, then buy this book.

I would not consider this book to be a "practical" book, where someone could find a practical advices, which could be straight used in his/her daily testing activities.
I've noticed this book on test designers' table and looked into it for several particular topics. It is pity, but noone of them contained useful info:
1. Chapter #7; "Setting clear phase criterias" (I read the Russian version book, titles in English version may differ): actually no any CLEAR criteria written, but some well-known measurable criteria critisized as non-practical.
2. Chapter #14; "Choosing defects management tool": 1 page of text without NO any criteria mentioned, on what particular functionality a tool should support for particular tasks.
3 Chapter #3; "Using emperical methods for rough estimation": most of methods are just reference to other books/articles (well, I'm surely will use it to find numerical figures for estimating purposes), all other text is a copy of project management methods applied to testing.

I need to declare, that I did not read the book from beinning to end, which saved pretty of my time, and may conclude that opening a book on 3 topics of particular interest and not finding a bit of usefulness - is enough to not recommend this book for testing professionals.

Rex Black helps you think about how testing can help your projects. In particular, the planning chapters (using the running example project) make many of the planning and risk management issues obvious. This book will help you determine which activities make sense for you to perform, how to analyze quality risks, how to estimate the work, and how to speak the language of the business (return vs. cost). If you only read the first seven chapters, you'll be farther ahead in your thinking about testing and preparing your group to test than you ever were before.

The prepare chapters (8-11) help you determine which people to select for your team, and how to prepare your test infrastructure, considering that test managers always have limited budgets, people, or time.

A particularly valuable piece of the perform chapters (12-13) is the discussion of how to manage the test builds, who owns what -- how to remove confusion from "which build do I test now?" to an organized plan of handoffs.

And in the perfect chapters, if you've been looking for a way to teach how to write test reports, chapter 14 is your answer.

If you're a manager, you'll use this book on every project, even if you only review the checklists to see if you've missed anything. If you'd like to become a test manager, read this book. Rex describes numerous ways of managing the testing and working with your peers across the organization, to become successful.

I highly recommend this book, whether you're starting a project, in the middle of a project, or completing one.

Sometimes a book comes along that just has to become part of your virtual profesional toolbox. Mr. Black has just given us poor testers another such book.
For me this book provides me with all the tips and tricks that I need during a project and that I would have to think of myself instead of just picking up this book and reading about them.
Even better, I now have an excellent source of course materials for our test engineers. Mr. Black explains and justifies every aspect of the testing process just about perfect and his gift for the metaphor makes this book a good evening read.
The checklist approach that he employs is a great planning aid. Our projections are much more precise this method.
I have added this book to our technical library for this project, and I will insist on making it part of every future test project that I will be part of. That is until Mr. Back publishes his next book.

Rex Black's latest book, "Critical Testing Processes" belongs in every test engineering library. Rex's book is logically organized; Part I, Prepare, embraces Chapters 1 through 7. He begins with a discussion of Planning, the first phase in the testing lifecycle, focusing on Quality Risks to assist test planning, He provides one of the best step-by-step examples I've seen to develop a test estimate. Rex sets the stage for us by showing how testing fits into the larger project context, and defining a 15-step testing process. He defines the context of his case study on the Sumatra project. In this chapter, Rex shows one of the nicer examples of the classic "V-Model" relating the development and testing lifecycles.
In Chapter 2, Rex explores the subject of Analyzing Quality Risks as the basis for his test planning, and shows a variety of templates and techniques that will assist the reader in performing this process, and links them to his case study. Note that using Quality Risks may have to be coupled with requirements/feature coverage on contracts with a government customer.
I believe that Chapter 3 (Gaze into the Crystal Ball; Estimate the Work Ahead), is one of the most helpful guides to Test Estimating that I've seen. Rex provides a variety of templates to assist folks unfamiliar with building a testing estimate.
Chapter 4 shows how testing provides "value-add", and gives the reader insight into aligning the initial estimate with the financial constraints of the project. Rex discusses ways to reduce cost by focusing testing based on the Quality Risks, in the context of the Sumatra case study. Templates, spreadsheets, and methods for calculating testing cost and return on investment are supplied.
In Chapter 5 Rex shows how to take the realistic estimate that was created and sell it to the project team. He also has a section titled "Predict with Honesty", which emphasizes the necessity for Ethics in our business.
Chapter 6 discusses the significant efforts in continuous test planning, It uses a variety of excellent figures to illustrate the author's points; however, note that there are 2 Figure 6-5's in this chapter, which results in the remaining figures being mis-numbered.
Chapter 7 goes into detail on how to get stakeholder support for the Test Plan. The Test Plan is the keystone for successful testing. Rex also provides an interesting section on what to do "When Key Players Don't Support the Test Plan" and how to work in a regulated (e.g., export restrictions) environment.
Chapters 8 through 11 are the section titled "Prepare". Chapter 8 on hiring testers is another area of the book not dealt with in many texts, but is extremely critical to successful testing. There are several parallels here to the Perry/Rice book "Surviving the Top Ten Challenges of Software Testing".
In Chapter 9 Rex provides pointers to career growth in a testing team, and assessing skills of the team members. He gives some tips on creating job definitions. He also addresses the challenges posed by having to accept team members other managers don't want, and use of contractors and consultants. Good chapter!
Chapter 10 gets back into the more technical side of test management. Through his Sumatra case study, he provides some insights into stress testing, and use and support of test tools.
In Chapter 11 Rex discusses details of approaches to test coverage, test design, selection and implementation of automated tools. He also takes some time to discuss approaches to "vague requirements", which is a problem most of us face.
Chapters 12 and 13 are Part III, Perform. Rick provides an excellent discussion of management of test releases in Chapter 12. This discussion is nicely illustrated through the case study. Note that you need to have the ability and a mechanism to UNINSTALL any release.
In Chapter 13 Rex defines a test execution process, and then goes on to show how that process works. He defines a set of test tracking worksheets, and illustrates use of the process and the worksheets on "the Big Build".
Chapters 14 through 17 are Part IV. Rex defines the Bug Reporting process. He describes use of this process through application to "the Big Build". He goes on to show how to, and how NOT to, report bugs, and emphasizes the necessity of describing one symptom per bug report. One caution in this chapter; Rex uses shaded boxes to emphasize points. Several of these boxes were misplaced in the book assembly process, so the reader needs to use care in navigation on pages 391 through 394.
The title of Chapter 15 seems a little misleading to me, in that it doesn't deal with writing a Test Summary Report (IEEE definition), but rather with the critical, on-going process of reporting test metrics. Rex focuses on describing the creation of a "test dashboard", and use of that dashboard for providing a succinct delivery of test status. Rex describes what I believe are a useful set of metrics charts. Unfortunately, the book assembly process resulted in Figures 15-2 and 15.3 being reversed, which led to much confusion on my initial read.
In Chapter 16 Rex discusses change management as it applies to bug fixes. The Sumatra case study is used to provide an informative view into the change management process. Rex notes that such a process must balance considerations of features, schedule, budget, and quality by assessing impacts from all project groups.
Rex concludes his book with Chapter 17 with some thoughts as to how testing can provide value.
Rex finishes up with a Glossary that defines his terms.
A suggestion for the interested reader. Read Rex's book in concert with the book from Drabick titled "Best Practices for the Formal Software Testing Process: A Menu of Testing Tasks". Drabick's book shows the reader "What to Do"; Rex Black's book shows "How to implement the What".

This book is written for the test manager and/or project manager who oversees one or more testing efforts. The author has done a great job of taking his own personal experiences (good and bad) gleaned from years of "in the trenches" work, and threading them together into a single fictional story that he uses to illustrate his proven method of managing testing projects.
Part 1 (Chapters 1 to 7) talks about the stuff you need to do to Plan for a testing effort, such as; convincing senior management that spending money on testing is a good Return On Investment (ROI), how to get a realistic ballpark estimate for how long the testing is likely to take, and when & who should get involved in the project.
Part 2 (Chapters 8 to 11) deals with Preparing for test execution; selecting test strategies & techniques, putting a testing team together (and keeping them together), and determining the appropriate measure(s) of test coverage
Parts 3 & 4 (Chapters 12 to 17) first focuses on perhaps the most stressful phase of a testing project - test execution. When the "heat of battle" is most intense; it's useful to have examples, templates, and checklists that a test manager can draw upon to help them manage and report on the test execution in a controlled and credible manner. The book then wraps-up by discussing process improvement; what went well, and what could have been improved (no witch hunts please!).

In summary, I believe Rex has built a very comprehensive and detailed composite documentary on how he has defined and deployed the most critical processes needed to support a software testing effort.

In the vain of "full disclosure", you should know that I've known Rex for many years, and consequently I cannot be considered a completely impartial reviewer.

I've only been working with Crystal for a few weeks but am already putting together some pretty decent reports. I could not have done it without this book. After such a short amount of time my copy is somewhat dog-eared and filled with yellow post it notes for quick reference to the things I need. It is open at my desk whenever I work with Crystal.

If you are a Crystal novice this book provides an excellent foundation for Crystal Reports. If you are an intermediate/advanced user there is plenty here for you as well. I especially like the financial twist the report provides since most of my reports are payroll, general ledger and accounts payable/receivable related.

The discussion forum associated with the book is also an excellent resource. I was "stuck" on a couple issues and was helped by both the author and other users on the forum.

Bischof's book is a complete, well-researched reference that quickly arms a novice Crystal Reports user with the techniques necessary to create sound, well-formatted financial (and other) reports. The appendix on Balance Statements and Income Statemens is a fabulous jump-start for those who must get up to speed quickly! If Crystal Reports is your platform for information delivery, this book belongs in your library.

The very clearly written style, REAL WORLD EXAMPLES!!!, and great technical content make this book a must have for Crystal Reports Development.

5 Stars

This is my first crystal report book and i can say this is the best crystal report book ever i found. Every chapters has a lot of Tutorials and Tips.

This book - like others written by Brian Bischof - is well laid out and clearly written. It has many excellent examples, and they are easy to find and utilize. It is also quite apparent that he has gone to considerable effort to illustrate the many new features that are to be found in CR XI.

I have had to purchased numerous books in the last year, trying to understand the differences between Visual Basic ver. 6 with Crystal Reports ver. 6, and Visual Studio.NET 2003 with its version of Crystal Reports and beyond to VS.NET2005 and CR-XI. Brian's books are the only ones that I have close at hand for when any problems arise.

Comments from using the electronic version of the book at books24x7.com.

I read the entire book for use on a capstone project I'm working on. This book hammered home many of the exact concepts I believed were present, but couldn't prove. I work in IT for a multi-billion / year company. Many of the issues Tom describes are the exact issues we've either gone through or are currently struggling with.

Key concepts for me:
1) IT cannot be responsible for data quality, but they are definately involved.
2) Data quality is a multi-facted management issue.
3) Quality has to be defined by the each organization. (i.e. what's good enough for company A may be substandard for company B.)

I also noticed the website address listed in the book is obsolete and has been replaced with this:
http://books.elsevier.com/companions/1555582516/?country=United+States

Have actually improved performance results by implementing many of the techniques found in the Field Guide (tips have helped me in a number of places and ways). An easy read. Practical, applicable and actionable.

This is an excellent everyday guide to data quality. Easy to read and filled with tips and techniques for starting and improving a data quality program. The field guide format makes it a great reference book.

Good practical advice for improving data quality. Covers the most common data quality problems. Well written. Some other sources to look at online:


http://www.dmreview.com
http://www.datalever.com

I like this book quite a bit because although it's not a huge doorstop of a tome in terms of length, it's quite complete and thorough. Some data quality books cover management aspects, some the technical aspects, and some take other angles. This book takes a look at all of the different angles on data quality and sums them up into a very nice package.

One of the things I liked about it is the section on social aspects of data quality, since so many technical people I work with have a great idea but aren't able to implement it for lack of understanding of the social aspects of working on data quality projects. Another is a part where Redman goes through the process of how data quality is tracked over time, to see if things are improving, and the way that he draws a distinction between records that are "perfect", and records that are "usable", which points out some differences that are important. There is even a very relevant section on data quality problems in the US elections of 2000.

The nice thing about this field guide is that it should have everything an organization needs to do some serious data quality work (including even middle management roles and responsibilities). I think it's a very solid book that would be a great addition to data manager's and other tech manager's libraries.

The Delphi 2 Developers Guide is the authoritative source I consult for advanced programming topics in Delphi. This book is aptly marketed as an expert level book. It goes well beyond the scope of the "This is Delphi" books typically found on store shelves. An underrated feature of this book is its comprehensive appendices of error codes. I highly recommend this book to anyone serious about Delphi programming

When many computer books today are just a rehash of the documentation, this book stands out as a real problem solver.
Although this book is not geared towards the beginner, if you are serious about developing applications in Delphi, this book should be on your shelf. In depth explainations and real world examples make this book well worth the price. Specifically helpful chapters include explainations of Windows Messaging, the Win32 API, multi-threaded applications, OLE, and more. There are also some very good chapters on porting your applications to Delphi 2 (32-bit) and differences between 16-bit and 32-bit applications.
As a Delphi developer, I keep this book handy at all times, and I am looking forward to the Delphi 3 version

Xavier and Steve do an excellent job of delving into the more advanced aspects of Delphi 2 and Win32 development, without wasting a lot of time on the 'newbie' stuff. Highly recommended!

If you want to do some serious work with Delphi, this book is for you. I covers virtually everything you must know about Delphi. Thanks to the authors.

THIS BOOK is art of perfection. No more to say. THANKS to the authors