Most people in the software field don't seem to understand even the basics of what software quality means, even those who are labeled as quality "experts." They see it as being error free, satisfying users, meeting requirements, or hitting cost or schedule targets. But in reality, it's only partly about some of those things, and not at all about others. In this column, I try to set those erroneous viewpoints aright.

Inspections are hard to do for small and immature organizations. This paper shows a way to introduce author reader cycles without going all the way to extreme programming practices.

Ms. Dekkers and Ms. Hendrickson talk about Elisabeth's five-step process for choosing a tool for your organization: Defining Initial Requirements; Investigating Options; Refining Requirements; Narrowing the List Down by Priorities; and Evaluating the Final List, Bringing in the Tool Vendors.

This papers on an analysis of a suite of tests and methods that have matured over many years. The author examinea aspects of testing from initial through mature stages of an in-use software product.