The Latest

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.

Increased demand for test expertise has generated interest in testing-specific professional certifications. Alyn Wambeke sorts through certification options for testers.

In comparing himself today to his younger self, Steve Smith says, "I've changed. The work that interests me wouldn't interest Young Steve. Although Young Steve would outdo me technically, I could compete in that arena: Young Steve couldn't compete with me in my new mission."

Brian Marick uses two bugs to illustrate a small, but valuable, test design tip: Try the next thing that a user would try.

Change is the watchword of life in the software world--perhaps no field has grown and transformed itself as quickly as our industry. To survive and succeed in this business we must truly be masters of change; those who have been the most successful are the ones who have been able to use change as a tool and catalyst. Maureen O'Hara describes how change can be an agent for growth.