Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Download
Standard view
Full view
of .
Look up keyword
Like this
6Activity
0 of .
Results for:
No results containing your search query
P. 1
A Guide to Evaluating a Bug Tracking System

A Guide to Evaluating a Bug Tracking System

Ratings: (0)|Views: 348|Likes:
Published by api-3806986

More info:

Published by: api-3806986 on Oct 17, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

03/18/2014

pdf

text

original

\u00a9 Copyright MetaQuest Software Inc.
A Guide To Evaluating a Bug Tracking System
White Paper
By Stephen Blair, MetaQuest Software
Published: October, 2004
Abstract

Evaluating a bug tracking system requires that you understand how specific features, such as
configurable workflow and customizable fields, relate to your requirements and your current bug tracking
process. This article provides tips and guidelines for evaluating features, and explains how these
features fit into a defect tracking process.

Stephen Blair is a programmer-writer at MetaQuest Software, developers of the Census bug tracking system as well as solutions for e-support, application self-healing, and desktop management.

Web site:www.metaquest.com
Telephone: 514 341-9113
Fax: 514 341-4757
E-mail:mailto :inf o @metaquest.co m

\u00a9 Copyright MetaQuest Software Inc.
Evaluating Bug Tracking Systems
i
Contents

Contents........................................................................................................................i Introduction.................................................................................................................1 Adaptability..................................................................................................................2 Bug Change Histories...................................................................................................3 Customizable Fields.....................................................................................................4 Notifications.................................................................................................................5 Ease-of-Use..................................................................................................................6 Security........................................................................................................................7 Reports and Metrics.....................................................................................................8 Workflow.....................................................................................................................9 Version Control Integration.......................................................................................10 Web-based Client.......................................................................................................11

\u00a9 Copyright MetaQuest Software Inc.
Evaluating Bug Tracking Systems
1
Introduction

Before you start evaluating bug tracking systems, make sure you identify your requirements for the system. Understanding these requirements will help you build a list of features that you can use to guide your evaluations.

To identify your bug tracking requirements, take a look at your current bug tracking process.
\u2022
What are the different roles and responsibilities of the people who will use the system?
\u2022
What is your workflow for managing and resolving bugs? Identify the steps in the process,
and determine who is responsible for each step.
\u2022
What information do you need to track for each bug?
\u2022
What reports and metrics do you need?
\u2022
Do you need to provide different levels of access to different users?

Once you identify your requirements for the system, you can translate the requirements into a \u201cfeature list\u201d. Table 1 provides an example of a feature list that could be used to evaluate a bug tracking solution

Table 1. List of features to evaluate

Adaptability
Change history
Version control integration
Customizable fields
Ease of use
E-mail notifications
Reports
Security
Web-based client
Workflow

The rest of this document provides tips and guidelines for evaluating these features. Hopefully
these guidelines will help you choose a bug tracking system that meets your requirements.
Remember, the purpose of a bug tracking system is to support your process, not to impose its
own.

Activity (6)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads
swathimc2008 liked this
ethanhuntnani liked this
sanjiv8620003463 liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->