Better Software Magazine Articles

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
June 30, 2002
Defect Management with Soffront TRACK Defects

Margaret Ramsey looks at Defect Management with Soffront's TRACK Defects. She concludes: "If this tool meets your requirements and its pricing isn't out of your ballpark, it's definitely worth considering. With its customizability and ease of use, TRACK Defects is one tool that should be on your evaluation list."
Margaret Ramsey
June 26, 2002
A Look at Bug Tracking Using Bugzilla

Robert Sievers manages QA on the development of Abi-Word, a cross-platform free-use open source word processor. When it came time to pick a bug tracking system, he looked into Bugzilla, the open source bug tracking system created by mozilla.org, and found that the open source development model worked just as well for QA tools as it does for utilities and applications.
Robert Sievers
June 26, 2002
A Look at TeamTrack 3.0, a Web-Based Defect Tracking Tool

George Hamblen and Stephen Bailey look at TeamShare's TeamTrack 3.0, a Web-based defect tracking tool. TeamTrack offers a fully functional defect tracking system over a company intranet. Since all of the functionality is offered from the server, this means each desktop needs only a browser to access the system.
George Hamblen Steve Bailey
June 26, 2002
Does a Bug Make a Noise When It Falls in the Forest?

You've probably heard the question about noise in the forest: Does a tree falling in the forest make any noise if no one is there to hear it? Noel Nyman examines the question, "Is a bug a bug if no user can ever make it happen?"
Noel Nyman
June 26, 2002
Writing Effective Bug Reports

Have you ever had a bug returned to you for more information? Have you ever found a critical bug only to have it deferred to another release? Elisabeth Hendrickson tells you how to write effective and informative bug reports that will get noticed.
Elisabeth Hendrickson's picture Elisabeth Hendrickson
June 26, 2002
Tracking Severity: Assessing and Classifying the Impact of Issues (a.k.a. Defects)

How does one categorize Severity? Should you use numbers like 1, 2, 3; generic names like High, Medium, Low; or more specific names? A telephone switching system, for example, might use industry-specific categories such as "system issue," "line issue," or "call issue." Other environments, as we'll see in this article, tailor classification terms to meet their own functional needs.
Tim Dyes
June 26, 2002
Software Measurement Programs

A metrics program is any planned activity in which you use measurement to meet some specific goal. If you do not have a clear technical goal for a metrics program, then you are almost certainly not ready for such a program. Here's how to design a measurement program that leads to decisions and actions.
Norman Fenton
June 26, 2002
Bringing Your Test Data to Life

Tracking test results is one of the fundamental tasks that your software testing organization must perform to be successful. Explore how a customized database can enhance that process.
Len DiMaggio
June 26, 2002
In Search of Defect Tracking Systems

Defect tracking systems influence business-critical decisions. Building and installing a corporate-wide defect tracking system takes a small but well-balanced development team. Your implementation may be as simple as opening the package and typing "setup" or it may take months of programming. Here's how to find and implement the right system for your organization.
Bob Johnson
June 26, 2002

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.