Better Software Articles

Please enter an article title, author, or keyword
Analyzing Requirements Bugs

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.

Søren Lauesen's picture Søren Lauesen
No More Whining

Johanna Rothman urges test managers to stop whining and deal with the "Not-Enough" problem. She concludes: "You have more capability to influence attitudes, behaviors, and actions in your organization than you know. If you feel like a second-class citizen, reframe the situation. Rethink your job and how you do it, and realize the importance of the contribution–finite, but powerful–you can make toward your organization's product quality."

Johanna Rothman's picture Johanna Rothman
Flying Solo: Is Consulting for You?

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.

Alyn Wambeke's picture Alyn Wambeke
Visual Modeling with Rational Rose

Darren Pulsipher looks at Visual Modeling with Rational Rose. He concludes: "Rose is far from the perfect Visual Modeling tool, but it is definitely one of the best OO tools on the market, and the most popular. Rational Software has done a great job in supporting its tools with user conferences, training, professional services, and seminars."

Darren Pulsipher's picture Darren Pulsipher
Are Your Requirements Complete?

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.

Patricia L. Ferdinandi's picture Patricia L. Ferdinandi
When Applications Collide

Having multiple applications installed and running on a personal computer system presents interesting challenges for testing, even if all the applications are from a single vendor. Bill Mullins imparts some lessons he learned while testing multiple applications.

Bill Mullins's picture Bill Mullins
Software Tester Certification Options

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

Alyn Wambeke's picture Alyn Wambeke
Twenty Years Ago

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."

Steven M. Smith's picture Steven M. Smith
Bugs Beneath the Surface

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

Brian Marick's picture Brian Marick
Re-creating Me

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.

Maureen A. O’Hara's picture Maureen A. O’Hara

Pages

Upcoming Events

Nov 28
Dec 04
Jun 25
Sep 30