Stalking The Wild Software Defect



Email    print   
August 15, 2002 —  (Page 1 of 5)
Some development managers release impressive software armed with only a spreadsheet, a pile of Post-it notes and a confident attitude. Others, equipped with every QA tool imaginable, have never met a deadline. Clearly, bug-stomping success isn't the result of tool quality, but of your ability to get the most out of the tools available.

According to successful bug hunters, the key to effectively using QA tools (by which we mean anything in the configuration management pantheon, from bug-tracking databases to version management to source-code control) is to view the system as something more than software. "Like e-mail, defect-tracking systems are inherently a vehicle for carrying on a conversation that's disjointed in location and time," explained Elton Hay, a consultant who specializes in QA tools. "[The] ability to facilitate is one of [their] main functions." Ideally, QA tools enable team members to communicate about a project's status, control the process a bug goes through, avoid redundant work, and engage the development staff in taking ownership of the code.

Bug-tracking applications control what happens to any bug entered into the system. That process, at best, can reflect only the efficiency of your organization's workflow. "The software enables us to implement the QA process we have in place," said Mike Cooper, QA manager at financial consulting company Revenue Technologies Corp., which uses Seapine Software Inc.'s TestTrack. "You have to know that before you can do anything else."

So, the first step is to determine that workflow. "What is the current development process? Is it documented? Is it followed? Is it followed consistently throughout the entire organization?" asked Mark Griffith, senior consultant at Merant International Ltd. The more "yes" answers provided, the easier it will be to deploy and use the chosen QA tools. "Draw a physical flowchart or workflow diagram," advised Cooper.

As part of the workflow process, consider which staff members need to see which items, who supervises the process, who assigns bugs to be fixed. "Defining the flow of work through the software is probably the most important part of using it," said Jay Varner, director of programming at Data Information Management Systems, which makes election management software and relies on Red Gate Software Ltd.'s tools.




Pages 1 2 3 4 5 


Share this link: http://sdt.bz/26693
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
New York City to open Academy for Software Engineering
High school would give foundational education in technology Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb