Track Them Darn Bugs!
How do you choose a defect tracking system? There are so many choices. Small, large, client-server, multi-platform, expensive, cheap; integrated with source code control systems, call tracking systems, sales support systems...;
What to do?
In this one day seminar we'll study your user's requirements, get a quick overview of different approaches to defect tracking, and compare vendor's solutions.
Do you clearly understand your defect tracking system's requirements?
- Who are the users? The scope may be wider than you thought!
- What kind of system do you really need? Fast? Reliable? Inexpensive? Enterprise-wide? Your needs today and tomorrow.
- What other systems need to be connected to your Defect Tracking System? Call Tracking? EMail? Configuration Management? Other databases?
Do you know what it takes to track defects?
- Walkthrough a prototypical defect database data dictionary. Learn various schemes for classifying defects; IEEE 1044 Standard Classification for Software Anomalies, Simple Bug Model, Fault-Failure Model.
- Follow a defect through its life cycle, from original reporting, investigation, resolution, to retirement. Examine critical information which must accompany each defect.
- Issues associated with defect information: Causal Analysis, Ping-Pong Effect, Patterns of defect motion, Mean Time to Repair.
Examine aspects of some commercial defect tracking systems.
- $500,000 heavy duty client-server systems, $350 single desktop applications, roll-your-own desktop databases...
Debrief and summarize - look at next steps.
- What are your choices?
- How much is it costing you NOT to choose?
Who should attend?
Those who are going to choose a system, and those who'll have to live with that choice; Development Managers,
QA Managers, Developers, Quality/Test Engineers, Customer Support Representatives, Documentation Specialists.
One Day - No limit on attendees
Last updated: 27-Feb-1998
Copyright © 1996 by Brian Lawrence. All Rights Reserved.