Please enter an article title, author, or keyword
Streamlined Change Request Management

Most start-up companies start with paper-based change request management tools and then migrate to automated solutions. Many of the change request management tools available on the market integrate with the change management tool, and ensure that all bug fixes in the code are controlled and managed. Critical bugs reported while the product is in the field require immediate code fixes. The origin of some of these bugs is in the early development phases of requirements and design and may require documentation changes. When the number of field reported bugs is high, maintaining the traceability of the fixes is critical to future development activities. Also, research shows that over 70% of the defects originate from the requirements and design phases and that the cost of fixing these defects in successive phases increases exponentially. The key then remains in developing a change request management tool, which integrates with the CM tool and tracks the changes to the impacted configuratio

Nikhil Kalyanpur
CMM: The Road Not Taken

This article discusses the successful aspects of process improvement efforts that are not explicitly addressed by the CMM, but which are critical in achieving business and process improvement goals. It also summarizes the lessons learned by an organization that matured with these practices.

Shiva Kumar
Starting a Metrics Program

This article explains a set of six metrics, which collectively provide valuable insight into:

a) Effort variation
b) Assessing the organizational capability
c) Knowing how well the organization meets its commitments on time
d) Defect detection capability of QA&QC activities, hence control on price of conformance
e) Defect leakage across the phases of projects, organization wide
f) Productivity metrics - a sure input to scheduling

These six metrics are easy to understand and implement. The cost of implementation will be minimal, if the basic systems like time tracking and defect tracking systems are in place, and the organization follows a standard method for project size estimation.

Abrachan Pudussery's picture Abrachan Pudussery
A Comparison of IBM's Orthogonal Defect Classification to Hewlett Packard's Defect Origins, Types, and Modes

In the last three years, the author has worked with seven Software Development teams to help them categorize defects using Hewlett Packard's Defect Origins, Types, and Modes. More recently, the author has assisted a software testing and development organization analyze the results of defects categorized using IBM's Orthogonal Defect Classification (ODC).

John Huber
How Did I Get So Jaded?

Churning out medium-grade software to meet deadlines, and experiencing critically defective projects over the years, can easily wear down optimism till it gives way to cynicism in the software testing and quality professions. In this column, Eileen Strider empathizes with that tendency and offers ideas that may improve the quality of your experience.

Eileen Strider
Removing Requirement Defects and Automating Test

Organizations face many problems that impede rapid development of software systems critical to their operations and growth. This paper discusses model-based
development and test automation methods that reduce the time and resources necessary to develop high quality systems. The focus is how organizations have implemented this approach of model-based verification to reduce requirements defects, manual test development effort, and development rework to achieve significant cost and schedule savings.

Mark Blackburn
Designing an Automated Web Test Environment

This paper offers an alternative to the typical automated test scripting method of "record and playback now and enhance the automation environment later." It explores a regression automation system design for testing Internet applications through the GUI, along with scripting techniques to enhance the scalability and flexibility of an automated test suite. This paper will present a basic
structure for an automated test environment, and will expand on each of the items found in that structure. Web testing levels will be laid out, along with a basic approach to designing test scripts based on those Web-testing levels.

Dion Johnson's picture Dion Johnson
When Test Drives the Development Bus

Having finished our last project, which ended as a fire drill as usual, the managers of development and test concluded that we didn't ever want to go through that again. All agreed the test team had been riding the development cycle bus long enough.

Cindy Necaise
How to Jump-Start Inspection by Outsourcing

Even though the benefits of inspection have been extensively documented, you may find it hard to introduce this practice into your development process. A novel approach to finding defects, an outsourced software inspection service is easier to introduce and has successfully jump-started inspection in the software development organizations of major telecommunications and industrial process companies.

Jasper Kamperman
Configuration Management for Distributed Development

Configuration Management (CM) includes synchronizing and supporting developers in their common development and maintenance of a system. In order to utilize skilled personnel despite geographical location, groups of developers are now working all over the world on the development of common systems, a situation called distributed development. This article discusses the different cases and architectures with respect to distributed development and their demands on Configuration Management Tools. It also presents the features of some currently available CM tools that support Distributed Development.

Nina RajKumar


Upcoming Events

Apr 26
Jun 07
Oct 03
Nov 14