The Latest

Models are useful in different settings in different ways. Models can test facts, ideas and understanding, simulate operation, and aid coordination between systems and people. In this column, Becky Winant lists six model patterns she has seen in practice in software development organizations, talking about where each is appropriate, and the strengths and weaknesses of each.

Summary:
Where do you find new testers? For the most part, the answer is typically not "from your local university computer science or software engineering department." Testing just isn't taught as a subject in most university curricula. Here, James Whittaker suggests ways to get testing into your university.

Robin Sahner looks at generating test code with Teradyne TestMaster. His group evaluated TestMaster on two projects. It did what they hoped it would, and now they're using TestMaster on all of their projects. They're not employing it to shorten their test development time or use fewer people; instead they plan to use it to get a more complete, more easily maintained set of functional tests using the same resources. Editors Note: Teradyne SST has become a new company called Empirix.

Analysis of bug reports from previous projects tells us about our most frequent errors, and can help us improve. But very few companies spend the time to analyze bugs from completed projects. Otto Vinter and Soren Lauesen explore using bug reports to improve the software development process.

Alyn Wambeke interviews several software consultants for their take on the ups and downs of working on their own. He also gives pointers on getting started, and on how to determine if you're up to the challenge.

Every system contains at least one (and probably more) set of requirements that fits into one of these categories: the functional who, what, where, when, why, how, and the nonfunctional design and project constraints. No one method or technique captures all requirements, but this approach can assist quality engineers in identifying missing requirements. Our objective is to spot the gaps in the requirements sets—just as a Tetris player spots gaps in those moving blocks—as soon as possible.

Jerry Weinberg's workshops and writings have taught, encouraged, and inspired many people over the years. In this interview by Beth Layman, Jerry gives insightful and entertaining answers about the state of the practice, becoming a technical leader, and the future of software engineering.